Real Estate Trust Account Three-Way Reconciliation Guide

Real estate broker trust account three-way reconciliation is the monthly check that three balances agree: the trust account's bank statement balance, the brokerage's internal trust ledger balance, and the sum of every individual client sub-ledger balance. The three numbers must match. Most US state real estate commissions require the reconciliation monthly with a signed worksheet retained on file, and reconciliation deficiencies — missing worksheets, unsigned worksheets, unexplained variances — are among the most commonly cited findings in state audits and a leading cause of license discipline.

The regulator language is unambiguous. The North Carolina Real Estate Commission's monthly trust account reconciliation rule — Rule A.0117(e) — requires brokers to retain a worksheet for each monthly trust account reconciliation showing the balancing of the bank statement, the books (the cash account), and the property trial balance. Other state commissions phrase it differently, but the three-balance shape is the same wherever the rule is written: bank, books, sub-ledger, all agreeing, every month, signed.

This article is the first-week-of-the-month operator's playbook for closing the trust account: extracting the three sources, running the match, investigating each variance to disposition, and assembling the audit package the examiner expects. The monthly trust account reconciliation workflow is mostly about the documents that feed it — the bank statement PDF, the property-management software ledger export, the per-client sub-ledger compilation — and that's where the close is won or lost.

What's at Stake When the Worksheet Doesn't Tie

State real estate commissions audit on two cadences. The first is routine — a multi-year examination cycle that rotates through every active brokerage and every active property-management firm in the state. The second is complaint-triggered: a single client, tenant, or former employee makes a complaint, and an examiner is on the brokerage's books within weeks. Either way, when the examiner shows up, they ask for the trust account reconciliation file for any month inside the look-back window, not just the most recent close. Whatever was produced for September 2024 has to still be retrievable, in full, with the worksheet signed.

The disciplinary fact pattern is consistent across major-state commissions — TREC in Texas, the DRE in California, DBPR in Florida, DOS in New York, NCREC in North Carolina. The two findings cited most often are commingling — operating funds resting in the trust account, or trust funds resting in the operating account — and reconciliation deficiencies, which means missing worksheets, worksheets signed by the wrong party, or variances left unexplained on the worksheet itself. The disciplinary range runs from corrective orders and fines through suspension and, in the worst patterns, revocation. The worksheet is the document the examiner reads first because it tells them, fast, whether the brokerage knew what was in the account and whether anyone signed off on knowing.

Retention follows the same general shape across states even though the specifics differ. Most state commissions require trust account records retained on a multi-year window, commonly between three and seven years. The signed monthly reconciliation worksheet, the supporting bank statement, the supporting trust ledger report, and the supporting sub-ledger balances all live together for that window. Pulling them apart, or losing one, is itself a finding.

The practical implication for the operator is straightforward. The worksheet has to be defensible standalone. Someone — possibly an examiner the broker has never met, possibly years after the close — will read it without the broker in the room, looking for a reason to flag it. Anything obvious only to the person who ran the close that month is a finding waiting to happen.

Source 1 — The Bank Statement: Cleared Balance and the Transaction Ledger

Two outputs come off the bank statement and feed the reconciliation. The first is the cleared month-end balance — and the operator has to be precise about which number that is. The closing balance on the statement is the balance after the last posted transaction of the closing period; the ending balance is the same on most statements but not all; the available balance is a real-time number, often higher, that includes uncleared deposits and excludes uncleared debits, and it is never the right input for a three-way reconciliation. Use the cleared balance the bank reports as of the statement's close date.

The second output is the dated, line-item transaction ledger for the month: every deposit, every issued check (with check number) and every cleared check, every ACH credit and debit, every wire in or out, every returned item from an NSF, every bank service charge, every interest credit, and every sweep into or out of the account. The reconciliation runs against this list, not against a summary.

Pulling those two outputs is rarely difficult conceptually. The pain is in the format. Most banks deliver the statement as a multi-page PDF where the closing-balance line is buried somewhere on page two or three between summary tables and disclosure boilerplate. Statements from regional and community banks often arrive as image-only scans that won't copy-paste. The transaction list inside the PDF varies bank to bank: some present transactions in strict chronological order, some group them by type (deposits, then withdrawals, then fees), and a meaningful minority do both — chronologically in one section and by type in a separate section that subtotals everything. Transcribing that subtotaled section as if it were the transaction list double-counts every transaction in the month.

When the bank offers a CSV or OFX export, the transaction list comes out cleaner than anything that can be lifted from the PDF. But the export is not the document the examiner asks for. The PDF statement is. The export and the PDF have to reconcile to each other before the export gets used for anything downstream — every transaction in the export should match a line on the PDF, every line on the PDF should match a row in the export, and the closing balance on the export should equal the closing balance on the PDF. Once that internal check passes, the export becomes a working file the operator can run filters against.

Reading line items from a multi-page bank statement PDF into a structured spreadsheet is the slowest manual stage in most monthly closes. It is the one place in the workflow where the operator's hours scale linearly with statement length and where every additional bank account multiplies the work. This is where prompt-driven extraction earns its place: a prompt against the bank statement PDF — including image-only scans — returns the dated transaction list as XLSX, CSV, or JSON ready for the reconciliation, with each row referenced back to its source page so the line item can be checked against the original. A prompt as plain as "Extract the dated transaction ledger for this trust account bank statement: date, description, deposit amount, withdrawal amount, check number, running balance" produces the working file in minutes rather than hours, and the same prompt runs the same way on next month's statement and the month after that. We build automated extraction of bank statements and PM trust ledgers for exactly this point in the workflow — the closing-balance and transaction-ledger capture, and the three-source match the rest of the close runs against.

One variance trap routinely lives at this step: a bank service charge or an interest credit that the bank posted on the statement but that hasn't been mirrored to the internal trust ledger yet. The amounts are usually small, the timing is the last day of the month, and the bookkeeper is looking at the GL rather than the statement. Until the charge or the credit is journaled into the GL, the bank-vs-GL match will be off by exactly that amount. Catching it on the bank-statement side, before opening the GL, makes the rest of the close shorter.

Source 2 — The Internal Trust Ledger: GL Balance and Daily Journal

Source 2 is the brokerage's own books. The reconciliation needs two things from them: the month-end internal trust GL balance, and the dated journal of trust-account postings — every deposit in, every disbursement out, every transfer between sub-ledgers, every fee allocation — that produced it. The journal is what gets compared against the bank statement transaction ledger; the GL balance is what gets compared against both the bank's adjusted cleared balance and the sum of sub-ledgers in source 3.

Where each platform exposes those two outputs is well-known to anyone running the close. AppFolio surfaces them in the Property Trust Account report, which gives both the period-end balance and the underlying journal of postings. Buildium calls the equivalent the Bank Account Ledger. Yardi — Voyager or Breeze — produces a trust-account journal under the bank-account ledger view, with the GL roll-up sitting on the same screen. Rent Manager's bank ledger does the same job under different navigation. The same property-management platforms run the AP side of the operation as well; if AP automation has not been built around them yet, AI invoice processing for property management AP is the natural counterpart workflow to the trust-side ledger, sitting on the same software stack.

For brokerages without PM software — small operations running the trust account in Excel or Google Sheets — the spreadsheet has to do the same job the platform reports do. Every deposit and every disbursement gets a row. Every row carries a posting date, the cleared date once the bank confirms it, the amount, the counterparty, and a sub-ledger reference identifying which client, tenant, or transaction the posting belongs to. The GL balance is the running total across all rows; the daily journal is the row history filtered by date. The sub-ledger reference per row is the part operators most often skip — and the part that destroys the reconciliation when source 3 has to be reconstructed at the end of the month, because there is no way to decompose a deposit into its sub-ledger holders if the row never recorded who the holder was.

The most common cause of a bank-vs-GL break in the first day or two of variance investigation is a posting-date issue. A rent receipt deposited on October 31 might appear on the bank statement with a clearing date of November 1, while the GL recorded it on October 31 — or vice versa, depending on the platform's posting convention. AppFolio, Buildium, Yardi, and Rent Manager each have a setting for whether bank postings book on receipt or on clearing, and the answer is not the same across the four. A two-day variance at month-end that exactly matches a single deposit amount is almost always this issue. Knowing the platform's convention before opening the variance investigation saves the time it would otherwise take to chase the deposit across two months of journal entries.

Source 3 — The Sub-Ledger Compilation: Every Client, Every Holding

Every dollar in the trust account belongs to a specific party — a client whose earnest money is sitting against a pending closing, a tenant whose security deposit has not yet been refunded or applied, an owner whose rent collections have not yet been disbursed, a vendor whose retention is being held against punch-list completion. Sum the individual balances of every one of those holders and the total has to equal the trust GL balance. The sub-ledger is the trust account's liability detail: it tells you, dollar by dollar, who the money belongs to. Property management client sub-ledger reconciliation is the third leg of the three-way match, and on most operator's books it is the leg that fails first.

Each major platform produces a report that surfaces the per-holder view. AppFolio's tenant ledger and owner ledger reports together cover the resident and owner sub-ledger holdings, with security deposits broken out separately on the deposit-detail report. Buildium's Property Bank Account Balances report rolls the per-property balances into a summary that has to tie to the trust GL. Yardi's resident trial balance gives the resident sub-ledger view, with security deposits and prepaid balances visible as separate columns. Rent Manager's tenant trust report does the equivalent under different naming. In every case the report is the platform's view of the third balance — every entity holding funds, the balance held for that entity, summed.

Where the third balance commonly breaks is not in the platform's math but in what the operator forgot to add to the sub-ledger compilation. Five categories of holdings fall off systematically:

Security deposits held outside the platform. Many states require security deposits in a separate, dedicated deposit account, and the operator stops thinking of that account as "the trust account" because it has its own bank statement and its own report. The state real estate commission still considers it within scope of the broader trust accounting obligation, and the deposits in that account are sub-ledger holdings that have to appear in the compilation.
Earnest money held against pending closings. Earnest money is often parked in a separate sub-account inside the trust bank account, or in a transaction-specific holding tied to a particular contract. The pending-transaction file knows the amount; the platform's tenant or owner reports may not.
Prepaid rents. A tenant who pays for the next two months in advance creates a sub-ledger liability for the months that have not yet been earned. Some platforms apply prepaid rent to the receivable as if it were earned; some hold it as a liability until the rent period rolls. Either way, the compilation has to count the unearned portion as a sub-ledger holding.
Owner reserves. Property managers commonly hold a minimum reserve on each owner's behalf — a few hundred to a few thousand dollars per property — as a repair float. The reserve is the owner's money sitting in the trust account; it is a sub-ledger balance for that owner and has to appear in the compilation.
Vendor holdbacks. Retention amounts withheld from a vendor pending punch-list completion or warranty period are sub-ledger holdings on the vendor's behalf, not income to the brokerage and not money to be swept. A holdback that is not on the sub-ledger is money the GL counts that the compilation does not.

For each holding, the sub-ledger has to carry a dated, named line — who the holder is, what the balance is, when the holding started, what the underlying transaction reference is. An aggregated total per category, however neatly it sums, is not enough. The auditor's first move on the sub-ledger report is to pick a single client at random and ask the operator to walk that client's history from the first deposit through to the current balance. If the line is not there, the operator cannot answer.

Tying Out the Three Balances

With the three sources in hand, the match is one equation:

Bank cleared balance, minus outstanding checks, plus deposits in transit, equals the internal trust GL balance, which equals the sum of all sub-ledger balances.

When all three numbers agree, the worksheet ties and the close is done. When they don't, the form of the break tells the operator where to look first.

A bank-vs-GL break — bank cleared balance, after timing adjustments, does not equal the GL — is almost always one of four things: a posting-date issue from source 2, a missed bank service charge or interest credit from source 1, a reconciling item that was carried forward incorrectly from last month's worksheet, or an outright posting error. The variance investigation in the next section walks each of these to disposition.

A GL-vs-sub-ledger break — the GL balance equals the bank's adjusted cleared balance, but the sum of sub-ledgers does not equal the GL — is an internal allocation problem on the operator's own books. The most common patterns are a deposit posted to the GL but never allocated to a sub-ledger, a sub-ledger entry that didn't make it to the GL, or a transfer between two sub-ledgers that was recorded once when it should have been recorded twice (a debit on one holding and a matching credit on the other). The bank is not involved in any of these.

A three-way break — all three numbers disagree — is usually a compound problem rather than one large variance. The discipline is to investigate the bank-vs-GL break first, get the GL clean, and then re-test the GL-vs-sub-ledger break against the corrected GL. Trying to investigate both breaks simultaneously is how a four-hour close turns into a two-day close.

Run the match in the same order every month. Bank to GL first, then GL to sub-ledger sum. The variance investigation has a predictable starting point, and the worksheet from one month is comparable to the worksheet from the next.

Variance Investigation: Concrete Moves When the Three Don't Tie

This is the section the SERP doesn't deliver. Most competitors stop at naming the suspects: outstanding checks, deposits in transit, posting errors. The trust account variance investigation that actually closes the books is the one where the operator has the specific filter, the aging cutoff, and the cross-check ready before opening the GL. What follows is the source-by-source playbook — what the variance is, the filter that surfaces it, and the disposition that resolves it.

Outstanding checks. Filter the trust GL for issued check numbers that have no matching cleared-check entry in the bank-side transaction list. Age each by issue date. Anything inside the state's stale-check window — commonly somewhere between 90 and 180 days, depending on the state — is a routine reconciling item; subtract it from the bank cleared balance and move on. Anything outside the window is no longer a reconciling item. The disposition is one of three: contact the payee and re-issue, void the check and re-allocate the funds back to the original sub-ledger holder, or, if the payee cannot be located and the holding is past dormancy, process the holding through the escheatment pipeline. A void without a re-allocation is a commingling event waiting to happen.

Deposits in transit. Filter the GL for deposit entries dated in the closing month that have no corresponding bank credit before the statement's cut-off. Add them to the bank cleared balance for the worksheet. The next move is the discipline that catches problems early: look at the first week of the next bank statement and confirm each in-transit deposit cleared. Anything still uncleared five business days into the new month is no longer a timing item — it is either a deposit that was prepared but never delivered to the bank, a deposit that was lost in transit, or a posting error. Flag it for follow-up before treating it as in-transit on next month's worksheet.

Posting errors. Reconcile the GL daily journal totals by date against the bank deposit and disbursement totals by date for the closing month. The simplest version is a two-column comparison: total of GL entries on October 7 vs. total of bank line items on October 7. Most days will agree; the days that don't are the candidates. For each flagged date, walk the GL postings against the bank line items one transaction at a time. The errors fall into a small number of shapes: an amount mis-keyed by a transposed digit, a deposit booked twice, a check posted to the GL that was never written, or a bank line that was never journaled. The disposition is to journal the correction and document it in the worksheet's variance explanations.

Unallocated receipts. Filter the bank deposit list for receipts that posted to the GL but that have no corresponding sub-ledger posting — a deposit went into the trust account, the GL recorded it, but no specific client or transaction got credited. Trace each one. The usual sources are a tenant payment received without a unit identifier, a partial earnest-money wire received before the contract was logged, or a settlement receipt whose allocation paperwork came through later. When the holder can be identified, post the allocation. When the holder cannot be identified within the close window, age the receipt as an unallocated balance and surface it for the aged-balances review described later in this article. Unallocated receipts that age past the state's dormancy window have to be reported and remitted to the unclaimed-property administrator — they are not the brokerage's money to keep.

Fee sweeps. Identify any management-fee or admin-fee sweep that moved funds from the trust account into the operating account during the month. For each sweep, confirm two things. First, that the sweep was authorized — that the fee had actually been earned per the management agreement and was allocable to a specific client or property. Second, that the sub-ledger of the originating client carries the matching debit so the sub-ledger total drops by the swept amount. A sweep that took money the brokerage hadn't yet earned is an unauthorized sweep, which is a commingling event regardless of whether anyone called it that. Disposition: reverse the sweep back into the trust account and re-take it once the fee is genuinely earned and allocable.

Timing differences. A deposit dated October 31 that clears on November 1 is benign timing — note it as a deposit in transit, add it to the bank cleared balance, expect it to disappear from next month's worksheet. A deposit dated October 31 that does not clear in any subsequent statement is not a timing difference. It is either a deposit that was never made — investigate the receipt, the deposit slip, and the courier — or a posting error on the GL side that has to be corrected. The distinction matters because operators who have been treating a "timing item" as benign for three consecutive months are by definition no longer looking at a timing item.

NSF returns, bank service charges, and interest credits. Cross-check each bank-side line item against the GL. A returned tenant check on the bank statement that was never reversed on the GL leaves the GL overstating the trust holdings by the returned amount and the originating tenant's sub-ledger overstated as well. The correction has to journal the reversal and reduce the tenant's sub-ledger holding. Bank service charges and interest credits — small, end-of-month, easy to miss — almost always need to be journaled into the GL before the worksheet ties; the bank already posted them, so the variance is on the operator's side, not the bank's.

Document each variance and its disposition in the worksheet itself, in a column the auditor can read in order. The disposition column is what the examiner reads first when they reach the variance section, and a worksheet whose dispositions read clearly tells them, faster than anything else, that the broker knew what was in the account and resolved each item on its merits.

Assembling the Audit Package the Examiner Expects

Once the worksheet ties, the close is not finished — the artefact the examiner asks for is a package, not a worksheet alone. Wording differs between the major-state commissions, but the real estate trust account state audit package they each request shares the same shape. Six documents go in:

The signed reconciliation worksheet, dated, with the variance dispositions in their own column
The supporting bank statement for the closing month, in full
The supporting trust GL ledger report and the daily journal that produced the GL balance
The supporting sub-ledger balances report — the trial balance — showing every holder and their balance as of close
Variance explanations with disposition for any item that did not resolve within the closing month
A copy of the prior month's worksheet, so any item that carries forward can be traced from one close to the next

The signature is its own gotcha. Many state commissions require the designated broker's own signature on the broker trust account reconciliation worksheet, not the bookkeeper's, not the property manager's, not a delegate's. A worksheet signed by the wrong party is a finding even when every number on the page is correct. The designated broker signs the worksheet because the worksheet is the document by which the designated broker takes personal responsibility for the state of the trust account that month.

The package has to stay together over the retention window — worksheet, statement, GL report, sub-ledger balances, and dispositions all retrievable as one set when the examiner asks for the September 2022 reconciliation, not reassembled from four filing systems while the examiner waits. The same package shape shows up internationally — the Ireland PSRA Section 35 client account reconciliation pack is structurally identical: a periodic three-source reconciliation the licensee produces on demand.

The practical move that turns the package from a scramble into a one-click response is keeping each month as a single PDF. Worksheet, bank statement, GL report, sub-ledger trial balance, and dispositions all merged into one file, named with the brokerage, the trust account, and the closing month, in that order. When the examiner asks, the file goes back as an attachment that day. When the examiner asks for thirteen months at once, the response is thirteen attachments, not thirteen archaeology projects.

What the Reconciliation Should Surface: Commingling and Aged Unallocated Balances

The monthly close is not just a compliance box. It is the brokerage's primary surface for two specific exposures that auditors look for and that the variance investigation, run honestly, will reveal. A trust account commingling check reconciliation worth signing is one whose worksheet shows the operator looked.

Commingling shows up as the result of a variance, not as a separate audit step. Two patterns are worth naming:

Operating-account funds resting in the trust account. Most commonly, the broker's own money used to "fix" a shortfall when the trust account ran short for a disbursement, or to fund a pending transaction before the buyer's wire arrived. License-disciplinary on its face. It surfaces in the variance investigation as an unexplained deposit on the bank side that has no sub-ledger holder — money in the trust account that does not belong to any specific client.
Trust funds resting in the operating account. Most commonly the result of a fee sweep that took more than was earned, or a deposit posted to the wrong account. It surfaces in the variance investigation as a missing GL entry the bank-side ledger expected to find — money out of the trust account on the bank statement, no sub-ledger relief on the operator's books, because the funds went somewhere they did not belong.

The disposition for each is the same shape. Correct the mis-allocation in the same close month if the calendar permits. Document the correction in the worksheet's variance explanations — the explanation column is where the designated broker's account of what happened lives, and an unexplained correction is itself a finding. Surface anything material to the designated broker for sign-off; the worksheet does not become defensible until the broker has actually signed off on it.

Aged unallocated balances are the second exposure the close should surface. Sub-ledger items whose holders cannot be identified, or whose holders have been unreachable for an extended period, age past the state's dormancy window — typically a multi-year window depending on jurisdiction and the type of holding (security deposits, earnest money, and unallocated receipts each have their own dormancy treatment in many states). Once aged past the window, the balances are no longer the brokerage's to keep in the trust account. They have to be reported and remitted to the state unclaimed-property administrator under that state's escheatment program. Holding them indefinitely against the day the holder might reappear is not a compliant disposition.

The AP side of the operation runs the analogous discipline against stale vendor checks and unclaimed credits — the same surface, the same pipeline, applied to a different document set. Operators running both sides of the brokerage's financial close benefit from working from the AP escheatment workflow for stale and unclaimed balances as a model: the dormancy logic, the holder-due-diligence requirement, the state-by-state remittance cadence, and the documentation discipline are common to both, and a brokerage that runs them as one workflow rather than two has a smaller compliance surface to manage.

The Trust Account's Neighbour Workflows

The trust account does not operate in isolation. Three transactional flows pass through it every month, and each has its own document-extraction and reconciliation discipline that runs alongside the three-way close.

Earnest money flows in from real estate transactions and out at closing. Each pending transaction sits as a dedicated sub-ledger holding from the day the earnest-money check or wire arrives to the day the funds are released to the title company at closing or refunded to the buyer if the contract is terminated. The settlement statement is the source document for both the inflow context and the closing-day disbursement that drains the holding, and the brokerage's own copy of the closing-day disbursement detail has to match the statement issued by the title company. The operational side of that match — pulling line items and earnest-money entries off the statement into a working spreadsheet — is its own workflow, covered separately in extracting ALTA settlement statements and earnest-money line items to Excel.

Commission disbursements flow out of the trust account when a transaction closes. The commission disbursement authorization (CDA) — issued by the brokerage and delivered to the closing agent — names the parties to be paid and the amounts each receives. When the closing agent disburses per the CDA, each disbursement clears a sub-ledger holding (the closing's earnest money plus the buyer's funds at closing) and posts a corresponding GL debit. Reconciling the CDA against the disbursements that hit the bank statement is the brokerage-side counterpart workflow to the trust reconciliation; both close on the same set of bank-statement transactions but answer different questions. The brokerage back-office side of that match — reconciling each CDA against the title company wire and the agent split sheet through to month-end close — is its own monthly close discipline that runs alongside the trust three-way.

Owner draws flow out of the trust account on the property-management side every month. The rent collected on each owner's properties, less management fees, less repairs, less reserves, becomes the owner's draw — disbursed on the owner-statement run. The owner statement is the source document for both the disbursement amount and the matching sub-ledger reduction. Across a multi-property portfolio, the owner-statement run produces dozens or hundreds of disbursements in a single batch, and consolidating AppFolio, Buildium, and Yardi owner statements into a portfolio spreadsheet is the working file the broker reconciles against the trust GL on the same close cycle.

Each of these neighbour workflows has its own extraction and reconciliation rhythm, and each produces transactions the trust reconciliation has to absorb. The close-of-month operator who runs all three benefits from working from the same source-document discipline across all of them — bank statements, settlement statements, CDAs, and owner statements all converted into the same kind of structured working file, all reconciled on the same monthly cadence, all kept together in the same audit-package retention.