The AP platform, layer by layer
Accounts Payable Platform: The AP Automation Platform for Invoice Capture, Line-Level Coding, and Approvals
Try it now, capture a real invoice
Your file is used only for this demo and deleted automatically within hours.
An accounts payable platform is the system of record for what you owe suppliers: it takes the invoice in, reads the data off it, codes every line to a GL account, routes it for approval, and keeps a dated audit trail. Vendors use the word for products that cover very different amounts of that job, which is why two quotes for an accounts payable automation platform can differ by a factor of ten. This page breaks the category into seven layers, shows which ones we cover and which we do not, and gives you the questions that separate the platforms that read your invoices well from the ones that only look like they do.
7
layers to compare any AP platform on
Line level
GL coding, a different account per line
0
templates to map before your first invoice
Accounting sync on the roadmap
What this accounts payable platform actually runs
Capture, coding, approval and the payables record. Stated plainly, with the gaps named further down the page.
Capture with nothing to configure first
Upload a PDF or forward it to your intake address. The model pulls vendor, invoice number, PO reference, dates, currency, subtotal, tax, discount, shipping and total, plus every line item, on suppliers it has never seen before.
GL coding at the line, not the invoice
Each line on a bill carries its own GL account. A single invoice can split across six cost centres without a manual journal afterwards, which is the difference between usable department reporting and a catch-all account.
Confidence scores on every extraction
The platform stores how sure it was about each field. Low confidence surfaces for a human look instead of quietly landing in your ledger, so review effort goes where it is actually needed.
A vendor master that earns its keep
Tax ID, 1099 flag, payment terms, default GL account, bank and remittance details, and status per vendor. January stops being an archaeology project because the 1099 flags were set as you went.
Threshold approval with a dated audit log
Set an amount above which a bill needs sign off. Every approval writes an immutable record of who approved what and when, which is the evidence an auditor asks for and email cannot produce.
REST API for the things we did not anticipate
POST an invoice for upload, GET invoices, a single invoice by hash, or your vendor list. Included on the Scale plan, and the route to your own systems while accounting sync is still on the roadmap.
How to put an accounts payable platform in without a project plan
Four steps. The first invoice goes through on day one, not after a template build.
Load your GL accounts
Paste the chart of accounts you already use. This is the only setup that matters, because coding is where the platform earns its money and it needs your account list to do it.
Send in ten real invoices, including the awkward ones
Your largest supplier, a multi page invoice, a scan, a phone photo, and one with unusual tax. Demo sets are curated for the vendor. Yours is not, and it will tell you the truth faster.
Set the approval threshold
Pick the amount above which a bill needs a second pair of eyes. One number, applied consistently, catches more than a routing tree nobody maintains.
Count the corrections
Go back through those ten invoices and count fields you had to fix. That number, not a feature grid, tells you what the next twelve months will feel like on any platform you shortlist.
Payables run out of an inbox against payables run on a platform
The failure modes on the left are the ones finance teams describe when they start shopping.
Invoices in email and a spreadsheet
- Invoices sit in one person's inbox until they are back from leave
- Someone retypes around 30 fields per invoice
- Everything is coded to one catch-all account, so department reports are guesswork
- Approvals are forwarded emails nobody can reconstruct at audit
- Answering what do we owe right now means rebuilding a spreadsheet
- 1099 status gets worked out in January from memory
One accounts payable platform
- Everything arrives in a shared queue the moment it is sent
- Fields are read off the document with a confidence score attached
- Each line carries its own GL account, so the split is right at entry
- A dated approval record per bill, showing who signed off and when
- The payables balance and vendor master are one live record
- The flag is set on the vendor when they are onboarded
Where an AP platform pays for itself
Volume matters less than how complicated the coding is.
Finance teams past roughly 200 invoices a month
This is where retyping stops being part of the job and becomes the job. The hours go into data entry and coding, and both are the things a platform removes rather than reorganizes.
Businesses splitting invoices across cost centres
One supplier invoice covering six departments is where invoice level coding falls over. Line level accounts mean the split happens at entry instead of in a correcting journal three weeks later.
Teams that just failed an audit sample
Forwarded approval emails are not evidence and auditors say so. A dated approval log per bill answers the sample request directly, which is usually the cheapest control to fix.
Companies whose AP knowledge lives in one person's head
When the person who knew every supplier's coding by heart goes on leave, the process stops. A platform holds the vendor defaults and the account mapping where the whole team can see them.
What is an accounts payable platform?
An accounts payable platform is the system of record for money your business owes suppliers. It takes in the invoice, reads the data off it, puts a general ledger account on every line, gets the right person to approve it, and keeps a dated record of who did what. Accounting software stores the resulting journal entry. The platform is the layer in front of it, where the work happens.
That distinction matters when you are buying, because the word "platform" gets used for products that cover very different amounts of the job. Some cover intake and capture only. Some are really payment rails with a light approval screen bolted on. A few genuinely run the whole path. If you compare them as though they all do the same thing, you will buy the wrong one.
The seven layers of an accounts payable platform
Break any AP automation platform into layers and the sales pitches get easy to compare. Every vendor covers some of these. None of them, including us, covers all seven equally well.
| Layer | What it does | What goes wrong without it |
|---|---|---|
| 1. Intake | Gets invoices out of inboxes, post, and supplier portals into one queue | Invoices sit in a personal inbox while somebody is on leave |
| 2. Capture | Reads vendor, invoice number, dates, tax, totals and line items off the document | Someone retypes 30 fields per invoice and transposes a digit |
| 3. Coding | Puts a GL account on each line so the expense lands in the right place | Everything hits one catch-all account and the department reports are fiction |
| 4. Control | Matching, thresholds, duplicate checks, tolerance rules | You pay twice, or pay a price nobody agreed to |
| 5. Approval | Routes the invoice to whoever has authority and records the decision | Approvals happen by forwarded email and cannot be evidenced at audit |
| 6. Record | Holds the payable, the vendor master, and the audit trail | Nobody can answer "what do we owe right now" without a spreadsheet |
| 7. Payment and sync | Moves the money and writes the entry back to your accounting system | Double entry, and a month end spent reconciling two systems |
Most buying mistakes come from assuming a vendor is strong at layer 4 because it is strong at layer 2. Reading an invoice well and controlling it well are separate engineering problems. Our invoice matching software page sets out where the control layer sits, and the AP automation technology comparison covers what actually powers the capture layer at eight named vendors.
What this accounts payable platform does, and what it does not
Here is the honest version, laid out against the same seven layers. We would rather you find the gap on this page than three weeks into a trial.
| Capability | In AutoPayables today |
|---|---|
| Upload or email invoices into one queue | Yes, upload or forward to an intake address |
| AI capture with no templates to build | Yes, including line items, with a confidence score stored per extraction |
| Line level GL coding, a different account per line | Yes, this is the part we are genuinely good at |
| Vendor master with tax ID, 1099 flag, terms, remittance details | Yes |
| Purchase order records | Yes, POs and PO lines are stored |
| Approval on a spend threshold, with a dated audit log | Yes, one numeric threshold |
| REST API for invoices and vendors | Yes, on the Scale plan |
| Two way or three way PO matching | No |
| Duplicate invoice detection | No |
| Multi level or role based approval routing | No, one threshold rather than a routing tree |
| Paying the vendor | No payment rail. Payments are recorded, not sent |
| QuickBooks, Xero or NetSuite sync | Not yet, on our roadmap. The REST API is the route today |
| Multi entity or subsidiary dimensions | No. The honest workaround is a GL account per entity |
If layers 4 and 7 are the reason you are shopping, buy something else and do it with our blessing. The accounts payable solution providers roundup names the vendors that cover them, and accounts payable automation tools compared puts pricing next to scope.
What is the difference between an accounts payable platform and accounting software?
Accounting software is the ledger. An accounts payable platform is the workflow that decides what goes into the ledger and proves it was authorized. QuickBooks, Xero, Sage and NetSuite all hold a bill record, but they expect somebody to have already read the invoice, coded it, and got sign off. The platform is where that happens, and it hands over a clean, approved, coded result.
Teams under roughly 200 invoices a month often run without one and cope. Above that, the retyping becomes the job rather than a part of it. Our accounts payable systems page walks through where the line usually falls.
How much does an accounts payable platform cost?
Pricing splits into three shapes. Per user per month is common at the small business end: BILL publishes Essentials at $49, Team at $65 and Corporate at $89 per user per month, with Enterprise quoted. Per document or per invoice volume is the mid market norm, and it is how we price. Quote only is standard for enterprise suites, including Coupa, SAP Concur, Stampli, Esker and Medius, none of which publish list pricing.
Watch the extras, because they are where budgets break. Tipalti lists $99 Select, $199 Advanced and a quoted Elevate tier, then adds per payment fees and roughly $500 to $600 a month for each additional entity. Implementation is often a separate line, and it is fair to ask for it in writing before you sign. Our own plans are Starter free for 20 invoices a month, Growth $49 for 200, and Scale $149 for unlimited invoices plus the REST API. The AP automation pricing page compares the shapes side by side.
What should an accounts payable platform integrate with?
Three things, in this order. Your accounting system or ERP, because that is where the entry has to land. Your email, because that is where invoices actually arrive whatever the supplier portal promises. And your own systems, through an API, because every finance team eventually wants a number somewhere the vendor did not anticipate.
Ask for the integration detail in writing rather than taking the logo wall at face value. The useful questions are which direction data flows, whether it syncs dimensions and custom fields or only the GL account list, how often it runs, and who built the connector. Stampli, for example, publishes a five minute down and two hour up cadence for Sage Intacct and states it built the connector in house. That is the level of specificity worth insisting on. See AP automation integrations for what to ask each vendor.
Can an accounts payable platform pay vendors?
Some can and some cannot, and the difference is a licensing question rather than a feature toggle. Moving money means holding money transmitter licences or partnering with someone who does, which is why platforms that pay tend to charge per payment or take a slice of the card rail. BILL, Tipalti, AvidXchange, Melio and Ramp all move money. Capture and workflow tools, including this one, record the payment against the invoice and leave the transfer to your bank.
Neither model is wrong. If your bank already handles a payment run you are happy with, paying a platform to duplicate it is spend for its own sake. If chasing down remittance advice is eating a day a week, the payment layer earns its fee. We cover the trade off on the B2B payments platform page.
How long does it take to implement an accounts payable platform?
It depends almost entirely on the capture technology and the ERP connector, not on the size of your team. A template based tool needs somebody to map field positions for each supplier layout, so go live stretches while the template library gets built. Document aware capture skips that step, which is why a small team can be processing real invoices the same afternoon.
The ERP connector is the other variable. Medius publishes go live at eight to twelve weeks. Tipalti describes its Sage Intacct connection as a paid engagement of about four weeks. If you are not syncing to an ERP on day one, most of that timeline disappears. Our own setup is an upload and a list of GL accounts, and there are no templates to build first.
How do you evaluate an accounts payable platform before buying?
Test it on your worst invoices, not the vendor's demo set. Collect ten real documents: your largest supplier, three you onboarded this year, a multi page invoice, a scan, a phone photo, and one with awkward tax treatment. Run them through every shortlisted platform and count how many fields you had to correct. That number predicts your first year far better than any feature grid.
Then ask each vendor the three questions they least like: what does your product not do, what is the total first year cost including implementation, and can I see the accuracy figure measured on invoices like mine. A vendor that answers all three plainly is telling you something useful about the next three years. Our accounts payable audit software page covers the evidence side, which is usually the thing finance leaders discover they needed after the fact.
Who an accounts payable platform is worth it for
The pattern we see is volume plus coding complexity. A team doing 40 simple invoices a month against five GL accounts does not need one. A team doing 300 invoices that each split across six cost centres needs one badly, because the coding is where the hours go and where the errors that survive to the management accounts get made.
Growth stage companies hit this earlier than they expect, usually when the person who knew the coding by heart goes on leave. If that describes you, accounts payable process automation and invoice processing software both go deeper on the operational side, and accounts payable management software covers the vendor master and reporting layer.
Frequently asked questions
An accounts payable platform is the system of record for money owed to suppliers. It takes invoices in from email or upload, reads the data off them, codes each line to a general ledger account, routes the bill for approval, and keeps a dated audit trail. Accounting software stores the resulting entry. The platform is the workflow in front of it.
Accounting software is the ledger and expects an invoice to arrive already read, coded and approved. An accounts payable platform is where that work happens, then hands over a clean result. Most teams run accounting software alone until roughly 200 invoices a month, when the retyping starts to outweigh the subscription.
Three shapes exist. Per user per month, where BILL publishes $49 Essentials, $65 Team and $89 Corporate. Per invoice volume, which is the mid market norm and how we price at $49 for 200 invoices or $149 unlimited. And quote only, used by Coupa, SAP Concur, Stampli, Esker and Medius, none of which publish list pricing.
Some can, some cannot, and it is a licensing question rather than a feature. Moving money requires money transmitter licences or a partner who holds them, so platforms that pay usually charge per payment. BILL, Tipalti, AvidXchange, Melio and Ramp move money. Capture and workflow tools, including this one, record payments and leave the transfer to your bank.
Your accounting system or ERP first, because that is where the entry has to land. Then email, because invoices arrive there whatever the supplier portal promises. Then an API for your own systems. Ask which direction data flows, whether dimensions and custom fields sync or only the GL list, how often it runs, and who built the connector.
Capture technology and the ERP connector drive the timeline, not team size. Template based tools need field positions mapped per supplier layout, so go live stretches. Medius publishes eight to twelve weeks and Tipalti describes a roughly four week paid engagement for Sage Intacct. Without an ERP connector on day one, most of that disappears.
No. We store purchase orders and PO lines, but the engine does not perform two way or three way matching, and it does not run duplicate invoice detection or price variance tolerance checks. If matching is the control you are shopping for, our solution providers page names the vendors that do it properly.
It depends on coding complexity more than volume. Forty simple invoices a month against five GL accounts does not justify one. Three hundred invoices that each split across six cost centres does, because the coding is where the hours go and where errors survive into the management accounts.
Run your worst invoice through it before you shortlist anything
Upload one real supplier invoice, ideally the one that broke your last tool, and see every field the platform pulls out with its confidence score. No templates to build first, and the free plan covers 20 invoices a month.