S106 Financial Tracking: Managing Contributions from Receipt to Spend

Tracking section 106 contributions is the core of obligation monitoring. Every pound received from a developer needs a recorded receipt date, a calculated spend-by deadline, an allocation to a project, and evidence of spend. At councils managing 50+ live agreements, this involves hundreds of individual contribution lines — each with different amounts, indexation bases, and deadlines.

This guide covers the practical mechanics of S106 financial tracking, with a focus on the calculations and processes that prevent money from being lost, miscounted, or returned to developers.

This covers England only. This is general guidance, not legal advice.

The Financial Tracking Record

Each financial contribution needs these fields tracked:

Field	Source	Why It Matters
Agreement reference	S106 agreement	Links to the legal terms
Obligation purpose	Agreement schedule	Education, highways, open space, etc.
Base amount	Agreement	Starting figure before indexation
Indexation basis	Agreement	BCIS / RPI / CPI / fixed
Base date	Agreement	Starting point for index calculation
Trigger event	Agreement	When the obligation activates
Trigger date	Monitoring records	When you recorded the trigger firing
Indexed amount	Calculated	The actual amount to invoice
Invoice date	Finance records	When the demand was issued
Receipt date	Finance records	When payment arrived — starts the spend-by clock
Amount received	Finance records	May differ from invoice if disputed
Spend-by period	Agreement (clawback clause)	Usually 5–10 years from receipt
Spend-by deadline	Calculated	Receipt date + spend-by period
Allocation status	Service area	Which project the money is earmarked for
Amount spent	Finance records	Disbursed to date
Amount retained	Calculated	Received minus spent

This is too many fields for a single spreadsheet row — which is exactly why spreadsheet-based tracking breaks down at scale.

Indexation: The Calculation Most Councils Get Wrong

Most S106 financial contributions are index-linked. The agreement states a base amount and specifies an index (usually BCIS All-in Tender Price Index, sometimes RPI or CPI). The amount the developer owes is the base amount adjusted by the index movement from the base date to the calculation date.

The calculation:

Indexed Amount = Base Amount × (Index at Calculation Date ÷ Index at Base Date)

Example:

• Base amount: £150,000
• Index basis: BCIS All-in Tender Price Index
• Base date: Q1 2021 (index value: 388)
• Calculation date: Q1 2026 (index value: 461)
• Indexed amount: £150,000 × (461 ÷ 388) = £178,222

Note: the index values above are illustrative. Actual BCIS figures should be obtained from RICS at the point of calculation.

If you invoice £150,000 instead of £178,222, you've left £28,222 on the table for that single obligation. Across a portfolio of 100+ financial obligations, systematic under-indexation can cost a council hundreds of thousands.

Common indexation mistakes:

• Using the wrong index (the agreement says BCIS, the officer uses RPI)
• Using the wrong base date (using the agreement date when the index clause specifies a different quarter)
• Not indexing at all (invoicing the base amount verbatim from the agreement)
• Using an outdated index value (the index is published quarterly — check you're using the current figure)

BCIS index values are published by the Royal Institution of Chartered Surveyors (RICS) and require a subscription. If your council doesn't have BCIS access, check whether the index is available through your quantity surveying or property team.

Receipts: The Point Where Everything Gets Recorded

When finance confirms a developer payment:

1. Match to obligation. Identify which agreement and which obligation the payment satisfies. Developers sometimes pay a lump sum covering multiple obligations — split and allocate each portion.

2. Record the receipt date. This is the date the money hit the council's bank account, not the date the invoice was issued. The spend-by deadline is calculated from this date.

3. Check the amount. Does it match the indexed invoice? If less, record the shortfall and follow up with the developer. If more (overpayment), clarify with the developer and record accordingly.

4. Calculate the spend-by deadline. Receipt date + spend-by period from the agreement. If the agreement says "5 years from receipt," and the receipt date is 15 March 2026, the deadline is 15 March 2031.

5. Set alerts. At minimum: 18 months, 12 months, 6 months, and 3 months before deadline.

6. Notify the service area. The team responsible for spending the contribution (education, highways, parks) needs to know money has arrived and when it needs to be spent.

Allocation: Not the Same as Spend

Allocating a contribution to a project is an administrative decision. Spending it is a financial transaction. They are different events with different dates, and both need tracking.

Common confusion: A council allocates £200,000 of education contributions to a school expansion. The project is scheduled for next year. The monitoring officer marks the contribution as "allocated" and moves on. Two years later, the project is delayed. The contribution is still allocated-but-unspent, and the deadline is now 18 months away.

Track allocation and spend separately:

Status	Meaning	Deadline Risk
Received, unallocated	Money in holding account, no project identified	High — no spend timeline
Allocated, unspent	Earmarked for a project, not yet disbursed	Medium — depends on project timeline
Partially spent	Some money disbursed, balance remaining	Low-Medium — track remaining balance
Fully spent	All funds disbursed, evidence recorded	None — can discharge obligation

The highest-risk category is "received, unallocated" — money sitting in a holding account with no plan. The second-highest is "allocated, unspent" where the project timeline doesn't fit within the spend-by window.

Reconciliation with Finance

Your S106 monitoring records and the council's finance system will diverge. This is normal but needs regular reconciliation:

Why they diverge:

• Finance records a payment as a single transaction; S106 monitoring needs it split across obligations
• S106 records obligations by agreement reference; finance may use a different coding scheme
• Indexation adjustments appear in S106 records but not in finance (the invoice was for the indexed amount, but finance records the receipt)
• Transfers between S106 holding accounts and project budgets may not be reflected in S106 records

Quarterly reconciliation process:

1. Export S106 contribution receipts from your monitoring records
2. Export matching receipts from the finance system
3. Match by amount, date, and developer name
4. Investigate any unmatched entries
5. For each matched entry, confirm the receipt date and amount agree

Do this quarterly, not annually. Annual reconciliation (usually forced by IFS) means 12 months of discrepancies to untangle in December.

Clawback Prevention

The spend-by deadline is the hardest deadline in S106 monitoring. If unspent contributions cross it, the developer has a contractual right to reclaim them — see S106 Spend Deadlines: What Happens When Developer Money Expires for the full implications.

A financial tracking system prevents clawbacks by:

• Recording receipt dates (so deadlines can be calculated)
• Calculating and displaying spend-by deadlines (so they're visible)
• Alerting officers at defined intervals (so deadlines don't arrive silently)
• Tracking allocation and spend status (so at-risk contributions are identified early)
• Generating reports for senior leadership (so escalation happens before the deadline, not after)

For a quick check of your current deadlines, use the S106 Spend Deadline Calculator.

For the broader monitoring framework, see The Complete Guide to S106 Monitoring for Planning Officers.

Sources

• Town and Country Planning Act 1990, Section 106
• Community Infrastructure Levy Regulations 2010
• PAS — Infrastructure Funding Statements
• GOV.UK — Planning Obligations Guidance