AI document processing in Pakistan: what it automates, and what it costs

AI document processing in Pakistan means software that reads the paper your business already receives — supplier invoices, CNIC copies, bank statements, referral letters, claim forms — pulls out the fields that matter and routes each document to the right place, with a person checking only the cases the model is unsure about. A focused project starts from $15,000 and takes six to sixteen weeks. Whether it pays for itself depends less on which model you use than on three decisions most vendors skip.

We built this for a healthcare network that was receiving thousands of referral letters a week as scans, faxes and email PDFs. Today about 81% of referrals are routed without a person reading them first, and median time to triage has gone from days to hours. The full case study is here. What follows is what that project, and the ones since, taught us.

What it is good at, and what it is not

Good candidates share three traits: there are a lot of them, they come in a handful of recognisable layouts, and each one leads to a clear next action. In Pakistani businesses those are usually:

• Supplier invoices and delivery challans — vendor, NTN, line items and tax, matched against the purchase order before anyone keys them in.
• CNIC copies and onboarding forms — name, number and dates, with a check that the number is well formed and the card has not expired.
• Bank statements for lending decisions — transactions categorised, salary credits found, returned cheques flagged.
• Referral letters, lab reports and insurance claims — specialty, urgency and patient identifiers.
• Shipping and customs paperwork — consignee, weights and HS codes, checked against the commercial invoice.

Poor candidates are documents that arrive a few times a week, where one clerk is already quick; decisions that need judgement nobody could write down; and anything where a mistake cannot be undone and nobody wants to check the output. Automating those adds a system without removing any work.

Urdu, stamps and the photo taken at an angle

Pakistani paperwork is harder than the demos. Urdu and English on the same page, a rubber stamp across the total, carbon copies, and WhatsApp photos taken under a tube light at thirty degrees. Text-recognition engines that score well on clean English PDFs fall over on exactly the documents you most want to automate.

What works is unglamorous. Straighten, crop and clean the image before reading it. Choose the recognition engine per document type rather than one for everything. Let a language model read the recognised text in context instead of relying on fields sitting in fixed positions. And test on your own worst two hundred documents, not on a vendor's sample set. Printed Urdu is now readable by the better engines; handwritten Urdu still is not reliable, and if your documents depend on it we will say so in the first fortnight rather than in month four.

The threshold matters more than the model

Every model is wrong some of the time. The design question is what happens when it is. We set a calibrated confidence threshold: above it, the document flows straight through; below it, it goes to a person who sees the extracted fields beside the original page and corrects them in one click.

That one decision is what gets a project past an audit committee or a clinical governance board, and it is what makes the system improve. Every correction becomes labelled data for the next week's evaluation. A vendor promising 99% accuracy with no review queue is describing a demo, not a system you can put your name to.

What it costs

• One document type, one integration and a review screen: from $15,000, six to ten weeks.
• Several document families, an approval workflow and two or three integrations — an ERP, a core banking system, a patient record: ten to sixteen weeks, priced after discovery.
• Running costs: recognition and model usage are billed per page. At most mid-sized volumes this is small next to the hours it frees, but it belongs in the business case, and we estimate it from your real volumes rather than a brochure.

Every project starts with a two-week discovery sprint from $3,500. We take a sample of your real documents, measure the accuracy that is actually achievable on them, and give you a fixed price — or tell you the project is not worth doing yet.

Where the data goes

These documents carry CNIC numbers, medical histories and bank balances. Decide early which model providers are acceptable, whether data may leave Pakistan, and how long anything is kept. The options run from hosted models under enterprise terms that exclude training on your data, through models deployed in a cloud region you choose, to open models on your own servers — which costs some accuracy and more maintenance, and is sometimes the right trade. Whatever you choose, keep an audit trail of every model output and every human override.

How to know it worked

Measure before anything is built: documents per day, minutes per document, the age of the oldest item in the backlog, and the error rate in the system the data ends up in. Measure the same things afterwards. Our healthcare client reported results as the share of referrals routed without a first read and the median time to triage — numbers their own team tracked, not ones we chose for them.

If a team in your business re-types the same kind of paper every day, our AI and machine learning team can tell you within two weeks whether it is worth automating. If it is not, we will say that too.