Back to blog
本地化

Customers Asking for a VAT Invoice — What Should Support Send?

Sep 3, 20266 min read

“Please send me a VAT invoice for my order.” For a brand selling domestically this is a two-minute task. Selling cross-border into the EU, it is a request that support can easily get wrong in ways that cost the customer real money — a business buyer who cannot reclaim VAT because your document is missing a field has effectively paid 20% more than they expected. VAT invoice support is one of the few areas where a well-meaning improvised answer is worse than a slower, correct one. Chuhaike handles these requests daily, and this guide sets out where the line sits.

Key takeaways

  • An order confirmation or payment receipt is not a VAT invoice, and customers asking for one usually know the difference.
  • Compliant invoices have mandatory fields — a missing VAT number or invoice number makes the document useless for reclaim.
  • B2B and B2C requests follow different paths, and the customer’s VAT number is what separates them.
  • Support should issue from a template, never hand-edit tax amounts — that line belongs to finance.
  • Most of this can be automated away; recurring manual invoice requests are a systems gap, not a staffing one.

Why this request is not trivial abroad

In much of the EU, a VAT-registered business buyer has a statutory right to a compliant invoice, and their ability to reclaim the VAT depends entirely on the document being correct. That turns what looks like an admin request into something with direct financial consequence for the customer — which is exactly why these tickets escalate faster than their apparent size suggests.

The second complication is that the answer depends on facts support may not have: whether the sale was B2B or B2C, which entity sold the goods, whether VAT was collected at checkout under an IOSS scheme or paid by the customer at import, and whether the reverse charge applies. Get the classification wrong and you either issue a document the customer cannot use, or state a tax treatment that is simply incorrect.

What a compliant invoice has to contain

FieldWhy it mattersCommon failure
Sequential invoice numberRequired for the document to count as an invoiceReusing the order number instead
Invoice date and supply dateDetermines the reporting periodOnly showing the order date
Seller legal name, address, VAT numberIdentifies the supplying entityShowing the brand name, not the legal entity
Buyer name, address, VAT number (B2B)Without it the buyer cannot reclaimNever collected at checkout
Net amount, VAT rate, VAT amount, grossThe reclaimable figure must be explicitShowing only the total paid
CurrencyRequired where it differs from local currencyAmbiguous symbols such as a bare dollar sign

The single most common gap is the last row of the B2B case: the buyer’s VAT number was never captured at checkout, so no invoice issued afterwards can be fully compliant without going back to the customer. Adding an optional VAT number field to checkout removes a large share of these tickets before they exist.

Triage the request before answering

Most invoice tickets fall into four buckets, and identifying which one you are in should take under a minute.

  • B2C, just wants a receipt — the customer wants documentation for expenses or a warranty claim. A standard invoice showing VAT included is enough.
  • B2B with a VAT number on file — reissue from the template with the buyer’s details populated. Straightforward if checkout captured the number.
  • B2B without a VAT number on file — collect and validate the number, then reissue. Validate it rather than trusting the format; an invalid number invites problems later.
  • Import VAT paid by the customer — the customer paid VAT to the carrier at import, not to you. Your invoice will not show that VAT, and support needs to explain why, pointing them to the carrier’s import documentation.

Support issues invoices from a template. Support does not calculate, adjust, or reclassify tax. Writing that boundary into the SOP protects both the customer and the brand.

Where support stops and finance starts

Agents should be able to reissue an invoice, correct a buyer’s name or address, add a validated VAT number, and resend a document — all from a template, with no discretion over the numbers. Anything that changes the tax treatment goes to finance: a customer claiming they should not have been charged VAT, a reverse charge question, a dispute over the rate applied, or a request to reissue an invoice from a different legal entity.

The reason for a hard line is that an agent’s guess here is not a service error, it is a tax statement made on the brand’s behalf. Give agents a holding response that is honest about the handoff and gives a real timeline — “our finance team will confirm the treatment and come back to you within two business days” — rather than leaving them to improvise something plausible-sounding under time pressure.

Finally, treat volume as a signal. If invoice requests are a recurring category rather than an occasional one, the fix is upstream — a VAT number field at checkout, automatic invoice generation attached to the order confirmation, and a self-service download in the account area. Those three changes typically remove the majority of this ticket type, which is a far better outcome than handling them efficiently.

How Chuhaike handles VAT and invoice requests

Chuhaike — Shenzhen Chuhaike Cross-Border E-commerce Co., Ltd. runs invoice requests as a triage with a hard escalation line. Agents classify the request into the four buckets above, reissue from brand-supplied templates with no discretion over tax figures, validate buyer VAT numbers before adding them, and route anything touching tax treatment to the brand’s finance contact with a holding response that sets a real timeline. Recurring request patterns are reported back so the brand can close the gap at checkout rather than staffing around it. The team covers 15+ languages on 7×24 scheduling, with first response under two minutes on live channels, CSAT at or above 90% and NPS 8.2 / 10, handling 200,000+ tickets a month. Chuhaike serves 100+ clients across 20+ industries, holds ISO 27001 and ISO 9001 certification, and operates in line with GDPR and CCPA requirements.

FAQ

Is an order confirmation the same as a VAT invoice?

No. An order confirmation records what was bought; a VAT invoice is a tax document with mandatory fields including a sequential invoice number, the seller’s VAT registration and an explicit VAT amount. A business buyer generally cannot reclaim VAT from an order confirmation.

The customer forgot to enter their VAT number at checkout — can we still help?

Usually yes. Collect the number, validate it, and reissue the invoice with the buyer’s details. Whether the tax treatment itself can be changed after the fact is a finance question, not a support one, so confirm before promising a refund of the VAT charged.

The customer says they already paid VAT to the courier. Why is it on our invoice too?

It should not be. If VAT was collected at import by the carrier, your invoice should not also charge it — a customer reporting both is describing either a duplicate charge or a misunderstanding of the carrier’s handling fee. Either way it goes to finance, with the carrier’s import paperwork attached.

Can Chuhaike issue invoices on our behalf?

Yes, from your templates and within your rules. Chuhaike reissues and resends invoices, validates buyer VAT numbers, and escalates anything affecting tax treatment to your finance team rather than deciding it at the agent level.

Invoice and VAT requests piling up in your support queue? Talk to Chuhaike — Shenzhen Chuhaike Cross-Border E-commerce Co., Ltd. Visit chuhaikecx.com, WeChat chuhaikecx, or call 182-3116-2335.

Related Articles