UK Letting Agent Client Account Reconciliation Guide

UK letting agent client account reconciliation means proving that money received from tenants into a segregated client account can be traced through the client account cash book, the relevant tenancy and landlord ledgers, approved deductions, and the final landlord remittance. A sound month-end close leaves every landlord statement line traceable to source documents and to the client account itself, not just to a summary figure on a software screen.

In practice, that means the bank balance is only one part of the answer. The reconciliation also has to show that rent received was allocated to the right property and landlord, that deductions such as repairs or management fees were supported, and that the net amount paid out matches the landlord statement and the cash movement from the client account.

That is why a proper letting agent rent reconciliation depends on a wider evidence set than many teams first expect. The working file usually needs rent schedules, client-account receipts, contractor invoices, fee support, landlord statements, remittance summaries, and the relevant bank or client-account exports. Whether the agency works in Reapit, Street.co.uk, PayProp, Jupix, or spreadsheets, the month-end question is the same. If any one of those records is missing, the month-end position may still appear balanced while the supporting trail is weak.

The practical question each month is simple: can the agency explain where every pound came from, why every deduction was taken, and why the landlord received that exact net amount on that date. The rest of the workflow is about answering that question with documents, not assumptions.

What a CMP-compliant reconciliation must prove each month

Client money protection matters here because a letting agent is handling money that belongs to landlords, tenants, or contractors, not operating cash for the agency itself. The reconciliation therefore has to demonstrate more than a bank total. It has to show that liabilities recorded in the ledgers are supportable, that the client account cash book reflects real transactions, and that the bank position matches the accounting trail at the reconciliation date.

In practical terms, a client money protection reconciliation or Propertymark client account reconciliation is testing whether the agency can prove who the client money belongs to and why it moved. That includes rent collected and not yet remitted, deductions approved but not yet paid onward, reserve amounts retained, and any unresolved exceptions that explain why a ledger balance does not immediately clear.

That expectation is not theoretical. Propertymark accountant report requirements state that firms must confirm a reconciliation was completed within the required time frame and test two reconciliation dates by comparing client ledger balances, the client account cash book, and the client bank balance. That point matters because it sets the control standard for the monthly close: a balanced report is not enough if the agency cannot show how the figures were derived.

The same evidence-first mindset appears in adjacent property-account workflows such as UK commercial service charge reconciliation, residential service charge year-end accounts, and Section 20 major works invoice checks, but letting-agent client money adds its own monthly pressure because landlord remittances continue while repairs, fees, refunds, and tenant payment issues are still moving through the account. This article stays focused on that operational reconciliation work, not on scheme membership or legal advice about CMP display obligations.

How to reconcile rent received before you look at deductions

The workflow should start with money in, not money out. Before any landlord payment is treated as reliable, each receipt into the client account needs to be allocated to the correct property, tenancy, and landlord ledger position. If the rent intake is wrong, every later deduction and remittance check is built on a false base.

That is the core of letting agent rent reconciliation. Compare the banked receipts against the rent schedule or receipt report, then confirm that each item has been posted to the right tenancy ledger and rolled into the right landlord balance. A clean position here means the agency can distinguish cleared rent, partial payments, arrears, duplicates, failed collections, and unapplied cash rather than carrying unexplained balances into the remittance run.

Rent run reconciliation becomes especially important when one month contains split payments, late receipts, or corrections that land around the cut-off date. A receipt that appears in the bank on the last day of the month but is posted in the system the next morning can make the bank look ahead of the ledgers. A failed direct debit that was temporarily posted as received can create the opposite problem. Both cases need to be identified as timing differences or reversals, not buried inside a net figure.

At this stage, the target is not to produce a polished landlord statement. It is to create a dependable rent position that can support later deductions and payouts. Once the agency knows exactly what rent belongs to whom, the rest of the reconciliation can focus on proving why the outgoing numbers changed it.

Validate every deduction before landlord money leaves the client account

Once rent has been allocated correctly, the next question is whether every deduction is supported well enough to reduce the landlord's remittance. Repair invoices, compliance charges, management fees, credit notes, reversals, and retained reserves all change what the landlord receives, so each one needs evidence that supports the amount, date, property, and payee.

This is where many reconciliations become weaker than they look. A platform may show that a repair cost was deducted, but the supporting PDF may still be missing, unapproved, or attached to the wrong property. A fee may exist as a summarized line on a landlord statement without a clear fee calculation behind it. Credits and reversals can also distort the net position if the original invoice, correction, and reposting are not kept together in the working papers.

The practical test is straightforward: could someone reviewing the file understand why this deduction hit this landlord account in this month. If the answer depends on memory or on clicking through multiple screens, the deduction belongs in an exception queue until the evidence is gathered. Agencies that regularly deduct supplier costs from rent runs often run into the same document-control problem seen in UK builders' merchant statement reconciliation, where the statement summary exists but the invoice-level support is harder to verify quickly.

For agencies managing overseas landlords, the same evidence trail also supports NRLS deduction calculations and quarterly return records.

This is the point where Invoice Data Extraction can help without overstating its role. The product converts invoices and related financial documents into structured Excel, CSV, or JSON outputs from a prompt-based workflow, and each output row includes the source file and page reference. That makes it faster to check contractor invoices, credit notes, or supplier statements against deduction lines and spot missing support before a landlord payment is approved. It does not replace the agency's client ledger or bank reconciliation. It strengthens the evidence-preparation step that those controls still depend on.

If your wider property workflow also includes sales-side referral or panel billing, the same approach can help standardise panel conveyancer invoice rows in Excel before fee, VAT, branch, and reference fields are checked against internal records.

Match landlord statements, BACS batches, and remittances back to cash

After rent and deductions are validated, the reconciliation still is not finished until the outward payment trail is proved. The net landlord remittance should agree to the landlord statement, the payment batch, and the movement out of the client account. If those three views do not line up, the agency has a reporting problem even if the month-end bank balance looks reasonable.

Landlord payment statement reconciliation is often where hidden issues surface. A statement may show one net amount for a property, while the payment run combines several landlords into a single BACS batch and the bank only shows the total released. The reconciliation has to bridge that gap by tying each statement line back to the underlying rent received, approved deductions, and the specific payment instruction that formed part of the batch.

Letting agent BACS run reconciliation becomes harder when payments fail, are reissued, or are held over a cut-off date. A batch total can still match the bank while one landlord was paid late, one payment bounced, and another remittance was split across two dates. Void periods, refunds, retained reserves, and late credits create the same problem: the top-line batch can appear correct while the landlord-level explanation is incomplete.

For that reason, each remittance line needs its own trail. The working papers should make it easy to answer three questions for every outgoing amount: which rent receipts funded it, which deductions reduced it, and which bank movement or payment file actually sent it. When that chain is clear, the landlord statement becomes a defensible summary rather than a number that only makes sense inside the software.

Build an audit-ready reconciliation pack without replacing your lettings system

The strongest month-end process is usually the one another reviewer can follow without explanation. It gathers the rent schedule, client-account exports, contractor invoices, fee support, landlord statements, remittance summaries, and exception notes into one review pack so an owner, external accountant, or CMP reviewer can see how the month was reconciled without reconstructing it from memory.

That matters because most agencies are working across a mixed stack. One office may rely on Reapit, another may use Street.co.uk, PayProp, Jupix, or a spreadsheet-led process, and the reconciliation problem stays the same across all of them: the documents behind each movement are harder to review than the summary lines in the software. For a broader operational context, the same document discipline sits inside invoice processing for property management.

This is where document extraction earns its place. Invoice Data Extraction lets teams upload invoices and other financial documents, describe what to extract in a prompt, and export structured XLSX, CSV, or JSON outputs with source file and page references. That makes it easier to sort contractor invoices, landlord statements, and related PDFs by property, landlord, amount, or exception status before the final review. For a wider property-finance version of that workflow, see invoice processing for property management.

The boundary is important. A tool like this helps structure evidence and speed review. It does not replace the agency's lettings platform, BACS controls, client ledger, or trust-account procedures. What it can do is make the supporting trail easier to test, especially when the same team is chasing missing PDFs, checking deductions across multiple landlords, or preparing records for an external review.