Reconcile Conveyancing Search Fee Invoices to a Matter Ledger

When a legal cashier sets out to reconcile conveyancing search fee invoices to matter ledger postings, three things have to land at once: each invoice line matches the correct matter, each component carries the right VAT treatment, and each posting hits a destination ledger that will reconcile under the SRA Accounts Rules. None of those is independently difficult on a clean line. The work, and the time, is in the lines that resist all three.

The VAT step changed in late 2020. HMRC withdrew the postal concession on property search fees from 1 December 2020, so the long-standing habit of treating postal search fees as outside-the-scope disbursements no longer holds. The dedicated VAT section below carries the source and the practical splits; what matters at this point is that a single search-pack invoice rarely has a single VAT treatment, and the cashier has to recognise that before any line touches a ledger.

The starting point for this article is that the rows are already on the desk. Whether they were keyed manually, exported from a search-pack vendor's portal, or produced by AI-powered invoice data extraction that converts the supplier PDF into a structured spreadsheet, the question is no longer how to capture the data. It is what the cashier does with it.

The hard work concentrates in the exceptions. Inconsistent or malformed matter references, property addresses buried in description fields, mixed-VAT search bundles posted as a single line, duplicate-looking charges where a closed-loop integration has already posted the same item, and lines that do not map to any live matter at all. Generic ledger-reconciliation guidance has nothing useful to say about any of these. The rest of this article walks each in the order a cashier will hit them.

Match Each Line to the Right Matter Before Anything Else

Matter matching is the first hard problem on a search-fee batch, not the easiest. Search suppliers format invoices for their own systems, not for the firm's matter file structure, so the fields a cashier actually needs to identify a matter — the firm's internal reference, the client surname, the property address — rarely sit in clean columns. They sit in description text, line notes, and free-text reference fields, and the cashier's first job is to reassemble them into a working matching key.

The realistic failure shapes are predictable enough to recognise on sight:

• Matter references absent or malformed: truncated to fit a supplier's column width, prefixed with the supplier's own job number, or carrying the firm's old reference style from before a case-management migration that is still leaking through.
• Property addresses embedded in description fields, with the postcode separated from the street name or appearing only in a line footer the supplier treats as decorative.
• Client surname mismatches because the search was ordered against the buyer's full legal name and the matter is filed against a shortened spelling, a known-as form, or the surname of a co-buyer.
• Batched invoices that cover several matters in one document, with no consistent grouping and a single supplier total at the foot.

Source data quality dictates downstream effort. A row arriving with an empty or wrong reference field is a reconciliation problem before anything else has happened; the cashier ends up doing per-line forensics instead of per-line posting. The realistic answer to most of this lives upstream, where the fields are first captured, rather than at the cashier's desk. A workflow that can extract conveyancing disbursement invoices into a clean spreadsheet and normalise references, addresses, and component splits before the rows ever land in the ledger system is materially less work than a workflow that does not.

When a line will not match cleanly, the practical first move is to read the fields together, not in isolation. Description text plus reference plus address fragments will usually identify a candidate matter where any one of them in isolation would not. Confirm the candidate against the case-management record before posting: open searches on a live matter, the property address as recorded against the file, the client name on the matter file. If the match is still ambiguous after that, set the line aside as an exception and post the rest of the batch around it. A line forced through into the ledger and reversed two days later costs more time than the line that waited on the exception list.

VAT Treatment After the Brabners Withdrawal

The current position on conveyancing search fee VAT treatment dates from late 2020. HMRC's Revenue and Customs Brief 6 (2020) on VAT treatment of property search fees withdrew the postal concession from 1 December 2020, ending the long-standing practice of treating postal search fees as outside-the-scope disbursements. After that date, postal and electronic search fees recharged to clients are generally part of the firm's legal supply, with VAT applied at the firm's rate. The SRA disbursement test is the surviving narrow path under which a search fee can still be passed through outside the scope of VAT.

Operationally, the consequence is that a typical search-pack invoice does not carry a single VAT treatment across the document. The local authority search component, the CON29 enquiries, the LLC1 land charges register, water and drainage, environmental and chancel reports, and HMLR statutory fees can each behave differently. Some, chiefly the HMLR statutory fees, pass through outside the scope. Others are recharged supplies that attract the firm's VAT. Posting the whole bundle as a single VAT-free disbursement out of habit produces incorrect ledger entries and a quarter-end VAT return that will not tie back to its underlying postings.

The control point sits before posting, not after. When a search-pack invoice arrives, the cashier needs the per-component split on the line before any line touches a ledger. Whatever the supplier's invoice claims at the bundle total, the matter ledger has to record each component on its own footing. Where the supplier does not break the components out itself, and many do not, the cashier reconstructs the split from the supplier's tariff or from the firm's standard search-pack composition, and posts against that reconstruction.

The SRA disbursement test is the framework that decides which destination each component takes. For a fee to qualify as a true disbursement passed through outside the scope of VAT, the firm has to be acting as the client's agent in incurring the supply, the client has to be the recipient of the supply, and the firm has to pass on the exact amount with no margin. Where any of those conditions fails, the line is a recharged supply: the firm bears the VAT input on its purchase, charges the client the firm's VAT-inclusive rate, and the line books to the office account rather than the client account.

Posting the Disbursement to Client and Office Ledgers

The legal cashier search fee posting decision starts with one question per component: does the line meet the SRA disbursement test or not? A true disbursement, where the firm is incurring the supply as the client's agent and passing on the exact amount, posts against the client account on the matter with no VAT applied by the firm. A recharged supply, where any of those conditions fails, posts against the office account at the firm's VAT-inclusive rate, and is then billed to the client through the matter bill rather than directly through the disbursement ledger. The two postings look different, and the evidence that has to attach to each looks different too.

The practical sequence per component is straightforward once the destination is decided. The cashier identifies the destination based on the SRA test, posts the line against the matter ledger with the supplier's invoice number recorded against it, attaches or references the source invoice page so the entry can be retrieved on demand, and records the VAT treatment alongside the line so the rationale is recoverable on inspection. None of that is novel for an experienced cashier. What trips firms up is doing it inconsistently across components on the same invoice.

The per-component split done at the VAT step matters here, not back there. A single search-pack invoice can produce postings in both directions on the same matter ledger: the HMLR statutory fee passes through to the client account as a true disbursement, the local authority search component books to the office account as a recharged supply at the firm's VAT rate, and a chancel or environmental report sitting in the same bundle takes whichever destination its conditions support. The cashier is not posting the invoice. The cashier is posting the invoice's components, and they do not all go to the same place.

A line that reads "search fees" with no breakdown is a future reconciliation problem, even if it ties out today. Every posting should carry enough on its face to reconstruct the decision: which supplier, which invoice, which component, which VAT treatment, which destination ledger. When a reviewer or an SRA inspector pulls the line a year later, that information either lives in the ledger entry or it lives nowhere accessible.

This sits inside a broader law firm accounts payable workflow with matter-level coding discipline that conveyancing-finance teams already run for non-search disbursements: counsel's fees, court fees, expert reports, statutory company filings. The conveyancing search-fee posting follows the same principles, with the post-Brabners VAT split as the conveyancing-specific complication. A firm that is disciplined about matter-level coding on the rest of its AP cycle has most of the infrastructure already; what it needs is the per-component split on the search-fee side specifically.

Exception Types and How to Clear Them Without Audit Noise

The happy path posts itself. The cashier's value is in the lines that do not, and search pack invoice exception handling is where that value lands or fails to. The exception types below are the ones a UK conveyancing-finance team sees on every batch. Resolved well, they leave a defensible audit trail and a clean ledger; resolved badly, they create the kind of quarter-end reconciliation breakage that costs days to unwind.

Inconsistent or malformed matter references. Where the reference field is unusable — a free-text note from whoever ordered the search ("Mr Patel new build"), or just a property address standing in for a missing reference — cross-check the property address and the case-management record's open searches against a candidate matter, confirm the match before posting, and treat the supplier-side reference as supporting evidence rather than the matching key. Audit-noise risk: posting against the supplier reference verbatim creates an entry that does not link back through the firm's own matter file structure, which is the structure an SRA inspector will be looking through.

Property addresses embedded in description fields. Where the address is fragmented across description text, the reference field, and line notes, read those fields together, normalise the address into a single record (street name, building number, postcode together) before matching, and where the firm runs extraction software, treat description-field cleanup as something done upstream rather than at the cashier's desk. Audit-noise risk: a matter ledger line that records the address fragment the supplier surfaced most prominently, rather than the property address as recorded against the matter, will not match a property-address query later.

Mixed-VAT search bundles posted as a single line. The invoice bundles a local authority search with HMLR statutory fees and an environmental report; the supplier shows a single VAT figure at the bottom; the bundle total ties to the bank payment. Resolution: split the bundle into its components, identify each component's VAT treatment per the post-Brabners position, and post each component separately to the matter ledger. The single bundle line is almost always wrong, even when it ties to the bank, because the VAT treatment underlying the total is not uniform across the components. Audit-noise risk: a bundle posted as a single client-account disbursement misclassifies the recharged-supply components, and the firm's VAT return for the period stops tying back to the postings that fed it.

Duplicate-looking charges. The same search appears twice: once on the supplier invoice that has just landed, and once as a posting from the case-management or search-platform integration that recorded the charge when the search was originally ordered. Resolution: identify the source of the duplicate first. A parallel posting from a closed-loop integration is a duplicate to be reversed; a genuine re-order of the search after the first attempt failed is two separate chargeable events. Retain the line that ties to the underlying supplier evidence, reverse the duplicate, and document the decision against the matter so a reviewer does not flag it later as a missed reconciliation. Audit-noise risk: leaving both lines posted overstates the matter's disbursement total, and reversing the wrong line breaks the supplier-invoice tie-out.

Lines that do not map to a live matter at all. The matter has been closed, the instruction was withdrawn before completion, the buyer pulled out, or the supplier billed against the wrong job. Resolution: identify which case applies before deciding the route. A closed matter that still owes the disbursement gets the posting through whatever closed-matter resolution route the firm runs (typically reopened briefly, posted, billed, reclosed); a withdrawn instruction with the search already incurred either gets billed to the client where the engagement letter supports it or is written off against the firm; a supplier billing error gets a credit request raised with the supplier and the line held off the ledger until the credit lands. Audit-noise risk: forcing the line onto an arbitrary live matter to clear the exception list is the worst outcome of the set, because it puts a charge against a client who never authorised it and creates a dispute the firm has to unwind from a position of having posted incorrectly.

Bundled batches that span multiple matters. A single supplier invoice carries lines for several matters, sometimes with no matter identifier on individual lines and a single grand total at the foot. This is closer to the panel-conveyancer billing pattern than the single-matter search-supplier pattern, and the article on consolidated panel conveyancer invoice extraction covers the upstream side of getting per-matter rows out of these documents. Resolution: decompose the invoice into per-matter postings before any line touches a ledger, treat the supplier invoice number as a parent reference each child posting cites, and reconcile the sum of the child postings back to the parent invoice total before signing off the batch. Audit-noise risk: per-matter postings whose sum does not reconcile to the supplier invoice total leaves the firm unable to evidence what it actually paid for, which is the question every supplier-statement reconciliation eventually asks.

For most firms, a portion of these exceptions is reducible upstream rather than in the cashier's worklist. Prompt-based invoice extraction, where the user describes in plain language what the AI should pull and how, can normalise matter references and split mixed-VAT bundle components into separate rows before the data lands on the cashier's desk. That is not a complete answer to exception handling — supplier billing errors, withdrawn instructions, and duplicate-looking charges from closed-loop integrations all still need cashier judgment — but it removes the failure modes that come from the document's shape rather than from the underlying transaction.

Reconciling Against the Case Management or Search Platform

Matching invoice lines to matters and posting them with the right VAT split is the per-line discipline. The matter ledger reconciliation conveyancing teams run beyond the per-line level is the per-batch discipline that confirms the firm was billed for what should have been incurred, not just that what was billed was posted somewhere reasonable.

The closed-loop case is the simpler one. Where the firm orders searches through an integration that posts charges back to the matter automatically — LEAP and InfoTrack are the names that come up most often in the UK conveyancing market, but the pattern applies to any case-management system with a search-supplier integration — the reconciliation runs against the integration's own record. The supplier invoice should match line-for-line against what the integration ordered and posted; lines that diverge are the ones that need attention. The exceptions worth surfacing are searches ordered outside the loop (manual phone or email orders the cashier knows happened but the integration did not record), and lines where the integration's posting and the supplier invoice disagree on amount or VAT, usually because the supplier's tariff updated after the search was ordered, or because the integration made a VAT call the post-Brabners position would now revisit.

The manual case is where most of the work sits in firms that do not have a closed-loop integration on every search supplier. The reconciliation runs against the case-management system's open-search log, or against the firm's internal search-ordering record. The cashier confirms three things on each invoice line: that there is an authorised search request on a live matter the line corresponds to, that the amount on the invoice matches the expected supplier rate within an agreed tolerance, and that nothing in the supplier's batch is unaccounted for relative to the firm's own ordering record. The control points for the manual case are the ones the closed-loop case automates: a per-matter reconciliation report at month-end covering ordered, billed, and posted; a flag against any invoice line that cannot be tied back to an authorised search request; and a tolerance threshold below which the cashier accepts the line and above which the cashier queries it with the supplier.

Whatever the setup — closed-loop, manual, or hybrid — the reconciliation question is the same. Can the firm answer "did we get billed for the searches we should have been billed for?" with evidence, on demand, for any matter in the period. The discipline does not end at the search-fee step. The conveyancing matter ledger reconciles back against several other documents over the life of the matter, including UK completion statement data extraction at the closing point, where the per-matter ledger has to tie out to the statement going to the client. The same per-matter audit-trail discipline supports both reconciliations.

What the Matter Ledger Should Look Like at Month End

The test for SRA reconciliation conveyancing disbursements at period close is operational, not theoretical. Any reviewer should be able to take a search-fee line on a matter ledger and trace it back through four links: the supplier invoice it came from, the VAT decision applied to it, the destination ledger (client or office) the decision points to, and the authorised search request on the matter that justified incurring the cost in the first place. Where any of those links is missing on a line, that line is the reconciliation problem to fix before sign-off, not a line to live with through to next quarter.

The per-matter check is where the trace runs. Every search-fee posting on the matter has a supplier invoice line behind it, a VAT treatment recorded against the line, a posting destination consistent with the SRA disbursement test outcome for that component, and an audit reference back to the supplier invoice page or supplier reference. If any of those is absent, the line either gets the missing detail filled in from the source documents or gets reversed and reposted with the detail attached. Leaving a partially-evidenced line in place because it ties out at the total level is how reconciliation breaks at quarter-end, when a question on a single line cannot be answered without going back to documents that may by then be hard to retrieve.

The per-supplier check runs in the other direction. Every supplier invoice in the period is fully posted across the matters it covers; bundle splits reconcile back to the parent invoice total; any line not yet posted carries an exception status with a documented reason, whether a credit awaited, a matter resolution pending, or a duplicate under review. A supplier whose invoice total in the period does not reconcile to the sum of postings against it is the easiest reconciliation breakage to spot and the most embarrassing to leave unaddressed at sign-off.

The per-period check rolls up. The client account and office account reconciliations on conveyancing matters tie out to the underlying postings; no client-account postings sit in suspense waiting on a matter resolution that has been forgotten; the exception register at sign-off lists each open item and its resolution path with a name against it. This is the SRA Accounts Rules control environment expressed as a working closing checklist rather than as a regulation: the rules are the standard, but what defends the ledger on inspection is the closing discipline that produced it.

The same per-matter audit trail that supports SRA reconciliation also supports cost recovery. Firms that track recoverable legal disbursements by matter on the litigation side use the same evidence chain — supplier invoice, posting, matter, justification — to support recovery against the paying party. The conveyancing search-fee posting that meets the SRA Accounts Rules test for inspection is also the one that supports recovery from the client without dispute.