Accounting & ERP

Your accounting system is the foundation of your plan in Peaky, so connect it first. Each sync brings in your legal entities, chart of accounts, customers and suppliers, and posted transactions. They become your Ledgers and Transactions, fill the statement widgets on Views, and feed the Accounting & ERP tab on Metrics — one series per ledger group, split by entity and, when you track them, by dimension. ERP systems — Odoo, Business Central, Dynamics NAV and SAP — bring the operational side of the business as well: sales, purchasing, stock, pipeline and people, as metrics on a tab named after the system. You find all of these integrations under the Accounting & ERP tab on the Integrations page.

The general flow is on Connecting an Integration. When your company has more than one legal entity, connect from the Integrations page of the entity whose books these are.

Integration

How you connect

Notes

Exact

Sign in to Exact

Brings in every division; you choose the main one

Octopus

Sign in to Octopus

Choose a dossier before the first sync can run

Sage

Sign in to Sage


QuickBooks

Sign in to QuickBooks


Yuki

API key


EMAsphere

Tenant ID and access key

Brings in every company in the tenant, with ledger mapping

Light

API key, or OAuth with your own client

Also brings in the spend side: invoices, cards, expenses, purchase orders, contracts

Rillet

API key

Also brings in billing, payables, banking and ARR

Odoo

URL (or a Peaky Connector), database, username and API key

Metrics from the Odoo modules you choose, and your people for Headcount

Business Central

Sign in with Microsoft, then choose a company

Also revenue, costs and invoicing metrics

Dynamics NAV

Server address (or a Peaky Connector), OData version, company, username and access key

Also revenue and costs metrics

SAP Business One

Sign in through your identity provider, or username and password

Also revenue, costs, orders, invoicing, pipeline and headcount metrics

SAP S/4HANA

Your tenant's addresses, then sign in

Same as SAP Business One

Odoo, Dynamics NAV, SAP and self-hosted servers must be reachable from the internet — see On-premise and self-hosted servers. An Odoo, a Dynamics NAV or a SAP Business One that only runs on your own network can be reached through a Peaky Connector instead — see Odoo, Dynamics NAV and SAP Business One through a Peaky Connector.

Single-entity companies. When the first accounting sync brings in exactly one set of books, those books become your workspace's only entity, so the entity switcher does not show a separate empty entity next to your real data.

If your own login at the provider cannot authorize Peaky — common when you are not the administrator of the books — use Ask someone else to send a connection link to your accountant. Links can be completed for Exact, Octopus, Sage and QuickBooks.


Exact

  1. Find Exact under the Accounting & ERP tab and click Connect.

  2. Sign in to Exact Online and approve access. The in-app connection uses the Belgian Exact Online site; if your Exact account is in another country, contact support.

  3. You return to Integrations with the Exact Settings open. Your current Exact division is already selected — check it, or pick another under Select Division. See Integration Settings.

  4. The first sync starts straight away.

What syncs: every division your Exact account can see, each as its own entity, with the division you selected as the main one. Per division, Peaky brings in the chart of accounts, customers and suppliers, cost centres and cost units (usable as dimensions), and transaction lines.

Deleted lines. When you delete financial transaction lines in Exact, the next sync removes the matching lines in Peaky as well, so your metrics, statements and model never keep lines that no longer exist in your books.


Octopus

  1. Find Octopus under the Accounting & ERP tab and click Connect.

  2. Sign in to Octopus and approve access.

  3. You return to Integrations with the Octopus Settings open. Choose the dossier to read under Select Dossier — see Integration Settings.

  4. Click Sync on the card, or wait for the next daily sync.

Octopus does not pick a dossier for you, and the first sync fails until you have chosen one. If you connected during first-time setup, open Integrations afterwards and choose the dossier there.

What syncs: the selected dossier's book years, chart of accounts, customers and suppliers, and bookings. Each sync refreshes all posted transactions of the dossier, so Ledgers, the statement widgets and Metrics → Accounting & ERP match what is in Octopus today. When Octopus adjusts or renumbers booking lines on a document, Peaky keeps amounts and cost centre breakdowns aligned with Octopus instead of treating each adjustment as a separate entry. Run a manual sync after correcting entries in Octopus if figures in Peaky look out of date.


Sage

  1. Find Sage under the Accounting & ERP tab and click Connect.

  2. Sign in to Sage and approve access.

  3. You return to Integrations and the first sync starts.

What syncs: your business, its chart of accounts, contacts and ledger entries. After the first sync, each sync picks up what changed since the last one.


QuickBooks

  1. Find QuickBooks under the Accounting & ERP tab and click Connect.

  2. Sign in to QuickBooks Online and approve access.

  3. You return to Integrations and the first sync starts.

What syncs: one QuickBooks company per connection — its chart of accounts, customers and vendors, and transactions on an accrual basis. The first sync goes back to the start of the company's books; later syncs pick up from the last one.


Yuki

  1. Find Yuki under the Accounting & ERP tab and click Connect. A dialog explains how to create a key.

  2. Log in to your Yuki account and open the settings page (usually under the "more" options menu at the bottom left).

  3. Click Webservices in the Integrations section, then the + button.

  4. Fill in the form — Type: Entity; Entity: your entity; Rights: All webservices — and click Save.

  5. Copy the API key, paste it into API key in Peaky and click Connect. A Yuki key looks like a1b2c3d4-e5f6-…; anything else is refused as API key is invalid.

What syncs: the chart of accounts, customers and suppliers, and posted transactions of the first administration the key can see. Yuki projects come through as cost centres.


EMAsphere

  1. Find EMAsphere under the Accounting & ERP tab and click Connect.

  2. Log in to the EMAsphere platform and go to Share > Access Keys.

  3. Click + to create a new key.

  4. Copy your Tenant ID and the Access Key into the form in Peaky, and click Connect.

Several companies. One connection brings in every company in your EMAsphere tenant. When a sync finishes, the follow-up — turning the data into metrics, recalculating the model, checking for drift and updating statements — runs for each company that received data, not only for the entity where you connected.

Ledger mapping comes with it. EMAsphere already knows which ledger belongs in which group, and Peaky takes those assignments over. Once the first sync has been processed, your ledgers are already in their groups. Review or change the assignments on Ledgers at any time.


Light

Light is an accounting and spend-management platform, so it feeds Peaky twice over: your books land in Ledgers like any other accounting source, and the spend side arrives as tables you can build metrics on, with a starter set already made.

  1. Find Light under the Accounting & ERP tab and click Connect.

  2. In Connect Light, choose API key (recommended) or OAuth.

  3. Fill in the fields for that method (below) and click Connect. With OAuth you then sign in to Light and approve access.

API key: in Light, go to Settings → API Keys, create a key, and paste it into API key.

OAuth: Light does not give Peaky a shared app, so OAuth needs a client of your own:

  1. Select OAuth and copy the Redirect URI to give to Light.

  2. Ask Light's helpdesk for an OAuth client ID and secret for your environment, giving them that redirect URI.

  3. Paste the Client ID and Client secret into the dialog.

Your client ID and secret belong to your connection only. Light rotates its access, so Peaky renews it on every sync; with an API key, syncs keep using the key until you replace it.

What syncs: your company entities, chart of accounts, vendors, customers and ledger transaction lines, and the spend side: sales invoices, purchase invoices, credit notes, customer credits, card transactions, expenses, purchase orders, contracts, products, bank accounts, cards and users.

  • Books. Ledger lines become posted transactions and feed Ledgers, the statement widgets and Metrics → Accounting & ERP. When your Light company has several legal entities, each becomes its own entity in Peaky with its own ledgers and transactions, and the follow-up work runs for each of them.

  • Ledger groups. On the first sync, when an entity has no ledger groups yet, Peaky creates them from Light's account types (for example Revenue, Personnel costs, Accounts payable). Review them on Ledgers.

  • Spend metrics. Invoiced Revenue, Sales Invoice Count, Vendor Spend, Card Spend, Card Spend by Merchant Category, Expense Spend, Open Purchase Commitments, Active Contract Value and Active Contract Count.

  • Data page (when custom metrics are enabled for your company): the Light tables — Sales Invoices, Purchase Invoices, Credit Notes, Customer Credits, Card Transactions, Expenses, Purchase Orders, Contracts, Customers, Vendors, Products, Bank Accounts, Cards and Users. Rows that belong to one legal entity carry a company entity column, so any metric can be split per entity.


Rillet

Rillet is an accounting system for finance teams. Like Light, it feeds Peaky twice over: your books land in Ledgers like any other accounting source, and the rest of what Rillet knows — invoices, bills, payments, contracts, bank transactions and ARR — arrives as tables you can build metrics on, with a starter set already made.

  1. In Rillet, sign in as an administrator, go to Settings → API keys and create a key.

  2. In Peaky, find Rillet under the Accounting & ERP tab and click Connect.

  3. In Connect Rillet, choose the Environment the key belongs to — Production, or Sandbox for a key from Rillet's sandbox — paste the key into API key and click Connect.

Peaky checks the key with Rillet straight away. When the connection fails, the dialog says why:

Message

What to do

Rillet refused this API key…

Copy the key again in full, check it has not been revoked, and check the Environment: a sandbox key does not work against production, nor the other way round

Could not reach Rillet…

Rillet did not answer. Try again in a few minutes

Rillet answered in a way Peaky did not expect…

Try again; contact us if it keeps happening

Peaky only reads from Rillet; it never changes anything there.

What syncs: your subsidiaries, chart of accounts, customers, vendors and journal entries, and from the rest of Rillet: invoices and their lines, invoice payments, credit memos, contracts and their items, the ARR waterfall, bills and their lines, bill payments, vendor credits, charges, reimbursements, bank accounts, bank transactions, products and custom fields.

  • Books. Each journal entry line becomes a posted transaction and feeds Ledgers, the statement widgets and Metrics → Accounting & ERP. Every legal subsidiary becomes its own entity in Peaky, with its ledgers in that subsidiary's own currency, and the follow-up work runs for each of them. Elimination subsidiaries are left out. Custom fields on a line become dimensions.

  • Ledger groups. On the first sync, when an entity has no ledger groups yet, Peaky creates them from Rillet's account subtypes (for example Cost of goods sold, Personnel, Deferred revenue). Revenue and general operating expense accounts are split further by their Rillet account group. Review them on Ledgers.

  • Later syncs. After the first full sync, Peaky reads again every entry in the periods you have not closed in Rillet, plus every closed month in which something changed since the last sync. It checks the result against Rillet's trial balance; when the two differ, the next sync reads everything again.

  • Permissions. When your API key may not read part of Rillet — bills, say — the sync carries on without it, the integration shows what it could not read, and those tables keep the rows of the last sync that could. The key does need to read your subsidiaries.

  • Metrics. Invoiced Revenue, Invoice Count, Open Receivables, Cash Collected, Billed Spend, Open Payables, ARR, MRR, Net New ARR, Paying Customers, New Customers, Churned Customers and Card Spend.

  • Data page (when custom metrics are enabled for your company): the Rillet tables, in four groups — Revenue & Receivables, Spend & Payables, Banking and Reference Data. Every row that belongs to one subsidiary carries a subsidiary column, so any metric can be split per entity. Amounts are in each document's own currency, named in its currency column.


Odoo

Connect Odoo

  1. Find Odoo under the Accounting & ERP tab and click Connect.

  2. In Odoo, go to Settings > Users > your user, and under Account Security generate a new API Key.

  3. Back in Peaky, under Where does your Odoo run?, choose Online for Odoo.com, Odoo.sh or a server reachable from the internet. For an Odoo on your own network, choose On your own network, through a Peaky Connector, then pick the Connector and its Target instead of entering a URL — see Odoo through a Peaky Connector.

  4. Fill in the rest of the form:

Field

What to enter

Example

Odoo URL

Your Odoo address (online only)

https://mycompany.odoo.com

Database

The database name

mycompany

Username

Your Odoo login email

admin@mycompany.com

API Key

The key you just generated


  1. Click Connect. Peaky reads which Odoo apps are installed and opens the Odoo Settings so you can confirm which modules to sync — see Integration Settings. Every module Peaky supports is selected to start with.

If Peaky cannot connect, the form stays open and says what to check:

Message says

What to check

Could not reach Odoo at this URL

The Odoo URL — the address you open Odoo at, without a path after it

Odoo refused these details

The Database, Username and API Key

This user cannot read the installed apps

Connect with a user that has administrator rights in Odoo

That server address cannot be reached from Peaky

Use your server's public address — see On-premise and self-hosted servers — or connect through a Peaky Connector

The connector is not connected to Peaky

Start the connector on its machine and wait until it shows Connected on the Connectors tab

The connector refused the request

The connector's configuration needs a target of that name with profile = "odoo-readonly"

The list of installed apps is read when you connect. If you install another Odoo app later, reconnect Odoo to make it selectable.

What Odoo syncs

The Accounting module brings your chart of accounts and posted journal lines — your books. HR brings your people. Each other module adds its own metrics (the settings list them under the app names your Odoo uses, for example Employees for HR):

Module

Metrics

HR

No metrics of its own: your employees and their wages fill Headcount

CRM

Open and won leads, pipeline value, conversion rate

Sales

Orders, revenue, pending value, average order value

Subscriptions

Active, new and churned subscriptions, MRR

Purchase

Orders, open value, average value — committed spend

Manufacturing

Manufacturing orders, bills of materials, work centre hourly cost, average product cost

Inventory

Stock value and stock movements

Maintenance

Equipment count and cost, requests, labour hours

Point of Sale

Register sessions, cash balances and discrepancies, orders, revenue, tax, payments, item sales, discounts

Loyalty

Programs, rewards, outstanding balances and cards

Helpdesk

Tickets opened, closed and open, average resolution time

Odoo employees in Headcount

With the HR module selected, each sync also brings in your Odoo employees — the ones who left included, since Odoo archives them — with their department, job position, work address country, employee type, working schedule and the wages on their contracts:

  • Dates. A person starts on the start of their first contract. They end on the departure date Odoo recorded when they were archived, or else the end of their last contract. Someone still employed on a fixed-term contract ends on that contract's end date. Draft and cancelled contracts do not count.

  • Contractors. Employees of the Contractor or Freelance type count as contractors; every other type counts as an employee.

  • FTE comes from the contract's working schedule, against your company's full-time hours. Without a schedule, the person's FTE is left as it was — full time for someone new.

  • Wages. Each contract's wage comes in from the date the contract starts, so a raise you record as a new contract keeps its own date. From Odoo 19, where a raise is a new version of the employee's contract, each version's wage comes in from the version's date. Wages are converted to full time, so a part-time wage is divided by the FTE, and an hourly wage becomes a monthly one.

  • An archived employee with neither a departure date nor an ended contract is not brought in.

Each sync fills Peaky's people records from them, and the Headcount metrics are computed from those — see Headcount and Metric Reference. When custom metrics are enabled for your company, the employees and their wages are also tables on the Data page, under Odoo. Wage columns there are visible only to people with Wages → View, and no custom metric can be built on them.

Peaky reads only what Headcount shows: no private address, identification number, bank account or family details. The Odoo user you connected with needs access to the Employees app, and to Contracts on Odoo 18 and earlier, for the dates and wages to come in.

Several companies in one database. One connection covers the whole Odoo database. When it holds more than one company, each becomes its own legal entity in Peaky after the first sync: the entity you connected from stays linked to the first Odoo company, and the others appear in the sidebar entity switcher. The module choice applies to all of them.


Business Central

Business Central (Microsoft Dynamics 365) connects one company at a time.

  1. Find Business Central under the Accounting & ERP tab and click Connect.

  2. Under Where does your Business Central run?, keep Cloud and click Continue with Microsoft. For Business Central on your own servers, choose On-premises instead — see Business Central on your own servers.

  3. Sign in with Microsoft and approve access.

  4. On Choose a company, pick the company to sync. The list covers every company in your Production and Sandbox environments; each row shows its environment. When a company has no display name, Peaky shows its name or identifier instead.

  5. Click Connect company. You return to Integrations and the first sync starts.

To bring in another Business Central company, connect again from another entity's Integrations page.

What syncs: your chart of accounts, G/L entries, sales invoices, purchase invoices, customers, vendors and items.

  • G/L entries become posted transactions and feed Ledgers, the statement widgets and the Accounting & ERP tab on Metrics.

  • On the first sync, when the entity has no ledger groups yet, Peaky creates them from your chart-of-accounts hierarchy (headings and the posting accounts below them). Review them on Ledgers.

  • Built-in metrics: Revenue, COGS, Operating Expenses, G/L Movement by Category, Sales Invoiced, Sales Invoice Count and Purchases Invoiced — often broken down by account category, status or currency.

  • When custom metrics are enabled for your company, the Data page has G/L Entries, Chart of Accounts, Sales Invoices, Purchase Invoices, Customers, Vendors and Items.

Business Central on your own servers

Business Central installed on your own servers (on-premises) serves the same OData web services as Dynamics NAV, so Peaky connects it through the Dynamics NAV integration. In Connect Business Central, choose On-premises and click Continue with Dynamics NAV: the Dynamics NAV form opens, and everything below applies, with OData V4 and your Business Central server's address and server instance (such as https://bc.mycompany.com:7048/BC220). A server that is not reachable from the internet can be connected through a Peaky Connector.

This brings in your chart of accounts and general ledger entries — less than Business Central online, which also brings sales and purchase invoices, customers, vendors and items.


Dynamics NAV

Microsoft Dynamics NAV (Navision) runs on your own servers. Peaky reads it through its published OData web services. Business Central on your own servers connects the same way — see Business Central on your own servers.

  1. In NAV, publish OData web services for the chart of accounts and G/L entries.

  2. Under Users, open (or create) the user Peaky should use and generate a Web Service Access Key.

  3. In Peaky, find Dynamics NAV under the Accounting & ERP tab and click Connect.

  4. Under Where does your Dynamics NAV run?, choose Reachable from the internet, at its own address for a NAV server published to the internet. For a NAV on your own network, choose On your own network, through a Peaky Connector, then pick the Connector and its Target instead of entering a URL — see Dynamics NAV through a Peaky Connector.

  5. Fill in the rest of the form and click Connect. Peaky checks the connection before saving it and queues the first sync.

Field

What to enter

Example

NAV server URL

Your OData web-service address, starting with https://, with its port and server instance (online only)

https://nav.mycompany.com:7048/BC130

OData version

OData V4 (NAV 2017 and newer) or OData V3 (NAV 2013 R2–2016)


Company

The NAV company name

CRONUS International Ltd.

Username

A NAV user with web-service access

PEAKY

Web Service Access Key

The key from the user card


If connecting fails, the message says what to check:

The message says

Check

Could not reach NAV at this address

The NAV server URL and port, and that the OData service is running

NAV answered, but has no OData service of this version there

The server instance in the URL (such as BC130) and the OData version

NAV refused these details

The Username and Web Service Access Key

NAV has no company of this name

Use one of the company names the message lists

That server address cannot be reached from Peaky

Use your server's public address — see On-premise and self-hosted servers — or connect through a Peaky Connector

The connector is not connected to Peaky

Start the connector on its machine and wait until it shows Connected on the Connectors tab

The connector refused the request

The connector's configuration needs a target of that name with profile = "nav-readonly"

What syncs: your chart of accounts and general ledger entries. They feed Ledgers, Transactions, the statement widgets and Metrics → Accounting & ERP. On the first sync, Peaky creates ledger groups for an entity that has none yet. Built-in metrics are Revenue, COGS, Operating Expenses and G/L Movement by Category; with custom metrics enabled, the Data page has G/L Entries and Chart of Accounts.


SAP Business One

SAP Business One connects one company database at a time through your Service Layer. In Connect SAP Business One, first choose Where does your SAP Business One run?: Reachable from the internet, at its own address, or On your own network, through a Peaky Connector — see SAP Business One through a Peaky Connector. Through a connector, Peaky signs in with a username and password only. For a Service Layer reachable from the internet, choose how to sign in:

OAuth (modern, via your identity provider) — for systems with an external identity provider:

  1. Enter your Service Layer URL and Identity provider base URL.

  2. Click Connect, sign in at your identity provider and approve access.

  3. You return to Peaky and the first sync starts.

Your identity provider has to be one Peaky accepts. If Peaky refuses it, contact support.

Username & password (legacy login) — for older systems without federated sign-in:

  1. Enter your Service Layer URL, Company database, Username and Password.

  2. Click Connect. Peaky signs in to check the details before saving them, and queues the first sync.

If connecting fails, the message says what to check:

The message says

Check

Could not reach the Service Layer at this address

The Service Layer URL and port, and that the Service Layer is running

The Service Layer refused these details

The Company database, Username and Password

Signed in, but this user cannot read the chart of accounts

Give the user read access to the financials

That server address cannot be reached from Peaky

Use your server's public address — see On-premise and self-hosted servers — or connect through a Peaky Connector

The connector is not connected to Peaky

Start the connector on its machine and wait until it shows Connected on the Connectors tab

The connector refused the request

The connector's configuration needs a target of that name with profile = "sap-b1-readonly"

With OAuth, Peaky renews access through your identity provider in the background; with a username and password it signs in to the Service Layer on every sync.

What syncs: chart of accounts, journal entries, sales and purchase orders and invoices, business partners, items, opportunities, leads and employees.

  • Journal lines become posted transactions and feed Ledgers, the statement widgets and Metrics → Accounting & ERP. Peaky creates ledger groups on the first sync for an entity that has none.

  • Built-in metrics on the SAP Business One tab: Revenue, COGS, Operating Expenses, G/L Movement by Category, Sales Invoiced, Sales Order Value, Purchases Invoiced, Purchase Order Value, Pipeline Value, Opportunities, Leads and Headcount — often broken down by account, status, currency or cost centre.

  • With custom metrics enabled, each of the synced record types is a table on the Data page.


SAP S/4HANA

SAP S/4HANA Cloud runs on your own tenant, so Peaky needs its addresses before you sign in.

  1. Find SAP S/4HANA under the Accounting & ERP tab and click Connect.

  2. In Connect SAP S/4HANA, enter your OData API host and OAuth base URL (from SAP BTP or IAS).

  3. Click Connect, sign in and approve access.

  4. You return to Peaky and the first sync starts. Peaky renews access in the background.

What syncs: the same data as SAP Business One — G/L accounts, journal lines, sales and purchase orders and invoices, business partners, products, opportunities, leads and workforce — with the same built-in metrics and Data page tables.

Required and optional data. Peaky needs your tenant's G/L account and journal entry APIs; without them the sync fails. The other APIs are optional: if one is not enabled for your connection, Peaky skips that data and still imports your books. Data from an earlier sync stays in place, and the next sync picks the data up once the API is enabled.