Pay many invoices at once — one customer click, per-invoice ERP posting

Consolidated payment is customer-initiated: one customer sits down, picks the specific invoices they want to pay right now, authorizes once, and the payment applies per-invoice in your ERP. Batch / scheduled payment runs are operator-initiated: AR or AP selects which invoices to push-debit against saved customer tokens on a schedule.

Clarity Payment Hub supports both patterns, but consolidated payment is the one customers actually use from the self-service portal — and it's what most B2B controllers mean when they say "I want to pay everything I owe you today."

In practice, as many as the customer wants. Payment Hub has been tested with single consolidated payments covering 300+ invoices without issue. Typical B2B month-end workflows are in the 20–80 invoice range when a controller is clearing the month's AP queue in one session.

The authorization is a single gateway transaction for the summed total (or two, on mixed-method batches); each invoice posts its own cash receipt to the ERP with its own line-item detail. If the total exceeds a gateway's per-transaction dollar limit, Payment Hub auto-splits into sub-authorizations while keeping the customer experience as one click.

Every eligible invoice in the consolidated batch gets its own Level 2/3 data enrichment — line items, tax, customer code, PO reference, freight, duty, product codes — pulled from your ERP and passed to the gateway. The interchange tier is protected on every qualifying commercial-card transaction in the batch, not averaged or dropped.

This is critical for B2B distributors and manufacturers where a month-end consolidated payment might cover $50K–$500K of commercial-card volume and Level 3 qualification per-invoice determines the savings. A typical distributor with $1M in monthly commercial-card volume saves ~$7,500 / month (0.75% of volume) with per-invoice L3 enrichment — worth protecting in every batch.

Yes. As part of the selection flow, customers see available account credits and credit memos alongside the open invoices. They can apply credits to any selected invoices (in full or partial), see the adjusted remaining balance, and pay the net amount in one authorization.

Payment Hub posts credit applications and cash receipts back to the ERP separately — credit applications as credit-memo closure entries, cash receipts as received-payment entries — so your AR aging, cash-application logs, and credit-memo closure all stay clean. The ERP sees the correct allocation per invoice.

Payment Hub supports mixed-method consolidated payments — a typical pattern is small invoices on a commercial card (for the Level 2/3 data and cash-back rewards) and large invoices on ACH (for the unit economics).

The customer selects a method per invoice sub-batch; Payment Hub runs two authorizations — one card, one ACH — and posts per-invoice cash receipts to the ERP regardless of which rail each invoice took. The customer sees a single consolidated receipt with per-invoice method breakdown.

The customer can adjust any invoice amount in the consolidated batch before authorizing — for example, paying $9,500 of a $10,000 invoice with a short-pay reason code — and the other selected invoices pay at their full amounts.

Payment Hub applies the short-pay with reason code to the specific invoice, leaves the remaining $500 open in the ERP (with the reason code attached), and routes the short-pay exception to your AR worklist for follow-up. The rest of the batch clears cleanly. Dunning resumes only on the unpaid balance of the short-paid invoice.

Both — on request. Payment Hub emails a consolidated receipt to the customer covering the entire authorization with a per-invoice breakdown (invoice number, amount, method, receipt confirmation).

Customers who also need individual invoice-level receipts for their AP records can download them from the portal or request them by email. On the ERP side, each invoice has its own cash-receipt record for audit; the consolidated authorization is also linked for reconciliation.

Where compliant surcharging is enabled, Payment Hub applies the surcharge only to the card portion of the consolidated batch (ACH never surcharged; debit and prepaid cards excluded). The surcharge is shown to the customer before authorization, tracked as a separate ERP line per invoice, and state-by-state network rules are enforced automatically. The ACH portion clears at the base invoice amount without surcharge.

Yes. Role-based thresholds are configurable per customer contact and per customer account. A typical policy: AP clerk up to $10K per consolidated batch, controller up to $250K, CFO or owner for larger amounts. Payment Hub enforces the threshold at authorization time and routes larger batches to an approval flow if configured.

All Payment Hub gateway integrations support consolidated payment — the mechanic is Payment Hub's, not the gateway's. The gateway just sees a single card or ACH authorization for the total; Payment Hub handles the per-invoice fan-out on both the ERP side (cash-receipt posting) and the customer side (consolidated receipt with line detail).

Works identically across Worldpay, Adyen, Cybersource, Fortis, Elavon, PNC, PayTrace, Nuvei, Stripe, Braintree, Authorize.Net, Global Payments, NMI, USAePay, and the others in the supported library.

If all selected invoices are in the same currency, Payment Hub runs the batch in that currency through a gateway that supports it (Adyen, Stripe, Worldpay, Cybersource, and others support multi-currency processing). Mixed-currency batches are split — one authorization per currency — with per-invoice cash-receipt posting in the correct currency back to your ERP. Currency translation at the ERP side follows your ERP's own configured conversion logic.

Yes. The feature is configurable per customer segment — on by default for B2B commercial accounts, optionally off for specific segments where the single-invoice flow is preferred. This is most common for consumer-facing segments (patient-pay portals, donor giving pages) where the paradigm doesn't apply.