Improve receivables visibility
See What You've Collected. What You're Owed. And What Needs Attention.
Connect collected, outstanding, due, overdue and upcoming customer payment activity in Salesforce so finance teams can understand where receivables stand and what may need attention next.
Powered by the Salesforce-native Bonza Payments suiteTotal receivables$497,600Invoiced and expected
Collected$312,400Resolved
Outstanding$185,200Unresolved
Due$52,300At their date
Overdue$18,400Past their date
Upcoming$114,500Not yet due
Receivables flow
Illustrative flow. Of $497,600 invoiced or expected, $312,400 has been collected and $185,200 remains outstanding. Within that outstanding amount, $114,500 is upcoming, $52,300 is due and $18,400 is overdue. The overdue amount, together with other relevant signals, is surfaced for attention.
Needs attention
$18,400 overdue across 9 payments.Obligations past their due date.
3 payment methods approach expiry before an upcoming payment.Timing information for review.
$74,800 of upcoming recurring payment activity.Known future payment events.
Overdue payment activity increased.Payment insight, surfaced for a person to review.
Customer receivables
| Customer | Outstanding | Due | Overdue | Upcoming | Status |
|---|---|---|---|---|---|
| Acme Industries | $4,000 | $4,000 | — | $5,000 | Due |
| Northstar Logistics | $8,500 | — | $8,500 | $9,200 | Overdue |
| Global Corp | $4,250 | — | — | $4,250 | Upcoming |
| Harbourview Trust | $6,750 | $6,750 | — | — | Due |
Illustrative product interface. Every customer name, amount and date on this page is a sample used to explain the concept — none of it is real customer data.
Definition
What Is Receivables Visibility?
Receivables visibility is the ability to understand customer payment obligations and payment activity across what has been collected, what remains outstanding, what is currently due, what has become overdue and what is expected next.
Bonza Payments helps businesses keep this payment and receivables context connected within Salesforce so finance teams can understand the current position without reconstructing the payment story from multiple disconnected systems.
Receivables visibility is not the same as accounting. It is operational visibility into the customer payment lifecycle.
Bonza is a Salesforce-native payment management suite. It is not a general ledger, an ERP, an accounting platform, a treasury system or a credit bureau, and it does not perform bank reconciliation or revenue recognition.
The business problem
The Problem Isn't Always Missing Data. It's Missing Context.
A business may already hold every fact it needs. The difficulty is that each one lives somewhere else.
Scattered
Nine correct facts, one unclear picture
CustomerAcmeSalesforce
Invoice$10,000Invoices
Payment collected$6,000Gateway
Outstanding$4,000Spreadsheet
Due$4,000Spreadsheet
Customer credit$400Credit record
RefundNoneRefund record
Next expected payment15 NovRecurring schedule
Payment methodExpires 31 OctPayment method
Connected
The same nine facts, read together
Acme owes$4,000
Of an original$10,000
Already collected$6,000
CurrentlyDue
Credit available against it$400
Next payment expected15 Nov
But the method expires31 Oct
Same data. The connected reading surfaces something the scattered one cannot: the payment method expires two weeks before the next expected payment.
More payment data does not automatically create better receivables visibility.
Each fact can be correct while the overall payment picture stays unclear. The value comes from connecting the context, not from collecting more of it.
Context
A Receivables Number Without Context Is Only Half the Answer.
Outstanding
$125,000
- Is it due?
- Is it overdue?
- Which customers owe it?
- When is payment expected?
- Was part of it already collected?
- Did a refund change the position?
- Does customer credit exist?
- Is recurring activity scheduled?
- What changed since yesterday?
Connected receivables view
Due$52,300
Overdue$18,400
Upcoming$54,300
Customers — who owes each part
Payment activity — what has already happened
Attention — what may require review
The total tells finance how much. Context tells finance what it means.
The model
A Useful Receivables View Should Answer Five Questions.
Each one is answered by a different part of the payment lifecycle. Together they are the view.
What is still outstanding?
What is due or overdue?
What is expected next?
What needs attention?
Receivables visibility is not one number. It is a connected set of answers.
Any one of these answered alone leaves a gap. A team that knows the outstanding total but not the timing, or the timing but not the customer, is still reconstructing.
Where the work goes
When Payment Data Is Fragmented, Finance Becomes the Integration Layer.
Fragmented
Seven places, one manual assembly
Salesforce
Invoice system
Gateway
Spreadsheet
Recurring schedule
Refund record
Credit record
The finance team then reconstructs
What was paid? What is outstanding? What is overdue? What comes next? — four questions, assembled by hand, every time someone asks.
Connected with Bonza
One lifecycle, read in place
Customer
Payment obligation
Bonza payment lifecycle
Paid
Due
Overdue
Credit
Refund
Current position + forward view + attention, without the assembly step.
This is not a claim that Bonza replaces every external financial system. Your accounting platform stays where it is. What changes is that the customer payment context stops living in seven places at once.
How the picture is built
Six Capabilities, One Payment Picture.
01 · Receivables
Know What Is Still Outstanding.
Receivables visibility starts with understanding what payment value remains unresolved — not as a total, but as a position attached to a customer and an obligation.
The key question is the plainest one in finance: what are we still waiting to collect?
Explore Receivables
From obligation to outstanding position · illustrative
1Customer — Acme Industries
2Payment obligationINV-2041
3Original amount$10,000
4Payment activity$6,000
5Outstanding position$4,000
6StatusDue
02 · Due & Overdue Payments
Separate Due From Overdue.
Outstanding does not automatically mean overdue. Timing matters, and collapsing the two loses the distinction that tells a team whether a payment is simply still expected or has moved beyond its date.
This is visibility, not collections. Nothing here chases a customer.
Explore Due & Overdue Payments
Outstanding, separated by timing · illustrative
ΣOutstanding$185,200
→Upcoming — not yet due$114,500
→Due — at its date$52,300
→Overdue — past its date$18,400
!Attention — surfaced for review
03 · Payment Forecasting
Add a Forward View to the Current Receivables Picture.
Receivables tell finance what remains unresolved today. Forecasting adds visibility into relevant payment activity expected in future periods. The two answer genuinely different questions.
Receivables is what is still outstanding. Forecasting is what payment activity is expected next. Expected activity is not guaranteed cash.
Explore Payment Forecasting
Today outward · illustrative
0Today — current receivables$185,200
30Next 30 days — expected activity$125,000
60Next period — expected activity$141,200
→Future$118,300
Expected payment activity, not guaranteed cash receipts.
04 · Recurring Payments
Connect Repeating Payment Relationships to the Receivables View.
Recurring payment relationships create both historical and forward payment context. A mature receivables view should not treat every cycle as an unrelated transaction.
One unresolved month belongs in receivables. The months ahead belong in the forward view. Both belong to the same customer relationship.
Explore Recurring Payments
One arrangement across five cycles · illustrative
January and February collected. March outstanding. April upcoming. May scheduled.
March → ReceivablesThe unresolved cycle joins the outstanding position.
April + May → Forward contextKnown future payment events join the forward view.
05 · Invoices
Understand the Payment Obligation Behind the Receivable.
Invoice context connects what the customer was expected to pay with relevant payment activity and what remains outstanding. Without it, a receivable is an amount with no origin.
Bonza is not an accounting or ERP system. It connects the obligation to the payment, not the payment to your ledger.
Explore Invoices
Invoice to status · illustrative
1Invoice — original amount$10,000
2Payment$6,000
3Outstanding position$4,000
4Due / overdue statusDue
06 · Refunds and Customer Credit
See When Refunds or Credits Change the Customer Payment Story.
A customer payment relationship does not always end with collection. Refunds and customer credits can change how finance interprets the customer's payment position — and a receivables view that ignores them reads the relationship wrong.
Customer credit is recorded and managed within Bonza Payments. It is not a wallet, a cash balance, stored funds or a bank balance, and none of this adjusts an accounting ledger.
Explore Refunds & Credits
After collection, the position can still change
1Customer payment position
2Change required — a human decision
RefundValue returned through the relevant process, recorded in payment history.
Customer creditValue available against relevant future payment activity.
→Updated customer payment context
Over time
See How the Payment Position Changes Over Time.
Receivables are not static. A single obligation moves through several states, and the position means something different at each one.
Illustrative sequence for one obligation. Day 0: invoice raised for $10,000. Day 10: $6,000 collected. The outstanding position becomes $4,000. At the due date, $4,000 is due. If unresolved, $4,000 becomes overdue and is surfaced for attention. Separately, a future recurring payment of $5,000 is expected on 15 November.
Forward layer
Expected future payment · 15 Nov · $5,000
Running alongside all of the above, the same customer has an expected recurring payment. Receivables and the forward view describe the same relationship at different points in time.
Customer level
See the Customer Relationship Behind the Receivable.
Choose a customer. The position and the context behind it update together — which is the whole point.
Acme Industries
ILLUSTRATIVE
Current payment position
Payment context
Finance should not have to choose between a customer view and a payment view. Bonza connects the two.
Payment Command Center
Turn Receivables Visibility Into an Operating View.
Collected$312K
Outstanding$185K
Due$52K
Overdue$18K
Upcoming$115K
Receivables by status
Illustrative. Collected $312,400; outstanding $185,200; due $52,300; overdue $18,400.
Customer receivables
| Customer | Outstanding | Overdue | Upcoming | Status |
|---|---|---|---|---|
| Acme Industries | $4,000 | — | $5,000 | Due |
| Northstar Logistics | $8,500 | $8,500 | $9,200 | Overdue |
| Global Corp | $4,250 | — | $4,250 | Upcoming |
| Harbourview Trust | $6,750 | — | — | Due |
Needs attention
$18,400 overdue across 9 payments.Past their due date.
3 payment methods approach expiry.Before a relevant upcoming payment.
Upcoming recurring payment activity.Known future events in the next period.
Overdue payment activity increased.Payment insight, for review.
Payment forecast
Illustrative expected payment activity: current period $128,600; next period $141,200; following period $118,300.
Read together, the panels answer the four questions a finance leader actually asks: where do we stand, what changed, what comes next, and what needs attention. Filters shown here are illustrative. [Confirm which filter controls your implementation exposes before launch.]
AI payment insights
Don't Make Finance Search Every Number for What Changed.
Payment + receivables dataWhat already existsActivity managed inside Salesforce.
Change / patternSomething movedA shift a person would have to hunt for.
AI insight“Overdue payment activity increased.”Named in words, with context attached.
Human reviewA person decidesThe insight ends at review.
“Overdue payment activity increased.”
“Several upcoming payments have relevant payment methods approaching expiry.”
“Expected payment activity is higher in the next period.”
Bonza AI does not predict whether a customer will pay, produce default scores, or take collection decisions. It surfaces what changed so the team does not have to read every number to find it.
Payment method expiry
Some Receivables Problems Begin Before the Payment Is Due.
CustomerAcme IndustriesIllustrative record.
Payment methodExpires 31 OctRecorded expiry on the method held.
Upcoming paymentExpected 15 NovA payment that falls after the expiry.
AttentionReviewUseful context when looking at future payment activity.
Payment-method expiry is not itself a receivable. It is context that makes a forward view more useful. Bonza does not say the future payment will fail, and it does not update payment methods.
Payment setup
Keep the Payment Picture Connected Across Configured Gateways.
Configured gateways
Where payment processing happens.
Gateway A Configured
Gateway B Configured
Gateway C Configured
Bonza in Salesforce
One payment lifecycle
Relevant payment activity stays connected regardless of which gateway processed it.
Receivables context
One picture, not three
Gateway context can help teams understand how payment activity was processed.
Being precise about what this is not: Bonza does not perform settlement reconciliation, cross-gateway accounting reconciliation, smart routing, automatic failover or automatic optimisation, and gateways do not all offer identical capabilities.
Customer payment experience
Visibility for Finance Should Connect to Clarity for the Customer.
Business view
What the team needs to know
- Outstanding
- Due
- Payment context
Customer view
What the customer needs to know
- “What am I paying?”
- “How much?”
- “What options are available?”
- “What happens after payment?”
Receivables visibility helps the business understand what remains outstanding. The customer payment experience connects the customer to the relevant payment journey. These are two sides of the same payment relationship, and Bonza sits between them.
Being precise
Receivables Visibility Is Not the Same as Replacing Your Accounting System.
Bonza receivables visibility
What this page describes
- Customer payment obligations
- Payment activity
- Outstanding amounts
- Due and overdue status
- Upcoming payment context
- Customer payment history
- Relevant refunds and credits
- Payment operations visibility
Accounting / ERP
What stays where it is
- General ledger
- Journal entries
- Revenue recognition
- Tax accounting
- Financial statements
- Bank reconciliation
- Accounting close
Bonza is designed to make the customer payment lifecycle more visible and manageable in Salesforce.
Signature view
Understand the Past, Present and Future of Customer Payments.
Three zones, one relationship. Choose a zone to see what it holds and which capability answers it.
Receivables visibility is not only a backward-looking report.
A view that shows what happened, without what is open or what is expected, describes a payment operation that has already moved on.
Common mistakes
Four Mistakes That Make Receivables Harder to Understand.
Looking only at the outstanding total
A single number does not explain timing or customer context. It tells you the size of the position and nothing about what to do with it.
BetterSeparate outstanding, due, overdue and upcoming activity.
Treating gateway data as the receivables view
A gateway shows payment-processing activity, but may not carry the Salesforce customer and payment context that makes the activity meaningful.
BetterConnect processing activity with the wider payment lifecycle.
Using spreadsheets as the connection layer
Finance manually combines customer, invoice and payment information — which works, until the assembly has to be repeated every time someone asks.
BetterKeep relevant payment context connected.
Looking only backward
Finance knows what happened but not what is expected next, which makes every forward question a separate exercise.
BetterCombine current receivables with relevant forecasting and recurring-payment context.
Where you are today
How Mature Is Your Receivables Visibility?
Educational framing, not a score. Not every business needs to sit at the last level.
Fragmented
- Payment data across systems
- Spreadsheet consolidation
- Manual customer lookup
Visible
- Outstanding amounts visible
- Due and overdue status available
Connected
- Customer context
- Invoices
- Payment history
- Recurring activity
- Refunds and credits
- Gateway context
Forward-looking
- Payment Forecasting
- Payment Method Expiry
- AI Payment Insights
- Payment Command Center
Use cases
Where Better Receivables Visibility Changes the Finance Conversation.
CFO / finance leader
SituationLeadership needs to understand the payment position.
ProblemThe answer requires multiple reports or spreadsheets.
BonzaConnect relevant collected, outstanding, due, overdue and upcoming payment context.
OutcomeA clearer operational payment picture.
AR team
SituationThe team needs to know what remains unresolved.
ProblemOutstanding payment records are mixed with other payment activity.
BonzaSurface receivables and timing context.
OutcomeClearer attention.
Recurring payment business
SituationCustomers make repeated payments.
ProblemFinance needs both current receivables and future payment context.
BonzaConnect recurring payment activity with receivables and forecasting.
OutcomeBetter lifecycle visibility.
Multi-gateway business
SituationPayment activity can occur through more than one configured gateway.
ProblemGateway-specific views can fragment the payment picture.
BonzaKeep relevant payment activity connected with Salesforce payment context.
OutcomeMore consistent operational visibility.
Customer with a refund or credit
SituationPrevious payment value changed after collection.
ProblemThe current relationship can be misunderstood without post-payment context.
BonzaKeep relevant refund and customer-credit information connected.
OutcomeClearer customer payment context.
Business outcomes
What a Connected Payment Picture Actually Changes.
These are visibility outcomes. Bonza does not claim reduced DSO, a percentage improvement in working capital, higher collection rates, reduced bad debt, specific time savings, faster cash conversion, a specific return on investment or guaranteed forecast accuracy.
Understand collected, outstanding, due and overdue payment activity.
Reduce the need to piece together payment context across disconnected tools.
Connect payment activity with the relevant Salesforce customer.
See relevant expected payment activity alongside current receivables.
Surface payment states and relevant insights that may require review.
Keep refunds and customer credits connected with the wider payment story.
Keep relevant payment activity connected across configured gateway options.
Give finance a more complete payment picture when deciding where attention is required.
Why Bonza
See Receivables as Part of the Entire Payment Lifecycle.
Keep customer and payment context connected inside Salesforce, where the customer record already lives.
Connect collected, due, overdue and upcoming payment activity rather than reporting a single figure.
Bring invoices, recurring payments, refunds and credits into the wider payment story.
Connect current receivables with relevant Payment Forecasting, so the view does not stop at today.
Support payment operations across multiple configured gateways without making any one gateway the payment-management layer.
Use AI Payment Insights and the Payment Command Center to surface what changed and what may need review.
Questions
Receivables Visibility, Answered.
What is receivables visibility?
Receivables visibility is the ability to understand what customer payment value has been collected, what remains outstanding, what is due or overdue and what relevant payment activity is expected next. It is operational visibility into the customer payment lifecycle, not accounting.
How can I improve accounts receivable visibility in Salesforce?
Largely by removing the assembly step. When the customer, the invoice, the payment activity, the recurring schedule, the refund and the credit all sit in one lifecycle inside Salesforce, the position can be read rather than reconstructed. Bonza Payments is a Salesforce-native payment management suite built around that connection.
Can Bonza show outstanding customer payments?
Yes — with the customer and the originating obligation attached, so an outstanding amount is a position in a relationship rather than a number in a report.
Can Bonza show which payments are due and overdue?
Yes. Outstanding is separated by timing into upcoming, due and overdue, because those three states call for different responses even though the amounts look identical.
Can Bonza show upcoming expected payments?
Yes. Payment Forecasting provides forward visibility into relevant expected payment activity by period, presented alongside the current receivables position. Expected activity is not guaranteed cash.
What is the difference between receivables and payment forecasting?
They answer different questions. Receivables focus on unresolved customer payment obligations — what is still outstanding today. Payment forecasting provides forward visibility into relevant payment activity expected in future periods. An outstanding receivable is not automatically a forecasted collection.
How do recurring payments affect receivables visibility?
A recurring arrangement produces both history and forward context. An unresolved cycle belongs in the outstanding position; the cycles ahead belong in the forward view. Treating each cycle as an unrelated transaction loses the relationship they share.
Can Bonza connect invoices with payment activity?
Yes. Invoice context connects what the customer was expected to pay with the payment activity that followed and what remains outstanding — which is what makes an outstanding amount explainable.
Can Bonza show refunds and customer credits in the payment lifecycle?
Yes. A payment relationship does not always end at collection, and both can change how the customer's position should be read. Customer credit is recorded and managed within Bonza Payments; it is not a wallet, a cash balance, stored funds or a bank balance, and none of it adjusts an accounting ledger.
Can Bonza work with multiple payment gateways?
Yes. Relevant payment activity stays connected to the Salesforce payment lifecycle regardless of which configured gateway processed it, so the picture does not fragment by provider. Bonza does not perform settlement reconciliation, cross-gateway accounting reconciliation, smart routing, automatic failover or automatic optimisation.
Does Bonza replace my accounting or ERP system?
No. Bonza is a Salesforce-native payment management suite. General ledger, journal entries, revenue recognition, tax accounting, financial statements, bank reconciliation and the accounting close all stay with your accounting or ERP platform.
Can AI help identify receivables that need attention?
AI Payment Insights can surface relevant changes and patterns — for example that overdue payment activity has increased — and attach the context behind them. It does not score customers, predict whether a customer will pay, or make collection decisions.
What does the Bonza Payment Command Center show?
It brings the pieces into one operating view: receivables by status, customer-level receivables, what needs attention and the payment forecast. Read together they answer where you stand, what changed, what comes next and what needs attention.
Does Bonza automatically reconcile bank transactions?
No. There is no bank reconciliation, bank-feed reconciliation, automatic cash application or automatic invoice matching. Bonza provides payment and receivables visibility within the Salesforce payment lifecycle.
Stop Reconstructing Your Receivables. Start Seeing the Payment Picture.
See how Bonza Payments connects receivables, due and overdue payments, forecasting, recurring activity and customer payment context inside Salesforce.