Agencies · Back office
Reconciling timesheets, payroll and agency invoices
Connect approved work, payroll outputs and client billing with stable references, a reconciliation table and an exception process for genuine differences.
Freelancer SupermarketPublished 3 min read
Reviewed 17 September 2026. Recheck linked official guidance and assignment-specific requirements before relying on it.
Timesheets, payroll and invoices describe different parts of an assignment. Their totals will not necessarily be equal: pay and charge rates can differ, and different adjustments may belong in different records. Reconciliation means explaining the relationship and identifying unexplained differences.
Use a stable assignment reference and period throughout the process. If the systems cannot share one identifier, maintain a documented mapping. Name matching alone becomes unreliable when one worker has several assignments or a client operates through multiple entities.
Define what you expect to match#
Agree which records establish approved work, which payroll output confirms the processed input and which invoice lines bill the client. Document the applicable rates and effective dates. Where an amount is calculated differently across systems, write down the intended calculation and its source.
Decide which team owns the reconciliation and which teams resolve exceptions. The reviewer should be able to distinguish a known timing difference from an error that requires a correction. Both need a reference and a follow-up date where appropriate.
Create a period-level control table#
| Control | Comparison | Exception to investigate |
|---|---|---|
| Population | Expected assignments against received records | Missing or duplicate assignment |
| Work period | Approved work against processed period | Wrong week or overlap |
| Hours or units | Approved quantity against payroll and billing inputs | Unexplained difference |
| Rates | Effective approved rate against each output | Old or unauthorised rate |
| Adjustments | Approved change against resulting records | One team updated, another omitted |
| Completion | Expected outputs against issued files | Missing output or duplicate release |
Keep the supporting detail behind each control. A grand total can balance while errors in individual assignments cancel each other out.
Example: matching hours does not mean matching money#
Imagine an assignment with 35 approved hours, an illustrative pay rate of £20 and an illustrative charge rate of £28. The simple pay input is £700 and the simple billing amount is £980 before any other applicable items. These invented figures explain the comparison; they are not a recommended margin or a payroll calculation.
The hours agree while the amounts differ for an understood reason. If the billing file instead contains 40 hours, investigate the five-hour difference. Do not force the invoice amount to match payroll merely because the two files are being reconciled.
Manage corrections without losing the original record#
When a discrepancy is confirmed, record the authorised correction and link it to the original period. Ask the payroll and billing owners which downstream actions are required. A change in the source timesheet does not prove that a later payroll adjustment or credit note has been completed.
Carry unresolved differences into an exception register with an owner and next action. Review the register at the next cycle so timing items do not accumulate indefinitely under a generic “pending” label.
Sign off a complete explanation#
A useful reconciliation ends with the checked population, explained differences, unresolved exceptions and approval record. Retain the source versions used for that review. Then look for recurring causes such as inconsistent references, rate changes entered in only one system or late corrections.
The back-office outsourcing guide discusses which tasks to retain or delegate. Bring a redacted sample of the three records to our back-office service to discuss the controls and handoffs your agency needs.