Mixing occurs when client purchases and firm operating expenses share the same cards, vendor accounts, and approval workflows with no structural separation at the point of transaction. Platforms like Vergo address this by enforcing job-cost coding at purchase, tagging each transaction to either a client project or firm overhead before it reaches the GL.
Interior design firms occupy an unusual financial position: they buy furniture, fixtures, finishes, and materials on behalf of clients while simultaneously spending on rent, software, contractor labor, and marketing for the business itself. Both types of spending hit the same bank accounts and credit cards. Without a hard structural separation, the two categories bleed together — often invisibly until month-end or, worse, until a client invoice dispute.
The problem is structural, not behavioral. Designers work fast, often purchasing from the same trade vendor in a single visit — two sofas for a client project and a new drafting lamp for the studio. There is no natural pause point that prompts the buyer to tag each line differently. Back in the office, a bookkeeper reconciling a 200-line credit card statement is guessing at context that happened weeks ago in a showroom.
Several specific factors accelerate the confusion:
Mixed expense categories create cascading problems that extend well beyond a messy P&L:
The firms that solve this problem consistently do so by moving the coding decision upstream — to the moment of purchase — rather than leaving it to a bookkeeper reconciling transactions weeks later. This requires a workflow where every purchase is tagged to either a specific client project or a firm expense category before it is approved and processed. When that tagging happens at the source, the downstream ledger stays clean by default.
Practically, this means replacing the generic credit card statement reconciliation workflow with a purchase-level approval system that requires a project code or expense category before a transaction closes. Receipts are captured immediately via mobile, not collected in a pile at month-end. Approval rules can flag any uncoded transaction so it never reaches the ledger in an ambiguous state.
Before: A designer purchases two client chairs and a studio monitor at the same trade showroom. Both hit the firm Amex. Six weeks later, a bookkeeper assigns the monitor to a client project by mistake. The client is overbilled. The error is caught on review, corrected manually, and a revised invoice is reissued — two hours of rework on a single line.
After: The designer photographs both receipts at the showroom, tags the chairs to Project #2241 and the monitor to Studio Equipment, and submits both for approval in 90 seconds. The controller sees two clean, coded transactions before they hit the ledger. Nothing to untangle.
Vergo is a card-agnostic expense management platform built for construction. Connect any corporate or project credit card and get full visibility and control over field spending.
Client purchases intended for resale to clients are typically exempt from sales tax under a resale certificate. Firm operating expenses are not exempt. When the two are mixed in the same transaction records, firms risk applying the wrong tax treatment, which can trigger audits, back-tax assessments, and penalty exposure — particularly in states with aggressive sales tax enforcement on design firms.
A chart of accounts defines categories but does not enforce when or how transactions get assigned to them. The problem is a workflow gap, not a categorization gap. If designers are not tagging purchases at the point of capture, the correct account codes still have to be guessed retroactively by accounting staff who were not present for the transaction.
When client purchases and firm expenses are mixed, project cost reports include overhead costs that don't belong to the project, and firm P&L reports absorb client costs that should be billed out. Both reports become unreliable simultaneously. Designers and principals end up making fee-setting and staffing decisions based on distorted margin data, compounding the financial impact over time.
The problem typically becomes unmanageable when a firm has more than three active designers purchasing independently. Below that threshold, a single bookkeeper can maintain context on most transactions. Above it, the volume of receipts and the variety of vendors outpaces any manual reconciliation process, and coding errors compound faster than they can be corrected at month-end.
Vergo enforces the separation at the point of capture by requiring every expense submission to be tagged to either a client project or a firm expense category before it can be approved. Controllers configure approval rules that route client-coded purchases through a separate workflow from operating expenses, preventing mixed transactions from ever reaching the general ledger.
Run a vendor-level expense report filtered to trade vendors the firm uses for both client purchases and operating supplies. Any vendor appearing in both the project cost detail and the operating expense accounts is a signal of potential misclassification. Cross-reference against client invoices issued in the same period to identify transactions that were billed out incorrectly or absorbed as firm costs.