Why generic accounting software mishandles an architecture practice

An architecture practice that also supervises construction gets paid twice on the same project, in two different shapes, and almost no accounting software understands that.

Two fees, two behaviours

The design fee is typically a percentage of construction cost, released against stages. It is lumpy, it is front-loaded relative to effort, and it is earned when a stage completes rather than when hours are spent.

The supervision fee runs against time on site — monthly, or against construction progress. It is steady, it continues long after the drawings are done, and it is often what carries the practice's fixed costs.

They accrue differently, invoice differently, and arrive differently. Book them into one bucket and you lose the ability to answer the most important question in the practice.

Which half of my business is actually profitable? A practice that cannot answer that is optimising blind.

What goes wrong in a single-stream system

• Design looks wildly profitable in the months a stage completes and loss-making in every other month, because revenue and effort are in different periods.
• Supervision looks marginal because its costs — site staff, transport, time — are visible while its revenue is a small recurring line.
• Project profitability is a single number that averages two businesses and describes neither.
• Pricing the next project is guesswork, because the last one's outcome cannot be attributed.

The cash-versus-profit trap

A related and more dangerous problem. Profit follows stages completed. Cash follows invoices paid. In a practice with stage fees they drift apart quietly, and by the time it is felt, the fix is a difficult conversation about work finished two months ago.

Any system worth adopting shows both positions at once — earned and received — rather than making you infer one from the other.

What to look for

1. 1Separate fee structures on one project, reported separately all the way through.
2. 2Stage-based revenue recognition, not just date-based invoicing.
3. 3Site costs bookable against the project from a phone, as they happen.
4. 4One cash channel. Every payment should attach to the milestone it settles, so the ledger and the project total cannot disagree.
5. 5A real chart of accounts with vouchers — enough that your accountant works in the system instead of asking you to export it.