How-to · 23 Oct
How-to · 3 min read
How to connect ERP and CRM data into one business model
Finance and operations teams often have the customer in the CRM, the order in the ERP and the payment promise sitting in someone's inbox. Each system is correct about its own slice, so nobody thinks of it as broken. But the moment you ask a simple cross-system question, like which open invoices belong to a customer who promised to pay last week, someone has to open three tabs and a spreadsheet. And if you hand that same mess to an AI agent, it has nothing solid to stand on.
- Published
- 17 Nov 2026
- Delivery
- No. 12
- Topic
- AI and agents
- Evidence
- 10 claims quoted from ferratalabs.ai
01
Why it's hard
The usual fix is a sync job or an export that copies records from one system to another. Copies drift: a customer gets renamed in one place, a payment posts late in another, and soon there are three versions of the same account. Point-to-point integrations also only move fields, they do not carry the relationships, such as which contract an invoice came from or which caller is also the payer. The rules that tie it together, like how you price or when you escalate, usually live in people's heads and never get written anywhere a system can read.
This part describes the usual way. It makes no claims about Ferrata Labs, so nothing is quoted here.
02
How Ferrata Labs does it
Ferrata Labs builds what it calls the Ontology, a single model of your business that sits on top of the systems you already run. It reads your ERP (SAP, NetSuite, Dynamics 365 or Rillet) plus the CRM, bank, email and phone, and ties each record to the ones it belongs with. Your ERP stays the system of record, and nothing is copied per product, so the records do not drift apart. Agents for collections, payables, quoting or the close then read from that one model instead of guessing across disconnected tools.
Your ERP stays the system of record; the platform reads it, keeps what it reads exactly as it arrived, and writes back only what you allow.Quoted from ferratalabs.ai
A customer is one customer, whether they appear as a buyer, a payer or a caller. An invoice knows its order, its contract and its payments.Quoted from ferratalabs.ai
Every product and every agent reads the same records. Nothing is copied per product, so nothing drifts.Quoted from ferratalabs.ai
03
Step by step
- 1Connect your ERP and the tools around it; records are read on a schedule you set.
- 2Let the Ontology relate customers, orders, invoices, payments, vendors and periods to each other.
- 3Write down the rules from your team's heads (pricing, approvals, escalation) as instructions agents follow.
- 4Turn on one product's agents, which start at the reviewed level with a person releasing every step.
- 5Check any balance by opening it to the records and math behind it.
04
Tips
Start with the one cross-system question that costs you the most time every week, for example matching bills to orders and receipts. A narrow first use case shows quickly whether the joined model is right, and the next product reuses the same data.
Pick the function that hurts.Quoted from ferratalabs.ai
Do not skip writing down the informal rules. If your approval thresholds or pricing floors exist only as habit, an agent cannot follow them, and neither can a new hire. Treat this step as part of the integration, not an extra.
How you price, approve and escalate, written down once as the instructions your agents follow.Quoted from ferratalabs.ai
Ask for traceability before you trust any number. A joined view is only useful if each figure can be followed back to the record it came from, so finance can defend it in an audit. A model that hides where its numbers come from just moves the spreadsheet problem one layer up.
Balances are computed, never stored, and each one opens to the records and the math behind it.Quoted from ferratalabs.ai
If your data cannot leave your network, raise that on the first call. The same platform can run hosted, in your own cloud or data center, or fully air-gapped, so the choice does not lock you out later.
The same platform either way, so moving later is a change of address, not a rebuild.Quoted from ferratalabs.ai
05
Questions
Does this replace our ERP or CRM?
No. The ERP stays the system of record, and the platform only writes back what you allow.
Your systems stay where they are and stay the record.Quoted from ferratalabs.ai
Which ERPs can it read?
SAP, NetSuite, Dynamics 365 and Rillet are listed as systems of record, alongside CRM, bank, email, phone and documents.
SAP, NetSuite, Dynamics 365, RilletQuoted from ferratalabs.ai
Is our data used to train for other companies?
No. Each company gets its own database behind its own login.
Nothing learned from your data is used for anyone else.Quoted from ferratalabs.ai