Accounting & Audit System Builder

Accounting and Audit Router identifies where a business sits in the accounting cycle and directs the request to the matching module. It covers sixteen skills and never builds schemas or templates itself. The starting principle is to recommend the few modules the business will maintain rather than introduce a large database collection.

The route follows software selection, source-document filing, transaction recording, cash or bank movement, cash counts and day-book closure, ledger and stock reconciliation, monthly closing, credit-cycle analysis, and audit-file assembly. Requests about purchases, sales, receipts, payments, petty cash, expenses, payroll entries, withholding, inventory differences, financial statements, and working papers each have a corresponding module. The stage named by the user determines the route.

Intake asks only for unresolved facts that could change that route, one question at a time. Business type, approximate transaction count, current software, spreadsheet use, who records entries, registrations, unreconciled balances, and the desired outcome form the relevant context. Existing answers are reused; unknowns remain unknown. Advice questions receive direct advice with an optional build offer.

The shortlist contains two or three modules with a one-line reason tied to the request. Starter coverage includes sales, purchases, receipts, payments, petty cash, day book, and expenses, with withholding added when applicable. Growth adds selection, filing, reconciliation, inventory, payroll accounting, and monthly close. Larger needs select additional modules from the same pack rather than automatically expanding to everything.

Use it for broad accounting setup, books-of-account requests, repeated manual month-end assembly, or preparation for an auditor. A user who already names a particular book or report goes straight to its module. A stage-specific request can route without repeating intake. A module handoff can be:

monthly-closing-statements -> skills/monthly-closing-statements/SKILL.md

The router does not post entries, build or merge schemas, choose software for the business, determine local compliance, or perform an audit. Tax and statutory requirements vary by jurisdiction. Audit preparation assembles evidence; a qualified auditor provides the opinion.

The output is a concise module list containing slugs and skill paths, with short reasons as framing. Advisory shortlists wait for the user's choice. An explicit build or selected module continues under that module's own rules without combining multiple intakes.

The accounting flow preserves traceability from verified source documents through classification, tax assessment, entry, filing, ledger review, reconciliation, close, statements, analysis, and year-end papers. Receipt handling distinguishes receivable collections, advances, loans, and capital from sales income. Supporting documents reflect the actual transaction; missing invoices do not justify fabricated substitutes. Payment vouchers do not universally replace receipt notes; capture recipient acknowledgement when no formal voucher exists. Day-book debit and credit presentation follows the software format rather than a fixed rule for every receipt or payment. Internal purchase, wage or rent documents are used only where tax rules allow, never as a workaround for a missing bill. Year-end closing entries precede audit-file preparation. Withholding reconciliation is at least monthly and physical cash counts remain periodic.

Selected modules own their fields and requested artifacts. Notion work uses the chosen module followed by its import helper. The router itself runs no commands, APIs, or file writes and requests counts and software names rather than bank numbers, salary figures, or customer details. Sensitive statutory submissions require qualified human sign-off.