AR Follow-Up Cadence Design for Net-30 and Net-60 Terms

Late B2B payments aren't usually a "won't pay" problem. They're a "when do we remind them, and how" problem, and most companies solve it with the same tired trick: one cadence, applied to every invoice, regardless of whether the terms are Net-30 or Net-60. That's like using the same recipe for a soft-boiled egg and a slow-braised brisket and wondering why one comes out wrong. Net-30 and Net-60 invoices age on different clocks, hit different failure points, and need cadences built around those differences from day one.

Industry research consistently finds that a large share of B2B invoices in the US get paid late. Not because buyers are dodging bills. Late payment is usually a process failure. The Federal Reserve's 2025 report backs this up from another angle: 51% of small businesses say uneven cash flow is a serious financial problem, and slow-moving accounts receivable is the quiet engine behind that number. Net-30 in practice often stretches to 45 or 60 days before money actually lands, and that gap between the term on the invoice and the term in reality is the working capital squeeze finance leaders feel every month but rarely name out loud. A good chunk of late payments, roughly a third, happen simply because the invoice got buried or forgotten, not because anyone decided not to pay. That's not a collections problem. That's a reminder problem, and reminder problems have structural fixes.

How Net-30 and Net-60 terms create different risk windows from day one

Net-30 means 30 straight calendar days from the invoice date, weekends and holidays included, unless the contract says the clock starts at receipt instead (it should say which, clearly, in writing, so nobody's guessing). Net-60 shows up most in construction, big corporate accounts, and government or enterprise deals, anywhere a payment has to clear several layers of approval before a check gets cut.

Net-30 is the workhorse term. Roughly half of all B2B invoices run on it, according to the PYMNTS B2B Payments Report, so it's the baseline case most AR teams handle in bulk, day in and day out.

The cash float difference is where things get uncomfortable. A company billing $1M a month on Net-60 terms carries roughly double the outstanding receivables at any given moment compared to the same company on Net-30. Double the money sitting out there, unspendable, un-payroll-able, just waiting. That's not a rounding error. That's a structural lockup of cash, and it happens before anything even goes wrong.

And plenty can go wrong with Net-60 that simply doesn't apply to Net-30. Big buyers run multi-step approval chains, so one billing error can bounce an invoice clean out of this cycle and into the next. A missing PO number or a typo on a timesheet can freeze payment for weeks. And if one large Net-60 account represents a meaningful slice of revenue, a single delay on their end can ripple straight into somebody else's payroll. Layer on the fact that write-off risk climbs sharply the longer an invoice ages without follow-up, and the picture gets clear fast: the risk window opens at a different point for each term, and the approval complexity is different too. Run the same cadence on both, and one of them gets shortchanged. Every time.

The shared architecture underlying any effective follow-up cadence

Every touchpoint should trigger off the due date, not the calendar and not the invoice date. Two clients invoiced on different days of the month need to move through the same relative timeline, not land on the same calendar date. Otherwise the whole system turns into a mess of exceptions.

That means automation has to actually read the payment term attached to each invoice. Not just log the invoice date and call it done. A Net-60 clock starts a full 30 days later than a Net-30 clock, even on invoices issued the same day. If that distinction is missed, the automation is just guessing.

Underneath the timing, four tone phases apply no matter the term:

• Phase 1, pre-due and early overdue. Friendly, informational, benefit of the doubt. "In case this slipped through" is the vibe.
• Phase 2, mid overdue. Drop the friendly-reminder language. State the invoice number, the amount, the days overdue, and the consequences. No apologizing for asking to be paid.
• Phase 3, late overdue. Formal notice, reference any late fees sitting in the original contract, set a clear deadline.
• Phase 4, seriously overdue. A human steps in, a Controller or senior leader sends a direct message. The change in sender alone signals seriousness an automated email never will.

Channel matters as much as tone. Email carries the early touches, but once several emails go unanswered, phone and SMS need to enter the mix. SMS reminders reach buyers through a different channel than email, so relying on inbox-only outreach past the midpoint of a cadence is leaving speed on the table. And a phone call surfaces things email never will: "oh, that invoice bounced out of our system three weeks ago" is the kind of sentence that only comes out on a call, and it's often the fastest way to unstick a stalled payment.

There's a psychological piece too. A cadence that shows up on a predictable schedule reads as routine, as process, not as someone being difficult. Irregular follow-up reads as either sloppy or aggressive, neither of which helps collect a check. And not every account needs the same pace. Dunning sequences should flex based on the risk and payment history attached to that specific customer, so a reliable payer isn't getting the same escalation speed as an account with a track record of paying late.

The Net-30 follow-up cadence: touchpoint timing and escalation triggers

Thirty days is a tight window, so the first reminder has to go out early enough to beat processing lag, not after it's already eaten the clock.

• Day -3 to -5: Pre-due reminder. Friendly, confirms invoice details and payment method. Sending invoices within 24 hours of delivery can shave days off collection time on its own, and automated reminder cadences outperform manual chasing by weeks, not days.
• Day 0: Due-date notice. Neutral tone, payment link included.
• Day +3: First overdue follow-up. Still friendly, still assuming a processing delay rather than a refusal.
• Day +7: Second follow-up. Tone starts to firm up, restate the amount and days overdue, ask for confirmation of status.
• Day +14: Firm follow-up. Factual, no apology, reference consequences. Phone or SMS should be in play by now at the latest.
• Day +21: Escalation reminder. Reference late fee terms if they exist, set a resolution deadline.
• Day +30: Formal notice. Written, structured, tied to contract language.
• Day +45: Senior leader outreach. A Controller sends a direct, personal message, escalating to a senior contact on the buyer's side if the usual person has gone quiet.
• Day +60: Formal demand or collections consideration. This is the point to signal a legal path is possible without actually filing anything yet.

Contact within 48 hours of a missed payment collects far more often than waiting two weeks does. For Net-30, Day +1 or Day +3 outreach is essential. It's the whole game. And once a customer pays late on one invoice with zero pushback, that becomes the new normal for every invoice after it. The cadence isn't just protecting this payment, it's protecting the relationship's ground rules.

Send to a named billing contact whenever possible, avoiding a shared AP inbox where invoices go to die a quiet, forgotten death. And consider offering an early payment discount tied to payment within a short window, right in the pre-due reminder. It gives fast movers a reason to move even faster.

The Net-60 follow-up cadence: why a longer term demands earlier intervention, not later

The natural instinct is to treat Net-60 like Net-30 with an extra month tacked on. That instinct is wrong, and it's wrong in a way that costs real money. A longer window means more time for an invoice to get buried, more approval steps to trip over, and a single mid-cycle error can shove payment into an entirely new cycle, adding weeks with zero warning.

Pre-due reminders here reduce the odds that an invoice gets buried or forgotten before it's even due, catching the failure before it starts rather than after.

• Day -14: First pre-due reminder. Purely informational, confirms the invoice exists, the amount, and the due date.
• Day -7: Second pre-due reminder. Flags the coming due date, confirms payment method and contact.
• Day 0: Due-date notice.
• Day +7: First overdue follow-up. Friendly, assumes lag in a complicated AP process.
• Day +14: Firm follow-up. Factual, restates amount and days overdue. Phone enters the mix here.
• Day +21: Escalation reminder. Reference late fees, ask the AP lead directly for a status update.
• Day +30: Formal notice. Structured, contract-referenced, deadline attached.
• Day +45 to +60: Senior leader outreach, escalating to finance leadership on the buyer's side if needed.
• Day +75 to +90: Formal demand or collections path.

Documentation matters more here too. In supplier portal environments like Coupa or Ariba, keeping a clear record of each submission is essential, because a rejected invoice with no follow-up trail can sit unresolved for a significant stretch with nobody noticing until it's a real problem.

And if that Net-60 buyer is a big enough slice of revenue, one delay on their end becomes a payroll conversation on this end. The early cadence is risk management wearing a reminder-email costume, not just a way to get paid faster. Enterprise relationships can carry a slightly longer friendly phase out of professional courtesy, sure. But the firm and formal phases still need to fire on schedule. Deference is not a strategy.

Operational blockers that cadences must account for beyond simple non-payment

A cadence only works if the information inside it actually gets where it's going. Most of the time, the invoice isn't stuck because the customer is being difficult. It's stuck because of something mundane and fixable:

• Sent to a generic AP inbox instead of a real person
• Missing a PO number, a W-9, or some other document the buyer's system requires before it'll even process the thing
• Rejected inside a supplier portal like Coupa or Ariba with no clear notice sent back to whoever billed it
• Sitting in a pricing or timesheet dispute that nobody's actively resolving

Disputes that just sit there, open and untouched, are one of the most common reasons a payment never arrives on schedule. That means there needs to be a clear internal lane for logging a dispute, assigning it to a specific person, and tracking how long it takes to close. For Net-60 accounts especially, one small billing discrepancy can freeze the whole invoice for an extended period, and because the term is already long, that delay compounds instead of just adding on top.

The cadence itself needs to know how to get out of the way when this happens. A touchpoint that surfaces a dispute should pause the standard reminders and route straight to whoever handles resolution. Sending an automated "you're overdue" email to a customer who's disputing the invoice doesn't speed up payment. It just makes them annoyed at getting nagged about something they're already actively working through. So exception handling has to keep those edge cases visible to a human, not buried inside the automated flow, disputes and partial payments and portal rejections all need their own lane, separate from the default sequence.

Portal work is its own skill, honestly, distinct from writing a good reminder email. Knowing how to submit correctly, confirm it went through, and fix a rejection on a platform like Coupa takes someone who's actually spent time in that specific system. Email alone has a ceiling. Getting past it takes a person who can navigate the parts a cadence can't automate its way through.

How to configure automation to run term-specific cadences without manual oversight for every invoice

The AR automation market reached a substantial valuation in 2025, with North America making up 44.9% of that. Finance teams are clearly putting money into this, and the tools exist. The real question isn't whether to automate. It's whether the automation is set up to tell Net-30 from Net-60 in the first place.

That comes down to one configuration decision: automation has to read payment terms at the invoice level. Get that wrong and every Net-60 invoice runs on a Net-30 clock, or vice versa, and the whole cadence is quietly broken from the start.

None of that works without clean data underneath it, and this is the part most teams skip. Customer records need the right billing contact, the right email, and the correct payment term attached. Contract data needs to capture the billing trigger, the amount, and whether the deal is Net-30 or Net-60. Automating a process that's built on messy records doesn't fix the mess. It just runs the same mess faster, and now it's happening at scale before anyone notices.

Dunning sequences should shift based on the risk and payment history tied to each account, so a customer who always pays on time doesn't get the same aggressive pace as one with a habit of stretching 30-day terms to 45. And exception workflows need to be part of the build from the start, not patched in later:

• A disputed invoice pauses reminders and routes to whoever owns dispute resolution
• A partial payment triggers a specific follow-up on the remaining balance instead of a generic "you're overdue" email
• A portal rejection routes to a person who can fix it and resubmit

The biggest gains show up when automation covers the full invoice-to-cash cycle, cash application, payment matching, reconciliation, all of it, rather than just handling reminder emails and calling it done. And payment prediction technology can flag which invoices are likely to go late before the due date even arrives, which turns the pre-due reminder from a routine touch into something closer to a warning shot, sent to exactly the accounts that need it most.