Last verified with: 10.8.6.0
Summary #
LogiSense Billing provides a full-featured billing engine that supports subscription billing, usage billing, invoice generation, invoice delivery, and dunning-related downstream processes. It gives businesses flexibility in how charges are timed, grouped, and billed across customer accounts and packages.
Why It Matters #
Billing is the operational core of monetization. It is the process that converts configured products, pricing, usage, and contracts into actual financial transactions that customers can be invoiced for and that finance teams can manage.
Business Problem It Solves #
Businesses often need billing operations to handle:
- different billing cadences across customers or products
- one-time, recurring, and usage-based charging together
- package-level timing differences within the same account
- invoice generation and delivery
- exceptions around timing, proration, and operational collections
LogiSense Billing supports these scenarios through configurable billing behavior at the account, package, and bill-run levels.
Core Concepts #
Account Bill Day #
Each account has a bill day that determines when billing should normally occur. This becomes the baseline timing for package and service billing unless a more specific override applies.
Package Bill Day And Frequency #
Packages can define their own bill timing and frequency, allowing businesses to decouple a specific offer from the account’s default billing cadence when needed.
Bill Runs #
Bill runs are the operational mechanism used to process billing activity. They allow billing activity to be executed in a controlled and repeatable way.
Invoice Presentment And Delivery #
Billing does not stop at charge calculation. The platform supports invoice generation and invoice delivery behavior so the customer-facing billing outcome is part of the same process.
Proration And Timing #
Billing behavior often depends on timing, lifecycle changes, and when a service or package becomes effective. Proration-related behavior is an important part of ensuring charges align with business intent.
How LogiSense Supports It #
LogiSense Billing supports billing through:
- account and package billing schedules
- package frequency configuration
- bill run execution and bill run history
- bill groups for shared billing behavior
- invoice generation and delivery flows
- alignment with payment and dunning processes
This lets a business standardize billing execution while still accommodating customer-specific or offer-specific differences.
Common Use Cases #
Standard Subscription Billing #
A business bills recurring packages monthly, quarterly, or annually using account bill day and package frequency settings.
Mixed Billing Cadence On One Account #
One package follows the account’s standard bill day while another package uses a different cadence or billing date override.
Coordinated Invoice Generation #
The business runs billing operationally through bill runs and then delivers resulting invoices according to configured delivery behavior.
Billing With Downstream Collections #
Billing is coordinated with payment collection, whether payments occur immediately or later as part of an operational collections process.
Important Considerations #
- Billing behavior should always be reviewed alongside pricing, package frequency, and customer contract design.
- If package-level bill timing differs from account-level timing, that behavior should be intentional and documented.
- Bill runs are operationally important and should be treated as a controlled business process, not just a technical job.
- Proration, invoice timing, and payment timing should be aligned so customer outcomes match the intended commercial policy.