Exact Online UK – Gotchas

Journal-entry attachments are not exposed by Exact Online's Journals or general journal-entry endpoints. Use pass-through against /api/v1/{division}/documents/DocumentAttachments for native document attachment records; link the returned document ID to the journal entry.

Creating a bill payment records the bank transaction but does not automatically reconcile it with the linked bill — the bill's status will not change to paid until the payment is matched manually in Exact Online. A valid bank journal (Type=12) must be supplied via the bank_journal_code connection setting or pass_through[journal_code] per request; without one the API returns 'Invalid journal'.

Exact Online assigns invoice status automatically (open by default) and ignores the status field on create — invoices are finalized/processed in Exact Online, not via the API. Set VAT via line_items[].tax_rate.code; Exact derives the percentage from the code, so line_items[].tax_rate.rate is ignored on create.

Limit parameter for pagination is not supported for this resource.

A validation refusal — an unbalanced entry, an unknown or inactive reference (ledger account, journal, VAT code, currency), or a missing required field — returns 422 with the specific reason named. Any other 500 is a genuine unexpected downstream failure, not a refusal the request itself caused.

Use code as journal_symbol when creating a journal entry. allow_vat applies to general journals. x-apideck-company-id selects the division. This list has no server-side total count, so pagination metadata never includes a count.

type: bank requires iban — Exact needs a bank account reference to create a bank journal. type: payment_service requires a payment service provider reference that has no equivalent in this unified field set — creating a journal with that type will be rejected by Exact. Use pass_through to supply the required vendor field if you need payment_service, or use sales, sales_credit_note, purchase, purchase_credit_note, cash or general instead. type: other has no Exact equivalent and will be rejected — other is a read-side fallback for values Exact might introduce in the future, not a valid input.

Creating a payment records the bank transaction but does not automatically reconcile it with the linked invoice — the invoice status will not change to paid until the payment is matched manually in Exact Online. A valid bank journal (Type=12) must be supplied via the bank_journal_code connection setting or pass_through[journal_code] per request; without one the API returns 'Invalid journal'.