Agriculture Operations

Agriculture operations cover the daily work of running farms, projects, field teams, produce flows, livestock or poultry activities, market-linked pricing, payment obligations, and fund reporting. The module gives agriculture context and agriculture-owned source workflows while shared primitives execute the operational and accounting work.

Open Agriculture -> Operations for command-center guidance and agriculture entry points. Use Projects & WBS, Document Transactions, Inventory, Inspections, Payments, POS, Billing, Reporting, and GL for the owning workflows.

How To Read The Operations Area

Agriculture operations pages are orchestration surfaces. They help the user understand what to do next and where the record of truth lives.

• Use Agriculture pages for command-center guidance and agriculture-specific source workflows.
• Use Projects & WBS for funding control and cross-funding.
• Use Payments for execution and payout lifecycle.
• Use Inventory and Inspections for stock and quality truth.
• Use Reporting for report execution, export, snapshots, presets, schedules, and drilldowns.

In practice:

• stay in Agriculture when the business act is agriculture-native, such as a producer contract, produce delivery, settlement statement, field activity report, or worker attendance source record
• move to the shared primitive when you need the system of record for stock, inspection, funding, payment, reporting, or GL

Day-To-Day Product Story

A typical managed-farm day looks like this:

1. The operations manager reviews the command center and active projects.
2. A supervisor or field officer records field work, attendance, input use, inspection notes, or produce intake.
3. Evidence is attached: photos, GPS, timestamps, attendance sheets, device/checkpoint references, notes, signatures, or inspection results.
4. The supervisor reviews and approves the source record.
5. Approved source work creates or supports a payment obligation where money must be paid.
6. Finance selects approved obligations into a shared payment batch.
7. Payment lines inherit the project, WBS, fund source, cost category, source document, payee, and amount.
8. The batch is validated, approved, executed, and posted to GL.
9. Project fund reports show received funds, committed amount, paid amount, GL-posted amount, and available balance.
10. Exceptions are reviewed through reports and drilldowns.

Operational Lanes

Lane	Main user action	Owning primitive
Command center	See active guidance, exceptions, capability status, and next actions.	Agriculture workspace and Reporting
Field operations	Record field activities, work completion, attendance, input issue, supervisor checks, and evidence.	Events and Document Transactions
Project fund control	Register funding sources, fund receipts, obligations, cross-funding, and settlements.	Projects & WBS and Document Transactions
Payments	Pay approved obligations, settlements, workers, group leaders, suppliers, or farmers.	Payments
Stock and produce	Receive, issue, transfer, inspect, sell, or dispatch inputs and produce.	Inventory, Inspections, POS, Billing
Offline work	Download work packs, capture field data offline, sync, review, approve, or reject rows.	Documents, Events, Files, Reporting
Telemetry and incidents	Review device summaries, stale devices, battery/status exceptions, and incidents.	Resources, Events, Reporting
Market intelligence	Approve market snapshots and apply formula pricing or settlement references.	Pricing, Documents, Reporting

Quick Routing By Question

If the user asks...	Primary module to open first
Where do I record field work or attendance?	Agriculture source workflow built on Events/Documents
Where do I confirm stock after produce acceptance?	Inventory
Where do I record grading or inspection evidence?	Inspections
Where do I register funder/project/WBS/budget?	Projects & WBS
Where do I execute the payout?	Payments
Where do I verify fund position or cross-funding?	Reporting or Projects & WBS Fund Control
Where do I confirm accounting impact?	Reporting and GL/Accounting

Who Works Where During The Day

User role	Main page they open first	Main owner module they rely on later
Operations manager	Agriculture -> Operations -> Command Center	Projects & WBS, Reporting, and agriculture source workflows
Field supervisor	Agriculture source workflows such as activity or attendance records	Document Transactions, Events, and Inspections
Worker-group reviewer	Agriculture attendance or spending source workflows	Payments and Reporting after approval
Storekeeper or intake officer	Agriculture produce-delivery or intake workflow	Inventory and Inspections
Finance officer	Projects & WBS -> Fund Control	Payments, GL, and Reporting
Management or investor	Reporting links or approved report actions	Reporting and Projects & WBS

Project-Funded Work Flow

Use this flow when an investor, client, group, donor, grant, organization, or internal restricted fund is paying for work.

1. Open Projects & WBS -> Operations -> Project Control and confirm the project, WBS, owner/funder, and budget.
2. Open Projects & WBS -> Operations -> Fund Control.
3. Create and approve a funding source.
4. Create and approve the fund receipt when money is actually received.
5. Record the agriculture source document, such as a field activity report, worker attendance sheet, farm input issue, produce delivery, or spending request.
6. Approve the source document after evidence review.
7. Create or generate a payment obligation from the approved source.
8. Add selected approved obligations to a payment batch.
9. Execute and post GL.
10. Run Project Fund Position and Project Fund Utilization reports.

Expected accounting pattern for project cash funding:

Event	Debit	Credit
Project fund receipt	Cash, bank, wallet, or settlement account	Project due-to or restricted project liability
Project-funded payout	Project due-to or payable/clearing account	Cash, bank, wallet, or payment clearing

The exact accounts come from GL posting rules and system tags, not from the payment instrument alone.

Funding source and fund receipt are intentionally separate:

Record	Business meaning
Funding source	Approved agreement, commitment, grant, client instruction, restricted-fund authority, or contract.
Fund receipt	Money actually received and available to finance work, subject to accounting and fund rules.

The project owner/funder is the default commercial party for the project. A funding source can repeat that party as the document counterparty for audit, or use a different counterparty where the agreement is with another donor, group, organization, or internal fund holder.

Agriculture does not keep a second fund register. Once the fund source, fund receipt, obligation, cross-funding, or settlement needs approval, reporting, or accounting consequence, the user is already in the shared Projects & WBS / Reporting / GL path.

Field Activity And Attendance

Field activity records the work done on farms, fields, blocks, animal units, poultry houses, or processing areas.

Common agriculture source records include:

• field activity report
• worker attendance sheet
• farm input issue
• supervisor inspection
• treatment or animal health event
• feeding event
• harvest record
• produce intake record
• spending request

Important fields:

Field	Meaning
Project	Farm, investor project, season, block, grant program, or managed plantation being charged.
WBS/work package	Task, block, operation, animal unit, flock, cost bucket, or field activity under the project.
Counterparty/payee	Worker, group leader, supplier, contractor, transporter, farmer, or other party linked to the work.
Activity or document type	Defines the operational meaning and validation rules.
Cost category	Labour, inputs, transport, supervision, veterinary, feed, processing, inspection, or other spend class.
Amount or quantity	Work value, payable amount, input quantity, produce quantity, or settlement amount.
Evidence	Attachments, GPS, timestamp, notes, signatures, attendance details, inspection result, or device reference.
Funding source	Approved funding document or receipt used to authorize payment.

Approved source records should not automatically create financial impact unless the configured workflow allows it. They should first pass review and then create an obligation or stock/inspection/billing consequence.

That means:

• the agriculture source record explains what happened in the field
• the shared primitive records the downstream truth, such as stock, inspection outcome, payable, report fact, or GL impact

What Agriculture Does Not Own Here

Agriculture may provide the source context, but it does not own these runtime consequences:

• project fund-position accounting
• payment execution
• report execution
• stock balance truth
• inspection record truth
• GL posting truth

Those stay in their shared primitives even when the business story is agriculture-specific.

Agriculture owns the business narrative and source evidence. Shared primitives own the ledgers and reusable runtime.

Payment Obligations And Batches

Payment obligations are controlled payable requests. They should be created from approved source records where possible.

Before adding an obligation to a batch, confirm:

• source document is approved
• payee is correct
• payment channel is allowed
• amount is within remaining source amount
• project and WBS are present where required
• funding source has available funds
• budget has remaining amount where active
• payment instrument is verified where required

The backend rejects:

• duplicate source obligation in an active batch
• duplicate source obligation in the same batch
• amount above remaining source amount
• amount above available project funding
• amount above remaining WBS/budget
• invalid or unapproved source document

Fund Reports And Drilldowns

Run fund reports from Reporting -> Run Reports or from the Fund Control report action.

Key reports:

Report	Purpose
Project Fund Position	Shows funding documents, received amount, committed amount, paid amount, GL-posted paid amount, pending amount, available amount, project budget, and fund status.
Project Fund Utilization	Shows payment-batch utilization by source obligation, payee, project, WBS, funding document, status, provider reference, and GL posting state.
Project Cross-Funding Exposure	Shows temporary funding from one project/fund to another and settlement status.
Agriculture Market Price Snapshots	Shows approved or pending commodity price snapshots and pricing references.
Agriculture Telemetry Summary	Shows device/checkpoint summaries, stale-device status, battery/status exceptions, and review readiness.
Agriculture Incident Review	Shows operational incidents linked to evidence, telemetry, field activities, or inspections.

Report drilldowns should open in-place dialogs and preserve report context. They should not silently route users away from the report page.

Agriculture may seed report entry points or explain which report to run, but report execution, filters, snapshots, exports, schedules, and drilldowns remain owned by Reporting.

Produce Intake And Sale Flow

Produce aggregation and cooperative operations follow this pattern:

1. Confirm producer, supplier, group, or cooperative party.
2. Record produce delivery or harvest intake.
3. Capture quantity, UOM, location, lot/batch, and source reference.
4. Record grading or quality inspection.
5. Accept, reject, downgrade, or adjust quantity.
6. Move accepted produce into inventory if stock-managed.
7. Sell through buyer sale, dispatch, billing, or POS.
8. Prepare settlement.
9. Pay farmer, supplier, transporter, agent, or group through payment batches.

For a detailed produce example, see Produce Intake To Farmer Payout.

Livestock And Poultry Operations

Livestock and poultry use the same primitives, but the source records are different.

Typical records:

• animal or flock registration
• feeding record
• vaccination or treatment event
• mortality record
• weight or production measurement
• movement between pens, sheds, blocks, or locations
• inspection or health check
• stock issue for feed, medicine, or supplies
• sale, disposal, or transfer document

Where payments are needed, approved work or supplier records should flow into payment obligations and batches.

Offline Operations

Offline work is for remote farms where users capture data before the device reconnects.

Expected flow:

1. Prepare a work pack for user, device, location, project, WBS, expiry, and evidence policy.
2. Download the pack to the device.
3. Capture activities, attendance, input use, attachments, GPS/time, and idempotency keys.
4. Sync the batch when online.
5. Review duplicates, conflicts, and evidence upload status.
6. Approve valid rows and reject invalid rows.
7. Allow only approved rows to create downstream work records, obligations, stock, or report facts.

Rejected rows must remain auditable and must not create payment, stock, billing, or GL impact.

Telemetry And Incident Review

Telemetry is not treated as raw accounting truth. The ERP stores summaries and exceptions.

Examples:

• stale tracker
• low battery device
• missed checkpoint
• unexpected location movement
• sensor exception
• camera incident reference
• gate or weighbridge variance
• vehicle or equipment exception

Operational users review the exception, attach or link evidence, and either close, escalate, or connect it to a field activity, inspection, or incident report.

Market Intelligence

Market prices can support coffee, cotton, maize, tea, livestock, dairy, export produce, and other commodity operations.

A market snapshot should capture:

• commodity
• grade
• market/provider
• quote date and time
• currency
• UOM
• confidence/source metadata
• conversion inputs
• premium or discount
• approval state

Pricing, settlements, buyer sales, or contracts should retain the market snapshot and formula inputs used. Overrides need a reason and approver.

Troubleshooting

Issue	What to check
Fund report is empty	Project, date range, business unit, document type tag, approval status, and whether funding documents are approved.
I cannot find the stock or QC result in Agriculture	Check Inventory or Inspections; Agriculture is not the owning ledger for those consequences.
Payment line cannot be added	Duplicate source, source remaining amount, funding available amount, budget remaining amount, source approval, or payment channel.
GL posting fails	Business day, fiscal period, user BU access, posting channel, cash/bank/wallet balance, GL tags, and posting rule bindings.
Payee is wrong	Source document counterparty, party lookup, payment obligation payee, and payment instrument.
Offline sync does not create impact	Sync review approval, duplicate/conflict status, evidence upload, and idempotency result.
Telemetry does not show in reports	Device assignment, summary ingestion, exception rule, date range, and report filters.
Market price not available	Snapshot approval, commodity/grade/UOM/currency match, date range, and formula policy.

Related Guides

• Agriculture Overview
• Agriculture Setup
• Agriculture MVP Smoke Test
• Agriculture Full Strategic Acceptance
• Produce Intake To Farmer Payout
• Document Transaction Operations
• Payment Batches