Knowledgebase
1Whitepapers 61Network Time Servers (NTS) 8Time Servers (TS) 7Atomic Clocks (AC) 6Digital Clocks
Knowledgebase
Whitepapers (1)
Network Time Protocol and Leap Second Tutorial
Network Time Servers (NTS) (61)
Apache Log4j Vulnerability
Time Servers (TS) (8)
TS-300-MSF Hardware Manual
TS-400-GPS Hardware Manual
TS-500-GPS Hardware Manual
TS-500-MSF Hardware Manual
Atomic Clocks (AC) (7)
AC-100-MSF Hardware Manual
AC-300-MSF Hardware Manual
AC-400-GPS Hardware Manual
AC-500-GPS Hardware Manual
Digital Clocks (6)
Daylight Savings Time Calculator
Firmware
Inova Clocks Hardware Manual
SignalClock Insert - Timezone Setting Adjustment
  
NTS-4000-R - Known Issue with 6.0

We are aware of an issue with the NTS-4000 units running firmware older than 6.1 showing an incorrect date as of the 1st of January 2015.

The problem can be easily fixed by updating the firmware on your unit.

First you will need to download the software used to program the unit and the firmware file, both available in the zip file below.

Download NTS-4000 Firmware Version 6.2

Note: To make things easier extract the zip file to somewhere you can easily access like the desktop.

With most zip software, you can simply right click the zip file for extraction options.

Then install the NTS-4000 configuration client (SETUP.EXE)

When you have installed the NTS-4000 Configuration Client open the software and click on the magnifying glass in the top left of the application.

Note: You may need to allow firewall access if this is the first time you have used the software.

The magnifying glass searches your network for NTS-4000 units and will list them in the box below when it finds them.

To update the firmware on a unit click on the unit then click on the update firmware button (The third button along).

Enter the password or if there is no password set simply click "ok".

You will then be asked to locate the firmware file from the zip that you have downloaded.

The software is then sent to the unit this takes upto five minutes.

After this, you should receive a message telling you that the firmware was successful.

Your unit should now be running version 6.2 of the software.

If, during the update, you receive an error code (usually a negative error code) this is due to the software not being able to access the unit.

You should check that the windows firewall and your network firewall allow both TCP and UDP access to the NTS-4000.

Your local network administrator should be the first point of contact for these errors.

NTS-4000-S - Known Issue with 6.0

We are aware of an issue with the NTS-4000 units running firmware older than 6.1 showing an incorrect date as of the 1st of January 2015.

The problem can be easily fixed by updating the firmware on your unit.

First you will need to download the software used to program the unit and the firmware file, both available in the zip file below.

Download NTS-4000 Firmware Version 6.2

Note: To make things easier extract the zip file to somewhere you can easily access like the desktop.

With most zip software, you can simply right click the zip file for extraction options.

Then install the NTS-4000 configuration client (SETUP.EXE)

When you have installed the NTS-4000 Configuration Client open the software and click on the magnifying glass in the top left of the application.

Note: You may need to allow firewall access if this is the first time you have used the software.

The magnifying glass searches your network for NTS-4000 units and will list them in the box below when it finds them.

To update the firmware on a unit click on the unit then click on the update firmware button (The third button along).

Enter the password or if there is no password set simply click "ok".

You will then be asked to locate the firmware file from the zip that you have downloaded.

The software is then sent to the unit this takes upto five minutes.

After this, you should receive a message telling you that the firmware was successful.

Your unit should now be running version 6.2 of the software.

If, during the update, you receive an error code (usually a negative error code) this is due to the software not being able to access the unit.

You should check that the windows firewall and your network firewall allow both TCP and UDP access to the NTS-4000.

Your local network administrator should be the first point of contact for these errors.

Packaging Guidelines

To ensure that Galleon Systems receives a returned product free from damage, we urge you to follow these packing guidelines for safe transit of the item(s):

a) Where possible, return the product in its original packaging ensuring that it is secured appropriately within the box. Products should be protected using the polystyrene inserts [provided with the original packaging]. For added protection, pack surrounding voids with packing materials originally supplied.

The box should fit snuggly around the item and there should be minimal or no movement of the product once sealed in the box. Seal the box accordingly using industrial strength tape, making sure there are no gaps. The box should be sealed without the potential to open whilst in transit.

b) If (a) is not possible, a suitable alternative is required, ensuring that the box is of the correct size and strength to accommodate the enclosed unit. The product will need to be secured tightly within the box, making sure it’s completely protected and virtually free from movement.

Corners can be protected using polystyrene and to further protect the unit, Galleon Systems recommends heavy duty bubble wrap. It’s important that the box and packing used fits snuggly around the item to restrict movement in transit.

Ensure any voids within the box are packed with protective materials, then seal the box with industrial strength tape, making sure there are no gaps. The box should be sealed without the potential to open whilst in transit.

*Please note, Galleon Systems accepts no liability for returned products received in a damaged state, any damage caused will need to be referred to your courier.

Returns Procedure

To obtain any Technical Support with any of our products, please submit a ticket.

If throughout the Technical Support process it is deemed that you need to send any products back for repair, we will issue a Return Material Authorisation (RMA) Number and shipping instructions. For products returned from outside the EU please inform the carrier that the goods are to be repaired and sent back and will therefore qualify for Inward Processing Relief. Then ship the product, transportation prepaid, for inspection.

Typical Equipment repair or replacement time is five (5) business days, plus shipping times. One-way shipping is the customer’s responsibility. Galleon Systems will return ship the equipment by the same means it was received.

Galleon Systems will not be responsible for unauthorised returns or for returns that do not list the RMA Number on a packing list attached in plain view on the outside of the shipping container.

Setting up redundancy

This article provides useful information for our customers who wish to setup their devices in redundancy mode. Please note that the information in this article applies to the NTS-6001 and 6002 units only, running Firmware 11 or higher.

If your time server is running a software version older than version 11, you will need to upgrade your device to the latest firmware. The latest firmware brings with it the latest in security, stability and bug fixes. Upgrade instructions can be found here:

NTS-6002 Upgrade Instructions

NTS-6001 Upgrade Instructions

Below are a few redundancy features that our NTP servers offer:

(A) Teaming - This method enables both network cards in your NTS-6002 or 6001 to work together as one single card. This provides more bandwidth for the network and redundancy for your NTP server. There are 2 redundant modes for Teaming: Load Balancing and Failover. Load balancing will step in if one network card is under more stress than the other network card. In this case, load balancing will send data to the other network card and effectively balance the load between both network cards. Failover kicks in if one network suddenly becomes offline for whatever reason. Failover will use the second network until the first network is back online. Also, if in rare circumstances the network card becomes faulty, the second network card will take over. Load balancing and failover are both on by default when Teaming is enabled on your NTP server.

(B) Peering – Peering your NTP server to one or more time servers means that if your server loses connection with its antenna, it would synchronise to the peered time server via the Network Time Protocol. In theory, this should prevent disruption to client(s) that your NTP server is serving. What’s good about this option is that you don’t need to purchase another Network Time Protocol server, you could configure peering to a public time server (such as; pool.ntp.org). Providing your server has access to the Internet, this should work fine.

(C) Using Two Time Sources with your NTP server – This method requires two antennas. Here at Galleon Systems, we offer dual time-source NTP servers. Specifically, the NTP server will have both a GPS and Radio antenna connected to it. The NTP server will always favour GPS as a time-source as it is more reliable and accurate than the radio time-source. However, if for whatever reason, the server was to lose connection with its GPS antenna, the unit should switch to the radio time source. MSF is the radio signal for the UK (the signal originates from Cumbria), DCF for Frankfurt, Germany and WWVB for North America.

(A) How to enable Teaming

  1. Navigate to the web interface and login with your credentials. Ensure your device is running software version 11 or above by navigating to the Software Versions page, which is under the Administration tab in the web interface (if you have an NTS-6002, your device will be on version 11).
  2. Ensure you have connected both Ethernet cables which should lead to different switches or routers. Navigate to the Teaming page which is under the Network tab. Enter your network information. For fault tolerance and load balancing, ensure the bond mode is set to 'balance-rr'. Once you have finished configuring the unit, click 'Enable Teaming'.

For changes to take effect, you will need to restart the unit. To confirm if the changes have been taken effect, log into the web interface and view the 'Dashboard'. You should see 'Bonded Network' and all the relevant network information. This can be seen in the print screen below.

(B) How to configure Peering

To peer your NTP server to one or more NTP servers, you need to ensure that the NTP servers can reach each other. If you are peering to an Internet time server, ensure your NTP server has Internet access. You can verify reachability by using the Ping tool which is under the Network Tools tab. If your NTP server is going through a firewall, ensure port 123 over UDP is allowed on your Firewall.

  1. Navigate to the web interface and login with your credentials. From the navigation menu on the left click 'NTP' and then 'NTP Customisation'.
  2. You will now need to type in the IP address of the other NTP Server. Type the following command without quotes 'server 192.168.0.2' and replace the IP in this statement with the IP or hostname of the second NTP Server. If you are peering your NTP server to a pool (for example: pool.ntp.org), the statement would be ‘pool pool.ntp.org’. Replace the hostname in this statement with the hostname or IP of the pool. Once you have completed this step, you can verify if the peer was successful by following the steps below.

Verifying if your NTP server is being assisted

You can confirm if the peering was successful by logging into the web interface and clicking 'NTP' and 'NTP Status'. If there is a '*' next to the IP, it means that this is the current time source. The '+' refers to an NTP Server that is assisting you. If there is a ‘+’ next to the IP address or hostname of the NTP server that you configured peering with, it means you have peered the NTP servers together successfully. You can refer to the screenshot below for more information.

An 'X' is used to indicate an NTP server that has lost connection with its time source, as shown in the print screen below.

(C) Using Two Time Sources with your NTP server

Contact Galleon Systems if you wish to purchase another antenna for your NTP server. Please note that we can only guarantee compatibility with a Galleon NTP server. For more information, fill in our contact form: http://www.galsys.co.uk/contact/

Apache Log4j Vulnerability

Dear Customers,

 

Recently we have received many inquires surrounding the Apache Log4j vulnerability in relation to our equipment.

We can confirm that our NTS Time Servers don’t use this service and therefore are not susceptible to this vulnerability.

We would like to take this opportunity to wish everyone a Merry Christmas and a Happy New Year.

 

Best,

Galleon Systems Technical Support

 

How to upgrade to Firmware 12#8

This article contains upgrade instructions for the NTS-6002.

Please note: Upon update, the default network settings are restored to DHCP,  as such the NTS-6002 may not be accessible via the web interface if your network does not have a DHCP server attached to it.

(A) Upgrading via the web interface

1. Log in to the Web Interface and navigate to Administration. Select Backup.

2. Click Create Backup and download the backup file to your computer.

3. Download the firmware file from here. (please right-click on the link and click save as...)

4. From the Web Interface, select Administration from the navigation menu on the left.

5. Select Firmware Update and select the upgrade file.

6. Click the Update button.

The device will now perform the upgrade. Please allow 1 minute for the device to upgrade.

To verify the upgrade was successful, click Software Versions under the Administration tab. Under Operating System, confirm 5.10.109-Galleon-NTS-6002.V12 - #8 is displayed.

For Release Notes, click here.

Network Time Server Firmware Version 12

This update is available for the following units:

NTS-6002 Firmware: Please click here

Click here for NTS-6002 upgrade instructions. (please right click on the link and click save as...)

NTS-6001 Firmware: Please click here

Click here for NTS-6001 upgrade instructions. (please right click on the link and click save as...)

Please note NTS-6001 units with firmware version eight or below are no longer supported and cannot use this update.

Firmware 12#7 (Latest)

Release Date: 

  • Fixed an issue where changing the IP Address manually from onboard the NTS-600x works.
  • Fixed stray tags in the HTML code for the Linux OS
  • Fixed an issue in the certificate model where it was removing dashes from the Alternate Name.
  • Removed the ability to configure a Hostname on both network cards (the Hostname relates to the device itself and is independent of the network cards).
  • Added TLSv1.3 support.
  • Updated leap-seconds. list with the latest version (Expires 28 June 2020)
  • Updated the Linux kernel to 6.7.12
  • Updated Nginx to 1.18.0
  • Updated PHP to 7.4.18

Firmware 12#5

Release Date: 

  • Fixed an issue where changing the bonding mode in the web interface sometimes did not apply.
  • Fixed an issue in the certificate model where it was removing dashes from the Alternate Name.
  • Removed the ability to configure a Hostname on both network cards (the Hostname relates to the device itself and is independent of the network cards).
  • Added TLSv1.3 support.
  • Updated leap-seconds.list with the latest version (Expires 28 June 2020)
  • Updated the Linux kernel to 5.4.21
  • Updated Nginx to 1.16.1
  • Updated PHP to 7.2.16

Firmware 12#4 

Release Date: 01/04/2019

  • Fixed an issue where changing the bonding mode in the web interface sometimes did not apply.
  • Fixed an issue in the certificate model where it was removing dashes from the Alternate Name.
  • Removed the ability to configure a Hostname on both network cards (the Hostname relates to the device itself and is independent of the network cards).
  • Added TLSv1.3 support.
  • Updated Configuration Options on the Configure SSL page in the web interface.
  • Updated leap-seconds.list with the latest version (Expires 28 June 2020)
  • Updated the Linux kernel to 5.2.21
  • Updated PHP to 7.2.1

NTP has been updated to 4.2.8p13 which has the following security fixes:

  • Sec 3565: Crafted null dereference attack from a trusted source with an authenticated mode 6 packet

A crafted malicious authenticated mode 6 (ntpq) packet from a permitted network address can trigger a NULL pointer dereference, crashing ntpd. Note that for this attack to work, the sending system must be on an address that the target's ntpd accepts mode 6 packets from, and must properly authenticate the packet with a private key that is specifically listed as being used for mode 6 authorization.

This NTP version provides 17 bugfixes and 1 other improvement. 

Firmware 12#3

Release Date: 29/01/2018

  • Fixed an issue with Teaming where the web interface would prevent the user from changing the bond mode.
  • Fixed an issue with the Teaming page not reflecting the current Teaming settings.
  • Resolved a bug where GPS/Radio debugging would not output to the screen due to a bad Mime type.
  • Updated the certificate model to add the CN to the subject alternate names to prevent certificate errors.
  • Fixed an issue where, upon logging in via FQDN, the system would redirect from FQDN to IP address.
  • Fixed an issue with the NMEA Log not displaying errors correctly.
  • Added a Configure SSL page under Administration that will allow users to choose from Secure SSL Configuration and Compatibility Configuration. Secure SSL Configuration will support the TLSv1.2 protocols and modern cipher suites. Compatibility configuration supports the TLSv1.2, TLSv1.1 and TLSv1 protocols along with older SSL cipher suites for compatibility with older clients.
  • Applied mitigations against the Meltdown vulnerability (CVE-2017-5754).
  • Added secure flag to Cookies.
  • Updated Nginx to 1.12.1
  • Updated OpenSSH to 7.6p1
  • Updated OpenSSL to 1.0.2m
  • Updated PHP to 7.1.11
  • Updated CodeIgniter to 3.1.7

Firmware 12#1

Release Date: 13/04/2017

  • XSS headers added to Ngnix
  • Software update available notification added to Dashboard header
  • Incorrect logins recorded under Authentication Log now show in red
  • Updated the leap-seconds.list file to account for the upcoming leap second
  • Updated the Linux kernal to 4.10.9
  • Updated Nginx to 1.10.3
  • Updated OpenSSH to 7.5p1
  • Updated OpenSSL to 1.0.2k
  • Updated NetSNMP to 5.7.3
  • Updated PHP to 7.1.3
  • Updated CodeIgniter to 3.1.4

NTP has been updated to 4.2.8p10@1.3728-o which has the following security fixes:

Network Time Server Firmware Version 12#8

This update is available for the following units:

NTS-6002 Firmware: Please click here 

Click here for NTS-6002 upgrade instructions.

NTS-6001 Firmware: Please click here 

Click here for NTS-6001 upgrade instructions.

Please note that NTS-6001 units with firmware version eight or below are no longer supported and cannot use this updated.

Firmware 12#8 (Current)

Released Date: May 2022

  • Nginx updated to 1.20.2
  • Kernel updated to 5.10.109
  • OpenSSH updated to 8.9p1
  • OpenSSL updated to 1.1.1n
  • PHP updated to 8.0.17
  • Leap seconds updated to the latest (expires December 2022)

Firmware 12#7 

Release Date: 01/11/2021

  • Fixed an issue where changing the bonding mode in the web interface sometimes did not apply.
  • Fixed an issue in the certificate model where it was removing dashes from the Alternate Name.
  • Added TLSv1.3 support.
  • Updated bug allowing the change in settings for TLSV1.3 to be saved.
  • Fixed issues with bonding to use Active-Backup as default.
  • Fixed DNS backup bug, allowing the DNS to be moved from primary to secondary when one is unavailable.
  • Updated DHCP settings to be changed using the keyboard. 
  • Updated Configuration Options on the Configure SSL page in the web interface.
  • Updated Nginx to 1.18.1
  • Updated OpenSSH to 8.0p1
  • Updated OpenSSL to 1.1.1d
  • Updated NETSNMP to 5.9
  • Updated PHP to 7.3.11
  • Updated NTP Service to 4.2.8p15@1.3728-o

Firmware 12#5

Release Date: 

  • Fixed an issue where changing the bonding mode in the web interface sometimes did not apply.
  • Fixed an issue in the certificate model where it was removing dashes from the Alternate Name.
  • Removed the ability to configure a Hostname on both network cards (the Hostname relates to the device itself and is independent of the network cards).
  • Added TLSv1.3 support.
  • Fixed issues with bonding to use Active-Backup as default.
  • Updated DHCP settings to be changed using the keyboard. 
  • Updated Configuration Options on the Configure SSL page in the web interface.
  • Updated leap-seconds.list with the latest version (Expires 28 June 2020)
  • Updated the Linux kernel to 5.2.21
  • Updated Nginx to 1.16.3
  • Updated PHP to 7.4.1
  • Updated OpenSSH to 7.8p1
  • Updated OpenSSL to 1.1.0d

__________________________________________________________________________________________________________________________________________________________________________________________________________

Firmware 12#4

Release Date: 01/04/2019

  • Fixed an issue where changing the bonding mode in the web interface sometimes did not apply.
  • Fixed an issue in the certificate model where it was removing dashes from the Alternate Name.
  • Removed the ability to configure a Hostname on both network cards (the Hostname relates to the device itself and is independent of the network cards).
  • Added TLSv1.3 support.
  • Updated Configuration Options on the Configure SSL page in the web interface.
  • Updated leap-seconds list with the latest version (Expires 28 June 2020)
  • Updated the Linux kernel to 5.2.21
  • Updated Nginx to 1.16.1
  • Updated PHP to 7.3.11

NTP has been updated to 4.2.8p13 which has the following security fixes:

  • Sec 3565: Crafted null dereference attack from a trusted source with an authenticated mode 6 packet

A crafted malicious authenticated mode 6 (ntpq) packet from a permitted network address can trigger a NULL pointer dereference, crashing ntpd. Note that for this attack to work, the sending system must be at an address that the target's ntpd accepts mode 6 packets from, and must properly authenticate the packet with a private key that is specifically listed as being used for mode 6 authorization.

This NTP version provides 17 bug fixes and 1 other improvement. 

Firmware 12#3

Release Date: 29/01/2018

  • Fixed an issue with Teaming where the web interface would prevent the user from changing the bond mode.
  • Fixed an issue with the Teaming page not reflecting the current Teaming settings.
  • Resolved a bug where GPS/Radio debugging would not output to the screen due to a bad Mime type.
  • Updated the certificate model to add the CN to the subject alternate names to prevent certificate errors.
  • Fixed an issue where, upon logging in via FQDN, the system would redirect from FQDN to IP address.
  • Fixed an issue with the NMEA Log not displaying errors correctly.
  • Added a Configure SSL page under Administration that will allow users to choose from Secure SSL Configuration and Compatibility Configuration. Secure SSL Configuration will support the TLSv1.2 protocols and modern cipher suites. Compatibility configuration supports the TLSv1.2, TLSv1.1 and TLSv1 protocols along with older SSL cipher suites for compatibility with older clients.
  • Applied mitigations against the Meltdown vulnerability (CVE-2017-5754).
  • Added secure flag to Cookies.
  • Updated Nginx to 1.12.1
  • Updated OpenSSH to 7.6p1
  • Updated OpenSSL to 1.0.2m
  • Updated PHP to 7.1.11
  • Updated CodeIgniter to 3.1.7

Firmware 12#1

Release Date: 13/04/2017

  • XSS headers added to Ngnix
  • Software update available notification added to Dashboard header
  • Incorrect logins recorded under Authentication Log now show in red
  • Updated the leap-seconds list file to account for the upcoming leap second
  • Updated the Linux kernel to 4.10.9
  • Updated Nginx to 1.10.3
  • Updated OpenSSH to 7.5p1
  • Updated OpenSSL to 1.0.2k
  • Updated NetSNMP to 5.7.3
  • Updated PHP to 7.1.3
  • Updated CodeIgniter to 3.1.4

NTP has been updated to 4.2.8p10@1.3728-o which has the following security fixes:

NTP Check Tool

This software is a test tool that acts as a client to a NTP server. The Galleon SNTP client reports on the responses it receives and allows you to check the accuracy and precision of a NTP time server. You can specify how many requests to send and how large the time between each. The SNTP server checker is easy to use and can test the accuracy and reliability of any NTP server.

  • IP address - the time server you are checking.
  • NTP Version
  • Reference timestamp (the prime epoch ) used by NTP to work out the time from this set point
  • Round trip delay (the time it takes request to arrive and come back in milliseconds)
  • Local clock offset - time difference between host and client
  • Leap indicator (if there is to be a leap second that day - normally only on 31 December)
  • Mode 3 - indicates a client request
  • Stratum level - which stratum level the NTP server is (a stratum 1 server receives the time from an atomic clock source a stratum 2 server receives the time from a stratum 1 server)
  • Poll Interval (Will be 1 as only 1 requests is made by the SNTP client)
  • Precision - how accurate in milliseconds
  • Root Delay - This is a signed fixed-point number indicating the total roundtrip delay to the primary reference source at the root
  • Root dispersion (in milliseconds)- The root dispersion is the maximum (worst case) difference between the local system clock and the root of the NTP tree (stratum 1 clock)
  • Ref ID - the host name
  • Originate time stamp (time before synchronisation request)
  • Receive timestamp - the time the host got request
  • Transmit timestamp - the time the host sends back to us
  • Is response valid - synchronised or not

NTP Server Checker

Returning a product using IPR (Inward Processing Relief)

Galleon Systems deals with customers all over the world and therefore, has extensive knowledge of Inward Processing Relief (IPR). In order to help customers save money on shipping costs, in the rare instance products are returned to us for repair or replacement, we recommend finding out if your business is eligible for IPR.

To qualify for IPR, upon returning your Galleon Systems product simply inform your shipping courier that the goods being returned are to be repaired (or replaced), then re-exported. Your shipping courier will inform UK Customs and they will keep a record.

Upon receipt of the goods Galleon Systems will be notified that they came using IPR. Galleon Systems will then notify UK Customs when re-exporting the goods that IPR is in place, removing the requirement to pay duties.

As a Galleon Systems customer all that is required from you is informing your shipping courier that the goods are to be repaired and re-exported, qualifying you for Inward Processing Relief. Galleon Systems then takes care of the rest.

TimeSync 4 Manual

This is the Manual for TimeSync 4.

It will provide information regarding the installation and configuration of the software.

What Is Inward Processing Relief?

What is IPR?

IPR is a trade facilitation initiative that entitles overseas businesses to return products to the UK, for repair or replacement, free from import/export fees.

This exemption is granted on the condition that goods are returned to Britain within six months of receiving them.

As an added benefit, IPR could also remove the requirement to pay VAT (Value Added Tax).

How does IPR benefit businesses?

It cuts import and export shipping costs. The fact is, any goods simply arriving in the UK will be subject to import duty and VAT, this is a legal requirement.

However, if you’re returning goods to Britain for the purpose of repair or replacement with a view to those goods being re-exported, businesses could qualify for import duty and VAT exemption thanks to the IPR initiative.

The IPR initiative benefits importer and exporter equally. For example the importer is able to keep their prices competitive and their cost savings can be passed onto customers who will ultimately re-export the goods.

In the same way, should a business be the final exporter, purchasing goods that originate from outside the European Community (EC) from another party based in Britain/the EC, they can acquire the relief and pass it onto the exporter.    

The purpose of the entire IPR initiative is to benefit businesses by increasing European Community competitiveness in world trade.

Types of Inward Processing (IP)

There are two types of Inward Processing and Inward Processing Relief can be provided by way of suspension or drawback.

IP Suspension – UK customs duties are suspended when returned goods are first entered into the IP system. Suspension is considered the most suitable method for traders re-exporting all imported goods after processing.

IP Drawback – IP drawback means that a business pays the initial customs duties, and other costs, when the imported goods are first entered into the IP system. It is then possible to claim back duty expenses when exporting them after processing. Drawback is considered most suitable for traders intending to export goods.

Qualifying for IPR

To claim exemption from import/export fees and VAT using the IPR initiative you will require authorisation from UK customs.

 

Understanding Authorisations

There are five types of Inward Processing authorisation:

#1 – Simplified authorisation – allows companies to enter goods into IP without making a prior application for authorisation.

#2 – Local authorisation – for use by companies that use the IP system on a regular basis.

#3 – Specific authorisation – for use by companies that need to show why they are unable to use goods produced in the EU rather than importing from outside.

#4 – Single community authorisation – for use by companies if IP goods are to be processed in more than one member state of the EU.

#5 – Integrated authorisation – covers authorisation for IP and other customs procedures with economic impact.

For a more detailed explanation of Inward Processing authorisation and IPR relief, Galleon Systems recommends visiting www.gov.uk/inward-processing

Most popular articles 
 
Newest articles