https://bugs.kde.org/show_bug.cgi?id=519991

            Bug ID: 519991
           Summary: CSV import requires mandatory “Payee” field even when
                    source data does not provide one
    Classification: Applications
           Product: kmymoney
      Version First 5.2.2
       Reported In:
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: importer
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

The CSV import assistant in KMyMoney requires a column mapping for the “Payee”
field, even when the imported bank CSV file does not contain payee information.

Many banks only provide fields such as:
- Date
- Amount
- Booking text / Memo
- Reference text
- Currency
but no dedicated payee field.

Current behavior:
- The import cannot proceed unless a column is assigned to “Payee”
- Users are forced to misuse unrelated fields (e.g. currency, timestamp,
booking text) as a workaround
- This can interfere with KMyMoney’s transaction matching and automatic
categorization logic

Practical consequences:
- If a constant field like “EUR” is mapped to Payee, KMyMoney incorrectly
treats unrelated transactions as belonging to the same payee
- Automatic category assignment and memo suggestions become unusable
- Users may intentionally map unique fields (such as timestamps) only to
disable incorrect matching behavior

Expected behavior:
- The “Payee” field should be optional during CSV import
- Import should work correctly without payee information
- If no payee exists, KMyMoney should either:
  - leave the field empty, or
  - allow a configurable default behavior without affecting matching logic

Steps to reproduce:
- Export account transactions from a bank as CSV
- Use a CSV file without a dedicated payee column
- Start CSV import in KMyMoney
- Attempt to map fields
- Observe that import cannot continue without assigning a Payee field

Impact:
This affects usability of CSV import significantly, especially for banks whose
export formats do not contain payee data. Users are forced into artificial
mappings that can negatively affect transaction recognition and bookkeeping
workflows.

Environment:
KMyMoney version: 5.2.2-170c6c5
KDE Frameworks version: 6.24.0
Qt version: 6.10.2
Distribution: Windows 11 Version 25H2

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to