Overdue Invoices: The Complete Guide

What counts as an overdue invoice

An invoice is overdue the moment the due date passes without payment — there's no grace period unless your contract or payment terms say otherwise. What changes as time passes isn't the invoice's status, it's the tone your follow-up should take. A day-3 nudge and a day-60 final notice are dealing with the same unpaid invoice, but they need to read completely differently.

Most small businesses and freelancers lose money not because clients refuse to pay, but because the follow-up either never happens (awkwardness, or it falls through the cracks) or happens with the wrong tone — too soft to prompt action, or too aggressive too early, which damages a relationship over what's often just an oversight.

The escalation process, step by step

A predictable escalation pattern gets paid faster and keeps the relationship intact, because the client always knows where they stand. Chasa's own tone bands follow this exact structure:

1. 1-7 days overdue — friendly. Assume it's an oversight. Light, casual, no mention of consequences. This is the reminder most invoices only need.
2. 8-30 days overdue — professional. State the amount and due date plainly, and ask for a specific payment date. Courteous, but no longer casual.
3. 30+ days overdue — direct. State the amount and due date, set a clear deadline (commonly 7 business days), and — if your contract allows — mention late fees, pausing further work, or referral to collections as the next step.

You can write these by hand every time, or paste the invoice into Chasa and get a tone-matched draft in seconds — free, no account required for the first few. A few ready-made starting points if you'd rather write your own:

See all 18 free templates →

Legal validity of electronic reminders

A common worry: does an emailed payment reminder or demand notice actually count for anything legally, or does it need to be a signed paper letter? In the US, two laws answer this directly:

• UETA (Uniform Electronic Transactions Act) — a model law adopted, with minor variations, by nearly every US state. It establishes that a record or signature can't be denied legal effect solely because it's in electronic form.
• ESIGN Act — the federal equivalent, filling the gap for interstate and international transactions and for the handful of states with their own frameworks.

Together, they mean an emailed invoice reminder or final notice generally carries the same basic legal standing as its paper equivalent — the medium doesn't change the substance. What still matters, as it would with paper, is being able to show the communication was actually sent (and ideally, that it reached the recipient): a timestamped sent record, delivery confirmation, or a consistent chase history all help here. This is exactly what an audit trail is for — see the audit-ready workflows use case for how that evidence gets kept.

This section is general information about US federal and state law, not legal advice. Electronic-record rules for consumer transactions (as opposed to business-to-business) carry additional disclosure requirements under ESIGN, and international rules vary by country. Talk to a lawyer about your specific situation and jurisdiction.

SOX and accounts receivable

The Sarbanes-Oxley Act (SOX) focuses on internal controls over financial reporting. Any workflow touching invoices, approvals, or reconciliation needs to answer: who approved what, when, and whether the record can be altered after the fact. For accounts receivable specifically, that means an approval step before anything is sent, and a chase history that can't be quietly edited later.

Chasa never auto-sends — every follow-up routes through a human approval step, and the resulting chase history is timestamped and immutable. Full detail on what's covered and example workflows: SOX-aligned workflow automation →.

SOC2, security, and what's actually live

Unlike SOX evidence automation, SOC2 certification itself is not something Chasa currently holds — it's on the roadmap, and this guide won't claim otherwise. What's already true today: encrypted storage, short automatic data retention, and the same approval-logged, immutable chase history that underpins the SOX claims above, since evidence automation for accounts receivable is the same underlying discipline SOC2 will eventually extend to the rest of the stack.

For the complete, current picture of what's live versus planned — encryption, EU hosting, role-based access, subprocessors, and the SOC2/ISO 27001 roadmap — see the Chasa Trust Center, and for the SOC2-specific detail, SOC2 workflow automation →.

Pricing: Chasa vs. the alternatives

Chasa is a flat fee per workspace, not per seat — Free, then $7/mo (Solo) or $17/mo (Pro). Most invoice-chasing competitors charge substantially more at their entry paid tier, often per-seat or tied to revenue:

Figures use published list prices as of this writing (USD where available; converted at approximate rates otherwise) and can change — see the live, interactive comparison for current numbers.

Full side-by-side comparison → · See Chasa's plans →

FAQ

Try it on your own invoice

Free, no account required for the first drafts — paste an invoice and get a tone-matched follow-up in seconds.