A delinquency bucket is a band of days past due used to group overdue invoices for analysis, reporting, provisioning, and collection workflow triggers. Standard B2B buckets are Current, 1-30, 31-60, 61-90, 91-120, 121-180, and 180+ days past due.
A delinquency bucket is a band of days past due (DPD) used to group overdue invoices for analysis, reporting, provisioning, and collection workflow design. The term is used interchangeably with aging bucket, delinquency band, and aging tranche. Each bucket holds every open invoice whose days past due falls within the band on the reporting date.
The standard B2B cutoffs that most AR teams, auditors, and credit insurers use are:
Variations exist. Some controllers extend the schema to 360+ DPD for portfolios with long settlement cycles. Subscription and SaaS teams often use tighter buckets such as 7-day or 14-day bands, reflecting the shorter cash cycle and higher renewal sensitivity. The cutoffs themselves matter less than applying them consistently across business units, currencies, and reporting periods.
Buckets do three jobs that a flat list of open invoices cannot. First, they concentrate analyst attention. A collector working 600 open invoices needs a way to prioritise, and the bucket is the cleanest signal: the deeper the bucket, the lower the recovery probability and the higher the marginal value of an hour spent on that account.
Second, buckets drive provisioning. The IFRS 9 expected credit loss model and the ASC 326 (CECL) standard both rely on bucket-based loss rate matrices. Each bucket carries a calibrated loss percentage drawn from historical write-off data, and the provision for doubtful debts is the weighted sum across the portfolio. Without buckets, the allowance for doubtful accounts becomes a guess rather than an audited number.
Third, buckets set collection workflow triggers. Mature AR functions wire Level 1 actions (reminder email, dunning letter) to the 1-30 DPD entry, Level 2 actions (phone outreach, account hold review) to 31-60 DPD, and Level 3 actions (formal demand, credit hold, third-party referral) to 61-90 DPD and beyond. The bucket is the operational trigger, not just a reporting category.
Recovery rates degrade non-linearly as invoices age. Industry rules of thumb across B2B portfolios look roughly like this:
These ranges vary by industry, customer tier, and macro conditions, but the shape of the curve is consistent. The implication is that every day an invoice sits unworked in a younger bucket costs the business roughly the marginal recovery rate of the next bucket down.
The single most important pattern in delinquency bucketing is the cliff between 61-90 DPD and 91-120 DPD. Recovery probability typically drops from the high 70s into the 50-60% range across this transition. Beyond 90 DPD, customer relationships are usually strained, disputes have hardened, and budget cycles on the customer side have moved on.
The implication for credit and collections leaders is operational: defending the 90 DPD line is worth more than recovering older balances. A euro of effort spent stopping an invoice rolling from 61-90 into 91-120 typically returns more than the same euro spent chasing 121-180 DPD balances. Teams that report only on closing AR balance miss this dynamic entirely.
Five mistakes recur across AR teams:
AI-native and agentic collections platforms shift bucket analytics from descriptive to predictive. Instead of reporting on what is in each bucket today, they model what will be in each bucket next week, and which specific invoices are most likely to roll forward if left untouched.
Three changes follow. First, monitoring becomes continuous rather than month-end, with bucket migration tracked daily and surfaced on collector dashboards. Second, predictive scoring identifies the high-risk invoices inside each bucket (which 31-60 DPD balances will roll into 61-90 if not actioned this week), letting collectors focus on prevention rather than chasing the deeper buckets after the damage is done. Third, action triggers fire automatically at bucket boundaries, with reminder cadences, escalation emails, and account holds applied without manual ticketing. The bucket stops being a static reporting category and becomes the live spine of the collection operation.
A delinquency bucket is a band of days past due used to group overdue invoices for analysis, reporting, provisioning, and collection workflow triggers. Standard B2B buckets are Current, 1-30, 31-60, 61-90, 91-120, 121-180, and 180+ DPD. The deeper the bucket, the lower the recovery probability and the higher the required collection intensity.
Most B2B AR teams use Current, 1-30, 31-60, 61-90, 91-120, 121-180, and 180+ DPD. Some extend the schema to 360+ DPD for long-cycle portfolios. Subscription and SaaS teams often use tighter 7-day or 14-day bands. The cutoffs themselves matter less than applying them consistently across business units and reporting periods.
Under IFRS 9 expected credit loss and ASC 326 (CECL), each bucket carries a calibrated loss percentage drawn from historical write-off data. The total allowance for doubtful accounts is the weighted sum of bucket balances multiplied by their loss rates. Without buckets, the provision becomes a judgement call rather than an audited matrix output.
The 60-90 DPD cliff is the sharp drop in recovery probability between the 61-90 DPD bucket (typically 70-85% recovery) and the 91-120 DPD bucket (typically 50-70% recovery). It is the single most important inflection in the aging curve. Defending the 90 DPD line is usually a higher-return use of collector effort than chasing older balances.
Bucket migration analysis tracks how invoices move between buckets over time: forward to deeper buckets, backward to paid, or held in place. Strong AR teams keep roll-forward rates below about 5% per cycle from Current into 1-30 DPD. Migration is a leading indicator of collection effectiveness, where DSO is a lagging one.
AI-native platforms move bucket analytics from descriptive to predictive. They monitor migration daily rather than at month-end, score which invoices inside each bucket are likely to roll forward, and trigger reminder cadences, escalations, and account holds automatically at bucket boundaries. The bucket becomes the live spine of the collection operation rather than a static report category.
