Skip to content
Developerhome
Accounting
API Status:

Checking…

Breaking Changes in API version v1 in case of a No Deal Brexit

  Less than to read

Though the nature of Britain’s leaving the EU is still subject to uncertainty to this date (Sep 30, 2019), we owe you maximum clarity about what the possible scenario of a No-Deal-Brexit would mean for the API that we hold available to you. The following is a list of changes that will break your API integration when we switch our cloud software into “Hard Brexit mode”. You will be made aware of this event to react accordingly. The following is meant to help you get prepared for the changes. (As new scenarios for a Brexit arise, we will do our best to keep you updated.)

Note: The Brexit changes only affect businesses in the UK 🇬🇧 which are VAT-registered. Businesses in other countries supported by this API (Canada, France, Germany, Ireland, Spain, U.S.) can safely ignore the upcoming Hard Brexit changes.

Please be aware that all issues about pre- or post Brexit behaviour concern the official date of the invoice/credit note/payment, not the time of creation of this entity.

Goods/services indicator required for sales to foreign customers

Operations concerned

  • create and update actions on endpoints
    • /sales_invoices
  • create action on endpoints
    • /sales_invoices/:id/credit_notes

This change will only be in effect, when …

… all of the following two conditions are met:

  • The business which the resource is being created for is VAT registered.
  • The contact_id of the invoice refers to a foreign customer.

What will change?

In the data posted, the line item attribute eu_goods_services_type_id will become mandatory for foreign contacts which reside outside of the EU.

All other combinations (VAT/non VAT, in or outside the EU) do not require the eu_goods_services_type_id attribute for line items and set a default value when it’s not passed.

Possible values for eu_goods_services_type_id are 1 for goods and 2 for services.

There will be no change in the response body returned by the API.

Goods/services indicator required for purchases from foreign vendors

Operations concerned

  • create and update actions on endpoints
    • /purchase_invoices
  • create action on endpoints
    • /purchase_invoices/:id/credit_notes

This change will only be in effect, when …

… all of the following two conditions are met:

  • The business which the resource is being created for is VAT registered.
  • The contact_id of the invoice refers to a foreign supplier/vendor.

What will change?

In the data posted, the line item attribute eu_goods_services_type_id will become mandatory for foreign contacts which reside outside of the EU. Additionally on credit notes, the field also becomes mandatory when the contact is non VAT-registered.

All other combinations do not require the eu_goods_services_type_id attribute for line items and set a default value when it’s not passed.

Possible values for eu_goods_services_type_id are 1 for goods and 2 for services.

There will be no change in the response body returned by the API.

Limitations to Expenditures

Operations concerned

  • create and update actions on endpoints
    • /expenditures

This change will only be in effect, when …

… both of the following two conditions are met:

  • The business which the resource is being created for is VAT registered.
  • The contact_id of the invoice refers to a foreign supplier in the EU which is not VAT registered.

What will change?

The operation is not longer possible. The API will respond with a 422 status code.