- Home
- Industries
- Accounts Receivable
Accounts Receivable
Know What You're Owed. Know What Needs Attention Next.
Connect collected, outstanding, due, overdue and upcoming customer payment activity inside Salesforce so Accounts Receivable teams can understand where payments stand and what may need attention next.
Salesforce-native payment management suiteIllustrative Accounts Receivable operating view. The total payment position shows $412,800.00 collected, $250,000.00 outstanding, $61,500.00 due, $48,200.00 overdue and $118,400.00 upcoming. The receivables timeline runs expected, outstanding, due, overdue, then attention. The needs-attention panel lists three items: an overdue payment for Demo Customer, a payment method expiring 31 October before a relevant upcoming payment on 15 November for Sample Account, and a relevant AI payment insight for Example Client, each requiring human review. The customer payment position table lists three sample customers with their original obligation, collected amount, outstanding amount, status and relevant next event. Every figure on this page is illustrative sample data and is not real customer data. Expected payment activity is not guaranteed cash.
An amount sits in exactly one timing state on any given day. Which one decides how soon a person looks at it.
Overdue payment · $5,000.00 past its relevant expected date.
Human reviewPayment method expires 31 Oct; relevant upcoming payment 15 Nov.
Internal signal · human reviewRelevant AI payment insight: the customer payment position changed.
Insight · human review| Customer | Original obligation | Collected | Outstanding | Status | Relevant next event |
|---|---|---|---|---|---|
| Demo Customer | $20,000 | $15,000 | $5,000 | Due | Relevant date |
| Sample Account | $30,000 | $30,000 | $0 | Collected | Refund recorded |
| Example Client | $14,000 | $6,000 | $8,000 | Outstanding | Next relevant payment, future date |
Definition
What Is Accounts Receivable Management in Bonza Payments?
A direct answer for anyone comparing receivables, payment-management and accounting capabilities.
Accounts Receivable management in Bonza Payments helps Salesforce-powered businesses understand customer payment obligations across collected, outstanding, due, overdue and relevant upcoming payment activity.
Bonza connects receivables with customer and payment context so Finance and AR teams can understand not only how much remains open, but also where individual customer payments stand in the wider payment lifecycle. Salesforce can manage Accounts Receivable this way through payment management, with the receivables position sitting on the same customer record the rest of the business already uses.
The work behind the number
Finance Usually Has the Number. The Hard Part Is Understanding What Is Inside It.
A total Accounts Receivable balance can tell Finance that an amount remains outstanding. It does not automatically answer any of these.
Which customers make up that balance?
What is not yet due?
What is due now?
What has become overdue?
What has already been resolved through relevant payment activity?
Has a refund changed the payment position?
Does relevant customer credit exist?
What recurring payment activity is expected next?
Is a relevant payment method approaching expiry before an upcoming payment?
Which payment situations deserve attention?
The AR problem is often not missing data. It is having to reconstruct the meaning of the data.
Signature · AR total ≠ AR position
The Total Tells You How Much. The Position Tells You What It Means.
Four illustrative receivables portfolios. Every one of them reports the same outstanding total. Step through them and watch how little that total tells you on its own.
This figure is written once and never changes. It is the number an AR report would lead with, and it is the same in every portfolio below. Everything that actually decides what a team should do today is in the composition, not here.
Portfolio A · almost all of it is not due yet
Comfortable timing$205,000.00 + $30,000.00 + $15,000.00 = $250,000.00 matches the outstanding total above
Six per cent of this balance is overdue. Most of it simply has not reached its expected date. A team looking only at the $250,000.00 total would have no way to know that.
This is the balance an AR report would call healthy, and it is the same number as the next three.
Portfolio A, mostly ahead. Not yet due two hundred and five thousand dollars, due thirty thousand dollars, overdue fifteen thousand dollars. The three bands sum to two hundred and fifty thousand dollars, matching the frozen total. Overdue is six per cent of the balance.
The sum of the three bands is computed from the data on every change and compared against the frozen total, so the arithmetic is shown rather than claimed. All figures are illustrative sample data. This is a composition view, not an aging report, a collections queue or a score.
Two businesses can have the same outstanding AR balance and completely different payment situations. The AR total tells Finance how much is open. The payment context tells Finance what that number means.
Expected → collected → open → attention → next
Accounts Receivable Should Explain the Journey—not Just the Balance.
Six stages, each of which a balance alone collapses into a single figure.
Expected
A relevant customer payment obligation exists, with an amount and a customer attached to it.
Collected
Relevant payment activity has occurred through a configured gateway and is recorded against the customer.
Open
Some part of the payment obligation remains unresolved. This is the outstanding receivable, and on its own it says nothing about urgency.
Timing
Whether the open amount is upcoming, due or overdue. This is where an outstanding figure becomes operable.
Attention
A relevant payment situation deserves review. A person looks at it and decides; nothing on this path resolves itself.
What's next
The next relevant payment event, whatever form it takes, stays attached to the same customer payment story.
Timing states
Not Every Outstanding Payment Needs Attention Today.
An outstanding payment is not necessarily overdue. An amount may remain outstanding before its expected payment date, become due when that date arrives, and become overdue after the relevant date passes.
The amount remains unresolved. Some part of a payment obligation has not been met by payment activity.
This is the amount, not the clock. It says nothing about urgency on its own.
Outstanding, and expected later. The relevant date has not arrived.
Visible, and not something anyone needs to act on today.
The relevant expected date has arrived. The amount has not changed; the date has.
A different queue from merely outstanding, and a different urgency.
The relevant expected date has passed, with the amount still the same as the day before.
The state most receivables reviews are built around.
Requires appropriate review. A person decides what happens next.
Bonza surfaces it with its timing and customer context. It does not decide, and it does not act.
If everything open is treated the same, Finance loses the timing context that makes receivables actionable. Portfolio B and Portfolio C in the section above are the same total and the same problem only if these states are collapsed.
Past → present → future
A Complete AR View Needs More Than Today's Outstanding Balance.
Three horizons. Most receivables reporting covers the middle one and stops there.
What happened?
- Collected
- Relevant payment history
- Refunds
- Customer credits
What is open?
- Outstanding
- Due
- Overdue
- Current customer payment position
What is expected next?
- Upcoming relevant payment activity
- Recurring payments
- Payment forecast
- Relevant payment method expiry
Past explains the history. Present explains the position. Future helps Finance see what may be coming next.
Customer level
The Aggregate Balance Matters. The Customer-Level Position Makes It Operable.
Nobody collects an aggregate. The work happens one customer at a time, even when the report is a single figure.
Total AR · $250,000.00 · illustrative · made up of positions like these
Three customers, three completely different conversations. Customer B is fully collected and still has a post-payment change worth knowing about. Customer C has nothing overdue and a reason to look before its next payment date.
AR operations happen customer by customer, even when Finance reports the total.
Invoice + receivables
The Invoice Establishes What Was Expected. Receivables Show What Remains Open.
Three different questions, routinely treated as one. Separating them is what makes it possible to say where a gap actually is.
Illustrative.
- What was expected?
- What remains unresolved?
- What actually happened?
This page is about the receivables position rather than about producing the invoice. Bonza does not generate accounting entries from any of it. For the invoice-driven payment model itself, see Invoice-Based Payments.
Payment management + AR
Receivables Become More Useful When They're Connected to the Payment Lifecycle.
Receivables visibility and payment processing are different. Configured gateways perform relevant transaction processing, while Bonza manages the wider Salesforce-native payment lifecycle.
Inside Salesforce, above the gateway.
Bonza Payments connects receivables with relevant Salesforce customer and payment context, including payment activity, refunds, customer credits, recurring payments and configured payment gateways. That is what turns an outstanding figure into something a team can act on: the amount is the start of the record rather than the whole of it.
AR should not begin and end with the outstanding balance.
Payment patterns behind the balance
Not Every Receivable Comes From a Recurring Payment Relationship.
Individual customer payment obligations may still require the same receivables visibility after the payment event.
Explore One-Time & Ad Hoc Payments
Recurring Payments Add a Forward Dimension to Receivables.
Recurring payment activity gives Finance both current payment context and relevant forward payment context: the payment in front of them, and the one expected after it.
- The current payment
- Its relevant status
- The current receivable position
- The next expected payment
- Due and overdue context
- Payment method expiry as an internal signal
- Payment forecasting of relevant expected activity
Post-payment change
A Collected Payment Can Still Change the Customer Payment Position.
A payment that was once collected may have a later event that changes how Finance should understand the customer payment story.
The refund stays attached to the payment it came from.
Customer Credit Changes the Context of the Next Payment.
Customer credit recorded and managed within Bonza Payments may be relevant to future customer payment activity where supported.
The other side of the receivable
Receivables Are an Internal View. The Customer Still Needs a Clear Way to Pay.
The same obligation looks entirely different depending on which side of it you are standing.
- Outstanding
- Due
- Overdue
- Customer payment position
- What am I paying?
- How much?
- What relevant option is available?
- Payment
- Status
The business may call it a receivable. The customer experiences it as a payment they need to understand and complete.
Explore Customer Payment Experience Customer Self-Service Payments
Connect Customer Payments With the Salesforce Experience They Already Use.
Where an organisation already uses Salesforce Experience Cloud for customer interactions, relevant payment activity can flow back into the same receivables position.
The organisation's own portal. Bonza does not provide the entire portal.
Experience Cloud is not the payment processor and Salesforce does not process payments.
Gateways
Your Receivables View Should Not Be Split by Payment Gateway.
Accounts Receivable can work across multiple configured gateways, with one payment-management layer above all of them rather than a separate view per provider.
Configured by the business, not routed automatically.
The gateway processes the relevant transaction. Bonza keeps the payment activity connected to the wider customer payment lifecycle.
Explore Multiple Payment Gateways Manage Multiple Payment Gateways
Forward view
Receivables Tell You What Is Open. Payment Forecasting Helps You See What Is Expected Next.
Bonza Payment Forecasting focuses on relevant upcoming customer payment activity. It is not corporate cash-flow, treasury or bank-balance forecasting.
- Relevant expected payment activity in the immediate window
- Relevant expected payment activity across the period
- Relevant recurring and upcoming activity beyond it
Explore Payment Forecasting Forecast Upcoming Payments
Sometimes the Signal Appears Before the Next Payment Date.
A payment method approaching expiry before relevant future payment activity can be useful operational context. It is two dates in an order worth noticing.
Illustrative.
AI Should Help Finance See What Deserves Attention—not Make the Financial Decision.
AI can help identify AR items needing attention by reading the context that already exists and pointing a person at what changed. The signal ends at a human.
- A relevant payment moved into overdue status.
- Upcoming payment activity changed.
- A relevant payment method is approaching expiry.
- The customer payment position changed.
- Default prediction
- Credit scoring or collection scoring
- Autonomous collections or AI customer chasing
- Automatic write-offs
- Automatic payment decisions
- AI gateway routing
The insight is presented with its context. A person reviews it and decides.
The operating view
Turn Accounts Receivable Into an Operational View.
The move this section is arguing for is from “what is our AR balance?” to “what is happening inside it?”
Illustrative Payment Command Center view for Accounts Receivable. The KPI strip shows $412,800.00 collected, $250,000.00 outstanding, $61,500.00 due, $48,200.00 overdue and $118,400.00 upcoming. The receivables position table lists four sample customers with their payment obligation, collected amount, outstanding amount and status. The payment forecast panel shows $34,200.00 expected this week, $118,400.00 across the next thirty days and relevant recurring activity. The needs-attention panel lists an overdue payment, a payment method expiry and a relevant AI payment insight, each for human review. The recent payment activity strip lists a payment, a refund, customer credit and a relevant status change. Every figure is illustrative sample data and is not real customer data. No general ledger, journal entry, trial balance, profit and loss statement or balance sheet appears, and none is provided by Bonza.
| Customer | Obligation | Collected | Outstanding | Status |
|---|---|---|---|---|
| Demo Customer | $20,000 | $15,000 | $5,000 | Due |
| Sample Account | $48,000 | $12,000 | $36,000 | Overdue |
| Example Client | $14,000 | $6,000 | $8,000 | Upcoming |
| Test Organisation | $30,000 | $30,000 | $0 | Collected |
Expected payment activity only. Not a cash-flow, treasury or bank-balance forecast.
Sample Account · $36,000 outstanding, past its relevant expected date.
Human reviewExample Client · method expires 31 Oct, next relevant payment 15 Nov.
Internal signal · human reviewDemo Customer's payment position changed after a recorded refund.
Insight · human reviewAll values illustrative sample data, not real customer data. This is a payment-management operating view, not an accounting dashboard: no general ledger, journal entries, trial balance, profit and loss, balance sheet, bank reconciliation, revenue recognition or tax accounting appears, and Bonza provides none of those.
Balance view → operating view
A Balance Is Useful. An Operating View Is More Actionable.
Both describe the same receivables. Only one of them tells a team where to start.
$250,000.00
Total AR · illustrative
“How much is outstanding?”
“What happened, what remains open, what is expected next, and what needs attention?”
The balance is a financial position. The operating view explains the customer payment activity behind it.
Transaction view ≠ receivables view
A Successful Transaction Does Not Explain the Entire Receivable.
A gateway can tell you a payment succeeded. That is a true statement and an incomplete one.
“Did the payment go through?”
“Where does the customer payment relationship stand?”
The transaction tells Finance what happened once. The receivables view explains where the customer payment relationship stands.
Cross-industry AR patterns
Different Industries. The Same Core Receivables Questions.
Each entry is the question that sector actually asks, and what Bonza does not provide there. The pattern being shared does not make the surrounding systems interchangeable.
Financial & professional services Client obligations
“What client payment obligations remain outstanding?”
Keep relevant client payment activity and receivables connected to Salesforce. See Financial & Professional Services.
- Trust accounting
- Matter billing
- Escrow
- Accounting system functionality
Education Learner or payer obligations
“What relevant customer or payer payment obligations remain open?”
Connect supported payment activity and receivables. See Education.
- Student accounting
- Financial aid
- Tuition calculation
Healthcare Customer payment activity
“What relevant customer payment activity remains outstanding?”
Manage supported customer payment context and keep it attached to the Salesforce record.
- Medical billing
- Claims
- Patient accounting
- Insurance adjudication
Technology & SaaS One-time and recurring
“What one-time or recurring customer payment activity remains open, and what is expected next?”
Connect relevant payment activity across both patterns. See Technology & SaaS.
- ARR
- MRR
- Revenue recognition
- Subscription billing
- Usage billing
Membership & associations Member obligations
“What relevant customer or member payment obligations remain open?”
Keep payment and receivables context connected. Membership status stays in the membership system or CRM and is never set by Bonza. See Membership & Associations.
- Membership accounting
- Dues calculation
- A renewal engine
Real estate & property Property-related obligations
“What supported customer payment obligations remain unresolved?”
Connect the payment activity and its position, in neutral payment language. See Real Estate & Property.
- Rent ledger
- Lease accounting
- Escrow
- Property accounting
Nonprofits Where receivables apply
“What relevant payment obligations remain open where receivables apply?”
Manage the relevant payment activity and its position. See Nonprofits.
- Donations
- Pledges
- Grants
- Fund accounting
Other Salesforce-powered businesses The same five questions
Where customer payment obligations exist, the same core AR questions remain, whatever the sector is called.
What was expected? What was collected? What remains open? What needs attention? What is expected next? See Other Salesforce-Powered Businesses.
- Universal industry compatibility
- Vertical-specific functionality
Two paths
Most Receivables Follow the Payment Lifecycle. Exceptions Need Attention.
The normal path needs nobody. The attention path ends at a person every single time.
Nothing needs a decision
Four steps, no review needed. This is the path most receivables follow, and it is the one that should stay frictionless.
Ends at a person
Seven steps, and step six is a person. Bonza does not automatically resolve the exception: it makes it visible with the timing and customer context needed to decide.
What goes wrong
Seven Accounts Receivable Mistakes That Make the Balance Harder to Operate.
Each is defensible on its own. Together they are why the month-end AR conversation starts with rebuilding context.
Managing the total without the customer context
Connect aggregate receivables to customer-level payment positions.
Treating outstanding, due and overdue as the same thing
Preserve the timing context, so urgency comes from the date rather than a guess.
Using the gateway as the AR system
Separate transaction processing from receivables management. The gateway knows transactions, not obligations.
Looking only backward
Add relevant forward payment visibility, remembering that expected activity is not guaranteed cash.
Managing refunds and credits outside the receivables story
Keep post-payment changes connected to the payment they came from.
Splitting receivables by payment channel or gateway
Keep one broader payment-management model above the providers.
Asking Finance to reconstruct context manually
Connect payment lifecycle information around the customer, so nobody has to assemble it.
The cost nobody budgets for
The Hidden Work in AR Is Often Reconstructing What the Balance Means.
Seven checks before anyone can answer a single customer question. None of it appears on a plan.
Two steps, and the eight facts are already attached to the record rather than assembled from seven places.
If Finance has to rebuild the customer payment story before it can understand the receivable, the operation is still fragmented.
Maturity
How Accounts Receivable Operations Mature.
A description of how these operations tend to develop. Nobody is scored here, and no level is assigned to anyone.
Balance visible
Finance knows the amount outstanding. What is inside it has to be asked for.
Status visible
The timing states become distinguishable from one another.
- Outstanding
- Due
- Overdue
Customer connected
Receivables sit against the customer alongside what actually happened.
- Customer
- Payment activity
- Relevant obligation
- Refunds
- Credits
Forward-looking
The view stops being purely historical, with expiry remaining an internal signal.
- Recurring activity
- Upcoming payments
- Payment Forecasting
- Payment Method Expiry
Attention-driven
Teams can see where review may be needed, with people still making the decisions.
- Payment Command Center
- AI Payment Insights
- Exception-focused workflows
Across the business
One Customer Payment Position. Different Teams Need Different Answers.
Five teams, five sets of questions, one lifecycle underneath them.
- What was collected?
- What remains outstanding?
- What is due?
- What is overdue?
- What happened after the commercial event?
- What remains open?
- What is expected next?
The same connected customer payment record underneath every one of these questions, inside Salesforce.
- Where is the payment lifecycle?
- What needs attention?
- What did this customer pay?
- What remains open?
- Was there a refund or credit?
- How do we keep payment and receivables context connected without building separate payment applications?
The questions change by team. The customer payment reality should not.
Team views in more depth: Finance & Accounts Receivable, Revenue Operations, Business Operations, Customer Service and Salesforce Teams.
Patterns
Common Accounts Receivable Patterns.
Six situations that recur regardless of sector, and what connecting them changes.
A customer payment obligation remains unresolved.
Finance knows it is open but needs more context.
Connect the outstanding position with relevant customer and payment context.
Clearer receivables visibility.
The relevant expected payment date arrives.
Finance needs to distinguish it from future outstanding activity.
Surface due context as its own state.
Clearer timing visibility.
A relevant payment remains unresolved after its expected date.
It becomes another line in a large AR balance.
Surface overdue context for review.
Clearer attention visibility.
A customer has continuing relevant payment activity.
Finance can see the current payment but not the next expected payment context.
Connect recurring and relevant upcoming payment visibility.
Better forward awareness.
Payment value changes after collection.
AR context no longer matches the original transaction.
Connect refund or relevant customer-credit activity to the payment.
Clearer customer payment history.
Payments are processed through different configured gateways.
Finance has to reconstruct customer payment activity provider by provider.
Keep the wider payment context connected in Salesforce.
More coherent payment visibility.
Business outcomes
What a Connected Receivables Operation Actually Changes.
Defensible outcomes only. There is no claim here about reduced DSO, reduced bad debt, faster collections, higher recovery, faster cash flow, working-capital improvement, specific productivity gains, specific cost reduction, specific ROI or guaranteed collection.
Understand collected, outstanding, due and overdue payment activity.
Understand the payment position behind the aggregate AR figure.
Distinguish outstanding, upcoming, due and overdue from one another.
See relevant recurring and upcoming payment activity.
Keep refunds and customer credits in the wider payment story.
Keep payment-management context connected across configured gateways.
Give Finance, Operations, RevOps and Customer Service relevant views of the same lifecycle.
Surface payment situations that may deserve human review.
Why Bonza
Why Run the Receivables Operation Through Bonza?
Eight reasons, all of them about what sits behind the number rather than the number itself.
Keep receivables connected to relevant Salesforce customer context.
Connect the outstanding amount with the payment activity behind it.
Understand timing within the open receivables position.
Support different customer payment patterns in one model.
Keep post-payment value changes connected to the payment history.
Manage wider payment context across configured gateways.
Connect relevant upcoming and recurring payment activity.
Use AI Payment Insights and the Payment Command Center to surface relevant context.
The wider lifecycle
Accounts Receivable Is One View of a Larger Payment Lifecycle.
Not every receivable touches every capability. These are the parts of the suite the position can draw on.
Read by:
Receivables tell you what is still open. The connected payment lifecycle tells you why, what happened, and what may come next.
FAQ
Accounts Receivable Questions.
Twelve questions buyers actually ask, answered against established capabilities.
What is Accounts Receivable management in Salesforce?
Accounts Receivable management in Bonza Payments helps Salesforce-powered businesses understand customer payment obligations across collected, outstanding, due, overdue and relevant upcoming payment activity. The receivables position sits against the customer record rather than in a separate system, so the amount open and the activity behind it can be read together.
What is the difference between Accounts Receivable and payment management?
Receivables answer what remains unresolved. Payment management covers the wider lifecycle around that: the payment activity that produced the position, the timing states within it, post-payment changes such as refunds and customer credits, the configured gateways involved, and the relevant upcoming activity. A receivables figure is one view of that lifecycle rather than the whole of it.
What is the difference between an invoice and a receivable?
An invoice establishes a relevant payment obligation and states what was expected. A receivable describes what remains unresolved after payment activity has been recorded. A third question sits alongside them both, which is what actually happened, and that is the payment activity itself.
What is the difference between outstanding, due and overdue payments?
An outstanding payment is not necessarily overdue. An amount may remain outstanding before its expected payment date, become due when that date arrives, and become overdue after the relevant date passes. The amount can be identical in all three states; what differs is the timing, and therefore how soon a person should look at it.
Can Bonza show collected and outstanding payments together?
Yes. Collected and outstanding amounts are visible against the customer alongside the timing state of whatever remains open, so a total can be read next to the composition that makes it up. Two balances that look identical can be in very different positions once that composition is visible.
Can Bonza show upcoming customer payments, and is that cash-flow forecasting?
Bonza Payment Forecasting focuses on relevant upcoming customer payment activity. It is not corporate cash-flow, treasury or bank-balance forecasting, and it is not revenue or working-capital forecasting. Expected payment activity is not guaranteed cash.
How do recurring payments connect with Accounts Receivable?
Recurring payment activity gives Finance both current payment context and relevant forward payment context: the current payment and its status, the resulting receivable position, and the next expected payment. This does not describe subscription billing, plan management, usage billing, proration, automated retry or dunning.
Can Accounts Receivable work across multiple payment gateways?
Yes. Bonza can support multiple configured payment gateways with one payment-management layer above them, so the receivables view is not split by provider. Bonza does not perform settlement consolidation, gateway reconciliation, smart routing, automatic failover, least-cost routing, automatic retry or token portability.
How do refunds and customer credits affect the payment position?
A payment that was once collected may have a later event that changes how Finance should understand the customer payment story. A refund stays attached to the payment it came from, so the payment history is updated rather than replaced. Customer credit is recorded and managed within Bonza Payments and may be relevant to future customer payment activity where supported; it is not cash held by Bonza, a wallet balance, stored funds, a bank balance or escrow.
Can Bonza surface expiring payment methods, and can AI identify items needing attention?
A payment method approaching expiry before relevant future payment activity can be surfaced as useful operational context. It does not say the payment will fail, and there is no automatic card updater, automatic outreach or automatic remediation. AI Payment Insights can point a person at relevant changes such as a payment moving into overdue status or a changed upcoming position, and every insight ends at human review rather than an action.
Does Bonza automatically chase overdue customers, or is it a debt-collection platform?
No to both. Bonza is not a debt-collection platform and performs no collections activity. There is no automated dunning, no automatic email or SMS reminders, no autonomous collections or AI collection agents, no promise-to-pay handling, no legal collections, no late-fee calculation, no automatic write-offs and no bad-debt management. Overdue amounts are surfaced for a person to review and decide.
Does Bonza replace accounting software or ERP?
No. Bonza Payments is not an accounting system, general ledger, ERP or bank. It does not provide journal entries, double-entry accounting, a chart of accounts, revenue recognition, tax accounting, bank reconciliation, settlement reconciliation or automated reconciliation, and it does not perform credit scoring, default prediction or collection scoring. Its focus is customer payment management inside Salesforce.
Accounts Receivable
Don't Just See the AR Balance. Understand What's Inside It.
See how Bonza Payments connects receivables, customer payment activity, due and overdue visibility, recurring payments, refunds, credits and upcoming payment context inside Salesforce.