Due today · INV-2240DUE
Due & overdue payments
Know What's Due. See What's Overdue. Act Before It Gets Lost.
Surface due and overdue customer payments in Salesforce, understand what's still outstanding and give finance teams a clearer view of where attention is needed.
Part of the Salesforce-native Bonza Payments suite| Customer | Amount | Due date | Status | Timing | Payment context | |
|---|---|---|---|---|---|---|
| Acme Customer | $4,500 | Today | DUE | Expected today | Invoice INV-2240 · card •••• 4242 | View |
| Northstar Industries | $2,800 | 06 Sep | OVERDUE | 18 days outstanding | Invoice INV-2214 · card •••• 4242 | View |
| Brightpath Logistics | $9,450 | 28 Aug | OVERDUE | 27 days outstanding | Invoice INV-2190 · bank transfer | View |
| Global Corp | $6,200 | 08 Oct | UPCOMING | In 14 days | Invoice INV-2255 · bank transfer | View |
| Northwind Traders | $2,400 | 01 Oct | UPCOMING | Payment method expiring soon | Recurring REC-0391 · card •••• 1188 | View |
| Harbor Academy | $3,150 | 12 Sep | PAID | Collected 12 Sep | Invoice INV-2205 · card •••• 3007 | View |
Interface shown is an illustrative representation of Bonza Payments inside Salesforce. Amounts, customers and references are sample values.
The real problem
The Problem Isn't Knowing That Customers Owe You.
It's knowing what needs attention before outstanding payments disappear into the noise.
A finance team may have hundreds or thousands of payment records. Knowing that money is outstanding is not enough. The operational questions are narrower than that:
- What is due today?
- What becomes due next?
- What is already overdue?
- How long has it been outstanding?
- Which customer is responsible?
- What payment activity has already occurred?
- Is there an upcoming recurring payment?
- Does the customer have a credit?
- Was there a refund?
- Is a payment method approaching expiry?
- Where should the team look first?
WITHOUT CONNECTED VISIBILITY, THE ANSWERS ARE SPREAD ACROSS
The result is not necessarily a lack of data. It is a lack of operational clarity.
Payment states
Not Every Outstanding Payment Needs the Same Attention.
Four states carry four different operational questions. Reading them as one undifferentiated pile of "unpaid" is what makes payment work feel like searching.
The payment is expected on a future date — an invoice obligation, a scheduled recurring collection or another expected payment.
“Do we know what's coming?”The expected payment date is today. The payment is current rather than late, and it belongs in today's working view.
“Is this payment ready to be collected or completed?”The expected payment date has passed and the relevant amount remains outstanding. Time has changed the status, not the customer relationship.
“Does this now require attention?”The relevant amount has been received and the record moves out of the attention view and into payment history.
“Can this leave the attention queue?”Time moves a payment between states. Bonza reflects that movement in the payment operation — it does not take action on a customer's behalf.
From list to queue
An Overdue List Tells You What Happened. An Attention View Helps You Decide Where to Look.
Every record carries the same weight
Customer, amount, date, status — sorted, but not prioritised. The team still has to work out which line matters this morning.
The same records, read by timing
Bonza helps teams distinguish payment states instead of treating every outstanding record the same. It does not assign a proprietary risk score or label customers.
Core capability
Know What Needs Attention at Every Payment Stage.
Five operational questions, answered where the customer already lives.
What's coming due?
Forward visibility into relevant upcoming payment obligations, so the team sees what's approaching before the due date arrives rather than discovering it afterwards.
What's due now?
Payments whose expected date has arrived are surfaced together as one current view — not reconstructed by opening customer records one at a time.
What's overdue?
Payments that remain outstanding beyond their expected due date are identified as a distinct state, with how long they've been outstanding visible alongside the amount.
Who does it belong to?
Every payment obligation stays connected to its Salesforce customer and account context, so an amount is read as part of a relationship rather than as an anonymous row.
What happened around it?
Where applicable, the surrounding payment story stays connected — payment history, invoices, one-time payments, recurring payments, credits, refunds and payment-method information.
Due & overdue workspace
Turn Your Outstanding Payments Into a Working Queue.
Filter by timing, search by customer or reference, and read each payment with its context attached. Try the filters — this is a live, illustrative representation of the workspace.
- Due
- 28 Aug
- Payment
- Invoice INV-2190
- Outstanding
- 27 days
- Due
- 06 Sep
- Payment
- Invoice INV-2214
- Outstanding
- 18 days
- Due
- 15 Sep
- Payment
- One-time PAY-8871
- Outstanding
- 9 days
- Due
- 19 Sep
- Payment
- Invoice INV-2231
- Outstanding
- 5 days
- Due
- Today
- Payment
- Invoice INV-2240
- Method
- Card •••• 4242
- Due
- Today
- Payment
- Recurring REC-0412
- Method
- UPI
- Due
- 27 Sep
- Payment
- Invoice INV-2248
- Timing
- In 3 days
- Due
- 29 Sep
- Payment
- Recurring REC-0377
- Timing
- In 5 days
- Due
- 01 Oct
- Payment
- Recurring REC-0391
- Method
- Expiring soon
- Due
- 08 Oct
- Payment
- Invoice INV-2255
- Timing
- In 14 days
- Due
- 15 Oct
- Payment
- Invoice INV-2261
- Timing
- In 21 days
- Collected
- 12 Sep
- Payment
- Invoice INV-2205
- Method
- Card •••• 3007
- Collected
- 19 Sep
- Payment
- One-time PAY-8790
- Method
- Card
No illustrative payments match that filter or search.
Optional filters such as customer, date, payment type or gateway may be available depending on configuration. [Confirm the final filter set before launch.] Overdue carries a strong attention indicator, due a clear active one, upcoming a neutral informational one and paid a resolved state — deliberately professional rather than alarming.
Time and status
See When an Outstanding Payment Crosses Into Overdue.
Drag the handle to move one illustrative payment through time and watch the state change around it.
Upcoming
The payment is expected on a future date. It sits in the forward view so the team knows what's approaching.
This timeline is educational. It shows how payment status changes with time. Bonza does not automatically send reminders, escalate, apply late fees, assign collections or contact customers at any of these intervals. What happens next is your team's decision.
Customer context
Before You Follow Up, Understand the Payment Story.
Amounts shown are illustrative and connected to one Salesforce account rather than to an anonymous payment row.
CHRONOLOGICAL PAYMENT STORY · ILLUSTRATIVE
Collected 02 Sep · card •••• 4242$2,750PAID
Expected 10 Sep · outstanding$1,240OVERDUE
Expected today · card •••• 4242$4,500DUE
Next collection 05 Oct · monthly$3,440UPCOMING
Issued 28 Aug$300AVAILABLE
Processed 21 Aug · against INV-2151$150PROCESSED
Payment-method expiry
Some Future Payment Problems Become Visible Before the Due Date.
If a payment method is approaching expiry before a future payment, teams may benefit from seeing that information while there is still time to understand the situation.
- Customer
- Northwind Traders
- Next payment
- 01 Oct
- Amount
- $2,400
- Payment method
- Card •••• 1188
- Expiry
- 09/26
- Status
- EXPIRING SOON
This payment method may require attention before the upcoming collection.
The team sees the situation with days to spare rather than after the collection date. What to do about it — reach out, request an updated method, or simply note it — remains a human decision.
Bonza does not state that a payment will fail, update payment methods automatically or contact customers on your behalf. Expiry visibility depends on what the configured gateway exposes.
How they relate
Receivables Tell You What's Outstanding. Due & Overdue Tells You What Needs Attention.
“What money are we still waiting to collect?”
- FOCUS
- The overall outstanding position across customers.
- VIEW
- PaidOutstandingDueOverdueUpcoming
“Which payment obligations need attention based on timing?”
- FOCUS
- Operational payment status — what to look at, in what order, today.
- VIEW
- UpcomingDueOverdueResolved
They are connected capabilities, not competing ones. Receivables provides the broader financial picture; Due & Overdue provides a more focused operational attention view of the same payment activity.
Backward and forward
Look Back at What's Late. Look Forward at What's Next.
Due and overdue visibility is more useful when teams can understand both past-due obligations and relevant upcoming expected payments. Payment forecasting extends the forward half of that view.
Expected collections are not guaranteed collections. Forward visibility describes what is scheduled or expected, not what will be received.
Explore Payment Forecasting →Payment intelligence
Use Intelligence to Surface What Deserves a Closer Look.
Intelligence in Bonza is an insight and prioritisation layer. It reads payment data you already have and points at what may deserve review. Every action stays with your team.
Bonza intelligence does not contact customers, make credit decisions, assign debt risk scores, write off balances, trigger legal action, guarantee collection or change payment terms on its own.
From attention to resolved
When Attention Turns Into Payment, Keep the Lifecycle Connected.
Where relevant, payment collection connects with a one-time payment, the customer payment experience and a configured payment gateway — so identifying an overdue payment leads naturally into the rest of the Bonza payment lifecycle instead of into a separate tool.
Bonza does not invent automatic collection mechanisms. Collection happens through your configured payment capabilities, initiated by your team or your customer.
Multi-gateway
Keep Payment Visibility Connected Across Your Gateway Strategy.
Due and overdue status should read the same way regardless of which configured gateway the payment activity came through.
Gateways shown are examples. Gateways differ in what information they expose, so some context — such as payment-method expiry — depends on the gateway. Bonza is the Salesforce-native management layer, not the gateway. [Confirm the supported gateway list before launch.]
Payment Command Center
See Due and Overdue Payments in the Bigger Payment Picture.
This page helps a finance team investigate the payment obligations that need attention. The Command Center helps leadership read the whole payment operation around them.
Surfaced for review. Your team decides what to act on.
Use cases
Built Around the Payment Moments Finance Teams Need to See.
An expected payment reaches its date
- NEED
- Know that the payment now requires current attention.
- BONZA
- Surfaces the payment as due within the payment operation, alongside the customer it belongs to.
The date passes, the amount remains
- NEED
- Distinguish it from current and future obligations.
- BONZA
- Surfaces overdue status with how long the amount has been outstanding.
Several outstanding payments at once
- NEED
- See them together in one operational view.
- BONZA
- Provides due and overdue visibility connected with Salesforce customer context.
A recurring collection is expected soon
- NEED
- Understand what is approaching before it arrives.
- BONZA
- Connects upcoming recurring payment visibility with the broader payment picture.
A method may expire before a collection
- NEED
- Awareness before the payment date, not after it.
- BONZA
- Surfaces relevant expiry information where the gateway exposes it.
An outstanding payment is received
- NEED
- Move from an attention state into a resolved payment state.
- BONZA
- Keeps payment status connected with the wider payment lifecycle and receivables view.
Connected suite
Due and Overdue Is One View of a Much Bigger Payment Lifecycle.
The outstanding position Invoices
What was billed Payment Management
The full lifecycle One-Time & Ad Hoc
Request and collect Recurring Payments
Scheduled collections Credits
Balances in the customer's favour Refunds
Post-payment changes Customer Payment Experience
How customers pay Multiple Gateways
Your gateway strategy Payment Forecasting
The forward view Payment Intelligence
Insights and signals Payment Command Center
The whole operation
What changes
Operational Clarity, Not a Bigger Spreadsheet.
Outcomes describe the visibility Bonza provides. We do not claim percentage improvements in overdue balances, DSO, collection rates or recovery — those depend on your process, your customers and your commercial terms.
Why Bonza
Know What Needs Attention Without Losing the Bigger Picture.
Salesforce-native
Due and overdue payment information sits with the Salesforce customer context it belongs to, not in a separate system your team has to cross-reference.
Payment-lifecycle coverage
Move from identifying an outstanding obligation into the wider payment-management process rather than stopping at a list of names and amounts.
Paid / due / overdue visibility
Clear operational payment states, so timing — not guesswork — determines what the team looks at first.
Forward visibility
Connect current obligations with upcoming payments and relevant payment forecasting, so today's queue is read next to what's coming.
Payment intelligence
Surface insights such as payment-method expiry and payment attention signals where supported — always as information for a human decision.
Multi-gateway flexibility
Keep payment management connected while working with multiple configured gateways, with a default or preferred gateway where you need one.
FAQ
Due & Overdue Payments in Salesforce, Answered.
What is a due payment?
A due payment is a payment obligation that has reached its expected payment date. It is current rather than late — the date has arrived, and the payment is ready to be collected or completed.
What is an overdue payment?
An overdue payment is one where the expected payment date has passed and the relevant amount remains outstanding. Nothing about the customer has changed; time has moved the payment into a state that warrants attention.
How can I track overdue payments in Salesforce?
With Bonza Payments, overdue payment obligations are surfaced inside Salesforce alongside the customer record, with the amount, the expected date, how long it has been outstanding and the related payment context — rather than being reconstructed from spreadsheets, gateway dashboards and manual lists.
Can Bonza Payments show due and overdue customer payments?
Yes. Upcoming, due, overdue and paid are the operational states this page is built around, and they can be read as one working queue with filters and search, or per customer.
What is the difference between receivables and overdue payments?
Receivables answer “what money are we still waiting to collect?” — the overall outstanding position. Due & Overdue answers “which payment obligations need attention based on timing?” — a focused operational view of the same payment activity. They are connected capabilities rather than competing ones.
Can I see upcoming payments before they become due?
Yes. Forward visibility includes relevant upcoming obligations such as invoice-related payments and scheduled recurring collections, so teams can see what is approaching rather than only what has already slipped.
Can due and overdue payments be connected to Salesforce customer records?
Yes. Because Bonza is Salesforce-native, each payment obligation stays connected to its customer and account context, along with the payment history, invoices, credits and refunds around it.
Can Bonza show payment methods approaching expiry?
Where the configured gateway exposes that information, yes. Expiry can be surfaced against upcoming payment activity so teams have early visibility. It does not mean a payment will fail, and Bonza does not update payment methods automatically.
How do recurring payments relate to due and overdue payments?
Recurring collections create expected future payment obligations. Those appear in the upcoming view, become due when their date arrives, and — if the relevant amount remains outstanding afterwards — are read in the same overdue state as any other payment obligation.
Does Bonza automatically contact customers about overdue payments?
No. Bonza provides visibility, prioritisation and payment-management capabilities. It does not send automated dunning sequences, reminder emails or SMS chasing, generate collection messages, or contact customers on your behalf. It surfaces what needs attention; your team decides what to do about it.
Can I collect an overdue payment through Bonza Payments?
Payment collection happens through your configured payment capabilities and gateways — for example a one-time payment or the customer payment experience — and the resulting payment status stays connected to the same record. Bonza does not create automatic collection mechanisms of its own.
Can due and overdue payments appear in the Payment Command Center?
Yes. Due and overdue amounts sit alongside collected, outstanding, upcoming, recurring, credits, refunds and expiring payment methods in the Command Center, including a needs-attention panel — the operational view at leadership level rather than the working queue.
Know Which Payments Need Attention Today.
See how Bonza Payments helps finance teams surface due and overdue payments, understand customer context and keep payment activity connected to Salesforce.