Employee expense reimbursement is where finance discipline quietly breaks down. ERPNext ships a solid Expense Claim DocType with an Expense Approver and a link to Employee Advance, but out of the box it assumes staff will hand-type each line, attach a photo separately, and trust that everyone remembers the per-meal cap and the mileage rate. There is no OCR, no automatic policy-limit enforcement per expense category, no structured per-diem or mileage calculator, and only a single approval hop. Finance ends up policing spend in spreadsheets and email, receipts go missing, and month-end reimbursement runs are a manual reconciliation slog.

Expense Claim & Reimbursement Pro is a proper Frappe app — its own module, DocTypes, and hooks.py — installed onto your existing ERPNext site rather than bolted on as a hosted add-on. Employees capture a receipt from the mobile browser or a Frappe-based PWA; the image is attached as a File, queued to a background OCR job (Tesseract or a pluggable cloud vision provider) via frappe.enqueue, and the extracted vendor, date, tax, and amount pre-fill the claim line for the employee to confirm. A Expense Policy DocType holds per-category limits, receipt-required thresholds, and rates; a validate server-side hook checks every claim line against the matching policy and either blocks submission or flags a Policy Violation child row that the approver sees in context. Mileage and per-diem are computed by whitelisted methods (@frappe.whitelist) from distance/day inputs and configurable rates, so the numbers are consistent and auditable rather than guessed.

Approval is driven by Frappe's native Workflow engine plus role profiles, so you get true multi-level routing — for example line manager, then department head above a threshold, then finance — with state transitions, conditions, and email/mobile notifications. Permissions use standard ERPNext roles and permission levels so an approver sees their team's claims and finance sees the queue, with nothing leaking across departments. On final approval, a on_update/on_submit doc event creates the downstream posting: either a reimbursement line fed into the employee's next Salary Slip component through Payroll, or a Journal Entry / Purchase Invoice against accounts payable for a direct bank payout — you choose the route per company or per employee. Everything is exposed over the standard Frappe REST API and whitelisted methods, so a companion mobile app or your own dashboards read and write the same records.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your expense categories, policy rules, approval hierarchy, payout route (payroll vs AP), and OCR provider, then build and configure the app against your ERPNext v15 or v16 site. We deliver the installable source, run UAT on a staging bench with a rollback plan, hand over the git repository, and support you through go-live. Typical delivery is one working week from confirmed scope — no marketplace download, no fabricated feature list, just a maintainable app your team owns.