The invoice for an outsourced service arrives once a month and usually gets one of two treatments: approved without being read, because the amount looks like last month's, or argued over for the same three line items every time. Both point to the same thing. The contract never wrote down how the number is built.
The invoice is where a badly drafted contract becomes visible. Everything left ambiguous — what counts as a unit, what happens to rework, when a new agent starts being charged — comes back as money, with someone in procurement asking for an explanation the operation does not have at hand.
Reviewing is not reconciling
Reviewing an invoice means checking whether the line items and the arithmetic make sense. Reconciling is something else: comparing the data behind the charge against your own figure, measured outside the provider's system. Without that second source there is no reconciliation; there is trust, which is useful but is not a control.
You do not need a mirror system. It is enough that the client can count, with its own tooling, whatever is being billed: cases closed in the month, active seats, scheduled hours. If neither side can count the same thing independently, the problem is not the invoice — the billing unit was badly chosen.
What gets reconciled, by pricing model
Each model produces a different invoice and a different argument. The underlying logic sits in BPO pricing models; what follows is what to look at once the model is running.
- Per hour or per FTE. You compare hours: contracted, scheduled and actually covered. The questions that decide the amount are whether you pay for the seat or the person, what happens when someone is absent with no cover, and how a seat is billed while the vacancy is being filled.
- Per transaction. You compare a count, and the definition rules. Is a reopened case one or two? Does the same customer writing through two channels count twice? Is a case billed when it could not be resolved because the client's system was down? Those answers matter more than the unit rate.
- Per outcome. You reconcile the baseline and the attribution window. If the outcome can be produced by causes outside the provider's control, the invoice turns into a monthly argument about causality.
The items that are not the rate
Most differences are not in the unit price but in what surrounds it. These belong in the contract with their calculation rule, even if they are worth nothing the month it gets signed:
- Setup and transition. Documentation, initial training, configuration. Charged once, and usually billed against milestones rather than in full at kick-off.
- Premiums and overtime. Night, Sunday and public holiday work under the applicable labour rules. If the operation covers wide hours, this is not a detail: it is a recurring line.
- Tools and licences. Who buys them, in whose name they sit, and whether they are passed through with or without margin. The detail is in tools and licences in BPO.
- Surge capacity. The price of an extra hour during a peak and how much notice it requires.
- Custom reporting. Any report outside the standard package ends up either charged or not built.
When a new agent starts being charged
This is the item that generates the most argument and gets written down the least. An agent in training is not producing yet, and someone pays for that time: the client, the provider, or both in some proportion. All three are defensible and none is free; what does not work is not having agreed.
The same goes for replacements after attrition. If an agent leaves in month four, the next one goes through the learning curve again, and the contract should say whether that second ramp is billed like the first. How long that curve actually runs is covered in agent training and ramp-up, and it determines what the answer is worth.
How service credits reach the invoice
A service level agreement with penalties needs a mechanism, not just a percentage. Define what base the credit is calculated on, over which period it is measured, whether it arrives as a credit note or as a deduction on the following invoice, and who issues the calculation. In practice it works better to apply the credit to the next month rather than the current one: the last day's measurement is rarely closed when the invoice goes out.
Credits also do not replace the real conversation. An operation generating credits two months running has a problem that discounting will not fix, which is the subject of what to do about an SLA breach.
Annual adjustment and currency
A contract running longer than a year needs a written adjustment rule: what is adjusted, against which reference, on what date, and whether there is a cap. In Colombia the cost of a people-intensive operation moves mainly with the annual minimum wage decision, which lands at the end of the year and applies from January. A contract silent on this turns every January into a renegotiation.
If billing happens in a currency other than the one costs are incurred in, the rule has to be explicit: which rate, as of what date, who carries the movement, and whether there is a band beyond which it gets reviewed. Without that, the exchange difference is discovered on the invoice and argued without criteria. None of this is legal, accounting or tax advice: the final wording should be reviewed by the right professional in each country.
A contract that does not say how the invoice is built is handing that decision to whichever month the disagreement happens in.
What to do with a difference
Differences will happen. What keeps them from escalating is having the procedure written before you need it: a window to raise an objection, the rule of paying the undisputed portion while it is resolved, one person on each side with authority to decide, and a record of what was agreed.
That last part is the one most often skipped. A difference settled by email between two people gets argued again in six months, once those two people have moved roles. If the agreement changes a definition, it belongs in the contract or the operating annex, not in an inbox.
And one practical rule: a billing dispute cannot slow the operation down. The team doing the work should not find out that there is an argument about money in progress.
Who approves it, and against what
Approving the invoice is not accounts payable's job. It belongs to the contract owner, the only person able to say whether the number reflects what happened. To do that they need the supporting report before or alongside the invoice, not after, and cut to the same dates as the monthly operations report.
When the invoice and the operations report use different cut-offs, reconciliation becomes impossible and the review degenerates into accepting the total. Aligning the two costs one decision at the start and belongs to contract governance.
When the invoice is not the problem
Two patterns are worth reading as symptoms. If the same item is argued every month, there is no billing error: there is a badly written definition, and it gets fixed in the annex, not in the email thread. If the amount moved because volume did not look like what was expected, the matter belongs to demand forecasting and to the tolerance band that was agreed.
All of this is worth looking at before signing rather than at the first billing cycle. How to read a proposal with that in mind is covered in how to read a BPO quote in Colombia.
How smartBPO works it
We send the supporting report together with the invoice, cut to the same dates as the operations report, and detailed down to the unit being charged. We write into the contract the definitions that normally become arguments: rework, cases that cannot be resolved for reasons outside our control, training time and replacements after attrition. We list the ancillary items even when they are worth zero at signature. We agree the annual adjustment rule and, where relevant, the currency rule before the first billing cycle. And we keep the billing review inside the same operations meeting, because a disagreement about the number is almost always a disagreement about what happened during the month.