Blog
Order entry with ERP integration, without custom code
In short
Order entry without custom code means: orders are read and checked against your master data before the ERP, then reach the ERP by a route it already knows: REST API or an export as CSV, XLS, XML or JSON. No connector per ERP, no template per customer.
For the overview of types, process and automation, see our guide to order entry.
What does ERP integration without custom code mean?
The work happens before the ERP. Incoming orders are read, checked against your master data and handed over as a finished record. They reach the ERP by a route it already knows: a file import or an interface. You need no connector per ERP and no programming project per customer.
Five routes into the ERP
| Format | Typical route into the ERP | When it makes sense |
|---|---|---|
| REST API (JSON) | Middleware, an integration platform or the ERP itself fetches finished records | When data should flow without an intermediate step, or an integration layer already exists |
| CSV | The ERP's standard import | The simplest start: map the columns once, then every order arrives the same way |
| XLS / XLSX | The ERP's Excel import | When someone should see the data once more before it is imported |
| XML | Import interfaces that expect structured documents | When the ERP already reads documents as XML |
| JSON (file) | A script or integration platform reads the export | When further processing happens outside the ERP |
What happens before the export
- Orders are read without templates, from email text, PDF or scan, in any customer layout and with no set-up per customer.
- Customer, item numbers and terms are checked against the master data in your ERP or CRM.
- Fields that do not match with confidence go to you for review instead of landing in the ERP unchecked.
- Only checked records are exported, in the format your ERP reads.
SAP, Business Central or an industry ERP?
What matters is which imports your ERP offers, not its name. Whether SAP, Microsoft Dynamics 365 Business Central or an industry-specific ERP, there is usually a file import or an API to hand over to. Where a deeper integration is wanted, our ERP integration partners build it.
In the largest production system, around 1.5 million documents a year across eight country markets run this way, with about 80% less processing time.
Frequently asked questions
Do I need a connector for my ERP?
No. To start, a file import for CSV, XLS or XML is enough, and most ERP systems have one. The REST API is the route when orders should flow into the ERP without an intermediate step.
Who sets up the import in the ERP?
You or your ERP service provider, once: columns or fields are mapped. After that, every order arrives in the same format, whatever it looked like at the customer's end.
What happens to orders the AI is unsure about?
They are not exported but put in front of you for review. Only after approval do they go to the ERP.
Does the ERP need to be changed or replaced?
No. smartextract works before the ERP and hands over finished records. Nothing changes in the ERP itself apart from the import you set up.
Where can I find the technical documentation?
At docs.smartextract.ai, with the export formats and the API reference.
Send us a document and watch the extraction.
30 minutes, your own documents, no preparation needed.