UK Estate Agency Referral Fee Reconciliation Under DMCC

UK estate agency referral fee reconciliation is the monthly job of tying every line on a consolidated panel-conveyancer invoice to three things: a CRM completion record, the per-seller referral disclosure signed at instruction, and the standard-rated 20% VAT treatment for an introducer-service supply. The output is a register that can answer a Competition and Markets Authority enquiry on demand, line by line, without reconstruction.

Since 6 April 2025 the regime around that register has hardened. The CMA now holds direct consumer-protection enforcement powers under the Digital Markets, Competition and Consumers Act, and the National Trading Standards Estate and Letting Agency Team's Material Information guidance was formally withdrawn on the same date, with its substantive definitions carrying over pending CMA update. Under the CMA's direct consumer enforcement powers under the DMCC Act, the Authority can impose a financial penalty of up to £300,000 or 10% of a business's global turnover, whichever is greater, for substantive consumer-protection infringements. Individual accessory liability is also capped at £300,000. That is the reason the referral-fee audit trail now matters operationally rather than only on paper.

The reconciliation problem sits one layer below the regulatory commentary. The compliance lead already knows DMCC enforcement is live; the operational question is what to do with this month's panel statement on the desk. Each line on it has to clear the three matches independently, because each is a separate audit risk: a billed referral that exceeds the disclosed amount is a live DMCC-enforceable issue regardless of whether the completion is correct, and a referral coded as a disbursement rather than a standard-rated supply is its own VAT exposure regardless of how clean the disclosure is.

Three matching dimensions for every panel-invoice line

Each line on the consolidated panel statement has to clear three separate matches before it can be logged as clean. The dimensions are independent: a line can clear one and fail another, and each failure is its own audit issue.

Dimension 1 — panel-invoice line ↔ CRM completion record. The match keys are the property address, the completion date, the case reference, and the branch or cost centre that took the instruction. The CRM (Reapit, Alto, Dezrez, Street, or whichever the agency runs) is the source of truth on whether a case completed, when it completed, and which branch carries it. If the panel statement names a case the CRM does not show as completed, dimension 1 has failed and the line cannot move forward until the cause is resolved.

Dimension 2 — panel-invoice line ↔ per-seller referral disclosure signed at instruction. The match keys are the fee amount, the fee basis (fixed amount or percentage), and the conveyancer named at the point the seller signed the disclosure. This is the dimension the post-DMCC regime cares about most directly. The Material Information rules require a referral fee to be disclosed to the seller in writing at instruction; if the panel later bills £200 against a disclosure that said £150, the variance is exactly what a substantive consumer-protection investigation will land on. Dimension 2 is the disclosure audit, and it is what makes a panel statement reconciliation in estate agency meaningfully different from any other AP reconciliation.

Dimension 3 — panel-invoice line ↔ VAT treatment on the ledger. Referral fees from a conveyancer panel are a supply of introducer services, standard-rated at 20%. They are not a recharged disbursement, and HMRC's distinction matters here: a disbursement is a payment made on behalf of a client and recharged at cost, whereas an introducer fee is consideration for a service the agency actually supplied. The match is between the gross-and-VAT split on the panel invoice and the VAT code applied on the purchase ledger. A line coded as a disbursement when it should be standard-rated is a VAT exposure independent of whether dimensions 1 and 2 are clean.

The three-dimension match only runs if the input to it is structured. A panel-conveyancer invoice that lives as a PDF, with twenty or two hundred case lines stacked across pages, cannot be reconciled line by line in any practical sense. The reconciliation needs the statement carried as one row per case with, at minimum, the completion date, address, case reference, branch, conveyancer, gross fee, VAT, and total in their own columns. For finance teams who have not yet converted the PDF, our automated panel-invoice extraction for UK estate agency finance teams handles the conversion in a single prompt-driven pass, and the companion article on how to extract a UK estate agency panel conveyancer invoice into per-case Excel rows covers the prompt shape and the column structure the reconciliation depends on.

Walking each line through the reconciliation, case by case

With the framework set, each line on the statement resolves into one of a small number of outcome classes. Pre-deciding what each variance means turns the monthly job into triage rather than re-derivation.

Completed and matched, all dimensions clean. The CRM confirms the completion at the address and date the panel statement names; the disclosure on file matches the billed fee, the fee basis, and the conveyancer; the VAT split on the line is consistent with a standard-rated supply, and the purchase ledger codes it accordingly. Log the line, attach the disclosure reference, code the VAT, mark the register row complete. In a panel relationship that runs cleanly this is the bulk of the statement — usually the great majority of lines fall here, and treating the rest as the work to be done rather than the whole job is what makes the reconciliation sustainable.

Completed but disclosure-mismatched. Dimensions 1 and 3 clear; dimension 2 fails. The signed disclosure said £150 and the panel invoice charges £200, or the disclosure named one conveyancer at instruction and the panel has billed against another. This is the live CMA disclosure-audit case, and it deserves treatment as such. There are usually three causes worth checking: the fee was changed mid-transaction without a re-issued disclosure to the seller, the wrong disclosure was attached at instruction, or the panel has applied a tier the agency was not on. Document the variance on the register row, record the resolution path (re-issued disclosure, panel correction, credit-note request), and keep the paper trail intact. If a CMA enquiry into the period later asks for chapter and verse on a specific case, this is exactly the line that will surface.

Billed but no completion. Dimension 1 fails. The panel has billed against a case the CRM does not show as completed. Three causes are worth distinguishing because each resolves differently. The case may be abortive — sale-agreed-then-fell-through — in which case the panel's billing logic against fall-through varies by panel agreement, and the line gets reconciled against the CRM's abortive record rather than against a completion. The panel may be referencing the wrong case ref, in which case the right CRM record is sitting somewhere else and the line clears once it is matched. Or the CRM may simply have a gap where the completion has not yet been posted, in which case the resolution is on the agency's side. The register row carries the cause, not just the unmatched flag.

Completion but no bill. The CRM shows a completion that should have triggered a referral; the panel statement carries no corresponding line. This is income the agency is owed, and it is worth chasing promptly rather than waiting for next month's invoice to surface it. The disclosure obligation attaches at instruction whether or not the panel ultimately bills, so the audit trail benefits from being closed in-period rather than dragged across statements; a register row with a dimension-1 match and a dimension-2 disclosure on file but no panel line is its own audit signal.

Credit-note netting. A negative line on the panel statement reverses an earlier billed referral, usually because of a panel correction or a refund against an abortive case. Reconcile the credit against its original line by case reference, not by netting the period total — netting at the period total level loses the per-case audit trail and breaks dimension 2 because the original disclosure no longer ties to a specific live billed amount. The register row for the original case carries the credit reference and the resolution; the register does not gain a separate row for the credit itself.

Mid-transaction fee adjustments. The fee changed after instruction — an uplift for a complex sale, a discount, a scope change in what the conveyancer is doing. The clean answer is that a re-issued disclosure should have been signed by the seller at the point the fee changed, before the panel billed against the new amount. If a re-issued disclosure exists, attach it to the register row and reconcile against it. If it does not, the line is functionally a disclosure mismatch under dimension 2 even though the variance is procedural rather than financial, and it goes on the register the same way: variance documented, resolution path recorded.

The referral-fee register that holds the audit trail

The register is where the matched output lives. A workable UK estate agency referral-fee register runs as a single consolidated table with one row per case across all panel providers, not a sheet per panel — because the disclosure obligation is per seller, not per panel, and the same case can carry referral lines from a conveyancer, a mortgage broker, a surveyor panel, and an EPC panel. A per-panel sheet design fragments the audit trail along the wrong axis and makes a case-level CMA enquiry an exercise in cross-referencing.

At minimum the row carries:

• Completion date
• Property address
• Seller name
• Case reference
• Branch or cost centre
• Panel provider
• Conveyancer named on the disclosure
• Gross fee
• VAT
• Total
• Disclosure ID (the reference to the signed document)
• Disclosure-shown-to-seller flag
• Disclosure-amount-matches-billed flag
• Exception class (clean, disclosure mismatch, billed-no-completion, completion-no-bill, credit-note, mid-transaction adjustment, abortive, dual-agency split, franchise split)
• Resolution note (free text, populated when the exception class is anything other than clean)
• Posting reference on the purchase ledger

Carrying the dimensions explicitly as their own columns is what makes the register a true Material Information referral-fee audit trail rather than a list of paid invoices. A row with all three flags green and a posting reference is a closed case from an audit perspective; a row with an open exception class and an annotated resolution note is an open case with its working visible. Most rows sit cleanly in one or the other.

The register has two practical homes. One is alongside the accounting stack as an Excel or Google Sheet, refreshed each period from a structured per-case feed of the panel statement and matched against a CRM export and a disclosure log. The other is extended into Xero, Sage, or QuickBooks via custom fields on the supplier-bill record, with a saved report producing the register view. Either is defensible; the choice is mainly about where the finance team already does its work and where the disclosures are most easily linked from. The non-defensible answer is the register that lives only in the panel-provider's own portal — when the agency leaves the panel, the audit trail goes with it, and the panel's view of any case is in any event only one dimension of the three the register has to carry.

Retention follows the firm's existing document policy. Six years aligned with Companies Act and HMRC record-keeping minimums is a sensible floor for the register itself and for the underlying disclosures, and the disclosures should be linked from the register row rather than copied into it, so that an enquiry can pull any signed document on demand without the register turning into a document store. The register's job is to be queryable; the disclosures' job is to be retrievable.

The agency's reconciliation is one half of a paired audit trail. On the legal-cashier side of the same transaction, the conveyancer is running their own ledger reconciliation under the SRA Accounts Rules — disbursements posted to the matter ledger, client-account postings reconciled against the bank — and the same panel relationship surfaces there as outgoing referral payments rather than incoming income. Finance teams who want the symmetry visible can read across to the conveyancer-side workflow, where the same input-document discipline applies and the article on how to convert UK conveyancing disbursement invoices into Excel rows for matter-ledger posting covers the legal-cashier-side mechanics.

Harder cases a multi-branch agency actually sees

The framework absorbs the routine cases. The harder ones are operationally distinctive but regulatorily identical: each one comes back to whether a per-seller disclosure exists and whether it matches the fee that was actually billed. The register design above carries them as long as the exception class and branch fields are populated.

Sale-agreed-then-fell-through referrals. The case did not complete. Some panel agreements charge no fee against fall-through; others charge a reduced fee, sometimes called an abortive fee. The reconciliation runs against the CRM's fall-through record rather than against a completion record, and dimension 1 is matched as abortive rather than completed. Dimension 2 still applies — the disclosure was signed at instruction regardless of whether the sale completed, so the same disclosure-amount-matches check runs against any fee actually billed. The register row carries the abortive exception class and the date the case fell through, and the case stays on the register rather than being deleted because the disclosure obligation attached at instruction is what audit cares about, not the eventual outcome.

Dual-agency referral splits. Joint-sole and multi-agency arrangements share an instruction across two agencies, and a referral fee can split between them by a pre-agreed percentage. The register row carries the split percentage and the booking entity, and each agency reconciles its own portion against its own disclosure to that seller. From the audit perspective, both agencies have an independent disclosure obligation and an independent register row to maintain — the split is administrative, not regulatory.

Mortgage-broker cross-referrals. The same logical shape repeats. A consolidated invoice from the mortgage-broker panel attaches referrals to specific cases; the same three-dimension match runs against CRM, against a per-seller disclosure (which may be a separate document from the conveyancer disclosure on the same case, signed at the point the mortgage referral was made), and against the VAT treatment. The register absorbs this as another panel provider on the same row set; a single property sale can therefore generate two register rows tied to the same case reference, one for each panel.

Surveyor and EPC referrals. Same logic again: a panel that bills referrals on completed cases, a separate disclosure made to the seller, the standard-rated VAT treatment. The reconciliation moves are unchanged. Material Information platforms — Moverly, MoveReady, mio — sit upstream of all of this in the disclosure-capture stack rather than being panels themselves; treat their records as the source of dimension-2 evidence rather than as another consolidated invoice to reconcile against.

Franchise-network splits. For franchise agencies — Connells, LSL, Spicerhaart, Fine & Country, Arun, similar networks — the booking entity on the panel invoice may be the franchisor or a network booking entity rather than the local branch that took the instruction. The branch and cost-centre column on the register is what holds this together. Match the branch from the CRM record, even where the panel invoice is booked centrally, so the audit trail still resolves per branch when an enquiry asks. A network-level register that loses the branch attribution is not audit-ready in the way a CMA enquiry will need it to be, because the disclosure was made at the local branch and the seller-facing accountability is local.

The pattern across all of these is the same: every variant comes back to whether the disclosure exists and matches, and whether the case can be tied to a branch and a CRM record. Once those are carried on the register, the apparent complexity of multi-branch and multi-panel reconciliation flattens out into the same row-by-row work the routine cases use.

What audit-ready looks like when the CMA asks

Audit-ready is a state of the register, not an aspiration. At any point in the period, a query for a given case reference, address, or seller name pulls one row with every flag populated, every exception class either resolved with a documented note or annotated with the open reason, the disclosure linked to a retrievable signed document, and the line tied to a posting reference on the purchase ledger. When a CMA enquiry into a specific transaction lands, the response is a register pull plus the underlying disclosure, returned within hours rather than reconstructed across statements over weeks.

The practical test of an audit-ready posture is how well it handles the awkward enquiries rather than the routine ones. Three are worth pre-testing internally: the disclosure that does not match the billed fee, the abortive case where the disclosure obligation still attached at instruction, and the franchise-booked invoice where the branch cost centre needs to surface against a network-level booking entity. If the register answers all three without the response team having to leave the table and chase documents from the panel portal or the franchisor's accounts, the workflow is doing its job.

For agencies running both sales and lettings sides, the lettings-side reconciliation runs under a separate regime entirely — the client-account reconciliation on the UK lettings side under CMP and Propertymark rules sits on its own register and its own evidence base, and should be treated as an independent audit trail rather than folded in with the referral-fee work described here.

The reconciliation is the same routine month on month. The register's value compounds as it accumulates resolved exceptions, disclosure links, and ledger references — by the second or third period the response to most enquiries is already a query against an existing dataset rather than an investigation, and the variance classes that needed working out the first time around become triage decisions on the next month's lines.