Latest / Cash Flow Conversations with Fexingo: Working Capital, Receivables, and Small Business Finance / How Small Businesses Lose Cash To Overdue Invoices
Transcript
- Lucas: Let's start with a number that keeps small business owners awake at night. It's not profit margin, and it's not customer churn. It's the days sales outstanding, or DSO, creeping from forty-five days to sixty-five. We're seeing this across the board right now in October twenty twenty-six, where corporate payables departments are quietly extending terms from net thirty to net sixty just to manage their own liquidity. Luna: Right, because when rates are still elevated, holding onto cash becomes cheaper than paying suppliers immediately. So the risk shifts entirely to the vendor. Lucas: Exactly. And the cost isn't just the interest rate you'd pay on a line of credit. It's the opportunity cost of that capital sitting idle while your operations stall. Take a mid-sized manufacturing company we tracked last quarter. They had two million dollars tied up in overdue invoices, money that could have been used to buy inventory at a bulk discount or hire additional staff. Instead, they were borrowing against receivables at twelve percent APR just to keep the lights on. Luna: That's a brutal effective interest rate. Did they try to chase the debt, or did they just absorb the hit? Lucas: They tried everything. Late notices, phone calls, even threatening to stop shipments. But here's the thing about late payment costs killing small business margins: the act of chasing the invoice itself consumes hours of administrative time. You're paying your best account managers to send angry emails instead of closing new deals. The hidden tax is in the labor hours, not just the financing cost. Luna: So you're saying the operational drag is actually larger than the financial interest? That seems counterintuitive for most founders I talk to. Lucas: It is, until you map it out. If an accounts payable clerk spends fifteen minutes per day following up on five different overdue invoices, that's seventy-five minutes a day. Multiply that by the hourly wage plus benefits, and you're looking at thousands of dollars monthly in pure overhead. Plus, the relationship damage. When you have to escalate to a formal demand letter, you've already signaled that the partnership is strained. You might get paid, but you'll likely lose the next contract. Luna: I see. So the solution isn't to be more aggressive, but to make payment so frictionless that they have no reason to delay? Lucas: Precisely. And that brings us to the most underutilized tool in small business finance: the early payment discount. Most businesses think offering a two percent discount for payment within ten days is too expensive. But let's do the math. If you give up two percent to get paid in ten days instead of sixty, you're effectively earning an annualized return of roughly twenty-four percent on that cash. That's not a cost; it's a guaranteed investment yield. Luna: Wow. Twenty-four percent annualized is higher than almost any safe investment available right now. Why don't more businesses structure their terms this way? Lucas: Because it requires a mindset shift. They view discounts as a loss of revenue rather than a gain in liquidity. But consider the alternative: if the client delays payment by sixty days, you're financing their operation at zero percent. You're essentially giving them an interest-free loan. By offering a clear, automatic discount, you remove the ambiguity. The client chooses to pay early because it makes economic sense for them, too. Luna: It turns the dynamic from you begging for money to them choosing to invest in your relationship. That's a powerful reframe. Lucas: It is. And it works best when baked into the invoice automatically. Don't wait for the due date to remind them. Put the discount window right at the top. 'Pay within ten days and save two percent.' It creates urgency without aggression. Meanwhile, for those who don't take the discount, the full amount is due in thirty days. This separates the serious partners from the chronic late payers quickly. Luna: Does this work equally well for B2B service providers versus product manufacturers? The cash cycles feel different. Lucas: Actually, it works even better for services. A software consultancy or a marketing agency has lower fixed costs than a manufacturer. Their marginal cost of fulfilling the project is low, so preserving cash flow is critical for growth. A manufacturer might need that cash to buy raw materials, but a service provider needs it to pay salaries. Both benefit, but the liquidity pressure is often more immediate for services. Luna: Makes sense. Salaries don't negotiate. Raw materials might have some wiggle room. Lucas: Right. And speaking of wiggle room, let's talk about the middle ground. Not every client will pay in ten days. What about a tiered structure? Offer one percent off if paid within thirty days, and zero percent after that. It captures the moderate delayers and incentivizes them to move earlier without requiring the full sacrifice of the two percent discount. Luna: That feels like a pragmatic compromise. It acknowledges that life happens, but still rewards promptness. How do you enforce these terms without becoming the villain? Lucas: You automate the reminder. Use a system that sends a polite notification on day twenty-eight, another on day thirty-one, and a final notice on day thirty-five. No human interaction until day forty-five. This removes the emotional weight from your team. They aren't being rude; the system is just doing its job. It depersonalizes the collection process significantly. Luna: I love that. It protects the relationship because the bot is the bad guy, not your friend. Lucas: Exactly. And if they still don't pay by day forty-five, then you step in. But by then, you've given them every benefit of the doubt and every incentive to pay. You've documented the history. You have the paper trail. It makes any further escalation much stronger legally and relationally. Luna: So the key is structure over sentiment. Clear terms, automated nudges, and financial incentives. Lucas: Structure wins every time. Now, before we dive deeper into the specific tools for automating this, I want to pause for a moment. We deliberately don't run ads on these conversations. If you want to support that choice, the link is buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Yeah, it really helps keep the production quality high and the commentary independent when listeners chip in directly. Lucas: Thanks for keeping us going. Let's get back to the mechanics. Once you've set up these terms, how do you handle the actual reconciliation? Many small businesses still rely on email attachments and manual data entry. Luna: Oh, that's a nightmare. One wrong digit and the whole month gets thrown off. It's such a fragile process. Lucas: It is. And that fragility is where errors creep in. You miss a discount window because someone manually entered the data late. You apply a payment to the wrong invoice. These tiny errors compound. The fix is integrating your invoicing platform directly with your bank feed. When a payment comes in, the system matches it automatically based on the invoice number in the reference field. Luna: So you're telling clients to include the invoice number in the payment reference? That sounds simple, but does it actually work? Lucas: It works ninety percent of the time. For the ten percent that don't, you use ai powered matching tools that can recognize patterns in remittance advice. But the primary defense is making it easy for them to tell you what they paid. Include the invoice number prominently on the PDF. Maybe even add a QR code that links directly to a payment portal where they can select the invoice and pay instantly. Luna: QR codes on invoices? That feels futuristic for something as old-school as billing. Do people actually scan them? Lucas: They do, especially on mobile devices. If you're sending invoices via email, a clickable link is even better. Reduce the clicks to one. One click to open the invoice, one click to pay. Every extra step is a chance for distraction or procrastination. Friction kills conversion, even in payments. Luna: That's a great analogy. Treat your payment process like a checkout funnel. Minimize abandonment. Lucas: Spot on. And speaking of abandonment, let's talk about the psychology of the first invoice. If you send a messy, unclear invoice for your first project, the client learns that you're disorganized. They may delay payment simply because they don't trust your processes. Clarity signals professionalism. A clean invoice with clear terms builds confidence that future payments will be handled smoothly too. Luna: So the invoice is a branding tool, not just a bill. That changes how I'd design mine. Lucas: Absolutely. It's your first impression of your back-office operations. If the front office is polished but the back office is chaotic, the disconnect erodes trust. Consistency across the board reinforces reliability. Luna: I agree. Reliability is currency. Now, what about the bigger picture? If you optimize your receivables, you free up cash. But what do you do with that cash? Just sit in a savings account? Lucas: No, you deploy it strategically. Pay down high-interest debt first. That's a guaranteed return equal to your interest rate. Then, reinvest in growth initiatives that have a higher ROI than your cost of capital. Maybe it's marketing, maybe it's new equipment. The goal is to turn static cash into active assets. Luna: Active assets. I like that framing. It reminds me that cash isn't just safety; it's fuel. Lucas: Exactly. And the more fuel you have available quickly, the faster you can accelerate. Optimizing receivables isn't just about survival; it's about velocity. It allows you to pivot faster than competitors who are bogged down by slow-paying clients. Luna: So in a tight market, the company that collects fastest actually wins, regardless of who has the prettiest logo. Lucas: Always. Speed is the ultimate competitive advantage in business finance. Everything else is secondary.