See What's Coming Before the Payment Date Arrives.

Upcoming payment forecasting provides forward visibility into customer payment activity expected over a future period. It answers "what is expected next?" rather than "what happened?" — and it covers expected payment events, not guaranteed cash receipts.

Bonza Payments helps businesses see relevant upcoming, scheduled and recurring customer payment activity inside Salesforce. The forward view is built from payment activity you already manage — recurring payment schedules, relevant upcoming payment activity and the customer and payment context attached to them — arranged by time rather than by record.

Yes, where the implementation supports the relevant inputs. Expected payment activity can be viewed across near-term and later horizons with the customer, amount, expected date and payment context alongside it, so a total can be understood rather than just read.

Recurring payment schedules can contribute to future payment visibility because they represent known upcoming payment events. Scheduled activity should not be treated as guaranteed collection — a schedule tells you when a payment event is expected, not what its outcome will be.

Receivables and payment forecasting answer different questions. Receivables show unresolved payment obligations — what you are still waiting to collect. Forecasting shows relevant payment activity expected in future periods. An outstanding payment is not automatically the same thing as a forecasted payment event, and keeping them separate is what makes both useful.

No. Bonza is positioned around payment-operations forecasting, not complete treasury, bank-balance or corporate cash-flow forecasting. It does not include bank balances, vendor payments, payroll, taxes, financing, investments, expenses, liquidity or treasury planning, and it offers no scenario modelling or what-if planning.

No. Forecasted payment activity represents expected or scheduled payment activity. Actual collection depends on what happens at the relevant payment event. This page uses "expected", "scheduled" and "forecasted" deliberately, and never "certain", "guaranteed" or "committed cash".

Yes. Expected payment activity stays connected to the customer and payment context behind it, so finance can see which relationships sit underneath an aggregate figure rather than only the total. Customer-level current position and forward position are shown separately, on purpose.

Payment Method Expiry can add useful context when a relevant payment method approaches expiry before an upcoming expected payment. The value is early visibility. It is not a prediction that the payment will fail, and Bonza does not claim automatic card updating, automatic customer outreach or automatic remediation.

Where supported, AI payment insights can interpret a change in the forward view — for example, that expected recurring payment activity is higher next month — and present the relevant customer, amount and timing context for a person to review. AI does not guarantee payment outcomes, score customers, predict defaults, assign payment probabilities, change the forecast on its own or contact anyone.

No. This page makes no forecast-accuracy claims and there are no confidence scores, probability weightings, customer payment probabilities or default predictions. A forecast here is a structured view of expected payment activity, not a statistical model of it.

Yes. Upcoming activity can be read in the Payment Command Center alongside collected, outstanding, due and overdue, with relevant attention signals in the same view. The forward view is one column of the operation, not a separate application.

Expected payment activity connected to different configured gateways can be read within the same broader Salesforce payment-management environment. Gateway configuration determines how a payment is processed; it does not need to split the forward view into separate reports. Capabilities vary by provider and configuration.

Relevant upcoming payment activity can contribute to the forward view where the implementation supports it as a forecast input. Not every payment record is automatically a forecast input — which inputs are included is a configuration decision rather than an assumption. [Confirm supported forecast inputs before launch.]

Due describes a payment obligation that has reached its date. Overdue describes one that has passed it without being resolved. Upcoming describes expected payment activity that has not reached its date yet. They sit at three different points on the same timeline, and a useful payment operation can see all three at once.