Developers

The canonical data model

The shared objects every ERP connects through, which is why changing ERP is one adapter.

A product tour of InvoiceIQ by Analytos: Accounts Payable and Accounts Receivable on one platform.

The objects

ObjectWhat it isAPAR
PartyWho the document is from or forVendorCustomer
OrderThe commitment, with its lines and what remains to billPurchase orderSales order
MovementThe goods actually moving, with its linesItem receiptItem fulfilment
DocumentThe incoming paperVendor invoiceBill of lading
ResultWhat is written back, with its linesVendor billCustomer invoice
CodingThe account and dimensions on each result lineExpense GL · class · departmentRevenue GL · class · tax, from the order line
ChargesTax, freight and other non-goods linesPlaced by rulePlaced by rule

What an adapter implements

  • Fetch the order, with its lines and remaining quantities.
  • Fetch what moved against it, with its lines and what has already been consumed.
  • Translate the incoming document in, and the result out.
  • Name the dimensions this ERP carries.
  • Translate the ERP’s status codes — exactly once, here. No engine code ever sees them.

The NetSuite adapter is the contract, Stockly implements the posting path, QuickBooks is a stub. A CDM Objects page shows each field mapping.

Why it matters

The matching kernel sees only roles — commitment, fulfilment, output — so the same tested code decides both buying and selling.

The API

Every screen runs on the same REST API, so upload, inbox, rules, matching and posting are all callable.

Want to see it rather than read about it?

A walkthrough takes an hour and starts with your own documents.