bookkeeping

Invoice capture: what accounting software misses

AA
Aurum Avis Labs Author
7 min read

Invoice capture: the gap beside the accounting tool

Accounting software in a Swiss SME often already reads the invoice. bexio, Abacus, Sage, DeepCloud: PDF or photo, fields from the page, coding suggestion, often a match to the bank line. The gap that still costs a morning is the path into that tool: mail attachments, PDFs from portals, approval in Teams or on paper, and a purchase order that lives somewhere else. A second OCR product on documents the accounting tool already reads is usually wasted money.

This is for the office lead or finance person who keys supplier invoices, and for the owner who hears «we should automate bookkeeping». The reader runs an SME with office work; the trustee stays in the mandate. Closing, odd cases and the annual accounts stay with the trustee or the person who already signs them. A workflow can propose fields and queue a document. Once coding, period or input VAT is unclear, a human decides.

One of three office workflows, beside the Monday report and quote follow-up: three workflows worth automating.

What the software often already does

If the invoice is already in the tool, much of the «AI» pitch has shipped. Drop a PDF or mail it to the inbox the vendor gave you. The tool reads supplier, date, amount and tax, suggests an account and often a payment. The bank import then lines up against what you booked.

Use that path for every invoice that can reach it without a courier. Turn on the vendor’s capture and teach suppliers to mail the tool directly: that is the first fix and it does not need a project.

The trustee remains owner of the close and of cases the suggestion cannot see: a mixed bill, a foreign VAT knot, a document that is not an invoice. Say that out loud when a vendor offers to «replace the fiduciary work». The capture gap and the close are different jobs.

The path in, which is the actual work

Walk last month’s invoices and mark how each one arrived. In a typical small office the split looks like this.

A share already hits the accounting inbox and comes back as a suggestion. Leave those on that rail.

The rest is the gap: utility or telecom PDF behind a login, supplier cockpit, scan in a personal inbox, «ok to pay» in Teams or on paper, match to a purchase order or project code in Excel or a job tool. Five inboxes, three portals, and a clipboard workbook: often a shadow system in Excel. The sheet is a queue, not a second set of books.

A useful build starts where the document becomes a file a flow can see: shared mailbox or folder where the person drops the portal PDF after download. Scraping a forbidden portal or storing passwords in notes is not the design. If the portal has no export, the download stays a person. The flow starts at the drop folder.

Approval stays a person with a name. The flow can show amount, supplier and project code and wait. A thumbs-up in a busy channel is not a booking unless you deliberately chose that control and could explain it to the trustee.

A suggestion is not a booking

The model may fill supplier, date, amount, tax and a proposed account. Someone who knows the chart of accounts confirms or edits, then the booking exists. Practically that is a queue: waiting documents and done documents. The status «the AI posted it» is how a wrong input-VAT code reaches the books until the close.

Write when the queue may not auto-accept: unclear period, split lines, unknown supplier, total mismatch with the PO, personal data beyond the invoice. The boring single-line PDF from a known supplier can later get a lighter check after a month of the queue shows the error rate. You do not start there.

If every document is a project bill with many exceptions, it is not a first automation case. Same questions as which process to automate first: it repeats, it hurts, it has an edge (document in, confirmed fields out), and the file must exist already.

  1. Count one month

    How many invoices, and how each arrived: vendor inbox, portal, personal mail, paper.

  2. Turn on the rail you already pay for

    Accounting inbox, upload, bank match. Suppliers who can mail the tool directly should.

  3. One drop folder for portals

    The person downloads. The flow picks up the file. No second OCR on PDFs the accounting tool already reads.

  4. A queue with a named approver

    Suggestion on one side, booking on the other, after a person confirms coding, period and input VAT.

An architecture office, about forty invoices a month

Picture a 12-person architecture office in Bern. Books on bexio. The trustee does the close. About forty supplier invoices a month.

Roughly half arrive by mail in the bexio inbox. Coding comes back as a suggestion. The office confirms and moves on. That half is not the project.

The other half sits with the office manager: PDFs from two utility portals and a mobile login, materials supplier only in a cockpit, approval as a Teams message («ok for the model workshop»), project code on the job list not on the invoice. She keeps a holding sheet and keys the portal pile on Thursday. OCR already works for files that reach the tool. The pain is Thursday.

A sensible case is the drop folder plus the queue. She still downloads portals. PDFs go in one folder. A flow files them into the review list with fields the reader saw and an empty project code when the job list did not match. She fills the code, checks VAT on multi-rate bills, then the booking exists. The Teams «ok» becomes a field on the queue or stays manual habit. The trustee sees confirmed bookings.

What you do not build: a second OCR subscription, a promise that Thursday disappears, or a flow that posts the portal pile overnight. If a quarter of the pile is split project bills, those stay in the human queue.

When to stop

Stop when volume is a few invoices a week and the vendor inbox already catches them. The Thursday habit is not long enough to justify a build.

Stop when you wanted the trustee removed from the relationship. The capture path can be shorter. The judgement at the close is still theirs or yours.

Stop when the «process» is twelve special suppliers and no standard PDF. Write the exceptions down. Automate the standard pile first, or stay manual until one exists.

Bring the path, not a software shortlist

Who sends what, to which inbox or folder, how often, which tool holds the booking, who approves, where the purchase order or project code sits. One month of that in a list is enough for the Process Check. You leave with a case and a package size, or with «turn on the vendor inbox and stop there».

What the half hour covers: what the Process Check is.

Does automatic invoice capture replace the trustee?

No. OCR, coding suggestions and often bank matching can stay in the tool you already use. A workflow may propose fields and queue a document. When coding, period or input VAT is unclear, a person decides. The close and odd cases stay with whoever already signs them.

bookkeeping invoices process automation
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.