Finance acknowledges ADR-0057 net promotion recognition and immutable pricing snapshots
Finance acknowledges ADR-0057 and approves Revenue as the sole authority for named promotion selection, calculation, validation and immutable redemption snapshots. Callers may select an opaque Revenue promotion identity, but they do not become authoritative for discount terms or monetary totals. The proposed additive interface preserves the correct boundary and does not create a Finance-owned operational surface.
Price and recognition treatment
Finance confirms the proposed line facts and their distinct meanings:
lineSubtotalCentsandunitPriceSnapshotCentspreserve the gross catalog basis.lineDiscountCentsis the stored promotion discount applied once to the complete line.lineTotalContributionCentsis the net line consideration after the promotion and is the control total for recognition.perCreditValueSnapshotCentsis the immutable net per-credit allocation snapshot used by Revenue's recognition mechanics.creditsGrantedTotalremains the purchased credit quantity and is not reduced by the discount.
Finance will consume Revenue's stored integer-cent facts rather than independently recalculate percentage discounts or eligibility. The stored net line contribution is authoritative for the line's total recognized consideration. Per-credit allocation must cumulatively close to that exact net line total so rounding cannot create or destroy revenue. Revenue's existing recognition allocation already treats the line contribution as the closing control total, including when the rounded per-credit snapshot does not divide evenly across all granted credits.
Discounting changes consideration per credit, not the number of credits purchased. Consumption, forfeiture, refund and correction recognition therefore continue to use the immutable purchase attribution and net value snapshots associated with those credits. No historical Order Item, PromotionRedemption, recognition row or attribution slice is repriced when a promotion changes, retires or the feature flag is disabled.
Provider and reconciliation treatment
Provider invoice lines must carry the already-discounted net amount. The same promotion must not be applied again by the provider adapter or by any downstream consumer. Revenue's validated order total, provider payable total and confirmed payment must reconcile from the same net line contributions, with taxes and other separately snapshotted amounts treated under their existing rules.
Finance reporting can derive promotion value from lineDiscountCents, gross catalog basis from the existing gross snapshots and recognized revenue from Revenue's net recognition facts. Immutable PromotionRedemption identity, name and term snapshots provide the audit lineage from the discount amount back to the named promotion without making mutable catalog state part of historical reporting.
The current finance-mart surfaces already include discount reporting and derive recognized revenue from Revenue's recognition silver face. Finance requires no code, schema, mart field, retroactive entry or new owned commitment for ADR-0057. Existing zero-cent reconciliation tolerance remains controlling. A provider total that differs from Revenue's validated net total, a duplicated discount, or recognition that does not cumulatively close to lineTotalContributionCents is a variance or release blocker, not a Finance-side adjustment.
This acknowledgment does not authorize production activation, financial writes, customer messages, historical repricing or deployment. Finance has no objection to ADR-0057 acceptance and additive contract publication after Sales and Delivery acknowledge the consumer semantics and Revenue completes the existing deployment, alias, default-off flag and provider-total proof gates.
References
adrs/ADR-0057-revenue-named-promotion-price-authority.mdmemos/2026/2026-10-09-revenue-named-promotion-approval-request.mdcontracts/finance-mart/revenue-recognition-rollup.mdcontracts/finance-mart/reconciliation.mdcontracts/mart-consumer-api/api-surface-draft.mdmemos/2026/2026-05-22-revenue-mart-silver-gap-classification.mdmemos/2026/2026-06-12-revenue-june-recognition-compute-gap-fixed.md