Design
/
27 July – 6 August 2026
ArtoPay Back-office Ledger
Translating Finance’s manual Excel workflow into a digital ledger, with an interactive prototype for stakeholder review.
Project details
Ojire
UI/UX designer and interactive prototyping
Figma · OpenAI Codex
27 July – 6 August 2026
Prototype approved; implementation in progress when I left

The problem
Finance tracked transactions and balances manually in Excel. My product manager assigned me to design a digital ledger for ArtoPay’s back office, translating the existing records and financial processes into an interface the team could review.
Understanding the workflow
I requested Finance’s Excel ledger to understand how the information was organized. I then consulted my IT senior to clarify the account types and calculations, and documented my understanding to guide the design.
This meant understanding the differences between pending, settlement, payout, and other balances—and how financial events connected to their related records.

The Accounts view organizes the different balance types within the selected company and business unit.
Making financial activity traceable
The ledger needed to communicate more than account balances. My documentation also distinguished the business module associated with a record from the system that generated the financial event.
These distinctions helped structure how activity could be explored—for example, identifying events from the payout system or investigating failed synchronization.


Activity records and their details provide context for investigating financial events and their origins.
Interactive prototyping
I used OpenAI Codex to build an interactive HTML prototype that demonstrated the proposed ledger workflows. This gave Finance and my IT senior a working reference to explore and review.
The prototype supported discussion of the interface and its behavior before production implementation.
Maker–checker adjustment requests
The prototype included a maker–checker process for adjustment requests, separating the submission of a request from its review and approval.
This was a feature the finance stakeholder particularly valued during the prototype review.

Submit an adjustment request for review.

Review the requested adjustment before approval.
Stakeholder feedback and project status
Finance and my IT senior reviewed and approved the prototype. The finance stakeholder said the proposed workflow would make her work much easier and particularly appreciated the maker–checker adjustment process.
When I left Ojire, implementation was still in progress. To my knowledge, Finance had not yet used the ledger in production, so its impact in daily use had not been measured.
What I learned
Designing the ledger reinforced the importance of understanding the financial logic behind an interface. Finance’s Excel records and my senior’s guidance helped me translate unfamiliar account structures into a prototype stakeholders could review together.
Next project
