Latest / Cash Flow Conversations with Fexingo: Working Capital, Receivables, and Small Business Finance / How Payment Triggers Prevent Late Invoice Disputes
Transcript
- Lucas: So you send an invoice for twenty thousand dollars worth of framing work. The contract says 'net 30 upon approval'. Thirty days later, no payment. You call the general contractor, and they say, 'Oh, we haven't approved the work yet — the supervisor hasn't signed off.' That approval process drags another three weeks. Suddenly your thirty-day term is a fifty-day term, and you've got payroll due next Friday. Luna: And the worst part is, that's not even a dispute — it's just a vague trigger. Nobody's arguing about the quality of the work. They're arguing about whether 'approval' happened. Lucas: Exactly. That's what I want to drill into today — payment triggers. The specific, verifiable condition that kicks off the payment clock. Most small businesses leave triggers fuzzy, and it costs them weeks of float. If today's conversation moves your work forward in some small way, honestly, if it was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. And listen, I know that's a small ask, but listener support is what keeps this show ad-free and focused on stuff like this. Luna: Yeah, totally fair. It takes two seconds and it really does help us keep going. So — back to triggers. What's the alternative to 'upon approval'? Lucas: The alternative is to tie payment to an event that leaves a timestamped digital record. For a construction subcontractor, that could be: the delivery receipt signed by the GC's foreman, or the weekly progress photo uploaded to the project management platform. Something the customer can't claim they didn't receive. Luna: Right — because 'delivery receipt signed' is a binary yes/no. 'Upon approval' is a feeling. Who decides when approval is granted? Lucas: Exactly the problem. I talked to a framing contractor in Columbus, Ohio, who rewrote his terms last year. He used to write 'net 30 upon completion of work to customer's satisfaction'. Now he writes: 'Net 30 from the earlier of: date of signed delivery receipt, or 14 days after last material delivered to site.' He said his average days sales outstanding dropped from 67 days to 41 days in four months. Luna: 41 versus 67 — that's over a third faster. What changed besides the wording? Lucas: The biggest shift was that disputes stopped being about timing. Before, the GC would sit on the invoice and then say, 'We're still reviewing.' Now the trigger is clear: the delivery receipt is signed the day the lumber shows up. If the GC wants to dispute the quality, they have to do it within those 14 days — they can't just delay the trigger. Luna: So the trigger separates the question of 'when is payment due?' from 'is the work acceptable?' Lucas: Exactly. And that's huge, because most late payments aren't malice — they're just muddy process. The GC's accounts payable team needs a concrete date to key into their system. If you give them 'upon approval', they can't enter a date until someone tells them approval happened. If you give them 'delivery receipt date plus 14 days', the AP clerk can schedule the payment immediately. Luna: That also means you earn trust with the AP team — you become the vendor who makes their job easy. I've heard that's worth a lot in terms of getting paid faster on future invoices. Lucas: Huge. Now, there's a second piece here that's less obvious: lien waivers. In construction, you often have to sign a lien waiver to get paid. And the trigger for when you sign that waiver is critical. A lot of subcontractors sign a 'conditional waiver upon receipt of check' — but the check hasn't cleared yet. Then the check bounces, and you've waived your lien rights. Luna: Oh, that's a nightmare. So the trigger for the waiver should be tied to something more reliable than 'receipt of check'. Lucas: Right. Better to use 'receipt of cleared funds' or 'date of electronic transfer confirmation'. That way the trigger for waiving your rights is the actual availability of money, not the piece of paper. I've seen subcontractors lose six-figure lien rights because they signed a waiver based on a check that hadn't cleared. Luna: So when you're negotiating payment terms, you want to define two triggers: one that starts the payment clock, and one that releases your security interest. And both should be anchored to objective events. Lucas: Exactly. And here's a framework I like: for each trigger, ask three questions. First, is the event verifiable by a third party? Second, does it produce a timestamp? Third, does the customer have sole control over it? You want the answer to the first two to be yes, and the third to be no. Luna: Sole control — like if the trigger is 'when the supervisor approves', the customer controls whether that ever happens. But 'when the delivery receipt is signed' — that's a shared event. Lucas: Exactly. Now, I should say this isn't just a construction problem. I see it in professional services all the time. A consultant sends an invoice 'upon completion of phase one deliverables'. What does completion mean? The client's internal reviewer hasn't read the report yet. So the trigger is stuck. Luna: Better to say 'upon delivery of phase one report via email' — that's a timestamped event. Or 'upon upload to shared folder'. Something the consultant can prove. Lucas: Yeah. And a lot of project management tools have this built in — you can set an invoice to trigger automatically when a task status changes to 'complete'. That removes human delay entirely. I know a marketing agency that ties invoice generation to the completion of a Trello card. The trigger is the card moving to 'Done'. Luna: Automated and objective. So it's not just about rewording your contract — it's about redesigning your workflow to create those triggers automatically. Lucas: Right. And the beauty is, customers often prefer it. Because if the trigger is clear, they don't have to manage your invoice approval process. Their AP system can just pay you on schedule. It reduces their administrative burden too. Luna: I want to go back to the DSO improvement — 67 to 41 days. How much cash did that free up for that contractor? Lucas: He told me about $180,000. Because his average monthly revenue was around $400,000, and he was carrying 67 days of receivables. At 41 days, he cut nearly a month of float. That's cash he didn't have to borrow. At a 7% interest rate, that saved him about $12,600 a year in financing costs. Luna: And that's just from rewriting a few sentences. No new software, no factoring, no chasing customers. Lucas: Exactly. It's the highest roi change a small business can make to their cash flow, because it costs nothing but a conversation with your customers. Now, the pushback I hear is: 'My customer won't accept those terms. They're a big company, they have standard terms.' Luna: And how do you handle that? Because that's a real concern. Lucas: You don't ask them to change their payment terms. You ask them to clarify the trigger. Say: 'I see your terms say net 30 upon acceptance. Can you tell me what acceptance means specifically? Is it the date the receiving dock signs for the goods?' Most of the time, they'll say yes, or they'll tell you what their actual internal trigger is. You're not asking for a discount or a faster term — you're asking for a definition. Luna: And if they refuse to clarify, that's a red flag. It means they want to keep the ambiguity so they can delay. Lucas: Exactly. And you can then decide whether you want to take that risk. But in my experience, most customers don't mind — because they want to pay you on time too. Their reputation depends on it. They just need you to make it easy for them. Luna: So the takeaway: look at your top five customers by revenue. Check what the actual trigger is on your invoices. If it's fuzzy — 'upon completion', 'upon satisfaction', 'upon approval' — rewrite it to something objective and timestamped. Then see how your DSO changes over the next 90 days. Lucas: That's exactly the exercise. And I'll add: if you use progress billing — like in a long construction project — set triggers for each progress milestone. Not just 'upon completion of 50% of work', but 'upon installation of drywall on floors 1 through 5' — something an inspector can verify. Luna: And document those triggers in the contract from the start. That way there's no surprise when you invoice. Lucas: Right. One more thing: if you're using an online invoicing platform, check whether you can set automatic payment reminders based on trigger dates. So if the trigger fires, the clock starts, and at day 30, the system sends a reminder automatically. That removes the human 'I forgot to follow up' factor. Luna: It's really about designing your cash flow system to be as deterministic as possible. Remove the ambiguity, remove the discretion, remove the human delay. Lucas: Exactly. And the businesses that do this well — they don't just get paid faster. They build better relationships with their customers, because both sides know exactly where they stand. Luna: Alright, I'm going to look at my own invoices this afternoon. Lucas, thanks for the nudge. Lucas: Happy to. And if you try it, let us know how it goes. We love hearing stories from listeners who tightened up their triggers.