Supplier Payout module

Why payouts needed a rethink

Supplier Payout is the module on FarMart OS that pays agri-output suppliers once a trade is done. Before this redesign, finance and ops ran payouts through CSV uploads and typed bank reference numbers (UTRs) by hand.

Hours lost to spreadsheets
No single approval queue
Typos in hand-typed UTRs
Late edits with no audit trail

I led the design end to end in 2025: approval flows, payment states, error handling, and what could still change before a file went to the bank. The launch is on LinkedIn.

What we aimed for

Cut the time to process a payout from two to three hours down to a few minutes, remove the errors that came from CSV uploads and hand-typed UTRs, and stop the wrong amount or account from reaching the bank.

What shaped the design

Money leaves the building

Once a file reaches the bank, a mistake is expensive, so status had to be obvious at every step.

Many hands, one queue

Procurement, finance and ops all touch payouts, so they needed one queue and one set of states.

The bank step counts too

A clean approval screen that still ended in a messy CSV upload would not have fixed the problem.

How it works

Approved tradeOne payout queue

Schedule
Approve
Send to bank

Supplier paid

Scheduling and approvals sit in one queue on FarMart OS, with a clear status for every payout. Approved payouts go to the bank with fewer manual steps, and once a payout is approved, the amount and account are locked. Failed uploads, bad UTRs and stuck approvals each have their own state, so teams act on the exception instead of rereading spreadsheets.

What changed

Payouts now move through the same FarMart OS that runs trade, KYC and finance, with tighter controls before money leaves the platform.

This work is under NDA, so screens aren't published here. For a walkthrough, email me at arvindsinghmems@gmail.com.