Phase Billing and the Close: FloQast or BlackLine for Architects

A project moving from design development into construction documents mid-month splits revenue across two phases with potentially different fee percentages. If the transition date used for billing doesn't match the transition date the project architect actually recognizes, the revenue recorded for that project will be wrong in a way that's easy to miss unless someone is specifically checking phase transitions as part of the close, not just reviewing total billed amounts.

Printing, travel, and consultant fees passed through to the client at cost, or with a modest markup, have to be tracked against the specific project that generated them and billed back promptly. Reimbursables that sit unbilled for more than a cycle or two quietly become an interest-free loan to the client, and a close checklist that doesn't specifically flag aging reimbursable balances lets that loan grow without anyone noticing until cash gets tight.

A related mistake shows up in how reimbursables get booked in the first place: recording them net against the expense account, instead of gross as both revenue and cost, understates the firm's actual billings. Say a studio spends $18,000 on printing, courier and consultant fees across its active projects in a month and bills all of it back at cost, booking that amount gross, as revenue on one side and cost on the other, which keeps the top line honest. Netting it against the expense line instead makes the studio look smaller than it is, which matters if you're ever presenting financials to a bank, a landlord, or a firm considering a merger.

A studio running a manageable number of concurrent projects, with clear phase-transition dates communicated by project architects, tends to do well on FloQast. Its checklist enforces the phase-billing and reimbursable review as standing monthly tasks without requiring the studio to overhaul its project management approach just to accommodate the close tool.

A firm running many concurrent projects across several offices, or one that regularly partners with outside consultants on joint ventures, benefits from BlackLine's deeper matching once phase-transition and reimbursable volume outgrows what a reviewer can reasonably check by hand each month. The same broader construction-and-design-adjacent sector data that applies to engineering firms is a useful reference point here too: firms in that category average 36 payables days¹, and a design practice running well beyond that is often carrying unreconciled reimbursable or consultant costs rather than a genuinely slower payment culture.

Pick one active project with a phase transition coming up in the next cycle and use it as a live test case for whichever platform you choose. Confirm the transition date, the reimbursable expenses tied to that phase, and any consultant costs all reconcile correctly before rolling the checklist out across the full project list. A single well-tested example gives the team a concrete reference for how the process should look, rather than learning the workflow for the first time across a dozen projects simultaneously.

Steps for a pilot on one project:

1. Pick one active project with a phase transition coming in the next cycle to serve as a live test case.
2. Confirm the phase transition date with the project architect rather than relying on the invoice date.
3. Reconcile the reimbursable expenses tied to that phase, checking whether any have sat unbilled for more than a cycle or two.
4. Tie out the consultant costs for the project against what was billed.
5. Roll the checklist out across the full project list once the test case reconciles correctly.

A project shared with an outside architecture or engineering partner, common on larger civic or institutional work, adds a reconciliation layer where each firm bills its own share and the two sets of books have to agree on the overall project economics even though they're maintained independently. Establish a shared reporting format with the partner firm at project kickoff, not mid-project, since retrofitting a consistent format after several months of divergent tracking is far more disruptive than agreeing on one up front.

A newly hired project architect, especially one coming from a firm with looser financial habits, needs a clear, early explanation of why phase-transition dates and reimbursable tracking matter beyond just good practice. Framing it as part of client trust, since accurate, timely billing keeps a client relationship healthy, tends to land better than framing it purely as an accounting requirement, and it's more likely to actually change behavior.

Pair that conversation with a short, written example, one project walked through from phase transition to billed reimbursable, rather than a general policy memo. A concrete example a new hire can compare their own project against sticks far better than an abstract description of the process.