Replay the history
Reconstruct account activity from authorized exports, opening balances, and versioned chart mappings. Establish the input boundary before comparing results.
A declared starting pointA core ledger shadow for Canadian banks
A new core release. A product rule change. A migration. Know what changed in the accounts—and why—before making the release decision.
In research & development · Seeking early design conversations
What the core posted
What the rules require
Trace it to the event, rule, or mapping.
A second view of your books.
Evidence for your next change.
Decisions owned by your team.
01 / THE APPROACH
SpiritLedger is being designed to give Technology and Finance a shared view of accounting outcomes, alongside the institution’s existing core.
Reconstruct account activity from authorized exports, opening balances, and versioned chart mappings. Establish the input boundary before comparing results.
A declared starting pointCompare baseline and candidate outputs against independently reviewed expectations, where business events and product rules are available.
An independent expectationConnect differences to source records, calculation dates, and configuration versions. Assemble reproducible evidence for the people making the decision.
A reviewable explanation02 / A SMALL DIFFERENCE. A REAL QUESTION.
In our synthetic deposit case, a candidate applies a rate change one day late. Every journal still balances. Two customers receive less interest than the stated expectation.
The useful question goes beyond the total: which day diverged, which rate applied, and what evidence supports the explanation?
Interactive illustration from our research specifications. These are synthetic, arithmetic-checked amounts—not output from a running SpiritLedger engine.
| Interest paid · CAD | Expected | Candidate |
|---|---|---|
| Account A | 51.50 | 50.30 |
| Account B | 24.20 | 23.70 |
| Total | 75.70 | 74.00 |
First divergence: October 16 · Rate effective date
The candidate starts the new rate on October 17 instead of October 16. Account A is short CAD 1.20; account B is short CAD 0.50.
03 / BUILT AROUND THE DECISION
Investigate whether a candidate preserves the intended accounting behaviour before the scoped change is approved.
Explore interest, fees, corrections, and classification changes with their effective dates and historical meaning intact.
Plan for another reviewer to reproduce the case from a consistent ledger, chart, configuration, and evidence set.
04 / START WITH ONE CHANGE
We’re looking for conversations with Canadian banking teams working through deposit-platform changes. Help shape a focused validation workflow around a decision your team actually needs to make.
Start a conversationOpens a public GitHub inquiry. Share only non-sensitive project details.
Scope and acceptance would be agreed with your Technology and Finance owners. Product readiness and data access determine what can be validated.
A FEW PRACTICAL QUESTIONS
SpiritLedger is in research and specification. The ledger engine and application stack are still being evaluated. This site introduces the proposed product and invites early design conversations; it does not describe an available production service.
The proposed initial scope is a shadow alongside your existing core: replay, reconciliation, and validation. The institution’s core remains authoritative. Payment execution is outside the proposed initial scope.
Opening balances, posted journals, chart and mapping history, and completeness evidence are the starting point. Independent interest validation also requires business events, rates, calendars, and agreed product rules. Journals alone cannot independently prove calculation correctness.
Your core-platform lead, accounting or Chart of Accounts owner, and testing or reconciliation lead. Together we can identify an upcoming change, the decision owner, and a bounded question worth investigating.