UI/UX Designer Needed — Enterprise Finance Module (ERP)

────────────────────────────────────── PROJECT OVERVIEW ────────────────────────────────────── We are looking for an experienced UI/UX designer to produce the production-ready design for a Finance Module within a custom-built enterprise ERP system. The module is part of a larger ERP suite (HR, Finance, Legal) built for a regulated financial authority. The scope of work has been fully defined and validated. A functional prototype already exists (React + TypeScript + Tailwind). Your role is to take this prototype and produce a polished, professional, and accessible UI design that will be handed off to the development team for implementation. ────────────────────────────────────── MODULE SCOPE — 5 SUB-MODULES ────────────────────────────────────── 1. Payment Process Automation The core sub-module. Covers an 8-step outbound payment workflow: request creation → multi-tier approval → digital cheque generation → e-signature → bank execution → archive. Includes an embedded transaction search, filter, and export panel. This is the most complex screen set. 2. Budget Management Budget overview dashboard with 4 cost centre categories. Summary cards, data table with expandable rows, progress/utilisation indicators (colour-coded), and an edit modal for authorised users. 3. Document Management + Downloads Two-tab interface: (A) an eDossier for searching, uploading, and version-controlling finance transaction documents; (B) a managed forms library with download and version history functionality. 4. Notifications In-system notification panel (bell icon + dropdown + full page). Role-aware filtering. Read/unread states. 4 notification types with distinct visual treatment. 5. Bank Management IT Admin-only configuration interface. Bank list with account cards, add/edit modals, logo upload, and a change history log. ────────────────────────────────────── TECH STACK & CONSTRAINTS ────────────────────────────────────── • Frontend: React + TypeScript + Tailwind CSS + Shadcn/ui • The design must be implementable with Tailwind CSS utility classes • Component library: Shadcn/ui (Designer should be familiar with its component set) • Responsive: desktop-first, tablet-compatible • No mobile-only layouts required ────────────────────────────────────── DESIGN DIRECTION ────────────────────────────────────── This is an internal enterprise tool used by a small Finance team. The design should be: • Clean and professional — not a consumer product, not decorative • Data-dense but not cluttered — tables, cards, and status badges are the core patterns • High-trust appearance — this system handles outbound payments and financial approvals ────────────────────────────────────── DELIVERABLES EXPECTED ────────────────────────────────────── • Figma file with all screens, components, and variants • Design system: colour tokens, typography scale, component library (buttons, badges, modals, tables, forms, tabs) • Key screens for each of the 5 sub-modules • Annotated specs for the development team • Interactive prototype (Figma) covering the main payment workflow (Sub-module 1) ────────────────────────────────────── SCREEN COUNT (ESTIMATE) ────────────────────────────────────── • ~25–35 unique screen states across all 5 sub-modules • Multiple modal/overlay states per sub-module • Empty states, loading states, and error states for key flows ────────────────────────────────────── IDEAL PROFILE ────────────────────────────────────── • Strong experience designing enterprise or B2B SaaS products • Comfortable with data-heavy interfaces (tables, dashboards, forms) • Familiar with Tailwind CSS / Shadcn/ui component patterns • Experience producing developer-ready Figma files with auto-layout and component variants • Bonus: experience with ERP, finance, or compliance systems ────────────────────────────────────── HOW TO APPLY ────────────────────────────────────── Please include in your application: • Portfolio examples of enterprise / B2B / internal tools (dashboards, admin panels, data tables) • Your estimated timeline for this scope • Your proposed process (discovery, iterations, handoff) • Fixed price or hourly rate proposal