Know What's Been Paid. What's Still Owed. And What's Coming Next.

It is managing the customer payment lifecycle in the same environment as the customer relationship. Bonza Payments is Salesforce-native, so relevant one-time and recurring payments, invoices, receivables, due and overdue activity, refunds, customer credits and upcoming payment visibility stay associated with the Salesforce customer or account record rather than living in a gateway portal, a recurring-payment process and a spreadsheet separately.

Yes, where relevant customer payments repeat on a schedule. Bonza manages the schedule, the payment, its status and the next expected payment, with each one connected to Salesforce. It should not be read as rent management, lease billing, lease renewal, subscription billing or automatic rent collection, none of which Bonza provides.

Yes, and that combination is common. A relevant one-time or ad hoc payment and a recurring arrangement can run on the same customer, with both visible in one payment position. An amount from one motion can be overdue while the other keeps collecting on time, and both facts stay visible in the same place.

Yes, and it treats them as three different operational states rather than one unpaid figure. Outstanding means still expected, due means expected now, and overdue means past the expected date. The amount does not change between them — the date does, and that timing is what tells a team where to look first.

Yes. Payment forecasting in Bonza focuses on relevant upcoming, scheduled and recurring customer payment activity. This is payment-operations forecasting: it is not property revenue forecasting, occupancy forecasting, rental income forecasting, treasury forecasting, bank balance forecasting, cash-flow forecasting, investment forecasting or property valuation forecasting. Expected payment activity is not guaranteed collection.

Payment forecasting covers expected customer payment activity — which payments are upcoming, scheduled or recurring, and when. Cash-flow forecasting is a treasury and finance-planning exercise covering all inflows and outflows against bank positions. Bonza does the first and makes no claim about the second, and treating one as the other leaves neither trusted.

Yes, as timing context. Where a payment method expires before a future expected payment, that ordering can be surfaced so a person can look at it before the date arrives. It does not say the payment will fail, and there is no automatic card updater, automatic customer outreach, automatic remediation or automatic replacement.

Yes. A refund stays attached to the payment it came from, so the collected figure remains explainable rather than simply lower. Customer credit is recorded and managed within Bonza Payments and is available for relevant future payment use where supported. It is not a tenant wallet, a property wallet, a cash balance, stored funds, escrow or a deposit account, and Bonza does not hold customer money.

Yes. Bonza provides a Salesforce-native payment-management layer above configured payment gateways, with a configured default and selection of another configured gateway where appropriate. There is no smart routing, least-cost routing, automatic failover, cascading, automatic retries across gateways, success-rate routing, gateway optimisation, unified settlement or token portability, and provider capabilities are not interchangeable.

Where a property organization already uses Experience Cloud for customer interactions, relevant payment journeys can stay connected within that Salesforce environment, with payment activity flowing back to Salesforce payment context. Bonza does not provide property portal management, tenant or resident portal software, an owner portal, lease documents, maintenance requests, property search, authentication or document management.

No. Bonza focuses on Salesforce-native payment management rather than property, unit, lease, maintenance or facilities management. Properties, units, leases, occupancy, inspections, owners, tenants, facilities and property operations stay with the property-management system, and Bonza does not claim any of them.

No to both. Bonza manages the customer payment lifecycle, not the general ledger or the accounting close, and it is not an ERP, a property-accounting system, a revenue-recognition system, a tax system, a bank, a lender or an escrow platform. It also does not collect overdue payments on its own: it provides relevant payment visibility and operational context, with no automated dunning, autonomous collections, customer chasing, late-fee calculation, legal escalation or eviction workflow.