A practice's money across long projects
An architecture practice runs on a timescale that makes ordinary bookkeeping awkward. A project can take years. Fees arrive in stage payments tied to RIBA-style work stages rather than months. Costs — consultants, printing, planning fees, models, site travel — land unevenly, and many of them are spent on the client's behalf and rebilled later.
The bank statement records all of it and, being a PDF, tells you none of it. FlowParse converts it with AI — every transaction with date, description, signed amount and running balance — and validates the total against the closing balance the bank printed.
What you get is the practice's money as data: what came in, on which project, what went out, on what, and how the whole thing looks across a year rather than a month.
Fees that arrive by work stage, not by month
Architects are paid in stages. A concept design is signed off and invoiced; a planning submission is made and invoiced; construction runs for a year with periodic fees against it. The intervals between payments are long, uneven and dictated by the project rather than by your cash needs.
That makes a single month's bank activity almost meaningless as a signal. Income has to be read against the project it belongs to and the stage it represents, and that is only possible when payments are structured rows with a client reference you can attribute.
Once they are, fee income by project and by stage becomes visible — and so does the gap where a stage was completed, the invoice went out, and the payment never arrived.
Money spent on the client's behalf
Disbursements are the quiet financial risk in a design practice. Planning application fees, printing and plotting, model making, survey costs, specialist consultants engaged for a specific project — these are paid by the practice, out of the practice's cash, and recovered from the client afterwards. Sometimes.
The failure mode is simple and expensive: the practice pays, the cost is never invoiced on, and the money is gone. It is rarely a large sum individually, which is exactly why nobody catches it, and why over a year it can add up to a real dent in profit.
Structured bank data closes that loop. Disbursements are a category with a payee, an amount and a date; recovered disbursements appear as income. What went out and never came back is a filter, not an accident you notice by chance.
Structural, M&E and the consultant chain
Many projects require a chain of consultants — structural engineers, M&E, acoustics, fire, landscape — and depending on the arrangement they are either appointed directly by the client or subcontracted through the practice.
Where they are subcontracted through you, their fees flow through your account, and the margin between what the client is billed and what the consultant is paid needs to actually exist. Where the arrangement is that you merely coordinate, their fees should not be touching your account at all.
Structured payments make the arrangement visible in the numbers rather than only in the appointment letter, and where a consultant has been paid without a corresponding recovery, that is a question worth asking before the project closes.
What FlowParse pulls from a practice statement
Extraction is by meaning rather than by template, so it works with any bank: every transaction's date, the full description including project and invoice references, the signed amount, the running balance and the counterparty where the statement names one.
The description usually carries the project reference — the thing that makes attribution possible — and long descriptions that wrap across several lines are joined back into one field rather than truncated.
Amounts export as typed, signed numbers, so income and cost by project total in a single formula.
How to convert a practice bank statement
Upload the statements
Drop in one or many PDF statements from any bank — digital or scanned.
Let AI extract them
Every transaction is read with its date, description, signed amount and balance.
Check the balance
Opening balance plus transactions is checked against the closing balance the bank printed.
Export and categorise
Download clean Excel or CSV — or a QuickBooks or Xero-ready file.
Whether the project actually made money
The question every practice principal wants answered and few can answer confidently: did that project make money? The fee is known. The costs are scattered across two years of bank transactions, some of them rebilled, some absorbed, plus the salaried time nobody tracked properly.
Structured bank data solves the half that is knowable. Every payment attributable to a project — consultants, disbursements, travel, printing — totalled against the fees received for it, gives you a cash margin per project. It is not a full job-costing system, and it does not capture staff time, but it is dramatically better than a guess.
For a practice deciding what kind of work to chase, that comparison across projects is the most valuable thing in the accounts.
Long projects, patient cash
Long project cycles mean long cash cycles. A practice can be fully committed, with a healthy order book, and still be short of money in the specific month a large disbursement lands before the corresponding stage payment does.
Structured bank data is what turns that into something you can plan around. Money in and money out by month across the whole portfolio shows the troughs before you are standing in one, which is when a facility can still be arranged calmly rather than urgently.
It also shows how much of the practice's working capital is being lent to clients in the form of unrecovered disbursements at any given time — usually more than anyone assumed.
Software, insurance and the fixed base
A design practice carries a distinctive fixed cost base: CAD and BIM licences per seat, rendering and visualisation tools, professional indemnity insurance that scales with fee income and never gets cheaper, studio rent, and the salaries that dwarf everything else.
These are the costs that determine what fee level the practice has to sustain simply to stand still. As categorised rows, the fixed base per month is a total — and comparing it to fee income by month tells you exactly how many project months of cover the practice has.
Professional indemnity in particular deserves its own line rather than being buried in insurance, because it is one of the few overheads that grows as a direct consequence of winning more work.
Invoices out, payments in
Stage invoices go out and payments come back, weeks or months later, sometimes short, occasionally not at all. In a practice juggling several live projects, the invoice that quietly went unpaid is easy to lose.
Converting the bank statement gives you the payments side as clean data, so reconciliation against your invoices becomes a matching exercise. What is outstanding, how long it has been outstanding, and against which project — as a filter rather than a memory test.
Given the size of an architect's stage payments, one overlooked invoice is not a rounding error.
Years of statements in one pass
Projects span years, which means analysing a project means analysing years of bank data. Batch processing takes up to 100 statements at once and merges them into one sheet, with duplicate detection and a source-file reference on every row.
The practice account, the deposit account and any project or client account arrive in a single dataset — which is what a project post-mortem, a year end or a practice valuation actually needs.
Straight into QuickBooks or Xero
The converted statement goes directly into accounting software. FlowParse produces real bank-feed files — QBO, QFX and OFX — with a transaction ID per row so re-importing does not double-post, plus a Xero-ready CSV.
Most useful for the accounts and periods a live bank feed does not reach — an older account, or the early years of a long project that predate your current setup.
Scanned and posted statements too
A project that started five years ago has financial history that may only exist as scans. OCR runs first on scanned and photographed statements, then the AI structures the recognised text and flags low-confidence figures for review.
That old paper statement becomes the same clean rows as a current PDF — which is what makes a genuine project post-mortem possible at all.
Numbers you can price the next job on
Around 98% field-level accuracy on standard layouts, with low-confidence figures highlighted in an editable preview before anything exports.
Every statement is validated arithmetically against the closing balance the bank printed, so a missing disbursement or a duplicated payment is caught rather than quietly distorting a project's margin. That validation matters most here, because the number it protects is the one you will price your next project from.
Practice and client data stays private
A practice statement names your clients, your consultants and your fee levels. Uploads run over TLS, processing is EU-hosted, the original PDF is deleted immediately after processing, and documents are never used to train AI models.
Nothing is retained once your export is produced.
Projects that died, and what they cost
A significant share of architectural work never gets built. Planning is refused, funding evaporates, the client changes their mind at the end of a stage. The practice has already done the work and, depending on the appointment, may or may not be paid for all of it.
Abortive work is a real cost of doing business in this profession, and almost nobody quantifies it. Yet the costs are all there in the bank: the consultants engaged, the planning fees paid, the printing, the site visits — for a project that generated a fraction of its expected fee.
Structured, attributable spend makes that quantifiable. Knowing what abortive work actually cost you last year is what tells you whether your appointment terms and stage fees are protecting you, or whether you are absorbing risk you are not paid to carry.
Work done, not yet invoiced
Because architects invoice by stage, there is always work completed but not yet billed, and it can represent a substantial amount of value sitting outside both the bank and the invoicing system.
The bank cannot tell you what that work in progress is worth — no bank statement can — but it can tell you the other half: what has already been spent delivering it. Costs incurred against a project whose stage fee has not yet been raised are the closest measurable proxy for how exposed the practice is at any moment.
For a principal deciding whether to take on another project, that exposure is the constraint that actually matters, and it is invisible while the spend lives in PDFs.
The long tail of a construction stage
The construction stage of a project can run for years, with fees drawn periodically against it, and it is where administrative attention tends to lapse — the exciting design work is finished, the team has moved on to new projects, and the invoicing becomes an afterthought.
That is exactly when fees go uninvoiced and uncollected. A periodic construction-stage fee that quietly stopped being raised is easy to miss precisely because nothing dramatic happens when it does.
A structured payment history per project makes the gap obvious: the payments were regular, and then they were not. Catching that within a month rather than at the year end is the difference between an invoice and a write-off.
What winning work actually costs
Competitions, invited pitches and speculative proposals are how many practices win the work they are proudest of, and they are almost always loss-making in isolation. The visualisations, the models, the staff hours and occasionally the consultant input are all real spend against a fee that may never exist.
Practices accept that, but very few measure it — which means the cost of business development is one of the largest unexamined numbers in the accounts.
Structured spend attributable to pitches makes it examinable. Total the year's speculative cost against the work it actually won, and you have a conversion economics figure: what it costs this practice to win a project. That number is what tells you whether to enter the next competition, and it is far better than instinct.
Who this is for
Practice principals who want to know which projects actually made money, practice managers chasing unrecovered disbursements and unpaid stage invoices, and the accountants who serve design practices and would rather receive structured data than a box of statements.
If your project margins are currently a matter of opinion, converting the statements is how they become a matter of record.
Convert your practice's bank statements
Upload a statement and get clean, categorised rows — stage payments, disbursements and consultant fees — so project margins become a matter of record.