Per company, not per seat
Your company pays one subscription. Add reviewers, approvers, and the auditor who shows up in March — the bill doesn't move when the head count does.
Onivo · Pricing
AP automation pricing, sized to your invoice volume
Onivo AP is a subscription per company. Tiers follow how many invoices you process each month — not how many people log in to review, approve, or look something up. Pricing is quoted on a short call, sized to your invoice volume.
The model
One subscription, tiered by how much you process
Tiers sized by invoice volume
The tier is set by the invoices you run through Onivo each month. A team processing a few hundred pays less than a team processing a few thousand, and the tier moves when your volume does.
Quoted on a short call
No configurator, no gated grid. Tell us your monthly invoice volume and the ERP you run, and you leave the call with your tier and your number.
What's included
Every tier runs the whole product
The tier sets your invoice volume; every tier includes the full workflow — capture, coding, matching, approvals, ERP sync and the audit trail.
- Invoice capture and OCR — PDFs and emailed attachments read automatically, with a learning layer that improves per vendor from your team's corrections.
- Line coding — each line coded to a GL account, cost center, and project. A field is left blank rather than guessed.
- 2-way and 3-way matching — lines checked against the purchase order and goods receipt, with price, quantity, and amount tolerances you set.
- Approval routing — approvals routed by amount, cost center, and project.
- ERP sync — approved invoices become bills in your system's own terms, with query-before-create so nothing posts twice.
- Tamper-evident audit trail — a record of every decision, from arrival to posting.
- Duplicate protection — duplicate and reissued invoices caught before they are paid twice.
- Multi-invoice PDFs — one PDF holding several invoices is split into its parts.
A worked example
What a mid-volume tier includes
Take a team processing around 2,000 invoices a month. Every one of them arrives by email or upload and is read automatically — a PDF holding several invoices is split into its parts first — and the learning layer improves per vendor as your team corrects it. Each line is coded to a GL account, cost center, and project; a field the system is not sure of is left blank rather than guessed.
The same tier runs the controls. Lines are checked against the purchase order and goods receipt with the price, quantity, and amount tolerances you set; a duplicate or reissued invoice is held before it is paid twice; approvals route by amount, cost center, and project. Approved invoices post to your ERP in its own terms, with query-before-create so nothing posts twice, and every decision from arrival to posting lands in the tamper-evident audit trail — how that trail is protected is on the security page.
Getting started stays imports, not a project — masters in via CSV, ERP connected, rules set — and the bill does not move when reviewers, approvers, or the auditor join later in the year.
How the quote is built
Two questions set the number
Monthly invoice volume is the main driver — it sets the tier, and the tier moves when your volume does. (This page covers Onivo AP; the receivables side, Onivo AR, is in early access.) The second question is how many companies will run their payables through Onivo. Which ERP you connect shapes the setup, not the price — cloud accounting platforms sync over a live API, desktop systems work from export files, and every tier is fully featured either way.
That is the whole call. If you are evaluating alternatives, the comparison guides name the job each tool is hired for — and say plainly when the other tool wins. Bring your monthly invoice count and the ERP you run; you leave with your tier and your number.
Implementation
Getting started is imports, not a project
Import your masters
Vendors, GL accounts, and cost centers come in via CSV — the same exports your current system already produces.
Connect your ERP
Cloud accounting platforms connect over a live API; approved invoices sync as bills in your system's own Class, and Project terms. Other ERPs are rolling out — see the integration roadmap.
Set your rules
Choose your matching tolerances and who approves what, by amount, cost center, and project. Then forward an invoice and watch it land.
FAQ
Pricing, answered plainly
Why is there no price on this page?
Because an honest quote depends on your invoice volume, and we would rather size it on a short call than publish a grid that fits nobody. Bring your monthly invoice count and the ERP you run; we quote the tier on the spot.
Do all tiers include matching, approvals, and ERP sync?
Yes. Every tier includes invoice capture, line coding, 2-way and 3-way matching, approval routing, ERP sync, and the audit trail. Tiers size the invoice volume, never the feature list.
How long does implementation take?
Typically days to a couple of weeks for a cloud-accounting shop. You import vendor, GL, and cost-center masters via CSV, connect your ERP, set tolerances and approval rules, and forward the first invoice.
One short call
Book a demo
Get your quote and see the product in the same half hour
Bring your monthly invoice volume and the ERP you run. We walk through a live demo — capture, coding, matching, approvals, the ERP post — and quote the tier that fits.