Migration of Customs Declaration Tax ID Fields

Within the GeneralCustomsDeclaration object, simple string fields for tax IDs have been deprecated in favor of a structured object.

Summary of Changes

• Deprecated Fields on GeneralCustomsDeclaration:
  • seller_tax_id_number (string)
  • buyer_tax_id_number (string)
• Replacement:
  • seller_identification_numbers (object TaxIdentificationNumbers)
  • buyer_identification_numbers (object TaxIdentificationNumbers)

Reason for Deprecation

The TaxIdentificationNumbers object provides distinct fields for common identification types (e.g., vat, eori, ioss). This removes ambiguity and provides a clearer structure.

Before Migration (Example JSON Body)

You might have been populating the GeneralCustomsDeclaration object like this, assuming the number was a VAT number:

{
  ...
  "general_customs_declaration": {
    "seller_tax_id_number": "SE1234567890",
    "buyer_tax_id_number": "DE0987654321"
  }
}

After Migration (Example JSON Body)

You now need to identify the type of tax number you were providing and place it in the corresponding field inside the new object.

{
  ...
  "general_customs_declaration": {
    "seller_identification_numbers": {
      "vat": "SE1234567890"
    },
    "buyer_identification_numbers": {
      "vat": "DE0987654321"
    }
  }
}

If the number was an EORI number, you would use the eori field instead:

{
  ...
  "general_customs_declaration": {
    "seller_identification_numbers": {
      "eori": "SE1234567890"
    }
  }
}

You must map the previous string value to the correct field within the TaxIdentificationNumbers object based on the type of ID it represents.