financial-audit

To audit financial formulas for code parity, you compare documented calculations in CLAUDE.md against actual code implementations to identify discrepancies. This requires module documentation, a test suite covering financial calculations, and code references to map variables accurately.

Formula drift in financial code occurs when documented calculations and code implementations become misaligned over time. Auditing for this drift involves verifying that variable mappings and arithmetic in the documentation exactly match the production code.

You should run a financial formula audit during module audits, pricing changes, or pre-release checks where formula drift could arise. These checkpoints ensure documentation and code implementations maintain parity before critical updates reach production.

To verify financial calculations against documentation, you need module documentation in CLAUDE.md, a test suite covering financial calculations, and corresponding code references. These inputs allow the audit to map variables to implementations and generate a parity report.

Mapping financial variables to code implementations without a test suite is not supported by this audit workflow. A test suite covering financial calculations is explicitly required alongside CLAUDE.md documentation and code references to verify parity and flag discrepancies.