The challenge
In this scenario, the finance team receives several thousand supplier invoices and delivery notes a month, by e-mail, through supplier portals and on paper. Some are clean PDFs; many are scans or phone photos, in Arabic, in English or in both. Clerks read each one, find the purchase order, check quantities against the delivery note and key the lines into the ERP.
Errors surface late — at month-end, or when a supplier chases payment. Duplicates slip through, VAT details are keyed wrongly, and the team spends its time typing instead of resolving the exceptions that need judgement.
ZATCA’s e-invoicing (Fatoora) requirements mean many suppliers now issue invoices that carry a QR code and structured data. Not every document does, and delivery notes fall outside those requirements altogether. The process has to handle both.
Our approach
We would start with a two-week discovery: sample a few hundred real documents, measure how long each type takes today and where errors occur, and agree targets with the finance owner before building anything.
Structured data first, AI for the rest
Where an invoice carries e-invoice data — an embedded XML file or a QR code — the pipeline reads it directly. Everything else goes through OCR tuned for Arabic and English, then a language model that extracts supplier, VAT number, dates, totals and line items into a fixed schema.
Checks before anything is posted
- Match each invoice to its purchase order and delivery note, line by line
- Validate VAT numbers, totals and tax arithmetic
- Flag likely duplicates by supplier, invoice number, amount and date
- Send any low-confidence field or failed check to a review queue, with the source document beside it