Blog

Farm management guides

Short guides for plantation supervisors: piece-rate payroll, logging harvest with no signal, keeping stock and dispatch in one record, spotting a crop problem with a Kani photo, running dual payroll for pickers and permanent staff, recording attendance and leave so they flow into payroll, and reading profit and loss for the year. Prefer trying it? Create a free account and open a session.

Create free account

Guide

How piece-rate harvest payroll works on a plantation

A short walkthrough for supervisors who still total wages in a notebook.

Open a harvest session for the crop and field you are picking today. Each session is one block of work: pepper this morning, rubber tapping this afternoon, coconut on Thursday. The session stays open until you close it.

As workers bring in produce, log the weight against their name. Piece-rate pay is the weight times your rate per kilogram. Daily-rate and hybrid wages sit beside that, so a crew that mixes tapping and day labor does not need a second book.

Food charges and cash advances come off the wage before you approve the run. When the session closes, the totals are already there: who picked what, what it cost, and a payslip you can download. The same entries feed stock, so you are not typing the harvest twice into inventory.

That is the whole loop. If the block has no signal, log the weights in the Android or iOS app and let them sync when you are back on the road. Permanent staff stay on a separate monthly payroll, so pickers and salaried workers are not forced into one rate.

Related: farm payroll software, harvest management app.

Guide

Log plantation harvests offline — then sync when you get signal

A short walkthrough for supervisors whose blocks still have no mobile coverage.

Many spice, rubber, and coconut blocks in India still have no usable signal until you reach the main road. Harvest still has to be logged the same day, or payroll and stock fall behind.

Open a harvest session in the NilamFlow Android or iOS app before you walk out. Pick the crop, field, and pay rate the same way you would on the web. The session stays on the phone even when the network drops.

As workers bring in produce, log each weight against their name. Piece-rate and daily-rate entries sit in the same session, so mixed crews do not need a paper sheet as backup. When you regain signal — office Wi‑Fi or roadside data — the app syncs. Those weights feed payroll and inventory automatically, so you are not retyping the day's harvest into a spreadsheet.

That is the loop: capture in the field without signal, sync once, and keep payroll and stock aligned. Permanent staff stay on the separate monthly payroll, just as on the web.

Related: farm payroll software, harvest management app.

Guide

From harvest to dispatch: one stock record for your plantation

For estates that keep a harvest book, a store register, and dispatch slips, and want them to agree.

Many plantations keep three records for the same produce: the harvest book in the field, a stock register in the store, and a slip for every buyer load. When they drift apart, nobody can say how much copra, pepper, or rubber is actually on hand, or whether a load left with what the buyer was billed for.

In NilamFlow, the harvest session is where the stock record starts. Weights you log against workers in the field, online or offline, are added to inventory for that crop when you close the session. Nobody copies the day's harvest into a stock book.

When produce leaves the estate, record it as a dispatch: the vendor, the net weight, and the price per kilogram. Stock on hand drops by that net weight, so the store count and the dispatch records tell the same story at the end of the week.

Paid harvest wages and each dispatch total sit on the same farm. Profit & Loss counts vendor dispatch totals as income and paid harvest team payroll as a cost, along with retail sales and the farm's other costs. This month's profit is on the dashboard, so you are not working the figure out from separate books at year end.

That is the loop: log the harvest once, close the session so it becomes stock, dispatch from that stock, and read profit from the same records.

Related: farm payroll software, harvest management app.

Guide

Watch daily crop prices before you sell

A short walkthrough for estates that want the latest market rate in front of them before the next load goes out.

Before a load of pepper, cardamom, or rubber leaves the estate, most supervisors ring a trader or check a board for the day's rate. NilamFlow keeps those reference prices on one page, Market Prices, for the crops you choose to watch.

Open Market Prices and press Manage Crops. Only crops registered to your farm are listed. Tap the ones you want under Watched Crops, then press Save Preferences. NilamFlow fetches daily prices from public sources: the Rubber Board for rubber, and data.gov.in, Agmarknet, AgMart, and the Spices Board for other crops.

Price Trends draws a chart for each watched crop. Pick Last 7 days, Last 30 days, or Last 12 months under Period. Beside the latest price, the change over that period is written out as a percentage, with the direction read out to screen readers as Price up, Price down, or Price unchanged. Below the chart, Latest prices by market shows each market's most recent quote with Effective, Min, Max, Modal, Official, and Export columns and the date of the quote.

If you use the NilamFlow phone app with notifications on, a Daily crop prices updated notification comes at most once a day when a watched crop has a new price. It lists each crop with the price and an up or down arrow against the previous published quote. Crop Prices is its own notification category, so it can be turned off without losing other alerts.

These are reference rates. They do not change the price on your dispatches or sales; you still enter the price per kilogram you agreed with the buyer. Use them to decide when to sell and what to ask for.

Related: harvest management app, pricing.

Guide

Spot crop problems early: photo diagnosis with Kani

A short walkthrough for supervisors who want a first check on a sick vine, palm, or tree before they leave the block.

On a large pepper, coconut, rubber, cardamom, coffee, or tea block, a few marked leaves can sit in one corner until the row is already behind. Checking the plant the same day tells you whether to watch it, or to call someone before you decide on a spray.

Take the photo in daylight, close enough that the marks on the leaf or fruit are sharp. One problem in the frame is easier to read than a shot of the whole row. Look at the whole plant while you are there, so you know if it is one leaf or the tree, and send Kani the close photo of the leaf or fruit. If Kani cannot read the photo, it says so and does not use a credit. Take a closer, sharper picture and try again.

On the web, open Kani from the farm workspace, or press Ask Kani. If the check should stay on one crop, choose it under Crop before you attach the photo. The list is the crops already on this farm, or All crops. Type a short note first if you want the block or tree saved with the picture, then press Photo and attach a JPEG, PNG, or WebP. Kani starts as soon as the photo is attached. A written question is optional. The phone app calls the same Kani chat; Photo, Crop, and Ask are the labels on the web screen.

Read the reply in the chat. When Kani includes a confidence score, the label under the reply is High confidence, Some uncertainty, or Low confidence, and source titles appear when it has them. A reply it could diagnose uses 1 credit. The photo and the reply stay on that farm's Kani conversation, so anyone else on the farm can open it later.

Treat that reply as a first check, not a substitute for a visit. If the problem is spreading, the label is Low confidence, or you are about to choose a pesticide, take it to a local agronomist, the Krishi Bhavan, or a KVK, or send a sample for a lab test, before you spray. Kani is for people signed in to NilamFlow. On the pricing page it is listed on Pro at 100 credits/month and on Estate at 1000 credits/month. If this farm is not on one of those plans, the screen says Kani is part of the Pro plan.

Related: pricing, harvest management app.

Guide

Dual payroll on a plantation: pickers and permanent staff

A short walkthrough for estates that pay picking crews by the session and salaried staff by the month.

On many pepper, coconut, rubber, cardamom, coffee, and tea estates, two kinds of pay share the same week. Harvest pickers are paid from the weights, days, or trees logged in a harvest session, depending on the pay mode. Permanent staff are paid on a recurring run — daily, weekly, bi-weekly, or monthly. Mixing those into one notebook is where food charges and statutory deductions get lost.

NilamFlow keeps them as two payrolls. The Payroll Runs page help calls this part of the Dual Payroll Engine: this page is for permanent employees, and harvest worker payroll is separate. Open a harvest session and use the Payroll tab inside it.

Open a harvest session for the crop and block you are picking. Log each weight against the worker. Pay mode sits on the team member, not as one setting for the whole team. The modes are Weight only, Daily only, Daily + Weight, Salary only, Salary + Weight, and Per tree. Weight pay uses the logged quantity. Daily pay uses days marked Present. Per tree uses the trees recorded on the entry. If tree pay is already in the calculation, weight pay is not added on top. A base salary portion is added for the session only when Include base salary is turned on for that member, using their staff payroll config. Salary + Weight does not add that salary by itself.

When the farm handles grocery for the crew, and that session has a grocery cost, the cost is split across Present days and Leave days. Permanent and contract employees on that team are not charged those food days. Absent days are not charged. Close the session and payroll is calculated with it. Each run starts as draft. Approve it to lock the amount, then mark it paid. Food deduction comes off gross pay before net pay. Draft and approved harvest runs also show under Pending Harvest Payroll on the Payroll Runs page, with a link back to the session.

Set each employee's frequency and base pay under Employees, on Recurring Payroll Config, before you create a run. On Payroll Runs, press New Run, choose the frequency and the period, then Create Run. Entries are generated for employees whose active config uses that frequency. Attendance can add Absent days and Half days deductions. Approved unpaid leave can add an Unpaid Leave line. Approve the run — the confirm step locks the entries — then mark it paid. That is the staff loop: create, review, approve, pay.

Statutory settings are farm-wide under Statutory Payroll Settings. They apply to permanent staff salaries only, not to harvest or picking team pay. Turn on Provident Fund, ESI, professional tax, and TDS as needed. Set the PF and ESI rates and ceilings, and the professional tax slabs, on that screen. TDS is a switch there; its slabs are the New Tax Regime for FY 2025-26, with a ₹50,000 standard deduction, not a rate you type in. Per employee, turn PF or ESI on or off and set the TDS category under Employees → Statutory. TDS is calculated only when that category is Salaried. When the run is created, and again when you approve it, deductions above zero appear as line items — PF (Employee), ESI (Employee), Professional Tax, and TDS — and net pay drops by those amounts. Employer PF and ESI are stored on the pay entry, including a cost-to-company total. They are not taken from the worker's net pay.

PF, ESI, and professional tax follow the rates and slabs you configure. Keeping those correct for your state and for current law is still your responsibility; the app records and applies what you set. The TDS slabs stay on the FY 2025-26 new regime built into the app.

On harvest payroll, review the draft runs after the session closes, then approve and mark paid. On staff payroll, open the run, confirm attendance and statutory lines, approve, then mark paid. Paid harvest wages and paid staff payroll both appear on Profit & Loss, as Harvest team payroll and Staff payroll, so month-end cost is not left in a harvest book and a separate salary sheet.

Related: farm payroll software, harvest management app.

Guide

Attendance and leave for estate staff, and how they flow into payroll

A short walkthrough for pepper, coconut, rubber, cardamom, coffee, and tea estates that mark staff days and picking days before pay.

Permanent staff and picking crews are marked in different places. Under Workers, open Attendance. The page is Staff Attendance, and the help title is Daily Staff Attendance. It lists active permanent staff only. Picking crews are marked on the harvest session, on Team & Attendance, under Harvest Attendance. Those two marks do not feed the same pay lines.

On Staff Attendance, choose the date. It cannot be later than today. For each person, press P for Present, H for Half Day, A for Absent, or L for Leave. The status is saved instantly on click. Mark all asks you to confirm first, for example: Mark all employees as Present for this date? A note can be saved on the row. Payroll does not read that note. The cards count Present, Half Day, Absent, Leave, and Unmarked. If there is no active permanent staff, the page says No active employees found, and offers Add an employee.

The page describes Absent as a day the person did not report without approved leave, and treats it as an unpaid absence in payroll. It describes Leave as a day away with approved or recorded leave, kept separate from an unplanned absence. In the staff payroll run, only Absent and Half Day become attendance deductions. Present, Leave, and a day left unmarked do not add an Absent days line or a Half days line.

Leave requests are under Workers, then Leave. The page is Leave Management. Press New Request, or open the Apply Leave tab. The form is New Leave Request: Employee, Leave Type, From Date, To Date, and an optional Reason, then Submit Request. The count shown is working days, and Sundays are left out of that count. Saturday is counted. The request stays Pending until you act. All Requests can be filtered by All, Pending, Approved, Rejected, or Cancelled. Approve asks you to confirm: Approve this leave request? Reject opens Reject Leave Request, requires Reason for rejection, then Confirm Rejection. Cancel on a pending request asks: Cancel this leave request? Cancel on an approved request asks: Cancel this approved leave? The leave balance will be refunded.

Press Leave Types on that page. That is the Leave Types tab in Settings. Each type has Name, Days Per Year, and Paid leave. A new farm starts with Casual Leave, Sick Leave, Earned Leave, Maternity Leave, Paternity Leave, Compensatory Leave, and National Holiday as paid, and Loss of Pay Leave as unpaid. You can edit a type or add one. The list shows Paid or Unpaid beside the name. The Employee list on Leave Management is every active employee, not only permanent staff. Approving adds the request's working days to the used count for that type, for the year of From Date. Approval is not stopped when those days go past Days Per Year. Cancelling an approved request puts those used days back, and removes the Staff Attendance rows for those days only where the status is still Leave. Approving also sets each of those days, Sundays excluded, to Leave on Staff Attendance, including a day you had already marked.

Staff pay is under Wages. The page is Payroll Runs. Set frequency and base pay on the employee, under Recurring Payroll Config, before the run. Press New Run, set Frequency, Period Start, and Period End, then Create Run. The run includes employees whose active config uses that frequency. The daily rate for these deductions is the base amount divided by the calendar days from Period Start through Period End, Sundays included. Days marked Absent in that period add one deduction labelled Absent days. The amount is those days times the daily rate. Days marked Half Day add one deduction labelled Half days, at half a daily rate for each of those days. An approved request whose type is not paid adds one deduction labelled Unpaid Leave, for the unpaid days times the daily rate. Only the days inside the payroll period are counted, and Sundays in that overlap are left out. A type with Paid leave on does not add that line. Absent days follows the attendance mark. Unpaid Leave follows the approved request. If you later mark one of those days Absent, both lines can include it.

The lines are written when the run is created. On a draft, Refresh from attendance rebuilds them from the current marks and from approved unpaid leave. The confirm says manual allowances and deductions will stay. Approve asks: Approve this payroll run? This will lock all entries. Approving rebuilds the same lines, then locks the run. Removing Absent days, Half days, or Unpaid Leave by hand is refused, because attendance, leave, and statutory deductions are refreshed automatically. Then Mark as Paid. The confirm says this will finalise all payments. Net pay is gross pay minus deductions, and it is not taken below zero.

For pickers, open the harvest session and Team & Attendance. Harvest Attendance says Present counts for harvest pay and food, Leave counts for food only, and Absent counts for neither. Mark Present, Leave, or Absent, or use All Present, All Leave, or All Absent. Those buttons stay off once the session is paid. Daily pay, for Daily only and Daily + Weight, uses days marked Present between the session open date and the close date. Leave and Absent do not add a daily-pay day. Weights and trees already logged are still counted for weight pay and per-tree pay. Record the grocery on Food Costs. When Grocery Handled By is Farm, and that session has a grocery cost, the cost is split across Present days and Leave days. Permanent and contract employees on that team are not charged, and their days are left out of the split. Absent days are not charged. When Grocery Handled By is Team, that grocery cost is not taken off pay. Close Session calculates the payroll. The Payroll tab says wages are auto-computed when the session is closed. While every run is still draft, Recalculate Draft replaces that calculation. Once a run is approved, it cannot be recalculated. Food deduction comes off gross pay before net pay.

Related: farm payroll software, harvest management app.

Guide

How a plantation Profit & Loss is worked out

A short walkthrough for pepper, coconut, rubber, cardamom, coffee, and tea estates that want the year’s income and costs from the records already kept.

Open Reports. The page is Profit & Loss, and the badge reads Annual report. Under the title, the period is 1 January to 31 December of the year chosen in Year. That list runs from three years back to next year. There is no shorter period, and nothing on the page is a profit for one crop or one season. An owner or a manager can open it. A staff role cannot. Download PDF is for the owner. While the file is prepared, the button reads Preparing...

Total Revenue is net shop sales plus vendor dispatches. The note under the card says Net sales plus dispatches. Vendor dispatches is each dispatch’s Total Amount, dated by Dispatch Date. Record Payment does not change it, so an unpaid dispatch is still income. Under Sales, open Dispatch, then New Dispatch, and press Record Dispatch. Set Vendor, Dispatch Date, Gross Weight (kg), Sack Type, Sack Count, and Price per kg (₹). Net Weight (kg) is filled from the gross weight minus the sack deduction, and Total Amount (₹) is filled as that net weight times the price. The report uses the Total Amount saved on the dispatch. Retail sales (gross) is the Subtotal of each shop sale, dated by Sale Date. Under Shop Sales, open New Sale. Subtotal is the sum of the line Amounts. GST is not included, and Mark as Paid does not move the month. List for Sale, Marketplace, and Buyer Orders are not on this report.

On a shop sale, Credit Note opens Issue Credit Note. Fill Date, Credit Amount (₹), and Reason, then press Issue Credit Note. The note is applied as of the Date you typed. Less: credit notes uses that Date for the year, not the moment you pressed Issue Credit Note, and not the original Sale Date. The line is shown only when the year’s notes are above zero, with Net retail sales under it. Net retail sales is shop-sale subtotals minus those notes, and it is not taken below zero. The form starts Credit Amount (₹) at the Subtotal still left to credit, and it cannot go above the invoice total still left. This income line uses Subtotal, which does not. Each month’s shop-sale figure in Monthly Sales Revenue is not taken below zero on its own. The year figure is worked out once, so a month whose notes exceed that month’s subtotals can leave the monthly Revenue total and the year’s Total Revenue different.

Operating Expenses starts with the two wage lines. Staff payroll is the net pay of staff runs you have marked paid. Under Workers, open Wages. The page is Payroll Runs. Press New Run, set Frequency, Period Start, and Period End, then Create Run. Approve, then Mark as Paid. A draft or approved run is left out. The month is the month of Period End, even if you mark it paid in a later month. The whole net pay sits in that month. It is not split between Period Start and Period End. Net pay is what remains after the deductions on that run, and it is not taken below zero. Employer PF and ESI are stored on the pay entry and are not part of that net pay, so they are not in Staff payroll. Harvest team payroll is the net pay of harvest runs that are paid and have a paid time. On the session, open the Payroll tab. Approve or Approve All, then Mark Paid or Mark All Paid. A draft or approved harvest run is left out. The month is the month of that payment, not the session open or close date. Net pay is after the food deduction, and it is not taken below zero.

Grocery purchases is each grocery Amount, dated by Date. Under Harvest, open Worker Groceries. The page is Grocery Expenses. Record Expense asks for Team, Date, and Amount (₹). The form title is Record Grocery Expense. You can record a grocery there, or on the harvest session under Food Costs. Each saved Amount is included, whether or not it has been paid. When Grocery Handled By is Farm, the food charged on the harvest run is already taken off that net pay. Harvest team payroll is lower by that deduction. The grocery line is still the full spend, not a second copy of the wage. When Grocery Handled By is Team, that food is not taken off pay, but a grocery you still record stays on Grocery purchases. Inventory purchases is the Total of each purchase, dated by Purchase Date. Under Inventory, open Purchases, then New Purchase, and Save Purchase. Total includes Tax, Transport, and Other. Paid now does not change the cost, so an unpaid bill is included. Farm expenses is each expense Amount, dated by Date. Under Expenses, open Farm Costs. The page is Farm Expenses. Record Farm Expense asks for Category, Date, and Amount (₹), then Save Expense. Where a category was used, the report lists it under Farm expenses: Fuel, Seeds, Fertilizer, Equipment, Maintenance, Transport, Utilities, and Other. Those lines are the split of Farm expenses. They are not a further cost. Total Expenses is the five lines together. The card calls the same figure Total Costs, and the note reads Payroll, purchases, groceries & expenses.

Net Profit is Total Revenue minus Total Expenses. Below zero, the label is Net Loss. On Statement Summary, the badge reads Healthy when the year is a profit, Break-even when income and costs match, and Needs attention when it is a loss. The card says Margin for the chosen year. If Total Revenue is zero, the mark beside the title says No revenue. If Total Revenue is above zero and the year is a profit, that mark is the margin, and the line under Net Profit shows it with the words profit margin. A loss uses the words loss margin. A year that matches exactly says Break-even. Revenue vs Costs compares each month. Monthly P&L Summary lists Revenue, Costs, and Net from Jan to Dec. A zero in a row shows a dash, including a Net of zero when that month’s revenue and costs match. Monthly Costs names the same costs Staff Payroll, Harvest Payroll, Groceries, Inventory Purchases, and Farm Expenses. Stock Activity shows Usage records and Quantity used. Those figures are not rupees, and they are not in Net Profit. The page does not value unsold stock. For the owner, the dashboard block This month shows Profit or Loss. Revenue there is dispatch totals for the month plus shop-sale subtotals, and Costs uses the same five lines. Credit notes dated in that month are taken off that dashboard Revenue.

Related: farm payroll software, harvest management app.

Read the year from the records you already keep

Create a free account and open Profit & Loss.

Create free account