Agriculture: fields, crop cycles, livestock, automation, costing and harvest revenue
Set up fields, crop types and livestock, run a crop cycle from planting to harvest, post costs and revenue to the ledger, and optionally automate irrigation and feeding.
On this page
Process at a glance
- Set up master dataFarm managerFields, crop types, livestock profiles and animal groups.
- Plan a crop cycleAgronomistA Planned cycle with budget and expected yield.
- Start and run the cycleFarm managerCycle Growing; costs recorded and posted.
- HarvestFarm managerYield and sale rate recorded; revenue journal posted.
- Close the cycleFarm managerCycle closed once every cost is posted.
- Livestock feeding and costsLivestock supervisorFeeding events become livestock cost entries, posted to the ledger.
- Compare seasonsFarm managerYield and cost variance by crop type and planting year.
#Purpose and scope
This chapter covers the Agriculture module: field, crop type, livestock profile and animal group master data, the crop-cycle lifecycle with costing and harvest revenue, livestock feeding and cost entries, irrigation and feeding automation, and season comparison.
#Before you start
- Expense, payable (or cash), receivable and revenue ledgers in the chart of accounts. They are only needed when you post a cost or a harvest.
- Permissions: agriculture.cost.post (post a crop-cycle cost), agriculture.harvest.record (record a harvest), agriculture.livestock_cost.post (post a livestock cost) and agriculture.cycle.transition (start or close a cycle). The seeded FARM-MANAGER role is described as owning field and crop planning, irrigation scheduling, sensor-driven decisions and cost and harvest postings.
- For automation, IoT devices bound to the field or animal group (see the IoT guide).
#1. Master data
- Create Fields with a code, name and area in hectares. Purpose is Crop, Pasture or Barn. Soil type, location (free text) and company scope are optional.
- Create Crop types with the soil moisture, temperature and humidity ranges the crop prefers, an optional growing-degree-day base temperature and the typical days to harvest.
- Create Livestock profiles with the body temperature range and the feed ration per head with its unit.
- Create Animal groups (herd or pen) with species and head count, optionally linked to a field and a livestock profile.
#2. Plan and start a crop cycle
- Open Crop cycles and create a cycle with a code, field, crop type, planting date, expected harvest date, expected yield and unit, and budgeted cost. The expected harvest date cannot be before the planting date, and the field must exist.
- Optionally break the budget down by seed, labour, irrigation and other categories. The Budgeted Cost total stays independent of the breakdown.
- Open the cycle and choose Start cycle. Only a Planned cycle can be started; it becomes Growing.
| Status | How it is reached | What is allowed |
|---|---|---|
| Planned | Created | Edit, start, record costs |
| Growing | Start cycle | Record a harvest, record and post costs |
| Harvested | Record harvest | Late costs are still accepted; Close cycle |
| Closed | Close cycle | No further edits; no costs can be added or posted |
#3. Record and post costs
- On the cycle’s Cost Entries tab add a cost with a description and a positive amount. Choose the expense ledger (debit) and the payable or cash ledger (credit); they are only required to post.
- Post the entry to the ledger (needs agriculture.cost.post). Posting debits the expense ledger and credits the payable ledger, and tags the journal to the cycle so actuals roll up per cycle. Posting twice has no further effect.
#4. Harvest and revenue
- On the Harvest & Revenue tab enter the actual harvest date, the actual yield quantity and the sale rate per unit (all positive), and choose a receivable ledger and a revenue ledger.
- Record the harvest (needs agriculture.harvest.record). BSuit posts a journal for yield × rate: debit receivable, credit revenue. The cycle becomes Harvested.
#5. Close the cycle
- Post or delete every unposted cost entry.
- Choose Close cycle on a Harvested cycle (needs agriculture.cycle.transition).
#6. Livestock feeding and costs
- Record each feed dispense in Feeding events: animal group, time, source, quantity and unit.
- On a feeding event choose Create cost entry. Pick the basis: unit cost × quantity dispensed, or a total amount, and optionally the expense and payable ledgers.
- Open the animal group and, on its Cost Entries tab, post the entry (needs agriculture.livestock_cost.post). Posting debits the expense ledger and credits the payable ledger, tagged to the animal group.
#7. Irrigation and feeding automation
Every field and animal group starts with automation Off. In Fields and Animal groups choose Dry run or Live per record. Off only alerts and never actuates; Dry run logs what it would do without sending a command; Live issues a real IoT command. Irrigation events and Feeding events show the log, with the source (manual, rule or dry run).
| Track | Trigger | Guardrails |
|---|---|---|
| Irrigation (fields with a crop cycle whose crop type is set) | Soil moisture below the crop type’s range, or moisture within 5 points of the minimum while temperature is above range and humidity is below range | One hour cooldown between triggers; a daily cap in seconds per field that overrides telemetry once reached |
| Feeding (animal groups) | Schedule only: no feeding event in the last 24 hours | One hour cooldown; a daily feed cap per group |
#8. Compare seasons
Season comparison groups every crop cycle by crop type and planting year and shows expected and actual yield, budgeted and actual cost, yield and cost variance and net margin. Actuals are sourced from the ledger.
About this guide
- Status
- Partially reviewed
- Application
- BSuit ERP
- Audience
- Farm managers, agronomists, livestock supervisors and farm accountants
- Owner
- BSuit documentation team
- Reviewer
- Editorial review pending
- Last verified
- 2026-10-03
- Checked against
- cb3691bbf
- Seen on a running system
- Not yet
- Help version
- 2026.0.0-preview
- Guide ID
erp:article/guide/agriculture-farm-cycle
Known limits: Written from a read of the implementation; statements traced to source. Not yet walked through end to end by a trainer on a running system.