Case study: how a Jitra rice trader cut 90-minute reconciliation to 8 minutes

This is a case study. For the category-level read, see how a Kedah agri business still runs on paper.

A 28-year-old family paddy-trading and milling business in Jitra, Kedah was losing every harvest afternoon to a stack of carbon-copy weighbridge tickets. Every lorry crossing the bridge produced a paper weight, a deduction decision and a payment voucher — and every evening the accounts clerk sat down to tick them against each other. Ninety minutes a day, for the 40 to 60 loads that come through in the main season. We built a weighbridge-to-invoice flow: the bridge writes the ticket, the deduction is computed from the moisture and grade readings, the farmer's receipt prints at the yard, and the day closes on a screen showing only what doesn't match. Ten weeks in, it takes eight minutes.

The business

The business sits in Jitra, in the Kubang Pasu district of Kedah, in the middle of MADA's Region II — the Jitra irrigation region, roughly 31,600 hectares of paddy inside a scheme MADA administers across about 100,000 hectares in Kedah and Perlis.

The grandfather started it in 1998 as a lorry-for-lorry buyer. The second generation added a small mill on the same yard in 2009. Today it buys wet paddy from about 410 farmers, mills it, and sells rice to wholesalers in Jitra, Kodiang and Alor Setar, plus a direct run to retailers around Kubang Pasu. Nineteen people work there: two weighbridge clerks, four mill crew, three in the office, three drivers, four field buyers, three warehouse staff.

Volume runs on the double-cropping calendar: the main season roughly August to February, the off-season March to July. The main season is where the pain sits — about 1,850 loads across the season, averaging 4.6 tonnes gross per lorry, with 40 to 60 crossing the bridge on a peak day.

The problem they were actually trying to solve

Here is what a load is worth, and why the paperwork is hard. Paddy is bought wet off the field and priced with a deduction, called pemutuan, for moisture above standard, young grain, broken grain and foreign matter. The method is not a matter of opinion — the Kaedah Pemutuan Sebenar Padi has been in force since 2017, standardised under MS 84:2017, and every licensed buyer works to it. A load at 20% deduction pays the farmer on 800 kilos of every tonne. PeSAWAH, the farmers' association, has been pressing for those rates to be reviewed, citing deductions commonly running 20 to 22%, sometimes 24%.

The arithmetic underneath that is what made the reconciliation worth automating. With the paddy floor price at RM1,500 a tonne, a 20% deduction means payment is made on 736 kilos, not 800 — an effective 26.4% cut rather than the 20% the farmer expects.

Three things ran underneath the 90 minutes:

• Everything was re-keyed. The bridge printed a ticket; the clerk copied the weight into a ledger column, read the moisture meter by eye, and wrote the rate from a board on the wall.
• The rates moved and the paperwork did not. The buy price changed more than once across a season. Loads crossing after a change were sometimes priced at the old rate, and the error sat in the ledger until a farmer complained two weeks later.
• The end-of-day match was manual. Every ticket had to be tied to a payment voucher, every voucher to a cash-out, every dispatch weight to a buyer invoice — a 90-minute job that only ended when the clerk went home.

The owner said on the first call: "We are not short of paddy and we are not short of buyers. We are short of trust in our own numbers. A farmer asks me why he was deducted four percent more than the man across the road, and I go and read a ledger for twenty minutes. I want that answer on a receipt, the same day, while his lorry is still on the scale."

What we built — and why this approach

This is a business-automation build, and the automation had to start at the bridge, not at the office. Four parts:

1. A terminal at the weighbridge. The bridge reads its own weight and writes the ticket — gross, tare, net — into the ledger, so the number is never copied by a person. On an older bridge we add a camera that reads the display and a clerk tap to confirm.
2. A deduction engine configured to this operation's own SOP. The moisture, young-grain, broken-grain and foreign-matter bands the yard already works to become rules, not formulas in someone's spreadsheet cell. The system applies them from the readings, shows the clerk which band fired and why, and locks the ticket.
3. A receipt at the yard and an invoice from the same ledger. The farmer's receipt prints at the bridge with gross weight, each deduction line and its percentage, net payable weight, the rate applied and the total — and goes to the farmer's WhatsApp. The buyer's invoice for milled rice comes from the same records.
4. A day-end screen that shows exceptions, not tickets. The system matches every bridge ticket to its payment voucher and every dispatch note to its invoice, then prints only what fails to line up.

We architected it; AI built it — that operating model is on our Kedah services page. We chose this over an off-the-shelf agriculture ERP, which would want the bridge, the moisture meter and the farmer receipt rewritten in its shape and keeps the deduction bands in the vendor's hands. A tablet and a spreadsheet would still have left a human copying weights off a paper ticket. The build took 19 days.

How the operation changed

The clerk's day changed shape rather than getting shorter. Before, reconciliation was the last two hours of the afternoon. Now it is the last ten minutes, mostly reading exceptions.

• The weighbridge clerk confirms, they no longer transcribe. Readings go in at the bridge, the deduction computes itself, and the receipt prints before the lorry has cleared the yard.
• The farmer gets his answer while he is still there. Receipt in hand, itemised, with the deduction percentage and its reason on it, plus the same thing on his phone. The calls that used to arrive a fortnight later get answered at the counter.
• Disputes get a same-day answer. A farmer who queries a rate can be shown the receipt, the band that fired and the reading behind it.
• The finance lead reads a settlement, not a stack. Intake, dispatch, cash-out and receivables sit on one ledger.

The numbers, ten weeks in

The owner's own figures, ten weeks into the main season:

• Daily reconciliation: 90 minutes → 8 minutes, on peak days with 40 to 60 loads crossing the bridge.
• Loads with a transcription error: 1 in 11 → 0, across 620 loads since launch. The weight is never typed.
• Loads flagged with a weight, rate or deduction discrepancy: 28 last season → 27 in ten weeks, every one caught the same evening instead of surfacing weeks later as a complaint. The count did not drop because errors stopped happening — it dropped because they are caught on the day.
• Paddy mispriced against the actual reading: RM 34,400 across a season → RM 0. This was the real money: loads priced at a stale rate, deductions applied from a misread meter.
• Farmer queries: 3 to 5 days to settle → same day, 11 minutes average.
• Clerk hours on reconciliation: 5.5 hours a week → 0.5 hours a week.
• Farmers who came back the following season: 54% → 61%.
• Total program cost: RM 36,800 build + RM 1,850 a month retainer.
• Payback: 7 weeks, on RM 24,600 of mispriced paddy caught in the first ten weeks, against a build that cost RM 36,800.

What it would cost for your business

We don't publish a price sheet, because the price depends on how many loads cross your bridge a day. Three honest bands for a Kedah or Perak agri business:

• RM 18,000 – RM 28,000 build + RM 900 – RM 1,400 / month. Single yard, one weighbridge, paper tickets, one price list, farmer receipts at the counter. Up to 15 loads a day, 3 to 4 week build.
• RM 28,000 – RM 46,000 build + RM 1,400 – RM 2,600 / month. Multiple intake points, a deduction rule set matching your licensed SOP, WhatsApp receipts, buyer invoicing from the same ledger, day-end exception reporting and a per-farmer season ledger. The band this trader sits in. 5 to 7 week build.
• RM 46,000 – RM 85,000 build + RM 2,600 – RM 5,000 / month. Multi-yard or mill-and-trader, lab readings feeding the deduction rules, settlement and financing layers, accountant handoff, claims handling.

The same bands run on our Kedah business automation page; Perak equivalents are adjusted for field conditions.

What this looks like for your business

If you run a business where a number gets read off an instrument and then written down by a person, that number is a decision waiting to go wrong — and in a 1,850-load season it does not go wrong once. It goes wrong quietly, and shows up three weeks later as a farmer who does not trust your receipt.

We have built the same shape for an Ipoh wholesaler who closed every night with a 90-minute stock count and for a Taiping auto-parts distributor whose dispatch cycle ran four hours. On the agri side, an Alor Setar rice mill built a demand-forecast model for the other end of the chain — forecasting what to plant against, where this build makes sure what was bought gets paid for.

If you want to talk it through, book a 30-minute call. We will look at how many loads cross your bridge and how your deduction is calculated today, then come back with a number and a build week. We don't pitch you either way — for a yard running fewer than ten loads a day, a better weighbridge and a disciplined paper file may genuinely be right.