Give Finance One Connected View From Amount Due to Payment Collected.

It is managing unresolved customer payment obligations — what has been collected, what remains outstanding, what is due, what is overdue and what is expected next — inside the same environment as the customer relationship. Bonza Payments gives finance and accounts receivable teams a Salesforce-native view of that activity rather than requiring it to be reconstructed from separate systems.

By connecting the payment lifecycle around the customer: collections, receivables, due and overdue obligations, recurring payments, refunds, customer credits, upcoming payment activity and relevant attention signals. The aim is that answering "has this customer paid, what is still open, and what is coming next" takes one view rather than several systems and a spreadsheet.

Yes. Those are distinct states, and separating them is what turns an amount into a priority. Outstanding means unresolved; due means the date has been reached; overdue means it has passed without resolution. The Payment Command Center reads them together alongside upcoming activity.

Yes, where the implementation supports the relevant inputs. Upcoming activity is expected or scheduled payment activity, not collected payment — a schedule tells you when a payment event is expected, not what its outcome will be.

Yes. Recurring payment relationships create both historical and future payment context, and both can sit in the same finance view as the receivables position — the last payment, the current one and the next relevant payment read against the same customer.

Where supported, yes — and the useful part is seeing the expiry date next to the relevant upcoming payment date. That is early visibility, not a prediction that the payment will fail, and Bonza does not claim automatic card updating, automatic customer outreach or automatic remediation.

Yes. Refund and customer-credit activity stays part of the wider customer payment lifecycle rather than becoming a separate record set. Customer credit is customer value recorded and managed within Bonza Payments — not a wallet, a cash balance or stored funds — and it is not applied automatically.

Yes. Bonza supports multiple configured payment gateways while keeping relevant payment activity connected to the wider Salesforce payment lifecycle. Gateway selection is explicit; there is no smart routing, automatic failover or automatic gateway optimisation, and gateway capabilities vary by provider and configuration.

Yes — payment activity from different configured providers can be read together in one operational view, with the gateway recorded against each payment. This is operational visibility, not settlement or bank reconciliation.

No. Bonza is positioned around Salesforce-native payment management and operational customer payment visibility rather than general ledger, accounting or ERP replacement. It does not perform journal entries, tax accounting, revenue recognition, financial statements or the accounting close.

No. Bank reconciliation and settlement reconciliation are not claimed capabilities. Reading payments from several providers together in one operational view is a different thing from reconciling them against a bank statement or a ledger, and those remain with your providers and your finance platform.

No. Automated dunning, autonomous collections, automatic collection emails or SMS, promise-to-pay management, automated late fees and automatic debt escalation are not claimed capabilities. Bonza surfaces what needs attention; the decision and the action belong to a person on the finance team.

AI payment insights interpret changes in the payment picture — for example that several payments moved into overdue status, that payment methods are approaching expiry before relevant upcoming payments, or that expected recurring activity increased next month — and present them with the relevant customer, amount and timing context for review. AI does not contact customers, choose collection actions, predict default, issue refunds, create credits or make financial decisions.

No. There is no credit scoring, default prediction, collection probability or customer risk rating anywhere in Bonza. Attention signals describe what is factually true about a payment — that it is overdue, or that a payment method expires before the next expected payment — not a judgement about a customer.

Collected, outstanding, due, overdue and upcoming payment activity together, alongside refunds, customer credits, the receivables position, upcoming payments and relevant attention signals. It exists to answer four questions quickly: what happened, what is open, what is next, and what needs attention.

Yes. Finance sees the payment obligation and the customer sees the action they need to take; both belong to the same payment relationship. Where supported, customer-facing payment activity stays connected to the Salesforce customer record and the wider payment lifecycle that finance reads.