You run the Model 340
- Generate VAT Tape File program to generate a text file that you submit to the
government for VAT reporting. The system writes records to the flat file for posted
invoices and vouchers and certain other intracommunity VAT transaction for transactions
that:
Exist in the Taxes table (F0018).
Have a GL date that is within the period and year specified in the processing
options.
You can specify either a month or a quarter as the reporting
period.
The text
file is divided into separate blocks, or record types, of information. The record types
included are:
Record Type |
Description |
Record Type 1 (A) |
The text file includes only one record type 1. This
record includes information about the reporting company, the
reporting period, and so on. |
Record Type 2 (B) (continued in next row of
table) |
The text file includes three types of transactions
in record type B:
Record type B.1 (emitted invoice register) includes:
Emitted invoices that are not for intracommunity VAT
that have a batch type of IB when the value for the
Description 2 field of the document type set up in
UDC 74S/RL is a value other than P or it
doesn't exist in UDC 74S/RL, and the value in the
Description 2 field of the tax rate area set up in
UDC 74S/RT is a value other than P or it
doesn't exist in UDC 74S/RT.
Emitted invoices with a batch type of G when the
value for the Description 2 field of the document
type set up in UDC 74S/RL is C, or the value
in the Description 2 field of the tax rate area set
up in UDC 74S/RT is C. If the document type
doesn't exist in UDC 74S/RL, then the system looks
at UDC 74S/RT. If neither UDC table includes the
appropriate setup, the transaction is not
included.
The positive line amount for VAT for a reverse charge
transaction.
Record type B.2 (received invoices register) includes:
Accounts payable records (received invoices) for
which the tax rate area is not set up for special
intracommunity transactions and for which the batch
type is V (voucher entry) or W (manual checks
without match).
Received invoices with a batch type of IB or G when
either the value for the Description 2 field of the
document type set up in UDC 74S/RL is P, or the
value in the Description 2 field of the tax rate
area set up in UDC 74S/RT is P. The system looks for
the document type first. If it doesn't exist in UDC
74S/RL, then the system looks for the tax area at
UDC 74S/RT. If neither UDC table includes the
appropriate setup, the transaction is not
included.
The positive line amount and the zero-rate line
amount when the Enter the tax rate area line for
received with amount 0 processing option is not
blank for a reverse charge transaction.
|
Record Type B (2) (continued) |
Note: The reporting of fixed assets subject to prorata
VAT is not supported by the JD Edwards EnterpriseOne software. These
fixed asset transactions are not included in the Model 340 VAT
report. You specify in the Tax Areas - Tag File Maintenance - ESP
program whether a tax rate area is used for fixed asset
transactions. Transactions that use the specified tax rate areas are
excluded from the report. |
The system writes the text file generated by the Model 340 - Generate VAT Tape File
program to the Text Processor Header table (F007101) and Text Process Detail Table
(F007111). You then use the copy function in the Text File Processor program (P007101)
to copy the text file to the media that you use to submit the file to the
government.
See "Working with the Text
File Processor" in the JD Edwards EnterpriseOne Applications Financial Management
Fundamentals Implementation Guide.
Note: To assure that the final text file
that you submit does not include errors, you should run the report in proof mode,
send the file for validation, correct any errors, then run the report in final mode
before sending the final text file.
You can include transactions with a batch type IB or G in the received invoice register
of Model 340 VAT report, by completing this setup in the 74S/RL and 74S/RT UDC tables:
Batch Type |
Conditions |
IB or G |
The document type exists in UDC 74S/RL and Description 2 is
equal to P.
The document type (DCT) does not exist in UDC 74S/RL, the tax
area (TXA1) exists in UDC 74S/RT, and Description 2 is equal
to P.
|
You can include transactions with a batch type IB or G in the emitted invoice register of
Model 340 report, by completing this setup in the 74S/RL or 74S/RT UDC tables:
Batch Type |
Conditions |
IB |
Document type (DCT) exists in UDC 74S/RL and Description 2 is
not equal to P.
Document type (DCT) does not exist in UDC 74S/RL and tax area
(TXA1) exists in UDC 74S/RT with a value which is not equal
to P in the Description 2 field.
Document type (DCT) does not exist in UDC 74S/RL and tax area
(TXA1) does not exist in UDC 74S/RT.
|
G |
Document type exists in UDC 74S/RL and Description 2 is equal
to C.
Document type (DCT) does not exist in UDC 74S/RL, the tax
area (TXA1) exists in UDC 74S/RT, and Description 2 is equal
to C.
|
Note: For both the received and emitted
invoices, the address number (AN8.F0018) must be other than 0.