Invoices and forms with AI: a builder's guide to document processing

Document automation for a small business is a five-step pipeline: capture the document wherever it arrives, extract only the fields the task needs with a confidence score, validate them against simple rules (totals add up, the supplier is known, it isn't a duplicate), send anything uncertain or above an amount to a person for approval, and then enter the data into the accounting system or sheet and file the document in a named folder. AI does the extraction; the validation and approval steps are what make the accountant trust it.

What problem is the owner actually paying to remove?

Retyping. Invoices arrive by email, WhatsApp and photo; someone types the supplier, date, amount and VAT into a sheet or accounting software, then files the PDF somewhere nobody finds. The automation removes the typing and the filing. The number to measure is minutes per document, or documents processed per week without manual entry.

Step 1: capture

Define the channels: a dedicated email address, a WhatsApp number, a shared folder, an upload form. Everything lands in one inbox folder with the original preserved. Photos get straightened and cropped before extraction; a quality check rejects unreadable images with a message asking for a better one.

Step 2: extract

List the fields the task needs and nothing more: supplier name, invoice number, date, net, VAT, total, currency, and the line items only if the accounting needs them. Ask the model to return them in a fixed structure with a confidence per field and to say "unknown" rather than guess. Hebrew, English and mixed layouts are normal; test with real documents from the client, not samples from the web.

Step 3: validate

Rules a person can read: net plus VAT equals total within a small tolerance; the supplier exists in the client's list (or is flagged as new); the invoice number hasn't been seen before; the date is plausible; the currency is expected. Failed validation is not an error, it's a route to approval.

Step 4: approve

Low confidence, failed validation, a new supplier, or an amount above the client's threshold goes to a person with the document image and the extracted fields side by side, in the channel they already use. One tap to approve or correct. Corrections feed back as examples. In the first weeks, everything goes through approval; then the safe cases are released.

Step 5: enter and file

Write the fields to the accounting software or the sheet, in the client's structure. File the original as YYYY-MM/supplier-invoice-number.pdf in the client's storage with a link in the record. The accountant now finds every document in seconds, which is often the benefit they mention first.

Where it fails

Scoping the pilot

One document type, one channel, one destination: supplier invoices by email into a sheet with monthly folders, approval on everything for two weeks. Measure documents per week and minutes saved. Then add channels, then the accounting integration, then other document types (delivery notes, forms, receipts).

Best fit and not a good fit

Best fit: businesses receiving dozens of documents a week with a bookkeeper who retypes them. Not a good fit: a handful of documents a month; the pilot won't produce a number worth measuring. Automate the filing only, or skip it.

What to do this week

Ask the client for last month's invoices and where they went. Count them and time the retyping. That count and that time are the baseline and the case for the pilot.