Capture a usable document
Send a clear, complete photo or PDF. A multi-page invoice should stay together; separate invoices in one scan need to be identified individually. Keep the original attachment and record its source. When a handwritten item or date is uncertain, mark it for review rather than guessing a supplier, product or invoice period.
Validate the fields that change the transaction
Check supplier, invoice number, date, product, quantity, unit price, tax and total. In a sample bill with 12 units at SAR 10 before tax, the expected line net is SAR 120. Compare extracted values with the actual document, including discounts, tax treatment and rounding. Do not create inventory from a total that cannot be traced to usable lines.
Catch duplicates and avoid premature posting
Compare supplier, document reference, date and amount; use the original document to confirm a possible duplicate. If an invoice is already posted, stop and route for review. A cancelled draft may need a controlled re-creation path with the earlier reference retained. Keep the extracted record in draft until an authorized user confirms the proposed items and posting action.
Measure the work you save
Pilot a mix of clean invoices, handwritten notes and complex multi-page bills. Track elapsed time, review time, wrong fields and duplicates that escaped detection. Make a queue for ambiguous records and record why they failed. Improve the recurring errors first; a fast extraction that produces wrong stock or supplier balances saves little time overall.
Should OCR post purchases without review?
Start with reviewed drafts. Add automation only for well-tested cases with clear rules, audit evidence and a way to stop or correct errors.
