DANI LEYVA
ERP vendor import for financial system integration
A design-thinking approach to importing and mapping vendors from a client’s ERP, so teams would not have to transfer them by hand.

Context
Financial System Integration is a module for clients integrating from an ERP with this organization’s product — on the original case study, described as importing vendors from the ERP into the organization’s nutrition platform. Target users include nutrition directors and administrators in a school district. The work on the live portfolio is dated September 2023.
Role
Lead UX Designer at LINQ (September 2023 falls after I became Lead in July 2023). The work included usability testing to validate the designs before development.
Problem
Acquired clients were working in two systems. The integration platform needed a way for users to import vendors from their ERP. Users were transferring vendors manually, which was causing duplicate vendors and incorrect vendor selection on items and invoices.


Process
The work was framed around a clear problem and a concrete goal, then moved through competitor research, high-fidelity mockups, iteration, and usability research with users to validate the designs before development.
Usability studies with customers are part of my job and are done internally, not as public-facing research. For this project, usability testing was already part of the documented process, done to validate the designs prior to development and implementation.
Solution
The designed solution was an importing flow with intuitive importing and vendor mapping: prevent duplicates, and allow the system to create a new vendor if one does not already exist — so teams would not have to transfer vendors by hand.
Governance and collaboration
Leadership here was in how the work was framed and validated: a clear problem (manual transfer, duplicates, incorrect selection), a goal that included both mapping and creating vendors, and usability testing before development so issues could surface in the design process rather than after a build.
Outcome and status
Status: the business put the ERP project on hold. This page does not claim launch outcomes or product impact.
What usability testing showed during the design process (insights from research, not shipped results): users found the process generally seamless and simple. Some section titles were less clear than expected, which meant matching and mapping that should have been straightforward could be overlooked rather than vetted.
Learnings
Usability testing before development showed that a flow can feel simple overall and still fail in a specific place. Here, section titles that were less clear than expected put vendor matching and mapping at risk of being overlooked. That is a design-process learning, not a claim about a launched product.
