The Consultant Who Invoiced Four Times Before Getting Paid Once
The work was finished. The deliverable was clean, on time, and signed off. The consultant had done everything right — scoped the project carefully, met every milestone, submitted a professional invoice within twenty-four hours of completion. And then, for the next fourteen weeks, she did not get paid. She chased, she resent, she negotiated, she accepted a partial payment as a gesture of good faith, she invoiced again for the remainder, and she watched the professional relationship she had spent six months building dissolve one unanswered email at a time. When the final payment did eventually arrive, it was not a win. It was the end of an attrition. The money was there, technically. But so was the cost — and nobody had calculated that.
This is not an unusual story. It is, statistically speaking, the norm.
The Setup: A Project That Looked Like a Good Deal
The consultant — call her M — operates a boutique strategy practice. She works with mid-market companies on organisational restructuring, commercial due diligence, and operational redesign. Her projects run between three and six months. Her invoices are large. Her clients are, on paper, sophisticated businesses with procurement functions, finance teams, and payment policies.
She was engaged by a manufacturing group to lead a commercial review ahead of a potential acquisition. The engagement scope was clear: six weeks of active analysis, a final report, and a presentation to the executive committee. The contract was signed. The payment terms were net-30.
She delivered the final report on a Thursday morning. She invoiced the same afternoon.
What followed was not a payment. It was a process.
Week One: The Invoice in the Queue
The invoice was received, confirmed, and then — nothing. At day seven, M sent a polite follow-up. She was told the invoice had been logged and was "with finance." This is the first phase of the late-payment cycle, and it is the most deceptive, because it looks like progress. The invoice exists in the system. Someone has acknowledged it. The client is not hostile. Everything is fine.
But most late payments are not caused by clients refusing to pay — they happen because of structural problems in how invoices are sent, received, and processed, and the most common cause is administrative friction. The invoice has entered a bureaucratic queue that the consultant has no visibility into and no control over. It is sitting in a finance inbox, awaiting an approvals process that may require two or three internal sign-offs before a payment run is triggered. The consultant does not know when that payment run happens. She does not know whether her invoice is approved, disputed, or simply forgotten.
Understanding a client's payment processes is essential — some clients have rigid monthly payment cycles, while others are more flexible, and aligning invoicing to match the client's cycle can expedite payments. M had not asked. Nobody had told her. Her net-30 terms existed on paper. The client's actual payment cycle was net-45, running from the first day of the following month. She had invoiced on a Thursday in the middle of a billing period. Her invoice would not be batched until the following month's run. By the time her net-30 terms had elapsed, the client's internal clock had not even started.
Week Four: The First Re-Invoice
Day thirty came and went. M followed up again — this time more directly. She received an out-of-office reply. The contact who had commissioned the engagement was traveling. The finance team did not have her direct contact's authorisation on file for payments above a certain threshold. She was asked, politely, to resubmit her invoice to a different email address and to include a purchase order number that had not previously been mentioned.
This is the second phase: the administrative obstacle. It arrives exactly when the consultant believes she is close to resolution. The request for a PO number, a revised invoice format, a different submission address, or an additional approval signature is rarely malicious. It is usually the product of a procurement process that was never properly explained at the outset. But its effect is precise: the clock resets. The thirty days do not pause and resume — they restart from the date of the newly submitted document.
M resubmitted. She formatted the invoice to include the PO number. She addressed it to the new email. She noted politely in her covering message that the original invoice had been submitted thirty days prior and that payment was now due.
She did not receive a payment. She received an acknowledgement.
In the United States, 55% of all B2B invoiced sales are overdue. This is not a rounding error. It is the baseline condition of commercial invoicing — a system built on trust, operating without any structural enforcement mechanism at the moment the money should move.
Week Eight: The Partial Payment
Six weeks after the original invoice — and two weeks after the resubmission — a payment arrived. It was sixty percent of the outstanding amount.
There was no explanation attached. No breakdown. No note indicating what the remaining forty percent represented or when it might be paid. Just a bank transfer for a number that did not match any agreed milestone, any line item, or any prior communication.
This is the third phase, and it is the most psychologically complex. The partial payment creates a trap. It is enough to confirm that the client is not ignoring the debt — they know it exists, they have moved on part of it, they are presumably intending to settle the rest. But it is also enough to make escalation feel disproportionate. The consultant cannot claim non-payment. She cannot threaten legal action over a debt that has been partially acknowledged. She is now in a position where she must chase not a delinquent client, but a slow one — and the social cost of that chase is borne entirely by her.
Following up on an unpaid invoice often involves sending the client multiple reminders, and if they pay a portion but not all, starting to send statements becomes another time suck.
M wrote to the client asking for clarification on the partial payment. She was told that a query had been raised internally about one section of the deliverable — specifically, whether a particular phase of the work fell within the original scope or constituted an additional billable engagement. Nobody had raised this query before payment was made. Nobody had raised it during the six weeks the invoice had been sitting in the queue. It had emerged, apparently, only once someone in the finance team had reviewed the work product in order to approve the invoice.
This is the dispute phase — and it is the point at which the late-payment cycle becomes something more serious. It is no longer administrative. It is now commercial. The relationship between the consultant and the client has shifted from service provider and buyer to creditor and debtor, with a contractual disagreement layered on top.
The Hidden Ledger: What This Has Actually Cost
Let's stop here and count.
Time Spent Not Billing
Research shows that 14% of small businesses spend five or more hours weekly chasing overdue payments — roughly 260 hours per year, equivalent to six and a half full work weeks. At a billing rate of $75 per hour, those 260 hours represent $19,500 in lost revenue potential.
M's billing rate is considerably higher than $75 per hour. Every hour she spent drafting follow-up emails, formatting re-invoices, taking calls with the client's finance team, and documenting the dispute was an hour she did not spend on a paying engagement. It was also an hour she did not spend on business development — on the pipeline of future work that sustains a practice over time. The more time spent tracking down late payments, the less time available to knock out projects, look for new work, and gain experience.
This cost is invisible on any balance sheet. It does not appear as a line item. It lives in the gap between what the consultant earned and what she could have earned — a gap that widens silently with each week the invoice remains open.
The Opportunity Surrendered
There is a second, harder-to-quantify cost: the opportunity that M did not pursue because her attention was divided.
A consultant running a project engagement is not simply delivering against a scope — she is also, at every moment of client contact, positioning for the next engagement. The debrief meeting. The executive presentation. The follow-on question that arrives two weeks after the final report. These are not administrative formalities. They are the moments in which the next project is seeded.
By week eight, M's relationship with her primary contact at the manufacturing group had curdled. The contact was uncomfortable — aware that payment was overdue, aware that a dispute had emerged, aware that M's emails were now more formal and less collaborative. The follow-on engagement that had been informally discussed during the project's final phase — a second commercial review for a different acquisition target — was never formalised. There was no explicit conversation in which it was withdrawn. It simply stopped being mentioned.
Firms are delivering great work but struggling to get paid for it on time, creating a gap between project delivery and cash flow — and this gap can delay hiring decisions, limit investment, and force firms to operate more cautiously. For a solo practitioner, that caution is not strategic — it is existential. M had been counting on the follow-on engagement as part of her forward revenue plan. When it evaporated, she faced a pipeline gap she had not planned for.
The Cash Flow Distortion
For the weeks the invoice was partially outstanding, M was running her practice on compressed cash. Subscriptions, software licences, subcontractor payments, and professional indemnity insurance — all of these continued on their own schedules, indifferent to the state of her receivables.
When payments are delayed, businesses experience immediate cash flow strain that impacts operations and financial stability — and 60% of businesses with longer payment terms report cash flow problems, compared to 40% with immediate payment. For a larger firm, this strain is absorbed by working capital reserves and revolving credit facilities. For an independent consultant, it is absorbed by the individual — often quietly, often without acknowledgement that this absorption is itself a cost of doing business in a system that does not protect the service provider.
The average annual cost from late payments runs to $39,406 per company, and 76% of businesses report they must address late invoice payments before focusing on growth — while 89% say late customer payments have set back their long-term growth goals. These are not abstract figures. They are the aggregate expression of thousands of situations exactly like M's, playing out across every professional services sector, every quarter, with reliable consistency.
Week Twelve: The Third Invoice — and the Dispute in Full
The scope dispute had not resolved. M's position was clear: the deliverable had been scoped, agreed, and signed off. The client's position was that one section of the final report — approximately fifteen percent of the total work product — had not been explicitly itemised in the original engagement letter and therefore fell outside the agreed scope.
This is the most corrosive phase of the late-payment cycle, because it transforms the nature of the relationship entirely. The client is no longer slow to pay — they are actively contesting the debt. And the consultant is no longer a trusted advisor — she is a creditor making a claim.
M had a strong contractual position. The engagement letter was detailed. The scope was written broadly enough to encompass the disputed work. But a strong contractual position is not the same as a resolved dispute. Enforcing it requires time, administrative effort, and — at the extreme end — legal cost. When all else fails, legal action may be necessary, especially if the amount owed is substantial; small claims court is an option and doesn't require hiring a lawyer, but it should be the absolute last resort due to time and legal costs.
M did not want to take legal action. She wanted to get paid and to exit the relationship with as much dignity as possible. She drafted a detailed response to the dispute, citing the engagement letter, the project brief, and the signed-off deliverable. She issued a third invoice — adjusted to reflect only the undisputed portion of the outstanding balance, with a separate invoice for the disputed amount, clearly referenced, to be addressed once the scope question was settled.
She was, by this point, spending more time managing the payment process than she had spent on some of the smaller phases of the actual project.
The Relationship Cost
The accumulated costs of managing overdue accounts represent a significant drag on productivity. But the relationship cost is harder to denominate. M had entered the engagement with a strong referral — the manufacturing group's CEO had been introduced to her through a mutual contact in her network. That contact was now aware that the engagement had become contentious. Not because anyone had briefed him maliciously, but because these things circulate. Professional networks are smaller than they appear.
The referral relationship — the one that had generated this engagement — was not damaged. But it was not strengthened either. And in a practice built on referrals, the difference between a client who actively refers and a client who is merely neutral is measured in future revenue.
Week Fourteen: Payment, Finally
The dispute was settled through a negotiated reduction. M accepted a figure slightly below her full invoice in exchange for immediate payment and a written confirmation that the engagement was closed. She did not receive everything she was owed. She received enough to make further pursuit feel uneconomical.
The final payment arrived by bank transfer. There was no accompanying note. No acknowledgement of the delay. No apology.
She sent a brief, professional acknowledgement and closed the file.
Across the US freelance economy, an estimated $15 billion is lost annually to late and non-payment. M's situation had not resulted in a total loss. But it had resulted in a real one — in money negotiated away, in time spent chasing rather than billing, in a follow-on engagement that was never contracted, and in a professional relationship that ended not with goodwill but with exhaustion.
The Structural Problem No Invoice Can Solve
What M experienced is not a failure of character — not hers, not the client's. It is a failure of architecture. The standard consulting engagement is built on a foundation that requires the service provider to deliver first, invoice second, and wait indefinitely for the money to move. Every protection that has been added to that model — late fee clauses, PO requirements, escalation procedures — is a patch applied to a process that is structurally misaligned with how professional services actually work.
The consultant holds the risk from the moment she signs the contract to the moment the money lands. During that entire period, she is exposed: to administrative friction, to disputes that emerge after delivery, to partial payments that forestall escalation, to the slow erosion of a relationship that was supposed to generate future revenue. And each of these exposures compounds the others. The dispute is harder to resolve because the relationship has frayed. The relationship frays because the chasing is exhausting. The chasing is exhausting because the payment architecture provides no alternative.
For project-based businesses — consulting firms, marketing agencies, IT services providers, and similar organisations where revenue is tied to project milestones and deliverables — this is especially damaging, because a few delayed invoices can quickly strain operations. The problem is not isolated to any one type of client or any one type of engagement. It is endemic to the model itself.
What would have changed M's situation is not a more aggressive late fee policy, not a better-worded contract, not a more structured follow-up sequence. All of those things help at the margins. None of them address the central flaw: that payment, in the current model, is a separate event from delivery — one that happens later, contingently, through a process that the consultant does not control and cannot compel.
A Different Architecture
The consultants, brokers, and independent advisors who are beginning to restructure their payment processes are not doing so because they distrust their clients. They are doing so because they have counted the cost — the way M eventually did, sitting with a closed file and a final payment that was smaller than it should have been — and decided that the old model is not worth defending.
Shaka allows deal structures to be defined before work begins: the payment split, the parties, the amounts. When the client pays, the smart contract executes the distribution simultaneously to every party named in the deal. There is no invoice waiting in a finance queue. There is no partial payment creating a negotiating impasse. There is no re-invoicing cycle, because there is no invoice to re-send. Payment is final and irreversible at the moment of confirmation — not a promise, not a process, not a queue.
What M Would Do Differently
M still works with mid-market companies. She still takes on large, complex engagements. She is not, by nature, a suspicious person — she does not assume bad faith where administrative friction is the likelier explanation. But she has changed the way she structures her payment terms.
She now requires payment to be structured before work begins. She defines the split upfront — the percentage due at each milestone, the mechanism by which it moves, the parties who receive it. She does not invoice. She sends a payment link. When the client pays, the money moves.
She has not chased a payment since.
76% of businesses report they must address late invoice payments before focusing on growth. The ones who stop addressing them — because they have removed the conditions that create them — are the ones who are actually growing.
The consultant who invoiced four times before getting paid once did not fail to manage her client well. She failed to manage her payment architecture at all. That is the more expensive mistake. And it is the one that is entirely within her control to fix.
