Skip to main content
A Billing Period is two things together: Monthly on the 15th means every account carrying that period bills on the 15th of each month. Weekly works the same way against the day of the week. That is the whole definition. A Billing Period decides when, and nothing else.

​
Where it is attached, and what inherits it

A Billing Period is attached to a Plan — a Pricing Module marked subscribable. From there it travels down without being restated:
When a customer subscribes to a Plan, they begin billing on that Plan’s period automatically. Nothing further is configured on the subscription.
All four must share the same Billing Period. A Billing Account cannot hold subscriptions billing on different cycles, and a Billing Group cannot mix accounts billing on different days.This is what lets the billing orchestrator open a Bill Term over a whole Billing Group at once — it knows every account inside it falls due on the same day.

​
Billing Configuration

The Billing Period is one part of a Billing Configuration — a separate entity from the Pricing Module itself, created independently and then attached to it. It is required when a module is marked Plan. Like Rate Cards and Charges Rules, a Billing Configuration is reusable: the same one can be attached to many Plans rather than being recreated for each. It carries three things:
Billing Configuration doesn’t have versioning yet (tracked as a backlog item). Until it ships, editing the billing day, a dunning interval or the grace period affects every Plan it’s attached to, and their existing subscribers, instantly.
Full details on Dunning Configuration and Late Payment Configuration to be filled in.