Why Your CSV Import Has Wrong Categories and How to Fix It

CSV imports usually get wrong categories because merchant descriptions are inconsistent, transfers look like expenses, debit and credit signs are confusing, or automation rules are too broad. Fix the source columns first, then review categories and rules before reports are trusted.

Check the CSV columns first

Before blaming categorization, confirm the import data is clean.

Required columns:

• Date
• Description
• Amount

Common problems:

• Debit and credit are in separate columns.
• Amount signs are reversed.
• Summary rows are mixed into transaction rows.
• Descriptions are truncated.
• Multiple accounts are combined in one export.

Use the CSV Bank Statement Import Guide for the basic cleanup checklist.

Fix debit and credit signs

Wrong signs create wrong categories and wrong reports.

If spending imports as positive income, category reports become useless. If salary imports as negative spending, budgets look broken.

Before finalizing:

1. Confirm outflows are negative or mapped as debits.
2. Confirm inflows are positive or mapped as credits.
3. Check refunds.
4. Check card payments and loan payments.

Mark transfers separately

Transfers often look like expenses:

• ATM withdrawal
• Bank-to-bank movement
• Credit-card payment
• Savings transfer
• Currency exchange transfer

If these are categorized as groceries, bills, or income, reports will drift. Mark transfers before reviewing category totals.

For multi-account setups, use How Do I Manage Money Across Multiple Bank Accounts?.

Review ambiguous merchants

Some descriptions are too vague for reliable automation:

• POS PURCHASE
• ONLINE PAYMENT
• CARD TRANSACTION
• TRANSFER
• Payment processor names instead of merchant names

Do not create broad rules for vague descriptions. Categorize them manually or add a rule only when another field makes the pattern specific enough.

Tighten broad rules

A rule such as "if description contains payment, categorize as bills" will misclassify many rows.

Better rule inputs:

• Exact merchant phrase
• Account type
• Amount range
• Recurring day
• Payee reference
• Currency

Rules should speed up repeat review, not replace review entirely. See Rules & Automation.

Use a review queue

After import:

1. Review uncategorized rows.
2. Review high-value rows.
3. Review transfers.
4. Review new merchants.
5. Approve safe rules.
6. Reconcile the account.

Do not rely on reports until this queue is clean.

Re-import only when needed

If the mapping is badly wrong, it may be faster to delete the import batch and re-import with corrected columns. If only a few categories are wrong, fix the rows and rules.

Before re-importing, make sure duplicate detection or batch cleanup is available so the same period is not counted twice.

Tika workflow

In Tika:

1. Import the CSV through Bank Statement Import.
2. Review mapping and duplicate warnings.
3. Categorize uncertain merchants.
4. Mark transfers.
5. Use How to Categorize Transactions to keep categories useful.
6. Reconcile before reporting.

The short answer

Wrong CSV categories are usually a data-quality and rule-quality problem. Clean the columns, mark transfers, avoid broad rules, review ambiguous merchants, and reconcile before trusting reports.

Compare Free and Paid import capabilities on Tika pricing.