Fondimex
Simplifying complex CFDI validation, invoice management, and factoring workflows into a more focused financial experience for businesses.
Product Designer
Fondimex Validator
FinTech · Factoring
Complex Financial Workflows
01
The Challenge
Businesses needed a clearer way to validate CFDIs and manage invoices while coordinating payment information between invoice issuers and receivers.
The experience had to account for complex financial terminology, SAT and FIEL verification, different user roles, invoice states, payment information, and factoring eligibility—without making the workflow feel overwhelming.
02
Goal & My Role
Fondimex Validator was designed as a simpler, more focused entry point into the broader Fondimex ecosystem.
The goal was to let businesses validate CFDIs, centralize accounts payable and receivable, connect with counterparties, track invoice and payment status, and access factoring services when eligible.
As Product Designer, I worked extensively across the end-to-end Validator experience, translating financial rules and business requirements into user flows, interaction patterns, prototypes, and product interfaces.
I collaborated with Business, Engineering, and QA throughout the product definition and design process.
03
Turning Financial Rules into UX
A core design challenge was translating financial, regulatory, and factoring rules into a workflow users could understand without removing information required by the business.
Validate
CFDI, SAT, FIEL
Identify
Issuer or Receiver
Connect
Counterparty relationships
Manage
Payments and invoice states
Finance
Factoring eligibility and requests
04
Designing for Two Sides of the Same Invoice
The same invoice created different responsibilities and actions depending on whether the user was the Issuer or the Receiver.
The experience needed to identify the user's relationship to the CFDI and present the appropriate workflow, information, and actions without forcing users to understand the entire financial system.
Issuer
Manage accounts receivable, track payment status, add payment deadlines, and identify invoices eligible for early payment or factoring.
Receiver
Manage accounts payable, register payments, link payment receipts, and communicate payment information back to suppliers.
Invoice States
Structured different states and rules so users could understand what had happened and what action was available next.
Factoring Status
Supported clear progression through Not Requested, Requested, Approved, and Rejected states.
05
The Product Experience
CFDI Validation
Validate invoices while identifying issuer and receiver information and supporting SAT- and FIEL-related verification requirements.
Account Creation
Supported onboarding after invoice validation as well as first-time Issuer, Receiver, and standalone account creation flows.
Accounts Receivable
Helped businesses manage receivable invoices, payment dates, payment status, and eligibility for early payment.
Accounts Payable
Supported invoices pending payment, payment registration, receipt linking, and communication with suppliers.
Factoring
Enabled eligible businesses to request early payment and understand the status of factoring requests.
Invoice Management
Structured payment deadlines, invoice types, specialized financial concepts, and different business-rule-driven states.
06
Connecting Core UX with Growth
Validator also created a natural acquisition opportunity within the financial workflow.
After validating an invoice, users could share it with their counterparty. If that business was not already using Fondimex, the interaction created an opportunity to invite them into the ecosystem.
This connected a core product action—managing an invoice— with a product growth mechanism without requiring a separate acquisition flow.
07
What I Learned
Financial Complexity
Strengthened my ability to translate financial, regulatory, and factoring rules into understandable product experiences.
Role-Based UX
Learned to design workflows where the same financial transaction behaves differently depending on the user's relationship to it.
Simplification with Constraints
Reinforced that simplifying financial software does not mean removing required information—it means structuring it around decisions and actions.
Product Growth
Gained experience connecting core product functionality with acquisition mechanisms through counterparty relationships.
Detailed launch and product performance information is not currently included in this public case study.