Skip to content

Attaching to your existing ERP

We attach to the ERP you already run, such as SAP Business One, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Epicor, Infor, Sage, Acumatica, SYSPRO, QuickBooks Enterprise or whatever you run. This page lists the ways we connect, in the order we prefer them, and the rules for reading from the ERP and writing back to it.

Four ways to attach, in order of preference

Section titled “Four ways to attach, in order of preference”
Order Way of attaching Used for What to know
1 A supported API Reading and writing The ERP applies its own validation, numbering and posting to every call. The Systems and Data Audit records which screen-level checks the interface does not run. Not every ERP or version has one, and some cover only part of the system.
2 Database views or a read replica Reading only Good for history and bulk data. Never used to write. Not available when the ERP vendor hosts the database and does not open it.
3 File and EDI exchange Reading and writing in batches Uses the ERP’s own import and export jobs. It runs on a schedule, so it is slower, and errors come back in a log that has to be read.
4 Screen automation Writing, as a last resort Software fills in the ERP’s screens the way a person does. It breaks when a screen changes, so it needs the most watching.

In plain words:

  • A supported API is the interface your ERP vendor documents and supports for other software. It is our first choice because the ERP applies its own validation, numbering and posting to everything that comes through it.
  • Database views or a read replica let us read without slowing the live system. A view is a saved, read-only query on the ERP database. A read replica is a copy of the database that is kept in step with the live one. Order history, price lists and open purchase orders are read this way.
  • File and EDI exchange means files left where the ERP’s import job picks them up, export files the ERP writes on a schedule and EDI documents such as purchase orders, acknowledgments, ship notices and invoices.
  • Screen automation is for the transaction that has no API and no import. We use it only when the first three are not available, for one named transaction at a time, and we replace it when a better interface appears.

One ERP can use more than one of these. A sensible pairing is bulk reads from a read replica and writes through the API.

The choice is made from the Systems and Data Audit, the Discovery Sprint deliverable that records, for every system, how to get data in and out. Your IT manager or ERP administrator agrees to it before anything is built.

  • Reading comes first and needs only read access. The Discovery Sprint runs on read access alone.
  • Reads do not slow the live ERP. Bulk reads go to a replica, a view or an export, at times agreed with your IT team, so the people keying orders never wait on us.
  • We read what a workflow needs. Order entry needs customers, items, prices and credit status. It does not need payroll.
  • Live values are read live. A copy is fine for last year’s order history. A decision that depends on a current value, such as a credit check or stock on hand, reads that value from the ERP at the moment of the decision.
  • Copies show their age. Where a screen shows data copied from the ERP, it shows when the copy was taken.

Writing to the ERP is a bigger step than reading from it, and we treat it as one.

  • Writes go only through an interface the ERP supports: its API, its import jobs, its EDI exchange or, as a last resort, its own screens. We never write to the ERP’s database tables directly. A direct write skips the ERP’s validation, numbering and posting, and can leave records the ERP itself would never have created.
  • Each write-back is a named transaction. “Create a sales order” is a write-back. So is “update the promise date on a purchase order line”. For each workflow, the list of write-backs is written down and agreed with the workflow owner and your IT team. Nothing outside the list is written.
  • Write access is requested one workflow at a time, when that workflow is ready to write back. It covers only the write-backs on that workflow’s list. It goes through your change control and is tried against a test copy of the ERP first. See Releases and change control.
  • Every write is made under a named account. That is a person’s own account or an agent’s own service account, never a shared login. When a person approved what an agent prepared, the operations layer records who approved it. Access and credentials covers how accounts are set up.

Our engineers build every write-back to the same six steps.

  1. Check before sending. The operations layer checks the transaction against your rules: required fields, a valid customer and item, the price list, the credit limit. If an agent prepared it, the agent’s limits are checked too.
  2. Let the ERP validate. The transaction goes through the supported interface, and the ERP applies its own validation, numbering and posting. If the ERP rejects it, nothing is forced through. The rejection goes to a person, with the ERP’s own error message.
  3. Read back and compare. After the write, the operations layer reads the transaction back from the ERP and compares it with what was sent: the document number, the lines, the quantities, the prices, the total. A difference stops the case and sends it to a person.
  4. Record it. The ERP’s document number, who or what made the write, the time and the result are stored with the source document.
  5. Never write twice. Our engineers give each write-back a unique reference, so a retry after a timeout cannot create the same sales order a second time.
  6. Reconcile. On a schedule, the operations layer compares what it believes it wrote with what the ERP holds, and lists any difference for a person to look at.
  • Write to the ERP’s database tables.
  • Change your ERP’s configuration. A new field, a new import format or a new view goes through your change control, and your ERP administrator or ERP partner makes the change.
  • Keep a second master copy of customers, items or prices.
  • Claim an official integration with any ERP.