Prepare tax exemption and customer tax ID context in Getme
Use customer tax ID and exemption context carefully in supported tax workflows while keeping merchant responsibility clear.
Use this article to prepare exemption and customer tax ID context for Getme tax workflows where supported. Customer tax ID, exemption, reverse-charge, zero-rate, and certificate/documentation workflows remain provider-backed or workflow/account dependent unless confirmed in the specific product implementation. Getme does not decide whether a customer, product, shipping charge, service, or transaction qualifies for a different tax treatment.
Before using exemption or tax ID context
- Confirm the customer type, country, region, billing details, shipping context, and transaction workflow.
- Confirm whether the tax ID, exemption, reverse-charge, zero-rate, product, or shipping treatment is supported for that context.
- Collect, review, validate, and retain exemption certificates, tax IDs, customer declarations, or other supporting records where your business is required to handle them.
- Use approved sources or qualified review when the exemption or customer tax ID affects what tax is charged.
Customer tax IDs and business details
Customer tax IDs can be collected, stored, or attached to customer and transaction context only where the configured workflow supports it. Provider checks may confirm format or run supported validation flows, but Getme should not be treated as validating the tax ID, customer identity, exemption eligibility, certificate documentation, or tax outcome.
Exempt customers and exemption context
Some customers may have exemption context, such as nonprofit, government, reseller, or business-to-business situations, depending on jurisdiction and documentation. Your business is responsible for deciding whether that exemption applies and whether documentation is required before relying on the setting.
Product, shipping, and transaction context
Exemption or zero-rate context can depend on product type, shipping treatment, service type, customer status, destination, and transaction path. Keep product and shipping context separate when reviewing why tax was or was not applied, because a customer exemption and a product or shipping setting can affect the same transaction differently.
Reverse charge or zero-rate context
Reverse charge or zero-rate treatment can apply only where the provider workflow, customer tax ID context, jurisdiction, and transaction details support it. Treat this as provider-backed where supported, not as a universal Getme decision or a promise that every B2B transaction qualifies.
What Getme does not validate or decide
- Whether a customer is legally eligible for an exemption.
- Whether a customer tax ID proves the customer’s identity or business status for every jurisdiction.
- Whether a certificate, declaration, or supporting document is sufficient for your business.
- Whether reverse charge, zero-rate, product exemption, or shipping exemption treatment should be used.
- Whether collected tax context is ready for filing, remittance, financial records, or tax authority review.
Status table
| Item | Status |
|---|---|
| Customer tax ID | merchant/customer-provided, needs-review |
| Tax ID format check | provider-dependent, source-check-needed |
| Tax ID validity | not-guaranteed-by-getme |
| Exempt customer context | merchant-responsibility |
| Exemption certificate or documentation | merchant-responsibility |
| Product exemption context | workflow-dependent |
| Shipping exemption context | workflow-dependent |
| Reverse charge / zero-rate context | provider-backed where supported |
| Country or jurisdiction support | country/account-dependent |
| Filing and remittance | not-provided-by-getme |
| Qualified review | merchant-responsibility |