Skip to main content

Parties

In the dealing with Products, we deal with various Parties in the Supply chain. The Parties involves vary from Customers to Surveyors, but also Consignors and Consignees, or Customers of our Customers to which assets are sub-leased. But it could also be  Hence, a generic concept is the registration of Parties of which certain data related to those Parties should be available in the operational process. 

For example. When Product is loaded for a destination being another Terminal, a User should be 'bothered' only with specifying the destination/Consignee. In all likelihood, a customs declaration or electronic message is required in which the Consignee must be listed with potentially address details, a 'Tax warehouse reference' and a License reference. This data should be readily available from the parties setup, instead of a User having to specify every single time. As explained under Locations, a Terminal (Rotterdam and Amsterdam Location example) can be one of multiple locations listed under a License. This means that on the registration of Parties it should be carefully considered that certain data elements can be listed per party. In this case the physical location (Third Party Terminal name) should be registered as a Party including data elements such as:

  1. Address details;
  2. Economic Operators Registration and Identification (Eori) number (if avaiable);
  3. Excise warehouse license number (if available);
  4. Tax warehouse reference number under Excise warehouse (if available);
  5. ....

Another example is a Customer. When we import Product for our Customers, typically the VAT on import is for the account of the Customer. In many cases there is a facility subject to a license that allows the customer to defer the VAT to their periodic VAT return, where they don't have to pre-finance the VAT and then recover, but they can simply include it in their VAT return as a payable and receivable at the same time. If we do the import declaration, we don't want to 'bother'the user by having to include this information. Rather the registration of the Customer under Parties should allow the registration of a 'VAT deferment license' number. Hence, wherever a business process involves Party information, the details around the Party should come from the Party setup rather then having to key in data at every instance.
 
 

Wherever a business process involves Party information, the details around the Party should come from the Party setup rather then having to 'bother' a user to key in data at every instance