Mumbai · Delhi · Bengaluru · Pune · Kolkata
Engineering · sub-page 05 · back-office tool · AI

Bills come in every way.
One engine handles
them all.

Paper bill scanned. PDF emailed. Portal-uploaded. Couriered voucher photographed on a phone. The AP team should not care which channel it came through. AI Scan extracts the header and line items, matches them to the Work Order, drafts the RA Bill against certified work-done, and flags the discrepancies that protect your margin. Your back office reviews, approves — they don't re-key.

§ 01
The flow
Any source · same path · review-ready output

Capture. Extract.
Match. Draft.

Four stages from any inbound bill to a draft RA Bill ready for review. The first stage is channel-agnostic — the back office hits one button regardless of how the bill arrived. The last stage delivers a structured record linked to the right Work Order, with every discrepancy flagged.
▸ FROM ANY INBOUND CHANNEL · TO A REVIEW-READY DRAFT RA BILL ▸ ANY CHANNEL Paper bill · scanned PDF email attached Portal upload Phone photo 1 Capture single inbox whatever the source 2 Extract header + line items tax breakup · GST/TRN · TDS/WHT 3 Match to Work Order · vendor · WO line to certified Work Done 4 Draft draft RA Bill · review-ready flags surfaced · approval queue ▸ NOT JUST OCR · STRUCTURED EXTRACTION + WO LINKAGE + DISCREPANCY FLAGS REVIEWER ALWAYS IN CONTROL · NOTHING POSTS WITHOUT APPROVAL ▸ LIVES INSIDE BILL INWARD · NOT A SEPARATE INBOX
§ 02
The pillars
Three deep-dives · what AI Scan actually does

Capture. Match. Flag.

The capture stage is where channel-agnostic ingestion happens. The match stage is where AI Scan stops being an OCR tool and becomes useful — by linking the extracted bill to your Work Order, vendor, and certified work-done. The flag stage is where it protects your margin.
Pillar · 01 · Capture

Any source. One inbox.

The AP team works from a single queue. Paper bills scanned at the back office, PDFs forwarded from the vendor's email, photos from a site engineer's phone, files uploaded by contractors via the portal — all land in the same place. Vendor letterheads vary, formats vary, languages vary, even quality varies. The capture engine handles the noise so the team handles the substance.

Multi-formatPDF · scanned image · photo · portal upload
Auto rotation + de-skewPhone photos work · paper scans work
Multi-page handlingBill + supporting docs as one package
Vendor template learningLayouts get easier over time · tenant-private
CAPTURE QUEUE · TODAY · 24 BILLS PAPER 8 scans PDF 9 email PORTAL 5 upload PHONE 2 photo RECENT · ALL CHANNELS · ONE QUEUE Vendor B · WO-088 · civil frame paper · 4 pages · scanned 09:14 PAPER Vendor F · WO-091 · MEP PDF · email forward · 09:42 PDF Vendor M · equipment hire portal · 1 page · 10:08 PORTAL Vendor K · finishing phone photo · de-skewed · 11:21 PHOTO AUTO-PREP STATUS 75% extracted 6 pending ▸ VENDOR LAYOUT LEARNING · TENANT-PRIVATE Vendor B template · 38 bills · 99% extraction Vendor K template · 4 bills · 84% · improving ▸ MATCH STAGE NEXT
Pillar · 02 · Match

To the Work Order. To the work-done.

An OCR'd bill is just text on a screen. A matched bill is a record. The match stage links the extracted bill to the right vendor (by GSTIN/TRN, name, address), the right Work Order (by reference number or amount + scope inference), and the right certified Work Done (so the rate is known, the qty is validated, retention rules apply, escalation gets computed). This is where the bill becomes useful.

Vendor identificationGSTIN/TRN match · fallback to name+address
WO linkageWO number on bill · or amount+scope inference
Line-to-activityBill items mapped to BOQ activity rows
Work Done lookupCertified qty pulled · rate sourced from WO
MATCHING · RA-BILL DRAFT · VENDOR B Match confidence · 96% vendor B · WO-088 · 4 line items mapped ▸ VENDOR MATCH GSTIN 27AABCU9603R1ZX → Vendor B exact match · master record ▸ WORK ORDER MATCH "WO-088" on bill → WO-088 · civil frame open WO · vendor B · ₹ 38.4 Cr active ▸ LINE → BOQ ACTIVITY MAP "M30 concrete slab" → BOQ-2.18 98% ✓ "Reinforcement steel" → BOQ-2.21 99% ✓ "Misc. shuttering" → BOQ-2.34? 72% ▸ WORK DONE · CERTIFIED · PULLED 2,840 cum slab · DPR ✓ QC ✓ engineer ✓ rate from WO · retention 5% · escalation +9% ▸ FLAGS NEXT · WHERE THE MARGIN GETS PROTECTED
Pillar · 03 · Flag

The discrepancies that protect your margin.

This is where AI Scan stops being convenience and starts being defence. A vendor's bill with the rate ₹50/cum higher than the locked WO rate. A line item the WO never authorized. Retention not deducted. Escalation under-applied. GST/TDS computed wrong. The reviewer sees these flags before they approve — clearly, with the source highlighted on the bill image, with the expected value alongside the billed value. Approving a clean bill is one click. Approving a flagged bill needs a reason logged.

Rate varianceBill rate vs WO rate · per line item
Qty over-claimVs certified Work Done · per activity
Out-of-scope lineNo matching WO line · flagged for review
Tax + retention checkGST · TDS · retention · escalation · all reconciled
FLAGS · RA-BILL DRAFT · 5 ITEMS CLEAN 2 items REVIEW 2 items BLOCK 1 item FLAGS · MOST IMPORTANT FIRST ▸ Out-of-scope line "Misc shuttering" — no matching WO line ₹ 0.18 Cr ▸ Rate variance M30 concrete · billed 6,260 vs WO 6,180 +1.3% ▸ Retention not deducted 5% retention missing per WO term − ₹ 0.31 Cr ▸ Reinforcement · clean OK ✓ ▸ Escalation · clean OK ✓ Net margin protected · this bill if approved as-is vs after flag review ₹ 0.51 Cr ▸ REVIEWER SEES SOURCE · APPROVES OR REJECTS
§ 03
Where used
One engine · multiple Bill Inward inboxes

Same tool. Different desks.

Bill Inward is a transaction that exists in multiple modules — Engineering for contractor RA bills, Materials for vendor invoices, Sales & Customer Care for brokerage. AI Scan plugs into all of them. The capture queue, the matching logic, the flag-review pattern — same everywhere. Different teams, different vendors, same protection.
Engineering · this module

Contractor RA Bills

Civil contractor bills, MEP contractor bills, finishing contractor bills · matched to Work Orders · routed to billing engineer.

Materials & P2P

Vendor invoices

Material vendor bills · matched to Purchase Orders + GRN · routed to AP. Same engine, different match rules.

Sales & Customer Care

Brokerage Bill Inward

Channel partner brokerage invoices · matched to booked customers · routed to brokerage tracker.

Engineering Portal

Portal-routed bills

Bills uploaded by contractors via the portal flow into the same AI Scan queue · no separate inbox.

§ 04
Outcome
Why this is worth deploying

Less time. Less leakage.
More control.

AI Scan does not replace the AP team. It replaces the data-entry portion of their job. The judgment portion — what to approve, what to reject, what to investigate — stays with them. They just get to spend more time on it.
▸ The case for the back office

From typing bills
to reviewing exceptions.

90% Of bill data extracted without re-entry
Faster cycle from inbox to AP-ready
100% Audit trail · source bill image kept · flag history
§ 05
Related
Other Engineering sub-pages

Where to go next.

AI Scan is the back-office tool. The Contractor Portal is one of its input channels. Project Engineering owns the Work Orders and Work Done that AI Scan matches against. BIM Revit BOQ is the other AI tool in the Engineering family.
My AP team used to fight at month-end. Bills piling up, vendors calling for status, errors caught only after payment went out. Now the bill enters the queue however it arrives — paper, email, portal. AI Scan does the typing. The team does the thinking. We close books on day four instead of day eleven.
— Finance Controller · Indian developer · 18 active projects
Next step

See AI Scan
on a real bill.

30 minutes. We'll take a real contractor bill from your stack — paper, PDF, anything — drop it into AI Scan, walk through extraction, matching, and flag review. You'll see what your team would actually do with this on day one.