bookkeeping-patternslisted

# Bookkeeping Patterns > Standards: **IFRS Conceptual Framework for Financial Reporting (2018)**, **US GAAP (ASC) Conceptual Framework Statement of Financial Accounting Concepts No. 8**, **FASB Accounting Standards Codification**, **AICPA Audit Standards**, **Pacioli's Summa de Arithmetica (1494, the original codification of double-entry)**, **ISO 4217** (currency codes), **ISO/IEC 20022** (financial messaging). ## Purpose Every SaaS, marketplace, fintech, e-commerce, or B2B platform that handles money is operating an accounting system whether engineering recognises it or not. Skill of bookkeeping pattern decides whether finance can close the books each month, whether auditors can trace transactions, whether tax authorities can verify revenue, and whether the founders can answer "how much did we make last quarter" without a heroic spreadsheet exercise. This skill teaches the engineering pattern for double-entry bookkeeping: the chart of accounts (CoA), the journal-and-ledger schema, immutable accounting events, reconciliation patterns against external systems (payment processors, banks), and the operational patterns that survive audit. It is the foundation upon which IFRS/GAAP reporting (the `ifrs-gaap-reporting` skill) builds. The principle invented by Luca Pacioli in 1494 still applies: every transaction touches at least two accounts; debits equal credits; the ledger must always balance. Modern systems add timestamping, immutability, idempotency, and multi-currency — b