Debt Collection
In a business where data accuracy directly affects client trust, the debt collection ("Inkasso") process was split across two platforms after a merger. Users had to complete a single submission across two interfaces, creating overhead, eroding productivity, and increasing the risk of errors.
Core user flows from both platforms were consolidated into a single, unified interface, eliminating redundant steps, reducing the risk of errors, and giving users one place to complete the entire submission from start to finish.
2023 - 2025
Lead UX/UI Designer
1 UX/UI Designer
1 Project Manager
1 Product Owner
4 Developers
Figma
Jira
Lucidchart
2023
The original submission flow lived on the parent platform. Users moved through four separate screens to submit a single case.
INHERITED PROCESS
FIRST ITERATION
The first iteration replicated the process from the parent platform, a multi-step approach, that served as a functional foundation. At this stage, the priority was establishing feature structure and validating the process end-to-end, using the Storybook-based legacy UI available at the time.
NEW DIRECTION
The multi-step process was consolidated into a single-screen, checkout-style interface. Users could review and complete a submission in one place, with expandable sections replacing separate screens.
USER FEEDBACK
2024 - 2025
Impact: Reduced manual effort through automated invoice escalation and a modernized, maintainable process.
Problem
What had been a pragmatic starting point was now a ceiling on what the product could do.
By this stage, the "Inkasso" feature was working, but it was built on an outdated component library and a legacy Frontend architecture that was becoming increasingly difficult to maintain.
Solution
The interface was redesigned around a new Design System, replacing the outdated component library and aligning the feature with the rest of the platform's evolving UI standards.
In parallel, working closely with the engineering team, we introduced Automation for transferring overdue invoices and modernized key parts of the Frontend architecture by reducing manual steps for users, as well as technical debt for the team.
Key Improvements
Design System Modernization
Replaced deprecated component library
Improved accessibility compliance
Increased visual consistency across screens
Automatic transfer of overdue invoices
Configurable rule-based settings
Eliminated manual case submissions
Workflow Transparency
Inline history log
Centralized visibility across debt collection cases
Customer exclusion management
Status overview for submitted invoices
Technical Foundation Improvements
Migrated frontend code from JavaScript to TypeScript
Modernized legacy Node environment
Implemented TanStack Table for scalable, interactive data tables
Before: From Manual Submission
2024
After: To Automated Case Handling
2025
Redesigned Submission Form
Redesigned Contract Confirmation
SETTINGS · AUTOMATION SCREENS
Automation Configuration
Customer Exclusion Management
Submitted Invoices Overview
Outcome
What started as a fragmented multi-platform workaround became a maintainable, automated, single-screen experience.
Users gained a faster and more intuitive submission process. The engineering team gained a codebase they could build on. And the product gained a foundation that could scale with the company rather than against it.