Integrations
Your owed invoices, in your books, each one once. Procurement's matched and approved invoices leave as bills your accounting package imports, with your own account and tax codes on every line.
Bill exportSample data
Owed, once, your codes, your books.
Four rules hold for every bill, whether it leaves as a file today or through a live connection later.
- Owed
- An invoice is a bill once Procurement matches it to its order and receipt, or an approver accepts its exception. Nothing else leaves.
- Once
- Every bill that leaves is recorded against its invoice under a unique key. Exporting it again is refused, rather than paid twice.
- Your codes
- Each line posts to your expense account and the tax to your tax account, with your package's own tax code, so it does not add tax again.
- Your books
- We say what is owed, not that it was paid. Where your package allows it, bills land as drafts for your accountant to approve there.
Every app works without it.
Integrations is optional. Compliance, Inventory and Procurement are complete on their own, and nothing in them waits on a connection. A bill export needs no accounting subscription from us; a live connection runs on your own Xero or QuickBooks Online subscription.
What exists, and what comes next.
- Now Bill export
- A file your package imports as bills: Xero matches its columns by name, QuickBooks Online maps them on upload. Built, and waiting on its first pilot's import.
- Next Your package, connected
- Matched invoices pushed as bills by the scheduler, with a sync log and retries. Built for the first pilot's package, Xero or QuickBooks Online.
- Then The other package
- The second connector, when a pilot keeps its books there. Nothing is built ahead of a customer who needs it.
Keeping your books by hand?
Tell us which accounting package you use and how many bills a month you enter. The first pilot's package is the first live connection we build.