Expense Management with Receipt OCR

Expense management in Dynamics 365 Finance & Operations has the right bones. Expense reports, expense categories, the policy framework, per diem rules, cash advances, project and sales-tax integration, workflow approval and posting to vendor invoices or the general journal all exist and all work. What it lacks is the part employees actually touch: capture.

So the process degrades in a predictable way. Someone photographs a receipt on their phone, emails it to themselves, and three weeks later sits down to type merchant, date, amount, currency and tax into TrvExpTrans line by line. Card transactions import cleanly into the environment but sit unmatched, because matching an imported card line to a receipt that only exists as a phone photo is manual work nobody schedules. Per diem gets claimed for days where lunch was provided. Mileage is entered as a round number. Policy violations are caught by an approver reading a report rather than by the system refusing the line. And finance closes the month with a pile of unreconciled card transactions and a set of expense reports that arrive after the period they belong to.

The expense module is not broken. The distance between a receipt in someone's hand and a validated line in TrvExpTrans is what is broken, and that is the gap this app closes.

What ECOSIRE builds

An X++ extension plus a Power Platform capture layer, both delivered as source. Standard expense objects are extended, never overlayered.

Receipt capture and OCR

The employee photographs a receipt in a Power Apps canvas app - or forwards it to a monitored mailbox, or drops a PDF into the expense report. The image is stored as a document attachment against the expense line through document management, so the original is always one click from the approver and from the auditor. Extraction runs against an Azure AI document-processing service in your own Azure subscription, under your own tenant and your own data residency, and returns merchant, date, gross amount, currency, tax amount and tax registration number. Those values pre-fill the expense line; every one of them stays editable, and the extracted values are stored alongside the final values so you can see what was changed and by whom. We are explicit about this: OCR is a pre-fill, not an authority. Extraction quality depends on receipt quality, and thermal-paper receipts photographed badly will need correction.

Card feeds and matching

Card transactions come in through the standard credit-card transaction import, on a scheduled batch job in the SysOperation framework rather than a manual click. The app adds the matching engine on top: candidate matching on amount, date window, currency and merchant name, with configurable tolerances, and a review screen showing unmatched card lines and unmatched receipts side by side. Matched pairs create the expense line automatically. Unmatched card lines age, and an ageing batch notifies the cardholder and then the cardholder's manager before finance has to chase anyone by email.

Policy, per diem and mileage

The standard F&O policy framework already blocks and warns on category limits. The app extends it with rule types Gulf and regional finance teams keep asking for: receipt mandatory above a threshold that varies by category and by legal entity, duplicate detection across all reports for the same worker and amount and date, spend concentrated with a single merchant, weekend or public-holiday spend on a category that should not have it, and a hard block on a report submitted for a closed period. Per diem builds on the standard per diem rules with automatic reduction where a provided meal or hotel breakfast is flagged on the itinerary, and partial-day proration by departure and return time. Mileage supports tiered rates by cumulative distance per worker per year, per vehicle class, with distance either entered or captured from start and end addresses in the mobile app.

Approval and posting

Approval keeps using the F&O workflow framework, so your existing hierarchy, delegation and escalation stay. What the app adds is what the approver sees: the receipt image next to the line, a plain-language list of policy findings, and the ability to reject a single line and return only that line rather than bouncing the whole report. Posting is unchanged - vendor invoice or general journal, project expense lines against ProjTable where the report is project-bound, sales-tax recovery through the standard tax engine, and ledger dimensions defaulted from the worker's position and overridable per line.

Integration and data

Every object the app adds is exposed as a data entity for the data management framework and OData: capture records, OCR extraction results, match candidates, policy findings and mileage tiers. Business events fire on submission, approval, rejection and match failure so you can drive notifications from Power Automate without polling. Dual-write keeps the mobile app in step with Dataverse.

Who it is for

Organisations already live on expense management in Dynamics 365 Finance & Operations with a travelling or field workforce, corporate cards in circulation, and a month-end that is regularly held up by late or unreconciled expenses. Typical buyers are the shared services or accounts payable lead, the financial controller, and the internal audit function that has to sample receipts.

How delivery works

1. Scoping call. Your current expense category and policy setup, card providers and file formats, per diem and mileage policy, project integration, tax recovery rules, and which mobile platform your workforce actually uses. 2. Fixed quote. Written scope, fixed price, lead time - typically one working week from acceptance. 3. Build. X++ extension and Power Apps canvas app developed against a copy of your configuration. 4. Install in test. Deployable package into your sandbox through LCS, Power Platform solution into your test environment, OCR service wired to your Azure subscription. You test with real receipts and a real card file. 5. Production. Deployment in your change window, with a pilot group before full rollout. 6. Support. A defect-correction window after go-live, plus a written handover so your team owns the code.

Honest limits

OCR is probabilistic. We will tune it against a sample of your real receipts during the build and tell you what accuracy looks like on your own documents rather than quoting a number here. Azure AI consumption, Power Platform licences and card-provider file access are your costs and your contracts. Handwritten receipts, faded thermal paper and multi-page hotel folios need human review, and the app is designed on the assumption that they will get it.