Accounts Receivable Resources

How to Read a Receivables Balance, and What It Cannot Tell You.

A reference on the two artefacts every AR team works from — the ageing report and the standard measures — written around their limits rather than their definitions. Useful against whatever system you already have. Everything is on this page.

Reference on this page — no download, no form

The five buckets, and what each is usually asked to prove

    Every amount on an ageing report looks the same regardless of why it is there. That single fact explains most of what goes wrong in receivables.

    What this is

    A Reference About Limits, Not a Definition List.

    Including a plain account of what this page is not.

    What this page is

    • The five ageing buckets, each with what it actually says, what people read into it, and what it cannot tell you
    • Eight structural reasons a receivable is late that have nothing to do with a customer being unwilling to pay
    • Twelve standard AR measures, each tagged with the layer that holds the data it needs — including the ones Bonza cannot produce
    • Ten questions a working receivables operation should be able to answer quickly
    • An honest account of which part of all this a payment-management layer can actually help with

    What this page is not

    • Not a guide library. No resource has been published, and this page offers no download, title, author, date, page count or file size
    • Not accounting guidance. Write-offs, allowances and ledger treatment belong to accounting policy, and Bonza is not an accounting system
    • Not a collections playbook. Bonza surfaces what needs attention and does not chase, escalate or apply fees
    • Not a claim about reducing DSO. This page explains what DSO measures and why a payment-management layer cannot produce it alone
    • Not a scorecard. Nothing here is submitted, scored or counted

    An ageing report answers one question well: how long has this been open. Almost every decision a receivables team makes depends on a different question, and the report is silent on all of them.

    The ageing report

    Five Buckets, and What Each One Is Not Able to Tell You.

    Bucket boundaries vary between businesses; the readings below do not. Select a bucket to see what it says, what it is assumed to say, and where the gap sits.

    These are illustrative readings of how ageing buckets behave, not a measurement of any business. No figure, ratio or amount appears anywhere on this page.

    See how outstanding, due and overdue differ as states

    Why things are late

    Eight Reasons a Receivable Is Late That Have Nothing to Do With Willingness.

    Read the left column of each pair first. That is the point: on an ageing report, all eight are indistinguishable from a customer who simply has not paid.

      Chasing harder works on exactly one of these. The other seven need something recorded that currently is not.

      The measures

      Twelve Standard AR Measures, and Which Layer Holds the Data.

      Each one carries what it measures, what it hides, and where its data lives. Filter by data source to see which measures a payment-management layer can produce on its own and which it cannot.

        Half of the standard receivables vocabulary needs data that lives in accounting or an ERP. Bonza Payments is not an accounting system, holds no general ledger and does not produce those measures. Stating that plainly is more useful than implying a payment suite covers all of receivables, because the gap decides which systems you still need.

        See the receivables capability itself

        How to tell

        Ten Questions a Working Receivables Operation Can Answer Quickly.

        Not a maturity score and not a form. Any of these that takes a spreadsheet and an afternoon is pointing at something the ageing report was never going to show you.

        • For any open amount, was anything collected against it at all?
        • Which open amounts are in question rather than simply unpaid?
        • Which customers hold recorded credit that has not been applied to anything?
        • Which expected payments have a stored payment method that expires before their date?
        • How much of what is open comes from repeating arrangements rather than one-time amounts?
        • For a given customer, what does the whole payment relationship look like, not just the open rows?
        • Which open amounts were created in the last thirty days and which have been moving down the report for months?
        • When an amount passed from not-yet-due to due to overdue, did anything about it change other than the date?
        • Can a service agent see the payment position from the customer record without opening the finance system?
        • Can the customer see the same position you see, and pay from it?

        These are written to be answerable about a system you already have, including as questions to take into an evaluation of Bonza Payments.

        Where Bonza fits

        The Part of Receivables That Is a Payment Problem.

        The reference above is deliberately vendor-neutral. This section is not, and it is marked so you can weigh it differently.

        What Bonza Payments does here

        • Records what was expected against what was collected, so a partial payment reduces the open amount rather than sitting beside it
        • Keeps outstanding, due and overdue as three distinct states rather than one state with a date filter
        • Holds the payment position against the Salesforce customer record, so the balance has a relationship behind it
        • Keeps refunds and recorded customer credit attached to what they came from
        • Surfaces a payment method expiring before the payment that depends on it
        • Flags what is worth a person’s attention, and leaves the judgement to the person

        What Bonza Payments does not do here

        • No accounting, no general ledger, no write-offs and no allowance for doubtful accounts — Bonza is not an accounting platform or an ERP
        • No DSO, CEI, average days delinquent or bad debt ratio, because those need sales and ledger figures Bonza does not hold
        • No dispute or deduction records, so it cannot report a dispute rate
        • No collections, dunning, chasing, fee application or recording of promises to pay
        • No transaction processing — a configured payment gateway performs that
        • No storage of funds. Recorded customer credit is a record, not stored cash

        Stated as one position: Bonza Payments manages the payment lifecycle behind a receivables balance inside Salesforce, and makes no claim to measure, replace or report the accounting that sits above it.

        See what connected receivables visibility changes

        About downloads

        What This Page Would Show You If There Were Anything to Download.

        A receivables resources page usually opens with a shelf of templates. This one does not, because the shelf is empty.

        If downloadable accounts receivable resources are published later, this section will list them with their actual titles and dates. Until then it states the count, which is currently zero.

        Answered

        Accounts Receivable Questions, Answered Here.

        Questions about the reference itself, and about the limits it keeps pointing at.

        What does an ageing report actually tell you?

        One thing, reliably: how long each open amount has been past its date. It is silent on why. A disputed amount, an unmatched partial payment, an unapplied credit, a duplicate obligation and a customer who has decided not to pay all appear identically, which is why working a receivables operation from the ageing report alone produces follow-up aimed at the wrong things.

        Why does Bonza Payments not report DSO?

        Days Sales Outstanding is calculated against credit sales for a period, and that figure lives in accounting or the ERP. Bonza records what was expected and what was collected; it does not hold what was sold, so it cannot produce the measure on its own. The same constraint applies to the Collection Effectiveness Index, average days delinquent, bad debt ratio and allowance for doubtful accounts. Six of the twelve measures on this page sit in that category.

        Which receivables measures can a payment-management layer produce on its own?

        The ones built only from expected amounts, collected amounts and dates: ageing buckets, the overdue share of what is open, partial-payment exposure, and expiry exposure on expected payments. Total open receivables and the recurring share of what is open need data from both layers. The counts on this page are derived from that list rather than asserted.

        What is the difference between receivables visibility and accounting?

        Accounting records what happened for the purposes of reporting and statutory obligation, and owns the ledger, write-offs and allowances. Receivables visibility, in the sense used here, is about operating the open amounts day to day: what is owed, by whom, in what state, what has been collected against it and what needs someone to look. Bonza works on the second and replaces none of the first.

        Why does partial payment keep appearing in this reference?

        Because it is the condition that breaks the most measures at once. The transaction succeeded, so anything built on transaction results shows it as paid; the customer is still not settled, so the balance disagrees. Unless collected is recorded against expected on the same obligation, the shortfall is not in the ageing report, not in the balance and not in anyone’s queue.

        Does Bonza do collections or dunning?

        No. Bonza surfaces what has gone overdue and what is worth a person’s attention, and the action stays with the team. It does not chase customers, run escalation sequences, apply fees, record promises to pay or make a decision on anyone’s behalf. Dunning is a billing-system function and collections is an operating discipline; neither is a payment-management capability.

        How early can a receivables problem actually be seen?

        Earlier than most reports allow. A payment method that expires before its payment date is knowable the moment both dates exist. An amount whose request was never delivered is knowable before the date arrives. An unapplied credit is knowable the moment it is recorded. All three are invisible on an ageing report because the report only begins describing an amount once it is already late.

        Is this reference specific to Salesforce?

        The buckets, causes and measures apply wherever receivables are managed. The context is Salesforce, because that is where Bonza Payments operates, and because several of the questions on this page are only answerable when the payment position sits on the customer record rather than in a separate finance system.

        Can receivables be managed in Salesforce without doing accounting in Salesforce?

        Yes, and the distinction matters. Holding payment obligations, collected amounts, states and attention against the customer record is an operating capability. Recording journal entries, running write-offs and maintaining a ledger is accounting. Bonza does the first and none of the second, which is why it sits alongside an accounting system rather than in place of one.

        Why is the first thirty days more important than the last ninety?

        Because almost every structural cause on this page is created early and only becomes visible late. By the time an amount reaches the oldest bucket, the information that would explain it — whether the request was delivered, whether the amount was agreed, whether something was collected and not matched — has usually stopped being recoverable. The oldest bucket is where the cost appears, not where the cause is.

        Is there a downloadable version of this reference?

        No. No accounts receivable guide, template, checklist, ageing-report model or PDF has been published, so there is no title, author, date, page count or file to offer, and this page does not imply otherwise. The reference is delivered in full on the page, which means it can be read, linked to and quoted without requesting anything.

        What should I bring to a conversation about receivables?

        Which of the ten questions above your current setup answers quickly and which take an afternoon, and roughly how much of your oldest bucket you believe is genuinely owed rather than bookkeeping that never closed. Those two answers make a conversation about your actual receivables operation rather than a demonstration of features.

        Where to take this

        Bring the Questions the Ageing Report Cannot Answer.

        The useful conversation is not about the size of the balance. It is about which parts of it you cannot currently explain, and what would have to be recorded for that to change.

        Useful things to have to hand

        • Whether partial payments currently reduce the open amount or sit beside it
        • Where a disputed amount lives today, if anywhere
        • How you find an unapplied credit
        • Which of the twelve measures your team is actually asked for
        • What proportion of the oldest bucket you would expect to survive a review