Systems
the tools you keep or move in
Move your payroll, CRM, sales tool or ERP in, or keep it running beside the books. A rule turns a record into a draft, and nothing leaves outside what you signed: the mandate or the payment itself.
Beside the books
A record is not a transaction
a rule turns it into a draft for you
- Records sync once a day and stay what that system says. They never enter your reports, budgets, VAT or tax.
- A payment from a rule goes to the account in your address book, never to bank details from the system.
What connects
The systems you keep
and where each record lands
Connected systems · example
- MailForwarded bills, or a Gmail inbox read once a dayBills
- Payroll and HRPeople and their pay by its API, paid under your mandateBeside the books
- ERPNetSuite, SAP, Odoo, Business Central, by their own sign-inBeside the books
- AccountingQuickBooks Online and Xero: contacts, invoices, billsMoved in, or beside
- CRM and salesCustomers, deals and orders, matched by emailContact card
- Sales platformsStripe, Shopify, PayPal, Etsy, Gumroad, app storesIncome
- AI providersAn admin key: what your agents spendSpend
- Any other systemYour script sends rows with a key that ends by itselfIts own accounts
- Banks, cards and walletsconnect as rails, on their own pageRails →
- Keeping a system beside the books comes with Pro and above. Moving one in takes no slot.
- The owner, whoever connected it and the admins see a connected system, and can open it to members, viewers or your accountant. Nobody else sees it exists.
Connecting
By its own sign-in
an agent proposes the map, you approve it
- Invoice 1038$4,200 · matched by emailNorthwind
- Invoice 1043$1,800 · matched by emailBrightpress
- Invoice 1044$650 · no contact with that emailNot linked
An API key, OAuth with your app, NetSuite tokens or an integration user. The agent reads with small requests, shows real rows, and nothing syncs before you approve. It never sees the key.
Both ways
What it reads, what goes back
and what only a rule can do
- ReadsRecords once a day, with small requests
- Asks firstA read sent as POST shows you the request: Allow this request, or Decline
- Sends backEntries from your books into QuickBooks, Xero or NetSuite, each under your policy, and six signed money events
- Acts in OrlaA rule drafts an invoice or a payment for you
Secrets, dates of birth, national ids and bank details are left out even when a system has them. How events are signed and retried →
Questions
About systems
the short answers
Which systems can Orla read?
Payroll and HR tools, CRMs, sales tools and ERPs with an API that answers JSON: by a key, OAuth with your app, NetSuite tokens, or an integration user for SAP Business One and Odoo. One inside your own network connects through a runner next to it.
Can Orla change anything in my systems?
It reads. A read sent as POST shows you the request first, and anything that would change data is refused. What goes into QuickBooks, Xero or NetSuite are entries from your books, each under your policy.
Do a system's records go into my books?
Not while you keep the system. Move it in, and its contacts, open invoices, bills and transactions become yours in Orla.
Which plans can connect a system?
Keeping one beside the books: Pro and above. Moving one in: every paid plan, Solo included.
Read next
- In the cabinetConnections Every connection, says what it reads and writes
- On the siteOrla for Slack Answered in the channel it was asked in
- On the siteWebhooks Your systems hear about your money
- On the siteOrla API Payment requests, prepaid balances, webhooks
- On the sitePayroll cash Enough on the right account by payday
Bring the system you keep
and we map it with you
On a thirty minute call we connect a system and approve its first map together.