audit-xml-parsing

Auditing XML parsing for encoding corruption involves inspecting your XML manager's decoding order and ParseError handling to detect malformed fiscal documents. The review checks UTF-8 and Latin-1 fallbacks, BOM handling, and whether parse errors retain sufficient debug context.

Latin-1 fallback handles UTF-8 declared fiscal files by applying a safe decoding order when declared encoding fails. It catches encoding corruption in files like FAPEMO, preventing broken ingestion flows by verifying the fallback logic correctly processes Latin-1 encoded content.

Recovering contextual debug info from XML ParseError requires catching the error and preserving file, line, and column details. The audit evaluates whether your parsing code records this context in a user-debuggable way so failures become discoverable rather than silent.

Your XML ingestion pipeline needs a structure that aggregates and exposes parse errors downstream. The audit evaluates how your index file collects parse errors and validates whether downstream behavior omits, retries, or reports failures to ensure they remain discoverable.

Fiscal document ingestion fails silently on malformed XML when ParseError handling gaps prevent errors from being recorded. The audit identifies missing contextual preservation and checks if parse errors are aggregated properly to prevent silent ingestion failures.

You can audit BOM handling and encoding fallbacks without external dependencies by reviewing your existing XML parsing code. The audit relies on inspecting specific functions and grep patterns internally to produce an evidence-based report on encoding robustness.