Block Management Section 20B Supplier Invoice Register

A block management Section 20B supplier invoice register is the control sheet a UK residential managing agent uses to track whether service-charge costs have been demanded or notified within the 18-month recoverability window. It ties each supplier invoice to the block, service-charge schedule, incurred-date basis, demand date, Section 20B(2) notice status, and days remaining, so late costs can be demanded, notified, reconciled, investigated, or written off before recovery is put at risk.

The legal trigger is familiar, but the operational failure usually starts earlier. Section 20B of the Landlord and Tenant Act 1985 limits recovery where relevant service-charge costs were incurred more than 18 months before the demand is served, unless the tenant was notified in writing within that period that the costs had been incurred and would later be recovered through the service charge. For a block management finance team, that turns the supplier-invoice inbox into a dated evidence problem.

The register is how the firm sees the problem in time. A lift maintenance invoice, insurance premium, fire alarm testing invoice, cleaning contract charge, or surveyor's fee is not just an AP item waiting to be posted. It is also a cost that must be connected to a lease, schedule, block, demand cycle, and notice history. If that connection is left until year-end accounts, the 18-month clock may already be close to expiry.

A useful register does not try to make the legal judgement automatically. It makes the finance facts visible enough for the right person to decide. The AP clerk can capture the supplier, date, amount, property reference, VAT, and line description. The block manager or reviewer can confirm the schedule, incurred-date basis, demand route, and any need for a Section 20B(2) notice. The service-charge accountant can later trace the same line into the year-end pack.

That is the difference between a generic invoice list and a service-charge compliance register. The generic list answers "what have we received?" The Section 20B register answers "which recoverable costs are at risk if we do not demand, notify, or resolve them this month?"

The fields that make the register defensible

A defensible S.20B compliance register needs more than invoice number, supplier, and amount. It has to show why a cost sits in a particular block's service-charge account, which date was used for the 18-month calculation, and what happened before the deadline expired.

The core fields are:

• Block or scheme
• Service-charge schedule, such as block, estate, reserve fund, sinking fund, or another lease-defined schedule
• Supplier name
• Invoice number
• Invoice date
• Service period or works period
• Incurred-date basis
• Received date
• Posting date or payment date where relevant
• GL code or cost category
• Net, VAT, gross, and recoverable amount
• Demand status and demand date
• Section 20B(2) notice status and notice date
• Notice evidence or document link
• Days from incurred and days remaining
• Review status

The block and schedule fields do much of the work. Supplier invoices often arrive with imperfect property references: a postcode, a building name, a contractor job number, a site contact, or a free-text address that does not match the management system exactly. A register that simply imports the text visible on the PDF can still misallocate a cost. The safer design is to keep both the extracted property reference and the reviewed block allocation, with an exception flag where the match is uncertain. The same matching discipline applies when letting agents turn contractor invoices into landlord statement recharge lines, even though the downstream output is a landlord ledger rather than a service-charge schedule.

The schedule field is equally important. A communal electricity bill might belong to the block schedule. Grounds maintenance might sit on an estate schedule. Insurance might need apportioning across several buildings. A reserve-fund contribution, sinking-fund spend, or major works cost might follow a different lease path from ordinary annual expenditure. If the register cannot separate those lines, it cannot explain the demand trail later.

The review status should drive action, not merely describe history. Useful statuses include OK, at risk, notice required, notified, query with block manager, awaiting credit note, split required, excluded from service charge, and time barred. A portfolio finance lead should be able to filter the register and see which lines need a decision this month, not just which invoices were posted last month.

The evidence field is where the register earns its keep under pressure. Link the invoice PDF, notice copy, demand batch, apportionment schedule, email approval, or accountant query directly against the line. When a leaseholder inspection or tribunal-side reconstruction asks why a cost was recovered, the answer should not depend on someone remembering which inbox folder held the document.

Incurred date is the control point, not the inbox date

The date that matters for Section 20B risk is not necessarily the date an AP clerk opens the supplier email. A register that uses received date as the default control point can make an old cost look safer than it is.

The register should separate the dates that appear in the workflow:

• Invoice date: the supplier's document date.
• Service period: the period covered by the charge, such as quarterly lift maintenance or an annual insurance premium.
• Received date: when the managing agent received the invoice or statement.
• Posting date: when the item was entered into the accounting or property-management system.
• Payment date: when the supplier was paid.
• Incurred-date basis: the reviewed date used for the Section 20B ageing calculation, with a note explaining why.

In many routine AP workflows, invoice date and incurred-date basis may be the same. That assumption still needs review. Annual insurance can cover a policy period that starts before the broker statement is posted. Utilities may cover a billing period that ended weeks before the invoice arrived. Cleaning, grounds, concierge, and security contracts may be billed monthly in arrears. Surveyor, solicitor, fire-risk, or contractor invoices may relate to work completed on a different date from the invoice issue date.

The register does not need to turn every AP clerk into a leasehold lawyer. It needs to keep the uncertainty visible. A field such as "incurred-date basis" or "S.20B date note" lets the reviewer record whether the ageing calculation is based on the invoice date, service completion date, contract milestone, payment date, or another reviewed basis. Where the position is uncertain, the line should be flagged for the block manager, finance lead, or legal adviser rather than allowed to age quietly.

Supplier category helps the review. Lift servicing, fire alarm testing, emergency lighting checks, dry riser tests, water hygiene inspections, communal electricity, cleaning, garden maintenance, pest control, drainage, insurance, accountant fees, and professional surveyor fees all create different evidence patterns. The point is not to invent a different rule for each supplier. The point is to avoid treating a mixed portfolio of supplier documents as if every line has the same timing risk.

The strongest register therefore stores both the raw dates extracted from the invoice and the reviewed date used for ageing. If a leaseholder, accountant, or tribunal later asks why a cost was treated as recoverable, the firm can show the document date, the service period, the demand date, and the reasoning that connected them.

From PDF invoice batch to monthly review queue

The practical workflow starts with the monthly supplier-invoice batch. Contractor PDFs arrive through shared inboxes, portals, post scans, and block-manager forwards. Some are single-site invoices. Others cover several buildings, several schedules, or a period that does not match the service-charge year. The control only works if those documents become structured fields early enough for review.

A typical month-end flow looks like this:

1. Collect the supplier invoice PDFs for the block or portfolio.
2. Extract supplier name, invoice number, invoice date, service period, visible property reference, line description, net, VAT, gross, and total.
3. Match the extracted property reference to the reviewed block and schedule.
4. Flag exceptions: missing property reference, multi-block invoice, unusual service period, late invoice, credit note, duplicate, or uncertain incurred-date basis.
5. Post or import reviewed lines into the property-management or accounting system.
6. Update demand status, notice status, evidence links, and days remaining.
7. Review the at-risk queue with the block manager or finance lead.

This is where invoice extraction has a narrow but valuable role. A block management finance team can extract supplier invoice data into structured spreadsheets before the legal and lease-specific review begins. Invoice Data Extraction converts invoice and financial-document batches into Excel, CSV, or JSON outputs from a prompt-based upload workflow, so the reviewer starts with sortable fields rather than a folder of PDFs. The product can help capture visible invoice data at scale; it does not decide whether the cost was incurred on a particular legal date, whether a lease permits recovery, or whether a Section 20B(2) notice has been validly served.

That distinction matters. Automation should remove the transcription burden, not hide the judgement. The AP clerk or reviewer still needs to confirm block allocation, schedule treatment, incurred-date basis, and notice action. For portfolio work, the best output is not a finished legal answer. It is a clean import file and exception list that lets the team review the right lines first.

A general property management vendor invoice tracker can show whether supplier bills have been received, approved, and paid. The Section 20B register adds the service-charge layer: which leaseholder demand or notice preserves recovery, which evidence proves it, and which costs are ageing towards risk.

The monthly review should end with an action queue, not a static spreadsheet. Lines with clean block allocation, clear incurred-date basis, and a current demand path can be marked OK. Lines with fewer than three months remaining, missing demand evidence, unresolved apportionment, or unclear service period need escalation while there is still time to act.

When the register should trigger a Section 20B(2) notice

A Section 20B(2) notice is not a filing label for old invoices. It is the route the statute preserves where relevant costs have been incurred but the leaseholder will not receive a service-charge demand for those costs within the 18-month period. The register should make those candidates visible early enough for a proper notice decision.

The control field is simple: notice required, yes or no. The evidence behind it is more detailed. A useful notice register view should show the cost description, supplier, amount or estimate basis, block, schedule, incurred-date basis, leaseholder population, notice sent date, notice evidence, and reviewer sign-off. If the notice was served by post, email, portal, or a mixed method, the method and document location should be recorded as well.

Waiting until month 17 is poor control. A better ageing view bands costs by remaining time:

• More than six months remaining: monitor and resolve normal posting or demand issues.
• Three to six months remaining: confirm demand route, account timetable, and whether notice may be needed.
• Fewer than three months remaining: escalate to the block manager, finance lead, or solicitor for a demand or notice decision.
• Expired: investigate whether an earlier notice or demand covers the cost, then decide the recovery and write-off position.

On-account service-charge demands need particular care. Where the leaseholders have already been charged on account, the year-end balancing position may still depend on whether the later deficit or additional cost has been demanded or notified in time. The register should not treat "budgeted somewhere" as the same thing as "the relevant cost has been preserved". It should show the link between the supplier cost, the on-account demand, any final account timetable, and any notice served to preserve later recovery.

Year-end deficits create a similar problem. If final accounts will not be ready before the 18-month window closes, the register should identify the affected costs before the accounts process becomes the bottleneck. The notice decision may involve legal wording, service method, leaseholder addresses, and board or freeholder approval. The spreadsheet cannot make those steps valid, but it can stop the team from discovering the issue after the window has closed.

The operating discipline is to review the notice queue every month. If the line is not ready to demand, the question becomes whether it needs notification. If it does, the evidence field must later prove what was notified, when, to whom, and where the notice copy is stored.

Exceptions that break a simple invoice list

The register earns its place when the supplier documents stop being tidy. A straight invoice list can cope with a monthly cleaning bill for one block. It struggles with multi-block insurance, late contractor claims, credit notes, estate-wide costs, and invoices inherited from a previous managing agent.

Late invoices need an explicit received-date and review-status trail. If a contractor sends an invoice 14 months after completing work, the line should not disappear into ordinary AP. The register needs to show the service period, invoice date, received date, incurred-date basis, days remaining, and demand or notice action. The same applies where an old invoice is found in a shared inbox after a staff change or portfolio transfer.

Credit notes should reverse the original entry rather than erase it. Keep the supplier, credit note number, original invoice reference, amount, reason, and service-charge treatment. If the original cost was demanded and later credited, the register should show the correction path so the year-end account and leaseholder query trail do not contradict each other.

Duplicate invoices need the same discipline. Do not silently delete a suspected duplicate from the register, because the next reviewer may need to understand why it was excluded from recovery. Keep the supplier, invoice number, duplicate source, original invoice reference, review status, and exclusion or reversal evidence. If the duplicate was posted and then reversed, the register should show both sides of the correction.

Mixed schedules need splitting. A contractor may invoice for estate lighting, block entrance repairs, and car park maintenance in one document. An insurance broker may issue one statement for a dozen buildings. The register should allow one source invoice to create several reviewed lines, each with its own block, schedule, amount, incurred-date basis, and evidence link. Where the split comes from a broker schedule, contractor breakdown, lease percentage, or internal allocation, record that basis.

Reserve fund and sinking fund costs also need care. Some costs are annual operating expenditure. Others are capital reserve or cyclical works expenditure. The register should follow the lease and accounting treatment rather than force every supplier line into the same demand path. If a cost is excluded from the service charge or absorbed elsewhere, the status should say so.

Major works are the boundary to police. A recurring operating register should not become the whole project file for qualifying works, consultation notices, estimates, dispensation evidence, and final-account reconciliation. Where an invoice belongs to a consulted works programme, link it to the project record and keep the dedicated Section 20 major works invoice reconciliation process intact. The same separation applies upstream at Stage 2 consultation, where building the Section 20 Notice of Estimates pack with per-flat contractor cost apportionment belongs with the project file rather than the operating register. The register can still track timing and demand status, but the consultation evidence belongs with the major works file.

Change of managing agent is another common weak point. Incoming firms should create an onboarding exception view for inherited invoices, open supplier statements, prior demands, notices served by the outgoing agent, and missing evidence. If notice evidence is missing, do not mark the line as safe because someone says a notice was probably sent. Mark it as evidence required until the document is found or the recovery position is reviewed.

How the register feeds year-end accounts and inspections

The Section 20B register should reconcile into the year-end service-charge pack without a second reconstruction exercise. By the time the accountant prepares the Statement of Service Charge Expenditure, each supplier line should already have a reviewed block, schedule, amount, incurred-date basis, demand or notice status, and evidence link.

The reconciliation test is practical: register total by block and schedule should agree to the expenditure reported for that block and schedule, after accruals, prepayments, credits, reallocations, and excluded costs have been handled. If the year-end account shows repairs of £42,000 for Block A, the register should be able to show the supplier lines that make up that balance, which were demanded, which were notified, which were accrued, and which were adjusted after review.

This is where the monthly register feeds UK residential service charge year-end reconciliation. The accountant should not have to infer the Section 20B position from a nominal ledger export and a document folder. The register gives the accountant the timing and evidence layer that the ledger does not always carry: service period, notice date, demand batch, allocation basis, and unresolved exceptions.

RICS gives the operating context. The RICS Service Charge Residential Management Code says the 4th edition of the Service Charge Residential Management Code is effective from 7 April 2026 and aims to improve standards, consistency, transparency, timely documentation, and dispute reduction in residential leasehold service-charge management. A register is not proof of compliance by itself, but it is the evidence layer that makes timely documentation and transparency workable across a portfolio.

The same evidence matters for leaseholder inspection and RMC oversight. If a leaseholder or recognised tenants' association requests access to supporting documents after a service-charge summary, the managing agent needs more than a pile of invoices. It needs to show which cost was charged to which schedule, how the amount was apportioned, whether the demand or notice timing was controlled, and where the supporting document sits. The same register feeds the directors' own oversight work when an RMC or RTM board runs a Section 22 inspection audit on the year's supplier invoices, since the per-line reconciliation against demands relies on the same schedule, apportionment, and evidence trail.

Tribunal-side reconstruction follows the same pattern. A disputed line is easier to explain when the register shows the supplier invoice, service period, incurred-date basis, demand date, notice evidence, and later credit or adjustment. Without that trail, the firm may still have the underlying documents, but the story has to be rebuilt under pressure.

Operating rules for keeping the register useful

A Section 20B supplier invoice register fails when it becomes a year-end spreadsheet exercise. It works when it has a fixed monthly rhythm, clear ownership, and escalation rules that people actually follow.

Give the register an owner. In a small firm, that may be the service-charge accounts lead. In a larger managing agent, ownership may sit with a portfolio finance manager, regional AP lead, or senior block manager. The owner does not need to make every legal or lease judgement personally, but they do need to make sure every at-risk line has a reviewer, due date, and evidence trail.

The monthly control should be short and disciplined:

• Import or update the current supplier invoice batch.
• Resolve block and schedule matching exceptions.
• Review incurred-date basis for older or unusual costs.
• Update demand dates and notice dates from the service-charge system.
• Attach or link evidence for demands, notices, credits, and apportionment schedules.
• Produce an ageing report by portfolio, block, and review status.
• Escalate the at-risk queue before month-end close.

Escalation should be objective. A line needs review where the incurred-date basis is uncertain, fewer than three months remain, block allocation is missing, a multi-block apportionment is unresolved, there is no clear demand route, notice evidence is missing, or the item has already expired. That list keeps the review focused. Finance leaders and RMC/RTM directors do not need to read every invoice line each month; they need to see the items where recoverability, evidence, or allocation is not under control.

Document storage has to match the register. A link to the invoice is useful only if the file name, block, supplier, date, and amount are clear enough for someone else to find it later. The same applies to Section 20B(2) notices, demand batches, allocation workings, and credit notes. Staff turnover is one of the biggest tests of a compliance register: a new reviewer should be able to understand the line without asking the person who first processed it.

If a missed window is discovered, the register should force an honest decision. Check whether an earlier demand or notice preserves the cost. Seek specialist advice where the legal position is uncertain. Decide whether the landlord, freeholder, RMC, or managing agent absorbs the cost if it is unrecoverable. Then fix the control failure that allowed the line to expire, whether that was late supplier chasing, weak inbox ownership, missing notice review, poor block matching, or a year-end-only reconciliation habit.

The point of the register is not to make Section 20B risk disappear. It is to make the risk visible while there is still time to demand, notify, reconcile, or challenge the supplier evidence.