The Quiet Cash Leaks Draining Your Business
Most cash problems don’t explode—they drip. Use this practical playbook to find revenue and cost leaks, fix the systems behind them, and prevent their return.
By TheMurrow Editorial
January 10, 2026
Key Points
- 1Diagnose quiet cash leaks by separating revenue reversals, slow collections, and avoidable spend—then assign ownership so “normal” losses stop compounding.
- 2Prevent chargebacks and fraud by improving billing clarity, customer communications, and exception policies—because many disputes start as confusion, not crime.
- 3Run a monthly find-fix-prevent audit across disputes, A/R aging, SaaS renewals, and facilities costs to catch drift early without building bureaucracy.
The cash problem that rarely looks like a cash problem
Most cash problems don’t arrive with drama. They arrive quietly—one disputed charge here, one forgotten software renewal there, a few invoices that slip from “net 30” to “whenever.” Nothing breaks. No one panics. Then the quarter closes and the numbers feel oddly tight, as if the business is working harder for the same results.
The most frustrating part is psychological: leaders often treat cash pressure as a revenue problem (“we need more sales”) when it’s frequently a retention problem (“we’re not keeping what we already earned”). Quiet cash leaks don’t announce themselves as fraud, waste, or operational drift. They show up as “normal,” which is why they persist.
The data points are not small. Global payment card fraud losses reached $33.83 billion in 2023, according to the Nilson Report (reported Jan. 6, 2025). The U.S., notably, accounted for 25.29% of global card volume but 42.32% of fraud losses. Meanwhile, companies trying to manage cash flow run into a different leak: Atradius reports late payments affect around half of B2B invoices, and bad debts average about 6% of B2B sales on credit.
The most frustrating part is psychological: leaders often treat cash pressure as a revenue problem (“we need more sales”) when it’s frequently a retention problem (“we’re not keeping what we already earned”). Quiet cash leaks don’t announce themselves as fraud, waste, or operational drift. They show up as “normal,” which is why they persist.
The data points are not small. Global payment card fraud losses reached $33.83 billion in 2023, according to the Nilson Report (reported Jan. 6, 2025). The U.S., notably, accounted for 25.29% of global card volume but 42.32% of fraud losses. Meanwhile, companies trying to manage cash flow run into a different leak: Atradius reports late payments affect around half of B2B invoices, and bad debts average about 6% of B2B sales on credit.
Cash rarely disappears in one catastrophic event. It evaporates in small, tolerated exceptions.
— — TheMurrow Editorial
This article is a playbook for finding the leaks, fixing them, and preventing their return—without turning your company into a compliance factory. The point isn’t paranoia. The point is precision.
$33.83B
Global payment card fraud losses in 2023, per the Nilson Report (reported Jan. 6, 2025).
The taxonomy: where money slips away without raising alarms
Quiet cash leaks tend to fall into two buckets: revenue leaks (money you earned but don’t keep) and cost leaks (money you spend without realizing it’s avoidable). Both hide behind normal business activity, which makes them hard to see in aggregate.
The trick is not to hunt for a single villain. Quiet cash leaks usually survive because they’re distributed—across teams, tools, customers, and months. That diffusion keeps any one loss from feeling urgent, even when the combined effect is large.
To make the problem actionable, you need language that separates what’s happening: money reversed after the sale, money never collected on time, and money spent that doesn’t produce value. Once you can label the leak type, you can assign ownership and choose fixes that reduce future work rather than creating a permanent cleanup cycle.
The trick is not to hunt for a single villain. Quiet cash leaks usually survive because they’re distributed—across teams, tools, customers, and months. That diffusion keeps any one loss from feeling urgent, even when the combined effect is large.
To make the problem actionable, you need language that separates what’s happening: money reversed after the sale, money never collected on time, and money spent that doesn’t produce value. Once you can label the leak type, you can assign ownership and choose fixes that reduce future work rather than creating a permanent cleanup cycle.
Revenue leaks: you “made” the sale, but you don’t keep it
Revenue leaks often look like administrative friction rather than financial loss:
- Chargebacks and disputes that reverse legitimate payments
- Fraud losses that bypass controls
- Receivables drag, where slow-paying customers turn profits into a working-capital strain
Sift’s disputes data offers a useful directional signal: chargeback rates fell early in 2025 but climbed to 0.26% by Q3 2025, a 53% increase versus Q1. Vendor research isn’t gospel, but it reflects a reality many finance teams recognize: disputes rise when customers feel squeezed, confused, or emboldened.
The key is to treat disputes and slow collections as a retention issue, not merely a finance back-office headache. The money was earned—at least on paper. The leak happens in the gap between the transaction and what actually settles, clears, or gets paid.
- Chargebacks and disputes that reverse legitimate payments
- Fraud losses that bypass controls
- Receivables drag, where slow-paying customers turn profits into a working-capital strain
Sift’s disputes data offers a useful directional signal: chargeback rates fell early in 2025 but climbed to 0.26% by Q3 2025, a 53% increase versus Q1. Vendor research isn’t gospel, but it reflects a reality many finance teams recognize: disputes rise when customers feel squeezed, confused, or emboldened.
The key is to treat disputes and slow collections as a retention issue, not merely a finance back-office headache. The money was earned—at least on paper. The leak happens in the gap between the transaction and what actually settles, clears, or gets paid.
0.26%
Chargeback rate by Q3 2025 in Sift’s disputes data, a 53% increase versus Q1 (directional vendor signal).
Cost leaks: you pay, but you don’t benefit
Cost leaks usually wear the disguise of convenience:
- Unused SaaS seats and redundant tools
- Facilities overhead drift, where energy costs creep upward slowly
- Auto-renewals that survive because canceling is tedious
Zylo’s 2024 SaaS Management Index—based on 30 million licenses and $34B+ in spend under management—claims organizations use only 49% of provisioned licenses, creating what it calls a “license graveyard.” Even if your company is smaller than Zylo’s typical benchmark, the mechanism scales down: unused seats are unused seats.
These leaks persist because they feel low-stakes. A few seats here, an unnoticed renewal there, slightly higher utility bills month after month—none of it triggers an alarm. But together they function like a hidden tax on the business.
- Unused SaaS seats and redundant tools
- Facilities overhead drift, where energy costs creep upward slowly
- Auto-renewals that survive because canceling is tedious
Zylo’s 2024 SaaS Management Index—based on 30 million licenses and $34B+ in spend under management—claims organizations use only 49% of provisioned licenses, creating what it calls a “license graveyard.” Even if your company is smaller than Zylo’s typical benchmark, the mechanism scales down: unused seats are unused seats.
These leaks persist because they feel low-stakes. A few seats here, an unnoticed renewal there, slightly higher utility bills month after month—none of it triggers an alarm. But together they function like a hidden tax on the business.
The most expensive line items are the ones no one feels responsible for.
— — TheMurrow Editorial
The rest of this piece breaks these leak types into practical diagnostics and repairs—starting with the one that hits fastest: payment disputes.
Chargebacks and disputes: the revenue you already “won” can still vanish
Card payments feel final. They’re not. Disputes can pull revenue back weeks after the sale, and the operational overhead—customer support time, evidence gathering, payment processor fees—creates a second, quieter loss.
The macro picture is sobering. The Nilson Report puts global payment card fraud losses at $33.83B in 2023, up from $33.45B in 2022 (reported Jan. 6, 2025). Even more revealing: the U.S. generates 25.29% of global card volume but 42.32% of fraud losses. That imbalance signals a system where fraud economics are particularly favorable for bad actors.
Disputes sit at the intersection of customer experience and payment rails. When a charge is unclear or a cancellation is messy, the bank dispute process becomes a customer’s fastest lever. The business loses twice: first in revenue pulled back, then in internal time spent reacting.
The macro picture is sobering. The Nilson Report puts global payment card fraud losses at $33.83B in 2023, up from $33.45B in 2022 (reported Jan. 6, 2025). Even more revealing: the U.S. generates 25.29% of global card volume but 42.32% of fraud losses. That imbalance signals a system where fraud economics are particularly favorable for bad actors.
Disputes sit at the intersection of customer experience and payment rails. When a charge is unclear or a cancellation is messy, the bank dispute process becomes a customer’s fastest lever. The business loses twice: first in revenue pulled back, then in internal time spent reacting.
42.32%
Share of global card fraud losses attributed to the U.S., despite only 25.29% of global card volume (Nilson Report; reported Jan. 6, 2025).
First-party fraud vs. “honest confusion”
Disputes aren’t always organized criminal fraud. Sift argues first-party fraud—a customer disputing a legitimate charge—has become a major driver, estimating it was 36% of reported fraud in 2024, up from 15% a year earlier. Because this is vendor research, treat it as a directional indicator rather than a definitive industry statistic. Still, it matches what many subscription and digital merchants see: “I don’t recognize this” often means “I regret this” or “I forgot I signed up.”
A fair counterpoint deserves airtime. Customers dispute charges for legitimate reasons, too:
- unclear billing descriptors
- confusing trial-to-paid transitions
- difficult cancellation flows
- delayed fulfillment or support breakdowns
Many “fraud” narratives collapse into service design problems.
A fair counterpoint deserves airtime. Customers dispute charges for legitimate reasons, too:
- unclear billing descriptors
- confusing trial-to-paid transitions
- difficult cancellation flows
- delayed fulfillment or support breakdowns
Many “fraud” narratives collapse into service design problems.
Practical fixes: reduce disputes before they become “fraud”
Merchants can’t control the economy, but they can control clarity. Effective steps usually include:
- Tightening billing descriptors so customers recognize the charge
- Improving receipts and renewal notices (especially for subscriptions)
- Shortening time-to-resolution for customer complaints so disputes don’t become their chosen channel
- Documenting delivery and consent in a way that’s easy to retrieve
The goal is to win more disputes, yes—but more importantly, to prevent them. Disputes are often a symptom that customers and merchants are not aligned on what was promised.
- Tightening billing descriptors so customers recognize the charge
- Improving receipts and renewal notices (especially for subscriptions)
- Shortening time-to-resolution for customer complaints so disputes don’t become their chosen channel
- Documenting delivery and consent in a way that’s easy to retrieve
The goal is to win more disputes, yes—but more importantly, to prevent them. Disputes are often a symptom that customers and merchants are not aligned on what was promised.
Dispute prevention checklist
- ✓Tighten billing descriptors so charges are instantly recognizable
- ✓Improve receipts and renewal notices, especially for subscriptions
- ✓Shorten time-to-resolution so support beats the bank dispute process
- ✓Document delivery and consent in a way that is easy to retrieve
Fraud is rising—and it’s shifting toward manipulation, not just stolen cards
Fraud headlines make it sound like the problem is purely technical. A different story is emerging: fraud increasingly exploits human behavior rather than security holes.
A Reuters report (Dec. 15, 2025) on the European Central Bank’s data notes EU/EEA payment fraud totaled €4.2B in 2024, up from €3.5B in 2023. The ECB emphasizes that strong customer authentication remains effective, yet fraud is “shifting toward payer manipulation.” Translation: criminals are getting better at convincing legitimate users to authorize payments themselves.
That shift matters for businesses because it changes what “prevention” looks like. You can harden systems, but you also need to harden decision points—how customers interpret prompts, how employees handle exceptions, how fast a suspicious request is escalated.
A Reuters report (Dec. 15, 2025) on the European Central Bank’s data notes EU/EEA payment fraud totaled €4.2B in 2024, up from €3.5B in 2023. The ECB emphasizes that strong customer authentication remains effective, yet fraud is “shifting toward payer manipulation.” Translation: criminals are getting better at convincing legitimate users to authorize payments themselves.
That shift matters for businesses because it changes what “prevention” looks like. You can harden systems, but you also need to harden decision points—how customers interpret prompts, how employees handle exceptions, how fast a suspicious request is escalated.
€4.2B
EU/EEA payment fraud total in 2024, up from €3.5B in 2023 (Reuters reporting on ECB data; Dec. 15, 2025).
A real-world example: when authentication works, criminals change tactics
Consider the logic chain. If authentication makes it harder to use stolen credentials, criminals pursue:
- social engineering that pressures users to approve a payment
- impersonation that triggers a “helpful” internal override
- confusion tactics that blur legitimate and illegitimate requests
The practical takeaway is uncomfortable: fraud prevention becomes partly an education and process design issue. Finance, support, and product teams all share the burden.
- social engineering that pressures users to approve a payment
- impersonation that triggers a “helpful” internal override
- confusion tactics that blur legitimate and illegitimate requests
The practical takeaway is uncomfortable: fraud prevention becomes partly an education and process design issue. Finance, support, and product teams all share the burden.
What prevention looks like when humans are the target
A fraud strategy that assumes only “bad cards” misses modern risk. Better approaches focus on:
- Clear, consistent customer communications (so impersonation stands out)
- Exception policies that require verification steps before overrides
- Fast internal reporting loops so suspicious patterns surface early
- Clear, consistent customer communications (so impersonation stands out)
- Exception policies that require verification steps before overrides
- Fast internal reporting loops so suspicious patterns surface early
When security improves, fraud doesn’t disappear. It adapts—and usually toward the easiest human shortcut.
— — TheMurrow Editorial
The lesson from the ECB framing is not “authentication failed.” It’s that authentication alone can’t carry the whole system.
Key Insight
Modern fraud prevention is as much about communication and exception-handling as it is about technical controls—because manipulation targets people, not just systems.
Receivables drag: the slow leak that turns profits into panic
Many companies don’t go broke because margins are bad. They go broke because cash arrives late.
Atradius’ Payment Practices Barometer for North America/USMCA 2024 reports late payments affect around half of B2B invoices, and bad debts average roughly 6% of B2B sales on credit. Those figures describe not just a cash-flow inconvenience, but a strategic constraint: late payments force companies to borrow, delay hiring, or ration inventory.
Receivables drag is especially dangerous because it disguises itself as growth. You can be “selling” more and still feel poorer, because the balance sheet is filling with money owed instead of cash in bank. The operational cost is subtle too: more follow-ups, more exceptions, more time spent negotiating what should have been predictable.
Atradius’ Payment Practices Barometer for North America/USMCA 2024 reports late payments affect around half of B2B invoices, and bad debts average roughly 6% of B2B sales on credit. Those figures describe not just a cash-flow inconvenience, but a strategic constraint: late payments force companies to borrow, delay hiring, or ration inventory.
Receivables drag is especially dangerous because it disguises itself as growth. You can be “selling” more and still feel poorer, because the balance sheet is filling with money owed instead of cash in bank. The operational cost is subtle too: more follow-ups, more exceptions, more time spent negotiating what should have been predictable.
Understanding DSO—and why benchmarks can mislead
Days Sales Outstanding (DSO) is often treated as a universal scorecard. AFP notes many companies aim for DSO under 45 days, while stressing that benchmarks vary by industry. AFP also cites a Zone & Co. 2024 survey with sample industry averages (for example, distribution/transportation at 41; energy/utilities at 19). The more useful comparison is often internal: your DSO now versus your DSO last year.
A DSO target that ignores customer mix can backfire. Tightening terms too aggressively can cost sales. Extending terms indiscriminately can create growth that starves the business.
A DSO target that ignores customer mix can backfire. Tightening terms too aggressively can cost sales. Extending terms indiscriminately can create growth that starves the business.
Practical fixes: stop treating collections as an afterthought
Receivables improvements tend to come from boring, consistent moves:
- Clarify terms upfront and repeat them on invoices
- Invoice promptly (delays are self-inflicted DSO inflation)
- Standardize follow-up so reminders aren’t ad hoc or emotional
- Segment customers: apply tougher processes to the accounts most likely to slip
A credible policy isn’t punitive. It’s predictable. Many late-pay cycles persist because customers learn that consequences are negotiable.
- Clarify terms upfront and repeat them on invoices
- Invoice promptly (delays are self-inflicted DSO inflation)
- Standardize follow-up so reminders aren’t ad hoc or emotional
- Segment customers: apply tougher processes to the accounts most likely to slip
A credible policy isn’t punitive. It’s predictable. Many late-pay cycles persist because customers learn that consequences are negotiable.
Receivables discipline checklist
- ✓Clarify terms upfront and repeat them on invoices
- ✓Invoice promptly to avoid self-inflicted DSO inflation
- ✓Standardize follow-up so reminders are consistent, not ad hoc
- ✓Segment customers and apply tougher processes to chronic late payers
SaaS waste: the modern “office supply closet” no one audits
Software spending is deceptively easy. A tool solves a real problem, a team adds a few seats, then a few more. Renewal arrives. Nobody wants to be the person who breaks a workflow. Over time, the stack turns into a museum of good intentions.
Zylo’s 2024 SaaS Management Index (Feb. 27, 2024) provides the starkest snapshot: across its dataset, companies use only 49% of provisioned licenses. Zylo also claims an average of $18M in annual license waste for enterprises. Most readers won’t map to that dollar figure—but most readers will recognize the pattern: unused seats, overlapping tools, and “we’ll cancel later.”
The quiet leak is not just the subscription cost. It’s the institutional reluctance to touch tools once they’re embedded, even when usage has faded. That reluctance becomes a budget line that renews on autopilot.
Zylo’s 2024 SaaS Management Index (Feb. 27, 2024) provides the starkest snapshot: across its dataset, companies use only 49% of provisioned licenses. Zylo also claims an average of $18M in annual license waste for enterprises. Most readers won’t map to that dollar figure—but most readers will recognize the pattern: unused seats, overlapping tools, and “we’ll cancel later.”
The quiet leak is not just the subscription cost. It’s the institutional reluctance to touch tools once they’re embedded, even when usage has faded. That reluctance becomes a budget line that renews on autopilot.
The small-business version of the license graveyard
You don’t need 10,000 employees to leak money through software. A 50-person firm can burn real cash by:
- paying for premium tiers no one uses
- carrying multiple tools for the same job (project management, chat, file storage)
- keeping ex-employee accounts active because offboarding is manual
SaaS waste is also a governance problem. IT may not own every purchase. Finance may not see the usage. Team leads may not know what renews when.
- paying for premium tiers no one uses
- carrying multiple tools for the same job (project management, chat, file storage)
- keeping ex-employee accounts active because offboarding is manual
SaaS waste is also a governance problem. IT may not own every purchase. Finance may not see the usage. Team leads may not know what renews when.
Practical fixes: make ownership unavoidable
A sane SaaS cleanup doesn’t start with a spreadsheet crusade. It starts with ownership and cadence:
- Assign a tool owner for each major system
- Review active users vs. paid seats before renewal
- Require a simple justification for new tools: what replaces what?
The aim isn’t to centralize every decision. It’s to prevent drift—the silent multiplication of subscriptions that nobody can defend six months later.
- Assign a tool owner for each major system
- Review active users vs. paid seats before renewal
- Require a simple justification for new tools: what replaces what?
The aim isn’t to centralize every decision. It’s to prevent drift—the silent multiplication of subscriptions that nobody can defend six months later.
Tool ownership rule
If a system renews, someone must own it: an accountable tool owner reviews seats vs. active users before renewal and documents what it replaces.
Facilities and energy drift: the overhead leak hiding in plain sight
Energy waste is an old problem that still behaves like a modern one: gradual, hard to attribute, and easy to postpone.
ENERGY STAR (U.S. EPA) says that following its staged approach, most buildings can cost-effectively cut energy use about 30%. That figure isn’t a guarantee—building type and capital constraints matter—but it frames a reality: many organizations run facilities below their achievable efficiency because no one is accountable for incremental improvement.
The U.S. Department of Energy’s Better Buildings Initiative adds a long-view data point: partners have saved nearly $22B since 2011 through efficiency improvements (progress reported Sept. 16, 2024). The magnitude matters less than the implication: operational savings compound, and institutions that treat efficiency as a program—not a one-time retrofit—capture far more value.
ENERGY STAR (U.S. EPA) says that following its staged approach, most buildings can cost-effectively cut energy use about 30%. That figure isn’t a guarantee—building type and capital constraints matter—but it frames a reality: many organizations run facilities below their achievable efficiency because no one is accountable for incremental improvement.
The U.S. Department of Energy’s Better Buildings Initiative adds a long-view data point: partners have saved nearly $22B since 2011 through efficiency improvements (progress reported Sept. 16, 2024). The magnitude matters less than the implication: operational savings compound, and institutions that treat efficiency as a program—not a one-time retrofit—capture far more value.
A practical example: “small” maintenance that pays
The common misconception is that energy savings require major construction. In practice, many wins come from:
- scheduling and set-point discipline
- basic maintenance that keeps systems operating as designed
- catching anomalies early instead of paying for them all season
Even modest steps can reduce volatility. Lower variability in overhead creates clearer forecasting and less pressure to “make it up” elsewhere.
- scheduling and set-point discipline
- basic maintenance that keeps systems operating as designed
- catching anomalies early instead of paying for them all season
Even modest steps can reduce volatility. Lower variability in overhead creates clearer forecasting and less pressure to “make it up” elsewhere.
The managerial takeaway: measure what you can control
Energy is often treated as a fixed cost. It isn’t. Treat it as a managed cost with periodic review, and drift becomes visible. Treat it as background noise, and you’ll keep paying for inefficiency you can’t even name.
Editor's Note
Overhead drift is rarely a single fix—it’s a cadence: schedule discipline, basic maintenance, and anomaly detection repeated often enough that “normal” doesn’t expand.
Building a “find, fix, prevent” cash-leak audit you’ll actually maintain
Most leak audits fail because they’re framed as one heroic clean-up. The better model is lighter and more frequent: a repeatable check that surfaces exceptions before they become normal.
The goal is not perfection; it’s detection. A monthly rhythm is often enough to reveal drift in disputes, receivables, renewals, and overhead. When you institutionalize the review, the business stops relying on memory, heroics, or whoever happens to notice.
What makes this sustainable is that each category has an owner and a simple question that keeps the review grounded: What changed since last month? Not “Are we perfect?” Change is where leaks reveal themselves.
The goal is not perfection; it’s detection. A monthly rhythm is often enough to reveal drift in disputes, receivables, renewals, and overhead. When you institutionalize the review, the business stops relying on memory, heroics, or whoever happens to notice.
What makes this sustainable is that each category has an owner and a simple question that keeps the review grounded: What changed since last month? Not “Are we perfect?” Change is where leaks reveal themselves.
Find: where to look first
Start where the data is already concentrated:
- Payment disputes and chargebacks (by product line and channel)
- Receivables aging (especially accounts that routinely slip)
- SaaS renewals (calendarized, with seat counts)
- Facilities costs (seasonally adjusted comparisons)
The point is not to capture every possible leak. The point is to identify the largest, most frequent ones that recur.
- Payment disputes and chargebacks (by product line and channel)
- Receivables aging (especially accounts that routinely slip)
- SaaS renewals (calendarized, with seat counts)
- Facilities costs (seasonally adjusted comparisons)
The point is not to capture every possible leak. The point is to identify the largest, most frequent ones that recur.
Fix: correct the system, not just the symptom
The strongest fixes reduce future work:
- Prevent disputes through clarity, not just better dispute responses
- Reduce DSO through predictable invoicing and follow-up, not last-minute pressure
- Cut SaaS waste through ownership and renewal discipline, not one-time cancellations
- Lower energy drift through maintenance and measurement, not sporadic initiatives
- Prevent disputes through clarity, not just better dispute responses
- Reduce DSO through predictable invoicing and follow-up, not last-minute pressure
- Cut SaaS waste through ownership and renewal discipline, not one-time cancellations
- Lower energy drift through maintenance and measurement, not sporadic initiatives
Prevent: assign responsibility and cadence
Prevention is governance with a human face. Assign each leak category to someone who can act, then set a review rhythm. Monthly is often enough to keep the problem from regrowing.
A helpful standard is to ask one question in each review: What changed since last month? Not “Are we perfect?” Change is where leaks reveal themselves.
A helpful standard is to ask one question in each review: What changed since last month? Not “Are we perfect?” Change is where leaks reveal themselves.
Monthly cash-leak audit (find, fix, prevent)
- 1.Find: Review disputes/chargebacks, A/R aging, SaaS renewals with seats, and seasonally adjusted facilities costs
- 2.Fix: Choose system-level repairs that reduce future work, not just one-time cleanup actions
- 3.Prevent: Assign an owner per leak category and ask “What changed since last month?” on a monthly cadence
Conclusion: the discipline of keeping what you earn
Quiet cash leaks thrive on ambiguity—about who owns the problem, about what “normal” looks like, about whether small losses matter. Yet the numbers show small losses add up quickly. Card fraud alone reached $33.83B globally in 2023, while late payments hit around half of B2B invoices and bad debts average ~6% of credit sales, per Atradius. On the cost side, Zylo’s dataset suggests organizations use only 49% of provisioned licenses, and ENERGY STAR argues many buildings can cut energy use around 30% cost-effectively.
The deeper lesson is cultural. Companies that keep cash well don’t necessarily sell more. They argue less with reality. They measure what’s happening, name ownership clearly, and reduce the number of places where “we’ll fix it later” can hide.
No dramatic overhaul is required. Just a refusal to tolerate quiet losses as the price of doing business.
The deeper lesson is cultural. Companies that keep cash well don’t necessarily sell more. They argue less with reality. They measure what’s happening, name ownership clearly, and reduce the number of places where “we’ll fix it later” can hide.
No dramatic overhaul is required. Just a refusal to tolerate quiet losses as the price of doing business.
No dramatic overhaul is required. Just a refusal to tolerate quiet losses as the price of doing business.
— — TheMurrow Editorial
T
About the Author
TheMurrow Editorial is a writer for TheMurrow covering business & money.
Frequently Asked Questions
What’s the difference between a revenue leak and a cost leak?
A revenue leak happens when you earn money but fail to keep it—through disputes, fraud, or slow collections. A cost leak happens when you spend money without receiving proportional value—unused software seats, redundant tools, or energy drift. Both are dangerous because they feel “normal” and don’t trigger alarms until they accumulate.
Are chargebacks always fraud?
No. Some chargebacks reflect true fraud, but many stem from confusion or dissatisfaction—unclear billing descriptors, trial-to-paid surprises, or poor customer support. Sift’s research suggests first-party fraud is rising, but businesses should also examine service design issues that push customers toward disputes as their fastest resolution path.
What statistics best capture payment risk right now?
The Nilson Report estimates global payment card fraud losses at $33.83B in 2023 (reported Jan. 6, 2025). It also found the U.S. produced 25.29% of global card volume but 42.32% of fraud losses, indicating disproportionate exposure. Separately, Sift reports chargebacks climbed to 0.26% by Q3 2025, up 53% versus Q1—a useful directional signal.
How do I know if my DSO is “bad”?
AFP notes many companies aim for DSO under 45 days, but “good” varies by industry and customer mix. A more reliable test compares your DSO to your own prior periods and to peers where possible. Atradius’ finding that late payments affect around half of B2B invoices shows the problem is widespread—meaning improvement often comes from discipline, not miracles.
What’s the fastest way to reduce SaaS waste without breaking workflows?
Start with renewals and seat counts. Zylo reports only 49% of provisioned licenses are used across its dataset, which implies immediate gains from reclaiming unused seats before renewal dates. Assign an internal owner per tool, review paid seats versus active users, and require teams to justify overlaps when multiple apps do the same job.
How often should a company run a cash-leak audit?
Monthly reviews catch drift early without creating bureaucracy. Focus each cycle on a few categories—disputes, receivables aging, SaaS renewals, and facilities costs—and ask what changed since last month. Quiet leaks flourish when nobody is looking; they shrink when someone is accountable on a predictable cadence.
