<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tc/onlinemanual/000067" xml:lang="en">
   <Header>
      <Title>EU Intrastat reporting</Title>
      <Keyword type="header" order="d1e1130208">
         <Level1>EU Intrastat</Level1>
         <Level2>overview</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1130213">
         <Level1>Intrastat</Level1>
         <Level2>overview</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>In LN, you can generate the
		EU Intrastat declaration and supply it to the Intrastat authorities by means of
		an external Intrastat provider program or directly in the format of an
		Instat/XML file.</Paragraph>
      <Paragraph>You can add or correct
		import/export-statistics data manually before you generate the output file.
		Refer to <Link href="/baanerp/tc/onlinemanual/000090" role="manual">Intrastat provider programs</Link> for details.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Collecting the Intrastat declaration data</SectionTitle>
      <List>
         <ListIntro>For the <Link href="/baanerp/tc/glossary/glossary#Intrastat_tc" role="glossary">Intrastat declaration</Link>,
		  the tax authorities provide you with a list of:</ListIntro>
         <ListItem>The goods on which you
		  must report.</ListItem>
         <ListItem>The commodity codes of
		  the goods.</ListItem>
         <ListItem>For some commodity
		  codes, the <Link href="/baanerp/tc/glossary/glossary#000410" role="glossary">supplementary unit</Link> you must use for the reported
		  quantities.</ListItem>
      </List>
      <Paragraph>Common requirements exist for all EU countries as well as
		country-specific requirements. Most of the data can be retrieved from LN and you must configure
		some extra data by defining extra Intrastat info sets.</Paragraph>
      <Paragraph>The data that exists in LN is collected from the
		various LN packages
		through <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>.</Paragraph>
      <Paragraph>LN collects the data from all orders that result in the shipment or receipt of
		items to which you have linked a commodity code, to EU member countries that
		are different from the country of your company's address.</Paragraph>
      <Paragraph>If prices are changed after the registration of receipts or
		deliveries, the logged Intrastat data is corrected directly by <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef>, <GUIRef href="/baanerp/sales" role="package">Sales</GUIRef>, <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>, or <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</Paragraph>
      <Paragraph>If the price of an order line changes after the receipt or issue
		of the goods, or invoice differences occur in the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module,
		the logged Intrastat data is updated. If a price change applies to multiple
		Intrastat lines, the difference amount is split over the lines. For example, if
		a sales order line results in multiple deliveries, multiple Intrastat lines are
		generated.</Paragraph>
      <Paragraph>Difference amounts caused by matching of an invoice to a
		purchase order line can also apply to multiple Intrastat lines. In this case,
		the difference amount is split over the Intrastat lines proportionally to the
		line amounts. Note that already processed Intrastat lines and lines with an
		internal price are not updated.</Paragraph>
      <List>
         <ListIntro>If prices are changed or invoice differences occur, the
		  following sessions update the logged Intrastat data:</ListIntro>
         <ListItem>
            <GUIRef href="/baanerp/td/pur/tdpur4122m000" role="session">Change Price and Discounts after Receipt (tdpur4122m000)</GUIRef>
         </ListItem>
         <ListItem>
            <GUIRef href="/baanerp/td/sls/tdsls4122m000" role="session">Change Prices and Discounts after Delivery (tdsls4122m000)</GUIRef>
         </ListItem>
         <ListItem>
            <GUIRef href="/baanerp/tf/acp/tfacp1110s000" role="session">Purchase Invoices (tfacp1110s000)</GUIRef>, during invoice
		  matching</ListItem>
         <ListItem>
            <GUIRef href="/baanerp/tf/acp/tfacp2107m000" role="session">Match/Approve Purchase Invoices (tfacp2107m000)</GUIRef>
         </ListItem>
         <ListItem>
            <GUIRef href="/baanerp/ts/soc/tssoc2121m000" role="session">Service Order Actual Material Costs (tssoc2121m000)</GUIRef>
         </ListItem>
         <ListItem>
            <GUIRef href="/baanerp/ts/msc/tsmsc1110m000" role="session">Part Lines (tsmsc1110m000)</GUIRef>
         </ListItem>
      </List>
      <Paragraph>The value of the goods is
		logged in the transaction currencies. When you export the Intrastat data, LN converts the amounts
		to the local currency using the exchange rates of the invoice date or order
		date. LN applies the
		transaction exchange-rate or the external exchange-rate as described in <Link href="/baanerp/tc/onlinemanual/000068" role="manual">To use the external exchange rate type</Link>. Unless the country is in a currency
		transition state, the local currency is the euro. If LN cannot find the
		exchange rates, LN exports the amounts in the transaction currency and places the transaction
		currency in the Currency field.</Paragraph>
      <Paragraph>In most countries,
		transactions of which the quantity and/or the value is zero must not be
		reported.</Paragraph>
      <Paragraph>In the <GUIRef href="/baanerp/tc/com/tccom7100s000" role="session">Intrastat Parameters (tccom7100s000)</GUIRef> session, you can select the required
		logging method for transactions concerning cost items and service items. For
		example, you can specify whether the transactions must always be logged, or
		only if a commodity code is present.</Paragraph>
      <Paragraph>In some countries, the Intrastat declaration must include the
		province or area from which the goods were exported. To provide this
		information, LN includes
		the <GUIRef href="/baanerp/tc/com/tccom4135s000#tccom135.stat" role="manual">State/Province</GUIRef> field of the ship-from address in the
		Intrastat data.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Extra Intrastat information sets</SectionTitle>
      <Paragraph>Intrastat data that cannot be retrieved from LN can be supplied by
		defining extra Intrastat information sets. For example, you must define the <Emphasis>Nature of Transaction A</Emphasis> attribute as an extra Intrastat
		info field. This field usually has the value 1 to indicate “All transactions
		involving actual change”.</Paragraph>
      <Paragraph>You can define up to 15 extra info set fields.</Paragraph>
      <Paragraph>You can define a default extra Intrastat information set for
		each ship-to business partner and ship-from business partner. When you create a
		sales order line, a purchase order line, or a project, you can use the default
		value or you can select a separate extra Intrastat information set for the
		order line.</Paragraph>
      <Paragraph>To set up extra Intrastat information sets, you must use the <GUIRef href="/baanerp/tc/com/tccom7104m000" role="session">Extra Intrastat Info Definition (tccom7104m000)</GUIRef> session to define the number of fields
		and the field length, and then use the <GUIRef href="/baanerp/tc/com/tccom7505m000" role="session">Extra Intrastat Info (tccom7505m000)</GUIRef> session to define the values of the fields.</Paragraph>
      <Paragraph>As the required number of fields and the length of each field
		can differ in each country, you can define the extra Intrastat information sets
		per country. For each field, you can specify the default value.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Correcting Intrastat transaction data and
		calculations</SectionTitle>
      <Paragraph>In the <GUIRef href="/baanerp/tc/com/tccom7171m000" role="session">Intrastat Transactions (tccom7171m000)</GUIRef> session, you can view the recorded data.
		You can supply missing data and make any necessary corrections, for example, to
		the quantity, the goods flow, and the nature of the transaction.</Paragraph>
      <Paragraph>As you can set up only one default delivery terms or <Link href="/baanerp/tc/glossary/glossary#000411" role="glossary">Incoterm</Link> code for a business
		partner and for an order type, it is possible that you need to correct the
		Incoterm code of some transactions.</Paragraph>
      <Paragraph>The Intrastat data must reflect the actual transaction data as
		they are recorded in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> and <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. Therefore, you cannot change the data
		related to the quantity or the invoice value. For corrections to this data, you
		must duplicate the record to be corrected and create a new <GUIRef href="/baanerp/tc/domains/corg#manual.corr" role="option">Manual Correction</GUIRef> transaction. In addition, manually entered transactions
		that do not originate from LN are made visible in the Intrastat
		declaration by the <GUIRef href="/baanerp/tc/domains/corg#manual" role="option">Manual Transaction</GUIRef> order origin.</Paragraph>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>Negative values are not allowed for the Intrastat declaration.
		  For example, to correct an Intrastat <GUIRef href="/baanerp/tc/domains/com.kotr#requirement" role="option">(-) Issue</GUIRef> transaction with a quantity of 500 because the actual quantity
		  was 450, you must manually create a <GUIRef href="/baanerp/tc/domains/com.kotr#receipt" role="option">(+) Receipt</GUIRef> transaction of 50.</Paragraph>
      </Note>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Correcting the invoice values</SectionTitle>
      <Paragraph>In some countries, the invoice value must be corrected, for
		example, to exclude the freight costs. It is also possible that goods that are <GUIRef href="" role="manual">Free Of Charge</GUIRef> have an invoice value of 0, but a statistical
		value of 1000 EUR. As the value of 1000 EUR cannot be based on the LN data, you must enter
		this value in <Link href="/baanerp/tc/glossary/glossary#000409" role="glossary">IDEP</Link>. Some IDEP versions
		provide 'Statistical Rules' to recalculate invoice values automatically.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Calculating the quantity in the supplementary
		unit</SectionTitle>
      <Paragraph>In the <GUIRef href="/baanerp/tc/mcs/tcmcs0128m000" role="session">Commodity Codes (tcmcs0128m000)</GUIRef> session, for some types of items you must define <Link href="/baanerp/tc/glossary/glossary#000410" role="glossary">supplementary unit</Link>. For example, the supplementary unit
		for recording tape is meters. If you import or export recording tape, you must
		report the weight and the number of meters. The supplementary unit for tiles is
		m2. If you import or export tiles, you must report the weight and the number of
		square meters.</Paragraph>
      <Paragraph>The <GUIRef href="/baanerp/tc/mcs/tcmcs0128m000#tcmcs028.quan" role="manual">Quantity per Reporting Unit</GUIRef> field in the <GUIRef href="/baanerp/tc/mcs/tcmcs0128m000" role="session">Commodity Codes (tcmcs0128m000)</GUIRef> session indicates the multiples of the supplementary
		unit in which you must report the shipped quantities. For example, if the
		supplementary unit is liters and the quantity per unit is 10, each time you
		ship 10 liters of the item the quantity for the Intrastat declaration increases
		by one.</Paragraph>
      <Paragraph>For details, refer to <Link href="/baanerp/tc/onlinemanual/000409" role="manual">The supplementary unit</Link>.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>The Intrastat data and the sales listing data</SectionTitle>
      <Paragraph>In some countries, auditors use the sales listing to check the
		Intrastat declaration data. However, in a number of aspects the Intrastat
		declaration data must be more detailed than the sales listing data. For
		example, the sales listing reports the goods values as a total per sold-to
		business partner, and the Intrastat declaration data include the goods values,
		the quantities, the commodity codes, and the transaction details.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Mapping the data</SectionTitle>
      <Paragraph>Some LN field values must be translated to the corresponding values required for the
		Intrastat declaration. For example, in some countries the various 3-character <Link href="/baanerp/tc/glossary/glossary#000411" role="glossary">Incoterm</Link> codes are
		compressed by type and represented by a single character code.</Paragraph>
      <Paragraph>For these types of translations, in the <GUIRef href="/baanerp/tc/com/tccom7120m000" role="session">Intrastat Mapping Scheme (tccom7120m000)</GUIRef> session, you can define the Intrastat mapping
		scheme to translate specific LN field values to the required values for the
		Intrastat declaration.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Preparing the export data</SectionTitle>
      <Paragraph>In the <GUIRef href="/baanerp/tc/com/tccom7271m000" role="session">Process Intrastat Transactions (tccom7271m000)</GUIRef> session, you can select the range of data
		to be exported by a number of criteria.</Paragraph>
      <List>
         <ListIntro>The following rules apply:</ListIntro>
         <ListItem>If you select a range of offices (departments), the departments
		  must all belong to enterprise units that are linked to the same financial
		  company. This is to avoid that the Intrastat data of different financial
		  companies is mixed.</ListItem>
         <ListItem>In many countries, separate Intrastat declarations are required
		  for the import flow and the export flow. To export the data for one flow, in
		  the <GUIRef href="/baanerp/tc/com/tccom7271m000#flow" role="manual" Update="No">Flow</GUIRef> field, select either <GUIRef href="/baanerp/tc/domains/com.kotr#receipt" role="option">(+) Receipt</GUIRef> or <GUIRef href="/baanerp/tc/domains/com.kotr#requirement" role="option">(-) Issue</GUIRef>.</ListItem>
         <ListItem>LN logs
		  the Intrastat amounts in the transaction currencies. When you export the data
		  from LN to the external
		  Intrastat application, the amounts are converted to the local currency using
		  the currency rates that are valid at the transaction time and date. If no
		  currency rate can be found, the export file contains the transaction currency
		  and the amount in the transaction currency. For information purposes, the
		  invoice value is also displayed in the local currency.</ListItem>
      </List>
      <Paragraph>When you export the Intrastat data, the amounts are converted to
		the company's local currency. If you must make the Intrastat declaration in
		euros and the company's local currency is other than euro, you can convert the
		amounts to euros in the IDEP application.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>The export file</SectionTitle>
      <Paragraph>To transfer the Intrastat data to the Intrastat provider
		program, you can export the data from LN to a file which you can import into the
		Intrastat application, or into Excel to create an Excel sheet if required. For
		a better performance, the Intrastat export file is first saved on the server
		and you can transfer it to the client.</Paragraph>
      <List>
         <ListIntro>You can create the following types of files:</ListIntro>
         <ListItem>ASCII Comma Separated Values (CSV) file.</ListItem>
         <ListItem>ASCII Positional file as required for IRIS.</ListItem>
         <ListItem>An Instat/XML file.</ListItem>
      </List>
      <Paragraph>Refer to <Link href="/baanerp/tc/onlinemanual/000066" role="manual">The Intrastat data</Link> for
		details.</Paragraph>
      <Paragraph>A positional file must not be compressed. The separator of a
		positional file can be comma or space.</Paragraph>
      <Paragraph>If you create a CSV file for IDEP, use the .csv extension to
		indicate the file type. If you want to process the file with Microsoft Excel,
		you can import the file as an Excel (.xls) file. Use the delimiter character
		for the column separation. You can generate a file header which in Excel
		results in a header row with column names.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>The EU Intrastat declarations in a multifinancial company
		structure</SectionTitle>
      <Paragraph>The EU Intrastat declaration requirements and the external
		application that can be used to generate the EU Intrastat declaration differ
		for the various European countries. Therefore, you must set up the EU Intrastat
		declaration data per country.</Paragraph>
      <Paragraph>All the enterprise units of the departments that submit their
		Intrastat declaration in one tax return must belong to the same financial
		company because the financial company has the tax number and the country. In a
		multifinancial company structure, if you set up the EU Intrastat declaration
		data you can enter the financial company to which the data applies. If you do
		not specify a company number, the data applies to all the financial companies
		for which you do not define company-specific data.</Paragraph>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000053" role="manual">To set up the EU Intrastat declaration</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000064" role="manual">To export the Intrastat data</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000066" role="manual">The Intrastat data</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000068" role="manual">To use the external exchange rate type</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>