Catering in One City, Serving in Another: Which Sales Tax Rate Goes on the Invoice

In most states, the sales tax rate on a catering invoice follows the event, where the food is served, not the kitchen where you cooked it. Roughly 37 states plus DC use destination sourcing, which means a caterer based in one city who serves a wedding two counties over generally charges the rate for the venue's address, not their own. A handful of origin-based states work the other way, and a few "home-rule" states add city-level twists on top. The right rate always comes from an address; the whole question is which address.

This article explains the rules and links the authorities that set them. It is not tax advice, your state's Department of Revenue and your accountant are the final word for your situation.

Why most of what you've read about this is wrong for caterers

Search "origin vs destination sales tax" and nearly everything you find is written for e-commerce, online sellers shipping boxes to a buyer's doorstep. That framing quietly misleads caterers, because a caterer's "delivery address" isn't a doorstep on a shipping label. It's an event venue, and it can differ from the client's billing address and from your kitchen. The e-commerce articles never deal with that three-address problem, so the advice transfers badly. A caterer who charges their home-city rate on every invoice because "that's where my business is" is applying origin logic in what is probably a destination state.

The destination rule, in caterer terms

Washington's Department of Revenue says it as plainly as any state: "The caterer must collect sales tax based on the location where the meals are served" (WA DOR, Caterers and catering). Cook in Tacoma, serve in Seattle, and Seattle's rate goes on the invoice.

That is the majority pattern. In a destination-sourced state, the taxable event happens where your client's guests eat, so the combined state + local rate for the venue's address is the one you collect. Your kitchen's rate is irrelevant unless the event happens to be in the same jurisdiction.

Origin states: the minority pattern

A minority of states, Arizona, Illinois, Mississippi, Missouri, Ohio, Pennsylvania, Tennessee, Texas, Utah, and Virginia, with California running a modified hybrid, source intrastate sales at the seller's location (TaxJar, origin vs destination). If you're a Texas caterer serving a Texas event, your own location's rate generally controls.

Two cautions before you relax. First, origin sourcing typically applies within the state; cross state lines and destination logic tends to take over. Second, even origin states carry wrinkles, district taxes, local use taxes, and special rules for delivered goods. Missouri, for instance, is origin-based on paper but layers 761 local jurisdictions with combined rates from 4.7% to 12.2%, plus destination-flavored use-tax rules for delivered goods (SalesTaxHandbook, Missouri). "Origin state" is the beginning of the answer, not the end.

Home rule: where it gets genuinely hard

A few states let cities administer their own sales tax, separately from the state. Colorado is the sharpest case: roughly 70 self-collecting home-rule cities, each of which can require its own registration and its own return (SalesTaxColorado, self-collecting jurisdictions). Alabama runs 200+ separately administered local taxes; Louisiana collects parish by parish; Alaska has no state sales tax but 100+ taxing municipalities.

The City of Arvada, Colorado, publishes the worked example every Denver-metro caterer should read. An out-of-city caterer serving an event in Arvada must collect Arvada's tax on the full invoice, food, rentals, setup, delivery, and the city explicitly bans burying it in the price: "Sales tax must be listed on the customer invoice and may not be absorbed into the total price" (City of Arvada, Caterers page). Serve events in three self-collecting cities in a summer and you may owe three separate registrations and three separate returns. That is not a software pitch; that is just what the rules say, and it is why metro Colorado caterers feel this problem hardest.

So which address sets your rate?

Work through it in order:

1. Is the event in a destination state (the ~37-state majority)? The venue's address sets the rate.
2. Is it an intrastate job in an origin state? Your business location's rate generally controls, check your state's rules for district and local add-ons.
3. Is the event in a home-rule city (CO, AL, LA, AK)? The city may administer its own tax on top of, or instead of, the state's collection, possibly with its own registration.
4. Billing address vs event address: the client's billing address is where the invoice goes; in destination states the service address is what the rate keys on. When they differ, that difference matters. (This question gets its own article: piece 2 of this series.)

The honest mechanic underneath all four branches: the right rate comes from an address. Not from your city, not from a statewide average, not from what the caterer across town charges. An address, looked up against the jurisdictions that tax it.

FAQ

"I cook in city A and serve the event in county B, which rate do I charge?" In a destination state, county B's combined rate, the rate for the venue's address. In an origin state, for an intrastate job, generally your own location's rate. Check which kind your state is before anything else.

"Do I use my city's sales tax rate for the cake?" (asked, nearly verbatim, by a Chicago baker on CakeCentral) Only if your city is where the sale is sourced. For a delivered wedding cake in a destination state, the delivery address controls, not your bakery's. Illinois is origin-based for intrastate sales, so the Chicago asker likely does use their own rate, but a baker in destination-based Wisconsin delivering to Madison would not.

"Does the rate apply to delivery, setup, and rentals too, or just the food?" It varies by state, and in home-rule cities like Arvada the answer can be "the whole invoice, including rentals, setup, and delivery." Itemization and what's taxable per line is its own topic, piece 3 of this series covers the invoice mechanics.

"What if I just charge my home rate on everything to keep it simple?" In a destination state you'd be collecting the wrong amount, too much (your client overpays and you're holding tax you can't cleanly remit) or too little (the shortfall is yours to make up out of pocket). "Simple" here usually means "wrong in one direction or the other."

Where Savi Tools fits

Savi Tools looks up the sales tax rate by address on the invoice. On the Growth plan, when your client has a full address, every invoice gets the jurisdiction-accurate rate applied automatically, and every taxed invoice records the state and ZIP it was taxed for. Your dashboard keeps a running view of what you've collected, split paid vs invoiced and address-accurate vs estimated, and at filing time you (or your accountant, through their free seat) export a clean CSV: state, ZIP, taxable amount, tax collected. Savi Tools tracks and reports; it does not file or remit tax, and it does not tell you where you owe, that stays with you and your accountant. Growth is $19/month. Start free →

Savi Tools tracks and reports collected sales tax by state and ZIP. It does not file or remit tax and does not provide nexus or tax advice. Consult your accountant. Never get surprised at tax time.