Exporting mileage to QuickBooks: a checklist without traps

— Product & Integrations Lead

Published: 4/28/2026 • Last reviewed: 4/28/2026 • 7 min read

QuickBooks export looks simple until the first reconciliation breaks. How to avoid that.

Why QuickBooks export needs a checklist

QuickBooks Online (QBO) and Desktop both accept mileage data via CSV upload, manual entry, or third-party connector. The flow looks straightforward: export approved trips from the mileage tool, import into QuickBooks, post to accounts. In practice, the failure modes are subtle and recur month after month if the workflow lacks a checklist.

The three most common failures: (1) chart-of-accounts mismatch, (2) multi-entity/class confusion, (3) date misalignment between trip date and posting date. Each is fixable in advance with a 5-minute pre-flight.

Pre-flight checklist

**Before the export**:

1. Confirm the QuickBooks chart-of-accounts code for vehicle reimbursement is current (a common pitfall is using a deprecated 6XXX account that QBO disabled). 2. Confirm the QBO Class or Location for each cost center — the import will fail if a class doesn't exist on the QBO side. 3. Confirm the period is closed in the mileage tool but *not yet* in QBO. 4. Confirm the export uses the right currency (USD vs CAD vs MXN — multi-entity QBO setups often have separate ledgers per currency).

**During the export**:

1. Use the dry-run preview to inspect the row count and total amount. 2. Reconcile the dry-run total against the mileage tool's period summary. 3. Verify the mapping covers: date, employee/vendor, amount, account code, class/location, memo (with trip purpose).

**During the import**:

1. Run QBO's import dry-run. 2. Resolve any 'unmatched account' or 'unmatched class' warnings before confirming. 3. After confirming, run the QBO 'Mileage by employee' report and reconcile against the mileage tool.

**After the import**:

1. Lock the period in the mileage tool. 2. Communicate to drivers that the period is closed and any late submissions land in the next period. 3. Archive the import CSV with a hash for the 7-year retention window.

Account mapping — the recommended structure

For a US company:

- **6300 — Travel: Mileage Reimbursement** (primary expense account). - Class/Location per cost center. - Vendor or Employee record per driver (W-2 employees as employees; 1099 contractors as vendors).

For a Canadian company, add the GST/HST tax code so the deemed Input Tax Credit (see post 114) flows automatically.

For a Mexican company on QBO Mexico, map to **5-1-04-001 Gastos de Viaje** with the deductibility flag set to deductible and the colaborador as proveedor (since QBO Mexico does not natively support employee reimbursements as expense categories).

Multi-entity setup

When the company runs multiple QBO entities (US + Canada, holding + opcos), the checklist expands:

1. Run one export per entity, never one consolidated export. 2. Use the entity-specific account codes (do not assume parent's chart-of-accounts is mirrored in subsidiaries). 3. Reconcile each entity separately — consolidated reconciliation hides per-entity errors. 4. If the parent rebills mileage to subsidiaries, use a clearing account and document the inter-company transfer in the QBO journal.

Common errors and the fix

**'Account does not exist'**: the export points to a code that's been deprecated or moved. Update the mapping config in the mileage tool, not in QBO. Re-run the dry-run.

**'Class is required for this transaction'**: the QBO file enforces classes but the export doesn't include one. Add a default class fallback in the mileage tool config.

**Duplicate import**: usually caused by running the export twice in one period. The fix is to delete the second batch in QBO (filter by import-batch-id), not to delete individual transactions.

**Currency mismatch**: a USD allowance imported into a CAD QBO file. The fix is to set the currency at the export level, not rely on QBO's auto-detection.

**Date drift**: trips dated last month posting to current month. Set the export to use trip date, not approval date. Approval date drift is the #1 cause of period-end reopening.

Reconciliation routine

After every import, run this 4-line check:

1. Sum of mileage tool 'approved trips' for the period × rate per km = X. 2. Sum of QBO 'Mileage Reimbursement' account postings for the period = Y. 3. X – Y should be zero (or within $1 rounding). 4. If X – Y > $1, investigate before signing off the close.

Document the reconciliation in the close ticket with the four numbers above. Auditors love this kind of paper trail.

When to skip the integration

The rule of thumb: a 4-driver fleet with monthly cadence often runs faster on manual QBO entry than via integration. The break-even is around 8 drivers; above that, the integration pays for itself in a quarter.

Quilometragem
Loading Quilometragem…