The platform
A layer on top of your ERP, not a replacement for it.
SAP, NetSuite or Dynamics keeps its place as the system of record. Atlas reads it into a layer of its own, models your receivables in one shape, and lets agents work there. Anything that changes the books goes to the ERP first, then comes back down.
Four layers
From the ERP's own records to agents at work.
Each layer has one job, and none of them asks you to move off the systems you run today.
- 01
Your ERP
Customers, invoices, payments and credit memos stay where they are. Atlas reads them through a connection set up when your instance is deployed.
- 02
The raw layer
Every record the ERP sends is kept verbatim and append-only. A new version is stored only when the content actually changes, so you can see what the ERP said and when.
- 03
One canonical model
Raw records are mapped into one model: parties with customer and vendor roles, invoices, payments, applications and credit memos, with exact amounts and currencies.
- 04
Agents on top
Follow-up, collections, promises, disputes, credit and charge-off work on the canonical model, so every agent reads the same balance and the same history.
Write-backs
Changes go to the ERP first, then come back down.
When Atlas applies a payment, issues a credit memo or puts an account on hold, it writes to your ERP and then reads the result back. The raw layer is never written first, so Atlas can never show a state your books do not hold.
- Read before write
- Atlas reads the target record before it changes it, and stops if it moved since.
- Confirmed
- A write counts only once the ERP's own record shows it.
- Idempotent
- A retried write never posts twice.
- Customers
- Invoices
- Payments
- Credit memos
- Journal entries
- Customersv3
- Invoicesv12
- Paymentsv7
- Credit memosv2
- Journal entriesv5
- Parties
- Invoices
- Payments
- Credit memos
- Applications
- Claimed
- Read before write
- Posted
- Confirmed
Why a layer
What changes, and what stays exactly where it is.
| Stays in your ERP | Added by Atlas | |
|---|---|---|
| Records | The ledger, customers, invoices, payments and terms | A verbatim history of every record and one canonical model over it |
| Decisions | Your posting rules and approval structure | Agents that follow up, rate credit, match cash and resolve disputes |
| Changes | Every change to the books | Write-backs through an outbox, read back to confirm |
| Reporting | Your financial statements | Activity, ratings and the full record of every touch |
One foundation
Every Ferrata product reads the same records.
Atlas sits on the same foundation as the rest of Ferrata's products. Adding one later switches on its agents; the data is already there.
One tenant per company
Your company has one foundation, shared by every Ferrata product you use, and no other company's data is in it.
No copies per product
There is no second invoice table or second customer list. A product adds its own agents and rules, never its own version of your records.
History you can trust
Renames, merges and re-keys in the ERP never break the history, because each record keeps its ERP identity and every past reference.
FAQ
How it layers on your ERP, run end to end.
Does Atlas replace our ERP?
No. Atlas layers on top of SAP, NetSuite or Dynamics, which stays the system of record. Atlas reads your customers, invoices, payments and credit memos, works on them with agents, and writes any change back to the ERP first.
How does Atlas keep its data in step with the ERP?
Atlas keeps every record the ERP sends in a raw layer, verbatim and append-only, storing a new version only when the content changes. It maps those records into one canonical model that every agent reads, so balances and history match what the ERP holds.
What happens when an Atlas agent needs to change something in the books?
The change goes through an outbox to the ERP. Atlas claims the work, reads the target record before writing, makes the change, and confirms it by reading the ERP's record back. Retries never post twice, and Atlas shows the change only once the ERP holds it.
Can Atlas run on more than one ERP?
Yes. Each record keeps the system and company it came from, and amounts carry their own currency. Atlas reads every connected system into the same canonical model and never adds balances across currencies.
If we add another Ferrata product later, does the data move?
No. Atlas runs on the same foundation as every Ferrata product. A second product switches on its own agents and rules over the records already there, with no migration and no second copy of your customers or invoices.
Related in Atlas
- ERP connectionsSAP, NetSuite, Dynamics and Rillet, read down and written back with care.View
- Deployment optionsHosted by Ferrata, in your VPC, on-prem or air-gapped. The same Atlas in each.View
- Modeling your operationsYour receivables operation, modeled as agents, rules and context you can see.View
- IntegrationsERPs, bank feeds, mailboxes, channels, payment links, CRM and reporting.View
- Accounts receivableThe whole receivables lifecycle, from credit application to recovery, worked by agents.View
See the platform work on your own receivables.
Thirty minutes on your own aging report. You leave with a view of how Atlas would work it, and an honest answer if the sequencing is wrong and you should fix something else first.
Your credit policy, terms, tone and escalation rules are your advantage, and they stay yours. Atlas is configured to the way you run receivables. You are not handing over a playbook or fitting into a template.