Reconciling compensation payments: the evidence gap nobody budgets for
Paying compensation and proving you paid it are different problems. How disbursement files are reconciled back to entitlements.
Paying compensation and proving you paid it are separate problems, and projects consistently solve the first while assuming the second comes free. It does not. Reconciliation — matching what was actually disbursed back to what was owed, person by person — is where resettlement records break, and it breaks late, when the completion audit arrives and nobody can produce an unbroken line from entitlement to receipt.
Why the records do not line up on their own
Compensation is rarely paid by the team that calculated it. The entitlement is determined by the resettlement unit from the census and valuation. The payment is executed by the implementing agency's finance function, or a paying agent, through a bank or mobile money operator — producing a disbursement file in the payer's format, on the payer's schedule, with the payer's identifiers.
Those two datasets were never designed to join. The register holds a person with a household code and an entitlement; the bank file holds an account number, a name string and an amount. Matching them is a manual exercise that someone has to actually perform, and in most projects nobody is explicitly assigned to it.
The entitlement register says what was owed. The disbursement file says what left the account. Nothing in either says they refer to the same person.
What reconciliation surfaces
Run properly, the exercise produces a small number of recurring exception types. Each is individually explicable. Collectively, undiscovered, they are what an audit finding is made of:
- Entitlements with no matching payment. Someone is owed money and has not been paid, and nobody noticed because the register was never checked against the bank.
- Payments with no matching entitlement. Money left the account against a name not on the register — sometimes a data error, sometimes not.
- Amount mismatches. Paid more or less than the determination, with no recorded reason.
- Duplicates. The same entitlement paid twice, typically after a failed first attempt was re-issued without the original being reversed.
- Name mismatches. Payment made to a relative, a spouse or an agent, which may be entirely legitimate and is indistinguishable from diversion without a record of the arrangement.
- Sequence failures. Payment dated after the displacement date for that parcel — a breach of the standard even where the amount was correct.
Per funder, not just in total
On co-financed projects the reconciliation has a second dimension. Different financiers fund different components, and each wants assurance about its own money. A reconciliation that balances in aggregate but cannot attribute payments to a specific credit or facility does not answer the question a lender is actually asking.
This becomes financially material where disbursement is tied to compliance milestones — an increasingly common structure, and one that converts an unreconciled register from an administrative untidiness into a withheld tranche.[3]
Continuous, not terminal
The decisive variable is when reconciliation happens. The same discrepancy costs almost nothing in the month it occurs and a great deal two years later.
| Reconciled monthly | Reconciled at audit | |
|---|---|---|
| Volume per pass | Tens of exceptions | Thousands, accumulated |
| Institutional memory | Staff still in post, case recalled | Staff rotated, nobody remembers |
| Corrective options | Pay the shortfall, recover the duplicate | Person may be untraceable |
| What it is called | An administrative correction | An audit finding |
The record each payment needs
For a payment to be defensible at audit it has to carry, at minimum: the person and their register identifier; the entitlement it discharges and the determination behind it; the amount, date and method; evidence of receipt by the named person; the funder or facility it was charged to; and — where it differs from the determination — the reason, recorded at the time.[2]
That final element is the one that separates a legitimate variance from an irregularity. A payment differing from the entitlement is not itself a problem. A payment differing from the entitlement with no contemporaneous explanation is indistinguishable from one.
Recording payment is not making payment
A distinction worth being precise about, because it is frequently blurred: a resettlement system should record and reconcile compensation, not execute it. Money movement stays with the project, the paying agent, the bank or the mobile money operator — institutions that are regulated to do it.
Staying out of execution is not a limitation. It keeps the system method-agnostic, so cash, bank transfer, mobile money and in-kind delivery all reconcile through the same register — which matters, because a single resettlement will use all four, and the households hardest to reach are usually the ones paid by the method with the weakest paper trail.[4]
Sources
- [1]Performance Standard 5: Land Acquisition and Involuntary Resettlement — International Finance Corporation, 2012.
- [2]Good Practice Handbook: Land Acquisition and Involuntary Resettlement — International Finance Corporation, 2023.
- [3]ESF Guidance Note 5: Land Acquisition, Restrictions on Land Use and Involuntary Resettlement — World Bank, 2018.
- [4]Evicted and Abandoned: The World Bank's Broken Promise to the Poor — International Consortium of Investigative Journalists, 2015.
Olule Solomon
Lead Consultant, ValueSpace
Olule Solomon is Lead Consultant at ValueSpace, where he works on land acquisition and resettlement systems for donor-financed infrastructure in East Africa. He writes about the practical gap between what the safeguard standards require and what a project can actually evidence at completion audit.
Related reading
- The RAP completion audit: evidencing compliance you cannot reconstructWhat a completion audit tests, why reconstruction after the fact fails, and the records that have to exist from day one.
- Costing a RAP: why resettlement budgets are wrong before they are approvedWhat a resettlement budget must contain, the line items projects systematically omit, and why contingency is not padding.
- Full replacement cost: the valuation rule projects get wrong most oftenWhat replacement cost means under PS-5 and ESS-5, why depreciation cannot be deducted, and how to evidence the basis.
Free entitlement matrix template
15 loss categories, eligibility split by tenure, valuation basis and the PS-5 provision behind every row. CSV, no registration wall.
Get the template →The software behind this
SmartLARMS keeps the record this article describes
PAP register, replacement-cost valuations, entitlements, recorded payments reconciled against disbursement files, and grievances — every change attributed and time-stamped, so a completion audit is evidenced rather than reconstructed. Offline-first in the field.