The modules

Twenty-three modules in 7 functional families, which are also the internal boundaries of the code and the layout of the repository you will receive.

This list covers chapters 8 to 27 of your specification, the foundation that carries them, and the two modules announced in chapter 4 without a detailed chapter — Visa Cards and Banking Partners. They are included in the commitment; their specification is produced with you at framing, before any development.

The count of twenty-three reconciles a gap the proposal flags in your document: chapter 4 announces 21 modules, the detailed chapters describe only 20. To these we add the ledger and reconciliation, which we bring into scope although your document does not list them.

Hover over a module to unfold its key features.

A note on the count

Your chapter 4 announces 21 modules. The detailed chapters describe 20, with different numbering: CRM & KYC is detailed in chapter 21 but missing from the list, while Visa Cards and Banking Partners appear in the list without being detailed. Our delivery covers the union of both lists — the only reading that drops nothing.

One module does not appear in your document: reconciliation. It is our addition, and the one we care most about. Without it, importing statements produces data that nobody confronts.

Our definition of "done"

A module is delivered when it passes, without us:

• Acceptance on your real operations, not on textbook cases
• Verification across every role — each sees exactly what it must see, and nothing more
• The trial balance is exact: on the acceptance dataset, postings sum to exactly zero
• Automated tests replayed on every integration
• Documentation, user and technical
• Deployed to your staging environment, and handled by your teams