Back Request Demo
Falco commercial control

Every charge has a reason.
Every entitlement has a trail.

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.

Terms become rulesEvents become billableInvoices remain traceablePayments govern access
Follow the value path
The commercial reality

A price list cannot govern a living platform.

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.

01

Value is not one-dimensional

A module subscription, a machine under service and a customised enhancement cannot be billed in the same way.

02

Activity moves continuously

Billable events occur between invoice cycles and must be recognised without duplicating earlier charges.

03

Payment has an operational consequence

The commercial record must remain connected to the access, capacity or service it activates.

Configure before calculating

The relationship is assembled before the first invoice.

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.

01

Commercial relationship

The source of truth that every billing event returns to.

Account-specific · governed · effective-dated
Who is being served?

Direct OEM, Partner OEM, White Label Partner or a sponsored Portal relationship.

Where does it operate?

Falco Cloud, third-party cloud or on-premises—the hosting context influences the eligible commercial structure.

What is being supplied?

Modules, billable objects, consumable packs, onboarding, portals or defined services.

How will value be billed?

Pre-paid or post-paid, with the applicable cycle, credit framework, quantities and pricing basis.

Transparent mechanism, protected rulebook. Customers can understand which dimensions govern a charge. The detailed eligibility matrix, thresholds and internal validations remain controlled inside Falco.
One engine · several charging families

Different value keeps its natural commercial shape.

Falco Ledger brings recurring access, measurable platform activity and service delivery into one system without forcing them into one billing pattern.

S

Module subscriptions

Recurring access governed by start point, billing cycle, trial transition, renewal and payment status.

Time-based access
O

Billable objects

Users, readings, machines, quotations, service calls and other measurable units linked to real platform activity.

Quantity + time
P

Consumable packs

Prepaid operating capacity purchased in defined packs before further governed actions can proceed.

Capacity control
↑

Onboarding

One-time implementation value aligned to delivery milestones such as advance, UAT and final completion.

Stage-triggered
C

Portal services

Sponsored customer participation linked to the OEM, the portal module and the account receiving access.

Relationship-based
+

Defined services

Storage, support, enhancements and customisation retain the commercial treatment appropriate to the service.

Service-specific
Trial to commercial service

A free trial ends cleanly. The commercial record begins once.

Trial entitlement, onboarding and the first subscription invoice remain coordinated. The customer experiences one controlled transition rather than overlapping activation and billing events.

Evaluation period

Use first. Decide with evidence.

  • Module-specific trial entitlement
  • Defined trial duration
  • Service remains visible as trial
  • Billing remains deferred until the trial closes
Trial closes
at governed boundary
Commercial service

One transition activates the paid relationship.

  • Trial completion becomes a billable trigger
  • Deferred onboarding is brought forward
  • First subscription period is formed
  • Duplicate prevention protects the transition
Onboarding follows delivery

Commercial milestones can follow implementation milestones.

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.

Stage 01

Advance

The commercial engagement begins and the first governed milestone is recorded.

Stage 02

UAT

A later invoice can align to user acceptance or another agreed delivery checkpoint.

Stage 03

Final

Final onboarding completion closes implementation and connects to subscription commencement.

Continuity

Subscription

The recurring commercial lifecycle proceeds from the governed start point.

Two object behaviours

The engine distinguishes controlled capacity from observed activity.

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.

Falco-controlled

Capacity can be enforced.

Examples include users, readings and prepaid action packs. Falco can prevent additional governed activity when licensed or purchased capacity is exhausted.

Control response: existing authorised activity remains traceable; new activity waits for additional capacity or entitlement.
OEM-controlled

Operations continue. Billing observes.

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.

Commercial response: minimum commitments, slabs, inclusion date and reconciliation govern additions. Deletions do not silently rewrite prior service value.
Time + events

The scheduler starts the cycle. Platform activity keeps it true.

Scheduled runs manage recurring obligations. Event triggers capture additions, stage completions, portal assignments and other billable changes between those cycles.

Schedule observes
Period boundary
Renewal point
Trial completion
Credit timing
Events observe
New object
Portal assigned
Stage completed
Pack requested
Controls decide
Eligible?
Already billed?
What quantity?
Which entitlement?
Calculation with context

Quantity alone never explains the invoice.

The engine combines the billable event with the governing commercial context. Exact internal formulas remain protected, while the mechanism behind every line stays visible.

Source event
What changed?
+
Applicable terms
What governs it?
→
Explainable line
Why this charge?
Minimum commitmentQuantity slabInclusion dateProratingPeriod alignmentCredit framework
Duplicate prevention

Before generating, Falco asks whether the obligation already exists.

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.

Observe

Trigger arrives

A schedule, transaction or manually governed milestone requests billing.

Resolve

Context is identified

The engine locates the account, offering, period and underlying source.

Compare

Prior billing is checked

Existing invoice records are tested for the same obligation and period.

Decide

Create or stop

Only a valid, previously unbilled obligation proceeds to calculation.

The invoice explains itself

Every line retains its commercial origin.

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.

Illustrative invoice anatomy

Commercial obligations

INV / ACCOUNT / PERIOD
Module subscriptionPeriodAmount
New billable objectsQuantityAmount
Onboarding milestoneStageAmount
Portal serviceAccountAmount
Illustrative structure only. Actual line items follow the governed commercial arrangement for the account.
SourceThe platform event, schedule or delivery milestone that initiated the obligation.
RuleThe applicable offering, billing basis, quantity treatment and period context.
HistoryApprovals, generation status, payment state and linked entitlement response.
Invoice to entitlement

Commercial completion becomes an operating instruction.

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.

Invoice generatedCommercial obligation recorded
Payment trackedStatus remains visible
Payment confirmedObligation satisfied
Offering matchedEntitlement identified
Entitlement updatedAccess activated, extended or continued
Portals connect two organisations

The sponsoring OEM controls access. Falco Ledger controls activation.

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.

OEM action
Select Portal Account
Assign portal module
Choose permitted menus
Submit assignment
Ledger action
Identify first assignment
Trigger invoice
Confirm payment
Activate portal access
Partner relationship

A referred OEM carries its commercial connection forward.

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.

Establish
Register partner
Set generic terms
Link Partner OEM
Refine OEM terms
Execute
OEM invoice
Terms evaluated
Commission computed
Advice generated
White-label independence

Falco licences the WLP. The WLP runs its own market.

A WLP receives Falco Ledger inside its isolated DI environment. Its customer products, prices, invoices and collections belong entirely to the WLP.

Falco → WLP

Platform entitlement

  • Prepaid licence term
  • Aggregate user capacity
  • Authentication Key
  • Renewal maintains instance access
No shared
customer billing
WLP → its OEMs

Independent commerce

  • Own offerings and commercial terms
  • Own prices and invoices
  • Own collections and customer records
  • Own payment-to-entitlement operation
Customer transparency

The mechanism is visible from trigger to consequence.

Transparency does not require exposing every internal formula. It requires preserving the evidence that lets a customer understand and verify the charge.

✓

What triggered it?

The originating subscription, quantity addition, portal assignment, service milestone or scheduled renewal.

✓

What governed it?

The applicable account relationship, offering, billing basis, period, quantity treatment and commercial terms.

✓

What did it activate?

The module access, service capacity, portal entitlement or operating licence linked to confirmed payment.

Commercial trail
10:04Billable event recorded
10:04Account terms resolved
10:05Duplicate check passed
10:05Invoice generated
Entitlement trail
14:28Payment confirmation recorded
14:28Offering matched
14:29Entitlement instruction issued
14:29Service status active
Falco Ledger

Commercial flexibility.
Engineered accountability.

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