Past-Due Notices Without FDCPA Mistakes

A good customer is 18 days late on a $4,800 invoice. The project manager says the work was excellent. Accounts payable says it never received the signed completion ticket. Your bookkeeping system has already added a late fee, and an automated sequence is about to send this message:

FINAL LEGAL NOTICE. Pay immediately to avoid prosecution, credit reporting, liens, attorney fees, and seizure of assets.

The company has not reviewed the contract, has no credit-reporting relationship, has not consulted a lawyer, cannot prosecute a civil invoice, and still has the missing completion ticket in a technician’s truck.

That message is not firm. It is inaccurate, operationally careless, and likely to turn a solvable invoice exception into a legal and customer-retention problem.

A useful past-due notice does four things:

1. confirms that the right person owes the right amount under the right agreement;
2. explains the account clearly enough for the recipient to act or dispute it;
3. asks for a specific response without harassment, humiliation, or false leverage; and
4. escalates only to a remedy the sender is legally permitted and genuinely prepared to take.

The drafting cannot start with tone alone. It starts with classification. A local contractor collecting its own home-repair invoice, a collection agency collecting a consumer account, a law firm collecting for a client, and a supplier collecting trade credit from a corporation do not occupy the same legal lane.

This guide is a U.S. operational framework, not a substitute for advice on a particular account. Federal and state debt-collection law, collection-agency licensing, consumer-protection law, interest and fee limits, lien rights, credit reporting, bankruptcy, probate, service contracts, and lawsuit deadlines vary. Have the sequence and templates reviewed for the states, account types, channels, and collection roles in which they will be used.

Use Documentorium only after the account has been classified and reconciled. Start from the accepted contract agreement, issued invoice, approved changes, completion evidence, credits, and payments. Put the current principal, fees that were validly agreed, credits, receipts, disputed lines, and undisputed balance in the customer statement of account. Then issue the past-due notice with the exact account reference, amount, due date, response options, dispute contact, and one real next step. The statement-of-account guide shows how that sequence keeps tone firm without asking the letter to do the ledger's job.

Classify the account before sending anything

The most dangerous template is one designed for a different legal relationship.

Answer five questions for every account.

Is the obligation consumer or commercial?

The federal Fair Debt Collection Practices Act defines a covered debt as an obligation arising from a transaction primarily for personal, family, or household purposes. The CFPB explains that the FDCPA does not cover business debts.

Examples that may be consumer in purpose:

• roof repair on an owner-occupied home;
• residential plumbing or HVAC work;
• personal landscaping service;
• household moving service;
• work for an individual’s family event.

Examples that may be commercial in purpose:

• HVAC service for a restaurant;
• repairs at a corporation’s warehouse;
• landscaping for an office park;
• materials bought for resale or business operations;
• work ordered by a general contractor for a project.

Do not classify from the address, name, or payment card alone. A home address can be a business site; a sole proprietor can buy services for business use; a company can pay for a consumer’s household project. Record the transaction’s primary purpose and supporting contract.

Are you the original creditor or collecting for someone else?

Under the federal definition, an employee of a creditor collecting the creditor’s own debt in the creditor’s own name is generally excluded from debt collector. A business can move into FDCPA territory, however, if its principal purpose is debt collection, it regularly collects debts owed to another, or a creditor uses another name suggesting a third party is collecting.

Classify the sender:

Do not make a small company sound like an outside agency. Northwest Recovery Division is not harmless branding when it is only the same contractor’s bookkeeper at the next desk.

Does state law reach more broadly?

The federal rule is not the outer boundary. The CFPB notes that state laws may cover original creditors even when the FDCPA generally does not.

California provides a useful current example of why a national template needs a state matrix. Its Civil Code defines a debt collector to include a person who regularly collects covered debts on behalf of itself or others. As of September 20, 2026, the statute also defines a limited category of covered commercial debt or credit involving a natural-person guarantor. The definition is limited to qualifying credit transactions owed to a lender, commercial financing provider, or debt buyer and uses a $500,000 ceiling in the circumstances the statute specifies; an ordinary supplier invoice is not automatically covered by that definition. The commercial provisions apply to covered commercial credit or debt entered into, renewed, sold, or assigned on or after July 1, 2025. See California Civil Code § 1788.1 for the applicability date and § 1788.2 for the scope. That does not mean every California business invoice is covered. It means the sender must read the actual definitions and exceptions instead of repeating the FDCPA does not apply to us as a universal answer.

Check:

• the debtor’s state;
• the property or transaction state;
• the collector’s state;
• original-creditor coverage;
• consumer and small-business coverage;
• collection-agency, debt-buyer, or attorney licensing;
• required disclosures and language access;
• call, text, email, voicemail, and workplace rules;
• interest, late fee, collection cost, and attorney-fee rules;
• limitation periods and time-barred-debt disclosures;
• litigation venue and pre-suit notice requirements.

Has the account entered bankruptcy, probate, litigation, or representation?

An ordinary reminder sequence should stop when the legal posture changes.

Create immediate holds for:

• a bankruptcy petition or notice;
• a deceased customer or estate notification;
• attorney representation concerning the account;
• a lawsuit, arbitration, or formal pre-suit process;
• identity theft or wrong-person claim;
• disputed authorization or fraud;
• military or other protected status relevant to the contemplated remedy;
• a regulator, attorney general, or consumer complaint;
• a cease-communication or channel restriction applicable to the sender;
• a settlement, payment plan, or insurance process already controlling the balance.

The Bankruptcy Code’s automatic stay generally stops acts to collect a prepetition claim. U.S. Courts explains that, while the stay is in effect, collection efforts such as payment-demand calls normally stop. Exceptions and relief from stay exist, so route the account to bankruptcy counsel or the designated specialist rather than trying to solve it with a new urgent email.

Is the sender still in routine accounts receivable or now doing regulated collection?

An invoice, statement, courtesy reminder, default notice, demand letter, validation notice, lien notice, and litigation notice are different documents.

Define the handoff point:

Internal accounts receivable may send approved first-party reminders through Stage 3. Any threatened legal remedy, collection-agency referral, credit reporting, lien action, repossession, service termination, personal-guaranty demand, probate claim, or bankruptcy communication requires the designated review and a channel-specific approved form.

Do not let an automation platform decide that a serious legal event occurred merely because an invoice reached a certain age.

Freeze the ledger before drafting the notice

Tone cannot cure a wrong balance.

Assemble an account packet:

• signed contract, proposal, purchase order, or other authorization;
• change orders and approved extras;
• invoice and itemization;
• delivery, service, inspection, or completion evidence;
• customer acceptance, punch-list, and warranty records;
• credits, discounts, retainage, deposits, refunds, and back charges;
• payment history and unapplied cash;
• tax treatment;
• agreed due date and payment condition;
• authorized interest, late fees, collection costs, and attorney-fee terms;
• prior notices and delivery evidence;
• customer communications, disputes, promises, and preferred channel;
• legal holds, bankruptcy searches when appropriate, or counsel instructions;
• limitation, lien, bond, or claim deadlines handled outside the reminder template.

Then reconcile the balance:

The notice should not demand the gross invoice if the customer paid part, earned a credit, or validly holds retainage.

Never invent collection add-ons

Regulation F prohibits an FDCPA debt collector from collecting interest, fees, charges, or expenses unless expressly authorized by the agreement creating the debt or permitted by law. Original creditors should apply the same discipline even where that provision does not directly govern them.

Do not add:

• a collection fee because the account became inconvenient;
• attorney fees before they are contractually and legally recoverable;
• a percentage late fee copied from another state or customer type;
• credit-card processing fees not properly disclosed and permitted;
• returned-payment charges without a valid basis;
• both interest and a late fee without reviewing whether the combination is allowed;
• future charges as though they have already accrued.

If an amount is uncertain, do not bury it in a total. State the undisputed current balance and route the disputed component for review.

Distinguish a reminder from a validation notice

An original creditor’s ordinary payment reminder is not automatically the validation notice required of an FDCPA debt collector.

Regulation F requires covered debt collectors to provide specified validation information in the initial communication or, with stated exceptions, within five days. The CFPB provides a model validation notice and detailed requirements. A generic Invoice overdue—pay now email should not be presented as compliance with that rule.

If the sender is an FDCPA debt collector:

• use a reviewed Regulation F workflow;
• identify the itemization date and required account information correctly;
• deliver validation information in the required manner;
• preserve the consumer’s validation-period rights;
• avoid collection language that overshadows those rights;
• stop collection of a debt or disputed portion after a timely written validation-period dispute until the required verification response;
• include required collector disclosures;
• retain evidence of the notice and communications;
• layer in state-specific notices without breaking the federal form or presentation.

This is a compliance implementation, not a place for improvisation by a project manager.

If the sender is the original creditor, it can still use a clear account summary and dispute path. Do not add This is an attempt to collect a debt simply because a search result said every past-due letter needs it. Conversely, do not omit a required disclosure when the sender actually is a covered collector. Classification controls the form.

Write a notice the recipient can reconcile

A recipient should be able to answer six questions without opening five attachments.

Who is writing?

Use the real legal or operating name under which the account was created. Include a monitored reply address and telephone number. Do not imitate a court, government office, law firm, credit bureau, or collection agency.

Who is the account holder?

Use enough information to identify the customer without exposing sensitive data. For a business account, name the entity, site, purchase order, and authorized contact. For a consumer, avoid placing full account, Social Security, payment-card, medical, or other sensitive information where a third party may see it.

What transaction is this?

Identify:

• invoice number;
• contract or project reference;
• service/delivery description;
• service location where appropriate;
• original invoice date and agreed due date;
• original amount;
• credits and payments;
• separately authorized fees;
• current amount due.

What should the recipient do?

Ask for one of three actions by a clear date:

1. pay through the stated method;
2. send the remittance details if payment was already made; or
3. identify the disputed item and supporting information through the stated channel.

Please handle immediately creates emotion but no workflow.

What happens next?

Name only the actual administrative step:

If we do not receive payment or hear from you by [deadline], the account will move to our credit manager for review of available next steps.

That is safer and more accurate than:

We will sue, lien the property, report you, garnish wages, seize assets, and charge all attorney fees.

Use a specific remedy only after confirming it is lawful, available, not stayed or expired, and genuinely intended.

How can the recipient resolve an error?

Provide a real person or queue that can access the ledger and job documents. A dispute address that nobody monitors is worse than none because it creates false confidence in the process.

Use a relationship-preserving escalation ladder

The age of an invoice is not the only escalation variable. Consider customer history, amount, dispute status, promised payment, procurement process, missing documentation, credit risk, and legal deadlines.

Due-date confirmation

Before the due date or immediately after invoicing, confirm:

• correct bill-to entity and address;
• purchase order and vendor number;
• tax and retainage treatment;
• completion documents;
• portal upload;
• approver;
• scheduled payment run;
• any rejected invoice status.

Many collections problems are invoice-delivery failures.

Courtesy reminder

Use a neutral subject line:

Invoice 1048 — payment status check

Message:

Hello [name],

Our records show $2,710.00 remains due on Invoice 1048 for the completed service at [site]. The agreed due date was [date]. A statement showing the original charge, credit, payment, retainage, and current balance is attached.

If payment has been sent, please reply with the remittance date and reference so we can match it. If anything on the invoice is incorrect or supporting paperwork is missing, tell us the item and we will review it. Otherwise, please arrange payment by [specific date] using [approved method].

Thank you, [real sender and contact]

This is direct without accusing the customer of bad faith.

Documented past-due notice

Once the first reminder produces no result, state the contact history and required response:

We sent the invoice to [approved address/portal] and followed up on [contact references]. We have not received payment, remittance details, or a dispute. The current reconciled amount due is $2,710.00.

Please pay or send a written account-specific response by [date]. If an internal approval, purchase order, completion document, or correction is holding payment, identify it and the responsible contact so we can address it.

Avoid you ignored us when delivery evidence is incomplete.

Account-review notice

This can explain operational consequences already authorized by the contract:

If the account is not resolved by [date], we will review it for credit hold and suspension of future non-emergency work under the agreement. Existing safety, warranty, shutdown, statutory, and other nonwaivable obligations are not changed by this notice.

Do not suspend work in a way that creates a safety hazard, violates a contract, abandons a regulated project, impairs a statutory duty, or breaches notice/cure requirements. Have the actual remedy reviewed.

Formal demand or referral review

At this point, pause automation. Review:

• liability and documentation;
• correct debtor and guarantor;
• disputes and defenses;
• limitation period;
• lien, bond, retainage, and notice deadlines;
• contract dispute process and venue;
• bankruptcy, probate, and representation;
• collection-agency or attorney licensing;
• likely recovery and relationship cost;
• settlement authority;
• exact remedy the business will use.

A formal demand should come from the real sender with authority. Do not put a lawyer’s name, law-firm appearance, case number, court seal, or legal department header on a document unless genuine and authorized.

External collection or legal process

The handoff packet should contain the complete, reconciled evidence—not just a spreadsheet total. Record who owns future communications, how direct customer contact will stop or be coordinated, and how payments or disputes received after referral will be transmitted.

Once an agency or lawyer is engaged, competing emails from the salesperson, owner, bookkeeper, and collector create inconsistent balances and compliance risk.

Never threaten a remedy you cannot or will not use

Regulation F prohibits an FDCPA debt collector from threatening action that cannot legally be taken or is not intended. It also prohibits false statements about the character, amount, or legal status of a debt and false implications about government, attorney, court, or credit-bureau involvement.

That gives every accounts-receivable team a sound drafting rule, regardless of exact federal coverage:

A stated consequence must have a legal basis, factual prerequisites, present availability, internal authorization, and genuine intent.

Arrest, prosecution, and police

Ordinary failure to pay a civil invoice is not transformed into a crime by bold type. Do not threaten arrest, jail, police, district attorney, immigration action, or a fraud accusation to force payment. A suspected crime should go through counsel and the appropriate factual process, not a collection-letter threat.

Lawsuit

Do not say we will sue Friday unless counsel has confirmed the claim, deadline, venue, prerequisites, and actual filing decision. Safer administrative wording is the account may be referred to counsel for review only if referral is a real option and will occur under the stated conditions.

For a time-barred consumer debt, Regulation F prohibits an FDCPA debt collector from bringing or threatening legal action. State law can also regulate time-barred-debt communications and whether a payment or acknowledgment affects rights. Route old accounts to counsel before requesting a good-faith token payment.

Lien or bond claim

Mechanic’s lien and payment-bond rights are technical, state-specific, and deadline-driven. Do not say we placed a lien when no lien exists, or we will lien your home when notice, licensing, timing, contract, owner, property, or project requirements are not satisfied. A preliminary notice is not necessarily a recorded lien.

Calendar preservation steps independently of the friendly reminder sequence. A salesperson’s payment promise may not extend a statutory deadline.

Wage garnishment or asset seizure

These commonly require a judgment and further lawful process. Regulation F bars a covered collector from implying that nonpayment will cause seizure, garnishment, attachment, or sale unless the action is lawful and intended. Do not describe a possible post-judgment remedy as an immediate event.

Credit reporting

Do not write this will destroy your credit or claim an account is already reported when it is not. Furnishing consumer information creates duties under the Fair Credit Reporting Act, including accuracy and dispute handling. Regulation F also requires an FDCPA collector to take specified steps before furnishing information about a debt.

If the business does not furnish to consumer reporting agencies, remove the threat entirely. If it does, use a reviewed furnishing program and describe only what is true and lawfully permitted. For an FDCPA debt collector, Regulation F generally requires the collector to communicate or attempt to communicate with the consumer about the debt before furnishing it to a consumer reporting agency; letters and electronic messages also involve a reasonable period for an undeliverability notice, subject to the rule's exceptions and timing requirements.

Fees and interest

Do not threaten an arbitrary daily charge. State the contract and legal basis, calculation method, through-date, and amount actually included. Keep future accrual separate:

Contractual simple interest, if applicable after review, is calculated at ___ on the unpaid eligible principal through [calculation date]. It is not compounded. Contact us for an updated payoff amount.

Only use that language when it is accurate and allowed.

Collection agency or attorney referral

Referral is not shame. State it plainly, and only when a real licensed/authorized route exists:

If unresolved, the account may be referred to our approved collection provider or counsel for review. Any further amounts will be sought only if authorized by the agreement and law.

Do not claim that referral automatically adds a percentage fee.

Protect privacy in every channel

Debt information should reach an authorized person, not the loudest available audience.

For an FDCPA debt collector, Regulation F generally prohibits communicating about a debt with third parties outside enumerated exceptions. The rule also addresses electronic communications, employer-provided email, public social media, opt-outs, limited-content voicemail, and inconvenient times and places.

An original creditor should still build privacy safeguards around consumer and business accounts.

Postal mail

• verify the address;
• avoid an envelope or postcard that publicly announces DEBT COLLECTION;
• limit sensitive account information visible through windows;
• record returned mail;
• do not keep sending to an address known to expose the matter to a third party.

Regulation F prohibits FDCPA collectors from using postcards and restricts collection-revealing envelope markings.

Email

• use an address the customer provided or approved for account communications;
• distinguish a shared accounts-payable mailbox from an individual consumer’s employer email;
• verify attachments and recipient autocomplete;
• avoid full payment-card, bank, tax-ID, or identity data;
• provide required electronic opt-out mechanisms when Regulation F applies;
• honor channel restrictions;
• track bounces and wrong-recipient reports.

For FDCPA collectors, the CFPB’s rule provides specific procedures aimed at avoiding third-party disclosure. Copying those procedures incompletely is not a substitute for implementing them.

Text messages

Text is fast and easy to expose on a shared screen or recycled number. Confirm authority, consent, applicable telephone law, time zone, opt-out handling, and privacy procedure. Do not migrate to a new number after the recipient says to stop texts.

Telephone and voicemail

Regulation F’s call-frequency framework creates rebuttable presumptions for FDCPA collectors: generally, no more than seven calls in seven consecutive days about a particular debt and no call within seven days after a conversation about that debt, subject to detailed exclusions and rebuttal factors. This is not a quota or permission to make seven concentrated calls. The rule’s general harassment prohibition and cumulative conduct across channels still apply.

In the absence of contrary information, Regulation F treats calls before 8:00 a.m. or after 9:00 p.m. at the consumer’s location as inconvenient. A consumer can identify other inconvenient times and places.

Do not leave account details on a voicemail that another person may hear. Regulation F defines a narrow limited-content message for covered collectors; it has required and optional content. A regular business should not label any short voicemail Reg F compliant without confirming that it meets the rule and that other law permits the call.

Social media and public pressure

Never post an unpaid customer list, tag a customer publicly, comment on the customer’s business page, contact family or coworkers to embarrass the customer, or reveal the balance in a neighborhood group. Regulation F bars public or contact-visible social-media debt communications by covered collectors and prohibits publishing deadbeat lists. Reputation pressure is also corrosive even outside that exact coverage.

Workplace and organizational contacts

For a consumer account, contacting an employer can disclose the debt and trigger specific restrictions. For a commercial account, contacting the correct accounts-payable employee is ordinary administration, but broadcasting a dispute to unrelated staff, customers, or vendors is unnecessary.

Build a contact hierarchy:

1. named billing contact;
2. named project/contact owner;
3. accounts payable or contract administrator;
4. authorized executive or credit contact;
5. external counsel or collector after approved referral.

Do not send PAY NOW to every address on the customer’s website.

Treat disputes as a branch, not an obstacle

When the customer says the work, amount, card charge, or authorization is wrong, pause the ordinary sequence and assemble the relevant job record. The chargeback defense guide shows how scope, approval, performance, delivery, invoice, and communication evidence fit together even when no card dispute has been filed. Issue a receipt for every payment and use the completion sign-off only for what it actually proves. If management is considering litigation, use the forum comparison guide with counsel instead of threatening every forum in a form letter.

A notice should invite enough information to classify the response.

Common dispute categories:

• wrong customer or entity;
• duplicate invoice;
• payment already made or misapplied;
• unauthorized work or change;
• scope, quality, damage, or warranty issue;
• missing purchase order, timesheet, ticket, inspection, waiver, or tax form;
• calculation, tax, fee, retainage, or credit error;
• insurer, landlord, tenant, owner, general contractor, or guarantor responsibility;
• identity theft or fraud;
• settlement or payment-plan disagreement;
• bankruptcy discharge or stay;
• limitation or legal-defense claim.

Log:

• received date and channel;
• exact disputed amount and reason;
• attachments;
• owner and response target;
• collection hold status;
• ledger correction;
• written resolution;
• revised due date or next step.

For FDCPA debt collectors, a timely written dispute during the validation period triggers the Regulation F cease-and-verify process for the disputed debt or portion. The rule also says collection communications during the validation period must not overshadow the consumer’s dispute rights. Do not write Pay in 48 hours or be sued above a notice explaining that the consumer has a validation period.

For an original creditor not subject to that exact federal process, pausing disputed collection while checking the file is still sound control. Continue seeking any undisputed portion only when the contract, law, facts, and communication make that distinction clear.

Offer payment arrangements without changing the deal by accident

A payment plan can preserve recovery and the relationship, but verbal promises create new uncertainty.

Document:

• acknowledged or disputed balance;
• payment dates and amounts;
• payment method and authorization boundaries;
• allocation to principal, interest, fees, and invoices;
• whether future charges accrue;
• treatment of missed or partial payments;
• grace, cure, and default process;
• effect on service or credit hold;
• effect on lien, lawsuit, limitation, guaranty, and other rights as reviewed;
• settlement discount and conditions;
• release or satisfaction after final cleared payment;
• authorized signers;
• governing required disclosures.

Do not say this will not affect our rights and assume that solves waiver, limitation, lien, or revival issues. Have the arrangement reviewed when those rights matter.

Avoid autopay surprises. State the amount and timing, obtain valid authorization, provide receipts, and never debit earlier or for more than authorized. Regulation F contains specific rules for postdated payment instruments used by covered collectors.

Decide what “final notice” actually means

Final should have a defined consequence. If five more final notices will follow, the word is false.

Use it only when:

• the ledger and debtor are verified;
• the account is not on hold;
• prior notice was delivered or delivery issues were addressed;
• the response date is reasonable and legally valid;
• the next step is approved;
• the sender will actually take that step if the stated condition occurs;
• the notice does not eliminate statutory or contract rights;
• the legal posture has been checked.

A precise alternative is often better:

Account review notice before credit hold

or:

Notice before referral to counsel for review

The title tells the recipient what administrative event is next without pretending a lawsuit already exists.

Use clear controls before any automated notice

Automation should assemble verified facts, not manufacture pressure.

Data gates before enrollment

• customer and debtor identity verified;
• consumer/commercial purpose classified;
• original creditor/collector role classified;
• state matrix applied;
• current balance reconciled;
• contract and delivery/completion evidence attached;
• authorized fees reviewed;
• no active dispute;
• no bankruptcy, deceased, representation, litigation, identity-theft, or complaint hold;
• approved address/channel;
• local time and communication preference known where needed.

Suppression events

Stop the sequence immediately on:

• payment or remittance evidence;
• returned mail or bounced email;
• wrong person or wrong number;
• dispute;
• complaint;
• cease or channel opt-out request;
• attorney notice;
• bankruptcy notice;
• death or estate notice;
• settlement discussion;
• manual legal or management hold;
• referral to an external collector or counsel.

Content controls

Lock:

• sender identity;
• approved subject lines;
• balance source;
• invoice references;
• payment links;
• jurisdictional disclosures;
• opt-out language;
• dispute route;
• escalation sentence;
• prohibited words and remedies;
• attachment selection;
• version and approval owner.

Do not let a general-purpose language model generate unsupervised legal threats from a notes field.

Channel and frequency controls

Count contacts across the whole organization and its vendors. A customer who receives three accounting emails, two salesperson texts, four automated calls, and a project manager’s social-media message did not receive one reminder from each team; they received a pressure campaign.

Regulation F’s official commentary says cumulative conduct across media can amount to harassment even when one channel viewed alone does not cross a specific threshold. Centralize the log.

Preserve an auditable communication record

For each account, retain under the applicable policy:

• the ledger snapshot used for each notice;
• contract and fee authority;
• notice version and jurisdictional rider;
• recipient address and source;
• send and delivery/bounce/return evidence;
• call attempts, conversations, voicemails, texts, and opt-outs;
• disputes, supporting documents, investigation, and resolution;
• payment promises and plans;
• legal, bankruptcy, probate, representation, and complaint holds;
• approval for each threatened or taken remedy;
• referral packet and handoff time;
• payments received after referral;
• settlement, release, lien satisfaction, or account closure.

Regulation F requires FDCPA debt collectors to retain evidence of compliance or noncompliance from the start of collection activity until three years after the last collection activity, with a three-year rule for recorded calls measured from each call. Other laws, limitation periods, tax rules, litigation holds, and contracts may require a different period. Do not blindly apply the Reg F period to every record or destroy records subject to a hold.

Language that works—and language to remove

Firm language is factual language.

Sample original-creditor notices

These examples are for a business collecting its own account in its real name after classifying the account and reviewing applicable law. They are not Regulation F validation notices and should not replace required state or collector disclosures.

Courtesy status check

Subject: Invoice [number] — payment status check

Hello [name],

Our records show a balance of $[amount] remains due on Invoice [number] for [brief service/project]. The agreed due date was [date]. The attached statement shows the original amount, payments, credits, and current balance.

If payment has already been sent, please reply with the remittance date and reference. If the invoice is missing a purchase order, completion ticket, waiver, tax form, or other support—or if you dispute any item—tell us what is needed at [monitored contact]. Otherwise, please arrange payment by [date] through [approved method].

Thank you, [real company and person]

Second notice

Subject: Response requested — Invoice [number]

Hello [name],

We are following up on the $[amount] balance for Invoice [number], originally due [date]. We sent our prior status request to [approved channel] on [contact reference] and have not recorded payment, remittance information, or a dispute.

Please do one of the following by [date]:

• pay through [approved method];
• send payment reference details; or
• identify the specific amount or document in question so we can review it.

Our account contact is [name/contact]. This message is from [company], the provider named on the invoice.

Notice before internal credit review

Subject: Account review scheduled — response requested by [date]

The current reconciled balance on Invoice [number] is $[amount]. We have not recorded payment or an unresolved dispute. Unless we receive payment or an account-specific response by [date], we will send the account to our credit manager to review a hold on future non-emergency work and other remedies available under the agreement and applicable law.

This notice does not state that a lawsuit, lien, credit report, or collection referral has occurred. If you believe the amount or responsible party is incorrect, contact [monitored contact] with the relevant invoice item and supporting information.

Payment-plan follow-up

Subject: Confirming proposed payment schedule for Invoice [number]

We discussed the current balance of $[amount]. The proposed schedule is [amount/date schedule]. No plan is effective until the authorized parties sign the attached agreement. Until then, the existing contract and account status remain unchanged, subject to applicable law.

Please review the balance, allocation, fees, missed-payment terms, service status, and payment method. Send corrections to [contact] before signing.

When to stop writing and get help

Escalate instead of sending another template when:

• you cannot prove the debtor, contract, delivery, or amount;
• the customer raises a credible performance or authorization dispute;
• a personal guaranty may be involved;
• the limitation, lien, bond, or claim deadline is close;
• the customer is in bankruptcy or may have received a discharge;
• the customer is deceased;
• an attorney represents the customer;
• identity theft, fraud, forgery, or wrong-person issues appear;
• you plan to furnish consumer credit information;
• you plan to sue, repossess, garnish, seize, lien, or terminate essential service;
• the debt is old enough to be time-barred or near that line;
• the collector or agency may need a license;
• multiple states are involved;
• the account includes medical, housing, utility, education, military, or other specially regulated debt;
• the customer threatens self-harm, violence, or another safety emergency;
• the communication has become emotional or retaliatory.

A ten-minute pause before a threat is less expensive than explaining the threat later.

Past-due notice checklist

Classification

• [ ] Transaction purpose is documented as consumer or commercial
• [ ] Sender is classified as original creditor, debt collector, debt buyer, attorney, or other role
• [ ] Applicable states and broader state-law definitions are checked
• [ ] Licensing and required disclosures are confirmed
• [ ] Routine AR, formal demand, validation, lien, lawsuit, and referral documents are separated

Account accuracy

• [ ] Correct legal debtor and any guarantor are verified
• [ ] Contract and authorization are in file
• [ ] Delivery, service, completion, and change evidence are available
• [ ] Payments, credits, retainage, tax, and unapplied cash are reconciled
• [ ] Every interest, fee, and cost has contract and legal authority
• [ ] Current amount is tied to a dated ledger snapshot

Holds and disputes

• [ ] No bankruptcy, discharge, probate, representation, litigation, identity-theft, or complaint hold applies
• [ ] Active disputes are paused and assigned
• [ ] Payment plans and settlements are reflected
• [ ] Limitation and lien/bond deadlines are separately calendared
• [ ] Wrong-person, wrong-address, and wrong-number reports suppress automation

Message content

• [ ] Real sender name and monitored contact are clear
• [ ] Invoice, project, due date, and current amount are identifiable
• [ ] Payment, remittance, and dispute paths are offered
• [ ] Response date is specific and reasonable
• [ ] No arrest, government, court, attorney, credit, lien, seizure, or fee claim is false
• [ ] Next step is lawful, authorized, and genuinely intended
• [ ] Required federal and state disclosures are included for the actual role
• [ ] Validation rights are not overshadowed when Regulation F applies

Channel and privacy

• [ ] Recipient and address are approved for account communications
• [ ] Envelope, email, text, voicemail, and attachment do not expose unnecessary debt information
• [ ] Local time, inconvenient-time/place, workplace, and channel rules are observed
• [ ] Electronic opt-out works where required
• [ ] Cease and medium-specific requests are honored
• [ ] Organization-wide contact frequency is logged
• [ ] No public or third-party pressure is used

Escalation and records

• [ ] Every notice version and delivery result is retained
• [ ] Call, text, email, dispute, and payment records are centralized
• [ ] Formal remedies receive required legal/management approval
• [ ] External referral transfers the full evidence packet
• [ ] Direct contact is coordinated after referral
• [ ] Closure, settlement, release, satisfaction, and write-off are documented

Sources

Sources were reviewed September 20, 2026. Federal and state debt-collection, privacy, credit-reporting, bankruptcy, licensing, and contract requirements can change; verify the actual account, sender role, jurisdiction, and remedy before sending a notice.

• Federal Trade Commission — Fair Debt Collection Practices Act Text, accessed September 20, 2026.
• Consumer Financial Protection Bureau — What Laws Limit What Debt Collectors Can Say or Do?, accessed September 20, 2026.
• U.S. House Office of the Law Revision Counsel — 15 U.S.C. § 1692a, Definitions, accessed September 20, 2026.
• Consumer Financial Protection Bureau — Regulation F, 12 CFR Part 1006, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.6, Communications, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.14, Harassing, Oppressive, or Abusive Conduct, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.18, False, Deceptive, or Misleading Representations, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.22, Unfair or Unconscionable Means, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.26, Time-Barred Debts, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.30, Other Prohibited Practices, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.34, Validation Notice, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.38, Disputes and Original-Creditor Requests, accessed September 20, 2026.
• Consumer Financial Protection Bureau — § 1006.100, Record Retention, accessed September 20, 2026.
• Consumer Financial Protection Bureau — Debt Collection Rule FAQs, accessed September 20, 2026.
• Federal Trade Commission — Consumer Reports: What Information Furnishers Need to Know, accessed September 20, 2026.
• U.S. House Office of the Law Revision Counsel — 11 U.S.C. § 362, Automatic Stay, accessed September 20, 2026.
• Administrative Office of the U.S. Courts — Bankruptcy Cases and the Automatic Stay, accessed September 20, 2026.
• California Legislative Information — Civil Code § 1788.1, for the applicability date for covered commercial credit and debt, accessed September 20, 2026.
• California Legislative Information — Civil Code § 1788.2, for the covered-debt definitions and scope, accessed September 20, 2026.
• California Legislative Information — Civil Code §§ 1788.10–1788.185, accessed September 20, 2026.

---

Disclaimer

This article is general U.S. information, not legal, collections, credit-reporting, bankruptcy, tax, accounting, or consumer-protection advice. Verify the account type, sender role, state coverage, contract, required disclosures, communication channels, remedies, and deadlines with qualified counsel and applicable authorities before sending a notice.