Daniel sent us this one — he's running into the classic consultant's tangle around client expenses. The core question is how to handle spending money on behalf of clients without creating an accounting nightmare or legal exposure. He mentions preferring virtual payment cards when clients issue them, but recounts one situation where a high-net-worth client wanted him to hold cash on trust, and when he refused, they handed him a credit card instead and buried him in administrative work — filing every expense down to five-dollar charges. The heart of it is this tension: you want to make life easy for clients, but saying yes without thinking through the consequences can cost you time, money, and legal exposure. And the right answer probably shifts depending on whether you're a sole operator or part of a larger practice.
This is one of those topics where the surface question is about payment methods, but the real thing underneath is about who carries the risk. And most of the advice out there is written for companies with finance departments — it completely misses what happens when you're one person and the person who does the expenses is also the person who does the work and the person who does the taxes.
The finance department is me and a shoebox.
So let's start with the thing Daniel flagged as his preferred method — virtual payment cards. These are essentially card numbers generated for a specific purpose, often with spending limits, expiration dates, or merchant category restrictions built in. The client issues one, you use it for their expenses, the charges land on their statement, and you never touch the money.
The money never passes through your books. That's the magic.
That's the magic. And it's not some niche fintech experiment anymore. Brex, Stripe, Ramp, Airbase — all of them offer virtual card issuance now. Brex in particular built a whole business around this. Their virtual cards let you set per-card spending limits, lock cards to specific vendors, set expiration dates that match a project timeline. The client's finance person can spin one up in thirty seconds and email you the card details.
This solves the taxable income problem straight away. Because if a client reimburses you for an expense, that reimbursement can look like income unless you're meticulous about documenting it as a pass-through. And if you mess that up, you're paying tax on money that was never yours.
The IRS is not messing around on this. Publication 535, which covers business expenses, is very clear — if you receive an advance or reimbursement from a client, you have to account for it properly or it gets treated as gross income. The virtual card approach sidesteps the whole thing because the funds never hit your account. You're not being reimbursed. You were never out of pocket.
The question becomes — why doesn't every client do this?
A few reasons. One, some companies just don't have the infrastructure. Virtual card issuance usually comes through a corporate card platform or a spend management tool, and if the client is running their business on a single Chase Sapphire card and QuickBooks, they might not have the option. Two, some finance teams are weirdly attached to reimbursement workflows because that's what they've always done. And three — and this is the one that I think matters most for the kind of clients Daniel's describing — high-net-worth individuals and family offices often operate differently from companies. They might not have a corporate card program. They might have a personal assistant who handles expenses manually. The virtual card solution assumes a certain level of organizational infrastructure.
The virtual card is the ideal, but it's not universally available. Which means you need a decision framework for when it's not on the table. And that framework has to account for scale — sole operator versus practice with staff.
Let's build that framework. I think there are basically four models for handling client expenses, and each one has a different risk profile and a different administrative burden. Model one is the virtual card — client pays directly, you never touch the money. Model two is the advance — client sends you funds upfront, you spend against that balance, and you reconcile at the end. Model three is reimbursement — you pay out of pocket and the client pays you back. Model four is the client-issued card — you carry a card in the client's name and use it for their expenses.
The situation Daniel described with the high-net-worth client was model four, with the added indignity of having to file every charge down to the five-dollar level.
And here's the thing about model four — it's model three wearing a costume. It feels like model one because you're swiping a card that isn't yours, but the administrative burden is actually worse than reimbursement because now you're doing the client's expense reporting for them. You're not just tracking what you spent — you're categorizing it, justifying it, attaching receipts, all according to their internal processes.
You've become their bookkeeper, unpaid.
If that card is in your name — even as an authorized user — and something goes wrong, you're in the chain of responsibility. If the card is in the client's name and you're just holding it, there can still be questions about who authorized which charge. I've seen situations where a consultant used a client's card for what they thought was an approved expense, and the client later disputed it.
Let's go through these models and figure out where the pitfalls actually are. Starting with the advance model — client sends you money, you spend it, you reconcile.
The accounting treatment is the first thing. If a client sends you ten thousand dollars as an advance for expenses, that is not your money and it is not income — but your bank account doesn't know that. You need to track it as a client funds liability on your balance sheet, spend against it, keep every receipt, and then return any unspent balance. If you don't return the balance promptly, or if you commingle it with your operating funds, you're creating a mess. And in some jurisdictions, holding client funds can trigger trust accounting rules or even licensing requirements.
That was the thing Daniel flagged — the client who wanted him to hold cash on trust. And he refused.
Holding client funds in trust is not a casual arrangement. In the legal profession, trust accounting is heavily regulated — lawyers have to keep separate trust accounts, they're audited, they can be disbarred for messing it up. Consultants aren't typically subject to those rules, but the underlying principle is the same. Once you're holding someone else's money, you have a fiduciary duty. If the bank fails, if there's fraud, if the IRS looks at that deposit and asks questions — it's on you.
The scale question matters here. A larger practice might have a dedicated client funds account and someone whose job includes reconciliation. A sole operator is doing all of this on a Sunday afternoon when they'd rather be doing literally anything else.
The advance model can work if the amounts are predictable and the timeline is short. If you're running a two-day workshop and the client sends you five hundred dollars for materials, fine — spend it, send the receipts, return the twelve dollars left over, done. But if it's an ongoing engagement with fluctuating expenses over months, the reconciliation burden compounds fast.
Model three — reimbursement. You pay out of pocket, client pays you back. This is probably the most common arrangement in consulting.
The most dangerous from a tax perspective. Because now you're commingling by design. Your money and the client's expenses are coming out of the same account. If you don't have a clean system for separating them, you're going to have a bad time at tax season. The IRS wants to see that reimbursements are not income. That means you need to track every expense, categorize it, match it to the corresponding reimbursement, and be able to produce that documentation if asked.
The reimbursement itself — if the client sends you a lump sum that covers both your fee and your expenses, and you don't break it out on the invoice, congratulations, you just made the entire amount taxable.
This is where I see sole operators make the same mistake over and over. They invoice for ten thousand dollars — eight thousand for the work, two thousand for expenses — but they don't itemize it. The client pays ten thousand. The IRS sees ten thousand in revenue. And now you're paying tax on two thousand dollars that just passed through you. The fix is simple — itemize expenses on the invoice, keep receipts, and make sure your accounting system distinguishes between revenue and reimbursements. But simple doesn't mean people do it.
I've seen the opposite mistake too — people who deduct the expenses but forget to record the reimbursement as a reimbursement, so it sits in revenue and they're effectively double-counting. The IRS does not love that either.
No, they do not. So reimbursement can work, but it requires discipline. And you need to be comfortable floating the expenses — if a client takes sixty days to pay and you've put five thousand dollars on your personal card, that's five thousand dollars of your working capital tied up.
Which brings us back to the virtual card as the gold standard. But you mentioned that not every client can issue them. So what do you do when the ideal isn't available and you're looking at models two, three, or four?
I think the first thing is to recognize that this is a negotiation, not an accommodation. The way Daniel framed it — "one wants to make life easy for clients" — that instinct is good business, but it can lead you to absorb costs and risks that the client should be carrying. The client's expenses are the client's expenses. Your job is to spend them responsibly, not to finance them or administer them.
The phrase "unjust accounting burden" in the prompt is doing a lot of work. It's not just unjust in the sense of unfair — it's unjust in the sense that the burden properly belongs to the client's finance function, not to the consultant's. When you take it on, you're effectively providing free back-office services.
Here's a concrete way to think about it. Suppose you're billing two hundred dollars an hour. If you spend two hours a month on expense reporting for a client, that's four hundred dollars of unbillable time — or four hundred dollars you could have billed to another client. Over a year, that's forty-eight hundred dollars. Over a multi-year engagement, it's real money. And that's before we talk about the mental overhead of keeping track of receipts and categories and deadlines.
The cognitive load of being a part-time bookkeeper for someone else's business.
So the framework I'd propose is this. First, always start by requesting a virtual card. Explain why — it's cleaner for your accounting, it keeps their expenses off your books, it reduces everyone's liability. Many clients who can do it will do it once they understand the rationale. Second, if a virtual card isn't possible, propose an advance arrangement with clear terms — the advance covers estimated expenses for a defined period, you reconcile monthly, unspent funds are returned or rolled forward with explicit agreement.
Third, if the client insists on reimbursement, build the administrative cost into your rate or add an expense handling fee. This is not weird. Law firms do it. Consulting firms do it. A five or ten percent surcharge on pass-through expenses is standard in many industries. It compensates you for the float, the tracking, and the tax compliance overhead.
Fourth — if the client wants you to carry their card, just say no. That's the one where the prompt's example is basically a cautionary tale. The five-dollar credit charges, the uncompensated time, the legal exposure — none of that is worth it.
I'd go further and say model four should not exist in professional services. If a client hands you a credit card and asks you to manage their expense reporting, what they're really doing is outsourcing their internal controls to you without paying for it. And you're accepting liability for something you have no business accepting liability for. What happens if the card is compromised? What happens if there's a disputed charge six months later? What happens if the client decides an expense wasn't authorized after all?
The other thing that jumps out from the prompt is the scale question — whether the consultant is part of a practice or a sole operator. Let's talk about how the analysis changes.
In a larger practice, you have leverage. You can say "our firm's policy is X" and it carries weight. You probably have an engagement letter that spells out expense handling. You might have an accounting department that handles reconciliation. The administrative burden per consultant is lower because it's spread across multiple people and there are systems in place.
The engagement letter point is important. A sole operator can and should have an engagement letter too — but in practice, many don't. They have an email thread and a handshake. And then when the expense question comes up, there's nothing to point to.
The engagement letter should absolutely address expenses. It doesn't have to be complicated. "Client will provide a virtual payment card for project-related expenses" is one sentence. "Consultant will invoice for reimbursable expenses monthly, with receipts attached, and payment is due within fifteen days" is another. "Expenses exceeding five hundred dollars require prior written approval" is a third. Three sentences, and you've just prevented ninety percent of the problems we're talking about.
It's easier to have that conversation at the start than six months in when you're already frustrated about the five-dollar charges.
The other advantage a practice has is that they can afford to fire a client over this. A sole operator might feel they can't. If you're depending on one or two big clients for most of your revenue, the pressure to accommodate unreasonable requests is much higher. But that's exactly when the risks are highest — because a dispute with your biggest client over expenses can threaten your whole business.
The sole operator paradox is that you have less leverage and more exposure at the same time.
Which is why the framework has to be even more disciplined for sole operators. You can't afford to be casual about this. Every expense arrangement needs to be documented. Every reimbursement needs to be tracked. And you need to be willing to walk away from a client who won't respect reasonable boundaries — because a client who won't give you a virtual card but will hand you their personal credit card and demand line-item reporting is telling you something about how they'll treat you on everything else.
Like adopting a feral cat.
I was going to say it's a leading indicator of client dysfunction, but yes, also like adopting a feral cat.
Let's talk about some specific mechanics. When you do have to handle reimbursements, what does good practice look like?
Separate tracking is non-negotiable. Whether it's a dedicated credit card that you use only for client expenses, or a separate category in your accounting software, or even a spreadsheet if you're very small — you need to be able to produce a clean report of what you spent, when, for which client, with receipts. QuickBooks, Xero, FreshBooks — they all handle this. Even something like Expensify or a dedicated email folder for receipts is better than nothing.
The receipt threshold matters. The IRS requires receipts for expenses over seventy-five dollars, but for client reimbursements, you should keep everything. The client might want to see that five-dollar parking charge, and if you can't produce it, you eat it.
The other mechanical thing is timing. Reimburseable expenses should be invoiced monthly, not accumulated. The longer the gap between the expense and the invoice, the more likely something gets lost or disputed. And if a client is slow to pay reimbursements, you need to have a conversation about it — not just let the balance build up while you quietly resent them.
What about the advance model mechanics? If a client sends you money upfront, how do you handle it properly?
Separate bank account if the amounts are significant. For most sole operators, a separate ledger account within your existing accounting system is probably sufficient — but the key is that you can point to exactly where the money is and what it's been spent on at any moment. You should also have a written agreement about what happens to unspent funds. Default assumption is they go back to the client, but some arrangements allow you to roll them forward to the next period. Whatever it is, write it down.
Never, ever treat the advance as your money. Even if it's sitting in your account. Even if the client says "just use it however." The tax authority will not see it that way.
There's a specific IRS concept here called "constructive receipt." If you have unrestricted access to funds, they may be considered income even if you haven't spent them. An advance that comes with no strings attached — no requirement to account for spending, no obligation to return unspent funds — that's not an advance. That's a payment. And it's taxable.
The strings are actually protective. The more formal the arrangement, the clearer it is that this is not your money.
Formality is your friend here. It feels bureaucratic and annoying, but it's what separates a legitimate expense arrangement from a tax problem.
Let's circle back to something you mentioned earlier — the idea of an expense handling fee. How does that work in practice?
There are a few ways to structure it. The simplest is a percentage markup on pass-through expenses — five to fifteen percent is common, depending on the industry and the volume. This compensates you for the administrative overhead, the float, and the compliance burden. Law firms have been doing this forever — it's called a "service charge" or "administrative fee" and it's completely standard.
It's not hidden. It's in the engagement letter, it's on the invoice, the client knows about it upfront.
Another approach is to build it into your rate. If you know a particular engagement is going to involve significant expense handling, you price that in. Your hourly rate or project fee reflects the additional non-billable time you'll spend on administration. The client doesn't see a separate line item, but you're still being compensated.
The third approach is to cap it — "the first five hundred dollars of expenses per month carry no surcharge, beyond that a ten percent handling fee applies." That protects you from the scenario where a project suddenly involves way more expenses than anyone anticipated.
It also incentivizes the client to issue a virtual card. If there's a ten percent surcharge on reimbursed expenses but no surcharge on virtual card expenses, suddenly the finance team has a reason to figure out how to issue one.
The handling fee is both compensation and a nudge toward better behavior.
Behavioral economics in the engagement letter.
I want to go back to the trust accounting question, because I think it's the scariest part of the prompt and the one that most consultants haven't thought about. Daniel mentioned a client asking him to hold cash on trust, and he refused. What would have happened if he'd said yes?
It depends on the jurisdiction and the amount, but the short answer is he'd be taking on fiduciary obligations without necessarily knowing what they were. In the worst case, if something went wrong — if the funds were misappropriated, even accidentally — he could be personally liable. If the arrangement wasn't properly documented, the tax authority might treat the funds as income. If the client went bankrupt, the funds could get caught up in bankruptcy proceedings. And in some regulated professions, holding client funds without proper trust accounting can result in losing your license.
Even for unregulated consulting, the reputational risk is enormous. "Consultant loses client's money" is not a headline you recover from.
"Just hold this money and spend it as needed — it's easier than invoicing." But they're actually asking you to become an unlicensed, unregulated financial intermediary. That's not a simplification. That's a trap.
The refusal was absolutely correct. And the alternative they came up with — issuing a credit card and demanding line-item reporting — was its own kind of trap, just less obviously dangerous.
The credit card approach is a trap of a thousand small cuts rather than one big one. It won't blow up your business overnight, but it will drain your time, complicate your taxes, and create an ongoing administrative relationship that you're not being paid for. And the fact that the client required reporting down to five-dollar charges tells you everything about what kind of client they were.
Micromanagement as a service, provided free of charge.
Here's a question for you. What do you think is the most common mistake consultants make on this topic — the thing that seems fine in the moment but causes problems later?
I think it's treating expense handling as a minor operational detail rather than a contractual term. The consultant wants to be easy to work with, the client suggests something casual, everyone agrees verbally, and nobody writes anything down. Then six months later there's a five-thousand-dollar expense the client doesn't remember approving, and there's no paper trail, and now you're in a fight with someone you need to maintain a good relationship with.
The "casual agreement" problem. And it's especially dangerous with expenses because expenses are inherently variable. You don't know at the start of an engagement how much you're going to spend on travel or materials or whatever. So the agreement needs to cover not just how expenses are handled, but what kinds of expenses are authorized, what the approval threshold is, and how quickly the client has to pay.
What happens if they don't pay.
Late payment on reimbursements is a form of involuntary lending. You're effectively financing the client's expenses at zero percent interest. If they take ninety days to reimburse you and you've put the expenses on a credit card that charges twenty percent interest, you're losing money on every transaction.
The expense policy needs teeth. Late fees, interest charges, the right to suspend work if reimbursements are more than thirty days overdue. Again, this is standard in larger firms, but sole operators often feel weird about including it.
The weirdness goes away the first time a client is sixty days late on a four-thousand-dollar reimbursement and you're looking at your credit card statement.
Let's shift to something more constructive. If you're a sole operator listening to this and realizing your current approach is a mess, what's the first thing you should do?
Audit your current clients. For each one, ask three questions. One, how are expenses currently handled? Two, what's the monthly administrative burden — in hours — of managing those expenses? Three, what's your financial exposure — how much of your money is currently floating client expenses? That audit alone will tell you where the problems are.
Then fix the biggest problem first. If you've got one client where you're floating five thousand dollars and spending two hours a month on expense reports, that's your priority. Either convert them to a virtual card, renegotiate the terms, or add a handling fee. Don't try to fix everything at once — just fix the worst situation.
For new clients, start clean. Engagement letter, expense policy, virtual card as the default. It's much easier to set expectations at the beginning than to change them mid-engagement.
The other thing I'd recommend is separating your business expenses from client expenses. If you use the same credit card for both, you're creating a reconciliation nightmare. Get a dedicated card for client pass-through expenses, or at minimum use a separate tracking system. The goal is that at any moment, you can answer the question "how much money am I owed in reimbursements right now?" without spending an afternoon in your accounting software.
If you can't answer that question right now, that's a sign.
That's a big sign.
I want to talk about one more scenario that the prompt didn't explicitly raise but that follows from the logic. What about expenses that you incur before the engagement is fully signed? The client says "go ahead and book the flight, we'll have the contract sorted by then," and then something falls through.
Never incur expenses without a signed engagement letter. I don't care how urgent it is. I don't care how good the relationship is. Until there's a signed agreement that includes an expense provision, you're spending your own money with no legal obligation on the client's part to reimburse you. If the deal falls through, you eat the cost.
The "go ahead and get started" trap.
It's not just about reimbursement. If you're incurring expenses on behalf of a client, you need to know what's authorized, what the limits are, and what the approval process is. None of that exists before the engagement letter is signed. So you're flying blind and hoping nothing goes wrong.
Which brings us to the broader principle here. The way you handle expenses is a proxy for how you handle the entire client relationship. If the expense arrangement is casual and undocumented and you're absorbing all the risk, that's probably true of other aspects of the engagement too.
The expense conversation is a test. A client who says "sure, we'll set you up with a virtual card, here's the spending limit, let us know if you need anything else" is a client who respects your time and understands that you're running a business. A client who says "just put it on your card and we'll figure it out later" or "here's my credit card, file the expenses weekly" is a client who sees you as an extension of their own operations rather than an independent professional.
There's a class dimension to this that's worth naming. The prompt mentions a high-net-worth client. There's a particular dynamic where wealthy individuals sometimes treat consultants like household staff — "here's the card, handle the expenses, I don't want to think about it." And it can feel flattering to be trusted with that level of access, but it's actually a demotion.
The "personal assistant" dynamic. And it's dangerous precisely because it feels like a close relationship. The client is treating you like an insider, which can feel good — until you realize that insiders don't get engagement letters and liability protections. They get informal arrangements and disputes resolved by power dynamics rather than contracts.
The antidote is professionalism at the boundary. You can be warm and collaborative and still have clear, documented terms. In fact, the clearer the terms, the easier it is to be warm and collaborative because you're not quietly anxious about the unresolved stuff.
The terms don't have to be adversarial. "I want to make sure we have a clean arrangement so neither of us has a tax problem" is a completely reasonable thing to say. Most reasonable clients will appreciate it. The ones who push back are telling you something useful.
Let's try to synthesize this into something actionable. If someone's listening and wants a decision framework they can use tomorrow, what would you give them?
Tier one, always push for the virtual card. It's the cleanest solution for everyone. Tier two, if a virtual card isn't possible, use an advance arrangement with a written agreement, separate tracking, and monthly reconciliation. Tier three, if you must do reimbursement, itemize everything, invoice monthly, keep all receipts, and build the administrative cost into your rate or add a handling fee. And under no circumstances accept model four — carrying the client's card and doing their expense reporting.
The trust thing — holding client cash — that's not even on the menu.
That's not on the menu. That's the thing you politely decline and then update your assessment of the client who asked.
The other through-line here is documentation. Whatever model you're using, write it down. Engagement letter, expense policy, something. The tax authority and the courts do not care about your verbal agreements.
Document as you go. Receipts, approvals, reconciliations. The time to build the paper trail is when the expense happens, not when the client disputes it six months later.
There's a phrase that shows up in the prompt — "unjust accounting burden." I keep coming back to it because I think it names something that a lot of solo consultants feel but can't articulate. The burden isn't just the time. It's the injustice of carrying a responsibility that properly belongs to someone else. And the injustice has a cost — not just in hours, but in resentment, in mental overhead, in the slow erosion of the sense that you're running a business rather than working for someone else.
The resentment is a business problem, not just a feelings problem. When you resent a client, the work suffers. You're less creative, less generous, less willing to go the extra mile. You start avoiding their calls. The relationship degrades. And it all started because you said yes to an expense arrangement that you should have said no to.
Saying no at the start is actually better for the relationship in the long run.
Boundaries preserve relationships. It's counterintuitive but it's true.
One last question. What's the trend here? Are virtual cards becoming more common? Is this problem solving itself over time?
The trend is definitely toward virtual cards and spend management platforms. Companies like Brex and Ramp have made card issuance trivial — it's an API call now. Stripe Issuing lets platforms generate virtual cards programmatically. The infrastructure is getting better and cheaper. And the more consultants ask for virtual cards, the more clients will adopt the tools to provide them. We're moving in the right direction. But we're not there yet, and in the meantime, the framework matters.
The advice is: push for the ideal, but have a plan for the reality.
That's the whole thing.
Now: Hilbert's daily fun fact.
Hilbert: In Tibet around the year four hundred, artisans laid a floor using a tiling of equilateral triangles and squares that produced twenty-three distinct vertex configurations across a single room. If you tried to recreate that floor today using standard ceramic tiles from a home improvement store, you'd need to custom-cut approximately sixty percent of the pieces, because modern manufactured tiles assume no more than three shapes in any repeat pattern.
...right.
I have so many questions about who counts vertex configurations.
So to close this out — the core idea I want to leave with is that expense handling is not a minor operational detail. It's a contractual, financial, and legal boundary that deserves the same attention as your rate and your scope of work. Get it right at the start and it disappears into the background. Get it wrong and it becomes a slow bleed of time, money, and goodwill.
If you take nothing else from this episode, take this: the virtual card is your friend. Ask for it. Make it your default. Your accountant will thank you, your tax return will thank you, and you'll spend less time being an unpaid bookkeeper for someone else's business.
Thanks to our producer, Hilbert Flumingtop. This has been My Weird Prompts. Find us at myweirdprompts dot com, and if you got something out of this episode, leave us a review wherever you listen.
We're back next week.
