FAQ
Frequently asked questions
Straight answers to the questions every InvoiceIQ evaluation asks.
Everything we get asked
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.
Want to see it rather than read about it?
A walkthrough takes an hour and starts with your own documents.