The client's accounts payable team sent it back again
Your consultants travel to the client's sites every week: trains, hotels, the occasional dinner with the client team. The engagement letter says reasonable expenses are rebillable in line with the client's travel policy. The client's policy caps hotels by city, requires standard class rail, excludes alcohol and wants itemised receipts. Your consultants claim under your own policy.
At month end the expenses go on the invoice. The client's accounts payable team rejects several items and asks for itemised receipts on others. The invoice is held until it is fixed. Operations spends a day going back to consultants for receipts they have thrown away.
Why expenses get rejected
- Each client's travel policy differs, and consultants do not see it when they book or claim.
- Expense tools apply the firm's rules, not the client's.
- Receipts are photographed but not always itemised.
- Expenses are compiled for invoicing weeks after they were incurred.
- Clients require specific backup formats, such as per-person or per-week summaries.
Policies also change. A client updates its travel policy mid-engagement, and the change reaches its accounts payable team long before it reaches your consultants. The first you hear of it is a rejected invoice line.
What rejections cost
| Effect | Consequence |
|---|---|
| Items rejected | Expense cost absorbed by the firm |
| Invoice held | Whole invoice paid late, not just expenses |
| Operations chasing receipts | Time spent on admin that should be automatic |
| Friction with client finance | Relationship strain at an awkward level |
Consultants lose out too. When an item is rejected by the client, the firm often absorbs it, but sometimes the question comes back to the consultant months later, long after the trip. Nobody enjoys justifying a hotel bill from a spring engagement in the autumn.
How we build client-aware expense checks
- Each client's expense rules are recorded once from their policy: caps by category and location, class of travel, excluded items, receipt requirements.
- When a consultant claims an expense against an engagement, through your existing tool such as Expensify, Xero Expenses, Dext or a custom form, the client's rules are checked.
- Items that break a rule are flagged to the consultant at the time, with the reason, so they can fix or reclassify it as non-rebillable.
- Receipts are read to confirm they are itemised, and the consultant is prompted while they still have the paper copy.
- At invoice time, rebillable expenses are compiled with backup in the client's required format.
- Rejected items are recorded, so rules can be refined and repeated issues spotted.
We cannot guarantee clients will accept every item, because their teams interpret their own policies. What we can do is catch the predictable problems before they reach them.
We usually begin with the clients whose invoices are rejected most often, set up their rules, and look back over recent rejections to test that the rules would have caught them. Other clients are added as their engagements start.
How it feels after
Consultants know the client's limits when they book, not three weeks later. Operations compiles expenses in minutes, with backup the client wants. Invoices stop being held for expense queries.
Non-rebillable items are known early, so engagement budgets reflect real travel costs.
Could this be happening to you?
- Clients reject expense items or hold invoices over expenses.
- Consultants do not know each client's travel policy.
- Receipts are chased at month end.
- Expense backup is compiled by hand for each client.
- Travel costs absorbed by the firm are not tracked.