A well-built internal collections policy is a concise, enforceable governance document that sets your credit terms, escalation timelines, roles, dispute rules, and legal guardrails so your finance team can recover cash consistently, every time.

Start here: define scope → set credit terms → establish 30/60/90 escalation buckets → assign owners → draft demand letter templates → schedule legal review. That six-step checklist is the backbone of every effective policy. Download the policy template below, fill in your thresholds and owner names, and you have a working draft by end of day.

---

Key Takeaways

A well-built internal collections policy combines clear governance, a tested escalation schedule, and consistent templates so your finance team recovers cash reliably and stays compliant.

---

What is an internal collections policy, and what does it cover?

An internal collections policy is a governance document, not a procedure manual. It answers the authority questions: who can approve a payment plan, what triggers an escalation, when does a write-off require CFO sign-off, and which laws govern your outreach. The step-by-step "how" lives in your procedures; the policy sets the rules those procedures must follow.

When you build an internal collections policy, you need to decide upfront which accounts and teams it governs. Typically, the policy covers:

• Accounts receivable (AR): all commercial invoices and recurring billing cycles
• Credit approval: the criteria and authority levels for extending credit at the point of sale
• Customer success and sales: exception requests, payment plan negotiations, and account holds
• Legal: escalation to litigation, credit reporting, and third-party agency referrals
• Finance leadership: write-off authority, reporting, and policy sign-off

The receivables in scope usually include B2B commercial invoices, installment plans, contractual disputes, and high-risk accounts. Small-balance recurring invoices under a defined low balance threshold may follow a simplified track. Consumer administrative debts, government receivables, and accounts already referred to outside counsel are typically carved out and governed separately.

Common policy boundaries worth defining early:

• Billing cadence (net 30, net 60, or custom terms by customer segment)
• Minimum balance thresholds that trigger formal collection action
• Delegated authorities by role (who can approve a discount, a payment plan, or a write-off)
• Which customer segments receive which escalation track

Practitioners consistently find that collections success depends as much on credit screening at the point of sale as on post-delinquency follow-up. Your policy should link directly to your credit approval rules so the two documents reinforce each other rather than contradict.

---

What core sections does every internal collections policy need?

Every complete, auditable internal collections policy must include these sections: purpose and scope, roles and responsibilities, credit terms, invoicing standards, escalation schedule, dispute resolution, accepted payment methods, write-off rules, reporting requirements, and review cadence. Miss any one of them and you will have gaps that surface at the worst possible moment, usually during an audit or a disputed account.

The most important structural decision is keeping policy and procedures as separate documents. The policy defines what is required and who has authority. The procedure document publishes the exact steps, scripts, templates, and system rules your collectors follow. Mixing the two creates a document that is too long to govern and too vague to execute. Centralizing both in a searchable knowledge base keeps them linked without merging them.

Section-by-section breakdown

1. Purpose and scope. One paragraph stating why the policy exists, which entities and account types it covers, and what it does not cover. Reference your credit policy here.

2. Roles and responsibilities. Name the policy owner (typically the Controller or CFO), the AR manager who executes daily tasks, and the approval authorities for exceptions, write-offs, and legal referrals.

3. Credit terms and credit approval. Standard payment terms by customer segment, credit limit authority levels, and the criteria for extending or revoking credit. This section links directly to your credit application and approval process.

4. Invoicing standards. Invoice delivery method, timing, required fields (PO number, due date, remittance instructions), and the process for correcting billing errors before they become disputes.

5. Escalation schedule. The 30/60/90-day (or custom) timeline with triggers, owner, channel, and next action at each stage. This is the operational heart of the policy.

6. Dispute resolution. How disputes are logged, who investigates, the SLA for response (generally within 30 days of receiving a debtor communication, per federal debt collection guidance), and how disputed amounts are treated during investigation.

7. Accepted payment methods. Which payment channels are authorized, how payment confirmations are documented, and who reconciles receipts.

8. Write-off rules. Dollar thresholds requiring manager, CFO, or board approval; documentation required before write-off; and whether written-off accounts are eligible for future credit.

9. Reporting requirements. Frequency, format, and audience for aging reports, DSO tracking, and recovery rate summaries.

10. Review cadence. How often the policy is reviewed (annually at minimum), who approves changes, and how version history is maintained.

On thresholds and delegation: a practical rule of thumb is to require manager-level sign-off for payment plans up to a defined dollar amount, CFO approval above that, and board notification for write-offs that exceed a materiality threshold. Whatever levels you choose, document them explicitly so auditors can trace every exception back to an authorized decision.

---

What escalation timeline should your policy follow?

Start contact immediately after an invoice is issued, not after it is overdue. Silence reads as permission to wait, and accounts that age past 90 days recover at a significantly lower rate than those contacted within the first 30. The recommended approach: send a payment reminder before the due date, then escalate through structured 30/60/90-day buckets with a defined owner, channel, and next action at each stage.

Federal debt collection guidance requires that demand letters include the due date, the debtor's right to review, and the consequences of nonpayment, and that responses to debtor communications be handled promptly, generally within 30 days. Build those requirements into your template language from day one.

Demand letter checklist

Every demand letter your policy authorizes should include:

• Account number, invoice number(s), and total amount due
• Original due date and number of days past due
• Clear statement of consequences (credit hold, credit reporting, legal referral)
• Debtor's right to dispute and the process for doing so
• Payment instructions and accepted methods
• Contact name, phone, and email for questions
• Date the letter was sent and the name of the sender (for your activity log)

Sample phone script (Day 31–60 call)

"Hi, this is [Name] from [Company] accounts receivable. I'm calling about invoice [#] for $[Amount], which was due on [Date]. We haven't received payment yet. Can we confirm a payment date today, or would a short-term payment plan work better for your situation?"

Log every call with: date, representative name, contact reached (or voicemail), and outcome or next commitment. That activity log is your audit trail and your evidence if the account moves to litigation.

---

Who owns collections, and how do you separate duties?

Clear ownership prevents accounts from falling through the cracks and prevents fraud. The policy owner, typically the Controller or CFO, is accountable for keeping the policy current and compliant. The AR manager executes daily collections tasks and approves routine payment plans. The CFO or a designated committee approves write-offs and legal referrals above defined thresholds.

The Department of the Interior's Credit and Debt Management Handbook requires documented internal controls, segregation of duties, and timely, well-documented collection actions tailored to debt type and amount. Those same principles apply directly to private-sector AR operations.

Approval authority matrix

Adjust the dollar thresholds to match your organization's materiality levels. The structure matters more than the specific numbers.

Separation of duties checklist

• Billing vs. collections: the person who creates and sends invoices should not be the same person who records payments received.
• Collections vs. reconciliation: the collector who contacts customers should not also reconcile the AR ledger.
• Write-off authority vs. collection execution: the person recommending a write-off should not have unilateral authority to approve it.
• Payment posting vs. bank reconciliation: separate these to prevent misappropriation.

Recordkeeping requirements to include in the policy: retain all demand letters (physical or digital) for a minimum of seven years, log every promise-to-pay with date and amount, document all disputes and their resolution, and keep signed repayment schedules on file. The GSA Accounts Receivable and Debt Collection Policy Manual specifies that late charges and adjustments require a clear audit trail, a standard worth adopting regardless of your organization's size.

---

What US compliance requirements affect your collections policy?

Your policy must address four primary US compliance touchpoints before it goes live.

• Fair Debt Collection Practices Act (FDCPA): Applies directly to third-party collectors. If your business collects its own commercial B2B debts, the FDCPA typically does not apply to your internal team. The moment you hire an outside agency, however, that agency is bound by the FDCPA, and your policy must specify what conduct standards you require from any agency you engage.
• Telephone Consumer Protection Act (TCPA): Using an autodialer or pre-recorded message to contact customers requires prior express consent. Your policy must define which outreach channels require consent documentation and prohibit unauthorized autodialer use.
• State collection laws: Many states have their own debt collection statutes that apply to first-party collectors and impose additional restrictions on contact frequency, permissible hours, and required disclosures. California, New York, and Texas each have notable state-level requirements. Your policy should require legal review of state-specific language before deployment in any new market.
• Debt Collection Improvement Act (DCIA) and Treasury rules: Relevant if your organization handles federal program receivables or government-backed accounts. OMB Circular A-129 requires agencies to prepare a Credit Management and Debt Collection Plan, establish oversight structures, and use the full range of collection techniques with documented internal controls.

When to call legal counsel

Involve your attorney before the policy is adopted, not after a problem surfaces. Specific triggers for mandatory legal review include:

• Initial policy adoption and any material amendment
• Any escalation that may lead to litigation or wage garnishment
• Credit reporting of delinquent accounts
• Engagement of a third-party collection agency
• Any outreach using automated dialing or text messaging
• Accounts involving bankruptcy, deceased debtors, or disputed ownership

Pro Tip: Require documented legal sign-off for any policy language that authorizes adverse actions, including credit reporting, account offsets, and litigation referrals. Keep that sign-off on file with the version history of the policy.

Practical legal checklist for the policy document

• Counsel sign-off date and attorney name on the policy cover page
• Retention schedule for demand letters and dispute correspondence (minimum seven years)
• Dispute handling SLA (respond within 30 days)
• Written prohibition on autodialer use without documented consent
• Statement of which state laws govern each customer segment
• Process for handling bankruptcy notices and cease-and-desist requests

---

What should your collections policy template package include?

A complete template package gives your team everything they need to execute the policy without improvising. The package should contain: a policy outline document, standard demand letters (first, second, and final), email subject line templates, a phone script card, a dispute intake form, a write-off approval form, and an escalation checklist.

Centralizing these templates in a searchable knowledge base reduces friction between AR, legal, and customer-facing teams and keeps everyone working from the same approved language. When a template changes, update the central repository first, then notify all users, rather than emailing revised files that create version confusion.

Customizing templates for your accounts

B2B vs. B2C language: B2B demand letters can reference contract terms, purchase orders, and commercial credit agreements. Consumer-facing language must be more carefully worded to avoid FDCPA-adjacent risks, even when the FDCPA does not technically apply to your internal team.

Small-balance vs. high-dollar accounts: A $200 overdue invoice warrants a firm email and one phone call before a write-off decision. A $50,000 account warrants certified letters, executive-level calls, and a formal payment plan negotiation. Your templates should reflect those differences explicitly.

Regional legal differences: If you operate across multiple states, flag which template elements require state-specific language and note which states require additional disclosures.

Policy appendix list

Every policy document should include these appendices:

• Appendix A: Version history (date, change summary, approver)
• Appendix B: Key contacts (AR manager, Controller, legal counsel, approved outside agencies)
• Appendix C: Sample demand letters (first, second, final)
• Appendix D: Dispute intake form and SLA
• Appendix E: Write-off approval form and authority matrix
• Appendix F: Applicable state and federal law references

---

Which KPIs should you track to measure collections performance?

The core metrics for any internal collections program are: Days Sales Outstanding (DSO), days delinquent by aging bucket, recovery rate, percent of AR past due, promise-to-pay conversion rate, and collector activity per account. Track all six, and you have a complete picture of both portfolio health and team performance.

DSO measures the average number of days it takes to collect payment after a sale. A rising DSO signals that either credit terms are too loose or follow-up is too slow. Most finance teams target a DSO within five to ten days of their stated payment terms.

Recovery rate is the percentage of delinquent balances actually collected in a given period. Track this by aging bucket (30-day, 60-day, 90-day, 90-plus) so you can see where accounts are falling out of the funnel.

Promise-to-pay conversion rate tells you how often a customer who commits to a payment date actually pays. A low conversion rate points to a scripting or follow-up problem, not necessarily a credit quality problem.

Collector activity per account (calls made, emails sent, letters issued) ensures your team is following the escalation schedule and gives you data to coach underperformers.

Reporting cadence and dashboard fields

Run a monthly AR aging report for finance leadership. The report should show: total AR balance, balance by aging bucket (current, 30, 60, 90, 90-plus), DSO trend over the last three months, recovery rate by bucket, and the number of accounts at each escalation stage.

The GSA policy manual calls for monthly monitoring with a clear audit trail, a cadence that works equally well for private-sector finance teams.

Sample action thresholds to build into your policy:

• DSO exceeds stated terms by more than 15 days: trigger AR manager review
• More than 10% of AR balance is 60-plus days past due: escalate to Controller
• Recovery rate on 90-day accounts falls below 40%: review escalation script and consider agency referral criteria
• Promise-to-pay conversion rate drops below 60%: audit collector activity logs and retrain

---

How do you roll out the policy without disrupting cash operations?

The recommended sequence is: pilot with a selected account segment, train the team, launch fully, run 30/60/90-day reviews, then get governance sign-off on the final version. Skipping the pilot is the most common rollout mistake. A two-week pilot on a defined account segment surfaces gaps in the templates, the escalation logic, and the system integrations before they affect your entire AR portfolio.

1. Select your pilot segment. Choose 20–30 accounts that represent your typical mix: a few current, a few 30-day, a few 60-day. Avoid your largest or most sensitive accounts for the pilot.

2. Assign a pilot owner. One AR team member runs the pilot, documents every exception, and reports daily to the AR manager. This person becomes your internal subject-matter expert.

3. Train the team before full launch. Cover: the policy structure, the escalation schedule, how to use each template, how to log activity, and how to handle disputes. A 60-minute training session with a written reference card is enough for most teams.

4. Run the full launch. Apply the policy to all in-scope accounts. Communicate the change to sales and customer success so they are not caught off guard by credit holds or escalation calls.

5. 30-day review. Pull the first month's KPIs. Compare DSO and recovery rate against your pre-policy baseline. Identify any templates that generated confusion or pushback.

6. 60-day review. Assess whether escalation timelines are being followed consistently. Check the activity logs for gaps. Adjust thresholds if the data supports it.

7. 90-day review and governance sign-off. Present findings to the CFO or Controller. Get formal approval of the final policy version. File the signed copy with version history.

Change management notes

Tell your sales team about the credit hold process before it happens to a customer they manage. Frame the policy as a tool that protects the business's cash flow, not a punitive measure. For CRM and ERP updates, load the approved templates into the system before launch so collectors are never working from an unapproved draft. Treating policy updates as part of operational release cycles keeps your documentation and your system templates synchronized as the policy evolves.

---

What should you automate, and what still needs human judgment?

Automate the repetitive, time-sensitive tasks: payment reminders, aging flag notifications, follow-up email sequences, payment link delivery, and monthly KPI reporting. Keep human judgment in the loop for disputes, high-dollar negotiations, payment plan approvals above your threshold, and any referral to legal or an outside agency.

A practical automation implementation checklist:

• Data integrations: connect your collections platform to your accounting system (QuickBooks, NetSuite, Sage, or similar) so aging data flows automatically without manual exports.
• Template loading: upload all approved demand letters, email subjects, and phone scripts into the platform before go-live. Version-control them the same way you version the policy.
• Permissioning: restrict who can send final-demand letters or trigger agency referrals. Match the system permissions to the approval matrix in your policy.
• Audit logs: confirm the platform logs every outreach attempt, every response, and every status change with a timestamp and user ID.
• KPI dashboards: configure the dashboard to surface DSO, aging buckets, and recovery rate automatically so finance leadership sees current data without waiting for a manual report.

When automation aligns with a well-documented policy, finance teams report meaningful reductions in days-to-payment and significant time savings on manual follow-up. Interval-ai, for example, automates multi-channel outreach and real-time tracking of overdue accounts, and clients report recovering substantial balances without adding headcount.

Pro Tip: Treat every policy update as a mini product release. Assign a policy owner who is responsible for version control, release notes, and notifying the team when templates in the system change. Policy-document drift, where the written policy says one thing and the system does another, is one of the most common compliance gaps in AR operations.

---

The biggest mistake finance teams make when building a collections policy

Most finance teams write a policy and then file it. The document exists; the behavior does not change. That gap between policy and practice is where cash gets lost.

The second most common mistake is building an escalation schedule that looks right on paper but has no data behind the thresholds. Setting a 90-day write-off trigger because "that's what everyone does" is not a policy decision. It is a guess. Your thresholds should come from your own aging data: at what point does your recovery rate drop below a level that justifies continued internal effort? That number is different for every business, and the only way to find it is to measure.

Overly legalistic language is a real operational problem, not just a readability complaint. When collectors cannot understand the policy, they default to their own judgment, which defeats the purpose of having a policy at all. Write the policy in plain language. Save the legal citations for the appendix.

The fix is straightforward: pilot small, require documentation for every exception, and use templates to enforce consistent tone across every customer interaction. A policy that is short, clear, and actually used beats a comprehensive document that sits in a shared drive.

---

Interval-ai cuts the time between policy and payment

Writing the policy is step one. Getting paid faster is the goal. Interval-ai gives finance teams an automated collections platform that puts your policy into action from day one, without adding headcount or chasing down manual follow-ups.

The platform manages multi-channel outreach across email, phone, and SMS, routes disputes automatically, maintains a full audit log of every customer interaction, and surfaces real-time KPI dashboards so you always know where your AR stands. Templates load directly into the system, so every message your team sends matches the approved language in your policy. When the policy changes, the templates update in one place.

Interval-ai clients report reducing days-to-payment by over 30 days and recovering significant balances without additional staffing costs. If you are ready to move from a policy document to a working collections operation, Interval-ai and see how the platform fits your AR workflow.

---

Sources

These authoritative US sources provide the federal and sector-level guidance your legal and finance teams should consult while drafting the policy.

• How to Build a Scalable Knowledge Base for Collections Policy
• Credit and Debt Management Handbook
• PART III: THE FEDERAL NONTAX DEBT COLLECTION PROCESS (May 2023)
• POLICIES FOR FEDERAL CREDIT PROGRAMS AND NON-TAX RECEIVABLES
• Accounts Receivable and Debt Collection Policy Manual (posted_version_08-21-2020)

---

This article is general information, not a substitute for advice from a qualified financial advisor. Consult a qualified financial professional about your own circumstances before acting on anything here.

FAQ

What is an internal collections policy?

An internal collections policy is a governance document that defines your credit terms, escalation rules, dispute handling process, write-off authority, and compliance responsibilities for recovering overdue accounts.

What is the recommended escalation timeline for collections?

Most finance teams use a 30/60/90-day escalation structure: email and phone contact in the first 30 days, formal demand letters and payment plan offers by day 60, and legal referral or agency handoff after day 90 with no resolution.

What are the best practices for managing internal collections?

Assign clear ownership, separate billing from collections duties, use standardized templates for every customer communication, track DSO and recovery rate monthly, and require documented legal sign-off before any adverse action such as credit reporting or litigation.

Does the FDCPA apply to internal collections teams?

The FDCPA generally applies to third-party debt collectors, not to businesses collecting their own commercial debts internally. However, any outside agency you engage is bound by the FDCPA, and several states have their own laws that extend similar protections to first-party collectors.

How often should you review and update a collections policy?

Review the policy at least annually, and immediately after any significant change in your customer mix, payment systems, or applicable state or federal law. Document every revision in a version history log and get fresh legal sign-off on material changes.