ERP connections
Your ERP, read down in full and written back with care.
Atlas works with SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365 and Rillet, alongside your bank feeds and AR mailboxes. Connections are configured when your instance is deployed. Reads are complete and kept verbatim; writes are off until you turn them on.
- 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
What connects
The systems receivables actually run on.
- SAP S/4HANA
- Customers, open items, invoices, incoming payments and credit memos.
- Oracle NetSuite
- Customers, invoices, payments, credit memos and applications.
- Microsoft Dynamics 365
- Customers, invoices, payments and settlements.
- Rillet
- Listed as an ERP Atlas works with. Details are set up with each instance.
- Bank feeds
- Deposits and returns, for matching payments to invoices.
- AR mailboxes
- Remittances, disputes and replies from the inbox your team already uses.
The outbox
Every write is claimed, checked, made and confirmed.
Write-back is off by default and switched on at deployment, one kind of change at a time.
- 01
Claim
One worker takes the change, so two can never write the same thing at once.
- 02
Read before write
Atlas reads the target record in the ERP and stops if it changed since the decision was made.
- 03
Write
The change is sent with an idempotency key, so a retry never posts twice.
- 04
Confirm
Atlas reads the record back. Only then does the change appear in Atlas.
Details that hold up
Built for the edge cases that break reconciliations.
Sync modes
Read-only, read with write-back, or a schedule that fits your close. Ferrata sets the mode at deployment and Atlas shows it to you.
Hybrid keys
Every record keeps its ERP identity beside Atlas's own, and every past reference is kept, so a rename or re-key never breaks history.
Exact money
Amounts are stored as exact decimals with an ISO 4217 currency. Balances are never added across currencies, on a screen or in a message.
Frozen FX
A payment applied in another currency carries its rate, recorded once and never recalculated.
FAQ
ERP connections, run end to end.
Which ERPs does Atlas work with?
Atlas works with SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365 and Rillet, along with bank feeds and AR mailboxes. Each connection is configured when your Atlas instance is deployed.
Can Atlas write to our ERP, and can we stop it?
Atlas writes back only when write-back is switched on, which happens at deployment and can be set one kind of change at a time. Until then Atlas reads only. Every write goes through an outbox that reads the record first, writes once and confirms the result.
What happens if a customer is renamed or merged in the ERP?
Atlas keeps each record's ERP identity next to its own id, and keeps every past reference. A rename, merge or re-key in the ERP updates the record without breaking its history of invoices, payments and contacts.
How does Atlas handle multiple currencies?
Every amount in Atlas carries its own ISO 4217 currency and is stored as an exact decimal. Atlas never adds balances across currencies, and a payment applied in another currency keeps the exchange rate recorded when it was applied.
Does Atlas need our ERP data exported first?
No. Atlas reads directly from the ERP through the connection set up at deployment, and keeps every record it receives verbatim, so nothing has to be exported, cleaned or uploaded by your team.
Related in Atlas
- How it layers on your ERPYour ERP stays the system of record. Atlas reads it, models it and works on top.View
- IntegrationsERPs, bank feeds, mailboxes, channels, payment links, CRM and reporting.View
- Cash applicationPayments matched to the right invoices and applied, from every source.View
- Deployment optionsHosted by Ferrata, in your VPC, on-prem or air-gapped. The same Atlas in each.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.