audit-accounting-classify

An accounting classification audit reviews how your code assigns categories like COMPRAS, GASTOS, ACTIVO, or OGND, checking for case inconsistencies and whether mappings are centralized. It produces an evidence-based report listing findings, severity, impact, and a final verdict.

Auditing destination folder path construction involves verifying the real folder-building logic in your classifier, including how the destination root, month, client, and sanitized emitter names are combined. The audit confirms whether directories are created correctly and identifies invalid routes or inconsistent mappings.

When a matching account is missing during catalog account lookup, an audit reviews how the catalog is loaded and how lookups behave, including whether defaults are applied. This detects misapplied accounts and ensures classified files land in the correct destination structure with expected rules.

You should run an accounting classification and destination path audit before trusting classification results for month-end exports. This confirms that classified files land in the correct Contabilidades folder tree structure with the expected category and account rules applied, preventing invalid routes.

Yes, you can audit specific modules for filesystem path assembly and category mapping by asking the AI to review only the modules listed in the Skill's scope. It verifies real code behavior for categories, account catalog lookups, and path assembly, producing an evidence-based report of actual findings.