Connects to your accounting system, both ways.
Atlas is not trying to be your ledger. It makes sure the ledger gets clean, coded, approved invoices without anyone typing them twice, and knows what has been paid. Eleven systems connect directly, with no middleware. Four are proven against live ledgers today; the other seven are proven against your own ledger during onboarding.
Eleven ledgers, swept every 15 minutes — not a nightly file.
QuickBooks Online, Xero, Business Central and Sage Accounting are proven live. NetSuite, Oracle Fusion, SAP S/4HANA, Sage Intacct, Sage 300, Sage X3 and BILL are proven against your ledger during onboarding. Accounts and suppliers read IN, approved invoices post OUT, payment status reads BACK.
- InChart of accounts, cost-centre dimensions and the supplier master, so ten years of vendors do not start as an empty list
- OutCoded bills to all eleven, purchase orders to eight, credit notes to ten. GRNI and rebate accrual journals to six, each off until switched on
- BackPayment status only. Atlas never pushes a payment — marking something paid that nobody paid cannot be walked back
- Never twiceEach bill carries an idempotency key written before the call. A connection that drops mid-post resumes instead of creating a second bill against a real supplier
No two ledgers can do the same things, and we say which.
A connector is only as capable as the system behind it. One package has no purchase-order document, another accepts no journal entry, several cannot close an open order. Atlas lists what YOUR ledger cannot do, and why, the moment you connect — not weeks later when a job fails.
- WhyThe alternative is a feature list that is true of the best connector and quietly false for yours
- ExampleSage 50 cannot be connected at all: no network interface, only a desktop toolkit that must run on the same computer as the data file. Said on the page rather than left as an assumption
- ExampleWhere a ledger will not let Atlas create a supplier safely, Atlas asks you to create and map it. Better than a half-formed record that cannot be invoiced
- NeverA speculative write into your accounts. An honest gap is better than a confident wrong posting
What reaches the ledger has already been matched.
The value of the integration is not the file format. It is that everything in the file has been through approval, receipt and a three-way match first. Peppol purchase orders are built too; sending on the Peppol network goes through an accredited access point, contracted before first use.
- SimpleInvoices arrive against a specific order, not as email attachments — including Peppol UBL invoices and credit notes, their arithmetic checked
- ThenThe match runs automatically; only exceptions need a person
- ThenApprove for payment and record the payment with its reference
- ComplexTax treatment is checked against what the order carried, so the ledger entry is right the first time
Not on that list? Then it pulls a feed.
The only drawing on the site. This is the one question a diagram answers better than a screen: what crosses the boundary, in what shape, and who controls the timing.
- OutPurchase orders, invoices, suppliers, contracts and ledger entries
- HowJSON or CSV over HTTPS, pulled by your finance system on its own schedule, incremental by date
- KeyOne API key, issued and rotated by your administrator
- Read-onlyThis route cannot change anything in Atlas, so an integration fault cannot corrupt a procurement record
On the four proven ledgers, set it up in an afternoon.
No integration project. Cloud ledgers: a sign-in and a mapping. Self-hosted — Sage 300, Sage X3, SAP S/4HANA, Oracle Fusion — a form with your address and an integration account. The seven not yet proven live are proven on your ledger at onboarding. Anything else: a key, an endpoint, a schedule.
- SimpleConnect the accounting system by signing in to it — the chart of accounts and cost-centre dimensions come back on their own
- ThenConfirm the mapping. A match Atlas made itself never counts as one a person confirmed, and a routine sync never downgrades your confirmation
- ThenPosting stays OFF until you turn it on. An unmapped push lands everything in a suspense account, which is worse than no integration because it looks like it worked
- ComplexFor a ledger with no connector: issue the API key, point their scheduled job at the feed, and rotate the key when somebody leaves
Commitment visible before the invoice, not after.
The gap between a purchase being approved and appearing in the ledger is where budget overruns are born.
- SeesCommitment against budget as orders are raised, not when billed
- SeesCycle time from invoice to payment, measured rather than estimated
- DoesCloses the period on figures that were already reconciled by construction
- ProofEvery ledger entry traces back through the invoice, the receipt, the order and the requisition
