Overview
Puzzle currently has two subledgers, both related to Stripe data. They help manage high volumes of transactions by summarizing activity before posting to the general ledger.
Subledger 1: Payment Processor Subledger
This subledger records all individual Stripe balance-affecting transactions that sync to Puzzle.
How it works:
All Stripe transactions appear in a full activity feed on the details page
Because some users may have tens or hundreds of thousands of Stripe transactions per month, Puzzle summarizes this activity into daily summary entries posted to the general ledger
Clicking into a daily summary shows all the individual transactions included in that entry
Reconciliation Report:
Puzzle auto-generates a monthly reconciliation report for each month
This gives a side-by-side comparison of activity received from Stripe against transactions posted to the Stripe GL account in Puzzle
This is strictly a reconciliation of the Stripe GL account in Puzzle against the source Stripe data
Subledger 2: Revenue Recognition Subledger
This subledger handles revenue recognition based on invoices pulled from Stripe, including subscription start and end dates.
How it works:
Puzzle pulls invoices from Stripe along with subscription start and end dates
You can apply policies (revenue recognition configurations) to each invoice
Once confirmed, Puzzle generates a revenue recognition schedule and the corresponding journal entries
Example:
An invoice dated July 12th for $2,500 would normally post revenue on that date in accrual accounting
With a revenue recognition schedule applied, Puzzle instead:
Posts a deferral journal entry on July 12th
Posts month-end journal entries to recognize revenue at the end of July, August, etc.
Posting to the General Ledger:
Any changes to policies, schedules, or invoices are captured in the subledger first
Changes will show as pending until fully compiled
Click Post All Pending to push everything to the general ledger
Once posted, the entries will be visible in the General Ledger detail view