Managing Trade Statistics in version 12 A Process Overview Bruno Cabaret Product Management [email protected].

Managing Trade Statistics in version 12

A Process Overview

Bruno CabaretProduct [email protected]

Page 2

Version 12 - Solution

General configuration - per Division

Goods transactions not yet invoiced

MUC transactions management

Report declaration

Trade Statistic Reconciliation

Trade Statistic

Electronic Output management

Page 3

CRS726 Trade statistic Settings

New Settings (1 of 2)

Based on goods transactions

– This permitted to handled trade statistic from stock transactions.

Business type and Labor code for Distribution Orders

– This permitted to allocate value code for DO and Internal transactions.

Customs exchange rate

– For transfer into local currency for reporting.

Electronic forms - for Declarations

– Using E-Collaborator runtime maps.

Page 4

CRS726 Trade statistic Settings

New Settings (2 of 2)

Triangular and MUC operations

– It is possible to allocate transactions on invoice transaction (sales division),

– Or on the goods transaction (warehouse division)

– Or on the Movex internal invoice (exchange between divisions and external invoice).

Triangular operations are identified from:

– Country code on warehouse (delivery / receipt)

– Country code on address (customer)

– Country code on master file (customer / supplier)

– Country code on warehouse

Intrastat and Extrastat

– Same handling.

Page 5

Goods transactions not yet invoiced

New Process (1 of 2)

Goods transactions not yet invoiced can be created from two functions.

– TXS330 for customer orders

– TXS340 for purchase orders

Selections available to control:

– Order Number - from/to

– Warehouse - from/to

– Transaction date - from/to

These functions should be run at end of month (before Report Declaration)

– This permitted to create trade statistic transaction from inventory transactions that are not yet invoiced to the customer.

Page 6

Goods transactions not yet invoiced

New Process (2 of 2)

These new functions also permitted to recreate transactions

– Update database and recreate transactions (item, warehouse, customer, supplier…).

– Update additional information (invoice number, invoice year, voucher number and voucher series)

– It is not possible to recreate transaction already reported (status 90)

– Change in general setup CRS726 is not handled to delete previous transactions (this previous delete should be done manually).

Update Intrastat transactions on invoice

– Transactions created on goods not invoiced are updated when invoice is handled

– A new transaction without amount is created if goods transaction is already reported (status 90).

Page 7

Where are generated transactions?

MUC transactions (1 of 9)

Four cases of triangular operations identified:

– Sales division in the same country as warehouse division

– Sales division in the same country as customer/supplier

– Sales division, warehouse division and customer/supplier in three different countries

– Warehouse division in the same country as customer/supplier.

Three possibilities:

– Follow the goods

– Follow customer/supplier invoice

– Follow internal invoice

Intrastat / Extrastat

– Automatic handling between Intrastat and Extrastat with the same setup.

Page 8

VAT registration number

MUC transactions (2 of 9)

External

– From Customer/Supplier in case of export with customer/supplier

– From division/warehouse for internal transactions

Internal

– From warehouse

– From country code if not registered on warehouse

Page 9

MUC transactions (3 of 9)

A standard process rule for simple case

CustomerEU 2

Sales divisionEU 1

Order

GoodsInvoice

WarehouseEU 1

External

Internal / MUC

•Export to customer from warehouse•EU Sales to customer

No differences between warehouse and sales division country

Page 10

MUC transactions (4 of 9)A standard process rule for more complex case

CustomerEU 2

Sales divisionEU 1

Order

GoodsInvoice

Internal InvoiceDelivering division

EU 3

Three options•1 = Follow goods•2 = Follow invoice•3 = Follow internal invoice

Four cases corresponding to country legal rule about triangulation•EU1 = EU3 <> EU2•EU1 = EU2 <> EU3•EU1 <> EU2 <> EU3•EU1 <> EU2 = EU3

External

Internal / MUC

Page 11

MUC transactions (5 of 9)Case 1 – EU1 = EU3 <> EU2

Country of Sales division = country of delivering division <> country of customer delivery address

EU 2

EU 1 EU 3

1 = Follow goods2 = Follow invoice3 = Follow internal invoice

Follow goods transactions

•Export (info type 2 or 5) to EU2 in EU3 division based on customer delivery/invoice

Follow External Invoice

•Export (info type 2 or 5) to EU2 in EU1 division based on customer delivery/invoice

Follow internal invoice

•Option 3 not available because it is not an EU transaction

Quarterly report

•Quarterly report (info type 3) in EU1 division for customer invoice

Page 12

MUC transactions (6 of 9)Case 2 – EU1 = EU2 <> EU3

Country of Sales division = country of customer delivery address <> country of delivering division

EU 2

EU 1 EU 3

1 = Follow goods2 = Follow invoice3 = Follow internal invoice

Follow internal invoice

•Export (info type 2 or 5) to EU1 in EU3 division based on internal invoice•Import (info type 1 or 4) from EU3 in EU1 division based on internal invoice

Follow goods transactions

•Export (info type 2 or 5) to EU2 in EU3 division based on customer delivery/invoice

Follow External Invoice

•No transaction because it is not an EU operation

Quarterly report

•No transaction because it is not an EU operation

Page 13

MUC transactions (7 of 9)Case 3 – EU1 <> EU2 <> EU3

Country of Sales division <> country of customer delivery address <> country of delivering division

EU 2

EU 1 EU 3

1 = Follow goods2 = Follow invoice3 = Follow internal invoice

Follow internal invoice

•Export (info type 2 or 5) to EU1 in EU3 division based on internal invoice•Import (info type 1 or 4) from EU3 in EU1 division based on internal invoice•Export (info type 2 or 5) to EU2 in EU1 division based on external invoice

Follow goods transactions

•Export (info type 2 or 5) to EU2 in EU3 division based on customer delivery/invoice

Follow External Invoice

•Export (info type 2 or 5) to EU2 in EU1 division based on customer delivery/invoice

Quarterly report

•Quarterly report (info type 3) in EU1 division for customer invoice•Quarterly report (info type 3) in EU3 division for internal invoice

Page 14

MUC transactions (8 of 9)Case 4 – EU1 <> EU2 = EU3

Country of Sales division <> country of customer delivery address = country of delivering division

EU 2

EU 1 EU 3

1 = Follow goods2 = Follow invoice3 = Follow internal invoice

Follow internal invoice

•Export (info type 2 or 5) to EU1 in EU3 division based on internal invoice•Import (info type 1 or 4) from EU3 in EU1 division based on internal invoice•Export (info type 2 or 5) to EU2 in EU1 division based on external invoice

Follow goods transactions

•No transaction because it is not an EU operation

Follow External Invoice

•Export (info type 2 or 5) to EU2 in EU1 division based on customer delivery/invoice

Quarterly report

•Quarterly report (info type 3) in EU1 division for customer invoice•Quarterly report (info type 3) in EU3 division for internal invoice

Page 15

Triangular and MUC transactions (9 of 9)A standard process rule for all countries legal requirement

EU 2

EU 1 EU 3

1 = Follow goods2 = Follow invoice3 = Follow internal invoice

Case 1EU 1 = EU3 <> EU2•Goods

•Export to EU2 in EU3 division•Invoice

•Export to EU2 in EU1 division

Case 2EU 1 = EU2 <> EU3•Goods

•Export to EU2 in EU3 division•Invoice

•Nothing•Internal invoice

•Export to EU1 in EU3 division •Import from EU3 in EU1 division

Case 3EU 1 <> EU2 <> EU3•Goods

•Export to EU2 in EU3 division•Invoice

•Export to EU2 in EU1 division•Internal invoice

•Export to EU1 in EU3 division, •Import from EU3 in EU1 division •Export to EU2 in EU1 division

Case 4EU 1 <> EU2 = EU3•Goods

•Nothing•Invoice

•Export to EU2 in EU1 division•Internal invoice

•Export to EU1 in EU3 division, •Import from EU3 in EU1 division•Export to EU2 in EU1 division

Customer

Sales division Delivering division

Country code

Page 16

Added handling

Report Declaration (1 of 1)

New report layouts in CRS600

– Report layouts 22 and 23 are added with sort and accumulation

– Report layouts 32 and 33 are added for report of standard printout for accumulation.

Report declaration Reconciliation

– Report declaration number, line number and report period are stored in Trade Statistic transactions when transaction status is set to 90.

Trade Statistic display

– View 7 permitted to access on report line declaration.

Page 17

With Stock transactions

Trade Statistic Reconciliation (1 of 3)

Intrastat transactions are created with link to one stock transaction

– Source file (CO, PO or DO), Order number, Order line, Delivery number and warehouse is stored on records

Trade Statistic display

– Jump to Stock transaction MWS070 is available by option 12 from Trade statistic to control origin.

Page 18

With Accounting entries

Trade Statistic Reconciliation (2 of 3)

At invoice process OIS100 / APS100 the Intrastat transaction are updated

– Accounting date, voucher number, voucher series, invoice year and invoice number are stored on Intrastat transactions

Trade Statistic display

– Jump to Voucher display GLS200 is available with option 13 from Trade statistic to control information

– View 6 is also available.

Recreate transactions from TXS330 for Customer Orders or TXS340 for Purchase Orders

– Accounting information are get

Page 19

With Internal Invoice

Trade Statistic Reconciliation (3 of 3)

At invoice process MFS100 the Intrastat transaction are updated

– Transactions based on Internal invoice process (setup 3) are updated with information from MUC (internal price, transfer currency code, customer code and supplier code)

– For others setup (1 and 2) no information is stored in Intrastat transactions

Trade Statistic display

– If an order is included in MUC jump to Internal invoice display MFS200 is available with option 14 from Trade statistic to control information.

Recreate Intrastat transactions for Distribution Orders

– New function TXS350

– Internal information are get from MUC

Page 20

Electronic form

Electronic Output Management (1 of 1)

Setting

– Electronic form is defined per division in CRS726.

Automatic management

– When running CRS600 with report layout 22, 23, 32 or 33 two files are created

– These two files (header and detail) are get by e-collaborator and send to customs.

Page 21

Summarize change in v12 In Previous Versions

– Transactions are created from invoice.

– Goods not invoiced are not included.

– Transactions are not always created in the good company.

– No easy link with sources

In V12

– Transactions are created from invoice process like previous version.

– Goods not invoices can be included.

– Setup in CRS726 permitted to define where transactions should be created.

– Internal invoice transaction can be included

– Standard EDI file

– Link with Stock transactions

– Link with Internal invoices

– Link with accounting voucher

– Link with Tax Declaration Report line.

Page 22

Table of Contents

Workflow Use

Use

Use

Results

Before Starting Gives you the starting condition for the process.

Workflow Describes the different activities in the process.

Results Tells you what you get at the end.

Uses Indicates what the results can be used for.

BeforeStarting

Managing Trade Statistics

Page 23

Before Starting

Your Company Must Have

Well-defined routines and policies for Configuring and Reporting Intrastat

Configured its system

– See supporting process: Configuring for Trade Statistics (TST)

Managing Trade Statistics

Page 24

The Intrastat Process in MovexIntrastat

Page 25

Configuring Trade Statistics

ERM for Configuring for Trade Statistics

Intrastat

Page 26

Reporting Imports

ERM for Reporting Imports

Intrastat

Page 27

Reporting Exports and EU Sales

ERM for Reporting Exports and EU Sales

Intrastat

Page 28

Identify Scenario and MUC structure

Customer

CustomerDelivery address

Deliveringwarehouse

DivisionOwner of

delivering warehouse

Sellingdivision

FiscalRepresentativeof selling Division

Goods

Invoice

Order

Int.Invoice

Export

Import

EU sales

EU sales

Triangular cases10 S = W <> C20 S = C <> W30 S <> C <> W40 S <> C = W

S

W

C

Page 29

MUC=0

Customer

CustomerDelivery address

Deliveringwarehouse

Sellingdivision

Goods

Invoice

Order

GG1FA6006(FR)

Int.Invoice

Export

Import

EU sales

UK

GG1FA6(FR)

FR

EU sales

Triangular cases10 S = W <> C20 S = C <> W30 S <> C <> W40 S <> C = W

Page 30

MUC=0 with fiscal representative

Customer

CustomerDelivery address

Deliveringwarehouse

Sellingdivision

FiscalRepresentativeof selling division

Goods

Invoice

Order

GG1FA6006(FR)

Int.Invoice

Export

Import

EU sales

UK

GG1FA6(FR)

FR

UK

EU sales

Page 31

MUC=1

Customer

CustomerDelivery address

Deliveringwarehouse

Sellingdivision

Goods

Invoice

Order

GG1FAE107(GB)

Int.Invoice

Export

Import

EU sales

SE

GG1FA6(FR)

FR

EU sales

Triangular cases10 S = W <> C20 S = C <> W30 S <> C <> W40 S <> C = W

31 2Option :

Page 32

MUC=1 with fiscal representative

Customer

CustomerDelivery address

Deliveringwarehouse

Sellingdivision

FiscalRepresentativeof selling division

Goods

Invoice

Order

GG1FAE107(GB)

Int.Invoice

Export

Import

EU sales

SE

GG1FA6(FR)

FR

SE

EU sales

Page 33

MUC=2

Customer

CustomerDelivery address

Deliveringwarehouse

Owner division of delivering warehouse

Sellingdivision

Goods

Invoice

Order

AAAFA1106(FR)

Int.Invoice

Export

Import

EU sales

UK

EEEFA6(FR)

AAAA01(SE)

FR

EU sales

Triangular cases10 S = W <> C20 S = C <> W30 S <> C <> W40 S <> C = W

31 2Option :

Page 34

ResultsResults

Things Look Better Now,

Trade Statistic records automatically created by Movex

Records reviewed

Legal Reports generated and sent to the authorities

Detailed back-up available in Movex

Page 35

Uses

What Do You Do Next?

Time previously spent producing reports can now be spent adding value to the business

Page 36

www.lawson.com