Pennsylvania
Every six months
Semiannual tonnage reporting with a per-ton fee, minimums, and a late-penalty framework.
PA Department of Agriculture ↗Fertilizer tonnage reporting
Turn one sales export into state-ready fertilizer tonnage reports.
TonnagePilot transforms fertilizer sales data into reviewed, state-ready reports that surface exceptions, apply the right rules, and preserve the proof.
Customer-approved/Source-linked rules/No government-fee custody
LIVE PRODUCT TOUR
Pennsylvania — Jul–Dec 2026Draft
sales_export.xlsx4,281 rows · 12 columns mapped
ImportNormalizeResolveCalculateReview
Start the guided filing tourGuided product tour
Let the product explain the product.
One filing canvas, five short steps. Each step advances the actual review packet — the rows, totals, and status change, never just the caption.
Pennsylvania — H2 2026Review packet
Draft — importingProductTonsStatus
12-4-8 Turf Blend97,544 LBRecognized
Liquid Calcium Plus8,364 GALRecognized
BioRoot X1003,136 LBRecognized
Wholesale resale4,600 LBRecognized
Reported total—
Did you know?
40+ different fertilizer reporting formats are documented across the industry.
The expensive part is not remembering a due date. It is rebuilding the transformation between sales data and each state's categories, units, fees, and delivery rules.
Source: FertTon — Paperless Fertilizer Tonnage Reporting ↗THE RULE CHANGES BY STATE — TWO VERIFIED EXAMPLES
Michigan
Excel or revise
The annual report is submitted in the official Excel format; other file types are returned for resubmission.
Michigan MDARD ↗ProductMappingStatus
12-4-8 Turf BlendUFTRS 623Reused
Liquid Calcium PlusUFTRS 773Reused
BioRoot X100UnmappedReview
Outcome
Get your time back.
Don't rebuild the same mappings every reporting cycle. TonnagePilot remembers what your team confirmed, reuses it on the next import, and brings only new exceptions forward.
Every confirmed SKU, counterparty, destination, and state category makes the next filing more review-driven and less spreadsheet-driven.
PRODUCT PROMISEBring forward the known. Surface only the new.
How it works
From export to proof.
One operational verb per step. One visible result.
Import
Start with the CSV or XLSX export you already have.
Normalize
Convert units, dates, destinations, products, and reversals.
Resolve
Confirm only unmapped products, licenses, and exemptions.
Calculate
Apply deterministic, versioned state rules and fees.
Approve
Authorize one exact, immutable filing version.
Prove
Submit through your own state channel and archive the receipt.
Example filing · demo data
Count the work — not fake traction.
No invented customers or volume claims. These counters animate one clearly labeled example filing — the same packet from the tour above.
0Source rows imported
0.0Tons normalized
0Exceptions surfaced
0Approved filing version
Demo numbers describe the example filing above. They will only ever be replaced by verified, permissioned product totals.
Control
Software does the heavy lifting. Your team keeps control.
Responsibility stays explicit: TonnagePilot prepares and organizes the work; your team reviews and approves the exact output.
Source-linked
Every total can be traced back to the source rows and the rule version that produced it.
No guessing
Unknown mappings remain visible and block the filing until your team confirms them.
Exact approval
Approval binds to one immutable payload. Later changes require a linked correction.
Proof retained
Downloaded, customer-submitted, receipt-recorded, rejected, and superseded stay distinct.
Bring one prior filing
See what the workflow catches.
Request a $500 shadow filing. We confirm fit first — state coverage, data format, and reporting frequency. No sensitive filing data through this form: qualification first, secure upload later.