For Academy decision-making, the same enrollment must be traceable through customer payment, processor settlement, delivery obligations and the financial result; no one of these records proves the others.
A fully delivered one-time purchase may have simpler timing than a subscription or future course promise. Do not force an arbitrary deferred-revenue schedule onto every product. A reconciliation design is not evidence that the integrations are implemented.
Piper distinguishes profit from cash and shows prepaid expenses and unearned revenue. Applying those distinctions to the Academy suggests a reconciliation across sales, settlements, access/delivery and accounting. This is a proposed management control; exact recognition treatment depends on actual contracts and current applicable standards.
Derived from BIZ-002, chapters 4–5 and 9, PDF sheets 39–55 and 86–94; applied to the owner-approved working plan. Proposed workflow, not validated operation.
Idea
A paid enrollment can create several different events: an order, cash held by a processor, a bank settlement, access granted, services still owed, and eventually a financial result. Link those events with stable identifiers and reconcile them; do not treat the order total as a complete financial picture.
Evidence And Inference
Piper explains retained earnings versus cash (chapter 4, sheet 46), timing and financing differences (chapter 5, sheets 49–54), and prepaid expenses/unearned revenue (chapter 9, sheets 92–94). The enrollment workflow is an Academy inference from those distinctions.
Application To Test
Use a sample enrollment, refund, fee and delayed settlement to test the proposed Snipcart-to-Xero reconciliation. Record access and any remaining delivery promises separately. Acceptance: every material difference has an explanation and replaying an event does not duplicate it. The accounting policy must match actual contract terms; this note sets no revenue-recognition policy.
No access
Related Foundation
No access