AR Aging Report: How to Read One and Use It to Get Paid Faster

Learn to read an AR aging report, diagnose overdue invoices, and prioritize collections by bucket to reduce DSO and improve cash flow.

Key takeaways

• An accounts receivable aging report sorts every unpaid invoice into time buckets, so you can see exactly how much you are owed and how late each payment is.
• The report is a cash flow tool, not a bookkeeping artifact. It tells you which overdue invoices to chase first and why payments are slipping.
• Reading it well takes about ten minutes. Start with totals and shape, find concentration risk, then trace the real blockers behind late payments.
• Each aging bucket maps to a specific next action, from a friendly reminder on current invoices to a recovery decision on anything past 91 days.
• Pairing the report with days sales outstanding turns a static snapshot into a trend you can manage week over week.
• Teams that automate invoicing and collection with Plooto remove the manual friction that pushes invoices into the 31 to 60 day bucket in the first place.

Why your accounts receivable aging report decides how fast you get paid

Late payments are not a rare problem; they are the default. Across North America, roughly half of all B2B invoices are paid late, according to the Atradius Payment Practices Barometer. The Federal Reserve tells a similar story from the other side of the ledger: In its Small Business Credit Survey, 51% of small firms named uneven cash flow as a financial challenge.

The accounts receivable aging report is how finance teams fight back. It groups outstanding receivables by how long they have been unpaid, then turns that picture into a plan. This guide shows you how to read one fast, what each bucket means, and how to use it to get paid faster.

Accounts receivable aging report meaning and why it's a cash flow tool

An accounts receivable aging report lists every open invoice and sorts it by how overdue it is. Picture a single page that answers one question: Who owes us money, and how late are they?

What an AR aging report shows (and what it doesn't)

An AR aging report shows a snapshot of unpaid invoices "as of" a specific date. It does not show trends on its own. Instead, one report is like a photograph. A series of reports over several months becomes a film, and the film is where the real story lives.

The report differs from two things people confuse it with. An invoice list shows what you billed. A customer statement shows what one customer owes. The aging report shows the whole book of receivables sliced by time, which is where outstanding receivables fit inside the larger cash conversion cycle. If you need the groundwork first, review the accounts receivable basics before you go deeper.

Why finance teams use AR aging reports to protect cash flow

Finance teams use the report as an early-warning system. An invoice that drifts from current into the 60-day bucket is a write-off in slow motion, and the report catches it while you can still act.

The report also works as an operational signal. Patterns in the buckets expose billing errors, customer disputes, a weak collections cadence, or payment terms that were set too loose. It connects directly to forecasting too, because each bucket tells you when cash is likely to land.

Who should own the AR aging report?

The controller or finance manager should own the report. The AR clerk runs the day-to-day follow-up, and sales or customer success steps in when a relationship needs leverage. One owner keeps the report honest and makes it the single source of truth for collections priorities and escalation.

AR aging report basics: Structure, fields, and common formats

Every AR report shares the same skeleton: Buckets across the top, customers down the side, and dollar amounts in between. Once you know the parts, any version reads the same way.

The standard aging buckets and what they mean

You may have a reason to bucket yours differently, but most reports use five standard buckets similar to these 5:

• Current: Not yet due
• 1 to 30 days past due: Recently late
• 31 to 60 days past due: A process is breaking
• 61 to 90 days past due: Elevated default risk
• 91+ days past due: Recovery mode

Customize the buckets when your business model demands it. Net 60 terms, project billing, and retainers all change what "late" means, so set bucket boundaries that match how you actually invoice.

Key columns to expect in an AR report

A clean report carries the fields you need to act: Customer name, invoice number, invoice date, due date, original amount, and current balance. Watch the credits and partial payments closely, because an unapplied credit can make a paid customer look delinquent. The strongest reports add a notes column for disputes, promises to pay, and collection stage. That single column turns a static list into a working tool.

Before you trust any report, confirm three things: The "as of" date and posting cut-off (so nothing looks falsely delinquent), a consistent rule for credits and unapplied cash, and any filters you applied by customer type or region.

How to read an AR aging report in 10 minutes

You can read an AR aging report in about ten minutes if you work from the top down. Start with shape, then risk, then root cause. Resist the urge to open individual line items first.

Start with totals and shape, not line items

Begin with the total AR balance and compare it to your monthly revenue. Does the size look normal for your business? Then check one simple health metric: The percent of AR that is current versus overdue. Finally, look at the long tail. How much money sits in the 61+ and 91+ buckets? That number is your risk, and it deserves the first hard look.

How do you spot concentration risk fast?

Concentration risk hides in plain sight. Calculate your top five customers as a share of total AR, then as a share of overdue AR. If one payer represents a large slice of what is late, a single stalled customer can freeze your cash. Cross-check those names against their credit limits and internal risk tiers so you know your real exposure.

What causes overdue invoices? Finding the real blockers

Most overdue invoices trace back to a handful of patterns, not bad-faith customers. The Atradius survey found that the leading cause of late B2B payments in the United States is administrative inefficiency in the customer's own payment process.

Look for repeating signals:

• The same customer, the same service line, or the same approver showing up late again and again.
• Separate genuine disputes from "no one is processing it" and from "the invoice never arrived."
• Many late payments are simple admin failures, such as a missing purchase order, wrong remittance details, or an invoice sent to the wrong billing contact.

What the aging buckets mean in practice and what to do next

Each bucket calls for a different play. Treating a five-day delay like a 95-day default wastes effort and damages relationships. Match the action to the age.

Current and 1 to 30 days: Prevent and recover early

For current invoices, the goal is prevention. Confirm the invoice was delivered to the right contact with the correct purchase order, and send a friendly "upcoming due" nudge on large balances.

For invoices 1 to 30 days late, assume oversight rather than refusal. Resend the invoice, remove friction with a payment link, and ask one question that captures the reason: Dispute, cash constraint, or approval pending.

31 to 90 days: Structure, then escalate

Once an invoice passes 30 days, stop sending reminders and start building a plan:

1. 31 to 60 days: Set a specific payment date, not "ASAP," and confirm the amount and method. Offer frictionless options like ACH or pre-authorized debit. Use a partial payment plan only when it genuinely speeds cash, not when it just delays the reckoning.
2. 61 to 90 days: Escalate with guardrails. Move the account from the AR clerk to the controller to an executive sponsor. Pause services if your credit policy allows it, and switch to formal, factual demand language backed by a documentation trail.

91+ days: Recovery mode and loss containment

At 91+ days, the question changes from "when will they pay?" to "how much can we recover?" Decide whether to pursue, settle, send to a collections agency, or write off. Protect future exposure by revising that customer's terms, requiring a deposit, or moving them to pre-authorized payments. Then feed the lesson back into your credit policy so the same gap does not reopen.

A bucket-based follow-up framework to get paid faster

When every overdue invoice runs through the same scoring and cadence, collections stop depending on who happens to remember.

Collections priority scoring

Score each overdue invoice on five factors: Days past due, dollar amount, customer history, dispute status, and concentration risk. A high score means call today. A low score means a templated email is enough.

Map each score band to a next best action so the report tells your team what to do, not just what is wrong. Service-based businesses and product-based businesses can use the same model with small tweaks.

Cadence playbook by bucket

Set a clear rhythm for who does what and when:

• Current: Upcoming-due reminders for high-value invoices only
• 1 to 30: Two to three touches per week, mixing email and a phone call
• 31 to 60: A weekly call plus written confirmation of any commitment
• 61 to 90: An escalation touch with management involved
• 91+: A weekly action review with a clear collections or legal checkpoint

Short, well-written templates shorten cycle time without burning relationships. Keep a friendly reminder, an invoice resend, and a promise-to-pay confirmation ready to go. For the full workflow that surrounds these touches, see the accounts receivable process guide.

AR aging report diagnostics: What patterns reveal about your business

The buckets are symptoms, and the diagnosis comes from how they move over time. Three patterns deserve your attention because each points to a different fix.

A high current balance but rising DSO

A healthy-looking current bucket paired with a climbing collection time usually means one of three things:

1. Revenue is outgrowing your collections capacity
2. You are invoicing late
3. Terms are creeping longer because sales keeps negotiating extensions without governance.

A growing 31 to 60 day bucket

A swelling 31 to 60 bucket signals a process breakdown, not a customer problem. The usual culprits are approval bottlenecks on the customer side, inconsistent follow-up with no clear owner, and payment friction from too few payment methods. This is the bucket to attack first, because it is the most fixable.

Separate disputes from delinquency to stop “fake overdue"

A stubborn 91+ bucket often hides disputes that were never resolved. Track dispute aging alongside invoice aging, and report "in dispute" separately from "delinquent." Then set a service-level agreement for dispute resolution so genuine disagreements do not quietly rot into write-offs.

AR aging vs DSO: How to measure collection performance

The AR aging report shows where you stand right now. Days sales outstanding shows how you are trending. Used together, they measure collection performance from both angles.

What is days sales outstanding (DSO)?

Days sales outstanding (DSO) measures how long it takes your business to collect payment after a credit sale. A lower number signals stronger cash flow and effective collections, as J.P. Morgan notes. For a deeper breakdown, Plooto's guide on days sales outstanding walks through the metric in detail.

How do you calculate DSO?

Calculate DSO in three steps:

1. Gather your total accounts receivable at period end, your net credit sales for the period, and the number of days in the period.
2. Divide accounts receivable by credit sales.
3. Multiply by the number of days.

A related metric, accounts receivable turnover, counts how many times you collect your average receivables in a period. J.P. Morgan offers a clean example: A shop with $80,000 in credit sales and average receivables of $10,000 has a turnover of 8, which means it collects its receivables about every 45 days. Avoid the common trap of gaming DSO by delaying invoicing, since it flatters the metric while hurting real cash.

Using the aging report to explain DSO movement

When DSO jumps, the aging report tells you why. Find which bucket grew most and you have your answer. If DSO rose but the current bucket still looks fine, check whether a few large invoices slipped into 31+ territory. For a complementary view, the collection effectiveness index measures how well you collect what was actually available to collect.

The AR aging action table you can copy into your process

The fastest way to operationalize everything above is a single table. Map each bucket to its signal, priority, action, owner, and goal, then keep it next to your weekly review.

To put the table to work, run a short weekly AR review. Walk the top overdue accounts, new delinquencies, dispute blockers, and promised payments. Track a handful of KPIs: Percent current, percent 31+, percent 61+, cash collected versus target, and broken promises. Require a reason code, a next step, and a date on every touch, and the report stays actionable.

Use AR automation to shorten time to cash

Manual AR is where good intentions go to die. Inconsistent follow-up, payment friction, and status blind spots ("Did they get it? Did they pay?") all push invoices deeper into the aging buckets.

Where manual AR breaks down

Manual invoicing creates an uneven cadence, so some customers get chased and others slip. Payment friction makes late payments worse, because every extra step gives a payer a reason to wait. And without real-time status, your team cannot tell a delivery failure from a stall. Remember that administrative inefficiency was the top cause of late payments in the Atradius data, which is exactly the failure automation removes.

How Plooto speeds collections

Accounts receivable automation software attacks those bottlenecks directly. Plooto automates invoicing and recurring billing, collects payments through direct debit and pre-authorized debit, and tracks status in real time so nothing falls through the cracks. Because it syncs with your accounting software through prebuilt accounting integrations, reconciliation lag shrinks and your aging report reflects reality. If your report keeps showing recurring 31 to 60 day problems, that is the signal to streamline collection with AR automation.

Implementation playbook: Improve your AR aging results in 30 days

You can move your numbers in a single month with a focused, week-by-week plan. Each week builds on the last.

1. Week 1, clean the data: Standardize customer records, billing contacts, and remittance details. Resolve unapplied cash and tag disputed invoices. Confirm how each invoice is delivered and that delivery is proven. A clean report tells the truth.
2. Week 2, lock the cadence: Assign owners, escalation rules, and a service-hold policy. Start promise-to-pay tracking and follow up on broken promises. Build templates and require a next-step note on every touch.
3. Week 3, reduce friction: Require purchase order and reference fields at invoice creation. Offer multiple payment rails where policy allows. Line up sales and account owners to support escalations.
4. Week 4, measure and tune: Compare your bucket distribution at the start and end of the month. Eliminate the repeat errors behind delinquency, and set next month's targets, such as cutting the 61+ bucket by a set percentage and lowering the DSO trend.

Governance and controls that keep overdue invoices from coming back

Cleaning up the report once feels great. Keeping it clean takes policy. A few enforceable guardrails stop overdue invoices from creeping back.

Credit and terms guardrails

Set objective triggers for when to tighten terms, require a deposit, or move a customer to pre-authorized payments. Base credit holds on bucket, amount, and concentration risk rather than gut feel. Define who can approve an exception, so longer terms are a decision, not a default.

Documentation and auditability

Keep written commitments, dispute trails, and approvals in one place. Consistent evidence is not just good housekeeping; it supports the judgments behind your allowance for doubtful accounts, an expectation reflected in SEC staff guidance on documentation. Good records protect both your cash and your financial reporting.

Collections best practices

Use a tone ladder that moves from friendly to firm to formal, never to threats. The Washington State Office of Financial Management publishes a useful set of receivable collection best practices you can adapt into a simple checklist, so every staff member collects the same way.

Turn your AR aging report into a weekly cash engine

The mindset shift is simple. Stop reading the aging buckets as categories and start reading them as root-cause signals. The three patterns that matter most are a growing 31 to 60 bucket, a creeping 61+ balance, and customer concentration.

The system that accelerates collections is just as simple: A bucket-based cadence, a scoring rule, and clear escalation. One table plus one weekly review ritual creates steady, measurable pressure on your DSO.

If you are still managing overdue invoices by hand, automation is the fastest way to reduce payment friction and lift on-time payments. Try Plooto for free and turn your AR aging report from a monthly autopsy into a weekly cash engine.

Try Plooto free