Billable Expenses: Why the Money You Spend for Clients Takes Longest to Come Back

The Expense That Is Also Revenue

Most expense claims are pure cost. An employee spends money, the business reimburses it, the cost lands in a department’s budget, and that is the end of the transaction.

Billable expenses are different, and the difference is structural rather than administrative. A consultant flies to a client site. The airfare is reimbursed to the consultant — and, under the engagement contract, recharged to the client. The same transaction is simultaneously an expense and a receivable.

This dual nature is why these claims behave badly. Every other expense has one owner and one lifecycle. A billable expense has two of each, and the handoff between them is usually nobody’s job.

The result is a category of revenue leakage that is almost perfectly invisible. When a rebillable cost is never invoiced, no error is raised. The employee was paid. The cost was recorded. The client was invoiced — just not for that line. Realised margin on the engagement is lower than expected, and the explanation gets attributed to scope creep or estimation error rather than to an expense that fell through a gap.

Where the Handoff Breaks

Five failure points, in roughly the order they occur.

The claimant does not flag it

At submission, the employee is thinking about getting reimbursed. Whether the cost is recoverable under a contract they have probably never read is not a question they are positioned to answer.

If billability is an optional field, it is left blank. If it defaults to non-billable, everything is non-billable. If it defaults to billable, finance spends the next cycle unwinding claims that were not.

The deeper issue is that this is the wrong person to ask. The claimant knows what they spent; the engagement owner knows what the contract permits. Those are different people, and the decision belongs to the second one.

The client reference is wrong or missing

Even when a claim is marked billable, it needs to attach to something: a client, an engagement, a project code, sometimes a specific phase or work package.

Free-text entry produces “Acme”, “Acme Corp”, “ACME — Phase 2” and “acme ph2” across four claims for the same engagement. None of them match cleanly to a project record, so none of them flow automatically into the invoice, and someone reconciles them by hand or not at all.

This is the same structural problem that breaks T&E reporting generally — a reference that should be validated against live master data is instead typed by a human. Keeping project, client and employee records synchronised is a precondition here, not a refinement, and we cover it in keeping master data in sync across ERP and HCM.

The receipt is missing or inadequate

On an internal claim, a missing receipt is a policy issue. On a billable claim, it is a revenue issue.

Most client contracts require supporting documentation for rebilled costs, and clients routinely dispute or withhold payment on expense lines submitted without it. A claim reimbursed to the employee on a card slip may be entirely unrecoverable from the client, which means the business has paid out with no prospect of recovery.

This changes the economics of receipt enforcement substantially. Organisations that tolerate missing receipts on small internal claims — reasonably — should not extend that tolerance to billable ones, where the threshold question is not compliance but whether the client will pay.

The timing misses the cycle

Expenses are invoiced in the billing run that follows their reimbursement, rather than the run that follows the cost.

Combine a three-week employee submission delay with a monthly billing cycle and 45-day client terms, and a cost incurred on the 2nd of March is invoiced on the 30th of April and collected in mid-June. That is three and a half months of working capital consumed by a cost that was contractually recoverable from the moment it was incurred.

Worse, engagements end. A claim submitted after the final invoice has gone out is frequently never billed at all, because reopening a closed engagement to bill a S$300 taxi is more trouble than it is worth. The submission deadline in your expense policy is doing revenue work on billable claims, not just accounting hygiene.

Nobody reconciles unbilled to billed

The final gap is the absence of a check. If no report compares billable expenses recorded against billable expenses invoiced, leakage is undetectable by construction.

The Cash Flow Shape Nobody Models

Billable expenses have a cash profile that differs from every other expense category, and it rarely appears in working capital planning.

Cash out is immediate. Employees are reimbursed on the next payment run — days, and rightly so, because slow reimbursement of out-of-pocket cost is a genuine employee grievance.

Cash in is delayed twice. First by the billing cycle, then by client payment terms.

The gap between those two is real working capital, funded by the business, on cost that was recoverable from day one. For a services firm where travel is a meaningful share of engagement cost, this is not a rounding item — and it is entirely a function of process timing rather than commercial terms.

There is also a margin reporting consequence. If billable expenses are recognised as cost when reimbursed but as revenue when invoiced, engagement margin swings between periods for reasons that have nothing to do with the engagement. Anyone reviewing project profitability mid-engagement is reading a number distorted by billing lag, which is the same period-matching problem that accrual accounting exists to prevent — and which IFAC identifies as a recurring weakness in project-based reporting specifically.

Designing the Handoff Properly

The principle is simple: the claim should carry everything the invoice needs, from the moment it is submitted.

Capture client, project and billability at submission, as validated fields. Not free text, not optional, not derived later. The claimant selects from projects they are actually assigned to, which both constrains the options and makes the selection easy.

Route the billability decision to the engagement owner. They approve the claim anyway in most structures. Make the billable flag part of that approval rather than a separate administrative step, so the person with contract knowledge is making the call.

Apply contract rules automatically. Markup or pass-through at cost, category eligibility, expense caps as a percentage of fees — these live in the contract and should be encoded against the project record, applied to every qualifying claim without anyone re-reading the agreement at invoice time.

Enforce evidence on billable categories specifically. A stricter documentation rule on billable claims than internal ones is not inconsistency; it reflects that a client, not just your own policy, is the audience for the receipt.

Invoice from cost date. Include the expense in the billing cycle following when it was incurred, accruing where necessary, rather than waiting for reimbursement to complete.

Report unbilled billable expenses before every cycle. One report: everything flagged billable, not yet invoiced, aged. Anything aging past a cycle gets a reason. This closes the loop, and it belongs alongside the other metrics in your T&E analytics pack.

Review the write-off decisions. When a billable expense is deliberately not recharged — a goodwill gesture, a client relationship call, a cost that fell outside contract scope — that should be a recorded decision with a named owner, not an omission. The distinction matters because the two look identical in the ledger and only one of them is a management choice. Tracking them separately is what lets you tell a commercial decision from a process failure, and the Institute of Internal Auditors treats exactly this kind of undocumented revenue adjustment as a standard control weakness.

The tax treatment deserves a note. Whether a recharge is a disbursement made as the client’s agent or an onward supply in your own right changes the treatment materially in most jurisdictions, and it interacts with what you can recover on the original cost — see input tax recovery on employee expenses. Set this per contract with your adviser rather than deciding it during invoice preparation.

How Peakflo Helps

Peakflo connects the two halves of a billable expense by running travel and expense management and accounts receivable and invoicing on the same platform, so a claim does not have to cross a system boundary to reach an invoice.

Client, project and billability are captured as validated fields at submission, with the claimant selecting only from engagements they are assigned to, and the billable flag confirmed by the engagement owner as part of the approval they already perform. Contract rules — markup or pass-through, eligible categories, caps against fees — are held against the project record and applied automatically, and evidence requirements can be set more strictly on billable categories than internal ones so a client-facing line is never invoiced without the receipt a client will ask for. Because the claim carries its client reference forward, billable costs flow into the invoicing run keyed on cost date rather than reimbursement date, and an aged unbilled-expense report surfaces anything approaching a cycle cutoff or an engagement close.

To see how much recoverable cost is currently aging unbilled in your own data, request a demo.

Our Verdict: Who Needs to Fix This?

Prioritise this if:

• Travel or third-party cost is a meaningful share of engagement cost and your contracts permit recharge
• Billability is captured as free text, an optional field, or not at all
• You cannot produce a list of billable expenses recorded but not yet invoiced
• Engagement margin regularly comes in below estimate without a clear commercial explanation
• Clients dispute expense lines, which usually indicates an evidence problem rather than a pricing one

Lower priority if:

• You work on fixed-fee engagements with expenses included, where nothing is separately recoverable
• Billable expenses are large, few and individually tracked, where per-item attention is already effective
• Your engagement volume is low enough that a manual pre-invoice check genuinely catches everything

A framing note worth making internally. This is usually treated as an expense administration problem, which is why it stays unresolved — expense teams are measured on processing cost and cycle time, not on recovery. Reframed as revenue leakage, it tends to get attention quickly, because unbilled recoverable cost is margin that was earned and not collected. Professional services guidance from bodies such as the ACCA and IMA consistently treats realisation against recoverable cost as a core engagement metric rather than an administrative one.

Conclusion

Billable expenses fail for an organisational reason rather than a technical one. They belong to two processes, and the boundary between those processes is where the client reference, the billability flag and the receipt requirement all quietly stop being anyone’s responsibility.

Nothing raises an alarm when it goes wrong. The employee was reimbursed. The cost was recorded. The invoice went out. Only the margin is lower, and margin variance is easy to attribute to anything except an expense claim that was never flagged.

Capture the client and the billability at submission, put the decision with the person who knows the contract, enforce evidence where a client will demand it, bill from the cost date, and run one report before each cycle listing what is recoverable and not yet invoiced. None of that is sophisticated. It simply requires someone to own the handoff — which, in most organisations, is precisely what is missing.

Frequently Asked Questions

What are billable expenses?

Billable expenses are costs incurred on a client’s behalf that the contract permits you to recharge — travel to a client site, project materials, third-party services bought for the engagement. They are reimbursed to the employee as an expense and recovered from the client as revenue or a pass-through.

Why do billable expenses get lost before invoicing?

Because they cross two processes that report to different owners. Expense handles reimbursing the employee and considers the claim closed at payment. Accounts receivable builds the invoice from timesheets and fees. Unless the claim carries a client and billability flag into the invoicing run, nothing carries it across.

Who should decide whether an expense is billable?

The project or engagement owner, not the claimant and not finance. The claimant knows what they spent but not the contract terms. Finance knows the terms but not the circumstances. The engagement owner is the only party who holds both, and the decision should be captured at claim submission.

Should billable expenses be marked up?

It depends entirely on the contract. Some agreements permit a handling markup, others require pass-through at cost, and some cap recoverable expenses as a percentage of fees. The markup rule belongs in the contract record and should be applied automatically rather than decided during invoice preparation.

What evidence do clients require for rebilled expenses?

Most client contracts require supporting receipts for rebilled costs, and many will dispute or withhold payment on expense lines submitted without them. This makes receipt quality a revenue issue on billable claims, not merely a compliance one.

How do billable expenses affect cash flow?

They create a double cash lag. You reimburse the employee within days, then wait for the next invoicing cycle plus the client’s payment terms to recover it. A cost incurred in March and invoiced in April on 60-day terms is cash out for roughly three months.

How should tax be handled on rebilled expenses?

Treatment depends on whether the recharge is a disbursement made as the client’s agent or a supply you make onward in your own right. The two are taxed differently in most jurisdictions, and the distinction should be set per contract rather than assumed at invoice time.

What is expense leakage in professional services?

Expense leakage is recoverable client cost that is never invoiced — claims submitted after the invoicing cutoff, claims never flagged as billable, claims missing the receipt a client requires, or claims whose client reference was miscoded. It reduces realised margin without appearing anywhere as a loss.

When should billable expenses be invoiced to the client?

In the billing cycle following the cost being incurred, not the cycle following reimbursement. Tying invoicing to reimbursement date compounds employee submission delay with your own billing lag, pushing recovery weeks further out for no reason.

How do you stop billable expense leakage?

Capture client, project and billability at claim submission rather than deriving them later, validate the client reference against live project data, enforce receipt requirements on billable categories, and run an unbilled-expense report before each invoicing cycle so nothing ages past the cutoff unnoticed.