Credit revenue recognition
Stigg gives Finance an auditable trail for credit-based revenue: every grant has a per-unit cost basis (how much the customer paid per credit), lifecycle dates (effective/expiry), a category (paid or promo), and every burn/expiry/revocation is captured in an append-only ledger. This lets you calculate recognized revenue precisely from actual consumption, while keeping deferred balances correct.How to operationalize rev rec
-
Export credit data to your warehouse
Connect a warehouse in Integrations → Data warehouse and use the exported credits tables to model rev rec (see the native integrations overview and the export schema). -
Model balances by grant
For each grant (grant_id
): trackamount_granted
,amount_remaining
,amount_consumed
,expires_at
,category
, andcost_basis
(per-unit).- Deferred revenue =
amount_remaining × cost_basis
(paid grants only). - Recognized revenue (consumption) =
consumed_in_period × cost_basis
. - Breakage (expiry) =
expired_in_period × cost_basis
(recognized per your policy). - Promotional grants have zero cost basis and do not generate revenue.
- Deferred revenue =
-
Translate to journal entries (example policy; align with your accounting rules)
- On purchase/grant of paid credits:
Dr Cash/AR; Cr Deferred revenue (foramount_granted × cost_basis
). - On consumption:
Dr Deferred revenue; Cr Revenue (forconsumed × cost_basis
). - On expiry (breakage):
Dr Deferred revenue; Cr Revenue (forexpired × cost_basis
, timing per policy). - On revocation/refund:
Reverse the appropriate portion of deferred/revenue per your policy.
All supporting facts come from the credit ledger and grants exports.
- On purchase/grant of paid credits:
-
Reconcile and report
- Tie period consumption (ledger decrements) × cost_basis to recognized revenue.
- Tie ending remaining × cost_basis to deferred revenue.
- Review expired and revoked entries separately for breakage/refunds.