Book a Demo

Manage recurring payments

Recurring Payments Should Repeat. Your Manual Work Shouldn't.

Manage scheduled and recurring customer payments in Salesforce with connected visibility into what has been collected, what is coming next and what may require attention.

See Recurring Payment Management in Action Explore Recurring Payments
Powered by the Salesforce-native Bonza Payments suite
Recurring payment workspace Active ILLUSTRATIVE VALUES

RECURRING PAYMENT

Customer
Acme Customer
Amount
$1,500
Frequency
Monthly
Next payment
15 Oct
Gateway
Configured gateway
Payment method
•••• 4242
Status
Active

PAYMENT ACTIVITY OVER TIME

  1. AUG$1,500
  2. SEP$1,500
  3. OCT$1,500Upcoming
  4. NOV$1,500Scheduled
  5. DEC$1,500Scheduled

PAYMENT METHOD EXPIRY

Card ending
•••• 4242
Expires
Oct
Next payment
15 Nov
Status
Review

Expiry sits before the next scheduled payment date, so this arrangement is worth a look.

CollectedIllustrative
UpcomingIllustrative
OutstandingIllustrative
Needs attentionIllustrative

Definition

What Is Recurring Payment Management?

Recurring payment management is the process of organizing, collecting, tracking and reviewing customer payments that are expected to repeat over time.

Bonza Payments helps businesses manage recurring payment activity within Salesforce, including relevant schedules, payment status, upcoming collections and wider customer payment context.

Recurring payment management is broader than simply repeating a transaction. It also involves understanding what happened, what is expected next and what may require attention.

The operational problem

A Repeating Payment Can Still Create Repeating Work.

A recurring payment schedule may remove the need to recreate every individual charge. Finance teams can still end up checking the same questions every cycle:

  • Was the payment collected?
  • What is the next payment date?
  • Which customer does it belong to?
  • Is anything outstanding?
  • Did a payment become overdue?
  • Is the payment method still valid?
  • Does the customer have a credit?
  • Was a refund issued?
  • What recurring payments are expected next month?
  • Which payment relationships need review?

When that context is scattered, the answers have to be reassembled by hand every cycle:

SalesforcePayment gatewaySpreadsheetRecurring scheduleInvoice informationCustomer notes

Automating the repeat transaction does not automatically create a manageable recurring payment operation.

How it works

Recurring Payments Are a Cycle, Not a Series of Unrelated Transactions.

A mature recurring-payment process preserves continuity across the whole customer relationship, so each payment does not have to be reinterpreted from scratch.

  1. 01Customer
  2. 02Payment arrangement
  3. 03Schedule
  4. 04Payment 1
  5. 05Payment 2
  6. 06Payment 3
  7. 07Next payment
  8. ↺Cycle continues
  9. Each cycle returns to the same customer arrangement, carrying its history with it.
CARRIED THROUGH EVERY CYCLE Payment statusCustomer contextReceivablesPayment methodRefund / creditUpcoming activity

Two operating models

Recurring Payments Become Hard to Manage When the Schedule Is the Only Thing Connected.

FRAGMENTED MODEL

The schedule fires. Everything else is manual.

  • Recurring schedule
  • Gateway
  • Payment
  • Spreadsheet
  • Manual Salesforce update
  • Manual status check
  • Next cycle ↺
InvoiceReceivablesCustomer recordRefundsCredits

Side systems stay disconnected from the cycle.

BONZA MODEL

The cycle stays attached to the customer.

  • Customer
  • Recurring payment arrangement
  • Schedule
  • Bonza payment management
  • Configured gateway
  • Payment activity
  • Status · receivables · next payment
  • Payment Command Center
  • Next cycle ↺

The goal is not simply to repeat the payment. It is to keep the payment relationship connected across cycles.

The operating model

Manage the Cycle, Not Just the Charge.

01Set upEstablish the recurring payment arrangement.
02ScheduleDefine when relevant payment activity is expected.
03CollectProcess recurring payment activity through the configured payment setup.
04TrackMaintain visibility into what happened.
05AnticipateSee what is expected next.
06Review exceptionsSurface outstanding payments, overdue status, payment methods approaching expiry and relevant AI insights — for a person to review.
↺ NEXT CYCLEThe arrangement continues, with everything the last cycle produced still attached to the customer.

Exception handling is surfaced for review. It is not fully automated.

How Bonza capabilities work together

Set It Up Once. Keep the Payment Relationship Visible Every Time It Repeats.

01 — Less repetitive administration

Stop Rebuilding the Same Payment Process Every Cycle.

For payment relationships that repeat over time, recurring schedules can reduce the need to manually recreate individual payment activity every billing period. Bonza keeps relevant recurring payment activity connected with the Salesforce customer and payment context.

Recurring PaymentsPayment Management
Explore Recurring Payments

RECURRING ARRANGEMENT · ILLUSTRATIVE

Set upArrangement created once
ScheduleMonthly · 15th
PaymentCollected · Sep
TrackStatus on the customer record
Next payment15 Oct
↺ REPEATSWithout rebuilding the process

02 — What actually happened

Know What Happened After the Schedule Fired.

A recurring schedule tells you what should happen. The business still needs to understand what actually happened. Bonza keeps payment status, customer payment history and the receivables position connected to the same arrangement.

“Did the expected payment become actual payment activity?”

Payment ManagementPayment StatusReceivables

EXPECTED → ACTUAL · ILLUSTRATIVE

Scheduled15 Sep · $1,500
Payment eventRecorded 15 Sep
StatusPaid
Customer payment history4 payments
Receivables positionNothing outstanding

03 — Forward visibility

See the Next Payment Before It Becomes Today's Problem.

Recurring schedules create a natural forward view of payment activity expected in future periods. Payment forecasting brings that expected activity into the same place as the rest of the payment picture.

Expected and scheduled activity is not guaranteed collection.

Payment ForecastingRecurring Payments
Explore Payment Forecasting

EXPECTED RECURRING ACTIVITY · ILLUSTRATIVE

TodayCycle in progress
Next payment15 Oct
Following payment15 Nov
Future payment15 Dec
This monthIllustrative
Next monthIllustrative
Following monthIllustrative

04 — Expiry in context

See Expiring Payment Methods in the Context of What Comes Next.

An expiry date becomes far more useful when it sits next to the next relevant recurring payment. Payment method expiry connects the two so the timing question is visible early enough to act on.

An approaching expiry is a prompt to review. Bonza does not update payment methods for you, and an expiry does not by itself mean a future payment will fail.

Payment Method ExpiryRecurring Payments
Explore Payment Method Expiry

EXPIRY VS NEXT PAYMENT · ILLUSTRATIVE

Payment method•••• 4242
Expires31 Oct
Next recurring payment15 Nov
AttentionReview

Payment method expires before relevant upcoming payment activity.

05 — Outstanding activity

When a Recurring Payment Becomes Outstanding, Keep It in View.

Recurring payments do not become operationally irrelevant simply because the expected collection date passed. Where relevant, outstanding payment activity stays visible within the broader receivables and due and overdue payments picture.

Follow-up remains a decision your team makes. Bonza does not run automated dunning.

ReceivablesDue & Overdue Payments

WHEN THE DATE PASSES · ILLUSTRATIVE

Expected payment15 Sep
DueDue
CollectedPaid
or OverdueOverdue
AttentionStays in receivables

06 — What changed this cycle

Let AI Highlight What Changed Across the Recurring Cycle.

AI payment insights read the payment information already in the operation and surface relevant changes with their context, so a person can decide what to do next.

Insights are recommendations and prioritization. They are reviewed and actioned by your team, not carried out autonomously.

AI Payment InsightsPayment Command Center

EXAMPLE INSIGHTS · ILLUSTRATIVE

Upcoming recurring payment activity increases next month.Based on active schedules · See forecast
Several payment methods expire before relevant future recurring payments.Review the affected arrangements · View cards
Multiple payment obligations moved into overdue status.Still visible in receivables · Prioritize
FLOWPayment data → change signal → insight → context → human review

The relationship over time

See the Relationship Over Time, Not Just the Next Charge.

CustomerAcme
Amount$1,500
FrequencyMonthly
GatewayConfigured gateway
Payment method•••• 4242
ILLUSTRATIVE
  1. JAN$1,500
  2. FEB$1,500
  3. MAR$1,500
  4. APR$1,500
  5. MAY$1,500Upcoming
  6. JUN$1,500Scheduled
  7. JUL$1,500Scheduled
PAYMENT METHOD•••• 4242Expires June

Customer context

See the Relationship, Not a Stack of Transactions.

The value of Salesforce-native recurring payment management is not only repeated processing. It is maintaining the payment relationship within the wider customer context.

Acme CustomerRecurring payment arrangement
  1. JAN
  2. FEB
  3. MAR
  4. APR
  5. MAYUpcoming
ALONGSIDE, ON THE SAME CUSTOMER InvoicesReceivablesRefundsCustomer creditPayment methodPayment forecastRelevant payment insights

Customer side

Keep the Customer Side of Recurring Payments Connected Too.

Where a customer-facing payment experience is part of the setup, the payment activity it produces belongs to the same Salesforce record as the rest of the relationship.

CONNECTED PATH Customer Recurring payment relationship Relevant payment context Bonza customer payment experience Payment activity Salesforce

Customer-facing capability depends on what has been configured, including Experience Cloud payments. This page does not claim that customers can pause, cancel, skip, reschedule or change the amount of a recurring payment themselves.

Explore Customer Payment Experience →

Gateway context

Manage Recurring Payments Without Building the Whole Operation Around One Gateway.

ARRANGEMENT Recurring payment arrangement Bonza Payments Configured gateway
CONFIGURED OPTIONS Gateway AGateway BGateway C Payment activity

Available recurring-payment behavior depends on the configured gateway and implementation. A recurring arrangement does not move itself between gateways, stored payment credentials are not portable between providers, and not every gateway supports recurring activity in the same way. Multiple payment gateways covers how gateways are connected and configured.

Exceptions

A Recurring Payment Process Is Only as Good as Its Exception Visibility.

Most recurring cycles may follow the expected path. The difficult operational moments occur when something changes — an overdue payment, an approaching expiry, a refund, an available credit, a status change, or an insight worth reading.

NORMAL CYCLE Schedule Payment Collected Next payment ↺
EXCEPTION PATH Schedule Payment event Attention Human review Next action

Automate the normal cycle. Make the exception easy to see.

After the payment

Recurring Doesn't Mean Every Payment Story Ends the Same Way.

Bonza's wider payment suite keeps post-payment activity connected with the customer relationship, so a refund or a credit does not fall outside the recurring picture.

PATH A

Refund

  • Payment collected
  • Change required
  • Relevant refund process
  • Refund history stays on the customer
PATH B

Customer credit

  • Payment collected
  • Change required
  • Customer credit issued
  • Credit balance remains available for future payment use

How a credit is applied to a future recurring payment depends on your configuration — it is not assumed to happen automatically.

The wider picture

Run the Recurring Payment Operation From the Bigger Payment Picture.

This page manages the cycle. The Payment Command Center helps teams see that cycle as part of the wider payment operation.

Bonza PaymentsCommand Center · Recurring view ILLUSTRATIVE VALUES
Recurring paymentsIllustrativeActive arrangements
UpcomingIllustrativeNext 30 days
OutstandingIllustrativeAwaiting collection
OverdueIllustrativeIn receivables
Payment methods expiringIllustrativeBefore next payment
Upcoming recurring payments View all
CustomerAmountNext paymentStatusPayment method
Acme Customer$1,50015 OctScheduled•••• 4242
Harbor Academy$3,15018 OctScheduled•••• 1190
Northwind Traders$8,92002 OctOverdue•••• 3007
Crestline Realty$64021 OctReview•••• 4821
Summit Members Club$1,20028 OctScheduled•••• 7733
Needs attention
Overdue recurring paymentRemains visible in the receivables picture.
Payment method expires before upcoming paymentSurfaced for review, not changed automatically.
AI recurring-payment insightExpected recurring activity changes next month.

Your team decides what to act on.

Forecast · expected recurring activity
Current monthIllustrative
Next monthIllustrative
Following monthIllustrative
Explore the Payment Command Center

Scope

Recurring Payment Management Is Not the Same as Full Subscription Billing.

Bonza is positioned around managing recurring payment activity within the Salesforce payment lifecycle. It is worth being precise about where that scope ends.

RECURRING PAYMENT MANAGEMENT

What this page is about

  • Payment schedules
  • Repeated payment activity
  • Payment status
  • Upcoming payments
  • Receivables context
  • Payment method expiry
  • Payment operations visibility
SUBSCRIPTION BILLING PLATFORM

A different category of product

  • Plan catalog
  • Usage billing
  • Proration
  • Subscription upgrades
  • Subscription downgrades
  • Revenue recognition
  • Complex billing rules

Bonza does not claim to provide this functionality.

Use cases

Where Businesses Need Better Recurring Payment Management.

Membership payments

SITUATION
Customers or members make payments on a repeated schedule.
PROBLEM
Teams need visibility across each payment cycle.
WITH BONZA
Keep relevant recurring payment activity connected to Salesforce.

A more manageable recurring-payment operation.

Ongoing service payments

SITUATION
A customer pays regularly for an ongoing service relationship.
PROBLEM
The business should not have to rebuild the payment process every cycle.
WITH BONZA
Manage recurring payment schedules and payment activity in one place.

Less repetitive administration.

Scheduled payments across multiple dates

SITUATION
A customer is expected to make payments across multiple dates.
PROBLEM
Teams need visibility into what has happened and what comes next.
WITH BONZA
Keep relevant scheduled payment activity in the payment lifecycle.

Better forward payment visibility.

Recurring payment with an expiring payment method

SITUATION
A customer's relevant payment method expires before future scheduled activity.
PROBLEM
The timing issue may only become visible late.
WITH BONZA
Connect expiry and upcoming payment context in the same view.

Earlier awareness.

Recurring payment becomes overdue

SITUATION
An expected payment remains outstanding.
PROBLEM
The recurring schedule alone does not tell finance what remains unresolved.
WITH BONZA
Keep the relevant payment in the due/overdue and receivables view.

Clearer exception visibility.

Educational framing

How Mature Is Your Recurring Payment Operation?

A way to describe where a recurring-payment operation sits today. Not every organization needs to reach the same level.

LEVEL 1

Manual

  • Repeated payment initiation
  • Spreadsheet schedules
  • Manual status checking
  • Limited forward visibility
LEVEL 2

Scheduled

  • Recurring payment arrangement exists
  • Gateway processes repeated activity
  • Operational context may still be fragmented
LEVEL 3

Connected

  • Recurring payment activity connected with Salesforce
  • Receivables visibility
  • Customer context
  • Upcoming payment visibility
LEVEL 4

Intelligent

  • Payment forecasting
  • Payment method expiry
  • AI payment insights
  • Payment Command Center
  • Exception-focused operations

Outcomes

What a Connected Recurring Payment Operation Gives Your Team.

LESS REPETITIVE ADMINISTRATIONReduce the need to manually recreate repeatable payment activity.
CONNECTED PAYMENT HISTORYKeep relevant payment cycles associated with the customer relationship.
BETTER FORWARD VISIBILITYUnderstand what recurring payment activity is expected next.
EARLIER EXCEPTION AWARENESSSee relevant overdue activity and payment-method expiry context.
CLEARER RECEIVABLES CONTEXTKeep unresolved recurring-payment obligations in the broader payment picture.
MULTI-GATEWAY FLEXIBILITYManage recurring activity in a payment environment that can support multiple configured gateways.
CONNECTED CUSTOMER CONTEXTKeep recurring payment activity tied to Salesforce customer data.
BETTER DECISION SUPPORTGive teams the context they need to decide where attention is required.

Why Bonza

Manage Recurring Payments as Part of the Full Customer Payment Relationship.

Salesforce-native

Keep recurring payment activity connected with Salesforce customer and business context.

Complete payment lifecycle

Connect recurring payments with receivables, due and overdue activity, refunds and credits.

Forward visibility

Bring upcoming recurring payment activity into payment forecasting.

Payment-method awareness

Connect relevant expiry information with future payment context.

Multi-gateway flexibility

Support recurring payment operations across a multi-gateway environment while respecting gateway-specific capabilities.

Payment intelligence

Use AI payment insights and the Payment Command Center to surface relevant changes and attention signals.

FAQ

Recurring Payments in Salesforce, Answered.

What is recurring payment management?

Recurring payment management is the process of organizing, collecting, tracking and reviewing customer payments that are expected to repeat over time. It covers the payment schedule itself and the operational context around it: what was collected, what is expected next, what is outstanding and what needs attention.

How can I manage recurring payments in Salesforce?

With Bonza Payments, the recurring payment arrangement, its schedule and the resulting payment activity live inside Salesforce and stay attached to the customer record. Teams can see payment status, upcoming activity, receivables context and relevant attention items without moving between separate systems.

Can Bonza Payments manage recurring customer payments?

Yes. Bonza Payments is a Salesforce-native payment management suite with recurring-payment capability: schedules, repeated payment activity, payment status and the wider payment context around each arrangement.

What is the difference between recurring payments and subscription billing?

Recurring payment management focuses on repeated payment activity, payment schedules, status and operational visibility. Full subscription billing platforms may additionally include plan management, usage billing, proration, subscription changes and accounting-specific billing capabilities. Bonza is positioned as Salesforce-native payment management, not a complete subscription billing platform.

Can I see upcoming recurring payments?

Yes. Recurring schedules create a forward view of expected payment activity, which appears alongside the rest of the payment picture and in payment forecasting. Expected activity is a forecast of what is scheduled, not a guarantee of collection.

Can recurring payments be connected with Salesforce customer records?

Yes. That connection is the point of a Salesforce-native approach: each payment cycle stays associated with the customer, alongside invoices, receivables, refunds, credits and payment methods.

Can Bonza show recurring payments that become overdue?

Yes. Where a relevant expected payment remains outstanding, it stays visible in the due and overdue view and in the broader receivables picture. Follow-up is a decision your team makes — Bonza does not run automated dunning or send automated customer chasing.

Can Bonza show payment methods approaching expiry?

Yes. Payment method expiry provides visibility when a payment method approaches expiry before future payment activity, so the timing can be reviewed early. An expiry does not itself mean a future payment will fail.

Can Bonza forecast upcoming recurring payments?

Payment forecasting provides forward visibility into relevant expected payment activity, while Recurring Payments manages the repeated payment relationship itself. Figures shown are expected and scheduled amounts rather than guaranteed collections.

Can Bonza work with multiple payment gateways for recurring payments?

Bonza can manage payments across multiple configured gateways. Available recurring behavior depends on the gateway and the implementation — a recurring arrangement does not switch gateways by itself, and stored payment credentials are not portable between providers.

Can customers manage their recurring payments themselves?

Customer-facing payment capability depends on what has been configured, including Experience Cloud payments. This page does not claim customer self-service for pausing, cancelling, skipping, rescheduling or changing the amount or payment method of a recurring payment.

Can Bonza automatically update expired cards?

No. Bonza surfaces payment methods approaching expiry in the context of upcoming payment activity so a person can review them. It does not include an automatic card updater.

Does Bonza automatically retry failed recurring payments through another gateway?

No. Bonza does not perform automatic gateway failover or smart routing between providers. Payment activity runs through the gateway configured for that arrangement.

How do refunds and customer credits relate to recurring payments?

Refunds and customer credits stay connected to the same customer relationship as the recurring activity, so post-payment changes remain visible in context. How an available credit is applied to future payment activity depends on your configuration.

Your Payments Repeat. Your Team Shouldn't Repeat the Work.

See how Bonza Payments helps you manage recurring customer payments, upcoming activity, receivables and payment-method attention inside Salesforce.

See Recurring Payment Management in Action Book a Bonza Payments Demo