Managed Coffee Portfolio Recording Script

This script is for recording a live Agriculture demo on the stat-solutions-network tenant. The story is a project-funded coffee plantation operator that receives money from different parties, manages farms on their behalf, records field work, pays workers or suppliers, and proves every movement through projects, payments, reports, and GL.

Use this script for screenshots, a short product video, or one continuous walkthrough. Do not narrate the demo as a named-company case study. Present it as a realistic managed coffee plantation operating model.

Opening Statement

Use this as the first voice-over:

“Pinkapple Agriculture is not a separate accounting system. It is an agriculture operating layer built on the same ERP primitives: Parties, Farms, Projects and WBS, Document Transactions, Events, Payments, Inventory, Inspections, Reporting, and GL. Agriculture captures the farm-specific operating story, while shared primitives keep money, stock, approvals, and accounting disciplined across the whole tenant.”

Then continue:

“In this demo, the tenant is a coffee plantation operator managing multiple farms for different funding parties. Each farm is treated as a project, so every fund receipt, field activity, worker attendance sheet, payment obligation, payout batch, and GL posting can be traced back to the project and funding source.”

Capability Story For This Demo

Frame the demo around these Agriculture capabilities:

Capability	What To Say
Basic Farm Operations	“Farms are agriculture business entities. They can link to locations, projects, and partitions, but they are not just generic locations.”
Field Operations	“Work orders, field activities, activity reports, and worker attendance capture what happened on the ground.”
Worker Groups	“Worker crews are managed through shared Parties and group membership roles. Attendance evidence can become payable obligations.”
Project Fund Control	“Funding source, actual receipts, approved spending, cross-funding, settlement, and fund reports are managed through Projects and WBS.”
Produce And Commercial Flow	“The same portfolio can continue from harvest and delivery into buyer sale, dispatch, settlement statement, billing, or payment.”
Accounting Discipline	“Fund receipts, payouts, settlements, and financial consequences post through the shared accounting core.”

Optional capability mention:

“The same service model can later enable offline field capture, IoT checkpoints and telemetry, and market price intelligence without changing the core project-funded operating model.”

Live Demo Data

Use these live rows for the recording.

Projects And Farms

• Projects: PRJ-000007 through PRJ-000021
• Farms: FAR-000001 through FAR-000015

Funding And Receipts

• Funding agreements: JFA-01 through JFA-15
• First farm receipts: JFR-01-01, JFR-01-02
• Second payout source receipts: JFR-06-02 through JFR-10-02

Field Work And Obligations

• Work order: JWO-01
• Field activity report: JAR-01
• Worker attendance: JAW-01
• Payment obligation: JOBL-01
• Second payout source attendance: JAW-06 through JAW-10
• Second payout source obligations: JOBL-06 through JOBL-10

Payments And GL

• Payment batch: JPB-20260820-01
• Payment batch: JPB-20260820-02
• JPB-20260820-02 is fully executed and posted to GL.
• GL journal batch number for JPB-20260820-02: BATCH-202608000276
• GL batch id for that payout: 2706
• Direct-worker payment batch: SMOKE-PB-DIRECT-22180210031035
• Direct-worker attendance: JAW-DIRECT-22180210031035
• Direct-worker obligations: JOBL-DIR-1-180210031035, JOBL-DIR-2-180210031035, JOBL-DIR-3-180210031035
• Direct-worker payment transactions: 143, 144, 145
• Direct-worker GL journal batch: BATCH-202608000296
• Direct-worker GL batch id: 2736

Produce And Commercial Flow

• Producer contract: JPC-01
• Harvest or intake record: JHR-01
• Produce delivery note: JPD-01
• Buyer sale order: JBS-01
• Dispatch note: JDN-01
• Settlement statement: JSS-01

Cross-Funding

• Open exposure: JCF-01
• Settled request: JCF-02
• Settlement document: JCS-01

Full Recording Path

1. General Dashboard

Open the general dashboard and set the business unit filter to STAT SOLUTIONS NANSANA.

Show:

• Agriculture head office card
• executive stats
• operational lane cards
• funding, obligations, and contracts trail
• produce and commercial trail

Narration:

“This is the head office view for agriculture operations. It combines field execution, document approval, funding control, and commercial flow into one snapshot. The dashboard is not the accounting source of truth; it is an operational control view fed by the shared ERP records.”

2. Project-Funded Farm Structure

Open Projects & WBS and show the project list.

Show:

• PRJ-000007 through PRJ-000021
• one project detail, preferably PRJ-000007

Narration:

“Each coffee farm is represented as a project. That gives the operator a controlled place to manage budget, WBS, funding, obligations, payouts, and reports per farm. This is what keeps money from different funders traceable.”

3. Farm Identity

Open Agriculture -> Setup -> Farms.

Show:

• FAR-000001 through FAR-000015
• one farm detail with linked project context
• one farm partition if visible

Narration:

“Farm is now an agriculture entity. It can link to a physical operational location, but it carries agriculture meaning: farm identity, project link, partitions, acreage context, crop context, and future field-specific operating controls.”

4. Funding Source And Actual Receipt

Open Projects & WBS -> Operations -> Fund Control.

Show these tabs:

1. Funding Sources
2. Fund Receipts
3. Payment Obligations

Best rows:

• Funding source: JFA-01
• Fund receipts: JFR-01-01, JFR-01-02
• Obligation: JOBL-01

Narration:

“A funding source is the approved commitment or agreement. A fund receipt is money actually received. Those are intentionally separate, because a funder may commit money before depositing it, or deposit in installments. Approved field work then becomes a payment obligation against the project and funding source.”

5. Field Evidence

Open Agriculture -> Operations -> Field Operations.

Show:

• work order JWO-01
• activity report JAR-01
• attendance sheet JAW-01

Narration:

“Field Operations is where the farm work story is captured. A supervisor or field team can record what was planned, what happened, who participated, and the supporting evidence. Once approved, this evidence can drive obligations and later payout.”

6. Worker Group Payment

Open Payments -> Bulk Payments.

Show:

• JPB-20260820-01
• JPB-20260820-02

Open JPB-20260820-02.

Highlight:

• status is successful
• five lines are successful
• source obligations are JOBL-06 through JOBL-10
• the batch is posted to GL

Narration:

“Worker or group-leader payouts do not happen in a separate agriculture ledger. The approved agriculture evidence creates obligations, and shared Payments executes the payout. This batch is a real cash payout batch with successful lines and GL posting.”

Optional direct-worker proof:

Open SMOKE-PB-DIRECT-22180210031035.

Highlight:

• status is successful
• three lines are successful
• payees are Amina Nalubega, Samuel Kato, and Grace Nansubuga
• source obligations are JOBL-DIR-1-180210031035, JOBL-DIR-2-180210031035, and JOBL-DIR-3-180210031035
• source attendance is JAW-DIRECT-22180210031035
• payment transactions are 143, 144, and 145
• GL batch is BATCH-202608000296

Narration:

“The same worker-group attendance model can also pay individual workers directly. The attendance document keeps the worker group, leader role, supervisor role, project, WBS, and funding source. The payment batch then pays each worker as a separate settled transaction and posts the total to GL.”

7. GL Proof

Open the GL journal batch workspace.

Search for:

• BATCH-202608000276
• or source reference PAYMENT-BATCH-44
• for direct-worker payout, search BATCH-202608000296 or source reference PAYMENT-BATCH-45

Show:

• posted batch status
• source type PAYMENT
• source id PAYMENT-BATCH-44
• for the direct-worker proof, source id PAYMENT-BATCH-45

Narration:

“The agriculture operation reaches the accounting core. The payout is posted through GL, so management can move from farm evidence to payment execution to financial statements without losing traceability.”

8. Project Reports

Open Reporting and run:

1. PROJECT_FUND_POSITION
2. PROJECT_FUND_UTILIZATION
3. PROJECT_CROSS_FUNDING_EXPOSURE

Recommended project:

• PRJ-000007

Show:

• PROJECT_FUND_POSITION with JFA-01, JFR-01-01, JFR-01-02
• PROJECT_FUND_UTILIZATION with obligation and payment usage
• PROJECT_CROSS_FUNDING_EXPOSURE with JCF-01, JCF-02, and JCS-01

Narration:

“Reports are run from the shared Reporting module. Agriculture contributes the operating context, but the fund position, utilization, and cross-funding exposure are project-level controls that can work across services.”

9. Cross-Funding

Open Projects & WBS -> Operations -> Fund Control -> Cross-Funding Requests and Cross-Funding Settlements.

Show:

• JCF-01 as an open exposure
• JCF-02 as a settled request
• JCS-01 as the settlement document

Narration:

“Cross-funding handles the real-world case where one project or fund temporarily supports another. The system records the request, exposes the due-to and due-from position, and then closes it through settlement.”

10. Produce And Commercial Continuity

Open Agriculture -> Operations and show the Produce and Commercial pages or tabs.

Show:

• JPC-01
• JHR-01
• JPD-01
• JBS-01
• JDN-01
• JSS-01

Narration:

“The same farm portfolio can move from field execution into harvest, delivery, buyer sale, dispatch, and settlement. Pinkapple keeps those as source documents that can hand off into Inventory, Billing, POS, Payments, and GL where needed.”

Short 3-5 Minute Version

Use this order if time is limited:

1. Agriculture dashboard
2. Project PRJ-000007
3. Farm FAR-000001
4. Funding source JFA-01
5. Fund receipts JFR-01-01 and JFR-01-02
6. Payment obligation JOBL-01
7. Payment batch JPB-20260820-02
8. GL batch BATCH-202608000276
9. Optional direct-worker split batch SMOKE-PB-DIRECT-22180210031035
10. Optional direct-worker GL batch BATCH-202608000296
11. Cross-funding report with JCF-01, JCF-02, JCS-01

Screenshot Checklist

• Agriculture dashboard with head office cards
• Projects list with the coffee farm projects
• Project detail for PRJ-000007
• Farms list and farm detail
• Funding source detail
• Fund receipt detail
• Payment obligation detail
• Field operation evidence
• Bulk payment batch detail for JPB-20260820-02
• GL batch detail for BATCH-202608000276
• Optional direct-worker payment batch detail for SMOKE-PB-DIRECT-22180210031035
• Optional direct-worker GL batch detail for BATCH-202608000296
• Project fund position report
• Project cross-funding exposure report
• Produce and commercial document rows

Language To Avoid

• Do not call this a named-customer implementation.
• Do not imply Agriculture owns Payments, Reporting, Inventory, Billing, or GL.
• Do not describe farms as only operational locations.
• Do not describe fund receipts as plain reference documents; they are financial source records that should reconcile into accounting.

Closing Statement

Use this as the final voice-over:

“The important point is traceability. A funded coffee farm starts as a project, receives money from a funding party, records field evidence, creates approved obligations, pays workers or suppliers, posts to GL, and reports fund position and exposure from the same ERP foundation.”