Agriculture Setup

Agriculture setup prepares the tenant to operate farms, projects, worker groups, produce, livestock, poultry, offline teams, telemetry devices, market references, and project-funded spending. It must be configured around the shared primitives that own the actual records.

Agriculture setup is not a second master-data tree. It is a readiness layer that explains which shared owner module must hold the real location, party, stock, inspection, project, payment, report, or GL configuration.

Open Agriculture -> Setup for agriculture guidance and contextual entry points. Open Platform Admin -> Companies -> Manage Services to activate or deactivate Agriculture capabilities for a tenant.

How To Use Agriculture Setup

Use the Agriculture setup pages to understand readiness, not to replace the owner modules.

• The Agriculture setup pages explain what must exist before users can operate safely.
• They may deep-link to a small number of canonical workspaces.
• They should not become alternate maintenance screens for Locations, Inventory, Inspections, Projects & WBS, Payments, Reporting, or GL.
• If a setup page mentions a shared primitive, that primitive owns the actual record.

Think of Agriculture setup as a launch checklist:

• read the capability or operating-model guidance in Agriculture
• open the owning primitive to create or maintain the real record
• return to Agriculture only when the source workflow needs agriculture context

Setup Principles

• Agriculture capabilities are managed by platform administration, not by tenant workspaces.
• Agriculture setup pages should not duplicate Inventory, QC, Projects & WBS, Payments, Billing, Reporting, or GL management screens.
• Use party lookups for owners, funders, farmers, groups, suppliers, workers, buyers, supervisors, and managers.
• Use project and WBS references when work is funded, restricted, grant-backed, investor-backed, or must be reported by farm/block/season.
• Use document types and system tags to control source documents, obligations, settlements, and report behavior.
• Use verified payment instruments and payment batches for payouts.

Capability Setup Reference

Capability	Main setup areas	Owning primitives
Basic Farm Operations	Farms, partitions, location bindings, operational items, parties, activity types	Farm registry guidance, Locations, Operational Items, Parties, Events
Field Operations	Activity types, work report document types, attendance sheets, approval rules	Events, Document Transactions, Projects & WBS
Worker Groups	Group leaders, worker lists, role capability, attendance evidence	Parties, Party Roles, Document Transactions, Payments
Project Fund Control	Project owner/funder, project/WBS, budgets, funding documents, GL tags	Projects & WBS, Document Transactions, GL, Reporting
Managed Plantation	Owner/funder party role, service contract, fee model, fund reporting	Parties, Projects & WBS, Billing, GL
Produce Aggregation	Produce items, UOM, grading templates, contracts, delivery documents	Inventory, Inspections, Document Transactions
Livestock	Animal or herd item identity, event types, treatment evidence, stock use	Operational Items, Events, Inventory, Inspections
Poultry	Flock identity, feed items, mortality events, production records	Operational Items, Events, Inventory, Inspections
POS Farm Sales	Stock items, pricing, registers, fulfillment, payment channels	POS, Inventory, Pricing, Payments
Offline Field Capture	Devices, users, work packs, sync rules, evidence requirements	Documents, Events, Files, Reporting
IoT And Telemetry	Devices, checkpoints, status rules, exception policies	Resources, Locations, Events, Reporting
Market Intelligence	Commodities, grade/UOM/currency policy, market providers, approval rules	Pricing, Documents, Reporting

Navigation Setup Map

Setup area	Open from	What to configure
Operating model	Agriculture -> Setup -> Operating Model	Read capability state, understand active presets, and see which primitive owns each workflow.
Farms	Agriculture -> Setup -> Farms	Review farm identity, partition hierarchy, project bindings, location bindings, and asset/resource usage before runtime execution.
Stakeholder roles	Agriculture -> Setup -> Stakeholder Roles	Review common agriculture roles such as project owner, funder, worker, group leader, supervisor, manager, supplier, buyer, and agent. Maintain actual roles in Parties.
Worker groups	Agriculture -> Setup -> Worker Groups	Review group-leader operating rules, attendance evidence policy, and payment handoff guidance. Maintain actual parties and groups in Parties.
Devices and checkpoints	Agriculture -> Setup -> Devices & Checkpoints	Review how devices/checkpoints should be represented and what telemetry exceptions should become reportable. Maintain the actual underlying records in shared primitives.
Market feeds	Agriculture -> Setup -> Market Feeds	Review commodity, market, provider, UOM, currency, grade, formula, and approval expectations before using shared pricing, documents, and reports.
Locations	Assets or Locations setup	Maintain physical/logistical places such as gates, warehouses, collection centers, stores, checkpoints, mapped sites, pens, or houses. Farm identity should bind here when needed, not collapse into it.
Operational items	Administration -> General Setup -> Operational Items	Maintain the shared item identity before stock, pricing, billing, POS, production, or agriculture uses the item.
Stock items	Inventory -> Setup	Maintain inputs, produce, packaging, feed, medicine, equipment consumables, and stock-managed outputs in the shared inventory master.
Inspection templates	Inspections -> Setup	Maintain grading, QC, field verification, livestock health, poultry, and evidence review templates in the shared inspection engine.
Project control	Projects & WBS -> Operations -> Project Control	Maintain projects, WBS, budgets, owners/funders, farms, blocks, seasons, and cost categories in the shared project primitive.
Fund control	Projects & WBS -> Operations -> Fund Control	Maintain funding sources, fund receipts, obligations, cross-funding requests, settlements, and fund reports in the shared project-funding primitive.

Primitive Ownership Reminder

When users say "Agriculture setup", split it into two layers:

• Agriculture-owned guidance: capability explanation, role guidance, worker-group operating rules, device/checkpoint rules, market-rule guidance
• Primitive-owned setup: locations, parties, stock items, inspection templates, project/WBS structure, funding documents, payment channels, report definitions, and GL tags

This distinction keeps one source of truth for every master record.

If a user asks:

• "Where do I create the farm or block?" use Agriculture -> Setup -> Farms for the model and shared owner primitives for the current physical bindings until Farm backend runtime is introduced.
• "Where do I create the produce or feed item?" use Inventory Setup.
• "Where do I define grading or QC checklists?" use Inspections Setup.
• "Where do I set up project owner/funder and budgets?" use Projects & WBS.
• "Where do I configure payment channels or instruments?" use Payments and the relevant shared setup.

User Concept And Field Reference

Field or concept	Meaning	Notes
Service capability	Feature preset enabled for the tenant, such as Worker Groups, Offline, Telemetry, or Market Intelligence.	Manage activation in Platform Admin. Tenant pages only show status and guidance.
Project	The funded or cost-tracked unit of work, such as farm, investor farm, estate block, grant program, season, campaign, or managed plantation.	Owned by Projects & WBS.
WBS or work package	The operational breakdown under a project, such as block, activity, task, animal unit, season task, or cost bucket.	Required where fund or budget control needs detailed traceability.
Project owner or funder	Party that owns, funds, sponsors, or restricts money for a project.	Use a real party lookup across applicable party types exposed by the Parties primitive. Auto-role assignment is backend-configuration dependent.
Counterparty	Party on a document, such as worker, group leader, supplier, farmer, buyer, investor, contractor, or transporter.	Use party lookup where available. Avoid typing names when a party record exists.
Funding source	Approved agreement or commitment authorizing spending for a project or WBS.	Usually a document transaction linked to the project and funder.
Fund receipt	Money actually received for a project.	Should reconcile to cash, bank, mobile money, wallet, cheque, or internal transfer accounting.
Document number	System-generated reference for a document transaction.	Users should leave it to backend numbering. Use External Reference for paper, bank, or contract references.
External reference	Human-entered outside reference for a real-world document or transaction.	Examples: contract number, bank slip, donor reference, field sheet number, supplier invoice.
Source document	Approved work, attendance, input issue, settlement, delivery, or other record that justifies an obligation.	Payment obligations should reference approved source documents.
Payment obligation	Approved payable request created from source evidence and fund context.	Payments can batch these obligations without manual re-entry.
Cost category	Agriculture or project cost bucket such as field labour, inputs, transport, supervision, processing, animal health, or feed.	Used for budgets, reports, and fund utilization.
Evidence	Attachments, GPS, timestamp, notes, photos, signatures, device references, or inspection results.	Evidence should remain attached to the source record.
Device or checkpoint	Field device, phone, scanner, camera, sensor, tracker, gate, block checkpoint, vehicle unit, or inspection point.	ERP stores summaries/exceptions and links to evidence, not high-frequency raw telemetry.
Market snapshot	Approved market price record for a commodity, grade, UOM, currency, provider, market, and timestamp.	Used only after approval. Settlements should retain snapshot and formula inputs.

Project-Funded Farm Setup

Use this setup when a tenant manages money for investors, clients, donors, organizations, groups, or internal restricted projects.

1. Create or confirm the funder or owner in Parties.
2. Create the project in Projects & WBS.
3. Select the project owner/funder using a party lookup.
4. Create WBS/work packages for farms, blocks, seasons, activities, or cost categories.
5. Create budget lines where spending control is required.
6. Create and approve the funding source document.
7. Create and approve fund receipt documents when money is received.
8. Confirm GL tags and posting rules for cash/bank/wallet, project due-to, project due-from, and payment clearing.
9. Confirm payment batch types and payment channels.
10. Confirm reports are available in the Reporting module.

Recommended Tenant Setup Sequence

1. Activate the Agriculture service and the needed capability packs in Platform Admin.
2. Confirm the business units, fiscal controls, and base accounting setup.
3. Prepare shared party data for owners, funders, workers, groups, suppliers, buyers, and managers.
4. Prepare shared locations, stock items, inspection templates, and operational items where applicable.
5. Create projects, WBS nodes, budgets, funding documents, and fund receipts where money is restricted.
6. Configure agriculture source-document types and event/document evidence rules.
7. Configure payment instruments, payment channels, and posting readiness.
8. Validate the required reports in Reporting before go-live.

Field Operations Setup

Prepare field work so approved records can later support stock, obligation, payment, or reporting actions.

• Define activity/event types such as weeding, pruning, spraying, manuring, harvesting, feeding, vaccination, treatment, mortality, transport, inspection, or supervision.
• Define required evidence such as photo, GPS, supervisor note, attendance sheet, worker count, input consumed, location, checkpoint, or attachment.
• Configure document types for field activity reports, worker attendance, input issues, spending requests, and completion evidence.
• Make project/WBS mandatory where the tenant controls spending by project or fund.
• Define approval responsibility before operational impact is allowed.

Worker Group Setup

Worker groups are useful when a group leader is paid on behalf of multiple workers or when attendance needs repeated analysis.

• Maintain workers, group leaders, supervisors, and managers as parties or users according to local policy.
• Assign appropriate party roles.
• Define attendance document types and evidence policy.
• Capture group member names or party references where the tenant needs repeated attendance analytics.
• Define whether payment is made to each worker or to the group leader.
• Ensure the payment obligation records who was paid and who the work relates to.

Produce And Stock Setup

Use shared Inventory and Inspections setup for produce, inputs, feed, medicine, packaging, and saleable outputs.

Important setup items:

• operational item
• stock item
• category
• UOM and conversion
• warehouse or collection center
• lot/batch policy
• inspection or grading template
• quality outcome policy
• valuation and costing treatment
• POS or buyer-sale pricing where applicable

For produce-specific intake, see Produce Intake To Farmer Payout.

Offline, Telemetry, And Market Setup

Area	Setup expectation
Offline	Define device/user assignment, work-pack scope, expiry, local capture fields, idempotency keys, sync review rules, evidence upload queue, and conflict handling.
Telemetry	Register the device/checkpoint/resource, define expected reporting interval, stale threshold, battery/status rules, incident categories, and evidence links.
Market intelligence	Define commodity, market, provider, quote time, grade, UOM, currency, conversion, confidence, formula pricing, premium/discount, and approval workflow.

Setup Checklist

• Agriculture service and required capabilities are active for the tenant.
• Tenant pages only show read-only capability state.
• Parties and party roles exist for funders, owners, farmers, workers, group leaders, suppliers, buyers, managers, and supervisors.
• Projects, WBS, and budgets exist where funding or cost control is required.
• Funding source and fund receipt document types are available.
• Source document types exist for field activity reports, attendance, input issues, and obligations.
• Payment channels, payment batch types, and instruments are configured.
• Cash, bank, wallet, project due-to, project due-from, clearing, and fee GL tags resolve to accounts.
• Locations, stock items, UOM, inspection templates, devices, and market references are ready for the active capabilities.

Common Mistakes

Mistake	Better practice
Activating capabilities from tenant Agriculture pages.	Use Platform Admin -> Companies -> Manage Services.
Creating agriculture-only duplicates of inventory, QC, payments, or reports.	Use shared primitives with agriculture context.
Treating Agriculture Setup as the owner of farms, produce items, or QC masters.	Use Agriculture for guidance, then create the real record in the owning primitive.
Typing project owner/funder names manually.	Use a party lookup and assign the Project Funder role.
Capturing field work without project/WBS when funds are restricted.	Require project and WBS context before approval.
Paying directly from an attendance sheet without an approved obligation.	Create or generate a payment obligation, then use payment batches.
Recording fund receipt documents without cash/bank/wallet accounting readiness.	Confirm GL posting rules and cash/bank source before payout.

Related Guides

• Agriculture Overview
• Agriculture Operations
• Agriculture MVP Smoke Test
• Operational Items
• Document Transactions
• Payment Batches