Accounts Receivable SOP: How to Track, Follow Up, and Escalate Overdue Invoices

Overview

A useful accounts receivable SOP is not just a reminder to “chase unpaid invoices.” It is a documented collections process that defines what happens from the moment an invoice is issued until payment is received, disputed, escalated, or written off according to company policy. For many small businesses, the problem is not a lack of effort. It is that invoice tracking lives in scattered spreadsheets, customer context sits in email threads, and overdue invoice follow up depends on whichever team member notices the issue first.

A stronger AR workflow fixes that by making a few decisions explicit:

• Who owns each stage, including invoice creation, monitoring, follow-up, and escalation.
• What triggers action, such as invoice sent, due soon, past due by a set number of days, dispute raised, or payment plan requested.
• What tools are the source of truth, whether that is accounting software, a CRM, a shared tracker, or a ticketing system.
• What message sequence is used so customer communication is consistent and professional.
• When finance involves account owners or leadership to resolve blockers or protect the client relationship.

The goal is not to make collections sound harsh. In most small businesses, good receivables management is really about clarity, timing, and recordkeeping. Many overdue invoices happen because purchase order details were missing, invoices went to the wrong contact, or the client expected a milestone sign-off before payment. A documented standard operating procedure helps your team catch those issues earlier.

This article focuses on an evergreen process you can adapt to your systems. If you are still tightening your front-end billing workflow, it can also help to review your customer intake and approval steps alongside a client onboarding checklist, since many AR issues begin before the first invoice is sent.

Step-by-step workflow

Use this workflow as the backbone of your accounts receivable SOP. The exact day counts may vary by business, but the structure should remain stable.

1. Confirm billing readiness before the invoice is issued

The collections process starts before the invoice exists. Before sending any invoice, confirm that the billing event is valid and complete. That usually includes:

• Customer legal name and billing address
• Accounts payable contact and email
• Purchase order number, if required
• Approved scope, milestone, delivery, or timesheet support
• Payment terms on file
• Any tax or VAT treatment needed for the invoice

If these details are inconsistent, the invoice may be delayed, disputed, or rejected by the customer’s AP team. Your SOP should require a quick pre-send review rather than leaving corrections for later.

2. Issue the invoice and log the key fields

Once the invoice is approved, send it from the system your business treats as the financial source of truth. Record at least:

• Invoice number
• Invoice date
• Due date
• Amount due
• Customer name
• Billing contact
• Assigned internal owner
• Status: sent, viewed, due soon, overdue, disputed, escalated, paid

If your accounting platform supports automated reminders and status updates, use them. If not, maintain a shared AR tracker with one owner responsible for daily updates. The key is that everyone sees the same status.

3. Send a confirmation or courtesy note for larger invoices

For routine low-value invoices, a system-generated email may be enough. For larger invoices, new customers, or clients with more complex internal approval chains, add a short courtesy message from the account owner or finance contact confirming:

• the invoice was sent,
• the due date, and
• whether any supporting documents are needed.

This step often prevents avoidable delays. It also makes later overdue invoice follow up easier because the customer already knows who to contact.

4. Review AR aging on a fixed schedule

Your SOP should set a standard review cadence. For most SMB teams, a weekly AR aging review is the minimum, with a lighter daily scan for incoming payments, new disputes, and invoices crossing key thresholds.

Typical buckets include:

• Current
• 1 to 15 days overdue
• 16 to 30 days overdue
• 31 to 60 days overdue
• 61 to 90 days overdue
• 90+ days overdue

The purpose of this review is not just reporting. It is to decide the next action on each open invoice. Every overdue item should have an owner, a next step, and a date for that next step.

5. Send a pre-due reminder

A simple reminder a few days before the due date can reduce late payments without creating tension. Keep it short and factual. Include the invoice number, amount, due date, and payment instructions. For customers with a strong payment history, this is often enough.

Your SOP can define this as an automated step for all invoices above a certain value or for all customers on net terms.

6. Start overdue invoice follow up immediately after the due date

When an invoice becomes overdue, the first follow-up should happen promptly. Avoid waiting until the balance is significantly aged. The tone should stay neutral and practical: confirm receipt, ask whether any documentation is missing, and restate payment terms.

A simple timeline might look like this:

• Day 1 past due: polite reminder from finance or automated system
• Day 7 past due: second reminder requesting payment date
• Day 14 past due: direct outreach from finance with call attempt if material
• Day 21 or 30 past due: involve account owner or manager
• Beyond that: follow formal invoice escalation process

The specific intervals matter less than consistency. Your accounts receivable SOP should define them so team members are not improvising on each account.

7. Classify the reason for non-payment

Not all overdue invoices belong in the same lane. During follow-up, tag the issue so the next step is clear. Common categories include:

• Administrative delay: invoice not received, wrong contact, missing PO, vendor setup issue
• Customer process delay: payment run scheduled later than expected
• Documentation issue: missing timesheet, statement of work, delivery evidence
• Billing dispute: amount, scope, rate, tax treatment, or milestone disagreement
• Cash constraint: customer requests partial payment or a plan
• Relationship risk: customer stops responding or raises broader account concerns

This classification keeps your collections process from becoming repetitive email chasing. It also helps leadership see whether the problem is actually billing quality, account management, or customer credit risk.

8. Resolve disputes separately from simple collections reminders

If the customer disputes the invoice, move it into a documented exception path. Finance should not continue sending standard overdue notices without context if the amount is under review. Instead, your SOP should require:

• logging the dispute reason,
• assigning an internal resolver,
• setting a response deadline, and
• tracking the revised expected payment date.

Many AR bottlenecks are really unresolved internal questions. A dispute path avoids the common problem where finance assumes account management is handling it, while account management assumes finance is still following up.

9. Escalate based on age, amount, or risk

Your invoice escalation process should define what triggers wider visibility. Escalation rules often include one or more of the following:

• Invoice is more than a set number of days overdue
• Balance exceeds a defined amount
• Customer has multiple overdue invoices
• Customer is unresponsive after repeated contact attempts
• Dispute remains unresolved beyond a defined window
• New work is being requested while prior invoices remain unpaid

Escalation does not always mean legal action or aggressive collections. In many small businesses, it first means involving the account owner, operations lead, or founder to make a business decision: continue service, pause future work, adjust terms, or negotiate a payment plan.

If your agreements allow late fees, document when they may be applied and who approves them. For teams that need help calculating those amounts, an invoice late fee calculator can support the administrative side, but the SOP should still define your internal approval and communication rules.

10. Record outcomes and close the loop

Every AR action should end with a clear status update. Possible outcomes include:

• Paid in full
• Partially paid
• Payment date promised
• On hold due to dispute
• Escalated to account owner
• Escalated to leadership
• Placed on payment plan
• Recommended for write-off under policy

Close the loop by updating the tracker, storing any customer communication, and noting whether the issue points to a broader process fix. If late payment happens because pricing, scoping, or billing timing is unclear, the right response may involve upstream changes, not just stronger follow-up. That is where broader finance planning tools like a cash flow forecasting template or a cash reserve calculator become useful alongside the SOP.

Tools and handoffs

A strong AR workflow depends on clean handoffs between teams. Even in a small company, collections usually touch more than one function.

Recommended tool stack categories

• Accounting software: source of truth for invoices, payments, credits, and customer balances
• Shared AR tracker: useful for notes, ownership, dispute status, and next action dates
• Email templates or CRM sequences: keeps overdue invoice follow up consistent
• Document storage: stores statements of work, approvals, timesheets, and proof of delivery
• Team communication channel: for internal escalations and quick status checks

If you are still evaluating systems, it may help to review a practical checklist for choosing the right cloud accounting software before redesigning your process around a tool that does not support your team’s needs.

Core roles and responsibilities

Your SOP should assign named responsibilities, even if one person covers multiple roles.

• Billing owner: issues invoice and verifies billing completeness
• AR owner: monitors aging, sends reminders, logs notes, and drives follow-up
• Account owner: helps when customer relationship context is needed
• Operations or delivery lead: confirms milestone completion or resolves proof-of-work questions
• Finance lead or owner: approves escalations, payment plans, service holds, or write-off recommendations

Example handoff points

• From delivery to billing when work is approved for invoicing
• From billing to AR when invoice is sent and due date is confirmed
• From AR to account owner when customer becomes unresponsive or raises concerns
• From account owner to finance lead when relationship, credit, or service continuation decisions are needed

The simplest way to reduce confusion is to define service-level expectations for internal responses. For example: disputes acknowledged within one business day, account owner pulled in after a set aging threshold, and escalation decisions made within two business days once flagged.

Quality checks

An accounts receivable SOP is only useful if it improves outcomes over time. Add a small set of quality checks that your team can review weekly or monthly.

Invoice quality checks

• Invoices include correct legal entity, contact, PO, and payment terms
• Support documents are attached when required
• Due dates match contract terms
• Amounts match approved pricing or milestone terms

Process quality checks

• All overdue invoices have a current owner and next action date
• Reminder timing follows the documented sequence
• Disputes are tagged separately from standard late payments
• Escalations happen according to policy, not personal preference
• Promises to pay are tracked and verified

Management review questions

• Which customers are repeatedly late, and why?
• Are delays concentrated in one stage, such as invoice setup or dispute resolution?
• Are account teams informed early enough when payment risk increases?
• Do payment terms still fit the risk level of the customer?
• Should deposits, milestone billing, or shorter terms be considered for similar future work?

These reviews often surface pricing and profitability questions, not just collections issues. If late payment creates pressure on margin or working capital, you may want to pair AR review with tools such as a profit margin calculator, markup vs margin calculator, or break-even calculator to see whether your billing structure is supporting the business as intended.

When to revisit

Revisit your accounts receivable SOP whenever the process stops reflecting how work actually moves through your business. In practice, that usually means reviewing it after a tool change, a team restructure, a rise in overdue balances, or a shift in customer payment behavior.

Use the checklist below as a practical trigger list:

• You've changed accounting software, CRM, or reminder automation
• Your invoice approval or delivery sign-off process has changed
• More disputes are appearing after invoices are sent
• Customers are asking for different terms or payment plans more often
• Ownership between finance, operations, and account teams is unclear
• Your escalation path depends on ad hoc founder intervention
• Cash flow pressure has increased and aging reports need closer review

When you update the SOP, do not just edit the document. Test it in the real workflow. Review three to five recent overdue invoices and ask:

• Could a new team member tell what happened without asking around?
• Were follow-up dates clear and consistent?
• Did the right person get involved at the right time?
• Was the root cause captured, not just the symptom of late payment?

A good final step is to keep a one-page operating version of the process alongside the full SOP. That summary can include aging buckets, email sequence timing, escalation thresholds, and owner responsibilities. Teams are far more likely to use a process they can scan quickly during a busy week.

If you want this article to become an internal working document, turn it into a simple operations checklist: define your stages, set day-based follow-up rules, assign owners, add your escalation thresholds, and review the workflow monthly until it feels routine. A calm, consistent collections process will usually outperform a reactive one.