Invoice OCR
Supplier, tax number, dates, line items and totals — with the arithmetic checked, so a total that does not match its lines is flagged rather than delivered.
- Line items
- Tax number
- Totals reconciled
- Multi-currency
SLT OCR · a Smart Lead Tech product
An Arabic-first computer-vision engine for document process automation: invoices, purchase orders, receipts, passports, identity cards, KYC packs, and mixed multi-page PDFs. Every field has its own verification model, and values that cannot be verified are routed to human review rather than delivered as fact.
Built for Arabic
Arabic is not a language you bolt on at the end. Right-to-left layout, letters that change shape with position, Arabic-Indic numerals, and handwriting that varies by governorate all break engines designed around Latin script. SLT OCR was trained on Arabic documents from the start, on real archives rather than synthetic text.
How it works
Each page is classified by type before anything is extracted, so an identity card is never processed as an invoice. Pages that do not fit a known type are flagged rather than forced.
Fields are resolved by dedicated models in dependency order — the identity number is parsed and checksummed before the values derived from it are trusted.
Structural checks, cross-field agreement and confidence thresholds decide whether a value ships. Anything below the bar goes to a human queue with its evidence attached.
Ready-made solutions
Each pipeline is trained for one document family and ships with its own validation rules. Start with the one that matches your backlog.
Supplier, tax number, dates, line items and totals — with the arithmetic checked, so a total that does not match its lines is flagged rather than delivered.
Front and rear of the same card are recognised as one person and merged into a single complete record. The number is checksum-validated and the derived fields cross-checked against it.
The machine-readable zone is read and its check digits verified arithmetically, then reconciled against the printed page. A mismatch is a review item, not a silent choice.
Order numbers, quantities and delivery terms lifted from supplier paperwork and matched against the order they belong to.
Photographed, folded and faded receipts — merchant, date, tax and total, from the awkward originals people actually submit.
A folder of mixed identity evidence resolved into one verified customer profile, with every field traced back to the page it came from.
A scanned PDF with no structure goes in; the same PDF comes out with a bookmark tree naming each document inside it. Pages need not be in order.
Rows, columns and merged cells recovered from scanned tables, including the ruled Arabic forms that defeat generic layout models.
Skewed camera captures, low-contrast photocopies and stamped pages — deskewed, cleaned and read.
Where it is used
Citizen records, archives and licence files digitised without leaving the premises.
Contract archives, meter records and customer files at box-by-box scale.
KYC packs, statements and onboarding evidence with a traceable audit trail.
Patient forms and insurance paperwork, processed without documents leaving the network.
Deeds, contracts and case bundles made searchable and correctly bookmarked.
Delivery notes, customs paperwork and proof-of-delivery captured at the depot.
Why SLT OCR
Cloud, or fully on-premises with no outbound connection. The on-premises build works air-gapped.
Uploads are processed in memory and results expire automatically. There is no document store to breach.
Every field carries a confidence and its evidence. Low-confidence values are labelled, never quietly guessed.
Trained on real Arabic archives, not translated Latin corpora.
Fragments of the same identity across several files are merged, so counts are correct.
Accuracy figures state the input they were measured on. Where a scenario is weaker, we say so.
Try it
Upload a document and see the extracted fields, their confidence, and what would have gone to review. Trial processing is rate-limited and results are erased automatically.
Contact
Tell us your document volumes and whether you need an on-premises installation. We will reply with packaging and a deployment plan.