Appearance
Agriculture Overview
Agriculture supports farm operations from planning and field work to funding, evidence, stock, sales, settlement, payment, accounting, and reporting. It is designed for small farms, cooperatives, produce aggregators, managed plantations, livestock and poultry operations, processors, exporters, NGO or grant programs, and large estates with remote teams.
Agriculture is not a separate copy of Inventory, Projects, Payments, Inspections, Billing, Reporting, or GL. It provides the agriculture operating model, capability guidance, source-document types, contextual entry points, and agriculture-specific reports. The shared primitives remain the owners of records and financial consequences.
What Agriculture Pages Are For
Use Agriculture pages for these three jobs:
- Understand the tenant operating model and active capabilities.
- Create or review agriculture-specific source workflows such as field activities, producer contracts, produce deliveries, buyer sales, and settlement statements.
- Launch the user into the correct shared primitive when the workflow moves into party management, project funding, stock, inspection, payment execution, reporting, or GL.
Do not treat Agriculture as a second CRUD menu for shared primitives. If the task is maintaining core party data, project funding, stock balances, inspection records, payment execution, or report execution, go to the owning module.
What Agriculture Can Support
| Operating model | Typical use |
|---|---|
| Managed plantations or investor farms | A tenant manages farms or blocks for clients, investors, groups, or organizations. Funds are received for a project and spending must be traceable by project, WBS, worker group, document, payment batch, and GL. |
| Estate farming | The tenant owns or operates farms and tracks seasons, blocks, activities, stock, workers, machinery, inspections, costs, and sales. Project/WBS may represent seasons, farms, blocks, or campaigns. |
| Produce aggregation and cooperatives | Farmers, producer groups, or suppliers deliver produce for grading, stock intake, buyer sales, settlement statements, and payout batches. |
| Contract farming and outgrower programs | Contracts, input issue, field supervision, produce delivery, grading, deductions, and settlement are central. Projects may represent seasons or campaigns. |
| Grants and NGO agriculture programs | Restricted funds, project budgets, approved spending, evidence, reports, and donor accountability are mandatory. |
| Livestock and poultry | Animals, flocks, pens, events, feeding, treatment, mortality, weighing, inspections, stock consumption, and sales can be captured through shared events, stock, inspection, and document primitives. |
| Processing and export | Produce moves through stock, quality, dispatch, buyer sales, billing, costing, and reporting. Market-price snapshots can support pricing and settlement where enabled. |
| POS farm sales | A farm shop, depot, or produce outlet sells stock through the shared POS flow while Agriculture keeps the commodity and farm context. |
Capability Presets
Capabilities are enabled for a tenant from Platform Admin -> Companies -> Manage Services. Tenant Agriculture pages may show read-only capability status, but they must not activate services or sync seed packs directly.
| Capability | What it unlocks |
|---|---|
| Basic Farm Operations | Locations, farms, blocks, parties, operational items, work records, and basic guidance. |
| Field Operations | Field activity events, work completion documents, attendance evidence, spending requests, and approval handoff. |
| Worker Groups | Group leaders, worker attendance, group-based evidence, payout preparation, and repeat attendance analysis. |
| Project Fund Control | Project/WBS funding, fund receipts, approved obligations, payment-batch funding context, GL due-to/due-from accounting, and fund reports. This is owned by Projects & WBS. |
| Managed Plantation | Owner/funder party context, service contract support, client fund traceability, management fees, and investor reporting. |
| Produce Aggregation | Producer contracts, produce delivery, grading, stock handoff, buyer sales, settlements, and farmer payout. |
| Livestock | Animal or herd events, health/treatment evidence, feeding, stock consumption, mortality, and sale/disposal records. |
| Poultry | Flock events, feed, mortality, egg or bird production, inspections, and stock/sales handoff. |
| POS Farm Sales | POS sales of farm produce or inputs through the shared POS and stock primitives. |
| Offline Field Capture | Work-pack download, local capture, sync review, evidence queue, duplicate checks, and conflict resolution. |
| IoT And Telemetry | Device/checkpoint status, stale-device alerts, low-battery exceptions, sensor/camera incident summaries, and review reports. |
| Market Intelligence | Commodity price snapshots, market references, formula pricing, settlement/buyer-sale linkage, and audit trail. |
Primitive Ownership
Agriculture uses these shared modules instead of duplicating them:
| Shared primitive | Agriculture use |
|---|---|
| Parties | Farmers, workers, group leaders, supervisors, investors, funders, suppliers, buyers, transporters, vets, and agents. |
| Projects & WBS | Farms, blocks, seasons, investor projects, grant programs, budgets, fund receipts, obligations, cross-funding, and fund reports. |
| Events | Field activities, animal events, supervisor checks, work completion evidence, device exceptions, and operational history. |
| Document Transactions | Funding agreements, fund receipts, attendance sheets, work reports, input issues, obligations, contracts, settlements, and buyer-sale support documents. |
| Inventory | Inputs, produce, lots, warehouses, transfers, stock issues, harvest stock, feed, drugs, packaging, and valuation. |
| Inspections | Quality checks, grading, produce inspections, field verification, livestock/poultry checks, and evidence review. |
| Payments | Worker, supplier, farmer, transporter, and settlement payout batches. |
| Billing And POS | Buyer invoices, service fees, farm shop sales, and revenue recognition. |
| GL And Posting Rules | Cash/bank, project due-to/due-from, stock, revenue, expense, settlement, and payment postings. |
| Reporting | Agriculture reports, project fund reports, market snapshots, telemetry summaries, utilization, and drilldowns. |
Navigation Reference
| Area | Open from | Purpose |
|---|---|---|
| Operating model | Agriculture -> Setup -> Operating Model | See active capabilities, service guidance, and which shared primitives own each workflow. |
| Stakeholder roles | Agriculture -> Setup -> Stakeholder Roles | Understand farmer, funder, supervisor, worker, buyer, supplier, manager, and group-leader roles. Actual party records remain in Parties. |
| Worker groups | Agriculture -> Setup -> Worker Groups | Guidance and entry points for worker-group setup and attendance flows. |
| Devices and checkpoints | Agriculture -> Setup -> Devices & Checkpoints | Guidance for field devices, checkpoint controls, telemetry summaries, and exception review. |
| Market feeds | Agriculture -> Setup -> Market Feeds | Guidance for commodity markets, approved price snapshots, and formula pricing. |
| Command center | Agriculture -> Operations -> Command Center | Operational launch point for field work, evidence, offline, telemetry, market, stock, payment, and reporting flows. |
| Field operations | Agriculture -> Operations -> Field Operations | Contextual entry point for field activities, work reports, attendance, and evidence documents. |
| Project fund control | Projects & WBS -> Operations -> Fund Control | Funding sources, fund receipts, obligations, cross-funding requests, settlements, and fund reports. |
| Payment batches | Payments -> Operations -> Payment Batches | Controlled payout execution for approved obligations and settlements. |
| Reports | Reporting -> Run Reports | Project fund position, utilization, cross-funding exposure, agriculture market, telemetry, incident, and operational reports. |
Agriculture Pages Versus Shared Owners
| Page type | What users do there | What users should not expect there |
|---|---|---|
| Agriculture setup guidance | Review capability state, field expectations, roles, devices, market rules, and flow | Full CRUD ownership for stock items, inspection templates, report definitions, or GL |
| Agriculture source workflows | Capture agriculture-specific source records and operating evidence | A duplicate payment engine, duplicate project-fund engine, or duplicate reporting shell |
| Shared primitive workspaces | Execute the authoritative workflow and store the record of truth | Agriculture-specific duplication of the same record |
Product Story
A managed-farm tenant may receive money from a project owner or investor. The money can arrive by bank, cash, mobile money, cheque, or internal transfer. The tenant records the funding source and fund receipt against a project and WBS. Field managers then plan work for blocks or farms, supervisors capture work done, worker attendance, input use, attachments, GPS/time evidence, and notes. Where the farm is remote, the same evidence can be captured offline and synced later.
After review, approved work creates or supports a payment obligation. Finance selects approved obligations into a shared payment batch. The batch line inherits the payee, project, WBS, source document, funding source, cost category, amount, and narration. Duplicate source lines and over-remaining amounts are blocked by backend validation. After execution and provider confirmation, GL posts the payout against project due-to/due-from or the configured cash, bank, wallet, or clearing accounts. Reports show received funds, committed amounts, paid amounts, available balances, source documents, payment batches, and GL status.
The same service can also run produce intake. A farmer or group delivers produce, the intake team captures quantity and UOM, quality records grade the produce, accepted produce moves into stock, buyer sale or POS handles revenue, and settlement statements feed farmer payout batches.
Daily Operating Rhythm
- Confirm active capabilities and business day readiness.
- Maintain parties, roles, locations, items, stock, inspection templates, projects, WBS, and funding setup.
- Record funding agreements and fund receipts where the work is project-funded.
- Capture field activities, attendance, inspections, input issues, harvest or produce intake, and supporting evidence.
- Review and approve source records before they can create stock, payment, settlement, billing, or GL impact.
- Generate or create obligations from approved work, attendance, spending, settlement, or supplier records.
- Batch approved obligations through Payments.
- Execute payouts and post GL.
- Review project fund position, utilization, operational exceptions, market snapshots, telemetry summaries, and drilldowns.
Day-To-Day By Role
| Role | Starts in | Usually finishes work in |
|---|---|---|
| Operations manager | Agriculture -> Operations -> Command Center | Agriculture source workflows, Projects & WBS, and Reporting |
| Supervisor or field lead | Agriculture field workflows | Agriculture source workflows and shared Document/Inspection evidence owners |
| Store or intake officer | Agriculture produce flow guidance | Inventory and Inspections |
| Finance officer | Projects & WBS -> Fund Control | Payments, GL, and Reporting |
| Executive or fund owner | Agriculture overview pages or report actions | Reporting drilldowns and Projects & WBS fund-control views |