What happened?
Completed payment activity you can report on.
- Collected payments
- Recent payment activity
- Refunds
- Relevant completed transactions
Payment forecasting
Turn upcoming, scheduled and recurring payment activity into a forward-looking Salesforce view so your team can understand what collections are expected next.
Part of the Salesforce-native Bonza Payments suiteIllustrative figures. September: $312,400 collected. October: $128,600 expected. November: $141,200 expected. December: $118,300 expected. Today falls between September and October, so September is a collected total and the three later months are expected payment activity rather than collected amounts.
| Customer | Expected amount | Expected date | Payment context | Status |
|---|---|---|---|---|
| Acme Corporation | $5,000 | 05 Oct | Recurring payment | Scheduled |
| Northstar Logistics | $8,500 | 08 Oct | Invoice payment | Upcoming |
| Global Corp | $4,250 | 12 Oct | Recurring payment | Scheduled |
| Lakeside Group | $2,900 | 18 Oct | Upcoming payment | Upcoming |
Illustrative product interface. Every customer name, amount and date shown on this page is a sample used to explain the concept — none of it is real customer data, and expected amounts are not collected amounts.
Definition
Payment forecasting provides forward-looking visibility into payment activity expected over a future period.
Bonza Payments helps businesses view relevant upcoming, scheduled and recurring payment activity within Salesforce so finance and operations teams can better understand what collections are expected next.
Bonza Payment Forecasting is designed for payment operations. It is not a treasury, liquidity or corporate cash-flow forecasting platform, and it does not model bank balances, payroll, expenses, vendor payments or tax obligations.
The real problem
Finance teams also need to understand what's coming next.
Those questions matter. They describe what has happened and where the payment operation stands today.
Reporting and forecasting
“What happened?”
“What is expected next?”
Both perspectives matter, and one does not replace the other. Reporting helps teams understand completed and current payment activity. Forecasting adds a future time horizon to the same payment information.
Signature model
The same payment operation reads differently depending on where you stand in time. Each horizon answers a different question.
Completed payment activity you can report on.
The current position, as it stands today.
Forward payment visibility over an upcoming period.
Payment Forecasting sits primarily on the future horizon. The Payment Command Center spans all three, placing the forward view beside what has happened and what is open. Accounts receivable visibility and due and overdue payments describe the present position in their own right.
How the forward view is built
Not every outstanding receivable automatically belongs in a forward view — an amount that is owed does not always have a known future payment date. Only relevant forecast inputs supported by your implementation contribute to the forecast. [Confirm the exact forecast inputs available in your Bonza implementation before launch.]
Core solution
See relevant payment activity expected over upcoming periods, in the same place you manage the payments themselves.
Why it mattersTeams gain a forward view instead of relying only on historical payment reporting.
Understand when relevant future payments are expected, not only how much is expected in total.
Why it mattersTiming changes the operational meaning of expected payment activity.
Bring scheduled recurring payments into the relevant forward payment picture.
Why it mattersRecurring payment arrangements create known future payment events that can contribute to forward visibility.
Connect relevant expected payment activity with the record it belongs to.
Why it mattersA forecast total is more useful when users can understand what sits behind it.
Where supported, connect relevant future payment activity with signals such as a payment method approaching expiry, outstanding payment context, or a relevant AI payment insight.
Why it mattersA future payment is more useful operationally when the team can see whether something may deserve review.
The horizon
Move along the horizon to see what sits in each window. Every amount and date is illustrative.
Behind the number
A single large number is hard to act on. A useful payment forecast lets the team understand the payment activity the aggregate view represents.
Scheduled recurring payment events falling in the period.
Expected payments with a relevant future payment date. [Confirm which invoice and receivable records qualify as forecast inputs in your implementation.]
Remaining supported upcoming payment activity in the period.
| Customer | Amount | Expected date | Payment context |
|---|---|---|---|
| Acme Corporation | $5,000 | 05 Oct | Recurring payment |
| Northstar Logistics | $8,500 | 08 Oct | Invoice payment |
| Global Corp | $4,250 | 12 Oct | Recurring payment |
| Lakeside Group | $2,900 | 18 Oct | Upcoming payment |
| Harbourview Trust | $6,750 | 22 Oct | Invoice payment |
The point is structure, not a single headline figure: a period total, the payment types that make it up, and the customer records underneath. Whether a user moves between those levels by clicking depends on how your implementation is configured. [Confirm available navigation between forecast summary and detail before launch.]
Recurring payments
Recurring payment schedules can provide visibility into payment activity expected in future periods, because the dates and amounts are already known. A scheduled payment is expected activity: whether it collects depends on what happens when the payment event occurs.
Receivables
The two views answer different questions. Receivables show the current outstanding position. Payment Forecasting shows relevant payment activity expected in future periods. An outstanding receivable is not automatically the same as a forecasted collection, and not every receivable has a known future collection date.
Due & overdue
Illustrative time axis. To the left of today: $18,400 overdue. At today: $52,300 due. To the right of today: $125,000 expected over the upcoming period.
Due & Overdue Payments helps teams understand payment obligations that require attention now or from the past. Payment Forecasting adds the future view. Together they help finance teams understand payment activity across time rather than at a single point in it.
Payment method expiry
A forward view makes one particular kind of problem visible early: the payment method attached to an upcoming payment may be recorded as expiring first.
The value here is early visibility, and only that. Bonza does not update the payment method, obtain replacement details, contact the customer, or predict that the payment will fail — it surfaces the timing so a person can decide what to do next.
AI payment insights
The two capabilities stay distinct. The forecast presents expected payment activity by period. An insight points at a relevant change or pattern within it, for a person to review.
Bonza AI does not predict payment success, score customers, or state that an expected payment will or will not collect. It interprets relevant payment context so the team knows where to look first.
Payment Command Center
| Period | Expected payment activity | Of which recurring |
|---|---|---|
| Current month | $128,600 | $51,200 |
| Next month | $141,200 | $58,900 |
| Following month | $118,300 | $54,400 |
| Customer | Amount | Expected date | Context |
|---|---|---|---|
| Acme Corporation | $5,000 | 05 Oct | Recurring payment |
| Northstar Logistics | $8,500 | 08 Oct | Invoice payment |
| Global Corp | $4,250 | 12 Oct | Recurring payment |
The payment forecast provides the forward-looking view. The Payment Command Center connects that forecast with the wider payment operation — what has been collected, what is outstanding, what is due, what is overdue — so the future view is read in context rather than on its own.
Expected, not guaranteed
This distinction matters more than any headline number on the page.
A recurring schedule or a relevant expected payment date creates a known future payment event.
That event contributes to forward payment visibility for the relevant period.
On the expected date, the payment is actually attempted or made.
The outcome is recorded — and it is only known at this point, not before.
A scheduled or expected payment can contribute to forward payment visibility, and that visibility is genuinely useful for planning and prioritisation.
The actual payment outcome depends on what happens when the payment event occurs. Bonza does not promise collection, guarantee cash flow, attach a collection probability, or model confidence intervals.
Forecast workspace
Change the horizon to see how expected activity is distributed. Short horizons explain immediate activity; longer ones show how scheduled activity changes over time.
| Customer | Amount | Expected date | Type | Status |
|---|
Period options shown here reflect fixed horizons. [Confirm which forecast periods your implementation exposes before launch — custom date ranges are not claimed on this page.]
Customer level
Payment forecasting should not exist only as an aggregate chart. Where supported, the relevant future payment activity stays connected with the customer relationship it belongs to.
Read side by side, the two columns tell a story a total never would: this customer has an upcoming recurring payment expected on 15 Nov, and the payment method on file is recorded as expiring on 30 Oct. That is a reason to review the relationship — not a statement about what the payment will do.
Payment setup
Bonza's multiple payment gateways environment can remain connected with the wider payment-management lifecycle, so the forward view does not fragment by gateway. This page is about payment forecasting, not gateway forecasting: no settlement forecasting, gateway liquidity forecasting, per-gateway accuracy, routing, success prediction or fee optimisation is claimed here.
Use cases
Connected suite
Payment Forecasting is not an isolated chart. It is one forward-looking perspective across the wider Bonza payment lifecycle.
Connected where relevant to invoices, due and overdue payments, payment method expiry visibility and Salesforce customer context.
Business outcomes
These are visibility and decision-support outcomes. Bonza does not claim guaranteed cash-flow improvement, better working capital, reduced DSO, higher collections, revenue growth, forecast accuracy percentages, reduced payment failure or a specific return on investment.
See relevant expected payment activity before the payment date.
Give finance and operations teams a clearer view of upcoming payment activity.
Understand relevant scheduled recurring collections across future periods.
Connect what happened, what is open and what is expected.
Surface relevant future payment relationships that may require review.
Keep relevant expected payment activity tied to Salesforce customer and payment information.
Give teams more context when deciding where to focus operational attention.
Why Bonza
Keep relevant forecast information connected with Salesforce customer and payment context, in the system your team already works in.
Connect forward visibility with receivables, recurring payments and other relevant payment activity rather than exporting it into a separate tool.
Bring scheduled recurring payment activity into the relevant future payment picture, where the dates and amounts are already known.
Understand the relevant customer and payment relationships behind expected payment activity, not only the aggregate total.
Connect relevant future payment activity with payment-method expiry visibility where supported, so timing problems appear early.
Bring forecasting into the wider Payment Command Center and AI Payment Insights experience instead of leaving it as a standalone chart.
Questions
Payment forecasting provides forward-looking visibility into payment activity expected over a future period. Instead of only reporting what was collected and what remains outstanding, it presents relevant upcoming, scheduled and recurring payment activity so a team can understand what collections are expected next.
Because Bonza Payments is Salesforce-native, the payment activity it manages already lives beside your customer records. Relevant future payment context — recurring schedules, upcoming payment activity and expected payment dates — is presented as a forward view organised by period, alongside the customer, amount and payment type each expected payment belongs to.
Relevant expected payment activity over upcoming periods, the timing of that activity, the recurring payment events contributing to it, and the customer and payment context behind each expected payment. Where supported it can also surface attention items such as a payment method approaching expiry before a relevant upcoming payment.
Yes. Upcoming expected payment activity is the core of this capability, presented with the customer, expected amount, expected date and payment context rather than as a single total.
Yes. Recurring payment schedules create known future payment events, which makes them a natural contributor to forward payment visibility. Those events are shown as scheduled and expected activity, never as guaranteed collection.
Receivables answer “what remains outstanding?” — the current position. Payment Forecasting answers “what payment activity is expected over the upcoming period?” — the forward view. An outstanding receivable is not automatically a forecasted collection, and not every receivable has a known future payment date.
The Payment Command Center brings together the wider payment operation across past, present and future. Payment Forecasting provides the forward-looking view of relevant expected payment activity, which the Command Center can then place beside collected, outstanding, due and overdue information.
Forecasting presents expected payment activity by period. AI Payment Insights interprets relevant patterns and changes within your payment information and prioritises what may deserve attention. Forecasting shows what is expected; insights help surface what is changing. Neither decides or acts on its own.
Where supported, yes — and that timing relationship is one of the more useful things a forward view makes visible. Bonza surfaces the expiry date alongside the relevant upcoming payment date so a person can review the relationship. It does not update the payment method, obtain replacement details, contact the customer or predict that the payment will fail.
No. A payment forecast represents expected payment activity. The actual payment outcome depends on what occurs when the relevant payment event takes place.
No. Bonza's positioning here is payment-operations forecasting: forward visibility into relevant expected payment activity. It should not be presented as a complete treasury, liquidity or corporate cash-flow forecasting platform, and it does not model bank balances, payroll, expenses, vendor payments, tax obligations or investment activity.
Yes. Because the forecast is built from payment activity managed inside Salesforce, relevant expected payment activity stays connected to the customer and payment information that gives it meaning — which is what makes a customer-level forward view possible rather than only an aggregate chart.
The forward view is built from payment activity rather than from gateway behaviour, so it does not fragment by gateway across a configured multi-gateway setup. Bonza does not claim gateway-level forecast accuracy, settlement forecasting, gateway liquidity forecasting, automatic routing, gateway success prediction or fee optimisation.
See how Bonza Payment Forecasting brings upcoming, scheduled and recurring payment activity into a forward-looking Salesforce view.