Own stock and customer stock mixed
Contract milling paddy sitting in the same godown balance as your own, so neither figure is trustworthy.
A husking mill does not need everything an auto rice mill needs. It needs the paddy register, the godown balance and the outturn to be right — and to stop living in three notebooks. That is where CloudMill starts.
We will be direct, because it saves everyone time: if you run a husking mill or a chatal, most of what an ERP salesperson will show you is not for you. Formula version control, biometric shift rosters and multi-company consolidation are real features, but they solve problems a twenty-tonne-a-day husking unit does not have. Paying for them is how small mills end up with software they log into twice a month.
What a husking mill does need is narrower and more urgent. Paddy arrives from several sources at several moisture levels. Some of it is milled on contract for someone else. Rice, bran and husk leave on different days to different buyers, often partly on credit. The register book records all of this faithfully and still cannot answer the one question that matters: is the outturn you are getting the outturn you should be getting?
CloudMill’s entry configuration covers exactly that — purchase, stock, milling, sales and a real ledger — and leaves the rest switched off until you grow into it. If you later add a second unit or move to automatic milling, the same account expands. You are not migrating twice.
Contract milling paddy sitting in the same godown balance as your own, so neither figure is trustworthy.
Rice goes out on credit to buyers whose outstanding balance nobody can state without opening three pages.
A percentage inherited from the way it has always been, with no way to tell if this season is worse than last.
The husking mill configuration ships with these five flows switched on. Everything else in CloudMill stays available but out of your way.
Supplier, variety, quantity, moisture, deduction and rate in one entry. Advances paid during the season adjust automatically when the paddy arrives, so settlement stops being a negotiation.
Your own paddy, customer paddy for contract milling, rice, bran, husk and bags each carry their own live balance. A physical count becomes a confirmation instead of an investigation.
Record what went in and what came out. CloudMill calculates the outturn and shows it against your own history for that variety, so a bad month is visible in the month it happens.
Cash and credit sales of rice, bran and husk with a running party balance. You can see who owes what before the next truck leaves the yard.
A genuine double-entry ledger underneath — cash book, party ledgers, expenses and a profit figure you can defend to a lender or a partner.
Illustrative figures for one month at a mid-sized husking unit. Nothing here is exotic — this is arithmetic a register book makes almost impossible to do, and a system does automatically.
| Line | Figure |
|---|---|
| Paddy milled in the month | 240,000 kg |
| Rice produced and sold | 148,000 kg |
| Bran sold | 18,500 kg |
| Husk sold or used as fuel | 49,000 kg |
| Measured outturn | 61.7% |
| Your own benchmark for this variety | 64.0% |
| Gap | 2.3 percentage points |
| Rice not produced | 5,520 kg |
| Value at ৳52 / kg | ৳2,87,040 |
Nearly three lakh taka in one month, from a gap that never appears in a register book because the register book never divides one column by another. The fix might be drying, blade wear, or a supplier sending poorer paddy than you are paying for — but you cannot fix what you cannot see.
Supplier-wise purchases with moisture, deduction, rate and advance adjustment — the notebook, but it adds up correctly.
Separate live balances for own paddy, customer paddy, rice, bran, husk and packaging across your stores.
Measured per milling run and compared with your own history by variety and season.
Third-party paddy tracked separately with milling charges raised against the owner, never mixed with your stock.
Cash and credit sales with running balances, so you know who owes what before you load the next delivery.
A real double-entry ledger with expenses, party accounts and a monthly profit figure that stands up to scrutiny.
Entry and balance checks from an Android phone, because most husking mill owners are not sitting at a desk.
Entries queue locally through a power cut or a dead connection and sync when the line returns.
Switch on production batching, payroll, VAT and multi-site whenever you need them. Same account, no migration.
Short, readable, and available on a phone — not a forty-page pack nobody opens.
| Report | The question it answers |
|---|---|
| Daily paddy and rice movement | What came in, what got milled, what went out today? |
| Outturn trend | Is this month better or worse than last, and for which variety? |
| Godown stock summary | What do I actually have, separated from what belongs to a customer? |
| Party balance (receivable) | Who owes me money and for how long? |
| Supplier balance and advances | What have I paid in advance, and against how much delivered paddy? |
| Cash book | Where did the cash go this week? |
| Contract milling statement | How much have I milled for each customer, and what charge is due? |
| Monthly profit summary | Did the mill make money this month, after by-products and expenses? |
Proper invoices and challans for buyers who need them, with VAT formats available when you register or when a buyer requires it.
Stock and receivable statements for a CC limit produced from live balances rather than assembled the night before.
Contract quantities and delivery challans kept against the contract so procurement reconciliation is straightforward.
Attendance and daily wage payment records kept properly, including advances and recoveries.
Document expiry reminders so a licence or a lease does not lapse unnoticed mid-season.
Every entry timestamped and attributed. When a figure is questioned, you can show how it got there.
The full suite would be, which is why the husking mill configuration ships with only five flows switched on: purchase, stock, milling, sales and accounts. You are not paying for or looking at modules you do not use, and you can turn the rest on whenever you need them.
Pricing depends on the number of users and which modules you switch on, and the entry configuration is priced for a small mill rather than a group. Talk to us with your actual volumes and we will tell you plainly whether it is worth it for you — including if the answer is not yet.
Yes, and this is one of the first things most husking mills fix. Third-party paddy is held as customer stock with its own balance, and milling charges are raised against the owner. Your godown figure only ever shows what is yours.
A phone is enough for daily entries and balance checks. Most mills use an Android phone at the gate and a laptop or desktop in the office for month-end work and printing.
Entries are queued locally and sync when the connection returns. Losing power does not mean losing the day’s data.
A notebook records transactions accurately. What it cannot do is divide one column by another across a season, which is why outturn drift and credit leakage stay invisible until they are large. If your mill is small and stable, a notebook may genuinely be enough — we will say so.
No. The same account moves to the auto rice mill configuration, keeping your history, suppliers, buyers and balances. You add the flows you now need instead of migrating to different software.
Full paddy-to-payment costing with weighbridge, by-product credit and VAT.
For mills that have added a feed line alongside rice milling.
Oil, dal, spice, aqua feed and cold storage configurations.
Explore the full feature set or browse all industries.
A short conversation about how much paddy you handle and how you sell is usually enough for both of us to know whether this is worth doing. If it is not yet, we will say so.