Smart Map Column Mapping Overrides

Smart Map Column Overrides

The Universal Ingestion Engine (UIE) auto-detects your bank’s CSV format, but until now there was no way to correct it if the detection got a column wrong. v5.3.0 closes that gap.

What’s New

• Editable column mapping — every column in the Smart Map step is now a dropdown instead of a read-only chip. Change any column role (Date, Description, Amount, Debit, Credit, Balance, Reference, Type, or Skip) without re-uploading the file.
• Re-analyse button — after changing one or more columns, click Re-analyse to re-run the partition, balance proof, and duplicate detection against the same CSV. No second upload required.
• Inline validation — invalid mappings (no date column, mismatched debit/credit pairs) show clear error messages and prevent re-analysis until corrected.
• Reset button — reverts all overrides back to the auto-detected mapping with one click.
• Provenance downgrade — any user-corrected schema is tagged as User Corrected, the lowest trust level. This prevents manually overridden schemas from being promoted into the preset library.
• Evidence trail — the original auto-detected schema and all user corrections are preserved in the import record, creating a complete audit trail of what changed and why.

Balance Proof Behaviour

• If you remove the balance column, the balance proof correctly shows “not applicable” with an amber warning. You can still proceed — balance proof is advisory, not blocking.
• If you remap and the balance proof fails, the mismatch warning appears immediately, giving you feedback before you reach the Preview step.

How It Works

The CSV is parsed once on upload and stored alongside the import record. When you change the column mapping and click Re-analyse, the backend re-partitions the same matrix with your corrected schema — no network re-upload, no re-parsing. The Total Row Conservation Law (|H| + |V| + |I| + |E| = m) is enforced after every remap, guaranteeing no rows are lost or created.