Introduction
Subscription billing on Clarity Payment Hub runs recurring, scheduled, and automated payments natively, and every charge posts directly to your ERP. There is no bolted-on subscription billing add-on with a separate ledger to reconcile. Monthly membership dues, annual maintenance contracts, quarterly service fees, installment payment plans, auto-pay on invoice, balance top-ups, and usage-triggered charges all run from one payment layer that posts to the correct customer and GL in your ERP. Recurring billing, failed-payment recovery, retry logic, card updates, and customer notifications are built into Payment Hub rather than stitched together across a separate subscription tool and a payment stack.
Native subscription billing: one system, one source of truth
Most businesses that need recurring or scheduled payments reach for a subscription-management tool such as Chargebee, Zuora, Recurly, Stripe Billing, or Maxio, and bolt it on top of their existing payment stack. That pattern solves the charge-on-a-cadence problem but creates a new one: a separate subscription ledger to reconcile back to the ERP, a separate customer record that drifts from the ERP master, and a separate cash-receipt posting path that usually needs manual CSV work or custom integration code. The tool meant to simplify ends up adding operational complexity.
Clarity Payment Hub works differently. Recurring, scheduled, and automated payments are built into Payment Hub, and every charge writes directly to the ERP through Clarity Connect. The customer master is the ERP. The invoice record is the ERP. The cash receipt is the ERP. Payment Hub runs the schedule engine, the retry and dunning logic, the card-updater integration, and the customer notifications, then posts the results into the ERP's existing recurring-invoice and revenue-recognition records.
The difference from standalone subscription billing software is where the billing system lives. A subscription billing platform like Chargebee, Zuora, or Recurly keeps its own ledger, its own pricing models, and its own customer record, then leaves your team to reconcile it back to the ERP. Payment Hub keeps one system of record. Your customers pay through Payment Hub, the recurring logic runs inside it, and every charge writes to the ERP. You operate one billing model, one set of pricing tiers, and one source of customer data for every subscription you run.
Three payment patterns: recurring, scheduled, automated
Subscription billing is shorthand for three payment patterns that share one trait: the charge does not need a customer action at the moment of payment. Payment Hub handles each as its own configurable pattern, and most organizations run all three across different parts of the business.
Recurring
A customer enrolls in a subscription, and Payment Hub charges the configured amount on the configured interval until cancellation. The card or ACH method on file is tokenized once and reused for every cycle. This covers monthly SaaS and service fees, quarterly maintenance contracts, annual membership dues, recurring licensing or access fees, and monthly utility-style billing. The recurring charge engine owns the schedule, so the customer does nothing after enrollment.
Scheduled
A scheduled payment is a single future-dated charge, such as charging a card on July 15, or an installment sequence, such as twelve monthly payments of $1,000 starting next month. Payment Hub fires each scheduled charge at the configured time with the stored payment method. Tuition payment plans, patient medical-billing installments, legal retainer milestone payments, paid-in-full future-dated scheduling, and down-payment plus balance schedules all fit this pattern.
Automated
An automated payment runs when an event happens rather than on a clock. Invoice auto-pay fires when an invoice lands, a balance top-up recharges when a balance drops below a threshold, a contract renewal charges when an anniversary is reached, and a usage-threshold charge fires when usage exceeds a configured limit. The pattern also covers contract anniversary renewals, usage-metered overage charges, and shipment-triggered captures from order deposits. All three patterns share the same tokenized method store, the same retry logic, the same card-updater integration, and the same posting path into the ERP.
Payment Hub supports the pricing models a subscription business actually uses: fixed monthly plans, pricing tiers, per-seat pricing, and usage-based billing. Usage charges, metered pricing, and recurring-revenue models run from the same engine, so the subscription model you sell is the billing model you operate. Price changes, plan upgrades, and new tiers post to the ERP, so revenue recognition stays accurate as your pricing evolves.
Native vs bolt-on: the operational difference
The choice between native subscription billing and a bolt-on tool comes down to how many ledgers, admin surfaces, and reconciliation cycles you are willing to run.
One system, one ledger
With native subscription billing on Payment Hub, charges post directly to ERP invoices and the general ledger. There is one admin surface, one audit trail, and one security model. Revenue recognition runs through the ERP's existing logic, so there is no monthly sync or reconciliation overhead. The subscription billing implementation is part of the Payment Hub go-live rather than a separate project, and retries, recovery, and notifications are baked in with no third-party scripting.
Two systems, two ledgers
With a bolt-on subscription tool, the subscription system keeps its own schedule and payment ledger. The customer master exists in both systems, so drift is the default. Cash-receipt posting to the ERP requires sync, CSV work, or integration code. There are two admin surfaces, two audit trails, and two security scopes. Revenue recognition often requires a dedicated third tool, and the two systems need monthly reconciliation. Implementation and configuration are a separate effort, and dunning and retry live in the subscription tool, disconnected from AR collections.
The bolt-on pattern makes sense for certain businesses: SaaS-native companies with no ERP, startups running on Stripe from day one, and companies with unusually sophisticated subscription mechanics such as complex metered charges, usage-based contracts, or consumption-model SaaS that justify a dedicated subscription-management platform. For the mid-market business with an ERP that already does recurring invoices, the operational-debt math tilts hard toward native: every subscription your team manages costs less to operate when the subscription, the invoice, and the cash receipt all live in one system.
The payoff shows up in the numbers. Cash flow becomes more predictable, month-end reconciliation disappears, and the finance team does not grow as the subscription base does. Recovered declines drop straight to revenue, and customers who would have lapsed on a failed card stay enrolled. Because Payment Hub runs on top of the ERP you already have, a new plan or price change goes live without re-platforming.
How Payment Hub powers subscription billing natively
Eight capabilities make subscription billing work end to end, from enrollment through failed-payment recovery, card updates, and customer self-management. All are built into Payment Hub, and all write to the ERP in real time.
Schedule engine
A central scheduler fires recurring, scheduled, and automated charges at the configured time. It handles timezone awareness, daylight-saving transitions, leap-year edge cases, and business-day-only scheduling. Failed fires retry automatically per the retry configuration, so a missed billing cycle does not need manual intervention.
Tokenized method vault
Cards and ACH credentials tokenize at the gateway vault on first capture and are never stored on Payment Hub servers or the ERP. Payment Hub works with the major payment gateways, so customers keep the payment methods they already use. Every later charge uses the token, which is how recurring charges run without re-entry. Network Tokens from Visa and Mastercard are supported where the gateway exposes them, so a stored credit card stays current as it is reissued.
Dunning and retry logic
A configurable retry cadence handles soft declines, typically Day 2, Day 5, and Day 10 with exponential backoff, before escalation. Hard declines flag for customer portal-based resolution. Customer notifications by email and SMS fire automatically for each declining event, so failed payments are worked the moment they happen rather than at month-end.
Account Updater integration
For gateways and card brands that support Account Updater services, including Visa VAU, Mastercard ABU, American Express, and Discover, tokens auto-refresh when the issuer reissues a card. Most expirations resolve without any customer action, because the reissued credit card replaces the old token transparently.
Proration and mid-cycle changes
Subscription upgrades, downgrades, add-ons, and cancellations pro-rate the current cycle and adjust the next cycle's amount. Changes post to the ERP so that invoice and revenue-recognition records stay accurate. The customer sees the prorated math on the next statement, and the billing cycle stays aligned with the ERP's books.
Self-service enrollment and management
Customers enroll, pause, change a payment method, or cancel from the self-service portal. Your team sees enrollment status and can enroll or unenroll a customer directly. One audit trail records who made each change, so subscription management lives in one place instead of phone notes and spreadsheets.
ERP-native invoice generation
Recurring invoices can be generated by the ERP on its own schedule, the invoice-first pattern, with Payment Hub charging against each new invoice. They can also be generated by Payment Hub and written to the ERP at the same time, the charge-first pattern. Both patterns are supported, and most mid-market deployments use invoice-first because the ERP already owns recurring billing for its other revenue.
Dashboard and MRR reporting
The subscription dashboard shows active subscriptions, upcoming charges, the dunning queue, MRR and ARR where relevant, churn indicators, and failed-payment trends. The customer portal shows each customer their subscription status, next charge date, payment method, and history. Exports feed your accounting system, so the numbers tie back to your books.
Most of this work is mechanical today: rekeying card details, chasing failed charges, reconciling cycles by hand. Payment Hub runs it on schedule instead. Methods tokenize once, charges fire on time, and the ERP stays in sync without manual data entry.
A subscription workflow: enrollment to renewal
A worked example. A customer enrolls in a $499 monthly maintenance subscription through the self-service portal. Payment Hub fires the charge every 15th of the month for eleven months, handles one declined payment with a successful retry, refreshes the token when the card is reissued, and renews at the anniversary, with no staff involvement and real-time ERP posting at each step.
Customer enrolls in the portal. The customer (Acme Manufacturing) logs into the self-service portal and selects a maintenance plan at $499 per month, billed the 15th of each month. The customer enters a Visa corporate card. Payment Hub tokenizes it at the gateway vault, creates a subscription record, and writes the enrollment to the ERP as a customer record plus a recurring-invoice schedule.
Month 1, first charge fires. On the 15th at 7:00 AM CT, Payment Hub's scheduler fires the first charge. The ERP has already generated the recurring invoice (INV-40821) for $499. Payment Hub identifies the credit card as Visa Corporate, applies Level III enrichment with line items pulled from the recurring-invoice definition, and captures $499. Clarity Connect posts the cash receipt to the invoice, and the ERP closes INV-40821. The customer receives a receipt email.
Months 2 to 6, successful recurring charges. Each month on the 15th, Payment Hub fires the $499 charge against the tokenized method. Each month the ERP's recurring-invoice engine generates a fresh invoice record, and each month Payment Hub captures, posts the cash receipt, and emails the customer. There is no staff involvement and no manual reconciliation. All charges are Level III enriched, and interchange savings are logged per transaction.
Month 7, declined payment and dunning. Month 7's charge declines as a soft decline for insufficient funds. Payment Hub marks the subscription as in-dunning, emails the customer a reminder, and schedules a Day 2 retry. The Day 2 retry also fails. The Day 5 retry succeeds: $499 captures, INV-41021 closes, and the customer receives a retry-success notification. The dunning status clears, and the failed payment never becomes a churn event.
Month 8, card reissued and Account Updater refreshes silently. The customer's issuing bank reissues the corporate Visa with a new expiration and number on the same account. Visa's Account Updater service pushes the updated token to the gateway, and Payment Hub's stored token auto-refreshes. Month 8's charge fires against the refreshed token without the customer or your staff doing anything. The customer is unaware the credit card number changed.
Months 9 to 11, autopilot continues. Three more months of successful recurring charges follow. The total so far is eleven successful charges of $499, or $5,489 captured. Each month carries Level III-qualified transactions, at roughly $5 to $8 of interchange savings per charge, for roughly $60 to $90 of Level III recovery on this subscription year to date.
Month 12, anniversary renewal. On the twelve-month anniversary, Payment Hub's automated renewal logic fires. The subscription renews automatically unless the customer has canceled or downgraded in the portal. A renewal confirmation email goes to the customer 30 days in advance, giving them opt-out time. The renewal price honors any annual-commitment step-up configuration.
Ongoing, the controller reviews the subscription dashboard. The controller opens Payment Hub's subscription dashboard periodically. Active subscriptions are visible with next-charge dates. MRR and ARR metrics are up to the minute. The dunning queue is visible with retry-scheduled dates, and the failed-subscriptions queue is visible with aged items for AR attention. Across more than 400 active subscriptions, the whole operation runs with one controller spending roughly 20 minutes a week on exception review, not the weeks of reconciliation work a bolt-on system would demand.
Dunning and retry logic: recovering the declines that would otherwise churn
Roughly 5 to 15 percent of card charges decline in any given month for soft reasons: insufficient funds, a temporary network issue, an issuer fraud hold, or an expired card. Without retries, each one is a potential churn event. Payment Hub's retry ladder is configurable and ships with a default that recovers 60 to 75 percent of soft declines without anyone touching them, which protects recurring revenue that would otherwise leak to involuntary churn.
Hard declines, a card that is closed, stolen, or reported, skip the ladder and go to the customer-portal resolution flow. The customer gets an email with a one-click link that signs them in and lets them replace the payment method without re-enrolling the subscription.
Expiring cards are a predictable event, not a surprise decline. Payment Hub sends reminders by email at 30, 15, and 7 days before expiration with a portal link to update. With Account Updater silently refreshing reissued cards, fewer than 20 percent of expiring cards need any customer action.
Industries where subscription billing shows up
Recurring revenue is broader than the monthly SaaS charge. Maintenance contracts, dues, tuition, utility bills, medical payment plans, services retainers, and installment arrangements all need recurring, scheduled, or automated payments.
Maintenance and Service Contracts
Equipment-maintenance contracts, HVAC service plans, IT managed services, facility maintenance, and pool, pest, or landscape recurring services all fit here. Billing runs monthly or quarterly against a pre-signed service agreement with auto-renewal on the anniversary. Common examples include industrial equipment maintenance, HVAC, plumbing, and electrical service plans, and IT managed-services subscriptions.
Membership and Association Dues
Trade associations, professional societies, fraternal organizations, fitness clubs, country clubs, and homeowner associations bill annual dues with autopay enrollment, monthly recurring charges for smaller organizations, and event-triggered renewal reminders. Typical cases include trade and professional association dues, membership organization billing, and HOA or club recurring fees.
Education, Tuition and Fees
K-12 tuition payment plans, higher-ed installment billing, continuing-ed registration, and test-prep or tutoring subscriptions all rely on this infrastructure. Scheduled installment sequences such as 10-month or 12-month tuition plans dominate, alongside recurring monthly programs. Examples include K-12 tuition payment plans, higher-ed installments, and tutoring or enrichment subscriptions.
Government and Utility Billing
Municipal water, gas, and electric utility billing with monthly statements and autopay enrollment fits this pattern, along with permit renewal subscriptions and parking or licensing annual renewals. Constituent-facing autopay is the dominant pattern, covering municipal utility monthly billing, permit and license annual renewal, and park or recreation membership.
Healthcare, Payment Plans
Patient medical billing payment plans for large post-insurance balances are a core use. Scheduled installment sequences let patients pay a large balance over 6 to 24 months, and recurring charges cover ongoing services such as physical therapy, orthodontics, and chronic-care subscriptions. Examples include medical balance installment plans, ongoing therapy or treatment subscriptions, and dental orthodontic payment plans.
Professional Services Retainers
Legal retainers, accounting and advisory monthly retainers, and consulting engagements run on recurring monthly or quarterly retainer charges plus scheduled milestone payments for project-based work. Typical cases include law firm monthly retainers, CPA ongoing advisory arrangements, and consulting managed-engagement fees.
Distribution and B2B Auto-Pay
Repeat B2B distribution customers enroll in invoice auto-pay, where every invoice generated by the ERP on the customer's orders fires an automatic charge against the tokenized method. Here the recurring element is auto-pay on every invoice, whatever its size, covering repeat B2B customer auto-pay, supply-contract recurring orders, and managed-inventory replenishment.
SaaS-Native and Pure Subscription Businesses
Pure-play SaaS companies with complex usage-based billing, consumption pricing, multi-tier pricing, and revenue-recognition complexity are a distinct case. Payment Hub handles the payment side, and for complex pricing mechanics such as usage, meters, and tiered models, some SaaS-native companies pair Payment Hub with a dedicated subscription-management platform. This is best assessed per case, and it covers usage-metered SaaS, consumption pricing models, and complex multi-product pricing.
Frequently Asked Questions
Does Payment Hub have native subscription billing, or is it a bolt-on?
Native. Payment Hub has built-in capabilities for recurring payments (subscription-style charges on any cadence), scheduled payments (future-dated single charges or installment sequences), and automated payments (event-triggered charges like invoice auto-pay, balance top-ups, or contract-renewal charges). The recurring schedule, retry logic, dunning, card-update handling, and customer notifications are all part of Payment Hub, not a separate add-on with its own ledger.
Because the charges post directly to your ERP through Clarity Connect, the subscription, invoice, and cash-application record stays in one place: your ERP. You do not need a separate subscription-management system such as Chargebee, Zuora, or Recurly bolted on top with its own reconciliation burden.
What billing cadences are supported for recurring payments?
Any. Daily, weekly, bi-weekly, monthly, quarterly, semi-annual, annual, and custom intervals (every 45 days, every 3rd Tuesday, every quarter-end, and so on). Within a given subscription, the amount can be fixed (the same amount each cycle), variable (based on usage or metered data pulled from the ERP), pro-rated (for mid-cycle enrollment or cancellation), or stepped (price increases at the anniversary).
Payment Hub runs the scheduler centrally and fires charges at the configured time with correct timezone handling. Holiday and weekend-aware scheduling is configurable: you can choose to fire on the scheduled date regardless, skip weekends, or use business-day-prior-if-weekend logic, depending on your customer preference.
What happens when a card on file fails (decline, expiration, and similar)?
Payment Hub runs configurable dunning logic. On a soft decline (insufficient funds, temporary hold, network timeout), it retries automatically on a configurable schedule, typically Day 2, Day 5, and Day 10, with exponential backoff. On a hard decline (card closed, stolen, reported), it marks the subscription as payment-failed and triggers the customer-notification workflow.
Expired cards are caught in advance: 30, 15, and 7 days before expiration, the customer receives a reminder email to update the payment method through the self-service portal. Account Updater services, where supported by your gateway and card brand, auto-refresh the token when the issuer reissues a credit card, so most expirations resolve without any customer action needed. If all retries and updates fail, the subscription escalates to your AR team with the exception flagged in the dashboard.
How does recurring billing integrate with our ERP's invoice generation?
Two patterns are supported. First, invoice-first: your ERP generates the recurring invoice on its own schedule (NetSuite, Acumatica, Dynamics, and Sage all have native recurring-invoice capabilities). Payment Hub sees the new invoice land in the ERP, matches it to the customer's stored recurring-payment subscription, and fires the charge automatically. The cash receipt posts back to the invoice.
Second, charge-first: Payment Hub's scheduler fires the recurring charge at the configured cadence and writes the invoice and the cash receipt to the ERP at the same time. Both patterns work, and the choice depends on which system your operations team prefers to own the subscription-schedule record. Most mid-market deployments use the invoice-first pattern because the ERP is the system of record for billing; the charge-first pattern is more common in subscription-native businesses where Payment Hub is the primary subscription source.
Can customers self-enroll in autopay through the portal?
Yes. Customers enroll from the self-service payment portal: pick a saved tokenized method, pick a rule (every invoice auto-pays, every invoice over a set amount auto-pays, a fixed monthly auto-pay amount, and so on), review terms, and confirm. Enrollment stores in Payment Hub's scheduler, and every triggering event fires the charge automatically.
Customers can pause, update, or cancel autopay anytime from the portal. Your AR team sees autopay status on each customer and can enroll or unenroll on behalf of a customer who prefers to handle it over the phone. Autopay enrollment is the most common way businesses move routine B2B invoice collection from chasing customers to automated charging.
Does this support installment payment plans for patient billing, tuition, or legal retainers?
Yes. Installment plans are a specific type of scheduled payment: take a large balance (say $12,000) and split it into a configured number of equal or custom installments on specific dates ($1,000 on the 15th of each month for 12 months, or four quarterly $3,000 payments, or one $4,000 down-payment plus eight monthly $1,000 payments). Payment Hub's scheduler fires each installment charge on its scheduled date using the stored payment method.
Missed installments follow the same retry logic. Plan completion is tracked and visible to both the customer (in the self-service portal) and your team. Common use cases include patient medical billing, K-12 tuition, higher-ed tuition, legal retainers with milestone payments, and B2B payment plans for past-due collections negotiations.
How is raw card data handled for recurring billing?
Raw PAN never touches Payment Hub, your servers, or your ERP. The initial card entry happens through a gateway-hosted iframe or JS-tokenization flow: the raw card number goes straight to the gateway's PCI-scoped vault and returns only a tokenized reference. That token is stored on Payment Hub's subscription record and used for every subsequent recurring, scheduled, or automated charge.
This keeps the deployment in lighter PCI SAQ scope (SAQ A or SAQ A-EP rather than the much heavier SAQ D). For ACH, the routing and account numbers follow the same pattern: tokenized at the gateway vault, never stored in plaintext on Payment Hub or ERP systems.
Can we do free trials, promotional pricing, or mid-cycle changes?
Yes. Free trials: a subscription enrolls with no charge for a set number of days, then starts charging at the configured cadence once the trial expires, and trial-end reminder emails go to the customer automatically. Promotional pricing: the first several cycles run at a discounted rate, then step up to standard, supported as a built-in subscription configuration.
Mid-cycle changes: upgrade, downgrade, or add-on changes can pro-rate the current cycle and update the next cycle's amount, and cancellation can be immediate, at end-of-current-cycle, or at a specific future date. All changes post to the ERP for invoice and revenue-recognition consistency.
Do recurring charges qualify for Level III interchange savings?
Yes. On any subscription paid via commercial card (Visa or Mastercard Corporate, Purchasing, Fleet, Government, or Business), Payment Hub applies Level III enrichment at the recurring-charge time. Line items (subscription description, term dates, SKU), tax, freight (typically zero for subscriptions), customer code, and destination ZIP are pulled from the subscription record and the underlying invoice in your ERP and packaged into the Level III envelope.
For a subscription-heavy business with B2B and B2G customers paying via commercial cards, Level III savings on recurring charges often represent 30 to 50 percent of total Level III recovery, each month, every month, compounding over the subscription lifetime.
What does the customer see for their subscription status?
From the self-service portal, the customer sees their active subscriptions (name, amount, cadence, next charge date), the saved payment method being used, payment history (successful charges and any failed or retried charges), upcoming renewals, and any scheduled installment sequences they are on. They can update the saved method, pause or cancel subscriptions, enroll in additional ones, or change cadence where policy permits.
Your team sees the same information plus operational context: dunning-retry-scheduled status, the failed-subscription escalation queue, upcoming card expirations, and Account Updater refresh history. The audit trail captures every change with who, when, and what.
Can subscription prices be variable or usage-based?
Yes. For usage-metered subscriptions, Payment Hub pulls the usage data from your ERP (or from a third-party metering source you have integrated) at charge time and calculates the cycle amount. For example, a managed-IT-services customer subscribed to a $500 base plus $0.10 per seat per month: Payment Hub queries the current seat count from the ERP on the 15th of each month and charges $500 plus the current seat count times $0.10.
For especially complex usage-based or consumption-based SaaS pricing with sophisticated metering, some businesses still pair Payment Hub with a dedicated subscription-management tool (Chargebee, Zuora, or Recurly) for the billing complexity, and Payment Hub then handles the payment-acceptance side of the resulting invoices. For simpler usage patterns (seat-based, capacity-based, quantity-based), Payment Hub handles the whole thing natively.
How long does a subscription-billing deployment take?
The core Payment Hub deployment takes 48 hours once ERP and gateway credentials are in place. Configuring specific subscription products (pricing, cadence, trial rules, proration logic, and retry configuration) typically takes another few days of focused configuration work depending on complexity. Migrating existing recurring customers from a prior system (if you are replacing a bolted-on tool like Chargebee, Zuora, or Recurly) takes additional time for data migration, but Payment Hub's scheduler can accept an import of existing subscription schedules with their saved tokens.
For net-new subscription billing (not migrating from a prior tool), expect 1 to 3 weeks to go live with a full subscription product catalog and customer self-service enrollment in place.