Past-Due Notices That Don't Burn Bridges (Or Trigger FDCPA)
Send accurate past-due reminders after checking the balance, sender role, applicable collection rules, disputes, privacy, and real escalation options.
Imagine a customer 18 days late on an invoice because accounts payable lacks the completion ticket. An automatic reminder threatens a lawsuit, lien, and credit report. The shop has reviewed none of those remedies—and still has the ticket on a technician's phone.
A useful past-due notice starts with a verified account, then gives the recipient a specific way to pay, identify a payment, or raise an error. Stronger threats cannot fix missing paperwork.
Check who owes what before writing
Reconcile the accepted contract, approved work, invoice, payments, credits, retainage, and any disputed items. Verify the correct customer entity and agreed due date.
Use the statement of account to explain the balance. The statement-before-collections guide keeps that arithmetic separate from the reminder.
Add only charges supported by the agreement and applicable law. For covered debt collectors, Regulation F 1006.22 restricts incidental amounts not authorized by the agreement or permitted by law. The late-fee guide explains why an overdue date does not itself authorize a new percentage fee.
Classify the sender and transaction
The Regulation F definitions distinguish covered consumer debt, creditors, and debt collectors. Federal FDCPA debt generally arises from personal, family, or household transactions, rather than business debts.
A contractor's employee collecting the contractor's own account in its actual name is generally outside the federal debt-collector definition. Exceptions and different business roles matter, including a creditor using another name that suggests an outside collector. Do not invent a “recovery agency” identity for your bookkeeper.
Federal coverage is not the whole inquiry. The CFPB explains that state laws may reach original creditors. Check relevant states, transaction purpose, licensing, required disclosures, and communication rules before using one national sequence.
An original-creditor reminder is not automatically a collector validation notice. Covered collectors must follow 1006.34 for validation information, timing, and delivery. Use a reviewed process for that role rather than adding a collector sentence to an ordinary invoice email.
Write one factual request
Use the past-due notice to identify the real sender, invoice, original due date, current amount, response date, payment route, and monitored dispute contact.
Illustrative first-party wording, subject to applicable requirements:
Our records show $2,710 remains due on Invoice 1048, originally due [date]. The attached statement includes payments and credits. Please pay by [date], send remittance details if payment was made, or tell us which item or supporting document needs review. Contact [named account contact] so we can resolve any discrepancy.
Before sending, confirm the contact can access the ledger and job evidence. Supply missing completion or purchase-order documents promptly. A completion signoff supports only what it actually records; it does not resolve every performance dispute.
Branch on disputes and legal holds
When a customer disputes authorization, performance, payment allocation, or fees, stop the affected automatic sequence and assign a person to investigate. Preserve the statement used, original communication, evidence, corrections, and response.
For covered collectors, a timely written validation-period dispute triggers the 1006.38 cease-and-verify requirements. Do not let a payment deadline overshadow statutory rights. Ordinary first-party dispute review is also sound practice, but it is not the same legal process.
On bankruptcy notice, stop routine demands and route the account for qualified review. U.S. Courts explains the automatic stay, which restricts collection while effective. Exceptions, discharge, relief orders, and the timing of the debt need account-specific assessment.
Representation, estate notices, wrong-person reports, settlement arrangements, and channel restrictions also require review before another standard reminder.
Escalate to a real next step
For covered collectors, 1006.18 prohibits false or misleading representations and threats of action that cannot lawfully be taken or is not intended. Apply the same factual discipline to your own reminders.
Do not imply that a lien, lawsuit, attorney referral, credit report, or seizure already exists when it does not. Confirm prerequisites, deadlines, authority, and genuine intent before describing a specific remedy. Keep lien and bond calendars separate from the reminder sequence; a payment conversation does not automatically extend them.
If suspension is contemplated, follow the applicable notice and cure procedure. Invoice age alone does not authorize pulling the crew off the job.
Protect the message as well as the balance. 1006.6 governs covered collection communications, including third-party and channel concerns. Verify recipients, avoid public pressure or unnecessary sensitive details, and honor applicable restrictions. Record the notice, delivery result, reply, and next owner in one account file. Issue a receipt when payment is received and update the balance before any follow-up.
Common questions
Does the FDCPA govern every overdue business invoice?
No. Federal coverage depends on the transaction and sender. State and other applicable laws still need review.
Should every reminder contain collector disclosures?
No. Use disclosures required for the actual role and jurisdiction. A generic reminder does not replace a covered collector's validation process.
Can I add a collection fee automatically?
No. Verify the contractual and legal basis before including any added fee or interest.
Sources reviewed October 18, 2026.