Usage metering ingestion

Paigo records product usage events to bill customers accurately. A Beam agent reads incoming usage data, applies your rule for how events map to billable meters, and updates the running totals per account. Clean, expected usage flows straight into the meter, while readings that spike, drop to zero, or arrive malformed are held and flagged. Anomalies that could over- or under-bill a customer are routed to a person to confirm before they affect an invoice. The agent keeps meters current between billing cycles so charges reflect real usage without manual tallying by the finance team.

Invoice preparation

Paigo assembles invoices from metered usage and plan terms. A Beam agent reads the current usage totals and pricing rules, then drafts each invoice according to your approved logic. Standard invoices are prepared and queued for sending, and the agent notes any credits or adjustments it applied. Invoices with unusual amounts, disputed usage, or unfamiliar plan combinations are routed to a finance person to approve first. This lets recurring billing move forward on schedule while a human keeps final say over anything that looks off before it reaches the customer.

Failed payment handling

Paigo follows payment status against issued invoices. A Beam agent reads payment results, applies your rule for retries and dunning, and updates each account's billing state. When a charge fails, the agent schedules a retry or notifies the customer per policy and records the outcome. Repeated failures, large outstanding balances, or accounts flagged as sensitive are escalated to a person to decide on next steps. Routine retries and reminders run on their own, so the finance team steps in only where a real collection decision or exception is needed.