Troubleshooting

CSV Will Not Import

An import stops when Capehelm cannot safely understand a required part of the statement or a row needs review.

Quick answer

Return to Confirm or Review and verify the CSV’s headers, delimiter, date format, description and amount mappings, currency, and row diagnostics.

Check these first

  • The CSV must be readable as UTF-8.
  • Required headers must be present once; missing or duplicate required headers are rejected by the built-in Mastercard and Scotia workflows.
  • The detected delimiter and date format must match the file.
  • A universal import profile must map a date, a description, and a valid amount model.
  • The default currency must be supported and unambiguous.

Review field mappings

In the universal Statement > Confirm > Review > Import workflow, confirm that the description and amount columns map to the correct fields. Conflicting mappings, ambiguous separators, invalid date formats, or an unsupported default currency block progress.

If a saved profile’s headers changed or are missing, remap them explicitly. Capehelm does not silently guess consequential field mappings.

Use the row diagnostics

Review the rows Capehelm flags. Current diagnostics cover invalid dates, missing descriptions, invalid amounts, ambiguous Mastercard CAD/USD amounts, and invalid checking balances.

Understand duplicates

Duplicate rows are handled separately and skipped rather than blindly imported again. A duplicate result is therefore different from a malformed row or an invalid field mapping.

Still need help?

Tell us what happened.

Email [email protected] and describe what you were trying to do, what happened, and any error message Capehelm displayed. Please write the error in the email instead of attaching sensitive files or screenshots.

Email Capehelm Support