How expense reimbursement is set up in finance and ERP systems

Expense reimbursement usually runs in an expense tool linked to the ERP. Employees submit claims, policy rules and approval limits are enforced on entry, approved claims post to the general ledger, and payment goes out through the accounts payable or payroll run, with each employee treated as a payee.

Policy as configuration

The written policy sits in a document somewhere on the intranet. The version that actually governs behavior is the one built into the tool. That includes the expense types, the per diem and mileage rates, the point at which a receipt becomes mandatory and the spending limits for each grade or cost center. The document and the configuration drift apart over time.

Each expense type maps to a general ledger account and often to a default tax code. A badly designed category list causes miscoding long after anyone remembers why it was built that way. Limits are typically held in a delegation of authority table. Sometimes it lives in the ERP and sometimes in the expense tool. Occasionally it lives in both, with different values.

Policy is communicated at onboarding and then mostly through rejection messages. Warnings that appear while someone is entering a claim shape behavior far more than any announcement does.

Tax data at the point of capture

Receipts are photographed or forwarded by email. Character recognition reads the merchant, date, amount and tax. Recoverable sales tax or VAT depends on a valid receipt showing the supplier's tax registration. Without one, the claim may still be paid, but the input tax cannot be reclaimed. Foreign spend carries local tax that is sometimes recoverable through separate refund schemes.

Some reimbursements count as taxable benefits to the employee. Certain meals do, and so does mileage paid above the statutory rate. These amounts must flow to payroll reporting. Setup therefore means agreeing which expense types are benefits and which tax codes apply by default. Many organizations set mileage and per diem rates at the statutory allowance so nothing becomes taxable by surprise.

Routing claims for sign off

Claims go to the line manager first. They escalate to further approvers when the amount crosses a threshold or when the claim contains sensitive categories such as entertainment or gifts. Finance often adds an audit step for flagged or sampled claims.

Routing reads reporting lines from the HR system. When those lines are stale, claims land with people who have left. Cover for absent managers is a common gap. Advances need sign off too, usually under tighter rules, because cash leaves the business before anything has been spent.

Paying and posting

An approved claim becomes a payable. Two patterns dominate. In the first, each employee has a supplier record in accounts payable and is paid in the normal payment run. In the second, approved amounts are exported to payroll and paid with salary. The payroll route simplifies bank details and benefit reporting, but it ties reimbursement timing to the pay cycle.

Posting is often summarized into one journal per batch. That keeps the ledger tidy and makes tracing back to a single receipt harder. Corporate card transactions arrive through a bank feed and are matched to claims. The business pays the card issuer directly, and the employee only has to substantiate the spend.

Employee balances and advances

Every employee effectively carries a personal account with the business. It holds open advances and card charges still awaiting receipts. It also holds any personal spend on a company card that must be repaid. Advances should be netted against later claims. Personal card spend is recovered by payroll deduction or by direct repayment.

These balances age quietly. When someone leaves, anything outstanding has to be settled before final pay. That only works if the HR leaver process triggers a check in finance. Reconciling the employee clearing account in the ledger to the open items in the expense tool is the control that catches most breaks.

Questions to ask the people who run it

• Which limits does the system block, and which depend on approvers knowing the policy?
• When a receipt is missing, what really happens? Is there a signed declaration, or does the claim get paid anyway?
• Who corrects miscoded expense types, and do those corrections ever reach the category setup?
• What happens to a claim when the approver has left or is on leave?
• Are advances ever written off, and who makes that call?
• Does anyone reconcile the employee clearing account, and what sits in it that nobody can explain?
• Which claims are paid outside the tool, through manual payments or petty cash, and why?
• How does finance find out that someone is leaving?
• Are taxable benefits from expenses actually reaching payroll, or are they reviewed only at year end?

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.