Accounting, simplified
Redesigning bank import workflows for the people who actually use them.
Company
Comarch
Year
2023
Role
UX/UI Designer
Scope
UX Research
Workflow Design
SMB SaaS
The problem
ERP XT was built around internal accounting logic, not user mental models. Module names like "Cash & Bank" and "Accounting" meant nothing to a bakery owner or freelance consultant. Workflows required 6–8 steps for tasks users expected to take two.
- Terminology mismatch — accounting language inaccessible to non-expert users.
- Cognitive overload on screens used infrequently.
- Too many steps — bank statement import required excessive clicks with no progress signal.
The approach
24 users across three groups — internal consultants, active clients, external partners. Remote sessions and in-person prototype testing revealed the same pattern: plain language and fewer steps mattered more than visual polish. Redesign focused on progressive disclosure and task-oriented navigation.
- Remote usability testing with task-based scenarios.
- Card sorting to validate navigation and terminology.
- Prototype testing with wireframes at different fidelity levels.
Key design decisions
Plain language navigation
Module names were rewritten to reflect user tasks: "Import bank statement" instead of "Cash & Bank reconciliation". Labels were tested with non-accountants — if a bakery owner couldn't predict where to click, the label changed.
Step reduction through smart defaults
Bank import was reduced from 8 steps to 3 by pre-selecting the most-used account, auto-detecting the file format, and collapsing optional matching rules. Users who needed advanced options still had access — they just weren't forced to see them.
Progress feedback during import
The original flow imported silently and showed a result table. The redesign added a three-step progress indicator (Upload → Match → Review) with inline match confidence per transaction. Users knew what was happening and why some transactions needed review.
Outcome
Testing across 24 participants showed significant workflow improvement. Key flows reduced from 6–8 steps to 2–3. Post-launch support tickets for the import workflow dropped sharply.
24
Participants across 3 user groups
–60%
Fewer steps in key workflows
↓
Support tickets post-launch