Financial & professional services
Manage one-time and recurring payment activity, receivables, refunds, customer credits, upcoming payments and configured payment gateways inside Salesforce with Bonza Payments.
Salesforce-native payment management suiteIllustrative client payment relationship for one sample client, Acme Advisory Client, whose relationship is active. The relevant payment obligation is $10,000, of which $6,000 has been collected, leaving $4,000 outstanding. The payment lifecycle runs from the invoice or payment obligation of $10,000, through a payment of $6,000, to $4,000 outstanding, a relevant due date, and a next expected payment. Payment context alongside it records the configured gateway, relevant refund activity, relevant customer credit and relevant recurring activity. Every figure on this page is illustrative sample data. Expected payment activity is not collected payment, and Bonza does not hold client funds.
The short answer
Client payment management inside Salesforce — not a financial system of record.
Bonza Payments gives financial and professional services organizations a Salesforce-native way to manage customer payment activity across one-time and recurring payments, receivables, due and overdue obligations, refunds, customer credits, configured payment gateways and upcoming payment visibility. Its value is in keeping relevant payment activity connected to the client relationship already managed in Salesforce: Salesforce-native customer payment management for financial and professional services organizations that need to keep payment activity connected to the wider client relationship.
Bonza should not be positioned as a core banking, accounting or industry-specific financial system. It is not a bank, a lending or loan-servicing platform, a wealth, portfolio or investment platform, a trust accounting or escrow system, an insurance claims or policy administration system, a securities platform or a money transmission platform, and it does not hold or manage client funds.
The real problem
For professional services firms, the payment problem is often less about transaction processing and more about keeping invoices, payments, outstanding balances and future payment activity connected to the client relationship. Firms tend to manage the client carefully and the payment casually — not through neglect, but because payment arrived later and went somewhere else.
An engagement, a firm they deal with, a set of amounts they have paid or owe. From where the client sits there is no distinction between the advisory work and the invoice for it.
The more valuable the client relationship, the more expensive payment fragmentation becomes operationally.
Five realities of relationship-based payment
Within a single client relationship a payment may be an invoice, a deposit where relevant, an engagement fee, a milestone-related amount where relevant, a one-time charge or a recurring service-related payment.
A payment without customer and account context does not tell operations who the client is, what the payment relates to, what remains outstanding, what was previously paid or what is expected next.
Invoices, gateway transactions, outstanding balances, refunds, credits, recurring payments and upcoming payments end up tracked across different systems, each correct on its own.
Clients tend to expect a payment experience that matches the rest of the professional relationship. A disjointed one is noticed precisely because everything else was not.
When a client asks whether a payment was received, what they still owe, where a refund is, whether they hold credit or what is due next, the firm should not be reconstructing the answer by hand while they wait.
Each of the five above is survivable alone. Together they describe a firm whose client record is careful and whose payment record is scattered — which is the gap this page is about.
The same payment, two views
One client, one $5,000 payment, nothing processed differently. Switch between the two readings of it.
Relationship-based businesses need more than transaction history.
Beyond the gateway
Processing sits at layer three. The layers around it are where a client relationship either stays legible or stops making sense.
Processing the payment is one moment. Managing the client payment relationship is the wider operation.
One client, many payment moments
Grouped as a firm would actually think about them: the engagement, the ongoing arrangement, and what happened after collection.
Illustrative payment events for one sample client, Acme Advisory. Group one, the engagement obligation of $10,000: a first payment of $6,000 collected on 15 August, a second payment of $4,000 still outstanding and due 15 October. Group two, the ongoing arrangement: a recurring payment of $1,500 collected 01 September, a next recurring payment of $1,500 expected 01 October which is expected activity rather than collected payment, and a payment method expiring 31 October which lands before the following expected payment. Group three, after collection: a refund of $500 raised 12 September against the first payment and carrying its relevant refund status, and a customer credit of $500 created 12 September and available for relevant future payment use. Every figure is illustrative sample data.
The client sees one relationship. The payment history should reflect that continuity.
The industry operating model
Capability by capability
Each one is an ordinary scenario in a relationship-driven firm, and each stays attached to the same client.
Not every client relationship fits a recurring schedule. Firms may need to collect relevant one-time or ad hoc payments while keeping the activity connected with the Salesforce customer relationship.
The operational question is not only "was a payment processed?" It is also "what remains unresolved in the client payment relationship?"
Timing tells finance whether an unresolved amount is simply still expected or actually requires attention. Those are different situations wearing the same number.
Where clients make relevant repeated payments, Bonza supports recurring payment management inside the wider Salesforce payment lifecycle.
Finance and operations teams in relationship-driven firms need forward visibility, because the next payment is usually part of a relationship that already exists.
Payment relationships change after collection. Refunds and customer credits should stay understandable within the wider client payment story rather than becoming side processes.
Customer credit is customer value recorded and managed within Bonza Payments — never a wallet, a cash balance, stored funds, an escrow or trust account, or client money held by Bonza.
Explore simplify refunds & creditsProfessional-services firms may already have different provider relationships or operational payment requirements. Bonza supports multiple configured gateways while keeping relevant payment activity connected to Salesforce.
A professional client payment experience should make the relevant payment context understandable without exposing internal payment complexity. Where Salesforce Experience Cloud is used, relevant payment journeys can stay part of the broader Salesforce customer environment.
Where clients pay through a portal, Experience Cloud payments covers that environment in full.
Explore improve customer payment experienceAttention, not automation
Use cases
Deliberately capability-based. No loan, insurance premium, investment contribution or mortgage scenarios appear here, because those are not established Bonza use cases.
The organization needs to collect a relevant customer payment.
Payment processing becomes disconnected from Salesforce customer context.
Connect customer payment activity with the Salesforce payment lifecycle.
Clearer payment visibility.
A client is expected to pay against a relevant invoice or payment obligation.
The invoice, payment and outstanding position become disconnected.
Connect the relevant payment activity and receivables context.
Clearer client payment visibility.
A client needs to make a one-time or ad hoc payment.
The payment becomes a separate transaction outside the wider relationship.
Keep relevant payment activity connected with Salesforce.
A more coherent client payment history.
The client makes relevant repeated payments.
Each payment cycle becomes operationally separate.
Manage recurring activity within the wider payment lifecycle.
Better continuity across cycles.
An expected payment remains unresolved.
Finance needs due, overdue and client context together.
Connect receivables and payment timing.
Clearer operational attention.
Client value changes after collection.
The post-payment event becomes disconnected from the original payment.
Keep refund and credit context connected.
Clearer post-payment visibility.
When a client asks
Client-facing teams do not need every finance function — they need relevant payment context within their authorized process.
Explore Bonza for customer serviceWhat most firms get wrong
The client relationship is lost the moment processing succeeds, and has to be rebuilt by hand afterwards.
Processing data becomes separated from Salesforce, and each provider becomes its own small operation.
Client, payment and timing context must be reconstructed manually, usually by the person who least wants to.
Teams know what was collected but not what is expected next — which in a recurring relationship is most of the picture.
The client payment history stops making sense the moment something changes after collection.
Maturity
A description of how client payment operations tend to develop. It is not a score, and no visitor is being assessed.
No firm is required to reach level five, and plenty operate well without it.
Outcomes
Keep relevant payment activity tied to the Salesforce customer relationship.
Understand what is collected, outstanding, due and overdue against each client.
See relevant upcoming and recurring payment activity before the date arrives.
Reduce the need to piece together payment history from multiple systems.
Keep refunds and customer credits inside the wider payment story.
Support multiple configured providers within one broader payment-management model.
Keep the relevant customer payment experience connected with Salesforce.
Give authorized teams more context when deciding what requires attention.
No reduced DSO, higher collections, faster payments, higher retention or client satisfaction, lower service cost, revenue growth, productivity figure or ROI appears on this page.
Why Bonza Payments
Keep relevant client and payment context in Salesforce, where the relationship already lives.
Connect one-time payments, recurring payments, receivables, refunds, credits and upcoming activity.
Keep payment activity associated with the wider customer relationship rather than a transaction log.
Work across multiple configured gateways without turning each provider into a separate payment operation.
Connect internal payment operations with relevant client-facing payment journeys.
Use recurring payment context, payment forecasting and payment method expiry where relevant.
Use AI payment insights and the Payment Command Center for additional operational context.
Not a bank, core banking, lending, trust accounting, escrow, accounting or ERP system — and it does not hold client funds.
Connected suite
The same payment foundation serves finance, operations, client service and revenue operations without becoming a different system for each.
The client relationship should not break when payment begins.
Questions
By keeping the payment operation in the same environment as the client relationship. Bonza Payments is Salesforce-native, so one-time and recurring payments, invoice-driven obligations, receivables, refunds, customer credits and upcoming payment activity stay associated with the Salesforce client record rather than living in a provider portal or a spreadsheet beside it.
Yes, both. An invoice-driven payment keeps the obligation, the payment and the outstanding balance connected, so the operational question "what remains unresolved?" has an answer. A one-time or ad hoc payment stays attached to the client's payment history rather than becoming an isolated transaction.
Yes, as recurring payment management within the wider payment lifecycle — the arrangement, the schedule, the payment activity and what is expected next. This is not complete subscription billing: plan management, usage billing, proration and subscription lifecycle management are not claimed capabilities.
Yes. Outstanding, due and overdue are distinct states of the same obligation, and timing is what tells finance whether an amount is simply still expected or needs a person to look at it. No automated dunning, autonomous collections or debt-collection capability is claimed.
Yes, and both stay connected to the original payment and the client. Customer credit is customer value recorded and managed within Bonza Payments — not a wallet, a cash balance, stored funds, or an escrow or trust account. Refund timing is not promised.
Yes. Bonza supports multiple configured gateways, including a configured default and explicit selection where a scenario calls for it, while relevant payment activity stays connected to Salesforce. There is no automatic routing, automatic failover, fee optimisation or settlement reconciliation, and provider capabilities are not interchangeable.
Yes to both. Where Experience Cloud provides the client-facing environment, relevant payment journeys can remain part of the broader Salesforce customer experience. Separately, forward visibility covers relevant upcoming and recurring payment activity and payment methods approaching expiry — as expected or scheduled activity, never as guaranteed cash.
No to both. Bonza does not provide trust accounting, client funds management, escrow or custody, and it should not be described as holding or managing client or customer money. It is a payment-management layer: configured payment gateways perform the relevant underlying payment processing, and Bonza keeps the surrounding Salesforce payment context.
No. Bonza is not a core banking platform, a lending or loan-servicing system, a wealth, portfolio or investment platform, an insurance billing, claims or policy administration system, a securities platform or a money transmission platform. None of those capabilities is claimed.
No. Bonza focuses on Salesforce-native customer payment management and operational payment visibility. It does not provide a general ledger, journal entries, tax calculation or filing, regulatory reporting, revenue recognition, expense management, bank reconciliation or settlement reconciliation.
No. None of those capabilities is claimed here, and no regulatory approval, financial licence, industry certification or compliance certification is implied anywhere on this page.
AI payment insights surface relevant changes for a person to review — that payments have moved into overdue status, that upcoming recurring activity has changed, or that payment methods approach expiry before expected payment activity. It does not score clients or credit risk, estimate default probability, detect fraud, take collection action or make financial decisions.
Financial & professional services
See how Bonza Payments connects one-time and recurring payments, receivables, refunds, customer credits, upcoming payment activity and configured gateways inside Salesforce for financial and professional services organizations.