Expense Report

Expense Report is a formal document submitted by an employee to request reimbursement for business-related spending, including itemized expenses, receipts, dates, and business justification. For US federal tax purposes the substantiation rules in Treasury Regulation 1.274-5 allow employers to waive receipts for expenses under 75 dollars, other than lodging.

Category: Expense Management SoftwareBest Expense Management Software

Finance closed the month with $40K in employee expenses still unsubmitted. The reimbursements hadn't been processed, the accruals hadn't been posted, and the department P&Ls were understated. Meanwhile, 14 employees were still waiting to be reimbursed for a trip six weeks earlier. The expense report process worked on paper; nobody was enforcing it. An expense report is a formal record of business costs an employee has incurred, which the company must review, approve and reimburse. It captures the who, what, when, where and why of each spend, along with supporting documents such as receipts, and it is the source record for posting the expense to the general ledger. Expense reports are how employee-initiated spending gets into the accounting system. Until a report is submitted and approved, the cost doesn't exist in the books. For finance, late submissions cause more than reimbursement delays: they produce an inaccurate close, understated department costs, and accrual estimates made under pressure at month-end.

How expense reports work

An expense report goes through several steps before a reimbursement is issued and an accounting entry is posted. The employee incurs a cost, captures documentation (usually a receipt), categorizes the expense, assigns it to the right cost center or project, and submits it for approval. The approver, usually a direct manager, checks the report for business purpose, policy compliance and complete documentation before approving. Finance then reviews the approved report, confirms coding, and pays the reimbursement through payroll or AP. The last step is posting the journal entry: a debit to the relevant expense account and a credit to the liability or cash account used for reimbursement. The failure points are predictable. Employees submit late because the process is manual or inconvenient. Managers approve without reading because they lack time or context. Finance finds coding errors after the fact, or closes the month on accrual estimates because the actuals aren't in. Late submissions feed straight into inaccurate P&Ls, and when a late batch does arrive, the pressure to process it quickly usually means fewer compliance checks and more coding errors than if the work had been spread across the period.

Receipt capture, card matching

Expense reports use one of two documentation models: receipt-based or card-transaction-based. In a receipt-based process, the employee submits a receipt for each expense, and finance verifies that it matches the claimed amount and qualifies under policy. In a card-transaction-based process, the spend is captured when the card is swiped, and the employee's job is to attach a receipt and add GL coding rather than enter the transaction. The card model reduces the risk of fraudulent or inflated claims but doesn't solve the documentation problem. If a cardholder never matches receipts to card transactions, finance has spending data with no GL coding and no business purpose, which isn't enough to post. Approval routing does more than authorize. Good workflows route by cost center owner, project budget holder or spend amount, so a $50 meal goes to a line manager while an $8,000 international travel report also gets a finance review before reimbursement. When routing is flat (every report goes to the same manager regardless of amount or type), approval becomes a rubber stamp instead of a control. The close impact is direct: every unsubmitted expense at period-end is either an understated cost or an accrual estimate that will have to reverse when the actuals arrive.

How platforms handle it

Most expense management platforms demo well on the clean path: employee submits, manager approves, the system syncs to the ERP, and the reimbursement posts. What matters is what happens off that path. If a report is submitted 45 days after the trip, does the system flag it or let it through? If a receipt is missing, can the approver still approve, or is the report blocked until documentation is attached? If an expense is coded to a cost center the approver doesn't own, does routing change, or does the wrong manager approve it? Ask the vendor to walk through each case. Test the accounting sync as well: does the platform post individual line items or summary entries to the ERP? Line-item posting gives better GL detail at higher volume; summary posting is easier to reconcile but loses granularity. Confirm whether the ERP sync is real-time or batch, and how reconciliation works when a sync fails partway through. For multi-entity companies, ask how the platform handles intercompany expense allocation, where an employee in one entity incurs costs that belong to a project owned by another.

Questions to ask

Does the platform enforce a submission deadline, and can it send automated reminders to employees with open, unsubmitted expenses before close?
Can approval routing be configured by cost center, expense category and amount threshold, or is it a flat one-level approval?
How does the system handle missing receipts: soft warning, hard block, or escalation to a separate review queue?
What is the ERP sync cadence (real-time, daily batch, or manual), and how are errors handled when a sync fails?
Does the platform provide a close-readiness view showing outstanding, unsubmitted, or unapproved reports by department as of the period cutoff?
How are intercompany expense allocations handled when an employee's home entity differs from the project or cost center being charged?

Common mistakes

The first mistake is not enforcing submission deadlines. Most companies have a stated policy, such as submit within 30 days or within two weeks of travel, but nothing that enforces it. Without enforcement, submissions pile up, employees get used to filing late, and finance either accrues estimates it will have to reverse or closes months with understated expenses. The fix has two parts: a clear cutoff date communicated before each close, and automated reminders sent when open expenses are still unsubmitted a set number of days before that cutoff. The second mistake is letting reports pile up before close and then rushing approvals to hit the deadline. When 30 reports land in a manager's queue on the last day of the period, approval becomes a formality with no time to check policy compliance or coding. Finance then inherits the coding errors when GL entries don't match department budgets. The structural fix is continuous processing: approvals should happen within a few days of submission, not in a bulk batch at close.

Comparing expense tools

Expense tools separate on whether policy is enforced at the point of spend or checked afterwards by whoever reviews the report. Once expense report is settled as a requirement, read the Expense Management Software category guide for how the market splits, then weigh the Airbase profile against the Tipalti profile on that requirement rather than on the feature list. Our Airbase pricing breakdown records what the vendor publishes and what is quote-based. The Tipalti against Airbase comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the expense management savings calculator so the business case is written down before a vendor writes it for you.

Expense Report questions

How is an expense report different from a corporate card reconciliation?

An expense report is an employee-initiated submission documenting out-of-pocket spending that needs to be reimbursed. A corporate card reconciliation matches card transactions, which the company has already funded, to receipts and GL codes. With an expense report, the employee is owed money. With a card reconciliation, the money is already spent and the work is documentation and coding. Some companies run both through the same expense report process, but they are structurally different: expense reports create a reimbursement liability, while card reconciliations are a coding and documentation exercise on spend that's already on the books.

What should finance do when an expense report is submitted after the close cutoff?

The options are to post the late expense in the current period (adjusting a prior period) or to post it in the period it was incurred (reopening or adjusting). Most finance teams post late submissions in the current period if the amount is immaterial, and flag material late submissions for a prior-period adjustment. The better upstream fix is an accrual process: if finance knows a trip occurred in March but the report hasn't been submitted, they should accrue the estimated cost in March and reverse it when the actual report comes in. This keeps the P&L accurate even when submission timing is imperfect.

How should expense report coding be validated before the report reaches the GL?

At minimum, the expense management platform should validate that the selected cost center and account code combination is active and correctly mapped in the chart of accounts. More advanced validation checks whether the employee is authorized to charge the selected cost center, whether the expense category matches the GL account (e.g., a 'meal' expense isn't coded to a capital account), and whether the spend is within budget for the period. Some platforms integrate with the ERP budget module to flag over-budget submissions before approval, rather than surfacing the issue after the fact.

What is the 75 dollar receipt rule?

Treasury Regulation 1.274-5 lets an employer accept a claim without a receipt for most expenses below 75 dollars, with lodging excluded. Many companies set a lower internal threshold anyway, because the rule sets the tax floor rather than the policy. The expense record still has to show amount, date, place and business purpose.

Corporate Card Reconciliation, Expense Policy Compliance, and Mileage Reimbursement come up in the same workflow as expense report, and the rest of the expense tools cluster is indexed in the finance operations glossary.