Bookkeeping Curriculum
Five layers behind our internal training.
This page describes the shape of the bookkeeping curriculum we built to train accountants on the internal platform we use to run our own firm. It defines what we mean by “bookkeeping fluency” in our operating context: accounting foundations, monthly close mechanics, the country-specific rules that apply where we work, and the platform-native workflows that distinguish bookkeeping with a system from bookkeeping with a spreadsheet.
We publish the shape because the shape is the useful thing. The individual competency list and the learning material behind each competency stay internal. They are not useful as reference documents; they are useful as exercises that have to be discovered.
Five Layers
A. Foundations
The basic accounting vocabulary. Anyone bookkeeping at any depth needs every item in this layer. This is the layer where someone moves from 'memorised rules' to 'real fluency'.
B. Close Mechanics
The work of closing the books, month after month, accurately. The largest layer because closing is the bulk of bookkeeping practice. Bank reconciliation, AR / AP cycles, payroll, accruals, depreciation, period close, statement generation.
C. Local Context
Operating fluency in the Cambodian regulatory and tax environment. Country-specific rules that any in-country bookkeeper must apply correctly without our spelling them out here.
D. Platform-Native
Advanced workflows specific to working on a platform that automates parts of bookkeeping. The layer that distinguishes bookkeeping with a system from bookkeeping with a spreadsheet.
Z. Capstone
End-to-end demonstration of accumulated skill. A single proof-of-fluency at the end of the curriculum: close one small entity for one month, from source intake through period-locked statements.
What the layered structure says about our practice
A curriculum is a claim. By defining the layers we consider necessary for bookkeeping in our operating context, we are also saying: this is the bar we hold ourselves to before we consider an accountant fluent in this work.
The layers reflect actual operating reality. Foundations and Close Mechanics are universal. The Local Context layer exists because no off-the-shelf international curriculum teaches the rules of any individual country in depth, and operating fluency in those rules cannot be skipped. The Platform-Native layer reflects how bookkeeping changes when daily entries are partly automated and the workbench is a system, not a spreadsheet.
We are also publishing the Operating System that contains this curriculum, the Canopy Framework that governs our project delivery, and the layered structure that ties them together.
Working on something this curriculum touches?
If you're hiring bookkeepers, training existing staff, or building a similar system, we'd welcome a conversation.