TTB Readiness for Breweries and Distilleries

TTB regulates anyone who manufactures, bottles, or wholesales alcohol beverages in the U.S. — breweries (27 CFR 25), distilled spirits plants or DSPs (27 CFR 19), wineries (27 CFR 24, covered separately), and importers. TTB's mission is revenue: federal excise tax on beer, spirits and wine. An auditor doesn't care whether your beer is good — they care whether the gallons you produced, removed, lost to evaporation, returned, or destroyed reconcile down to the proof gallon. The second mission is labeling integrity (COLA — Certificate of Label Approval) and formula approval for anything beyond a standard product. Most TTB findings come down to three things: incomplete daily records, late or wrong monthly/quarterly reports, and labels or formulas in use that don't match what was approved.

Breweries owe TTB daily records of beer produced, on hand, removed taxpaid, removed without tax (export, research, destruction), returned, and losses (27 CFR 25.291–25.301). DSPs owe similar records keyed to proof gallons: production gauge, storage account, processing account, transfers in bond, and tax determination. In both cases the auditor will ask to walk from a single grain receipt to the finished, taxpaid case — and every step in between must be on a dated, signed record. Paper-based producers usually fail not because the data isn't there, but because reconciling fermenter logs, distillation runs, barrel inventory and bottling reports across three filing cabinets takes days while the auditor waits.

Breweries file the Brewer's Report of Operations (TTB Form 5130.9, BROP) monthly or quarterly depending on tax liability. DSPs file monthly reports of production (5110.40), storage (5110.11), and processing (5110.28), plus the excise tax return (5000.24) on a semi-monthly schedule for most producers. Every line on every report must tie back to the daily records. Producers that build the reports manually at month-end typically have a 5–15% reconciliation gap they have to chase before they can file — that gap is what auditors look for. The fix is to make the report a view onto live data rather than an end-of-month exercise.

Any beer that isn't a 'standard' beer (anything brewed with non-traditional ingredients — fruit, spices, lactose, coffee, adjuncts beyond malted barley + hops + water + yeast) needs a formula on file with TTB before it ships. Distilled products generally need both a formula (for flavored, blended, or specialty products) and a COLA for the label. Operators get into trouble when the production formula drifts from the approved one — a recipe gets tweaked at brew day, the lab logs the change, but the formula on file at TTB still says the original. At inspection, the difference is a finding. The same problem shows up when a label is reprinted with a small change (alcohol by volume, net contents, government warning) and the new label is in use before a new COLA is approved.

TTB expects you to measure and explain every gallon. Losses (evaporation, leaks, spills, in-process) and gains (rare, usually a measurement reconciliation) must be recorded at the time they occur, with a reason and a signature. Destructions — dumped beer, off-spec spirits, returned product — must be witnessed and documented before TTB will allow you to claim back tax. Distilleries owe accurate proof gauging at every transfer using ATF/TTB-approved hydrometers or proof meters, with the gauge record signed and retained. A common audit failure is 'unexplained variance' — the proof-gallon balance doesn't close, and the producer can't show where the missing volume went. TTB will assess tax on the gap.

Most brewery and distillery software in market is good at one of: brewing scheduling, inventory, or accounting — but the TTB compliance piece is bolted on as a CSV export the brewmaster has to massage every month. Real TTB readiness needs four things together: (1) production execution that signs every step at the time it happens, (2) lot/barrel/case traceability from grain or molasses through to the taxpaid removal, (3) formula and COLA management linked to the recipe-of-record, and (4) report generation directly from the signed data, not a separate ledger. Ask any vendor to walk a TTB auditor through one real batch in their demo — most can't.