Reports
The report already exists. Because the data already does.
Operational, financial and compliance report packs — plus a QuickBooks-ready COGS journal export.
On most farms, a report is a person. Somebody exports three spreadsheets, joins them by hand, and produces the number the board asked for — then does it again next month, slightly differently, and nobody can reconcile the two.
Because the schedule, the sensors, the harvest weights, the labor hours, the energy meters and the ledger are one system, a report is a query rather than a project. The packs answer the three questions that actually get asked: what did the farm do, what did it earn, and can we prove it.
And the one that matters at month end: the COGS journal, formatted for QuickBooks. If your books live somewhere else, leave them there. The cost of a pound still comes out of operational reality instead of being re-keyed into a spreadsheet by somebody who was not on the floor.
Questions
The things people actually ask.
Are these canned reports, or a report builder?
Canned packs, covering the operational, financial and compliance questions farms genuinely ask. That is a deliberate choice. A blank report builder is what gets shipped when a vendor does not know what its customers need.
Why QuickBooks specifically?
Because that is where farms of this size actually keep their books. The COGS journal exports in a format QuickBooks will take, so you get an operationally-derived cost of goods without moving your accounting anywhere.
Do we have to use the platform ledger to get financial reports?
No. Digital Cultivation has a real double-entry general ledger if you want one. If you do not, the COGS journal export gives your existing books the number they were missing.
See Reports on a real farm.
We'll walk an order all the way through to its margin — on live farm data, not a slide.