Subscription billing — native recurring, scheduled & automated payments, posted to your ERP

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 / cash-application record stays in one place: your ERP. You don't need a separate subscription-management system (Chargebee, Zuora, Recurly, Stripe Billing) bolted on top with its own reconciliation burden.

Any. Daily, weekly, bi-weekly, monthly, quarterly, semi-annual, annual, and custom intervals (every 45 days, every 3rd Tuesday, every quarter-end, etc.). Within a given subscription, the amount can be fixed (same $X each cycle), variable (based on usage / metered data pulled from the ERP), pro-rated (for mid-cycle enrollment or cancellation), or stepped (price increases at anniversary).

Payment Hub runs the scheduler centrally and fires charges at the configured time with correct timezone handling. Holiday/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.

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, 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 / 7 days before expiration, the customer receives a reminder email to update the 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 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.

Two patterns supported. (1) Invoice-first: your ERP generates the recurring invoice on its own schedule (NetSuite, Acumatica, Dynamics, Sage, etc. 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. Cash receipt posts back to the invoice.

(2) 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 simultaneously. Both patterns work; the choice depends on which system your operations team prefers to own the subscription-schedule record. Most mid-market deployments use pattern 1 because the ERP is the system of record for billing; pattern 2 is more common in subscription-native businesses where Payment Hub is the primary subscription source.

Yes. Customers enroll from the self-service payment portal: pick a saved tokenized method, pick a rule (every invoice auto-pays, every invoice over $X auto-pays, monthly auto-pay a fixed amount, etc.), review terms, confirm. Enrollment stores in Payment Hub's scheduler; 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 / 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.

Yes. Installment plans are a specific type of scheduled payment: take a large balance (say $12,000) and split it into N equal or configured 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 + 8 × $1,000 monthly). Payment Hub's scheduler fires each installment charge on its scheduled date using the stored payment method.

Missed installments follow the dunning retry logic. Plan completion is tracked and visible to both the customer (in the self-service portal) and your team. Common use cases: patient medical billing, K-12 tuition, higher-ed tuition, legal retainers with milestone payments, and B2B payment plans for past-due collections negotiations.

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 / SAQ A-EP rather than the much heavier SAQ D). For ACH, the routing / account numbers follow the same pattern — tokenized at the gateway vault, never stored in plaintext on Payment Hub or ERP systems.

Yes. Free trials: subscription enrolls with no charge for N days, then starts charging at the configured cadence once the trial expires — trial-end reminder emails go to the customer automatically. Promotional pricing: first N cycles at a discounted rate, then step up to standard — supported as a built-in subscription configuration.

Mid-cycle changes: upgrade / downgrade / add-on changes can pro-rate the current cycle and update the next cycle's amount; 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.

Yes — on any subscription paid via commercial card (Visa / MC Corporate, Purchasing, Fleet, Government, Business), Payment Hub applies L3 enrichment at the recurring-charge time. Line items (subscription description, term dates, SKU), tax, freight (typically 0 for subscriptions), customer code, and destination ZIP are pulled from the subscription record and the underlying invoice in your ERP and packaged into the L3 envelope.

For a subscription-heavy business with B2B / B2G customers paying via commercial cards, L3 savings on recurring charges often represent 30–50% of total L3 recovery — each month, every month, compounding over the subscription lifetime.

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, any failed / retried charges), upcoming renewals, and any scheduled installment sequences they're 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, failed-subscription escalation queue, card-expiration upcoming, Account Updater refresh history. The audit trail captures every change with who, when, what.

Yes. For usage-metered subscriptions, Payment Hub pulls the usage data from your ERP (or from a third-party metering source you've integrated) at charge time and calculates the cycle amount. Example: a managed-IT-services customer subscribed to $500 base + $0.10 per seat per month; Payment Hub queries the current seat count from the ERP at the 15th of each month and charges $500 + (current_seats × $0.10).

For genuinely complex usage-based / consumption-based SaaS pricing with sophisticated metering, some businesses still pair Payment Hub with a dedicated subscription-management tool (Chargebee, Zuora, Recurly) for the billing complexity — 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.

48 hours for the core Payment Hub deployment once ERP and gateway credentials are in place. Configuring specific subscription products — pricing, cadence, trial rules, proration logic, dunning configuration — typically takes another few days of focused configuration work depending on complexity. Migrating existing recurring customers from a prior system (if replacing a bolted-on tool like Chargebee / Zuora / Recurly / Stripe Billing) 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–3 weeks to go live with a full subscription product catalog and customer self-service enrollment in place.