Field notes · 17 January 2026

Materiality bands and why we ask for them early

Why CodeNexusAI requests planning materiality and performance materiality before running anomaly detection on audit preparation files.

Anomaly detection without a materiality conversation produces noise. Every small suspense balance looks interesting; every large but expected inventory receipt looks alarming. Before we ingest extracts for a pre-audit anomaly review, we ask for the planning materiality and performance materiality your external auditors have shared — or your internal threshold if the letter has not arrived yet.

Those bands do not silence findings below the line. They change ranking. A TWD 40,000 payroll clearing difference may stay on the memo as a control hygiene note. A TWD 400,000 revenue cut-off candidate near year-end rises to the top of the working session.

Clients sometimes worry that sharing materiality reveals too much about the audit plan. In practice, the opposite happens: when we ignore the band, we waste your close team’s scarce hours on trivia, and the auditors still ask about the material items you never had time to document.

Back to field notes