Accounts Receivable Policy Template for Small Businesses

Published By California Recoveries Editorial

The short answer: an accounts receivable policy states who may extend credit, what must appear on an invoice, how payments and disputes are recorded, when overdue follow-up occurs, and who can approve exceptions. The template below is an operating framework to customize—not legal or accounting advice.

A policy is useful only when an employee can follow it without guessing. California's State Administrative Manual emphasizes written procedures, prompt billing, accurate records, timely follow-up, and defined responsibility. Those principles translate well to a small-business AR policy even though each business must adapt the details to its contracts, customers, systems, and professional advice.

Copy-ready AR policy outline

1. Purpose and scope

Template language: This policy establishes consistent procedures for approving customer credit, issuing invoices, recording payments and adjustments, resolving disputes, following up on overdue balances, escalating accounts, and retaining supporting records. It applies to all employees who sell on credit, create invoices, post receipts, communicate about balances, or approve account decisions.

List the business units and transaction types covered. If consumer and commercial accounts are both possible, require them to be classified and handled under the rules applicable to each rather than assuming one process fits all.

2. Roles and authority

RoleMinimum responsibilityAuthority limit to define
Sales or account ownerCollect customer and billing information before work beginsMay not promise unauthorized credit terms
BillingIssue accurate invoices with supporting referencesMay correct administrative errors
AR ownerPost receipts, maintain notes, and run remindersMay approve routine payment arrangements up to $_____
OperationsInvestigate delivery, scope, or quality disputesMay recommend—but not post—credits
ApproverApprove credit limits, exceptions, escalation, and write-offsDocument thresholds by role

3. Customer setup and credit approval

Template language: Before extending credit, the business will verify the customer's legal name, billing address, accounts-payable contact, tax information where needed, requested payment method, and agreed terms. Credit limits and exceptions require documented approval. Customer records will be reviewed at least [annually / on a defined trigger].

Use the detailed customer credit policy guide to define application evidence, risk tiers, limits, review triggers, and exception approval.

4. Contract and invoice requirements

  • Document the price, scope, due date, acceptance terms, and any required purchase-order number before performance.
  • Issue invoices promptly to the correct billing contact and channel.
  • Include a unique invoice number, issue date, due date, itemized description, amount, payment instructions, and dispute contact.
  • Retain the agreement, purchase order, delivery or acceptance evidence, invoice, credits, and correspondence in the account file.

5. Cash application and adjustments

Template language: Receipts will be recorded promptly and applied using remittance detail. Unidentified cash, short payments, credits, refunds, write-offs, and manual adjustments will be placed on an exception list and resolved by a named owner. Adjustments above $_____ require approval by _____.

Specify how quickly deposits are posted, who investigates unidentified receipts, and what evidence supports each adjustment. Reconcile the subledger and control account using the monthly AR reconciliation checklist.

6. Dispute handling

Template language: A dispute record will identify the invoice, disputed amount, customer reason, evidence requested, internal owner, response deadline, and resolution. Genuine disputes will be routed for investigation rather than left in the standard reminder sequence. Any credit or correction requires documented approval.

Set response times for common categories such as missing purchase orders, delivery questions, pricing differences, quality claims, or payments already sent.

7. Overdue follow-up schedule

Choose dates that fit your terms and customer relationships. Label the schedule as your internal policy, not a legal requirement.

TriggerActionRecord
Before due dateConfirm invoice receipt for material balancesDate and contact
1–7 days past dueFriendly reminder with invoice and payment optionsEmail copy
8–30 days past dueFollow-up email or call; identify blockers and request a dateContact note and promise date
31–60 days past dueManager review of evidence, dispute status, and account riskDecision and next action
Policy threshold reachedFinal internal notice or external-options reviewApproval and complete file

8. Payment arrangements and exceptions

State who may approve a plan, the maximum duration, whether new work continues, how missed installments are handled, and where the written agreement is stored. Apply exception criteria consistently and record the business reason.

9. Escalation and outside providers

Template language: An account will receive a documented escalation review when it crosses [age / balance / broken-promise / dispute] criteria. The reviewer will assess the record, applicable deadlines, economics, customer status, and available channels. No confidential file will be sent externally until the provider's qualifications, scope, fees, security practices, and written terms have been reviewed.

The policy should not promise that every account follows the same path. Bankruptcy, litigation, a credible dispute, or a time-sensitive legal issue may require qualified legal advice.

10. Reporting, records, and policy review

  • Review the aging report at a defined weekly or monthly cadence.
  • Track balances by aging bucket, unresolved disputes, unapplied cash, and broken promises.
  • Keep contact notes with date, channel, person, substance, and next action.
  • Retain records according to an approved schedule and applicable requirements.
  • Review the policy at least annually and after a material system, product, or legal change.

Implementation checklist

  1. Replace every blank and bracketed choice with a named role, amount, or deadline.
  2. Confirm the policy matches actual contracts, software, staffing, and bank workflow.
  3. Have qualified accounting or legal advisers review sections within their scope.
  4. Train everyone who sells, invoices, posts cash, handles disputes, or approves exceptions.
  5. Test the policy on three real but anonymized account scenarios.
  6. Publish a controlled version with an owner, approval date, and next review date.

A concise policy that people follow is stronger than a long manual nobody opens. Pair it with the collection process for day-to-day steps and the broader accounts receivable management guide for the full system.

Editorial review

How this page was prepared

This guide answers a defined operational question, separates general process guidance from legal advice, and links to 3 relevant primary or authoritative sources for verification.

Examples are illustrative, not reported customer outcomes. Advertising does not control our conclusions. Read our editorial and correction standards.