Overview
Supplier Payout is the module on FarMart OS that moves money to agri output suppliers after a trade is done.
Before this redesign, FarMart’s payout flow relied on CSV uploads, manual UTR entry, and long approval cycles. Finance and ops spent hours reconciling spreadsheets and fixing upload mistakes. The redesigned module brings scheduling, approvals, and bank handoff into one controlled system on the web: less spreadsheet risk, faster sign-off, and clearer accountability before money leaves the platform.
I led product design for the payout experience end to end: approval flows, payment states, error handling, and what could still be edited before files went to the bank.
What it was like before
- Finance and ops spent hours each cycle reconciling spreadsheets and fixing CSV upload mistakes.
- Approvals lacked a single queue with clear status, so payouts sat in limbo.
- Manual UTR capture introduced typos that were painful to trace after the fact.
- Data could be changed late in the process without a strong audit trail.
What we aimed for
- Automate payment processing so people are not the main path for every payout.
- Put approvals into one queue and cut transaction time from two to three hours down to a few minutes.
- Remove errors caused by manual UTR entry and CSV uploads.
- Lock down what can change before a file goes to the bank, so the wrong amount or account does not slip through.
Together, those goals improve operational efficiency, support compliance, and lower risk on high-volume supplier payments.
The constraints that shaped the design
Money leaves the building. Once a payout file hits the bank, mistakes are expensive. The UI had to make status obvious, and it had to stop unauthorized edits at the wrong moment.
High volume, many hands. Procurement, finance, and ops all touch payouts. The module needed one shared queue and language, not three versions of “almost paid.”
Bank handoff is brittle. Scheduling, approval, and upload are one journey. A clean approval screen that still ends in a messy CSV step would not have fixed the real problem.
How I worked on this
I owned end-to-end product design for the payout module on FarMart OS (web): the approval flows, payment states, error handling, and alignment with engineering on what could be edited before bank upload.
Like KYC, this was a focused module inside the OS platform, not a four-year product arc. I led the design through shipping. Launch notes are on LinkedIn.
What we built
- One payout queue: Scheduling and approvals in a single place on FarMart OS, with clear status instead of spreadsheet limbo.
- Controlled bank handoff: A shorter path from approved payout to bank upload, with fewer manual touchpoints.
- Tighter edit rules: Limits on what can change after approval, so late edits do not break the file that goes out.
- Error and exception handling: Designed for the messy cases (failed uploads, bad UTRs, stuck approvals) so teams can act on exceptions instead of re-reading CSVs.
Outcomes
- Shorter path from approved payout to bank upload, with fewer manual touchpoints.
- Clearer approval states so teams can act on exceptions instead of re-reading spreadsheets.
- Tighter controls on what can be modified before payments leave the platform.
- Supplier payments sit inside the same FarMart OS operating system that already runs trade, KYC, and finance for FarMart’s agri commodity B2B business.