Skip to main content

Audit file

The Audit File Voorraad is a report required by the Dutch Customs authorities, in which all relevant information in relation to the inventory and customs declarations is listed in a specific format as specified in the MIG. Effectively, the Audit File is a translation of the data coming from our DSM report into a specific format. 


Completed

  • Full Technical report - To be validated by the Customs authoritiesauthorities;
  • All data related to discharges and loads;

  • Transaction Associated Documents. All documents for the declaration systems DMS, NCTS, and EMCS are included in the audit file.


To be completed


Balance data (inv_period_balance)

  • Records with location type INLAND_WATER. This concerns vessels that have been loaded or discharged at our site. In these cases there is no opening or closing stock (beginning_quantity and ending_quantity). The question is whether we should include received and dispatched quantities. From the terminal’s perspective, this is a kind of storage location. We will report Product as stock in cases where, in case of incoming, we have declared goods on board without a movement. The same principle applies to loads as long as there is no completed Departure. We assume in other cases, where we have not taken any responsibility for the products (yet) no reporting is required?

  • For trains, blending takes place on the wagon. The wagon receives (received) base product and additive, andafter basewhich the end product andis additive are dispatched (dispatched).dispatched. The additional rows (mutations) that are required to track the transfer between procedures (USF – usual form of handling) arestill currentlyrequire missingimplementation fromin theAudit audit file.File.

  • Inventory should reconcile per row (ending_quantity = beginning_quantity + received_quantity – dispatched_quantity). This is currently not yet the case. For cust_transfers (production (ETW), inward processing, and usual form of handling), the additional rows (mutations) that are currentlyrequired missingto track the transfer between procedures needs implementation in the audit file. We have not yet addressed this. The data required for this is already available in our detailed_stock_movements_cu table. This concerns movements between procedures.

  • Movements between tanks (tank-to-tank transfers) are missingnot infully somecompleted cases.yet. ToAlso resolvehere this,the wemutations need toimplemetation adjustinto the setupAudit in the business rule configuration to correctly populate detailed_stock_movements.File.


Transactions (inv_transaction and inv_transaction_char)

  • Tank-to-tank movements have not yet been included in the audit file. The required setup in the business rule mutation configuration has not yet been added.added to Audit File.

  • Due to the missing setup,setup “movement”of tothe USFmutations, or IPR is not yet handled correctly in all cases. Thethe chain that allows goods to be traced from CPW to IPR, IPR production, and back to CPW is stillnot missing.

    yet
    • fully
  • implemented. 

    This also applies to USF (usual form of handling).

  • In the case of a density correction, we set the value CT in the characteristic NL_CUST_TRANSFER. However, this does not correspond to the description (“correction due to temperature difference”). The code CT seemed the most appropriate to us.


Products (inv_product and inv_product_char)

  • New goods that are created through blending arerequire missingimplementation inof somethe casesmutations (see comment under Transactions regarding IPR and USF).


Transaction Associated Documents

  • All documents for the declaration systems DMS, NCTS, and EMCS are included in the audit file.

  • The other documents mentioned in code list 6 (codelist trans.submsyst) and code list 6 (codelist document code) are still being reviewed by us to determine whether they are applicable to our situation.


Points of attention

  • The specifications mention a number of columns and characteristics required to track goods with regard to movements (between procedures). We are testing whether this works correctly in all cases. The plan is to create an automated check for this in the future.

  • During the Deloitte GTA session on Thursday, 20 November, Customs indicated in their presentation what types of validations/checks they perform on the submitted data. Building similar checks is on our roadmap.

Back to top