Billing Fundamentals

Last verified with: 10.8.6.0

Overview #

LogiSense Billing is designed to give organizations control over both when customers are billed and how billing operations are executed.

That matters because billing is not just about calculating charges. It is also about organizing customer populations, aligning billing to commercial agreements, controlling invoice timing, deciding when collections or enforcement should occur, and creating an operating model that works for the business.

The key concepts that shape this model are:

Account Bill Day,
Billing Frequency,
Bill Groups,
and Bill Runs.

Together, these capabilities let businesses support recurring, usage-based, and contract-related billing while still deciding how to segment customers and how much of the billing workflow should run at a given time.

The Core Billing Model #

At a business level, the billing model works like this:

An account is assigned a bill day.
Products and services carry pricing frequencies that determine how often they should bill.
Accounts are grouped into bill groups for operational segmentation and default billing behavior.
Bill runs are used to execute selected billing workflows against selected bill groups.

This creates a flexible model where timing, customer segmentation, and operational processing are connected, but not rigidly locked together.

That is one of the strengths of the platform. Businesses can control the commercial timing of billing while also controlling the operational way billing is run.

Account Bill Day #

The Account Bill Day is one of the most important billing concepts in the platform.

It determines the day of the month on which an account is billed for recurring services and packages, unless a more specific override is in place. In simple terms, it defines the anchor point for the customer’s recurring billing cycle.

Bill days can be configured from 1 through 28, which gives businesses a predictable monthly billing anchor while avoiding the complications of shorter calendar months.

For example:

an account with a bill day of 1 may bill on the first day of each applicable billing period,
while an account with a bill day of 15 may bill mid-month instead.

This matters because many businesses need to align billing with customer onboarding, contract terms, operational cycles, or financial preferences.

The platform also supports the idea that not every charge must always follow the exact same anchor. In some cases, package-level timing can override the account-level bill day when a specific service or offer needs its own billing cadence.

Usage Bill Day #

In addition to the general account bill day, the platform also supports a Usage Bill Day concept.

This is valuable in businesses where recurring subscription charges and usage charges do not need to bill on exactly the same rhythm. It gives organizations additional control over when usage is invoiced relative to the broader account billing cycle.

That flexibility can be especially useful when a business wants one operational rhythm for recurring subscription charges and another for metered usage settlement.

Billing Frequency #

Billing Frequency determines how often a priced item should bill.

This is typically defined on the priced offer itself, such as a package or recurring price, and works together with the account bill day to determine the billing cadence.

Examples include:

monthly billing,
quarterly billing,
annual billing,
or one-time charging.

This is important because frequency answers a different question from bill day.

Bill day answers: “On what day should billing happen?”
Billing frequency answers: “How often should this item bill?”

Together, they allow the business to create predictable recurring cycles while still supporting different commercial models across the product catalog.

How Bill Day And Frequency Work Together #

From a business perspective, the interaction is straightforward:

A product or service has a defined billing frequency.
The account has a bill day that acts as the cycle anchor.
The platform bills that item whenever its next bill date aligns with the applicable billing period.

This gives businesses a consistent way to support mixed commercial offers on the same platform.

For example:

one customer may have a monthly recurring offer,
another may have annual platform fees,
and another may combine recurring subscriptions with arrears-based usage.

The billing framework can support all of these without forcing every customer into the same cycle.

Proration And Billing Alignment #

Because customers do not always start on a clean cycle boundary, billing often needs to handle partial periods.

LogiSense Billing supports proration behavior so newly added recurring services can be aligned to the account’s billing cycle instead of forcing a custom billing date forever. This is valuable because it helps businesses keep customer billing predictable while still charging fairly for partial periods.

That means organizations can onboard customers on any day of the month while still converging them onto the billing pattern that makes operational sense.

Bill Groups #

Bill Groups are used to segment accounts for billing operations.

A bill group is a reusable grouping of accounts that are intended to be billed in a similar way. That similarity can reflect timing, invoice configuration, delivery behavior, operational workflow, or other business logic.

Bill groups are powerful because they let businesses organize billing populations deliberately instead of treating the entire customer base as one undifferentiated billing run.

Examples of why customers may be placed in different bill groups include:

different billing days,
different invoice delivery methods,
different invoice templates or delivery settings,
different payment or collection strategies,
different customer classes,
or different operational handling across markets or channels.

This provides a clean way to segment billing operations without duplicating the entire billing model for every customer type.

What Bill Groups Control #

Bill groups act as a default billing and invoicing framework for the accounts assigned to them.

They can carry default values such as:

bill day,
usage bill day,
invoice delivery behavior,
invoice date handling,
and invoice due-date behavior.

This is useful because many organizations want a consistent default operating model for a given customer segment, while still allowing account-level exceptions where needed.

That balance is important. Bill groups create standardization, but they do not eliminate flexibility.

Why Bill Groups Matter #

Bill groups matter because operational billing is rarely one-size-fits-all.

A business may want to:

bill enterprise customers on one cycle and SMB customers on another,
process ACH and credit card customers differently,
separate reseller populations from direct customers,
or stage billing operations across different waves instead of billing the whole customer base at once.

Bill groups make that possible.

They help organizations scale billing operations while keeping customer segmentation clear and manageable.

Bill Runs #

Bill Runs are the operational mechanism used to execute billing.

This is one of the most important concepts for understanding how the platform works. Billing does not simply happen because a date exists on an account. A bill run is what actually initiates the process.

Bill runs are associated with bill groups, and those bill groups determine which accounts are evaluated. The bill run then checks which accounts, packages, services, usage, invoices, and related processes should actually be actioned based on the configured bill period and the enabled run options.

This means bill runs are not just a timer. They are a workflow controller.

What A Bill Run Can Do #

A bill run can be configured to perform different combinations of billing operations, including:

billing recurring packages,
billing usage,
executing contract-related charges,
running accounts receivable or dunning rules,
compiling invoice balances,
collecting payments,
rendering invoices,
and delivering invoices.

This is one of the biggest operational strengths of the platform. Businesses do not have to treat billing as one indivisible job.

They can decide whether a given run should:

create charges only,
create and invoice charges,
invoice without immediate collection,
collect payments as part of the same workflow,
execute dunning or enforcement separately,
or run downstream document and delivery steps at the appropriate time.

Bill Period Start And End #

Bill runs use a Bill Period Start and Bill Period End range to determine which applicable bill dates fall into the run.

This gives administrators control over the billing window being processed. Instead of simply pressing “bill now” in a generic way, the business can define the billing period that the run should evaluate.

That becomes especially useful when running:

one-time catch-up runs,
scheduled recurring runs,
separate operational waves,
or special runs for selected groups of customers.

Billing As A Staged Operational Process #

One of the key business ideas behind bill runs is that billing can be staged.

Organizations often do not want every billing-related action to occur in one monolithic step. They may want one run to calculate charges, another to finalize invoices, and another to collect payment or execute enforcement processes.

This staged model supports several practical goals:

tighter operational control,
easier exception management,
better coordination with finance operations,
cleaner payment collection workflows,
and better support for customers with different billing arrangements.

It also helps teams align billing runs with internal review, reconciliation, and support processes.

Billing, Invoicing, Enforcement, And Collection #

A useful way to think about bill runs is to separate the major operational phases:

Charge Creation #

This is where recurring and usage charges are calculated and applied.

Benefit:

lets the business determine what the customer owes for the billing period.

Contract And Commitment Evaluation #

This is where commitment shortfalls, top-up behavior, or contract-related charges can be applied when configured.

Benefit:

ensures contractual commercial terms are reflected in the billing outcome.

Accounts Receivable Terms And Enforcement #

This is where dunning-style actions such as penalties, reminders, or suspension-related behavior can be executed.

Benefit:

supports revenue protection and receivables enforcement as part of the operating model.

Invoicing #

This is where charges are compiled into invoiceable balances and invoice documents are prepared or finalized.

Benefit:

turns billing results into customer-facing financial documents.

Payment Collection #

This is where payment can be collected for eligible accounts, such as accounts configured for automatic payment methods.

Benefit:

supports a more complete quote-to-cash or bill-to-cash workflow.

Rendering And Delivery #

This is where invoices are finalized and then delivered according to the configured delivery settings.

Benefit:

completes the customer communication step of the billing process.

Why This Flexibility Matters #

Different businesses want different billing operating models.

Some organizations want a streamlined approach where billing, invoicing, rendering, delivery, and collection all happen together. Others want more separation, for example:

billing overnight,
finance review in the morning,
invoice rendering later,
and payment collection in a distinct process.

Some also want dedicated daily runs for enforcement or payment collection that are separate from the recurring billing cycle itself.

LogiSense Billing supports those operating styles because bill runs can be configured as a flexible execution layer instead of a single fixed process.

Telecom And SaaS Examples #

Telecom Example #

A telecom provider may use different bill groups for enterprise customers, consumer customers, and reseller channels. Each group may have different bill days, invoice delivery rules, and operational billing schedules.

The provider might then use:

one recurring bill run to generate recurring and usage charges,
one daily run to execute dunning or suspension rules,
and another run to collect payments for autopay accounts.

Benefit:

supports scale, segmentation, and revenue protection across a diverse customer base.

SaaS Example #

A SaaS business may group self-service customers separately from enterprise contract customers. Self-service customers may use a more automated billing and payment collection workflow, while enterprise customers may require different invoice timing and payment handling.

The business can use bill groups to separate those populations and bill runs to define different operational workflows for each segment.

Benefit:

supports multiple go-to-market motions without rebuilding the billing model.

Why Customers Value This Capability #

Customers value these billing fundamentals because they provide both commercial control and operational control.

The platform does not just let businesses define what should bill. It also lets them define:

when customers should bill,
how often charges recur,
how customer populations are grouped,
which actions happen in a billing run,
and how billing, invoicing, enforcement, and collection should be staged.

That flexibility is what allows organizations to run billing in a way that matches their business model, their finance processes, and their customer experience goals.

The Bigger Business Benefit #

Billing fundamentals may sound simple, but they are what make large-scale billing operations manageable.

Account bill days create timing control. Billing frequency creates commercial cadence. Bill groups create operational segmentation. Bill runs create execution control.

Together, they give businesses the foundation to scale recurring and usage billing while still preserving flexibility in how billing operations are organized and run.ion was in as of the bill day to compute the invoice amount.

Still stuck? How can we help?