Ask most consulting firms how much they spent on client-related expenses last quarter and you'll get a shrug, not a number. Receipts sit in someone's wallet, get forwarded to finance three weeks late, or never get submitted at all. The result isn't just an accounting headache, it's real money: expenses that should have been billed to a client quietly become the firm's problem, and expenses that were never billable in the first place get mixed in and approved anyway. This guide walks through how to build an expense process that keeps those two categories straight and gets client-chargeable costs onto an invoice without anyone re-typing a thing.
In this guide
Billable vs. internal: two different expenses A lightweight approval workflow Rebilling client expenses onto the next invoice Why untracked expenses erode margin Receipt-capture hygiene that actually sticks Frequently asked questions
Billable vs. Internal: Two Different Kinds of Expenses
The first thing a consulting firm needs is a clean, consistently applied line between two categories of spending that look identical on a receipt but behave completely differently on the books. Client-chargeable expenses are costs incurred specifically because of an engagement, and they belong on that client's invoice: flights and hotels for an on-site workshop, mileage to a client's office, printing and binding for a deliverable, software licenses purchased solely for that project, or subcontractor fees brought in for a specific piece of work. If the expense wouldn't have existed without that particular client relationship, it's a candidate for rebilling.
Internal reimbursable expenses are the opposite: real costs the firm covers for its own operations that should never show up on a client's bill. A consultant's parking near the home office, a team lunch, a laptop charger, or a company-wide software subscription all fall here. These get reimbursed to the employee, but they're absorbed by the firm as overhead, not passed through.
The trouble starts when this distinction lives only in someone's head. If a consultant submits a taxi receipt without tagging which client it belongs to, or without flagging that it's billable at all, it either gets lost in general overhead (a quiet loss for the firm) or gets forgotten entirely and never reaches the invoice (a loss either way). Every expense should be tagged to a project and marked billable or non-billable at the moment it's submitted, not reconstructed from memory weeks later.
A Lightweight Approval Workflow That Doesn't Rely on Email
Most firms didn't design their expense process on purpose, it grew out of whatever was fastest at the time: a photo of a receipt texted to a project lead, a forwarded email with "please approve" in the subject line, a spreadsheet someone updates once a month if they remember. It works well enough right up until month-end, when finance is reconciling a stack of receipts against invoices that already went out, and half the paper trail is missing.
A workable alternative doesn't need to be complicated, it just needs three steps to happen in the same place instead of scattered across inboxes. First, the consultant submits the expense with a photo of the receipt attached, right at the time it's incurred, tagging the project and marking it billable or internal. Second, the project manager or finance lead sees it queued for approval against that specific project, with the receipt already attached, and approves or kicks it back with a note. Third, once approved, a billable expense attaches automatically to the project's running total and is ready to bill, while an internal one routes to reimbursement. No forwarding, no "did you see my email," no reconstructing what happened three weeks ago.
The payoff of that structure isn't just tidiness. It means the person approving an expense can see it against the project's budget and remaining scope in real time, catching an expense that's out of line before it becomes a client conversation instead of after.
Rebilling Client-Chargeable Expenses Onto the Next Invoice
Even firms that track billable expenses carefully often still lose the last step: manually re-adding every approved expense as a line item when an invoice gets built. That's a second data-entry point, and it's exactly the kind of handoff where a $340 hotel bill from six weeks ago quietly gets left off because nobody remembered to go looking for it.
The better pattern is to have approved client-chargeable expenses flow into the invoicing side of the workflow the same way billable hours do, sitting against the project until the next invoice is generated, at which point they're pulled in automatically with the receipt attached for the client's records. This is exactly the kind of connection a platform like Autovella is built to handle: an approved expense tagged to a project doesn't need to be found and re-entered, it's already waiting when the invoice is drafted. You can see how expenses, time, and billing connect on the features page.
A billable expense that never makes it onto an invoice is functionally a discount you didn't mean to give. The client received the value, the firm paid the cost, and the only step missing was someone remembering to charge for it.
Why Untracked Expenses Erode Margin the Same Way Unlogged Time Does
Consulting firms are usually vigilant about unlogged hours, because everyone understands intuitively that an hour worked and not billed is an hour of revenue gone. Expenses get far less scrutiny, even though the mechanism is identical. A $200 courier fee that never gets tagged as billable, a $1,200 flight that gets approved for reimbursement but never rebilled, a software license bought "for the project" that gets absorbed into general overhead instead of the client's invoice, each one is a direct, dollar-for-dollar hit to that project's margin.
The reason expenses slip through more easily than time is that they arrive irregularly and in small amounts, so no single miss feels significant. But add them up across a firm running a dozen active engagements, and the leakage looks a lot like the unbilled-hours problem everyone already takes seriously. If a project's margin looks thinner than expected at close-out, untracked or unrebilled expenses are one of the first places to check, right alongside scope creep and rate mismatches.
Receipt-Capture Hygiene That Actually Sticks
None of the above works if receipts don't show up in the first place. Getting consultants to capture and submit expenses consistently is less about policy documents and more about making the easy path also the correct path. A few habits make the biggest difference:
- Capture the receipt the moment it's incurred, not at the end of the week, memory of what a taxi ride was for fades fast
- Tag every expense to a project and a billable/internal status at submission, never leave that for finance to guess later
- Keep the original receipt image attached to the expense record, clients and auditors both eventually ask to see it
- Set a submission deadline tied to the billing cycle, not an open-ended "whenever," so nothing misses the invoice it belongs on
- Review flagged or unusually large expenses against the project's remaining budget before approving, not after the invoice is out
- Reconcile approved-but-unbilled expenses at least monthly, so nothing sits in limbo across a quarter
None of this requires a heavier process, it requires the same system that holds the project and the invoice to also hold the expense, so the receipt never has to travel through an inbox to get where it's going.
Keep expenses connected to projects and invoices
See how Autovella captures, approves, and rebills client expenses without a single spreadsheet.
Frequently asked
A billable expense is a cost tied directly to a client engagement, such as travel to a client site or materials bought for that project, and it gets passed on to the client, usually on the next invoice. An internal reimbursable expense, like a team lunch or a software subscription, is a real cost the firm covers itself and never appears on a client's bill.
Instead of forwarding receipts by email, consultants should submit each expense with a receipt attached directly to the relevant project, a manager approves or rejects it in the same system, and approved expenses flow straight into billing. That removes the inbox hunting and the month-end reconciliation surprises that email-based approval creates.
Yes, in a connected PSA platform an approved client-chargeable expense attaches to its project and is pulled onto that client's next invoice automatically, the same way logged billable hours are. That removes the manual step of re-entering expense line items when it's time to bill.