Invoice automation that cuts the month-end chase

In a South African factory the invoice job is simple to describe and expensive in hours. A PDF arrives. Someone keys the supplier, amount, and job or PO. Someone matches it. Someone chases the missing one. Payment waits. The owner hears about it when a supplier calls.

A measured workflow reads the invoice, drafts the capture, and flags a mismatch. A person still approves. That is invoice automation we will stand behind. Buying a new accounts-payable product is a different project.

Where the hours actually sit

Retyping is visible. The chase is larger. Missing PO numbers, job cards that do not match, and “please resend” loops eat more calendar time than the keystrokes. Time both before you change anything.

If two people already agree what a complete invoice looks like — supplier, amount, VAT, job or PO — a draft step can start. If that definition lives in one person’s head, write it down first.

What the workflow should do

• Read the supplier PDF or photo.
• Draft the capture line your bookkeeper would have typed.
• Propose a match to an open PO or job card when one exists.
• Hold the line for a person when the match fails or VAT does not add up.

The person who posts today should still post. The win is that they stop retyping and spend their time on exceptions. OCR is only the read step. It is not the whole job.

What not to change in the first month

Do not replace the ledger. Do not ask the floor to adopt a new portal before the draft-and-approve path works on the invoices you already receive. Start with the suppliers that arrive every week. Count the hours on those, then decide whether a wider change is worth it.

That is the same rule as the other AI automation examples and the offer on the home page: time one job, then take a scoped step.