Developers
The canonical data model
The shared objects every ERP connects through, which is why changing ERP is one adapter.
The objects
| Object | What it is | AP | AR |
|---|---|---|---|
| Party | Who the document is from or for | Vendor | Customer |
| Order | The commitment, with its lines and what remains to bill | Purchase order | Sales order |
| Movement | The goods actually moving, with its lines | Item receipt | Item fulfilment |
| Document | The incoming paper | Vendor invoice | Bill of lading |
| Result | What is written back, with its lines | Vendor bill | Customer invoice |
| Coding | The account and dimensions on each result line | Expense GL · class · department | Revenue GL · class · tax, from the order line |
| Charges | Tax, freight and other non-goods lines | Placed by rule | Placed 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.