Finance and accounting source of truth
Chwezi Accounting Doctrine: Finance and Accounting Skills for Systems and Decisions
A public cross-cutting accounting and finance doctrine for ledgers, reporting, budgeting, controls, audit, tax, treasury, costing, and finance-system integration.
Inspect on GitHub Chwezi Accounting DoctrineRepository facts verified locally on 22 August 2026
Direct answer
Chwezi Accounting Doctrine is the finance and accounting source of truth used when a software, business plan, proposal, or operational workflow touches ledgers, reporting, budgeting, controls, audit, tax, treasury, costing, or accounting-system integration. It is referenced by companion engines rather than mirrored into them.
Who it serves
Finance teams, accountants, auditors, system designers, business-plan authors, proposal teams, and developers building systems that handle financial information.
102
Finance/accounting skills verified
17
Category groups
Canonical source
Role in portfolio
Retired
Mirror model
Non-negotiable operating rule
Human in the middle. Every time.
Nothing is considered finished merely because an AI tool or skills engine produced it. A responsible person reviews the facts, logic, sources, calculations, code, security, privacy, context, and quality of the output before it is published, deployed, submitted, or used to make a decision. For some actions, the engine must stop until the user explicitly types that they approve the action; approval must never be inferred from silence or a vague request.
Human responsibility: approve, correct, escalate, reject, stop, or roll back the work.
Engine responsibility: make the method, evidence, limits, review points, and approval pauses visible.
In practice
A second view of the work this engine supports
The visuals illustrate the domain; they do not replace evidence, controls, or the human review required before a consequential decision or action.
Capability map
What this engine covers
The list below is a plain-language summary of the repository's verified capability surface. It is not a promise that every project needs every skill.
- Accounting and finance doctrine, ledger design, reporting, budgeting, FP&A, costing, controls, audit, tax, and treasury.
- Finance-system integration, accounting-engine architecture, posting services, mappings, reconciliations, period locks, and integrity jobs.
- Cross-cutting finance guidance for software engineering, SRS documentation, proposals, and business planning.
- Evidence, governance, professional review, and explicit boundaries for finance decisions and system behaviour.
How to use it
A repeatable route from request to evidence
Classify the finance need
Separate accounting doctrine, system behaviour, reporting, tax, controls, budgeting, costing, or professional judgement.
Route to the source
Use the canonical finance doctrine and add the owning companion engine for software, documents, proposals, or business planning.
Specify control logic
Define posting, mapping, approvals, reconciliation, period, access, audit, and exception rules before implementation.
Review and reconcile
Test accounting invariants, reporting rebuilds, controls, evidence, professional review, and operational handoff.
Good fit
When to use this engine
- A software system handles money, inventory value, payroll, tax, receivables, payables, grants, assets, or financial reports.
- A business plan or proposal needs financial logic, controls, costing, or a reconciled model.
- An organisation needs to document a ledger, posting service, reconciliation, period-close, or reporting process.
- A finance question crosses into architecture, requirements, testing, deployment, or operational controls.
Boundaries
What it does not replace
- It does not replace a qualified accountant, auditor, tax adviser, legal adviser, or statutory authority.
- Country-specific tax, regulatory, IFRS/IAS, IPSAS, and filing claims require current verification and professional review.
- Visual and document presentation decisions route to Design System Skills; implementation routes to Chwezi Dev Engine.
- It does not create evidence merely by writing confidently; source claims and project facts still need verification.
- It does not remove accountable human review, specialist judgement, approval authority, or professional sign-off.
- It does not authorise live account changes, client communications, production changes, or submissions without explicit permission.
Continue the route
Related first-party guidance
Business Plan Skills
Use the planning engine when financial logic is part of a feasibility, funding, valuation, or implementation plan.
Chwezi Dev Engine
Use the engineering engine for database, accounting-system integration, APIs, security, and application implementation.
Chwezi Accounting Doctrine on GitHub
Inspect the canonical public finance and accounting doctrine.
Frequently asked
Questions about Chwezi Accounting Doctrine
Why is accounting doctrine a separate engine?
Finance and accounting rules cross software, business plans, proposals, and operations. A separate source of truth prevents inconsistent or stale finance guidance being mirrored into multiple engines.
Can it approve financial statements or tax filings?
No. It provides doctrine and system guidance; qualified professionals and the relevant statutory or organisational authority remain responsible for approval.
When should a developer use this engine?
Use it whenever a system handles financial values, accounting records, controls, reporting, tax, payroll, inventory value, grants, assets, or audit evidence.
Ready to discuss your project?
Every engagement begins with a conversation. Book a consultation to explore how Peter's experience can serve your organisation.