Agriculture MVP Smoke Test

This checklist validates the minimum Agriculture flow before running the full strategic acceptance pack.

Agriculture remains service-context only. Inventory, inspections, documents, projects, payments, billing, reports, and GL remain owned by their shared primitives.

Smoke Goal

Prove that approved agriculture work can create a controlled payment obligation, move into a payment batch, execute successfully, post GL, and reconcile through project/fund reports.

Pre-Checks

Area	Expected state
Service	Agriculture service is active for the tenant and user.
Permissions	Test user has Agriculture operations plus shared Project/WBS, Document Transaction, Payment, and Reporting permissions.
Project/WBS	Project, WBS, fund source, and cost category are configured.
Party roles	Worker, supplier, farmer, or contractor parties exist where needed.
Payment setup	Payment channel, instrument, and GL posting rules are ready.
Fiscal setup	Business unit has current fiscal period, business day, and currency readiness.

Core Flow

1. Create or identify an approved agriculture source record, such as field activity, work completion, attendance sheet, or spending request.
2. Confirm the source record carries project, WBS, fund source, payee, amount, and approval context.
3. Generate a payment obligation from the approved source.
4. Open the shared Payments batch workspace.
5. Add the approved obligation as a batch line.
6. Attempt a duplicate source line and confirm the system rejects it.
7. Attempt an over-remaining amount and confirm the system rejects it.
8. Validate, approve, and execute the payment batch.
9. Confirm provider success or settlement outcome.
10. Confirm payment GL posting and source traceability.
11. Run Project Fund Position and Project Fund Utilization reports.

Pass Criteria

The MVP passes when:

• Approved source work generates only valid payment obligations.
• Unapproved, duplicate, or over-remaining payment lines are blocked.
• Payment batch execution preserves project, WBS, fund, payee, source document, and amount.
• GL posting uses the shared Payment and Accounting primitives.
• Project fund reports reconcile received, committed, paid, GL-posted, and available values.
• No Agriculture page duplicates shared primitive ownership.

Common Failures

Failure	Check
Obligation cannot be created	Source approval, project/WBS, payee role, amount, and permission.
Batch line rejected	Remaining obligation amount, duplicate source line, batch status, and payment channel.
Payment execution fails	Provider config, wallet/channel setup, beneficiary instrument, and business day.
GL posting fails	Fiscal period, currency, payment GL rule, COA, subledger, and operating context.
Reports do not reconcile	Source document links, project/WBS/fund metadata, GL batch status, and report filters.

Related Guides

• Agriculture Full Strategic Acceptance
• Agriculture Operations
• Project Fund Control
• Payment Batches