The Event Address, the Billing Address, and the Kitchen: What Actually Sets a Caterer's Sales Tax Rate

A catering job involves up to three addresses, your kitchen, the client's billing address, and the event venue, and in most states only one of them sets the sales tax rate. In the destination-sourced majority of states (roughly 37 plus DC), it's where the food is served: the event address. In the origin-based minority it's your business location. The billing address, the one on the invoice header, is usually the least relevant of the three, except that when the event address isn't captured anywhere, the billing address is what everything falls back to.

This article explains the rules and links the authorities. It is not tax advice; your state's Department of Revenue and your accountant decide your situation.

Three addresses, one rate

Picture a real job. Your commissary kitchen is in one suburb. Your client, a corporate office, is headquartered downtown, and that's the address on the invoice. The retirement party you're catering is at a lake venue in the next county. Three addresses, three different combined tax rates. Which one goes on the invoice?

In a destination state, the rate follows the service location, the lake venue. Washington's DOR states the caterer's version of the rule flatly: collect "based on the location where the meals are served" (WA DOR). Not where you cooked. Not where the check gets cut. Where the meals hit the tables.

Why the billing address keeps sneaking in

Invoicing software, all of it, ours included, is built around a client record, and the client record carries a billing address. When a caterer creates an invoice, the address in play is the client's, and it's natural to assume the tax rate rides on it. Often that's harmless: for the personal chef cooking weekly in a client's home, billing and service address are the same house. For the wedding caterer whose client lives in one city and marries in another, they're not, and the rate difference between the two can be multiple percentage points.

The practical takeaway: know which address your invoice's tax rate is keyed to, and make it the service address when the state's rules point there. If your tool looks up tax by the client's address, put the venue's address on the job's client record, or at minimum confirm the two addresses share a jurisdiction before you send the invoice.

"Do I use my city's rate for the cake?"

A Chicago baker asked exactly this on CakeCentral: "I work in Chicago and the sales tax here is 11.25%. Do I use that tax for the cake?" (thread). The replies included advice to "check with the IRS and your county tax commission office", which conflates federal and local authorities and answers nothing, and is a fair picture of the guidance this industry gets.

The actual answer has two branches. Illinois sources intrastate sales at the seller's location, so for an in-state delivery the Chicago baker's own combined rate likely does control. But move the same question to a destination state, a Wisconsin baker delivering to a Madison wedding, and the delivery address takes over. Same cake, same question, opposite answers, purely because of which state's sourcing rules apply. That's why no one-line answer on a forum settles it, and why "which address" is the right question to ask before "which rate."

The kitchen address: when does it ever matter?

In origin-based states (Arizona, Illinois, Mississippi, Missouri, Ohio, Pennsylvania, Tennessee, Texas, Utah, Virginia; California modified), your business location's rate generally governs intrastate sales (TaxJar). That's the kitchen's moment. Everywhere else, your kitchen determines plenty, health permits, cottage-food eligibility, commissary rules, but not the sales tax rate on a delivered or served job.

One more caution for the origin-state caterers feeling relieved: cross-border jobs (your Texas kitchen, an Oklahoma event) flip into destination logic, and home-rule cities in states like Colorado can require the event city's tax regardless of where you're based, on the whole invoice, separately registered and filed (City of Arvada).

FAQ

"My client's billing address and the venue are in different counties. Which rate?" Destination state: the venue's. Origin state, intrastate: yours. The billing address only controls if it happens to be the service address too.

"I charge every client my own city's rate because that's where my business license is." That's origin logic. If you're in one of the ten origin-based states and the job is in-state, it may be right. In the other ~40 jurisdictions, it's systematically wrong, over- or under-collecting depending on where the events fall.

"The venue is a private home. Does that change anything?" The rule is the same, the rate keys on the service address, whoever owns it. What changes at private homes is practical: get the actual address on the job record early, because "the client's house" and "the client's billing address" are often assumed identical and sometimes aren't.

"What about the deposit I collected before I knew the venue?" Deposit-and-balance mechanics, what gets taxed when, and how to show it on the invoice, are piece 3 of this series.

Where Savi Tools fits

Savi Tools prices sales tax from an address, specifically, the client address on the invoice. On Growth, an invoice for a client with a complete address gets the jurisdiction-accurate rate looked up and applied automatically, and records the state and ZIP it was taxed for. So the working rule above becomes a one-step habit: put the service address on the job's client record, and the right rate follows. Your collected tax accrues into a running view, paid vs invoiced, address-accurate vs estimated, with a filing-time CSV your accountant can use from their free seat. We track and report; filing stays with you and your accountant. 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.