- Due
- 28 Aug
- Context
- 27 days outstanding
Payment Command Center
See Your Entire Payment Operation at a Glance.
Bring collections, receivables, due and overdue payments, recurring activity, refunds, credits, upcoming payments and payment insights into one Salesforce-native operational view.
Part of the Salesforce-native Bonza Payments suiteLEVEL 1 · EXECUTIVE SUMMARY
LEVEL 2 · FORWARD VIEW
Expected collections, illustrative: this month $1.21M, next month $1.38M, following month $1.05M.
LEVEL 3 · ATTENTION
| Customer | Amount | Due date | Status | Payment context |
|---|---|---|---|---|
| Brightpath Logistics | $9,450 | 28 Aug | Overdue | Invoice · 27 days outstanding |
| Northstar Industries | $2,800 | 06 Sep | Overdue | Invoice · 18 days outstanding |
| Acme Corporation | $4,500 | Today | Due | Invoice · card •••• 4242 |
| Lumen Health Partners | $1,980 | Today | Due | Recurring · UPI |
| Crestline Realty | $3,120 | 27 Sep | Due soon | Invoice · in 3 days |
| Northwind Traders | $2,400 | 01 Oct | Upcoming | Recurring · method expiring soon |
- Due
- 06 Sep
- Context
- 18 days outstanding
- Due
- Today
- Context
- Invoice · card •••• 4242
- Due
- Today
- Context
- Recurring · UPI
- Due
- 27 Sep
- Context
- In 3 days
- Due
- 01 Oct
- Context
- Method expiring soon
No illustrative payments in that state.
LEVEL 4 · ACTIVITY · LEVEL 5 · DETAIL
No illustrative activity of that type today.
Every number here belongs to a customer. Select a row in the attention table to see that customer's payment context.
Interface shown is an illustrative representation of the Bonza Payment Command Center inside Salesforce. Every value, customer and insight is a sample. The filters above demonstrate how the views relate — [confirm the supported filter, drill-down and KPI set before launch].
Plain definition
What Is a Payment Command Center?
A payment command center is a centralised operational view of payment activity, outstanding amounts, due and overdue obligations, upcoming collections and related payment signals.
Bonza Payments brings these views together within Salesforce so finance and operations teams can understand the wider payment lifecycle from one connected workspace — what has been collected, what remains outstanding, what is coming next and what may require attention.
It is part of the wider Bonza Payments suite, connecting operational payment visibility with customer, invoice, receivables, recurring-payment, refund and credit context inside Salesforce.
The real problem
Payment Data Is Everywhere. Operational Clarity Usually Isn't.
The issue is rarely missing data. It's that answering one simple operational question can mean opening several systems and records.
Without a command-centre view, the payment operation becomes a series of disconnected searches. The mature model runs in one direction:
Dashboard vs command centre
A Dashboard Shows Numbers. A Command Center Shows What They Mean Together.
Collected, outstanding, overdue — each metric alone tells part of the story. What makes visibility operationally useful is the connection between them.
- Payments collected
- Refunds processed
- Credits created
- Receivables
- Due payments
- Overdue payments
- Recurring payments
- Upcoming expected collections
- Payment forecasting
- Payment-method expiry
- Overdue activity
- Relevant payment insights
- The account behind every number
- The relationship behind every amount
Visibility becomes operationally useful when related payment signals are brought together.
The workspace
One Workspace Across the Payment Lifecycle.
The Command Center isn't an isolated dashboard. It's the operational surface of the wider Bonza suite.
Core capability
Know What Happened. Know What's Open. Know What's Next.
What has been collected?
Relevant collected payment activity, readable at a glance instead of assembled from individual records.
What is still outstanding?
The receivables position sits in the same view — outstanding, due, overdue and the customer obligations behind them.
What is coming next?
Upcoming recurring payments, expected collections and the payment forecast keep the view from being purely backward-looking.
What needs attention?
Overdue payments, payments due soon, payment methods approaching expiry and relevant payment insights are surfaced as attention signals rather than buried in the same list as everything else.
What changed?
A recent activity feed shows the movement of the operation — payments received, refunds processed, credits created and used, recurring activity and relevant status changes.
Three time horizons
See the Payment Operation in Three Time Horizons.
What happened?
The movement of the operation, as it occurs.- Payments collected$11.6M
- Recent payment activity6 events
- Refunds$18K
- Credits created$42K
What still needs resolution?
The position the team is working through.- Outstanding$1.84M
- Due$126K
- Overdue$298K
- Customer obligations61 payments
What is expected?
The forward view, not a guarantee.- Upcoming payments$1.21M
- Recurring collections$386K/mo
- Forecast horizon3 months
- Method expiry signals12
Insights read the same data in all three horizons — what moved today, what has been open too long, what is approaching — and surface what deserves review. Bonza connects the past, present and near future of the payment operation; the team decides what to do about it.
Illustrative values throughout. This is operational payment visibility — not accounting, general ledger, treasury, cash management or business-intelligence reporting.
Attention
See What Requires Attention Without Opening Every Customer Record.
The attention panel is the part of the Command Center a finance team actually works from — filtered by timing, with the payment context attached.
| Customer | Amount | Status |
|---|---|---|
| Brightpath Logistics | $9,450 | Overdue |
| Acme Corporation | $4,500 | Due today |
| Crestline Realty | $3,120 | Due soon |
| Northwind Traders | $2,400 | Method expiring |
No risk scores, and no customers labelled high risk, low risk or likely to default — timing and status only.
| Customer | Outstanding | Overdue | Upcoming |
|---|---|---|---|
| Acme Corporation | $5,740 | $1,240 | $3,440 |
| Brightpath Logistics | $9,450 | $9,450 | $0 |
| Crestline Realty | $3,120 | $0 | $3,120 |
Receivables become more actionable when read alongside payment activity and upcoming collections.
The forward view
Look Beyond What Has Already Happened.
Expected collections across the current month and the two that follow, with recurring activity broken out where it helps.
| Period | Recurring | Upcoming | Expected total |
|---|---|---|---|
| This month | $386K | $824K | $1.21M |
| Next month | $412K | $968K | $1.38M |
| Following month | $394K | $656K | $1.05M |
Expected and scheduled payment activity — not guaranteed cash flow, probability-based forecasting, confidence scores or an accounting cash forecast.
| Customer | Amount | Frequency | Next | Method |
|---|---|---|---|---|
| Lumen Health Partners | $1,980 | Monthly | 01 Oct | UPI |
| Northwind Traders | $2,400 | Monthly | 01 Oct | Method expires first |
| Ridgeway Studios | $860 | Monthly | 05 Oct | Card •••• 3007 |
Where a payment method expires before the next collection, that is surfaced for review. Bonza does not remediate it automatically.
Signals, post-payment and gateways
Don't Stop Watching the Lifecycle After Collection.
| Customer | Payment method | Expiry | Next relevant payment | Attention |
|---|---|---|---|---|
| Acme Corporation | Card •••• 4242 | Oct | 15 Oct | Expiring soon |
| Northwind Traders | Card •••• 1188 | Sep | 01 Oct | Expiring soon |
Early awareness that a future payment relationship may need attention. This does not say a payment will fail, and Bonza neither updates payment methods nor contacts customers automatically. Expiry visibility depends on what the configured gateway exposes.
The Command Center includes what happens after payment, not only what happened during collection.
| Customer | Amount | Gateway | Status |
|---|---|---|---|
| Acme Corporation | $1,200 | Stripe | Paid |
| Northstar Industries | $850 | Razorpay | Paid |
| Global Corp | $2,100 | PayU | Processing |
Payment visibility across your configured gateway strategy — not settlement reconciliation, fee comparison, success-rate optimisation, automatic routing or uptime monitoring.
Intelligence
Surface the Signals That Deserve a Closer Look.
Intelligence in the Command Center is an insight and prioritisation layer. It reads the payment data you already have and points at what may deserve review.
Bonza intelligence does not collect payments, contact customers, change payment terms, choose gateways, issue refunds, change credit balances, predict defaults, make credit decisions or guarantee collection. Every number shown in an insight is illustrative.
From metric to customer
Every Metric Should Lead Back to a Customer Story.
An aggregate is a starting point, not an answer. “$298K overdue” only becomes useful when it resolves into the accounts behind it.
One number, 37 payments, 11 customers.
Plus recurring activity and recent payments, in the customer's own record.
This describes the information architecture — payment metrics connect to Salesforce customer context. [Confirm the supported drill-down behaviour before launch.]
Visibility matters most when it helps the team decide what to do next.
Bonza doesn't simply display data — but it doesn't act autonomously either. The Command Center connects visibility to the wider payment workflow, and a person decides.
Who uses it
One Payment Picture. Different Questions for Different Teams.
The same view, read for different purposes — not separate configurable dashboards per role.
The whole position
- “What has been collected?”
- “What remains outstanding?”
- “What is coming next?”
- “Where are payment issues emerging?”
Today's working list
- “What is due?”
- “What is overdue?”
- “Which customer needs attention?”
- “What was paid?”
What moved
- “What changed today?”
- “Are refunds or credits affecting activity?”
- “What recurring payments are coming up?”
How it connects
- “Is payment activity connected with customer records?”
- “Which payment workflows are active?”
- “How does payment fit the wider customer process?”
Connected suite
From One Dashboard Into the Entire Bonza Payment Lifecycle.
The Command Center is not another standalone feature. It's the operational front door to the wider Bonza suite.
What changes
One Place to Open Before the Day Starts.
These describe the visibility the Command Center provides. We don't claim reduced DSO, faster collections, percentage productivity gains, lower overdue balances, guaranteed cash-flow improvement, revenue growth, reduced headcount or specific time savings.
Why Bonza
A Command Center Built Around the Complete Payment Lifecycle.
Salesforce-native
Payment visibility stays connected with Salesforce customer and business context, in the environment your teams already work in.
Complete payment lifecycle
Bring together what happens before, during and after payment — not just collection metrics.
Paid / due / overdue visibility
See the core payment states from one operational view rather than three separate searches.
Forward payment visibility
Connect current payment activity with upcoming and recurring payments.
Post-payment visibility
Keep refunds and customer credits visible within the broader operation.
Payment intelligence
Surface relevant payment insights and payment-method expiry signals alongside the operational data.
FAQ
The Payment Command Center, Answered.
What is a payment command center?
A payment command center is a centralised operational view of payment activity, outstanding amounts, due and overdue obligations, upcoming collections and related payment signals — one place to understand the payment operation rather than several systems to search.
What can I see in the Bonza Payment Command Center?
Collected payment activity, outstanding receivables, due and overdue payments, upcoming and recurring collections, refunds, customer credits, payment-method expiry signals, recent payment activity and relevant payment insights — connected to Salesforce customer context.
Can the Command Center show paid, due and overdue payments?
Yes. Those core payment states sit together in one operational view, with the payment context behind each one rather than as three disconnected numbers.
Can I see outstanding receivables?
Yes. The outstanding position appears alongside collected activity and upcoming collections, and can be read by customer — receivables are more actionable when seen next to what has been paid and what is expected.
Can I see upcoming recurring payments?
Yes. Upcoming recurring collections appear in the forward view, including cases where a payment method expires before the next scheduled collection.
Can the Command Center show payment forecasts?
Yes — as expected and scheduled payment activity across the coming months, with recurring activity broken out where it helps. This is forecasted payment activity, not guaranteed cash flow, probability-based forecasting or an accounting cash forecast.
Can I see refunds and customer credits?
Yes. Post-payment activity is part of the view, so refunds and available customer credits stay visible in the wider operation instead of disappearing after collection.
Can I see which payment methods are approaching expiry?
Where the configured gateway exposes expiry information, yes. It is early awareness that a future payment relationship may need attention — not a statement that a payment will fail, and Bonza does not update methods or contact customers automatically.
Does the Command Center include AI payment insights?
Yes, as an insight and prioritisation layer. Relevant signals — payments that moved into overdue status, methods approaching expiry, changes in upcoming collections — are surfaced for review with illustrative figures.
Can I see payments from multiple payment gateways?
Yes. Payment activity across your configured gateways can be read together in Bonza rather than by opening individual gateway portals. That is payment visibility — not settlement or accounting reconciliation, fee comparison or gateway monitoring.
Is the Payment Command Center native to Salesforce?
Yes. It is part of the Salesforce-native Bonza Payments suite, which is why the payment picture stays connected to customer and business context rather than living in an external reporting tool.
Does the Command Center automatically collect overdue payments?
No. It surfaces what requires attention. Collection happens through your configured payment capabilities, initiated by your team or your customer — there is no automated dunning, chasing or recovery here.
Does AI take actions automatically?
No. The positioning is insight and prioritisation: payment signals are surfaced for review, and people decide the appropriate next action. AI does not collect payments, contact customers, change payment terms, choose gateways, issue refunds, alter credit balances or make credit decisions.
Can different teams use the Command Center?
Yes — the same payment picture answers different operational questions for finance leadership, accounts receivable, finance operations and Salesforce teams. That is different readings of one view rather than separately configurable dashboards per role.
Stop Piecing Together the Payment Picture.
See how the Bonza Payment Command Center brings collections, receivables, due and overdue payments, recurring activity, refunds, credits, upcoming payments and payment insights together inside Salesforce.