Know what is owed
Keep visibility into invoice-related amounts and customer payment obligations, on the same record as the customer.
WHY IT MATTERSFinance teams need a clear starting point for understanding what a customer is expected to pay.
Invoice payment management
Connect invoice-driven payments with Salesforce so your teams can see what customers owe, what has been collected and what still needs attention.
Part of the Salesforce-native Bonza Payments suiteDefinition
The gap after the invoice
Creating or recording an invoice is only one part of the receivables process. The operational work begins once an amount becomes due — and it needs six things held together:
The invoice is not the end of the process. It is the beginning of a payment lifecycle.
What Bonza does around an invoice
Keep visibility into invoice-related amounts and customer payment obligations, on the same record as the customer.
WHY IT MATTERSFinance teams need a clear starting point for understanding what a customer is expected to pay.
Connect invoice-driven payment needs with Bonza's payment collection. Where appropriate, payments use the configured Bonza payment experience and gateway setup.
WHY IT MATTERSThe payment should stay connected to the business context that created it.
Maintain visibility into whether invoice-related payments have been collected, and their relevant payment status.
WHY IT MATTERSTeams should not have to search a gateway portal to answer “did this customer pay?”
Connect invoice and payment information with broader receivables visibility.
A conceptual view of the relationship, not an accounting or reconciliation rule.
WHY IT MATTERSWhat is left is the number finance acts on.
An invoice and payment relationship may continue into receivables, due and overdue visibility, refunds, credits, payment history, the Command Center, forecasting and payment intelligence.
WHY IT MATTERSThe transaction should not become an isolated record.
Invoice-to-payment lifecycle
Step through one invoice. The figures on the right are the same record at each stage — what the finance team can see, and what they still need to know.
Illustrative record. [Confirm the invoice statuses your implementation uses before launch.]
Payment status visibility
| Customer | Invoice | Amount | Due date | Paid | Outstanding | Status |
|---|
No invoices in this view.
Filters shown as a UI concept. Every value on this page is illustrative.
Invoices and receivables
An individual invoice becomes more useful once finance can read it inside the customer's broader outstanding position.
Customer side
Where a customer-facing payment experience is configured, the customer can see what is due and pay through an available option — and the resulting activity stays visible in Salesforce.
Payment options depend on your configured gateways, and the customer-facing experience on what has been set up — including Salesforce Experience Cloud and customer credits where applicable. This page does not claim portal features beyond that.
Gateways
Bonza supports multiple configured payment gateways, with a default or preferred gateway set as part of your payment setup. Bonza is the management and orchestration layer — not the gateway itself.
Gateway names are examples. Not every gateway supports the same capabilities. [Confirm the supported gateway list before launch.]
After the payment
Once an invoice-related payment is collected, circumstances can still change. A payment may need a refund, or value may be held as customer credit for future payment use.
The payment sits against the invoice and the customer record.
A refund is processed through Bonza and the refund history stays alongside the original payment.
Explore Refunds →Value is tracked as a customer credit balance that remains available for future payment use.
Explore Credits & Refunds →How a credit is applied to a future payment depends on your configuration.
The bigger picture
One invoice is a transaction. All invoices together become an operational payment picture.
| Customer | Invoice | Amount | Status |
|---|---|---|---|
| Acme Customer | INV-10482 | $3,500 | Due |
| Harbor Academy | INV-10477 | $2,400 | Paid |
| Northwind Traders | INV-10461 | $8,920 | Overdue |
| Lumen Health Partners | INV-10490 | $5,600 | Paid |
Values are illustrative; metrics depend on what your implementation records.
Use cases
A customer has an amount due against an invoice and pays it.
Invoice → Payment → Status → Complete
The due date approaches and payment is still outstanding.
Invoice → Due → Outstanding visibility → Attention
The expected payment date has passed. Follow-up stays a decision your team makes.
Invoice → Overdue → Receivables → Follow-up
An invoice-related payment is collected but later requires a refund.
Invoice → Payment → Refund → Updated history
A customer credit forms part of the wider payment lifecycle around the invoice.
Invoice → Credit → Payment → Status
Connected suite
Outcomes
Why Bonza
Invoice and payment activity sits with the Salesforce customer context.
Move past recording an invoice or processing a single transaction.
Connect invoice activity with due, overdue and outstanding information.
Use your configured gateway options through the wider Bonza payment experience.
Keep refunds and customer credits attached to the payment story.
See invoice-driven payments inside the broader Command Center view.
FAQ
Invoice payment management connects the amount a customer owes with the payments collected against that obligation. It covers knowing what is owed, collecting payment, tracking status, understanding what remains outstanding and deciding what needs attention next.
Yes. Bonza Payments is Salesforce-native, so invoice-related payment activity and its status sit inside Salesforce alongside the customer record rather than in a separate system.
Payments collected against an invoice stay associated with that invoice and with the customer, so the amount owed, the payment activity and the outstanding balance can be read together.
Yes — payment status is the point of the page. Paid means the payment was received, due means it is expected, overdue means the expected date has passed and it needs attention.
Yes. Invoice and payment activity is connected to the customer, which is what lets teams see one invoice in the context of everything else that customer owes.
Where a customer-facing payment experience is configured, customers can pay through an available payment option and the activity stays visible in Salesforce. What customers can do depends on your configuration.
Yes. Multiple gateways can be connected, with a default or preferred gateway configured. Bonza is the payment management layer, not the gateway, and gateways differ in what they support.
Outstanding invoice amounts form part of the customer's receivables position, so an individual invoice can be read inside the wider picture of what that customer still owes.
A refund can be processed through Bonza and the refund history stays alongside the original payment and the customer, so the payment story remains complete.
Customer credit balances are tracked as part of the wider payment lifecycle and remain available for future payment use. How a credit is applied depends on your configuration.
Yes. Invoice-driven payments appear within the broader payment operation — collected, outstanding, due and overdue — alongside other payment activity. Which metrics appear depends on what your implementation records.
An invoice is a single obligation: what was billed, when it is due and what has been paid against it. Receivables is the position across obligations: what a customer, or the business, still has outstanding. Bonza connects the two, and is not an accounting or general-ledger system.
See how Bonza Payments connects invoice-driven collections, payment status and receivables with your Salesforce customer data.