A complete, token-based design system for ASBL Finance — a financial web application managing cashflow, payments, and account statements across projects.
Why This System Exists
Handling cashflow, inflow/outflow tracking, payment disbursement, and account statements across multiple projects and departments.
As a financial product, it demands precision in information hierarchy, status clarity, and trust signals.
A design system wasn’t optional. It was the only way to build something that scale teams could rely on consistently.
Consistency
Unified visual language across all screens and teams, same components, same behaviour, same trust.
Scalability
Clear component guidelines that handle new screens, features, or teams without breaking quality.
Efficiency
Eliminates repetitive design tasks. Enables rapid product updates without starting from scratch.
01 · Foundation
Typography
Inter
Weights: Regular · Medium · Semi-Bold · Bold
Colour Palette
Brand + Supportive
Feedback
02 · Token Architecture
Background
Text
03 · Component Library
Calendar / Date picker — with range selection
Navigation sidebar — Finance web app
05 · Feedback Patterns
Toast States
Error · Success · Info · Warning - each with optional title, body, and dismiss action
Badges
Status labels for financial states: Debited, Pending, Failed, Operational
Form Atoms
Checkbox, radio, toggle - all with complete state coverage including error and indeterminate
04 · Icon Library
Custom
Calculator, inbox/file, checkbox, ticket, hierarchy, presentation bar, user block, built for Finance-specific flows
Standard
Chevrons, shapes, typography, media, apps, real-world objects adopted from a unified icon library
Principle
Same stroke weight and optical size across both sets, custom and standard are indistinguishable in use
06 · Motion
Micro-animations – component states
Payment Pending · Scan States · Loading Indicators
UX Animation – onboarding and transitions
Guiding Behavior · Clarifying Actions · Status Updates
07 · The System in Use
Impact