Exact Online Integration: Data Mapping and Troubleshooting Reference
A field-level reference for how PSOhub data maps to Exact Online, plus common errors and how to resolve them
Published: 1 June 2026
Audience
-
Admin
Objective
This reference covers how PSOhub data maps to Exact Online for accounts, contacts, and invoices, and provides a complete list of common integration errors with their causes and resolutions.
Data Mapping
When an invoice is pushed from PSOhub to Exact Online, PSOhub sends account, contact, and invoice data. The tables below show how fields in PSOhub correspond to fields in Exact Online.
Accounts
Before creating a new account in Exact Online, PSOhub checks whether an account with the same name already exists. If a match is found, the existing account is used, and its identifier is stored. If no match is found, a new account is created.
| Field in Exact Online | Field in PSOhub |
|---|---|
| Name | Company Name |
| Address Line | Address |
| City | City |
| Status | C (Customer — set by default) |
Contacts
Before creating a contact in Exact Online, PSOhub checks whether a contact already exists for the associated account by searching on email address. The following logic applies:
- If a matching contact is found and is already linked to the account, that contact is used.
- If a matching contact is found but is not linked to the account, a new contact is created and linked to the account.
- If no matching contact is found, a new contact is created and linked to the account.
| Field in Exact Online | Field in PSOhub |
|---|---|
| First name | First name |
| Last name | Last name |
| Account | Associated Company |
Invoices
An invoice in Exact Online is made up of two parts: the invoice header and the invoice sales lines.
Invoice Header
| Field in Exact Online | Field in PSOhub |
|---|---|
| Description | Invoice name |
| Payment reference | Project Number – Project Name |
| Your Reference | Invoice Reference |
| Invoice to | Account |
| Type | 8020 (standard) or 8021 (credit note) |
| Invoice to contact | Contact email |
| Journal | Journal code (from integration settings) |
| Ordered by | Account |
| From | Date from |
| To | Date until |
Invoice Sales Lines
By default, PSOhub uses the item and tax code configured in the integration settings for all invoice lines. If a specific item or tax code is required for an individual line, these can be set on the contract line under Accounting details.
| Field in Exact Online | Field in PSOhub |
|---|---|
| Item | Default item (from settings) or item set on the contract line |
| Description | Line number – Invoice line name |
| Note | Line description |
| Quantity | 1 |
| VAT code | Default tax code or code set in the tax category |
| Net price | Amount to be invoiced |
📌 Note: Tax calculations are performed by Exact Online based on the VAT codes provided by PSOhub.
Troubleshooting
The table below lists the most common Exact Online integration errors, their causes, and how to resolve them.
| Error | Cause | Solution |
|---|---|---|
| Error encountered in converting the value from request payload for property 'OrderedBy' to type 'Guid' | The contact or company ID stored in PSOhub is no longer valid in Exact Online. This can happen if the contact or company was removed or merged in Exact Online. | Check whether the contact or company still exists in Exact Online. Contact PSOhub support to reset the ID to 0 in PSOhub, then try again. |
| Error encountered in converting the value from request payload for property 'Item' to type 'Guid' | An article is mapped to a contract line that does not exist in Exact Online, or the item code is not recognized. | Verify that the article exists in Exact Online and that the item code in PSOhub matches exactly. |
| Invalid invoice for (Type) | The contact or company in Exact Online is marked as a supplier, which is not supported for invoicing. This can also occur if the same email address appears twice. | Make sure the Exact Online contact is not set as a supplier. Check for duplicate email addresses. If the person needs to be both a supplier and an invoice contact, contact PSOhub support to manually map the correct contact. |
| Missing payment condition | No default payment condition is set in Exact Online. | Set a default payment condition in Exact Online, or apply a payment condition directly on the account record that was created during the test connection. |
| Service Unavailable | Exact Online is offline or experiencing downtime. | Check https://status.exact.com for service status, or contact PSOhub support. |
| User is not active | The Exact Online user who authorized the PSOhub connection has been deactivated. | Reactivate the user in Exact Online, or have an active user with the correct permissions reconnect via Settings > Integrations in PSOhub. |
| User division is not within division scope | The user attempting to connect does not belong to the Exact Online division they are trying to connect. | Make sure the user performing the connection belongs to the correct division in Exact Online. Each user has one primary division; if you need to connect multiple Exact Online administrations, a separate Exact Online user is required for each. |