Skip to main content
Status: Built in. The current list for your company is in Settings → Integrations.

What it syncs

Invoices, payments and credit memos are exported to Business Central.

How to connect

Connect with OAuth 2 from Settings → Integrations.

Who owns which data

BrandGate stays the invoice sender. Partial credit notes need to be handled by a person. The general rules are in the integration model.

Limits and known differences

Ask us if your case needs something that is not listed here: brandgate.dev/contact. Building it yourself? Follow Build an ERP integration.

Connect it through the API

Building the connection yourself? These are the typical field matches. The steps are the same for every system: Build an ERP integration. Use the BC number, not the GUID id, as external_id. BrandGate treats external_id as plain text that you choose and never reads it as a BC id, so the GUID would work too, but the number is what people see and it survives a company copy. The If-Match ETag that BC requires when you update its records is between you and BC: BrandGate has no ETag. Send source_updated_at (BC’s lastModifiedDateTime) so a late retry cannot overwrite newer data.
Field names are the ones your ERP usually exposes; check them against your version. Amounts go to BrandGate as decimal strings with at most two decimals ("299.50"), so round before you send: ERPs that hold prices as floating-point numbers need Math.round(x * 100) / 100.

What the API cannot hold yet

  • Price validity dates (startingDate, endingDate) and per-line currency.
  • Blocked items and payment terms given as an id (convert to days).