Start with the actual employer policy and its effective date
Record the policy version, currency, distance unit, applicable rate and submission rules. Ask which trips are eligible and how approvals and payment references are supplied. Do not treat an app total or an IRS tax rate as a promise that an employer must reimburse that amount. Local employment law, contracts and tax treatment are separate questions.
For a dated US comparison, the IRS page checked October 13, 2026 lists a business standard mileage rate of 72.5 cents per mile for January 1–June 30 and 76 cents per mile for July 1–December 31. These are tax guidance rates, not a universal employer policy. Preserve the travel date and verify the applicable rules rather than applying one annual rate to every 2026 trip.
IRS Publication 463 currently covers 2025. Its accountable-plan explanation requires a business connection, adequate accounting within a reasonable time, and return of excess amounts. It is useful background, not our determination that your arrangement qualifies. Check current guidance and ask payroll or a tax professional about your specific treatment.
Use trip IDs so a correction cannot become a second claim
Keep the original mileage evidence behind each row: date, business purpose, vehicle and distance method. Assign a simple stable ID such as T101. A claim can contain several trip IDs; a trip should not enter two active claims accidentally. Preserve a corrected version as a correction to the original, with the reason.
If miles and kilometres are mixed, resolve the unit before multiplying. Keep a claim’s reimbursement separate from tolls, parking and other expense lines unless the policy explicitly combines them. Do not compare a whole paycheck deposit with a mileage-only claim. You need an identifiable reimbursement line or payment reference.
If payment is not yet identifiable, write “not matched” and leave received amount blank. Blank does not mean zero paid. If payroll confirms that a particular claim has not been paid as of a date, then record zero with that confirmation date. This distinction prevents an incomplete bank search from becoming a false outstanding balance.
Worked claim: 100 submitted miles, 90 approved, partial receipt
Suppose a fictional employer policy pays USD 0.60 per eligible mile. This is an illustrative policy, not the IRS rate or a recommended rate. The claim contains two trips and payroll identifies the received allocation. The matched payment is dated October 10; this review is as of October 13, 2026.
| Trip | Submitted / approved miles | Submitted / approved amount | Matched receipt | Approved less received |
|---|---|---|---|---|
| T101 | 40 / 40 | 24.00 / 24.00 | 24.00 | 0.00 |
| T102 | 60 / 50 | 36.00 / 30.00 | 20.00 | 10.00 |
| Claim C17 total | 100 / 90 | 60.00 / 54.00 | 44.00 | 10.00 |
The submitted-to-approved difference is USD 6.00. The approved-to-received difference is USD 10.00. These are different questions. Ask: “Which 10 miles were excluded from T102, and is the remaining approved USD 10 scheduled for a later payment?” Do not claim that the entire USD 16 submitted-to-received difference is already approved and overdue.
If payroll supplies only a USD 44 claim-level payment, reconcile at claim level and leave the trip allocation unknown; do not invent the 24/20 split shown in this example. If a later payment brings receipts to USD 59 against USD 54 approved, the difference is −USD 5, a possible excess to clarify, not a bonus. Keep the payment date and reference and follow the confirmed correction process.
Keep mileage evidence in OdoCue; reconcile payment outside it
OdoCue’s current listing describes manual entry using odometer readings or direct distance, vehicle and purpose categories, local logs and totals. Premium adds CSV/PDF exports, yearly reports, reimbursement summaries, custom rates and unlimited report history. It does not require GPS tracking or account setup.
Use its trip export as mileage evidence, then reconcile claims and payment references in the separate worksheet. The current listing does not establish employer approval integration, payroll matching or guaranteed legal eligibility. Check currency, units and selected rates before sharing an export with your employer.
The CSV has illustrative detail rows, a total row and a blank row. When extending it, remove or recompute the illustrative total; never sum a total row as if it were another trip. It contains values, not automatic spreadsheet formulas. Store only the payment reference needed for reconciliation, not bank account numbers or a full private statement.
If the method fits your task, explore OdoCue’s listed features on an iPhone. Check current features and plans before downloading.
See OdoCue for iOSDownload the free worksheet
Use the CSV in Numbers, Excel or a spreadsheet editor. Two fictional trip rows, a clearly labeled total and a blank row. Replace policy and values; recompute totals. No formulas or personal tax eligibility assessment. Replace them with your own observations. The CSV is separate from the app and no email is required.
Questions answered
Is the IRS rate my employer’s required rate?
Not automatically. Confirm the employer policy, agreement and applicable local rules; IRS tax guidance is a separate question.
Does a blank received field mean unpaid?
No. It means the payment has not been matched. Record zero only when that claim’s unpaid status is confirmed as of a date.
What if one payment covers several trips?
Match at claim level unless payroll provides a reliable trip allocation. Do not invent a split.
Continue with OdoCue on iOS
Use the App Store listing to check compatibility, privacy information and current plan terms. A free download may offer paid features.
Download OdoCue for iOSSources and product details
- IRS: standard mileage ratesUS 2026 business rates split at July 1; checked October 13, 2026.
- IRS Publication 463 (2025): reimbursement arrangementsAccountable-plan background and adequate accounting; not a determination of employer policy or personal eligibility.
- OdoCue on the App StoreCurrent US App Store product description; checked October 13, 2026.
Editorial method: primary guidance, a current Apple listing, an original worked example and an independent critique. No search ranking, install or outcome result is claimed.