The job a managing agent is actually doing
A property management company runs somebody else's money through its own bank account. Rent arrives from tenants, deductions come off for management fees and repairs, the balance goes to owners, and deposits sit untouched because they belong to whoever eventually wins the argument about the carpet. None of it is the agent's income except the fee.
That single fact shapes everything about the accounting. The money in the client account is a liability, split across dozens or hundreds of individual owner and tenant balances, and the agent has to be able to prove at any moment which pound belongs to whom. It is the same discipline a law firm applies to client money, applied to a business with far more transactions and far thinner margins.
The bank statement is the anchor for all of it, and it usually arrives as a PDF. Turning that PDF into per-transaction data is the unglamorous step that makes reconciliation, owner statements and audit responses possible — and it is the step that quietly eats a week a month when it is done by hand.
Three-way reconciliation is the exam you sit every month
The control that regulators care about compares three things at the same cut-off date: the trust or client bank statement, the trust ledger in your system, and the sum of every individual owner and tenant ledger. All three must agree exactly. If the bank says £412,880 and the individual balances add to £412,340, somebody's money is somewhere it should not be.
In the United States most state real estate commissions require this monthly, with a signed worksheet retained on file — and reconciliation deficiencies are among the most commonly cited findings in state audits, which is a polite way of saying it is where licences get lost. In England, letting and managing agents have had to belong to an approved Client Money Protection scheme since 1 April 2019, with penalties up to £30,000 for not belonging and up to £5,000 for not displaying membership.
We do not perform that reconciliation, and no converter does — two of the three legs live inside your property management system. What we do is make the first leg workable: every line of the client-account statement as data, with a mathematical check that nothing was dropped in the reading. A three-way reconciliation built on a hand-typed bank side is a three-way reconciliation with an unexamined assumption in it.
One bank line, many properties
The second structural problem is allocation. A single deposit from a payment portal can cover forty tenants across twenty properties, arriving net of processing fees, with the breakdown living in a separate report rather than in the bank narrative. The bank shows one number; your ledger needs forty.
The same happens on the way out. One BACS or ACH run pays fifteen contractors, one transfer moves a month of management fees from the client account to the operating account, and one payment to a utility covers three blocks that each need their share. Every one of those lines has to be exploded into its parts before anything reconciles.
Extraction does not do the exploding — that mapping is your system's job and depends on data we never see. What it does is give you the bank side with dates, amounts, references and narratives intact, so the matching runs against real values rather than against numbers somebody keyed at speed on a Friday.
Tenant deposits are the money you must never touch
Deposits are held, not earned, and in many jurisdictions they must sit in a separate protected account or scheme with strict timelines. They move rarely and matter enormously: a deposit accidentally paid out as part of an owner disbursement is the kind of error that becomes a legal problem rather than an accounting one.
Because they are rare, they are also easy to lose track of in a statement covering thousands of ordinary transactions. Having the full statement as data lets you filter deposit-related lines and prove that the protected balance moved only when a tenancy genuinely ended — which is exactly the evidence an inspection asks for.
What we do not do is tell you whether your deposit handling complies with anything. Protection schemes, timelines and permitted deductions vary by country and by state, and that is a question for your regulator, your professional body or your solicitor, not for a document extraction engine.
Owner statements are your product, not your paperwork
Owners judge an agent on the monthly statement more than on anything else. It has to show the rent received, the date it arrived, the fee taken, the repairs deducted with enough narrative to be believable, and the amount transferred — and it has to survive being read by somebody who has been waiting for their money.
Every line of that statement traces back to a bank movement. When the bank side is data, producing owner statements is a filtering exercise; when it is a PDF, somebody retypes the same figures every month and occasionally transposes one, which produces the most expensive kind of email an agent receives.
The same data answers the awkward follow-up questions instantly — why was this month lower, when exactly did the tenant pay, what was that £340 charge — which is worth more in retained management contracts than the time saved.
How this differs from our landlord and estate-agency pages
Bank statement converter for landlords is written for someone who owns the properties. Their money is their money, the accounting question is profit per property and the tax question is their own. There is no client account and no third-party liability anywhere in it.
Bank statement converter for real estate covers agents and brokers whose income is commission on transactions — a business with lumpy income, split commissions and its own trust questions around deposits on sales, but not the ongoing month-by-month custody of other people's rent.
This page is the third case: you hold, disburse and account for money that belongs to other people, continuously, at volume, under a rule that says the three legs must agree. If you also own properties yourself, read both — but keep the accounts, and the extractions, strictly separate.
The documents this actually involves
It is rarely one statement. A typical managing agent has a client account, an operating account, a deposit account or scheme, and often a card for maintenance spend — plus everything suppliers and utilities send in.
| Document | Why it matters | What extraction gives you |
|---|---|---|
| Client account statement | The bank leg of the three-way check | Every line with date, narrative, amount, running balance |
| Operating account statement | Your own income and costs | A clean set of business transactions, separated from client money |
| Deposit account statement | Money you hold and must not move | Proof the protected balance only moved on tenancy end |
| Card statement | Maintenance and small purchases | Spend by property once you map the references |
| Contractor invoices | Recharges to owners | Supplier, date, net, tax, total and the line detail |
| Utility and service bills | Block and communal costs | Amounts and periods for apportionment |
The monthly workflow
The order matters. Proving the extraction before matching means a discrepancy is a real reconciling item rather than a possible typing error, which is the difference between an hour of investigation and an afternoon of it.
1. Collect
Download every account's statement for the period — client, operating, deposit, cards. PDFs are fine; scans are fine.
2. Convert
Extract each into rows. Multiple months and multiple accounts can be merged into one workbook with the source kept per row.
3. Prove it
Check each statement against its own opening and closing balance before anything downstream touches it.
4. Match
Import or paste into your property system and match against expected rents, fees and disbursements.
5. Explode the batches
Split portal payouts and payment runs into their component owner and tenant entries.
6. Reconcile three ways
Bank, trust ledger, sum of individual ledgers — at the same cut-off, to the penny.
7. Produce and file
Owner statements out, worksheet signed and retained, originals archived in your own storage.
Why a missing row is worse here than almost anywhere
In most businesses a dropped transaction is an accounting annoyance. In client-money accounting it breaks the only control you have: if one rent receipt never made it into the data, the three legs will not agree and you will spend a day looking for a difference that exists in your spreadsheet rather than in your bank.
That is why every statement we extract is checked against its own arithmetic — opening balance plus the transactions must equal the closing balance, per account. When it reconciles, the bank leg is provably complete. When it does not, the statement is flagged rather than quietly handed on.
It is a small thing that changes the character of the monthly close. The question stops being "did we read the statement properly" and becomes "where is the genuine difference", which is the question you were supposed to be answering all along.
Several accounts, several months, one workbook
Agents rarely need one statement. They need a quarter across four accounts, or a year of the client account for an inspection, and they need it in a shape that can be filtered rather than flipped through.
Merging handles that: many PDFs in, one workbook out, with a column identifying which account and which period each row came from. Overlapping periods are deduplicated rather than double-counted, which matters when somebody re-downloads a month that was already included.
Keep client and operating money in separate sheets even when they are in the same workbook. Physical separation in the bank is the rule; visual separation in the working file is the habit that stops somebody accidentally including a fee transfer in an owner's figures.
The management fee transfer, and the double-count it causes
Your fee shows up twice in the world: as a deduction inside the client account and as a receipt inside the operating account. Treat both as income and you have overstated revenue by exactly one hundred per cent — an error that survives surprisingly long because both numbers are real.
The clean model is that the transfer between the two accounts is a movement, not a transaction. Income is recognised once, in the operating account, and the client-account line is a reduction of what you owe the owner. Getting this wrong is one of the most common findings when a new accountant looks at an agency's books.
Extraction does not decide this for you — we return what the statement says, not what it means for your revenue recognition. What helps is having both accounts as data at the same time, so the pairing between an outbound line in one and an inbound line in the other is visible instead of assumed.
The differences that turn up every month
Most reconciliation differences are not errors, they are timing and identification. Knowing which is which before you start investigating saves the single largest block of time in the monthly close, because each type has a different resolution and a different owner.
The table is the short version of what a managing agent meets. Anything not on it is worth documenting the first time it appears, because it will appear again and the note you write today is the answer somebody needs in eleven months.
| Difference | Usual cause | Where it resolves |
|---|---|---|
| Rent received, not in the ledger | Payment reference not recognised | Allocation in your property system |
| Ledger shows rent, bank does not | Payment failed, bounced or was never sent | Chase the tenant, not the bank |
| Bank amount lower than expected | Portal or card fee deducted before payout | Record gross rent, fee as a cost |
| One deposit, many tenancies | Batched portal or lockbox payout | Split using the payout report |
| Payment run out, ledger unchanged | Contractor payments not yet posted | Post from the invoices, then match |
| Fee transfer between accounts | Management fee moved to operating | A movement, not income — recognise once |
| Old uncleared item | Cheque never presented | Investigate and write off with a note |
Arrears look different in the bank than in the system
Every property system has an arrears report, and it is only as good as the payments matched into it. A tenant who paid with a different reference, or whose partner paid from their own account, shows as in arrears while their money sits in your client account unallocated.
Working from the full bank data is how those get found. Filter the period's receipts, match against expected rents, and the unmatched remainder is the list of payments that need a human to identify — usually far shorter than the arrears report suggested and far more useful.
The reverse case matters too: a receipt matched to the wrong tenancy makes one balance look healthy and another look delinquent, and the chase letter that follows is the sort of thing that loses a management contract.
Payment portals net things off before you see them
Card and portal payments arrive net. The tenant paid £950, the platform kept its percentage, and the bank shows £941.30 — a number that matches nothing in your ledger. Multiply that across a portfolio and the reconciliation stops working row by row.
The fix is structural rather than clever: treat the gross rent as the receivable, the fee as a cost, and the net as the bank movement, then match the batch total rather than each line. That requires the payout report as well as the statement, and it requires both as data.
This is the same shape of problem marketplace sellers have, and the reasoning is worked through on bank statement converter for ecommerce if you want the longer version.
Maintenance spend, recharges and the evidence owners ask for
Repairs are where owner trust is won or lost. A £480 line on a statement means nothing; a £480 line with a contractor invoice attached and a property reference means the conversation ends there.
Extracting contractor invoices alongside the bank data is what makes that pairing possible at volume — supplier, date, net, tax, total and the line detail, all as fields you can match to the payment. The invoice PDF to Excel route handles the invoice side, and the two datasets meet on amount and date.
Keep the invoices themselves. We delete originals immediately after extraction, so the PDF an owner may ask to see has to live in your own document storage — the extracted data is the working record, the invoice is the evidence.
What an inspection or audit actually asks for
Whether it is a state commission, a professional body inspection or an accountant's client-money report, the requests are predictable: the reconciliations for a set of months, the statements they were built on, the individual ledger listing at the same date, and an explanation for every difference.
The painful part is never the maths, it is retrieval — finding the statements, proving the listing is complete, and explaining a difference from fourteen months ago that nobody documented at the time. A working file per month, with the extracted data and the signed worksheet stored beside the original PDFs, turns a week of archaeology into an afternoon.
Write the explanation while it is fresh. A reconciling item with a one-line note attached is a finding that closes; the same item with no note is a finding that expands.
Block and service-charge accounting is a different animal
Where an agent manages blocks rather than individual lettings, the money is service-charge funds contributed by leaseholders, often with a reserve or sinking fund held separately and spent on major works years later. The obligations attach to the fund rather than to an owner.
The bank-side work is the same shape — get the statements into data, prove completeness, allocate to the right fund — but the allocation rules come from the lease, not from a management agreement, and the annual accounts have their own form. Keep the operating fund and the reserve strictly apart, in the bank and in the working file.
The parallel with community associations is close enough that the HOA page covers the reserve-versus-operating trap in more detail, including the transfer that people count twice.
Where this sits next to your property software
Most agents run a dedicated system — the ledger, the tenancies, the owner statements, the arrears reports all live there, and that is the right home for them. This is not a replacement for any of it and does not want to be.
The gap it fills is the bank side of accounts the system cannot import: an older account with no feed, a period before the system was implemented, a deposit account at a different bank, statements a client sends you as PDFs when you take over their portfolio mid-year.
Where your bank offers a real feed into your system, use the feed — it comes from the source and needs no reading at all. Converters exist for the four gaps a feed does not cover: history beyond the window, closed accounts, institutions with no coverage, and the months a feed was broken.
The mid-year takeover, which is where the pain concentrates
Taking over management from another agent means inheriting a period you did not record, usually as PDFs, sometimes as scans, occasionally as a printout photographed on a phone. The owner still expects a statement for the full year.
That backlog is a batch job rather than a monthly one: convert everything at once, merge into a single workbook with a source column per row, prove each statement individually, then reconcile the handover balance. Batch conversion does the first part in one pass.
Reconcile the handover explicitly, in writing, with the outgoing agent. The balance transferred, the deposits held and the arrears position at the date of transfer are three numbers that will be disputed later if they are not agreed now — and the extracted data is what makes agreeing them possible in the first place.
The boundary, stated plainly
FlowParse is a document-extraction engine, not property management software and not trust accounting software. There is no rent roll, no tenancy record, no owner ledger, no arrears engine, no owner statement generator and no client-money ledger. It does not perform your three-way reconciliation — two of the three legs live in systems we never see.
It does not tell you whether your client-money handling complies with your regulator's rules, which deposit scheme applies, what your reconciliation deadline is, or how to treat a fee for tax. Those are questions for your professional body, your regulator and your accountant, and the answers differ by country and by state.
And it is not an archive. Originals are deleted immediately after extraction, so the statements, invoices and worksheets an inspection will ask for must live in your own storage. The extracted data is a working record; the bank's and supplier's documents remain the evidence.
A worked example: 340 units, four accounts
A regional agent manages 340 units for about ninety owners, with a client account, an operating account, a deposit account and a maintenance card. Before, the monthly close ran to roughly three days: downloading statements, keying the client account into a spreadsheet to sanity-check the system, chasing two or three differences and then producing owner statements.
The change was narrow. All four statements are converted at once into a single workbook with a source column, each one proven against its own balances, and the client-account rows exported into the format their system imports. The three-way reconciliation still runs where it always did.
The close is now about a day, and the useful part is not the time. Two of the three monthly differences turned out historically to be keying errors in the bank column rather than real reconciling items — and those disappeared entirely, which is what made the remaining differences worth investigating properly.
Where to start
Start with last month's client-account statement and nothing else. Convert it, check the closing balance matches the PDF, and compare the row count to your system's transaction count for the period. Fifteen minutes, and it tells you whether the rest is worth doing.
Then widen to all accounts for one month, and only after that to a quarter. Building the working-file structure — one sheet per account, a source column, the proof recorded — on a small scale is much easier than fixing it halfway through a year of data.
If the immediate problem is a takeover backlog rather than the monthly cycle, invert the order: do the backlog in one batch first, because that is the work with a deadline attached.
Where to go next
For the mechanics of conversion see bank statement to Excel, for many files at once see batch processing, and for merging accounts and periods into one workbook see consolidate bank statements.
For the completeness argument in full, bank statement validation explains what the balance check proves and what it does not. For the invoice side of maintenance spend, invoice PDF to Excel and extract invoice data cover the fields.
Adjacent situations: landlords for your own portfolio, real estate for commission-based agency work, and HOA and community associations for reserve-fund accounting.
Make the bank leg the easy leg
Convert every account for the period, prove each statement against its own balances, and start the reconciliation from data instead of from typing.