Running Spend Across Five Clients Without Mixing Up the Bills

A standard expense report groups spend by category, travel, software, meals, which tells you how much the firm spent on flights last month but nothing about which client that travel supported. For a firm billing clients a flat monthly retainer, that might not matter much. For a firm billing hourly or passing through reimbursable costs, it matters a great deal, because a client who agreed to reimburse travel for on-site visits expects that cost itemized against their engagement, not buried in a firm-wide travel total.

Advisors who travel to client sites need to book flights, hotels and local transportation on short notice, and Airbase's card-first model supports that well: a card with a category limit lets an advisor make the booking without waiting on an approval cycle, then tag the transaction to the right client engagement from the card interface. The risk is the same one every card-first system carries: if the advisor forgets to tag the client, or tags the wrong one because they're juggling three engagements that week, the error doesn't surface until someone reconciles it later.

Procurify's request-first flow fits a firm where different clients have genuinely different reimbursement policies, one client covers all travel, another caps it at a per-diem, a third expects pre-approval on anything over a set amount. Naming the client and confirming the reimbursement terms before the purchase clears means the advisor isn't guessing whether a cost will actually get paid back, and finance isn't chasing down which policy applied after the fact.

A firm with two or three advisors, each running one client at a time, can probably get away with a simple client-tag field on a card-first system, because the odds of misattribution are low when nobody is context-switching mid-week. A firm with advisors running four or five concurrent engagements each, which is common once a fractional practice scales past its first few hires, benefits more from Procurify's forced client-naming step, because the volume of small, fast decisions an advisor makes in a single week makes card-tagging errors far more likely.

Some firms leave it to the advisor's judgment whether a given cost is billable to the client or absorbed as firm overhead, on the assumption that the advisor knows the engagement terms best. In practice, advisors are inconsistent about this, one bills a working lunch to the client, another treats the same kind of cost as firm overhead, and the firm ends up with client invoices that don't match what similar engagements charged. A short, written reimbursement policy per client, set at engagement kickoff and referenced in the platform's approval rules rather than left to memory, removes that inconsistency before it becomes a client-facing billing dispute.

The best time to define a client's tag, and its reimbursement terms, is at engagement kickoff, not after the first invoice raises a question the firm can't answer cleanly. Have the engagement letter specify exactly what counts as reimbursable, travel above a certain distance, specific software the client requires access to, meals during on-site visits, and build that into the platform's approval rule for that client from day one. A firm that waits until the first billing dispute to formalize this ends up doing the same work under worse conditions, with a client already questioning the firm's process.

This matters even more when a firm brings on a new advisor mid-engagement. Without a documented, platform-enforced client policy, a new advisor has no way to know that Client A caps travel reimbursement at coach fare while Client B covers business class for flights over four hours, and the first mistake usually becomes the client's first data point about how carefully the firm manages its own operations.

Set up each client's tag in this order:

1. Define the client's tag and reimbursement terms at engagement kickoff, before the first invoice raises a question you cannot answer.
2. Have the engagement letter spell out what counts as reimbursable, such as on-site meals, required software or travel beyond a set distance.
3. Build those rules into the platform, so billability is decided by policy instead of by each advisor's judgment.
4. Issue individual cards with limits sized to each advisor's engagement load, so charges trace to both advisor and client.