Most travel and expense programs are assembled from a template. A submission window, a receipt threshold and a lodging cap arrive already filled in, and finance inherits numbers whose origin nobody can name. Those numbers are not arbitrary in principle. Some decide whether a reimbursement stays out of an employee’s taxable wages, and the rules that set them are published and specific.
This guide is for a controller or finance operations lead who owns the travel and expense operating model with procurement, payroll and tax input. It covers policy, booking channel, cards, substantiation, approvals, reimbursement, tax treatment, integration boundaries and the product categories available. It does not rank vendors, quote pricing or advise travelers on booking. The aim is to separate the thresholds a company may choose from those a tax authority has already set.
The tax sections below use published rules as control inputs, not as a determination for a particular employee or payment. Facts such as business purpose, travel status, allowance design, employing entity and local payroll treatment still have to be resolved by the organisation’s payroll or tax owner; the system’s job is to preserve the evidence and approved classification.
Quick answer
A design that meets the accountable plan requirements keeps reimbursements outside taxable wages, while a failure of business connection, substantiation or return of excess can convert every amount paid under the arrangement into reportable pay.
Decision: Approve a travel and expense operating model only when each policy threshold is identified as a company choice or a tax requirement, substantiation and return-of-excess deadlines sit inside a named safe harbor, and every process object has one authoritative system and one accountable owner.
Key takeaways
- Set the substantiation deadline from the accountable plan safe harbors rather than a template: 60 days to substantiate an expense and 120 days to return an unspent advance.
- An arrangement-level failure of business connection, substantiation or return-of-excess rules makes all payments nonaccountable; if an otherwise compliant plan has one employee fail to return excess, only that excess falls outside it.
- Federal per diem rates govern federal travelers on official travel; a company that adopts them is making a policy choice and still owns the tax outcome.
- Spend that never enters the managed booking channel cannot be policy-checked before commitment and arrives too late to control.
- Decide which system is authoritative for the expense record, the card transaction and the ledger entry before comparing products.
What travel and expense management covers
Travel and expense management is the set of policies, controls and systems governing costs employees incur on behalf of the business, from the decision to travel through booking, payment, substantiation, approval, reimbursement and accounting. It is a spend channel rather than a product category. Its defining feature is that an individual employee commits at the point of purchase, often while traveling, rather than a purchasing function committing against a supplier contract.
That difference sets the control problem. A purchase order authorizes the commitment before money moves; in travel and expense the money has usually already moved, so the available controls are those applied before booking, at payment, and at claim.
| Spend channel | How the commitment is made | Primary control point | What it should not be assumed to own |
|---|---|---|---|
| Travel and expense | An employee commits at the point of purchase, frequently mid-trip | Policy applied at booking and again at claim | Supplier contracting, sourcing or purchase-order-backed goods and services |
| Purchase-order-backed procurement | An approved requisition and order precede the commitment | Approval before the commitment exists | Employee out-of-pocket spend and substantiation rules |
| Non-purchase-order supplier invoice | A supplier invoices without a prior order | Coding and approval at invoice receipt | Per diem treatment, mileage and employee reimbursement |
| Corporate card program outside travel | A cardholder commits within an assigned limit | Card limit, merchant category control and review | Trip authorization and traveler duty of care |
Travel and expense is the largest category most organizations run without a purchase order, so it belongs inside the wider source-to-pay control model as a defined exception route rather than an unclassified remainder.
Build the policy from the tax rules, not a template
A published template can supply structure. It cannot tell a company which of its numbers are discretionary. In the United States the controlling rule is the accountable plan test in 26 CFR 1.62-2, which sets three requirements: business connection, substantiation, and returning amounts in excess of substantiated expenses.
The consequence of failing them is not proportionate. Under 1.62-2(c)(3)(i), an arrangement that does not satisfy one or more of the three requirements means all amounts paid under it are treated as paid under a nonaccountable plan. One failure is narrower: under 1.62-2(c)(2)(ii), where the arrangement otherwise qualifies but an employee does not return excess within a reasonable period, only the amounts above substantiated expenses fall outside the plan. A design defect and a collection failure carry very different exposure.
Substantiation deadlines that hold
Published policy guidance commonly specifies a 30-day submission window without naming an authority. The regulation instead provides two safe harbors. The fixed date method in 1.62-2(g)(2)(i) treats as reasonable an advance made within 30 days of when an expense is paid or incurred, substantiation within 60 days, and return of an unspent amount within 120 days. The periodic statement method in 1.62-2(g)(2)(ii) allows quarterly or more frequent statements of unsubstantiated amounts, with 120 days from the statement to substantiate or return.
A 30-day window is therefore permissible and tighter than the safe harbor, which is a defensible choice. What is not defensible is a policy with no stated deadline, or one applied inconsistently. The regulation also removes both safe harbors where a payor has a practice of over-reimbursing employees and avoiding reporting, so tolerated exceptions are a program risk rather than an administrative one.
Receipt thresholds are two different numbers
Company policy thresholds and the tax substantiation threshold are separate. IRS Publication 463 lists an exception to the documentary-evidence requirement where an expense other than lodging is less than $75, and its sample record instructs travelers to attach receipted bills for all lodging and any other expense of $75.00 or more. Lodging always requires documentary evidence regardless of amount. Publication 463 treats evidence as adequate if it shows the amount, date, place and essential character of the expense.
Many published policies set a receipt threshold well below $75. That is a control decision about audit evidence, not a tax requirement, and should be recorded as such so a later reviewer does not mistake an internal preference for a statutory floor.
Per diem, mileage and the federal rate question
For fiscal year 2026 the General Services Administration set the standard continental United States rate at $110 for lodging and $68 for meals and incidental expenses, with M&IE tiers running from $68 to $92 and no new non-standard areas added. Per Diem Bulletin FTR 26-01, issued 31 July 2025, applies from 1 October 2025 through 30 September 2026.
Private-sector adoption of those rates is a policy choice. GSA states in its per diem guidance that it sets per diem rates and related policies for federal travelers on official travel only. A company may use the federal figures as a reference, but that transfers no part of the tax analysis to GSA.
Two mechanics in the Federal Travel Regulation subsistence rules answer questions that recur in internal reviews, even where a company writes its own policy. Under 41 CFR 301-11.20, travel of more than 12 but less than 24 hours attracts 75 percent of the applicable M&IE rate, and the same 75 percent applies on the first and last day of longer travel. Under 41 CFR 301-11.17, an employee may request actual expenses up to 300 percent of the per diem rate, and the regulation states there is no authority to exceed that ceiling.
For personal-vehicle use the Internal Revenue Service set the 2026 business standard mileage rate at 72.5 cents per mile from 1 January 2026, up 2.5 cents, in news release IR-2025-128. Use of the standard rate is optional. Every rate here is dated: FY2027 per diem figures take effect on 1 October 2026, so a policy that hard-codes a dollar amount needs an owner and a review date.
How Australia treats the same allowance
A company operating an Australian entity cannot reuse the United States analysis. The Australian Taxation Office publishes reasonable amounts annually, and for the 2026-27 income year Taxation Determination TD 2026/4 sets them by destination and by three salary bands: $153,210 or less, $153,211 to $272,680, and $272,681 or more. The reasonable amount for overtime meal expenses is $40.
Two features differ sharply from per diem practice. First, the reasonable amounts operate as a substantiation exception rather than a cap, and the exception is lost on the whole claim if exceeded. TD 2026/4 states that an employee claiming more than the reasonable amount must fully substantiate the expenditure, not just the amount over it. Second, the accommodation figure applies only to short stays in commercial establishments such as hotels and serviced apartments, and cannot be used for other accommodation types even where an allowance was paid.
The reasonable-amount tables do not by themselves decide whether an allowance is assessable, deductible or subject to fringe benefits tax. The Australian entity should classify the payment from its actual facts and keep that conclusion separate from the software rule that checks an amount against a table.
The employer-side classification also differs. ATO guidance on living-away-from-home allowance fringe benefits states that an allowance paid for travelling for work is a travel allowance, assessable to the employee and not subject to fringe benefits tax, while a living-away-from-home allowance is a fringe benefit with its own taxable value, declaration requirements and concessions. Long assignments separate the two, so assignment duration belongs in the policy as a classification trigger.
Treat the booking channel as a control
Booking is the last point at which a commitment can be prevented rather than reviewed. A managed channel, whether a self-booking tool, a travel management company or both, applies class rules, advance-purchase rules, preferred suppliers and trip approval before money moves. It also records who is traveling where, which is the operating basis for duty of care.
Spend booked outside that channel is not merely a preference lost. It arrives as a card transaction or a claim after the fact, with no pre-commitment check, no itinerary record and often a merchant name that does not identify the supplier. This is why travel and card spend is a recurring gap in consolidated analysis, as the spend data-readiness framework sets out in its treatment of off-system spend.
The useful measure is therefore not policy compliance among claims already submitted, which is calculated on a population that has already been filtered. It is the share of eligible travel spend that entered the managed channel at all.
Cards, capture and the reconciliation contract
The payment instrument decides who carries the exposure and what has to be reconciled. Four arrangements are common, and they are not interchangeable.
| Arrangement | Who is liable to the issuer | Reconciliation obligation | Main control risk |
|---|---|---|---|
| Corporate liability card | The company | Match every posted transaction to a substantiated expense and a ledger code | Transactions settle whether or not they are ever substantiated |
| Individual liability card | The employee | Match reimbursement to substantiated expense; the card balance is not a company payable | Employee credit exposure and delayed submission |
| Personal funds and reimbursement | The employee | Substantiate before payment; no external feed exists to reconcile against | No independent transaction evidence beyond the receipt |
| Virtual or single-use card | The company | Match the issued authorization to the booking and the settled amount | Unused or partially used authorizations left open |
A corporate liability program creates an obligation a reimbursement program does not: the company owes the issuer on the statement date whether or not the cardholder has submitted anything. Unsubstantiated card spend is a live accounting item, not a pending administrative task, and needs an accrual basis and an aging owner.
Automated capture reduces keying, and its matching, exception and approval mechanics resemble those in accounts payable, where the same questions about confidence thresholds and exception ownership arise. The invoice capture and exception model is a useful reference for what an automated match should conclude on its own.
Approvals that are controls, not signatures
An approval adds control only when the approver has the authority, the information and the incentive to refuse. Three design decisions determine whether that is true.
The first is sequence. Pre-trip approval governs whether a commitment should be made and is the only approval that can prevent spend. Post-trip approval governs whether a claim is payable and correctly coded. A program that has only the second has review but no prevention.
The second is authority. Approval limits should follow a delegation-of-authority schedule tied to role and amount rather than defaulting to the reporting hierarchy, and the schedule needs a named owner and a change history. The same budget and delegation questions arise when specifying intake systems, and the treatment in the requisition control-led buyer guide transfers directly.
The third is independence. No one should approve a claim from which they benefit, approve a delegate’s claim where the delegation is reciprocal, or hold both approval and payment release. Where full separation is impractical in a small entity, the compensating control and its owner should be documented rather than assumed.
Review depth should follow risk rather than a fixed percentage. High-value claims, claims from approvers, claims sitting just below a threshold and claims submitted close to a deadline are worth systematic review. A flat sampling rate spreads effort evenly across a population that is not evenly risky.
Reimbursement, payroll and the wage boundary
Reimbursement is where a control failure becomes a payroll event. Under an accountable arrangement, reimbursements are not wages. Otherwise they become wages subject to reporting and withholding, with the scope set by whether a plan requirement was missed or an individual failed to return an excess.
The payment rail is a separate decision from the tax classification. Payroll offers a single net payment and existing bank details, but blends reimbursement with compensation in employee-facing records. Accounts payable keeps the two distinct and preserves a cleaner audit trail, at the cost of employee payee records in a second system. Either supports an accountable plan; the choice is about evidence, not tax status.
Unsubmitted and unapproved expenses remain a period-end obligation whichever rail is used. Card transactions that have posted, trips completed without a claim, and approved claims awaiting payment each need an accrual basis and an owner, which is why travel and expense belongs on the month-end close control checklist rather than in a queue reviewed only when someone chases it.
Product map based on official documentation, 20 August 2026
The set below is a neutral starting point, not a ranking, a shortlist or a complete market inventory. Scope statements are company-stated, from official product pages and documentation checked on 20 August 2026. Packaging and integrations change, and no public product page establishes what a specific buyer will contract for.
| Operating model | Primary job | What it may include | What it should not be assumed to own |
|---|---|---|---|
| Integrated travel and expense platform | Hold booking and expense in one product so itinerary and spend reconcile | Booking, policy at point of search, capture, approvals, reimbursement, card feeds and reporting | Ledger authority, payroll processing or supplier contracting |
| Card and spend platform | Make the card program the control point and derive the expense record from the transaction | Card issuance, limits and policy at authorization, capture, coding, ERP sync and reimbursement | Full travel inventory, traveler support or tax determination |
| Expense-first application | Own capture, policy checking, approval and reimbursement independently of booking | Receipt capture, policy rules, per diem and mileage, card reconciliation and accounting integration | Managed travel content, duty-of-care tracking or card issuance unless separately contracted |
| ERP-embedded expense module | Keep the expense record inside the system that already holds the ledger and employee data | Expense entry, policy flags, approval workflow, card import and posting to the ledger | Travel booking, traveler experience or specialist audit tooling |
| Listed here as | Product | Company-stated scope | Buyer verification focus |
|---|---|---|---|
| Integrated travel and expense | SAP Concur Expense | Capture, automatic data entry, policy checks at submission, approvals, reimbursement and reporting; travel integrated in higher tiers | Which capabilities sit inside the contracted tier |
| Integrated travel and expense | Navan Expense | Card transactions categorized by merchant and role, receipt handling, policy enforcement, reconciliation, ERP sync, reimbursement by payroll or bank | Categorization accuracy against the company chart of accounts |
| Card and spend platform | Ramp Expense Management | Expense management built into the corporate card, policies applied at card level, receipt and memo capture, approvals, ERP coding | Treatment of spend outside the card program |
| Card and spend platform | Brex Travel | Booking inside preset travel policy, pre-approval workflows, spend limits, receipt population, trip grouping, multi-currency reimbursement, ERP sync | Inventory coverage for required routes and override evidence |
| Expense-first application | Expensify | Receipt transcription, report creation and approval, card import and matching, multi-level ledger coding, mileage, reimbursement, accounting integrations | Behavior when transcription confidence is low |
| Expense-first application | Zoho Expense | Receipt autoscan, policy enforcement by entity, department and cost center, per diem and mileage automation, approvals, card reconciliation, country editions | Whether a country edition covers the required tax treatment |
| Expense-first application | Emburse Expense | Receipt extraction, automated policy enforcement with pre-submission validation, multi-level approvals, card reconciliation, reimbursement, ERP and accounting integrations | Which functions require the separate audit or travel products |
| ERP-embedded module | Microsoft Dynamics 365 expense management | Expense submission with receipt capture and project coding, configurable approval workflows, policy-violation flagging, finance and HR module integration, audit trails | Depth of card import and per diem handling against a specialist product |
The comparison that matters is not the feature list. It is whether default behavior matches the policy the company has decided to run, and which record the product expects to own.
Integration boundaries decide the evidence
Travel and expense touches more systems than most finance processes of its size, and every boundary can duplicate or lose a record. Assign one authoritative owner per object before selection.
- Employee, cost center and delegation data: normally the human resources system. An expense tool holding its own employee list will drift, and a stale approver is a control finding rather than a data annoyance.
- Card transactions: the issuer feed is authoritative for amount, merchant and posting date. The expense tool owns the classification applied to that transaction, not the transaction itself.
- The expense claim and its evidence: the expense system, including receipts, policy results, approvals and the audit trail, retained for the statutory record period.
- The accounting entry: the general ledger. Every posting attempt needs an accepted, rejected and reconciled state, not a one-way export.
- Payment and tax reporting: payroll or accounts payable depending on the chosen rail, with the accountable plan classification carried through rather than re-derived.
Those boundaries are the same ones that determine whether a wider estate can be reconciled at all, and the finance systems integration map sets out how to specify and govern each interface.
Measure the program on prevention, not throughput
Most travel and expense reporting measures how quickly claims move. That rewards a program which processes weak evidence efficiently. A useful measure set separates prevention, control and cost.
- Managed-channel share: eligible travel spend booked through the managed channel, measured against total travel spend rather than against submitted claims.
- Policy exceptions by originating stage: attributed to booking, payment or claim, so the fix is applied where the defect began.
- Substantiation aging: card transactions and completed trips without a submitted claim, aged against the policy deadline and the safe harbor limits.
- First-pass acceptance, cost per claim and cycle time: read together and never alone, since throughput without first-pass acceptance rewards weak evidence.
- Unsubstantiated balance at period end: the accrued exposure carried into the close.
Make the approval decision
Approve a travel and expense design when four things are demonstrably true. The policy states which thresholds are internal choices and which follow a tax rule, with the rule cited. Substantiation and return-of-excess deadlines sit inside a named safe harbor and are enforced consistently. Every object has one authoritative system and one accountable owner, including the accrual for unsubstantiated spend. And the measure set reports prevention before throughput.
No product page settles those points. A platform enforces a policy it is configured with, captures evidence it is asked to retain and posts entries a ledger accepts. It cannot decide which thresholds a company is entitled to choose, and it does not carry the consequence when an arrangement stops being accountable.
Frequently asked questions
What is the 300% rule for travel expenses?
It is a federal ceiling. Under 41 CFR 301-11.17 a federal employee may request actual expenses up to 300 percent of the applicable per diem rate, and the regulation states there is no authority to exceed it. An agency may authorize less. Private employers are not bound by it, though many borrow it as a cap.
Can a private company use GSA per diem rates for its employees?
Yes, as a policy choice. GSA sets per diem rates and related policies for federal travelers on official travel only, so adopting the figures transfers no part of the tax analysis. A company using them still sets its own reimbursement terms and remains responsible for the accountable plan requirements.
How long do employees have to submit an expense report?
Company policy sets the deadline, but 26 CFR 1.62-2 provides a safe harbor treating substantiation within 60 days of the expense as reasonable. A shorter internal window such as 30 days is permitted and common. Having no stated deadline, or applying one inconsistently, is the position that creates exposure.
What happens if an employee does not return an unspent travel advance?
Where the arrangement otherwise meets the accountable plan requirements, only the amount above substantiated expenses falls outside it and becomes reportable wages. The rest is unaffected. A safe harbor treats return within 120 days of the expense as reasonable, so aging of outstanding advances needs a named owner.
