QuickBooks Financial Signals Library
Accounts Receivable Signals
AR problems announce themselves early — in migration, cadence, and silence — long before they appear as bad debt. These four signals are how slipping receivables actually look in QuickBooks.
4 signals · Last reviewed July 22, 2026
The A/R Aging Summary is a snapshot; receivables risk lives in the movement between snapshots. A flat total can hide a portfolio getting structurally older. A reliable customer can break cadence weeks before they miss a payment outright. An open invoice can sit in perfect silence because nobody — on either side — knows it exists.
Each signal below compares today's AR against its own history, which is the comparison the standard reports don't make for you.
1.Aging bucket migration
Receivables moving from current into the 31–60 and 61–90 day buckets faster than your normal pattern — the aging report getting older, not just bigger.
Why it matters
Collectability decays with age; receivables that cross 90 days are recovered at a materially lower rate in most collection experience. Migration is the earliest structural signal that collections are slipping — visible while the total AR number still looks healthy.
Common causes
- Invoices sent late or with errors, stalling payment in dispute
- Customer-side cash problems spreading through their payables
- A follow-up cadence that quietly stopped happening
- Terms creep — exceptions becoming the norm
QuickBooks records to pull
- A/R Aging Summary, compared across dates
- A/R Aging Detail for the moving invoices
- Invoice records and dispute notes
- Customer payment history
How to investigate
- Run A/R Aging Summary and compare against last week's and last month's (keep dated copies — QuickBooks shows today's).
- Compute each bucket's share of total AR and flag structural shifts, such as the 61–90 share doubling.
- Drill into A/R Aging Detail on the invoices that moved buckets.
- For each: verify the invoice is accurate, was delivered, and isn't sitting in an unlogged dispute.
- Call — don't just re-email — the largest movers today.
False positives to rule out
- One large invoice crossing a bucket boundary on its normal schedule
- Net-60 or net-90 customers who look "old" but are current to their terms
Questions to ask next
- Is the migration concentrated in one customer or spread broadly?
- Are the moving invoices disputed, undelivered, or just unattended?
- When was each mover last actually contacted?
Illustrative example — not customer data
Total AR is flat month over month — the summary looks fine. But the 61–90 bucket went from 6% to 19% of the balance: three mid-size customers stopped paying on cadence while new sales kept the total level.
How Flash covers this signal
Flash compares the aging distribution daily against the company's own history and flags migration in the morning brief with the specific invoices attached. Collection calls stay human.
Related: AR aging daily review
2.Customer concentration
A large share of open receivables — or of revenue — depending on one or a few customers.
Why it matters
Concentration converts one customer's routine payment delay into your payroll problem. It also compounds silently: the biggest account grows, smaller accounts churn, and one day a single payment slip covers none of the next payroll. Lenders and acquirers price this as risk for the same reason you should.
Common causes
- Organic growth of one strong account
- Churn of smaller customers concentrating the remainder
- Project-based businesses between projects
QuickBooks records to pull
- A/R Aging Summary by customer
- Sales by Customer Summary, trailing twelve months
- Open invoices for the largest accounts
How to investigate
- Run A/R Aging Summary and compute each customer's share of open AR.
- Run Sales by Customer Summary for the trailing twelve months and compute revenue shares.
- Flag any customer above roughly 20–25% of either measure.
- For flagged accounts: review their payment-behavior trend, credit exposure against terms, and what happens operationally if they slipped 30 days.
- Track the number quarterly so drift is visible.
False positives to rule out
- Intentional anchor-client business models — the risk is still worth pricing explicitly
- A temporary spike from one large milestone invoice
Questions to ask next
- What happens to payroll if this customer pays 30 days late?
- Are we extending more credit than the relationship's history supports?
- What is the plan to diversify — or to formally accept the risk?
Illustrative example — not customer data
One customer is 43% of open AR. They pay reliably — but their industry just entered layoffs, and a three-week slip in their payment would cover exactly zero of the next payroll. Nothing about that risk appears on the aging report.
How Flash covers this signal
Flash computes customer concentration nightly across AR and revenue and flags threshold crossings and trend in the morning brief — with the exposure stated in weeks-of-payroll terms your team can act on.
Related: QuickBooks Customer Payment Risk
3.Stale open invoice
An open invoice with no activity — no payment, no partial, no logged customer contact — beyond your follow-up cycle.
Why it matters
Invoices don't age into payment by themselves. Prolonged silence usually means one of three things: the invoice was never actually received, it's stuck in an unlogged dispute, or both sides have forgotten it. Every silent week lowers recovery odds and weakens your position if the relationship sours.
Common causes
- The invoice never delivered — bounced email, wrong AP contact
- A dispute that exists in someone's inbox but not in the record
- A follow-up cadence that broke during a busy period
- The customer waiting on a correction nobody sent
QuickBooks records to pull
- Open Invoices report
- Invoice activity and audit history
- Sent status and delivery details
- Customer notes and communication log
How to investigate
- Run the Open Invoices report sorted by date.
- Flag invoices past your follow-up cycle with no logged activity of any kind.
- Verify each flagged invoice was actually delivered — sent status, correct contact, no bounce.
- Check with the account owner for disputes that never made it into the record.
- Re-send corrected, or call — and log the contact so silence becomes measurable.
False positives to rule out
- Invoices under an agreed payment plan
- Retainage or milestone billing not yet contractually due
Questions to ask next
- Did the customer ever receive this invoice?
- Is there a dispute that exists only in email?
- Who owns the follow-up, and when is the next contact scheduled?
Illustrative example — not customer data
An $8,400 invoice from May shows zero activity. The customer's AP address changed in April; the invoice bounced and nobody saw the bounce. Ninety silent days, discovered only because someone finally sorted Open Invoices by date.
How Flash covers this signal
Flash flags open invoices with no activity past your cadence every night, ranked by amount, in the morning brief. The call still has to be human — Flash makes sure it isn't forgotten.
Related: Open invoices review checklist
4.Customer payment cadence break
A customer paying meaningfully slower than their own established pattern — 28-day money arriving at 45 days.
Why it matters
Cadence breaks are the earliest external signal of customer distress — they appear before the customer says anything and weeks before the aging report shows a problem. A break can also mean something fixable on your side: the invoice landed in a new approval process, or a dispute is forming quietly.
Common causes
- Customer cash stress spreading through their payables
- Your invoices entering a new approval workflow on their side
- A forming dispute nobody has raised formally
- Contact turnover — the person who paid you left
QuickBooks records to pull
- Customer payment history — invoice date to payment date pairs
- A/R aging trend for the account
- Recent invoices and their delivery status
How to investigate
- For your top customers, compute average days-to-pay over the trailing six to twelve months.
- Compare the most recent invoices against that baseline.
- Flag customers slipping more than about 25% or more than two weeks past their own norm.
- Ask the relationship owner what changed before assuming distress.
- Tighten exposure on flagged accounts — deposits, smaller batches — until cadence recovers.
False positives to rule out
- Seasonal payment behavior the baseline should include
- One large invoice with explicitly negotiated extended terms
- Your own late invoicing — measure from the date sent, not the date created
Questions to ask next
- Did we invoice late, or are they paying late?
- Is this one invoice or a new pattern across several?
- What does the account owner know that the ledger doesn't yet?
Illustrative example — not customer data
A customer who paid in 26±3 days for two years takes 44 days, then 51. Two months later they asked every vendor for extended terms. The cadence break was the first signal; the aging report caught it six weeks after the ledger already knew.
How Flash covers this signal
Flash learns each customer's payment cadence from history and flags breaks against their own pattern nightly — not against a generic benchmark. Candidates appear in the morning brief with the invoices attached.
Related: Customer concentration
Run these checks by hand — or wake up to them done
Everything above works with nothing but QuickBooks and a schedule. Flash Daily Insights runs the same comparisons nightly through a read-only connection and delivers the candidates in a morning brief — what changed, what looks wrong, what to do next. It never changes your books.