Module subscriptions
Recurring access governed by start point, billing cycle, trial transition, renewal and payment status.
Time-based access
Falco Ledger connects commercial terms, platform events, controlled invoicing and service entitlement—operated by Falco DI for its ecosystem and independently by each WLP for its own customers.
Modules begin at different moments. Trials conclude. Objects and users grow. Services renew. Portals are assigned. Partners earn commission. The commercial engine must understand each change without losing the agreement behind it.
A module subscription, a machine under service and a customised enhancement cannot be billed in the same way.
Billable events occur between invoice cycles and must be recognised without duplicating earlier charges.
The commercial record must remain connected to the access, capacity or service it activates.
Falco Ledger first establishes the commercial context. Each later trigger is evaluated against this governed relationship—not against an isolated spreadsheet or a remembered exception.
The source of truth that every billing event returns to.
Direct OEM, Partner OEM, White Label Partner or a sponsored Portal relationship.
Falco Cloud, third-party cloud or on-premises—the hosting context influences the eligible commercial structure.
Modules, billable objects, consumable packs, onboarding, portals or defined services.
Pre-paid or post-paid, with the applicable cycle, credit framework, quantities and pricing basis.
Falco Ledger brings recurring access, measurable platform activity and service delivery into one system without forcing them into one billing pattern.
Recurring access governed by start point, billing cycle, trial transition, renewal and payment status.
Time-based accessUsers, readings, machines, quotations, service calls and other measurable units linked to real platform activity.
Quantity + timePrepaid operating capacity purchased in defined packs before further governed actions can proceed.
Capacity controlOne-time implementation value aligned to delivery milestones such as advance, UAT and final completion.
Stage-triggeredSponsored customer participation linked to the OEM, the portal module and the account receiving access.
Relationship-basedStorage, support, enhancements and customisation retain the commercial treatment appropriate to the service.
Service-specificTrial entitlement, onboarding and the first subscription invoice remain coordinated. The customer experiences one controlled transition rather than overlapping activation and billing events.
A one-time onboarding charge need not be compressed into a single event. Falco Ledger can recognise staged delivery while preserving one connected implementation history.
The commercial engagement begins and the first governed milestone is recorded.
A later invoice can align to user acceptance or another agreed delivery checkpoint.
Final onboarding completion closes implementation and connects to subscription commencement.
The recurring commercial lifecycle proceeds from the governed start point.
Not every billable object can be governed in the same way. Falco separates capacity it can technically control from operating activity that the OEM must remain free to perform.
Examples include users, readings and prepaid action packs. Falco can prevent additional governed activity when licensed or purchased capacity is exhausted.
Machines, quotations and service calls may be created because the business requires them. Falco records additions and applies commercial rules without obstructing the OEM’s operation.
Scheduled runs manage recurring obligations. Event triggers capture additions, stage completions, portal assignments and other billable changes between those cycles.
The engine combines the billable event with the governing commercial context. Exact internal formulas remain protected, while the mechanism behind every line stays visible.
Recurring schedules and live events can converge on the same commercial period. Falco checks the account, offering, object or event and billing period before creating a new obligation.
A schedule, transaction or manually governed milestone requests billing.
The engine locates the account, offering, period and underlying source.
Existing invoice records are tested for the same obligation and period.
Only a valid, previously unbilled obligation proceeds to calculation.
A customer should not need institutional memory to understand a charge. The invoice carries the offering, period, quantity and source context; the supporting trail carries the decision history.
The invoice is not the end of the process. Payment confirmation closes the commercial loop and activates, extends or records the continuation of the corresponding entitlement.
When an OEM assigns a portal module to a Portal Account, Falco Ledger recognises the sponsored commercial relationship. Payment by the sponsoring OEM activates the corresponding portal entitlement.
A channel partner is registered with commission terms. When a Partner OEM is linked, those terms can be retained or refined for that specific relationship. Relevant OEM invoices then trigger traceable partner commission advice.
A WLP receives Falco Ledger inside its isolated DI environment. Its customer products, prices, invoices and collections belong entirely to the WLP.
Transparency does not require exposing every internal formula. It requires preserving the evidence that lets a customer understand and verify the charge.
The originating subscription, quantity addition, portal assignment, service milestone or scheduled renewal.
The applicable account relationship, offering, billing basis, period, quantity treatment and commercial terms.
The module access, service capacity, portal entitlement or operating licence linked to confirmed payment.
Customers see the mechanism. Operators control the rules. Every charge remains connected to the event and entitlement that gave it meaning.
← Return to DI Admin