Assess Subcontractor Applications for Payment & Pay Less Notice

To assess a subcontractor application for payment under the Housing Grants, Construction and Regeneration Act 1996, the receiving QS values each AfP line against site progress at the contract rate, deducts retention, CIS on the labour element, and previously paid amounts to arrive at a certified payable. Where that certified figure is lower than the sum the subcontractor has claimed, a Pay Less Notice must reach the subcontractor before the Final Date for Payment, specifying the sum the contractor considers due and the basis on which that sum is calculated. Miss the Pay Less Notice deadline and the subcontractor's claimed amount becomes the notified sum and is payable in full, regardless of whether the underlying claim was defensible. That mechanic — the default payment notice and the smash-and-grab adjudication that follows it — is the reason the monthly assessment workflow exists in the shape it does.

Four anchor points fix the notice clock for any subbie payment cycle. The Due Date is set by the subcontract and is the date by which the AfP is treated as due. The Payment Notice goes out not later than five days after the Due Date, certifying the sum the contractor proposes to pay. The Final Date for Payment is set by the subcontract, fixing when the certified amount must actually be paid. The Pay Less Notice — when one is needed — must reach the subcontractor not later than the prescribed period before the Final Date for Payment. The prescribed period itself is set by the subcontract, typically one to seven days under JCT and NEC sub-contracts, and should be checked against the specific contract rather than assumed. The Payment Notice clock runs from the Due Date; the Pay Less Notice clock runs against the Final Date for Payment. Two different deadlines, two different reference points, and the construction act pay less notice deadline is the one that turns the whole assessment into time-pressured work.

If you have arrived here looking for the AP-team question of whether the incoming AfP also serves as a VAT invoice for input-tax purposes, that is a separate matter covered in AfP versus VAT invoice under JCT and NEC.

Loading the subbie AfP PDF into the assessment workbook

The input is a working PDF, almost always exported from the subcontractor's own quantity-surveying system or built off a contract-specific template. Each line is a work-package or BOQ item with a contract reference, a description, a unit of measure, a claimed quantity to date, a unit rate, a claimed cumulative value, and a previously certified value. Some subbies submit narrow files of fifteen to twenty header lines; others submit detailed spreadsheets with hundreds of rows where every BOQ item, every variation, and every dayworks sheet has its own line. The shape varies; the receiving discipline does not. The assessment workbook on the contractor's side is the canonical structure, and every AfP feeds into it.

The workbook columns the QS needs to populate for each AfP line are these:

• Contract reference — BOQ item number, variation number, daywork sheet number, or quoted-package reference.
• Description.
• Unit of measure.
• Claimed quantity to date and claimed unit rate.
• Claimed cumulative value.
• Previously certified quantity and previously certified value (from the contractor's own payment ledger, not the AfP's "previously paid" column).
• This-period claimed quantity (claimed cumulative quantity minus previously certified quantity).
• Assessed quantity to date and assessed cumulative value — populated as the QS works through the next steps.
• Measurement reference and evidence link — populated during measurement.
• Rate source — BOQ, Schedule of Rates, agreed variation rate, dayworks, lump-sum percentage complete.
• Retention applied, CIS treatment, previous-payment offset, and current-payable contribution — populated through the deduction sequence.
• Signed-off date and signed-off by — for the audit trail.

Loading the AfP PDF into that workbook by hand is where the month's work breaks down on a busy project. A mid-sized commercial fit-out can carry one hundred and fifty to four hundred lines on the larger subcontracts; an infrastructure scheme with multiple specialist subcontractors can run higher. Retyping line items, quantities, and rates is where transposition errors enter — and a transposition error in a unit rate or a quantity surfaces later as a contra-charge, a delayed certification, or, on the wrong end of the timing, an indefensible Pay Less Notice. AI-powered subcontractor invoice and AfP extraction takes the AfP PDF and produces structured rows for the workbook with the contract references, descriptions, quantities, unit rates, and cumulative values intact, ready for the QS to start measurement and rates application. The discipline is the same line-item extraction principle applied on the supplier-merchant side of the same project, which is covered for upstream documents in extracting line items from UK builders' merchant invoices — same extraction logic, different document type, different point in the procurement chain.

One convention is worth fixing in place before the next step. Every AfP line is a cumulative claim, not a this-period claim. The subcontractor states the quantity and value of work claimed to date across the entire subcontract; the previously certified amount is deducted at the end of the assessment, not at the start. The interim valuation subcontractor assessment runs cumulative throughout, and the current payable falls out of the final deduction. Mixing cumulative and incremental figures in the workbook is the most common cause of arithmetic that does not reconcile, and it is the one cause that is entirely avoidable.

Pairing each claimed line with site-measurement evidence

The AfP is a claim. The assessment is what the contractor is prepared to certify as the value of work properly executed cumulative to the valuation date. For each line in the loaded workbook, the assessed quantity is the lesser of the claimed quantity and what the evidence supports as in place at the valuation date, and that comparison runs on every line before any rate is applied.

The evidence types that back each assessed line vary by the work category. For measured trades — blockwork, rendering, screeding, ceilings, drylining — the primary evidence is the site QS's measurement book entry or a digital measure exported as a PDF, taken on a dated visit and tied to a specific area or grid reference. Photographic evidence keyed to a date, a location, and a contract reference supports the measurement and is the practical fallback where the trade is one that does not lend itself to discrete measurement. Foreman or site-supervisor dockets confirm work in place where the supervisor's sign-off is the contractual substantiation — typical on labour-only packages and on installations where the work disappears behind subsequent trades. Signed daywork sheets carry their own evidential weight where dayworks are claimed; the sheet itself is the record. Where the subcontract permits valuation of unfixed materials on site, delivery records and material-on-site reports — typically with photographic confirmation — are the evidence the assessment relies on.

The disputed-quantity cases are the ones the workbook needs to resolve before the rates step. Treat them in the same order each month:

• Claimed quantity exceeds measured quantity. Assess at the measured quantity. Record the measurement reference and evidence link; the claimed-versus-assessed difference will appear in the basis-of-calculation paragraph if a Pay Less Notice follows.
• Claimed work is in place but defective or non-conforming. Assess at zero on the affected portion, or at a remediation-discounted value where the defect is partial and the contract permits the discount. The contra-charge for remediation sits on its own ledger; flag the workbook line with the contra-charge ID so the basis paragraph reads through to the underlying record.
• Materials on site claimed but not yet permitted under the subcontract. Assess at zero pending the contractual trigger — typically delivery to a designated location, vesting documentation, or the contract's specific materials-on-site clause being met. Note the trigger condition on the workbook line.
• Variation work claimed without an instruction. Assess at zero pending the architect's, engineer's, or contract administrator's instruction, and flag the line for the variations register so the missing instruction surfaces against the right document.
• Variation work instructed but the rate not yet agreed. Assess at the QS's fair valuation pending agreement, and mark the line as provisional in the workbook.

Two timing points sit underneath all of this. First, the valuation date is fixed by the subcontract and is the date against which evidence must be taken. Work completed on the day after the valuation date does not count toward this month's assessment, regardless of when the AfP itself was sent in or received. Second, evidence has to exist at the valuation date — a photograph dated three days later does not retrospectively prove what was in place on the valuation date. The site QS's measurement visit needs to be scheduled against the valuation calendar, not against when the AfP arrives in the inbox.

Each assessed quantity, once settled, populates the assessed-quantity column on the workbook line, and the measurement reference and evidence link go into their own columns alongside it. That is the audit-trail record that the rates step works on top of, and that the Pay Less Notice basis-of-calculation paragraph will reference line by line if the assessment is challenged.

Applying contract rates by category: BOQ, Schedule of Rates, variations, dayworks, lump sums

Each line in the workbook now has an assessed quantity. The next step is to find the right rate for that line and produce the assessed cumulative value. There are usually five rate sources in play across a single subcontract, and the rule for which applies is set by the subcontract structure and by what kind of work the line represents.

BOQ rates apply to measured-work lines on subcontracts let against a priced bill of quantities. The rate to use is the one in the priced BOQ for that BOQ item, applied to the assessed quantity, and the line is capped at the BOQ scope — work claimed beyond the BOQ scope is variation work, not measured work, and goes through the variation route instead.

Schedule of Rates rates apply where the subcontract is structured on a rates schedule rather than a measured BOQ — a typical pattern on framework or term subcontracts where the scope is not fully defined at award. The rate to use is the rate-schedule rate for that line, applied to the assessed quantity, with the rate's qualifying conditions checked against the line. Many rate-schedule rates carry conditions on minimum quantities, working hours, or access — if those conditions are not met on the assessed line, the rate may not apply as stated and the line needs to be referred back to the subcontract's pricing principles.

Agreed variation rates apply to variation lines, drawn from the variations register. A variation needs both an instruction (architect's instruction, engineer's instruction, or contract administrator's instruction depending on the contract family) and an agreed rate before it can be valued at the agreed rate. Where the variation has been instructed but the rate is not yet agreed, the line is assessed at the QS's fair valuation pending agreement and flagged on the workbook as provisional. Where the variation has been claimed but no instruction exists, the line was already assessed at zero in the measurement step.

Dayworks are valued at the contracted dayworks labour, plant, and material rates against the signed dayworks sheet, with the percentage addition the subcontract specifies (typically a fixed uplift on labour, plant, and materials separately, set out in the subcontract's dayworks schedule). The signed dayworks sheet is both the evidence and the source of the hours and quantities. Unsigned dayworks sheets are not valued — the contract's signature requirement is what makes the daywork claim payable.

Lump-sum packages are valued by percentage complete against the package's defined milestones. The QS's job here is to assess the percentage complete against the milestones the subcontract sets out, multiply by the lump-sum value, and produce the assessed cumulative value for the package as a single line. Milestones that are not yet reached value at zero for the milestone increment regardless of effort claimed against them.

Two upstream documents sit underneath the rates step. The priced BOQ supplies the measured-work rates and the BOQ scope. The variations register supplies the agreed rates and the instruction status for variation lines. Both must be in good order before the rates step can close cleanly — a BOQ rate that has not been correctly transcribed into the assessment workbook, or a variation that has been valued without an instruction, will not survive a challenge.

Once each line carries its assessed quantity, its rate source, and its rate, the arithmetic on each line is straightforward: assessed quantity to date times the contract rate equals the assessed cumulative value for that line. Sum the assessed cumulative values across all lines on the subcontract and the result is the gross-cumulative valuation. That figure — not the headline AfP claim — is the figure the deduction sequence operates on.

The deduction sequence: retention, CIS on labour, previous payments

The deduction sequence runs in one specific order: gross cumulative valuation, then retention applied to the cumulative figure at the contracted rate, then CIS on the labour element of this period's payment by the subcontractor's verification status, then previously paid amounts offset against the cumulative-net total, and the remainder is the current payable. The order is not stylistic. Retention applies to gross cumulative because retention is a cumulative liability against the value of work done. CIS applies to this period's labour element only because the deduction is on the payment being made now, not on the cumulative position. Previous payments come last because they are the offset that turns the cumulative-net figure into a this-period payable. Rearrange any of those steps and the figure changes.

Retention. Apply retention as a percentage of the gross-cumulative valuation. The percentage is set by the subcontract — commonly three percent or five percent under JCT sub-contracts, sometimes lower on long-running framework arrangements, sometimes structured as a sliding scale that drops on practical completion. Read the rate from the subcontract; do not assume a default. The cumulative retention sits on the contractor's balance sheet as a liability to the subcontractor, half typically released on practical completion of the subcontract works, the remainder on the issue of the defects rectification certificate at the end of the rectification period. The cumulative retention figure on this assessment feeds the project's retention-release tracker, which is where the release dates and the release values sit.

CIS. CIS is deducted on the labour element of this period's payment only — not on materials, not on plant hire, not on the cumulative figure. The split between labour and materials/plant is taken from the subcontract pricing or, where not separately stated, from the subcontractor's own breakdown supported by their invoice or AfP detail. The deduction rate depends on the subcontractor's verification status with HMRC at the time of payment: gross status applies a zero-percent deduction, net status applies twenty percent, and the higher rate of thirty percent applies to subcontractors who are not verified or whose details cannot be matched. The verification is done with HMRC against the subcontractor's UTR before each payment, and the rate that HMRC returns is the rate that applies — past verification results do not carry over automatically. The deducted amounts feed the contractor's monthly return, and the mechanics of preparing the CIS300 monthly return from subcontractor invoices cover what the contractor then files and how the deductions reconcile to the AP record.

Previous payments. Deduct the cumulative total of all amounts already certified and paid to the subcontractor on prior valuations under this subcontract. The figure to use is the figure from the contractor's own payment ledger, not the figure in the AfP's "previously paid" column. Subbies sometimes state previously paid amounts incorrectly — occasionally because the AfP was prepared before a payment cleared, occasionally because of a genuine reconciliation gap, sometimes because the figure has been tilted to inflate this period's claim. The contractor's ledger is the record that matters, and the discipline of coding construction supplier invoices for accurate job costing is what keeps the subcontract payment ledger and the retention ledger reliable month to month.

Current payable. Subtract retention from gross cumulative; subtract CIS on this period's labour element; subtract the cumulative previously paid amount. The remainder is the current payable. That figure is what the Payment Notice certifies, and it is the figure that gets compared against the subcontractor's claimed amount when the notice decision is made.

Payment Notice or Pay Less Notice: the decision at the assessment desk

With the current payable settled, the QS now compares it against the AfP's claimed amount, and the decision branch is straightforward. If the assessed sum matches the AfP claim, issue the Payment Notice for the assessed sum and that is it — no Pay Less Notice required. If the assessed sum is lower than the claim, issue a Payment Notice for the assessed sum and a Pay Less Notice for the same sum, with its line-by-line basis of calculation. Both notices are needed in the lower-assessment case, because they do different jobs: the Payment Notice records what the contractor is paying, and the Pay Less Notice formally substantiates why it is less than the notified sum the AfP would otherwise crystallise into.

The two notices run on independent clocks against the same payment cycle. The Payment Notice is dated against the Due Date and goes out not later than five days after it. The Pay Less Notice is dated against the Final Date for Payment and must reach the subcontractor not later than the prescribed period before that Final Date — a prescribed period that is itself set by the subcontract and is typically one to seven days under JCT and NEC sub-contracts. The dates should be calendared against the specific subcontract clauses, not against a remembered figure, and on a portfolio of subcontracts let on different terms it is worth calendaring the dates per subcontract rather than running a single project-wide deadline.

The consequence path is what makes the decision time-sensitive. The Pay Less Notice is the only document that can reduce the notified sum below what the AfP would otherwise crystallise: a Payment Notice for an assessed sum lower than the claim does not, on its own, reduce the notified sum if the Pay Less Notice deadline slips. Where the contractor has not issued a Payment Notice at all, the AfP itself becomes the notified sum and the Pay Less Notice is the only remaining route to reduce it. The deadlines on the two notices are not interchangeable.

The contractual hooks vary by subcontract family but the underlying mechanic is the same. Under the JCT Standard Building Sub-Contract and the JCT DB Sub-Contract, the payment-notice and pay-less-notice provisions sit within the section 4 payment clauses and reference the Construction Act regime directly. Under NEC4 Subcontract, the equivalent mechanism sits within the subcontract's payment clauses (the clause 50/51 family, depending on contract option) read together with the Construction Act's Pay Less Notice requirement, which the NEC4 form is drafted to comply with rather than restate. Both contract families implement the same Act mechanic, and the workflow this article walks is the same workflow under either family.

The format of the notices themselves is broadly common regardless of the contract family in use. Each notice identifies the parties to the subcontract, the AfP being responded to, the Due Date, the Final Date for Payment, and the sum the contractor proposes to pay. The Pay Less Notice carries one further requirement that the Payment Notice does not: it must specify the sum the payer considers due and the basis on which that sum is calculated. The basis-of-calculation paragraph is where the Pay Less Notice either holds up under challenge or fails.

Writing the Pay Less Notice basis of calculation, line by line

Section 111 of the Housing Grants, Construction and Regeneration Act 1996 (as amended) requires that a notice of intention to pay less than the notified sum specify both the sum the payer considers to be due on the date the notice is served and the basis on which that sum is calculated. Those two elements are inseparable. A Pay Less Notice that names a sum without setting out how it was calculated does not satisfy the section, and a basis paragraph that does not reconcile to the notified figure does not either. The article's earlier workbook discipline exists to make this paragraph defensible — every assessed line that came out lower than the claimed line goes into the basis, with its measurement reference, its rate source, and its difference set out clearly enough that an adjudicator reading the notice can follow each adjustment back to its source.

A worked basis paragraph reads roughly as follows on a typical month's assessment.

Take Line 12 of the AfP, BOQ item 3.04 — blockwork to ground-floor partitions at the contract rate of seventy pounds per square metre. The AfP claims one hundred and twenty square metres complete to a cumulative value of eight thousand four hundred pounds. Site QS measurement on eighteen April records eighty-four square metres in place at that date, recorded against measurement reference MB-04-18/G-floor. At the contract rate of seventy pounds per square metre, the assessed cumulative value is five thousand eight hundred and eighty pounds. The difference for this line is two thousand five hundred and twenty pounds.

Take Line 18, variation 07 — additional drainage runs to the north elevation at the agreed variation rate of forty pounds per linear metre. The AfP claims thirty-five linear metres at one thousand four hundred pounds. The variations register records the works as instructed under architect's instruction AI-22 dated tenth April; the foreman's docket dated twenty-second April records twenty-two linear metres signed off as complete on that date. At the agreed rate, the assessed cumulative value is eight hundred and eighty pounds. The difference for this line is five hundred and twenty pounds.

Take Line 24, daywork sheet DW-118 — additional plasterboard repairs to the first-floor ceiling. The AfP claims sixteen hours of skilled labour. The signed daywork sheet records twelve hours, countersigned by the site manager on the day the work was done. At the contracted dayworks skilled-labour rate of thirty-two pounds per hour with the eighty percent contractual percentage addition specified in the subcontract, the assessed cumulative value on the verified twelve hours works out at six hundred and ninety-one pounds and twenty pence. The four unsupported hours value at two hundred and thirty pounds and forty pence; that is the difference for this line.

Take Line 31, the materials-on-site claim for ironmongery at three thousand two hundred pounds. The materials are recorded as delivered to the project on the seventeenth April delivery note DN-447, but the subcontract clause permitting valuation of unfixed materials on site requires the materials to be vested in the contractor and stored in the designated secure area, neither of which is recorded against this delivery at the valuation date. The line is assessed at zero pending the contractual trigger; the difference for this line is three thousand two hundred pounds.

The differences across these four lines total six thousand nine hundred and ninety pounds and forty pence, and they add to whatever further differences arise on other lines where the assessed value comes out lower than the claimed value. The headline sum the contractor considers due, against an AfP claim of, say, ninety-four thousand pounds, is the AfP claim minus the line-by-line differences just set out, minus retention applied to the cumulative figure, minus CIS on the labour element, minus previous payments. The basis-of-calculation paragraph in the Pay Less Notice carries each of those line entries explicitly, and the headline figure falls out of them rather than being asserted in advance.

On the question of templates: the pro-forma Pay Less Notice forms circulating in UK construction practice — typically a one-page heading-and-fields layout covering parties, contract reference, AfP reference, the Due Date, the Final Date for Payment, and the sum the payer considers due — are useful for the formal heads. The substance of any notice that will hold up in adjudication, though, lives in the line-by-line basis paragraph. That has to be drafted from the workbook each month against the specific AfP. There is no reusable template for it.

A few patterns of basis paragraph have failed in adjudication and are worth naming. A single global percentage adjustment applied to the AfP claim without line attribution does not satisfy the section: an adjudicator cannot trace the reasoning. A reference to "site progress generally" without measurement evidence on the lines actually reduced does not satisfy the section: the basis must reconcile to specific lines. Omission of lines that were assessed at zero — most commonly the materials-on-site lines and the variation-without-instruction lines — is itself a defect, because a line claimed at value but assessed at zero is itself a difference and needs to appear in the basis. The defensible Pay Less Notice is the one that mirrors the workbook line by line, not the one that summarises it.

The audit-trail fields the assessment workbook needs to defend every certified line

The workbook columns introduced in the loading step are not just for this month's arithmetic. They are the durable record the contractor's representative will rely on if the subcontractor refers a payment dispute to adjudication, and they are what the basis-of-calculation paragraph in any Pay Less Notice ultimately reconciles back to. Each assessed line should carry, by the time the workbook is signed off for the month:

• Contract reference. The BOQ item number, variation number with its instruction reference, daywork sheet number, or quoted-package reference. The reference is what ties the line to the contract document underneath it.
• Claimed quantity and value. Cumulative-to-date as stated on the AfP.
• Assessed quantity and value. The figure the contractor is certifying for that line at the contract rate.
• Measurement reference. The site QS's measurement book entry, digital measure file, or photographic evidence ID — whatever the contractor's representative would need to produce to substantiate the assessed quantity.
• Evidence link. The actual path to the file, document, or record. A measurement reference is only useful if the underlying record can be retrieved; a broken link or a misfiled document is, for adjudication purposes, no record at all.
• Rate source. BOQ, Schedule of Rates, agreed variation rate from the variations register (with the instruction reference), dayworks rate including the percentage addition, or lump-sum percentage complete.
• Retention applied. The retention rate from the subcontract and the retention amount on this line's contribution to cumulative gross.
• CIS treatment. Whether the line is part of the labour element subject to CIS deduction this period, and the verification status applied (gross, net, higher rate).
• Previous-payment offset. The previously certified value on this line, taken from the contractor's payment ledger.
• Current payable contribution. This line's contribution to the current payable after the deductions.
• Signed-off date and signed-off by. The QS or commercial manager who certified the line and the date the certification was made. This is the field that turns the workbook from a working file into a record.

The principle behind the fields is straightforward. If a subcontractor refers a payment dispute to adjudication, the contractor's defence is built from the workbook the QS produced at the time. Every cell that is empty is a cell the adjudicator will read against the contractor — adjudicators routinely treat missing measurement evidence as evidence of an indefensible assessment. Every cell populated with a defensible reference is a cell the contractor's representative can rely on without having to reconstruct the assessment from memory months later.

Two further disciplines sit alongside the per-line fields. First, version control. Each month's assessment is a snapshot tied to that month's valuation date, and the workbook should retain prior-month assessments alongside the current one rather than overwriting them. Adjudicators routinely look at the trajectory across months — was a line being assessed at one quantity for several months and then suddenly reduced? Was an instructed variation valued and then unpicked? Overwriting prior assessments destroys this evidence and removes the contractor's ability to show the subcontractor agreed (by accepting payment without challenge) to the cumulative position at earlier valuation dates.

Second, the contra-charge and dispute log. Where the contractor has assessed a line at zero or at a discount because of defective work, the contra-charge sits on a separate ledger with its own evidence — site reports, remediation costs, photographic records, third-party remediation invoices where rectification was sub-let. The workbook line should reference the contra-charge ID so that anyone reading the basis-of-calculation paragraph in a Pay Less Notice can follow the line through to the contra-charge record without having to ask. A Pay Less Notice that names a contra-charge by amount but does not reference its underlying record is one of the patterns that fails in adjudication.

Read the workbook fields and the version-control discipline together: the assessment workbook is the contractor's single durable record of every certification decision made on this subcontract, and every certification decision needs to reconcile to evidence the contractor can still produce months later. The Pay Less Notice basis paragraph reaches into that record line by line; the workbook is what makes the reach possible.

Where the subbie AfP assessment plugs into the wider commercial workflow

The monthly assessment is one node in a connected commercial-management workflow. Several documents feed into it, and several records pull from it; treating the assessment as standalone is what makes it slow each month, not the assessment work itself.

Upstream, three documents have to be in good order before the assessment can close cleanly. The priced bill of quantities supplies the rates for measured-work lines and defines the BOQ scope outside which work is variation work — and where the priced BOQ only exists as a tender PDF rather than a workable spreadsheet, turning an NRM2 tender BOQ PDF into pricing-ready Excel is the upstream step that has to happen before the assessment workbook can reference BOQ rates at all. The variations register supplies the agreed variation rates and the instruction status for each variation; a line claimed against an unagreed rate or an uninstructed variation cannot be valued against the variations register if the register itself is incomplete. The subcontract sets the retention percentage, the prescribed period for the Pay Less Notice, the dayworks percentage addition, and the materials-on-site clause that determines when unfixed materials value. None of those values should be guessed at the assessment desk; they should be read off the subcontract before the month's first AfP arrives.

Downstream, the assessment feeds four records that the contractor relies on through the rest of the project. The certified payable feeds the project's cost-value reconciliation on the subcontract-liabilities side, where the cumulative liability to subcontractors is one of the main inputs into the project's reported margin — the mechanics of pulling certified AfPs, client certificates, and the purchase ledger into a monthly CVR workbook cover how that liability rolls up at package level alongside earned value and cost to date. The retention deducted feeds the retention-release tracker, which is the document that determines when retention amounts are released on practical completion and on the defects rectification certificate. The CIS deducted feeds the contractor's monthly CIS300 return to HMRC. The certified figures across months form the documented basis of the final-account negotiation at the end of the subcontract — a final account that disagrees with the certified positions across the months without explanation is a final account that has to be reconciled.

The commercial-management point worth holding onto is that the assessment is the place where measurement, contract pricing, deductions, and notices meet. None of those four streams lives at the assessment desk on its own; each lives in its own document or system, and the assessment workbook is the place each meets the others on a monthly cycle. A clean assessment workflow is one where each upstream feeder document is in good order at the start of the month and each downstream record receives reliable data at the end of it.

The line-item extraction discipline that loads the AfP into the workbook in the first place is the same discipline that runs across the construction subcontract pipeline more broadly — supplier invoices, builders' merchant deliveries, plant hire dockets, and subcontractor AfPs all turn into structured rows in the same kind of receiving file, and automating construction invoice processing end-to-end is the cluster view of that discipline applied across the whole document mix. The subbie AfP assessment workflow is one specific node in that wider pipeline, distinguished by the Construction Act notice mechanics that wrap it and by the certification authority of the QS at the desk.