Use InnoVint's compliance tools to prepare a winery's TTB Report of Wine Premises Operations (Form 5120.17)
domain: innovint.us · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Keep harvest, bulk operation (crush, additions, transfers, blending), and packaging records current in InnoVint throughout the period, since the compliance report is generated from this underlying production data.
Determine your winery's filing frequency: monthly by default, or quarterly if on-hand wine never exceeds 60,000 gallons and you file quarterly excise tax returns, or annually if on-hand wine never exceeds 20,000 gallons and you file an annual excise tax return.
Use InnoVint's TTB Compliance module to generate the Report of Wine Premises Operations figures from recorded production data rather than manually re-aggregating from spreadsheets.
Reconcile InnoVint's generated report against physical inventory and any bulk wine received/shipped under bond before submitting, since discrepancies between recorded and physical inventory are a common audit flag.
Submit the finalized report through TTB's required channel (Pay.gov), noting InnoVint prepares the figures but the winery still files directly with TTB.
Known gotchas
Filing frequency (monthly/quarterly/annual) depends on gallons of wine on hand and excise tax filing status, not on winery size or revenue — confirm the actual on-hand-gallons threshold (60,000 for quarterly, 20,000 for annual) rather than assuming eligibility.
InnoVint generates the report figures from its own recorded production data; if any production activity (e.g., a bulk transfer from a custom-crush client) was recorded late or outside InnoVint, the generated report will be incomplete until that data is entered.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?