Dunning and payment retry management

Chargify tracks failed and declined payments through configured dunning schedules that retry charges and notify customers before service is paused. A Beam agent monitors these dunning events as they fire, reads the retry outcome and customer payment history, and updates the account or subscription status once a charge succeeds or a grace period ends. Where a customer disputes a charge, requests a refund, or repeatedly fails payment after retries, the agent stops and hands the case to a person on the billing team, so decisions about canceling or crediting an account stay with someone accountable for the relationship.

Usage based and metered billing

Many Chargify plans bill on usage, such as API calls, seats, or transaction volume, alongside a flat subscription fee. A Beam agent reads usage events as they are recorded, checks them against the customer's plan terms, and updates the upcoming invoice line items to reflect actual consumption. It can also flag accounts approaching a plan limit or unusual spikes in usage compared to prior periods. When usage figures look inconsistent with account history, or a customer disputes a metered charge, the agent routes the invoice to a billing team member for review before it goes out.

Subscription and invoice reporting

Chargify stores subscription status, invoice history, and revenue data for every account, covering upgrades, downgrades, cancellations, and renewals. A Beam agent reads this data on a schedule or when a subscription event occurs, compiles it into a revenue or churn summary, and updates a shared report or notifies finance of the change. It applies the reporting rules a customer has approved, such as which plan changes count as expansion or contraction revenue. Where a subscription event does not match any approved rule, such as a manual credit or an unusual contract term, the agent flags it for a person to classify.