Why do I need to put my tax registration number (for example, a VAT number or VAT ID) on all the accounts in my organization?

AWS assesses whether tax is due on the usage of each individual account based on each account's contact address, billing address, and, if applicable, the Tax Registration Number (TRN).

Adding a TRN to each applicable account means that the relevant TRN appears on each of your tax invoices for the applicable accounts, which enables you to claim credits from your local tax authorities, if applicable.

If AWS accepts TRNs from your country on the Tax Settings page, adding a TRN, business legal name, and business legal address to each of these accounts in your organization does the following:

  • Identifies the account as a "Business" customer.
  • Helps determine if AWS needs to collect tax for each individual account.
  • Allows AWS to issue tax-compliant invoices for each applicable account.

Note: The TRN on the member account can be the same as the TRN on the master account. If your organization includes different legal entities or different countries, you can have different TRNs for each account. Master accounts in an organization can check or update multiple linked accounts at the same time from the Tax Settings page of their console.

Accounts with the same TRN are grouped together on a single, itemized VAT invoice. If there are accounts in your organization without a TRN, each account receives its own tax invoice, if applicable.

For example, assume that your organization has a master account with a specific TRN, four member accounts with the same TRN as the master account, and six member accounts without a TRN. You'll receive a total of seven VAT invoices:

  • One VAT invoice for the five accounts sharing the same TRN.
  • One invoice for each account without a TRN.

In this example, if your TRN is applicable to the six accounts that don't currently have a TRN, and you add the TRN to these accounts, you'll receive only one VAT invoice.


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2018-06-01