topic Issue sending tax/VAT to 3rd party tool in 💬 RevOps Discussions

Issue sending tax/VAT to 3rd party tool

UserZ — Mon, 17 Nov 2025 18:29:38 GMT

Hi all,

I am trying to configure a connection between hubspot and easybill (billing/invoicing tool) and the custom coded connector is working for all datapoints except for VAT.

I realised I don't actually know how/where VAT is stored in hubspot because VAT or tax are not listed as a property anywhere I can find.

Has anyone else run into this issue? Have any advice?

Thanks!

Re: Issue sending tax/VAT to 3rd party tool

Jaycee_Lewis — Tue, 18 Nov 2025 23:52:20 GMT

Hi, @UserZ 👋 Thank you for your question. Let's invite a few of our community experts to the conversation — hey @Anton, @GiantFocal, @evaldas , have you set this up in any of your recent client work? Thank you for looking! — Jaycee

Re: Issue sending tax/VAT to 3rd party tool

UserZ — Fri, 21 Nov 2025 09:46:10 GMT

no need, I created a work around with a custom property on the company and deal 🙂
It is still a mystery where VAT on the line item is stored however...

Re: Issue sending tax/VAT to 3rd party tool

RubenBurdin — Mon, 15 Dec 2025 20:34:13 GMT

Hi @UserZ , this confusion is very common, so you’re not alone.

In HubSpot, VAT is not stored as a first-class CRM property on deals or line items. That’s why you can’t find it in the property settings. Taxes live in a slightly different layer depending on how you’re invoicing.

If you’re using line items only (no quotes), HubSpot does not persist VAT as a dedicated field. The tax amount is effectively baked into calculated totals like hs_total_price, but the VAT rate and tax value themselves are not exposed as readable properties via the UI or standard CRM APIs. This is why your connector can’t “see” VAT.

If you’re using Quotes, VAT is stored as part of the quote configuration, not the line item object. Tax details live on the quote object and are calculated at render time, which again makes them awkward to extract for external billing tools (https://knowledge.hubspot.com/products/create-and-use-taxes )

That’s why your workaround, adding explicit VAT fields on the company or deal, is actually the most reliable approach in 2025. Many teams do exactly this:

Store VAT rate and tax applicability as explicit custom properties
Let HubSpot calculate display totals for sales
Send clean, explicit tax fields to the invoicing system

If you need tax per line item downstream, the only deterministic option is to model it yourself with custom line item properties and calculate VAT outside HubSpot. HubSpot’s internal tax logic simply isn’t designed to be an external source of truth.

Your instinct was right. It’s not you. It’s just how HubSpot abstracts tax today.