CASE Study
Custom Accounting Workflow System
Designed an internal workflow platform for a UK accounting firm that unified fragmented document-processing workflows into a scalable operational system. The project focused on reducing cognitive load, supporting high-volume financial operations, and building a foundation for future automation.
Client: UK-based accounting firm
Scope: End-to-end product design for internal automation system

Context and problem
- Employees manually processed large volumes of receipts and invoices across multiple clients.
- Documents arrived in inconsistent formats, requiring extensive manual classification.
- Information was fragmented across folders, spreadsheets, and disconnected tools.
- Low-to-average digital literacy meant workflows had to be intuitive and predictable.
- Accuracy was critical, as small mistakes could affect financial reporting.
Goal
Design a unified workflow system that simplified document processing, reduced manual effort, and preserved established accounting practices while creating a scalable foundation for future automation.
My role
Product Designer
- Product discovery
- Workflow modelling
- Information architecture
- System modelling
- Feature definition Interaction design
- Developer handoff
Constrains
Low digital literacy
The interface minimized abstraction, reduced navigation complexity, and relied on familiar interaction patterns rather than advanced UI techniques.
Existing accounting model
Financial periods and folder structures reflected established accounting processes and therefore became fixed constraints that the product needed to support rather than redesign.
Operational priority
Daily document processing took precedence over administrative features such as employee or supplier management.
Large data sets
Users regularly navigated years of financial records, requiring efficient hierarchy, search, and recovery from deep navigation states.
Accuracy
Financial workflows demanded clear validation, confirmation, and visibility of system state to reduce operational errors.
Trust in automation
Machine-extracted information always remained reviewable and editable so users retained confidence and control over the workflow.
High Variability in Document Formats – Receipts and invoices came in inconsistent layouts, requiring a flexible ML parsing system and UX that allowed correction without friction.
Empty states
The system required users to review documents across multiple accounting periods while maintaining the rule that every document belongs to a specific folder.
Rather than treating empty states as placeholders, they became guidance points that helped users understand the next valid action without breaking the accounting workflow.



Clear folder status indicators
Accounting staff frequently switched between clients and accounting periods while processing large volumes of documents.
To reduce unnecessary navigation, folders communicate both their contents and current state at a glance.
Visual states distinguish:
- Empty folders
- Active empty folders
- Populated folders
- Active populated folders
This enables users to quickly identify where work is required without opening every folder individually. Folder states are communicated through both icons and color, ensuring they remain distinguishable without relying on color alone.
Expense codes
Expense codes are one of the most frequently referenced pieces of information during document processing.
To speed up recognition and reduce classification errors, payment types were reinforced with visual cues while preserving existing accounting terminology.
This improved scanability without requiring users to learn a new coding system.

System Thinking
This project required designing beyond individual screens.
The platform introduced a structured operational model that defined relationships between:
- Clients
- Accounting periods
- Documents
- Suppliers
- Expense codes
- User permissions
The focus was on reducing cognitive load while maintaining strict business rules and enabling future workflow automation.
Designing this product reinforced that effective enterprise UX starts with modelling workflows rather than interfaces.
Many of the project’s UX decisions emerged from understanding relationships between data, permissions, and operational constraints, rather than visual design alone.