Timesheet reconciliation before invoice in outsourcing: 5 checkpoints
Who this is for: Owner, delivery lead, and finance in T&M/hybrid B2B teams.
When to read: If tracker hours, contract baseline, and invoice lines diverge before month-end.
What you get: Five reconciliation checkpoints and a 7-day rollout.
Next step: Book a 20-minute review, invoice-readiness checklist, weekly template (CSV).
Reconciliation is not a last-day Excel exercise — it proves that contract, tracker, scope changes, and disputed lines tell one story before you assemble the invoice.
1. Contract and baseline scope
- Invoice period matches approved baseline (milestone, month, sprint).
- Rates, caps, discounts, and currency from the current commercial version.
- Latest change orders reflected in baseline, not only in email.
2. Tracker actuals
- Export covers the same period as the invoice; no unexplained catch-up entries.
- Hours mapped to projects/contracts; no orphan rows.
- Delivery explains anomalies (zero, spikes).
3. Scope changes and extra work
- Each material delta has commercial status (request / in review / approved).
- Approved scope is tied to this invoice or the next milestone.
- Silent rework without status goes to a risk list, not default billing.
4. Disputed and non-standard lines
- Volume, rate, or period disagreements listed separately.
- Owner and decision date assigned — no “invoice now, argue later”.
5. Invoice package
- “Ready to invoice” list agreed with finance (amount or range).
- Attachments match summary numbers.
- Week outcome recorded in one place, not only chat.
What to do in 7 days
- Assign an owner per checkpoint.
- Run reconciliation on 2–3 contracts; log top-3 mismatch types.
- Link output to the weekly readiness checklist.
When not to start
- No single contract baseline and rate table.
- Finance and delivery refuse a shared weekly slot.
- Expecting ERP alone to replace delivery alignment.