We make software in this category — disclosed at the end, where it comes up — but the first two-thirds of this page is true no matter whose tools you use, including none.

Every business has a pile.

It arrives as PDFs attached to emails, a spreadsheet from a supplier who has always sent spreadsheets, a photo of a receipt someone shot on a job site. Somebody opens each one, reads five or six numbers off it, types those numbers into the accounting system, and then asks somebody else whether it is all right to pay.

That loop is the work. Not the invoice — the retyping, and the waiting in the middle of it.

It is also the least interesting thing anyone in your business does, which is why it slides. The pile is never urgent on any given Tuesday and always urgent at the end of the quarter.

So the useful question is not “can AI do invoices.” It is: which parts of that loop can actually be handed over, which parts cannot, and what has to be true before you’d let it near your books.

What the machine is genuinely good at

Reading a document and pulling the fields out of it. Vendor, invoice number, date, amount, line items, purchase-order reference. Given a PDF that was generated by software — which is most invoices — this works, and it works on the messy ones too: different layouts, fields in different places, tables that don’t line up.

Here is the limit nobody in this category volunteers, and it is the single most common reason a paperwork pilot dies in week two.

If the invoice is a scan or a phone photo, there is nothing to read. A PDF generated by a computer carries a text layer. A picture of a piece of paper does not — it is an image, and text extraction returns empty. Any tool that promises to read “your invoices” is quietly assuming yours are digital. Ours does the same: our extraction covers PDF, Excel and CSV, and a scanned invoice needs either optical character recognition on top or a human at the keyboard.

So before you evaluate anything, go and look at last month’s pile and sort it into two stacks: files a computer made, and pictures of paper. The ratio between those two stacks predicts more about whether this will work for you than any feature list will.

The part that matters more than extraction

Getting the numbers off the page is the demo. Deciding whether the numbers are right is the job.

Three checks carry most of the value, and none of them are glamorous:

Is this a vendor we actually use? The classic invoice fraud is not a forged document, it is a real-looking invoice from a company you have never bought anything from, for an amount small enough that nobody wants to be the person who queries it.

Does it match what we ordered? A purchase-order match catches the duplicate that arrives twice, the quantity that grew between order and delivery, and the “price increase” that was never agreed.

Is it big enough that a person must decide? Every business already has this threshold, even if it lives in somebody’s head. Writing it down is most of the work of automating it.

An extraction error is annoying — a wrong date, a transposed digit, and someone fixes it. A validation error is what actually costs money. Which means the interesting part of any tool in this category is not how cleverly it reads; it is what it does with what it read, and who it asks.

The paperwork that has a date on it

Some of this pile is discretionary. Some of it is not, and the deadlines have moved recently in ways a lot of small businesses have not noticed.

In the US, the paper threshold collapsed. If you file ten or more information returns in a calendar year — 1099s, W-2s, 1098s, all types added together — you must file them electronically. That threshold used to be 250 per form type. It became 10 in aggregate for returns filed on or after 1 January 2024, and a ten-person business that uses a handful of contractors crosses it without thinking about it. The IRS runs a free filing portal for exactly this case, which is worth knowing before you buy something.

If you invoice European customers, “invoice” is becoming a data format by law. In France, from 1 September 2026 — this month — every business must be able to receive structured electronic invoices, large and mid-sized companies must issue them, and smaller companies follow on 1 September 2027; invoices travel through a state-approved platform rather than as an email attachment. In Germany, the obligation to be able to receive structured e-invoices has applied since 1 January 2025, with issuing phased in for larger businesses in 2027 and everyone in 2028.

You may not be in scope for any of that. The direction of travel matters anyway: the paperwork is turning into data whether or not you automate it. A business that can already produce and consume structured invoice data ends up compliant almost by accident. A business built around emailing PDFs back and forth has a project waiting for it.

What happens when it’s wrong

Everything above says automate. This section is why anyone actually goes through with it.

The AI will be wrong sometimes. Not often, and less often than the person doing this at 6pm on a Friday, but sometimes — and the difference between a system you trust and one you quietly stop using is entirely about what the wrong answer costs.

The shape that works is boring and it has three parts. The AI drafts the entry rather than making it. A named person approves what actually posts, with the extracted fields and the validation flags in front of them. And the decision leaves a record — who approved this, when, and what they were looking at — so that in nine months, when a vendor disputes it or an accountant asks, the answer is a record rather than a memory.

That third part is the one people skip and then regret. It is also, since the law changed this year, the one that has teeth: as we covered in detail with the primary sources, a California statute now bars a defendant who “developed, modified, or used” an AI system from arguing that the AI acted on its own. “The software did it” is not available. “Here is who approved it, and when” is.

Three minutes of this running on a real invoice — including the one that got held back.

What it looks like when it’s running

Ours ships as a starting workflow rather than a blank canvas, and the sequence is short enough to describe completely.

An invoice arrives. The AI extracts the fields and runs the three validations — vendor known, purchase order matched, amount against your approval threshold. It goes to the person who owns accounts payable, with the flags visible, and they approve or reject it. On approval, the accounts-payable entry posts to your accounting system, the file gets filed where your team already looks for it, and the payment gets scheduled. Every step lands in the record.

Three honest details about that, because the details are where these things are won or lost:

It records what is owed. It does not pay anyone. The posting step creates an accounts-payable entry in QuickBooks — a bill, money owed to a vendor. The payment step schedules and notifies. Moving money stays where it already is, with your bank and the person authorised to do it.

Until you connect your accounting system, it runs dry. An install that has not been connected logs what it would have posted instead of posting it. That is the sane way to spend the first week: let it run alongside your existing process and compare the two piles before anything reaches your books.

The reading can happen inside your own environment. The extraction step can run against a model hosted on your own hardware rather than a third-party API, which for anyone handling vendor data under confidentiality terms is the difference between a conversation with your lawyer and no conversation at all.

The short version

The pile is not an invoice problem, it is a retyping-and-waiting problem, and the retyping is the part a machine is genuinely better at than a tired human at the end of a Friday.

Sort your pile into computer-made files and pictures of paper before you evaluate anything — that ratio decides more than the feature list. Spend your attention on the validations rather than the extraction, because that is where the money is. Check whether you have already crossed a filing threshold you didn’t know about. And insist that a person approves what posts, with a record of that decision, because the alternative is a system nobody can defend nine months later.

Then let the machine do the typing.

Sources

  • The US e-filing threshold — IRS, Topic no. 801: Who must file information returns electronically. Ten or more returns in aggregate across all types, for returns required to be filed on or after 1 January 2024; the previous threshold was 250 per form type. The IRS’s free Information Returns Intake System (IRIS) portal is described on the same page.
  • France’s e-invoicing timetable — impots.gouv.fr, Je passe à la facturation électronique. Reception obligation for all businesses and the issuing obligation for large and mid-sized enterprises from 1 September 2026; micro, small and medium enterprises from 1 September 2027; transmission via a state-approved platform.
  • Germany’s e-invoicing timetable — European Commission, eInvoicing in Germany. Ability to receive structured e-invoices since 1 January 2025; issuing mandatory for businesses above €800,000 turnover from 1 January 2027 and for all businesses from 1 January 2028.
  • What “posting an AP entry” means — Intuit, QuickBooks Online API: the Bill entity. A bill is a recorded liability to a vendor. Creating one is not paying it, which is why the payment step in the sequence above is a scheduling step.
  • The liability position referenced above — covered with its own primary sources in when your AI makes an expensive mistake, who pays.

Disclosure: we make HitLai, a governed AI platform for small businesses. The invoice sequence described above ships as a starting workflow — AI extracts and validates, a named person approves what posts, the entry lands in your accounting system and the decision lands in a timestamped, tamper-evident record. It never moves money. If you would rather inspect the mechanics than take our word for them, the orchestration core, AICtrlNet Community Edition, is free and MIT-licensed.