From Vendor Bill
to Coded Entry.
In Seconds.
InvoiceIQ by Analytos reads supplier invoices and shipping documents, checks them against your orders, and posts them into the ERP you already run.
Connected to your stack
Built for finance teams
| # | Vendor | Invoice # | Amount | Due | Coding | Match | Receipt | Posting |
|---|---|---|---|---|---|---|---|---|
| 1 | Acme Utilities | INV-1001 | 2,956.25 | 2026-09-30 | Coded | Non-PO | Not needed | Ready to post |
| 2 | Globex Services | GX-88412 | 14,320.00 | 2026-10-02 | Coded | 3-way · pass | Received | Ready to post |
| 3 | Initech Labor | IL-2026-77 | 8,150.40 | 2026-09-28 | Coded | 3-way · pass | Received | Posted · VB-4410 |
| 4 | Northwind Steel | NW-5531 | 22,410.00 | 2026-10-10 | From PO | Pending receipt | Expected 09-21 | Waiting |
| 5 | Riverside Water | RW-30921 | 1,180.00 | 2026-10-01 | Watchlist | Non-PO | Not needed | Needs review |
| 6 | Globex Services | GX-88412 | 14,320.00 | 2026-10-02 | Coded | Duplicate | Received | Held |
| 7 | Contoso Freight | CF-1189 | 3,420.55 | 2026-10-05 | Coded | Price +6.2% | Received | Needs review |
| 8 | Acme Utilities | INV-1002 | 3,011.90 | 2026-10-30 | Coded | Non-PO | Not needed | Ready to post |
- Step 1ReadEvery line of the invoice or shipping document, text or scan.
- Step 2MatchAgainst the order and what was received or shipped.
- Step 3CodeAccount, class and department from your own rules.
- Step 4PostA person approves; it posts to your ERP with a full record.
Core capabilities
Get full visibility and control
over every document
One shared engine for reading, coding, matching and posting — built for finance teams that have to be able to show their working.
Integrate your finance stack
and simplify your close
Your ERP stays the system of record. InvoiceIQ sits in front of it, reads the documents it was never designed to read, and hands it a finished, reconciled entry — through one adapter per ERP.
Stay on top of every bill and shipment with live status across intake, coding, matching and posting — and a notification when a waiting bill finally has its goods.
Save hours by letting a shared mailbox feed the pipeline on its own, exactly once, and by letting rules your team already wrote make the same decision every time.
Unlock full control through the documented REST API and a canonical data model, so swapping or adding an ERP is one adapter — not a rebuild.
What it catches
The mistakes InvoiceIQ by Analytos stops
before they reach the ledger
Use cases
InvoiceIQ adapts
to the way you work
PO-backed purchasing with 3-way matching
Goods are ordered, received and invoiced by three different parties. InvoiceIQ matches all three within your tolerances, codes the bill, and posts — routing anything unproven to a person with the reason stated.
- Bill composed from the receipt, so over-billing is structurally impossible
- Waiting bills advance automatically as goods arrive
- Tax and freight placed correctly, never counted against received goods
- PO exists
- Vendor identity
- Price within 2%
- Quantity ≤ received
- Not already billed
2-way and non-PO bills, coded from your rules
Consulting hours, utilities, rent and licences have nothing to receive into a warehouse. Judge them against the order alone, or code them straight from vendor rules — still under the golden rule.
- A policy choice per vendor or company-wide, not a different product
- GL, class and department each resolved independently
- Statements, credits and prepayments recognised and routed, never billed by mistake
From bill of lading to customer invoice, the same day
The shipment document arrives as a PDF or a scan. InvoiceIQ finds the sales order, checks what actually shipped, records the fulfilment and raises the invoice at the order rate — drawing the order down so nothing bills twice.
- Partial shipments bill only what went out
- Over-shipments invoiced and flagged, never silently dropped
- Cannot bill for goods without a recorded fulfilment
- Drop ships too: a vendor shipment straight to your customer writes the receipt and the fulfilment together
Invoices that carry job, site, class or department
The same vendor hits different accounts depending on what was bought and which site it was for — and the logic lives in one person’s head. InvoiceIQ turns it into rules the whole team can read, test and edit.
- Signal lookups read the cost centre wherever the vendor prints it
- Lookup tables imported from Excel, CSV or pasted text
- Every coded line records which rule and which lookup answered
“Code Globex lines to 600200 and the site named in the description. If the line mentions security, use 600250 instead.”
Onboarding
Implementation built around
your chart of accounts
InvoiceIQ is deployed into your environment and mapped to your vendors, your customers and your dimensions — which is exactly why the coding comes out right rather than approximately right.
A walkthrough on your own documents
We start with your real bills, orders and shipping paperwork and show what InvoiceIQ would produce from them before anything is configured.
Vendor, lookup and rule mapping
Lookup tables import from Excel, CSV or pasted text. Coding rules are written in plain English and validated against your own past invoices.
ERP adapter configuration
One adapter connects the order, the goods movement and the posting. The demo ERP lets the team rehearse the whole flow with no live credentials in reach.
Backtest, then go live
Nothing governs money until it passes a test on your history. Your team sees what a rule would have done before it does anything.
Compare approaches
A better way to
code and match invoices
| InvoiceIQ | Manual keying | Generic capture tools | |
|---|---|---|---|
| The coding decision | Rules your team owns — the same invoice codes the same way every time | An experienced person, differently on different days | A model’s best guess, with no rule to point at |
| Reads scans and text PDFs | Structure-first parsing, OCR and vision, every value keeps its position on the page | A person reads anything, slowly | Capture is broadly a solved problem |
| Reconciles to the printed total | The golden rule — cannot be switched off by anyone | If someone remembers to check | Sometimes, and often only as a warning |
| 2-way and 3-way matching | Nine named checks, your tolerances, a reason on every verdict | By hand, on the invoices that get the time | Usually header-level, rarely composed from the receipt |
| Explains why | Rule, lookup, policy and approver recorded on every line and every posting | Institutional memory | A confidence score |
| Changing a rule | Plain English, backtested on your history, versioned with rollback | Retrain the person | A ticket to the vendor and a wait |
| Where it runs | Your environment — you own the code, one adapter per ERP | Your office | The vendor’s cloud, with your ledger inside it |
Ready for coding you can defend?
Start on the side of the ledger that hurts most. The other one is already built — same engine, same audit trail, one login.
Frequently asked
questions
InvoiceIQ by Analytos is an AI invoice automation layer that sits on top of the ERP a finance team already runs. InvoiceIQ AP captures supplier invoices, performs 2-way and 3-way matching against purchase orders and receipts, routes exceptions for review and detects duplicates. InvoiceIQ AR turns shipping documents into customer invoices priced from the sales order. Both post into the existing ERP without a rip-and-replace. It is built for mid-market businesses that buy and ship physical goods, such as manufacturers and distributors.
Analytos (Analytos Labs). InvoiceIQ by Analytos is not related to other products that use the name InvoiceIQ.
Turning a document into a correctly coded, matched and posted entry. On the payables side that is a vendor invoice becoming a vendor bill in your ERP; on the receivables side it is a bill of lading becoming a customer invoice. It sits in front of your ERP and hands it a finished, reconciled entry with a reason for every line.
Your ERP is the system of record and it is very good at that — it holds the order, the ledger and the approvals, and it matches and posts well. What it was never built to do is the thinking before a transaction reaches it: reading the supplier’s document, deciding which account and dimensions each line belongs to, and telling you why. That is the layer InvoiceIQ adds. Your ERP tells you what was posted; this tells you why, in time to do something about it.
NetSuite is live in production for a client. Stockly, Analytos’s own ERP, has a posting path. QuickBooks is the intended receivables target and its adapter is a stub today. Adding an ERP means writing one adapter against the same canonical model — fetch the order, fetch what moved, post the result — so it is a scoping conversation rather than a rebuild.
We deliberately do not quote a percentage, because any number depends on your document mix. Instead we made accuracy checkable: every bill has to reconcile to its own printed total or it does not post, table structure is detected first so missing rows are recovered, and anything unproven is held for a person with the reason stated.
Models read the document and write rule code at authoring time. At posting time no model is called for the accounting decision — an approved rule runs in a restricted sandbox with no imports, no network, no filesystem, no clock and no randomness. That boundary is why the same invoice codes identically every time.
Yes. Describe the rule in plain English; InvoiceIQ generates the code, shows you the logic back in plain language, compiles it in the sandbox and backtests it against your own past invoices. It only activates if the test is clean, and every version keeps one-click rollback and an audit row naming who changed it.
No. InvoiceIQ is deployed into your environment and mapped to your vendors and chart of accounts, and you own the code. Book a walkthrough and we will run your own documents through it.
Either, or both. The packager produces a build containing the platform and only the products you bought — the other product’s code is physically absent, not feature-flagged. Adding the second later is a configuration change, not a second implementation.