Oracle EMEA Add-on Localizations

Hungary Real Time Reporting

June 2018
Version: 1.0

Page 1 of 35
Table of Contents
Introduction............................................................................................................................................3
Features..................................................................................................................................................4
Setup steps............................................................................................................................................6
Reports and Processes.........................................................................................................................6
Pre-requisites...................................................................................................................................................6
Setup requirement...........................................................................................................................................6
Process – CLE: Invoice Data Extract – XML and CLE: Invoice Data Extract File Loader....................... 12
Conditions for XML file creation:.................................................................................................................. 12
Mapping table...............................................................................................................................................12
CLE: Invoice Data Extract – XML................................................................................................................. 20
Rules and Examples....................................................................................................................................21
Parameters...................................................................................................................................................21
XML file example..........................................................................................................................................23
Process – PL/SQL API...................................................................................................................................24
API Signature:..............................................................................................................................................25
Installation............................................................................................................................................26
Assignment of Concurrent Programs to Request Groups........................................................................26
Localization and Global Descriptive Flexfields...........................................................................................26
Forms Personalization..................................................................................................................................30

Page 2 of 35
Introduction

As per Hungarian regulations, businesses issuing B2B sales invoices by means of an invoicing software will be
required to provide real time invoice data to the Hungarian Tax Authorities (HTA). The Hungarian Real Time
Reporting must include all receivables transactions, that are with other businesses that have Hungarian tax
numbers, having a VAT amount equal to or above 100,000 HUF. This threshold can be lower if the taxpayer
decides so. The reporting obligation must be fulfilled immediately after the creation of the invoice. The invoice
is considered to be created when the invoice information in the invoicing software is “permanently closed’’.
In summary, the steps required for the Hungary Real Time Reporting specification include the following
components:
 Step 1 - Extracting Receivables transactions details
 Step 2 - Requesting a token from the Hungarian Tax Authorities (HTA) website that temporarily
authorizes the taxpayer to submit information (validity of 5 minutes)
 Step 3 - Formatting XML messages according to the prescribed format to communicate receivables
transactions to the HTA
 Step 4 - Electronically hashing messages to be sent to the HTA
 Step 5 - Sending file to HTA
 Step 6 - Managing HTA invoice validation response messages
 Step 7 - A dashboard for taxpayers to track submitted transactions to the HTA and their status
 Step 8 - API in order to upload statuses in the ERP
This solution will address steps 1 and 8. The steps related to the transmission and interaction with the tax
authority web site, that is steps 2 to 7, can be performed by partner solutions or as customer solution.

Page 3 of 35
Features

The EMEA Add-On Localization solution introduces two new concurrent programs CLE: Invoice
Data Extract – XML and CLE: Invoice Data Extract File Loader to generate and extract the XML file for
AR transactions (Invoices, CMs) and to upload the generated XML file to a specific directory. The
objective is to extract the XML file for all transactions that are final printed or are accounted and are
permanently closed.
Second part of this solution introduces a PL/SQL API, which is expected to called by the partner
or customer solution and will update Transaction with Business validation status received from Tax
Authority.

Page 4 of 35
Hungary Real Time Process flow:

Append the Token to

the XML file and First Tax Agency
Enter Invoice in Create Invoice Request Token Receive Token
electronic sign it. Validation on
ERP XML file (A) (valid 5 minutes)
Submit the file to the XML structure
Tax Agency

Log into the Online

Platform cancel the invoice Validation
Resubmit the Invoice No
Oracle EBS with errors by inserting an
Annulement (Erase) (B)
Successfully

Solution
Yes

Collecting the Update Second Tax

Query for Collecting the
status in the Validation Agency Receiving
Invoice Business results in the
Successfully transaction
Yes
ERP,no further Validation Response File
status ERP
action is needed status with Business Rules
API
No

Modification of the Modify the Invoice in

End If allowed in the ERP Back to step B B
Invoice is required the ERP

Insert a Credit Memo

as a new Invoice and
If modification of the Original Invoice is not possible Resubmit Invoice A
add the reference to
the Original Invoice

Processes done by the Tax Agency

Processes done by the Taxpayer

Page 5 of 35
Setup steps
Users will need to populate the Global Descriptive Flexfields listed below, when entering the
transactions. Mandatory Global Descriptive Flexfields / Localisations Descriptive Flexfields should also be
populated for LE, Customer Account, Payment Methods, Tax Codes, Items, Statistical Codes, Transaction
Types. Please see the details below.
The XML template will pick up information from the standard fields where the information is stored. There might
be some slight differences, in case you have a different setup such as the way the address is stored.

Reports and Processes

Pre-requisites
 Oracle E-Business Suite must be installed and running on the minimum supported Release 12.1.3 (or
higher).
 The required patches and setup must be done for Hungarian localizations
Setup requirement
1. Define LDFFs: Group Tax Registration Number, Threshold Amount and Hungary Real-Time Reporting
Start Date on Legal Entity
Legal Entity Configurator -> Query LE -> Legal Entity Details -> General -> Update -> click on CLE:
Additional Legal Entity Information link

2. Define personalization on Legal Entity. Detail steps see below in the document.

3. Define personalization on Tax Rates. Detail steps see below in the document.

4. Define Tax Codes and define LDFF VAT Rate Type on Tax Codes.
Tax Manager -> Tax Configuration -> Tax Rates -> Query Tax Rate Code -> Update -> click on CLE:
Tax Rates Additional Info

Page 6 of 35
5. Define Item Statistical Codes on Item and define LDFF ‘Product Code Type’ on Item Statistical Codes
lookup (JGZZ_STATISTICAL_CODE).
Product Code Category: Application Developer -> Application -> Lookups -> Application Object Library -
> JGZZ_STATISTICAL_CODE

Statistical code: Inventory -> Items -> Master Items -> Main -> GDF ‘Statistical Code’

Page 7 of 35
6. Define Tax Registration number only in any of the following format -> HUXXXXXXXX-Y-ZZ, HU-
XXXXXXXX-Y-ZZ, HUXXXXXXXX or XXXXXXXX-Y-ZZ for Customers. Define Group Tax Registration
on Customer.

Customer -> Tax Profile -> Tax Registration -> Default Reporting Registration Number

Customer Information -> Account -> GDF ‘Group Tax Number’

Page 8 of 35
7. For Private Individual Customers define on Customer Profiles in the field Customer Category value
Individuals.
Customer Information -> Profile -> Customer Category

8. Define GDFs for the transaction header: Payment Method, Bank Account Number, and in case of Credit
Memo define Original Invoice Number, Invoice Category, Invoice Appearance and on Lines define
values for the GDF Intermediary Service.
Transactions -> Transactions
Page 9 of 35
 Transactions -> Transactions -> Transaction Lines

9. Define LDFF Payment Method type on Receipt Method for particular Receipt Class.
Setup -> Receipts -> Receipt Classes

Transactions -> Transactions

Page 10 of 35
 10. Assign Program CLE: Invoice Data Extract – XML to Request Groups.

11. Define LDFF on Transaction Types to decide which transaction types are to be excluded.
Setup -> Transactions -> Transaction Types

Process – CLE: Invoice Data Extract – XML and CLE: Invoice Data Extract File Loader

Page 11 of 35
Conditions for XML file creation:

Not all invoices are affected by Real Time Reporting. The following must be taken into account when
selecting invoices:
1. Only AR Invoices are affected. This means purchase invoices are not exported.
- Only AR transactions are part of this solution.
2. Only domestic customers are affected; including foreign customers where on transaction Bill to Site -
> Address -> Country code is value ‘Hungary’. This means that there is no need to report EU sales
or exports.
- The CLE: Invoice Data Extract – XML is checking on transaction Bill To -> Address ->
Country code value ‘Hungary’ and is selecting only the invoices with a Bill To address
country code ‘Hungary’.
3. Only B2B invoices are affected. Supplies to private individuals do not need to be reported.
- Customers which are defined as Individuals are not selected for the XML file generation.
- Customer -> Profile -> Value Individuals
4. Only AR Invoices that have at least one line with a chargeable VAT are affected. There is no need
to report invoices that have all the lines with exempt supplies, zero-rated supplies or with reverse
charges.
- On the Tax code is LDFF ‘VAT Rate Type’ which identifies the type of VAT Code.
5. If the threshold decided by the Taxpayer is set to 0 , all AR Invoices with exempt supplies, zero-
rated supplies or with reverse charge will be reported.
6. Only invoices with VAT of more than HUF 100 000 (appr. EUR 320) are affected, as defined by
legislation limit. The threshold can be lowered as much as the taxpayer decides. There is no need
to report smaller values.
- Threshold amount can be defined by each company and the limit amount should be
defined on Legal Entity in the LDFF ‘Threshold Amount’. On Legal Entity it is also
possible to define Hungary Real-Time Reporting Start Date and the program CLE:
Invoice Data Extract – XML will extract only transactions with transaction date higher
as date defined in the LDFF.
7. If the Taxpayer decides to set the threshold to 0, it is possible to report all B2B invoices that have a
Hungarian Tax Number.
8. Transaction Types with LDFF ‘Exclude from Real Time Reporting and Data Provision Extract’ value
Yes will not be considered in the output. In case when LDFF value is Null or No the transaction type
will be included in the Data Provision Extract and also in the Real Time Reporting XML file. The
XML file should be created for Invoices, Credit Memos and Debit Memos.

A lot of fields in the XML, as per the requirement, are optional or only to be filled when related to a specific
industry. We do not provide information for those. Only tags displayed in this table are part of this solution. The
Tags which are not listed in the mapping table are not supported and are out of scope.
Some tags are mandatory and some are not. In case of mandatory tags, the user need to define all the data in
the system. In case when mandatory tags do not have data, the program will generate tags without value. In
case of non-mandatory tags the program will not display the tag in the XML file, if there is no value.

Mapping table

Tag name Tag name Type Mandatory Note/Mapping

Y/N
Invoice

Page 12 of 35
invoiceExchange
invoiceReference
originalInvoic type="SimpleText50N Y Transaction number of the original invoice, on
eNumber otBlankType" which the modification occurs

modificationI type="DateType" Y Credit Memo Transaction Date

ssueDate

modificationT type="TimestampTyp Y Creation date

imestamp e" Example: 10-MAY-2018 02:43:02

lastModificati type="SimpleText50N N Previous latest Credit Memo number

onReference otBlankType"
minOccurs="0"
modifyWithou type="xs:boolean" Y If original invoice was already reported then false
tMaster default="false" and if original invoice is not yet reported then true.
invoiceHead

supplierInfo

supplierTaxNumber Y Identifying Tax Registration Number from the Legal

Entity Registrations
Legal Entity-->Registration-->Identifying
Registration Number
The Hungarian Tax Registration Number can be
defined only in any of the following structures ->
XXXXXXXX-Y-ZZ, HUXXXXXXXX-Y-ZZ, HU-
XXXXXXXX-Y-ZZ or HUXXXXXXXX
taxpayerId type="TaxpayerIdTyp Y First 8 digit of the Hungarian VAT Registration
e" Number of the supplier. Hungarian Tax
Registration Number format is: XXXXXXXX-Y-ZZ,
this is the XXXXXXXX string
vatCode type="VatCodeType" N Single digit to indicate taxation type of the supplier
minOccurs="0" (Legal Entity) Hungarian Tax Registration Number
format is: XXXXXXXX-Y-ZZ, this is the Y string
countyCode type="CountyCodeTy N Hungarian Tax Registration Number format is:
pe" minOccurs="0" XXXXXXXX-Y-ZZ, this is the ZZ string

groupMemberTaxNu type="TaxNumberTyp N Tax group member number, when the purchase of

mber e" minOccurs="0" goods or services is done under group
identification number.
LDFF on Legal Entity -> CLE: Additional Info On
Legal Entity Profiles -> Group Tax Registration
Number
The Number should be defined only in any of the
following structures -> XXXXXXXX-Y-ZZ,
HUXXXXXXXX-Y-ZZ, HU-XXXXXXXX-Y-ZZ or
HUXXXXXXXX
taxpayerId type="TaxpayerIdTyp Y Value of ‘XXXXXXXX’
e"

vatCode type="VatCodeType" N Value of ‘Y’

minOccurs="0"
countyCode type="CountyCodeTy N Value of ‘ZZ’
pe" minOccurs="0"
communityVatNumbe type="CommunityVat N Prefix the Tax Registration Number(TRN) -> "HU"
r NumberType" prefix+8 chars (XXXXXXXX) from Tax Reg.
minOccurs="0" Number
supplierName type="SimpleText512 Y Legal Entity name
NotBlankType"

supplierAddress Y

simpleAddress This solution provides only the tags for simple

addresses. Detailed address tags are out of
scope.
countryCode type="CountryCodeT Y Constant value = HU
ype" default="HU"
Page 13 of 35
 postalCode type="PostalCodeTyp Y Postal Code - POSTAL_CODE’ attribute in
e" ‘Location Address’ .Detail is retrieved from
Address assigned to ‘Identifying’ Legal Entity
registration.

city type="SimpleText255 Y City - ‘TOWN_OR_CITY’ attribute in ‘Location

NotBlankType" Address’ .Detail is retrieved from Address
assigned to ‘Identifying’ Legal Entity registration.

additionalAdd type="SimpleText255 Y The detail additionalAddressDetail tag reports

ressDetail NotBlankType" Address fields:
address_line_1
address_line_2
address_line_3
Building - loc_information14
Stairway - loc_information15
Floor Table - loc_information16
Door - loc_information17

supplierBankAccount type="BankAccountN N Bank account number of the supplier in Hungarian

Number umberType" format.8 digit-8digit-8digit format. The Bank
minOccurs="0" Account number must be defined in required
Hungarian format.
Transaction -> Header -> GDF ‘Bank Account
Number’
customerInfo
customerTaxNumber type="TaxNumberTyp N Customer’s tax number
e" minOccurs="0" Customer -> Tax Profile -> Tax Registration ->
Default Reporting Registration Number
or when field is empty displayed is Default
Reporting Registration Number from Account Site
level.
The Hungarian Tax Registration Number can be
defined only in any of the following structures ->
XXXXXXXX-Y-ZZ, HUXXXXXXXX-Y-ZZ, HU-
XXXXXXXX-Y-ZZ or HUXXXXXXXX
taxpayerId type="TaxpayerIdTyp Y First 8 digit of the Hungarian VAT Registration
e" Number of the supplier. Hungarian Tax
Registration Number format is: XXXXXXXX-Y-ZZ,
this is the XXXXXXXX string
vatCode type="VatCodeType" N Single digit to indicate taxation type of the supplier
minOccurs="0" (Legal Entity) Hungarian Tax Registration Number
format is: XXXXXXXX-Y-ZZ, this is the Y string
countyCode type="CountyCodeTy N Hungarian Tax Registration Number format is:
pe" minOccurs="0" XXXXXXXX-Y-ZZ, this is the ZZ string
groupMemberTaxNu Group Tax Registration Number
mber Customer Information -> Account -> GDF ‘Group
Tax Number’
The Hungarian Tax Registration Number can be
defined only in any of the following structures ->
XXXXXXXX-Y-ZZ, HUXXXXXXXX-Y-ZZ, HU-
XXXXXXXX-Y-ZZ or HUXXXXXXXX
taxpayerId type="TaxpayerIdTyp N First 8 digit of the Hungarian VAT Registration
e" Number of the supplier. Hungarian Tax
Registration Number format is: XXXXXXXX-Y-ZZ,
this is the XXXXXXXX string
vatCode type="VatCodeType" N Single digit to indicate taxation type of the supplier
minOccurs="0" (Legal Entity) Hungarian Tax Registration Number
format is: XXXXXXXX-Y-ZZ, this is the Y string
countyCode type="CountyCodeTy N Hungarian Tax Registration Number format is:
pe" minOccurs="0" XXXXXXXX-Y-ZZ, this is the ZZ string
communityVatNumbe type="CommunityVat N Prefix the Tax Registration Number(TRN) -> "HU"
r NumberType" prefix+8 chars (XXXXXXXX) from Tax Reg.
Number
customerName type="SimpleText512 Y Name of Customer
NotBlankType"
customerAddress

Page 14 of 35
simpleAddress In this solution only tags for simple addresses are
provided. Detailed address tags are out of scope.
countryCode type="CountryCodeT Y Constant value = HU
ype" default="HU"
postalCode type="PostalCodeTyp Y Postal Code from customer’s site.
e" Customer Information -> Account Sites -> Site
Details -> Postal Code
city type="SimpleText255 Y City from customer’s site.
NotBlankType" Customer Information -> Account Sites -> Site
Details -> City
additionalAdd type="SimpleText255 Y Additional address details from customer’s site.
ressDetail NotBlankType" Customer Information -> Account Sites -> Site
Details ->

The detail additionalAddressDetail tag reports

Address fields:
address_line_1
address_line_2
address_line_3
Building - loc_information14
Stairway - loc_information15
Floor Table - loc_information16
Door - loc_information17

invoiceData

invoiceNumber type="SimpleText50N Y Transaction Number

otBlankType" Transactions -> Transaction Header ->
Transaction Number
invoiceCategory type="InvoiceCategor Y Invoice Category -> constant value NORMAL.
yType" Solution for Simplified and Aggregated invoices
minOccurs="0" are out of scope.
Transactions -> Transaction Header -> GDF
‘JG_RA_CUSTOMER_TRX’ and segment Invoice
Category
invoiceIssueDate type="DateType" N Transaction Date
minOccurs="0" Transactions -> Transaction Header -> Date
invoiceDeliveryDate type="DateType" N Tax Invoice Date
minOccurs="0" Transactions -> Lines Item -> Tax Information ->
Tax Invoice Date
invoiceAccountingDe type="DateType" N GL Date
liveryDate minOccurs="0" Transactions -> Transaction Header -> GL Date

currencyCode type="CurrencyType" N Currency

minOccurs="0" Transactions -> Transaction Header -> Currency
default="HUF"
exchangeRate type="ExchangeRate N Exchange Rate
Type" minOccurs="0" Transactions -> Tools -> Exchange Rate -> Rate
paymentMethod type="PaymentMetho N Payment Method values ->
dType" TRANSFER
minOccurs="0" CASH
CARD
VOUCHER
OTHER

The ‘Payment Method Type’ is defined in the

LDFF ‘CLE: Additional Info On Receipt Methods’ -
> segment ‘Payment Method Type’ and Payment
Method’ is defined in the GDF ‘Payment Method’
on Transaction Header

Transactions -> Transaction Header -> GDF

‘JG_RA_CUSTOMER_TRX’ and segment
‘Payment Method’

Setup -> Receipts -> Receipt Class -> Receipt

Method -> Actions -> CLE: Additional Info On
Receipt Methods -> Payment Method Type

Page 15 of 35
paymentDate type="DateType" N Due Date
minOccurs="0" Transactions -> Transaction Header -> Due Date

invoiceAppearance type="InvoiceAppeara Y Invoice Appearance values:

nceType" PAPER
ELECTRONIC
EDI
UNKNOWN

Transactions -> Transaction Header -> GDF

‘JG_RA_CUSTOMER_TRX’ and segment ‘Invoice
Appearance’

additionalInvoiceData N These are not mandatory tags but for

communication with customer’s /partner’s solution,
these are important tags.

Based on Transaction ID partners and customers

can use this API to update invoice validation
status.

Operation ‘CREATE’ is provided for new

transactions like Invoice, Prepayment Invoice, DM
and CMs without link to original invoice.

Operation ‘MODIFY’ is provided for partially Credit

Memos with link to original Invoice -> -> GDF
‘Original Invoice Number’ on Transaction Header
or ‘Original Transaction Number’ on Transaction
Header -> Reference Information

Operation ‘STORNO’ is provided for full Credit

Memos with link to original Invoice -> -> GDF
‘Original Invoice Number’ on Transaction Header
or ‘Original Transaction Number’ on Transaction
Header -> Reference Information

Operation name CREATE, MODIFY or STORNO

is provided in the dataName or dataValue tags.

Transaction is provided in the dataName and

dataDescription tag.

dataName type="DataNameTyp Y dataName structure->

e"
Example:
<dataName>C00000_827166663871CREATE</d
ataName>

C=Create, M=Modify and S=Storno

00000 = Constant value
_
827166663871 = Transaction ID
CREATE = Operation. (Values = CREATE,
MODIFY or STORNO)

dataDescripti type="SimpleText255 Y dataDescription = Transaction ID

on NotBlankType" Example:
<dataDescription>827166663871</dataDescriptio
n>

dataValue type="SimpleText255 Y dataValue = Operation -> CREATE, MODIFY or

NotBlankType" STORNO
Example:
<dataValue>CREATE</dataValue>

invoiceLines

Page 16 of 35
line
lineNumber type="LineNumberTy Y Sequential number of the line
pe"
lineModificationRefer N
ence

lineNumberReference type="LineNumberTy Y Line number of the original invoice, where the

pe" modification occurs, in case of ‘create’ operation
the tag shall contain the new line number, as a
sequential increment of the original invoice
Example:
Invoice1
Line 1
Line 2
Line 3
Credit Memo1 referring to Invoice1
Line 1 -> Line reference number 4
Line 2 -> Line reference number 5
Line 3 -> Line reference number 6
lineOperation type="LineOperationT Y Because transactions are Final Printed or
ype" Accounted and cannot be modified lineOperation
is constant value ‘CREATE’

advanceIndicator type="xs:boolean" N
minOccurs="0" Constant value ‘false’
default="false"

productCodes N
productCode Product code tags are displayed in the XML file
only in case when Item is defined on the line.

In case when Item is not defined and only

description is provided the product code tags are
not displayed.

productCode type="ProductCodeC Y Product Code Category is defined in the LDFF

Category ategoryType" ‘Product Code Type’ for the Lookup values
JGZZ_STATISTICAL_CODE
Application Developer -> Application -> Lookups -
> Application Object Library ->
JGZZ_STATISTICAL_CODE

Statistical code is assigned to the Item in the GDF

‘Statistical Code’.
Inventory -> Items -> Master Items -> Main ->
GDF ‘Statistical Code’

Product Code Category values:

VTSZ
SZJ
KN
AHK
CSK
KT
EJ
OWN
OTHER

productCode type="ProductCodeV Y Item (Item Number)

Value alueType"
productCodeValue tag is displayed in case when
Product Code Category are values
VTSZ
SZJ
KN

Page 17 of 35
 AHK
CSK
KT
EJ
OTHER

Transactions -> Line Items -> Item

productCode type="SimpleText50N Y Item (Item Number) for own products

OwnValue otBlankType"
minOccurs="0" Tag productCodeOwnValue is displayed in case
when product code category is OWN.

Transactions -> Line Items -> Item

lineDescription type="SimpleText255 N Line description
NotBlankType"
minOccurs="0" Transactions -> Line Items -> Description
quantity type="QuantityType" N Quantity
minOccurs="0"
Transactions -> Line Items -> Quantity
unitOfMeasure type="SimpleText50N N Unit of measure
otBlankType"
minOccurs="0" Transactions -> Line Items -> Unit of measure
unitPrice type="QuantityType" N Unit price
minOccurs="0"
Transactions -> Line Items -> Unit price
lineAmountsNormal
lineNetAmount type="MonetaryType" Y Invoice line Net amount in the currency of the
invoice

Transactions -> Line Items -> Amount

lineVatRate Y VAT Rate type is defined on Tax Code in the
LDFF ‘VAT Rate Type’

VAT Rate Type values:

VATPERCENTAGE
VATEXEMPTION
VATOUTOFSCOPE
VATDOMESTICREVERSECHARGE
MARGINSCHEMEVAT
MARGINSCHEMENOVAT
NR – not reportable.

vatPercentag type="RateType" Y Normal tax rates

e
Tag vatPercentage is displayed when LDFF value
on tax code is:
VATPERCENTAGE
Null
value NR and on transaction are lines with tax
codes which should be reported in the XML file

<vatPercentage>0.27</vatPercentage>

vatExemption type="SimpleText50N Y Exempt tax rates

otBlankType"
Tag vatExemption is displayed when LDFF value
on tax code is VATEXEMPTION.
And the tag displays the value form Tax Code
LDFF ‘Tax Exempt Reason’
<vatExemption>Exempt reason </vatExemption>

vatOutOfSco type="xs:boolean" Y Non subject of VAT

pe default="false"
Tag vatOutOfScope is displayed when LDFF
value on tax code is VATOUTOFSCOPE or
in case when the transaction line is without tax

Page 18 of 35
 <vatOutOfScope>true </vatOutOfScope>

vatDomestic type="xs:boolean" Y Domestic reverse charge

ReverseChar default="false"
ge Tag vatDomesticReverseCharge is displayed
when LDFF on tax code is
VATDOMESTICREVERSECHARGE

<vatDomesticReverseCharge>true
</vatDomesticReverseCharge>

marginSchem type="xs:boolean" Y Margin Scheme VAT

eVat default="false"
Tag marginSchemeVat is displayed when LDFF
on Tax Code is MARGINSCHEMEVAT

marginSchem type="xs:boolean" Y Margin scheme no VAT

eNoVat default="false"
Tag marginSchemeNoVat is displayed when
LDFF on Tax Code is MARGINSCHEMENOVAT

lineVatAmount type="MonetaryType" N VAT Amount in the currency of the invoice

minOccurs="0"

lineVatAmountHUF type="MonetaryType" N VAT Amount in HUF

minOccurs="0"

lineGrossAmountNor type="MonetaryType" N Gross Amount in in the currency of the invoice

mal minOccurs="0"

intermediatedService type="xs:boolean" Y Intermediated Service

minOccurs="0"
default="false" Value id displayed from GDF ‘Intermediary
Service’ on transaction line

Transactions -> Line Items -> GDF

‘JG_RA_CUSTOMER_TRX_LINES’ segment
‘Intermediary Service’

additionalLineData N Additional line data tags are not displayed.

dataName type="DataNameTyp Y
e"
dataDescripti type="SimpleText255 Y
on NotBlankType"

dataValue type="SimpleText255 y
NotBlankType"
invoiceSummary

summaryNormal

summaryByVatRate N

vatRate Y Summary according to VAT rates

vatPercentag type="RateType" Y Summary according to VAT rate type

e VATPERCENTAGE

vatExemption type="SimpleText50N Y Summary according to VAT rate type

otBlankType" VATEXEMPTION

Page 19 of 35
 vatOutOfSco type="xs:boolean" Y Summary according to VAT rate type
pe default="false" VATOUTOFSCOPE

vatDomestic type="xs:boolean" Y Summary according to VAT rate type

ReverseChar default="false" VATDOMESTICREVERSECHARGE
ge
marginSchem type="xs:boolean" Y Summary according to VAT rate type
eVat default="false" MARGINSCHEMEVAT

marginSchem type="xs:boolean" Y Summary according to VAT rate type

eNoVat default="false" MARGINSCHEMENOVAT

vatRateNetAmount type="MonetaryType" Y The net amount for a given tax rate in the currency
of the invoice
vatRateVatAmount type="MonetaryType" Y The VAT amount for a given tax rate in the
currency of the invoice
vatRateVatAmountHU type="MonetaryType" Y The VAT amount for a given tax rate in HUF
F minOccurs="0"

vatRateGrossAmount type="MonetaryType" N The Gross amount for a given tax rate in the
minOccurs="0" currency of the invoice

invoiceNetAmount type="MonetaryType" Y Net amount of the invoice in the currency of the

invoice.
invoiceVatAmount type="MonetaryType" Y VAT amount of the invoice in the currency of the
invoice.
invoiceVatAmountHU type="MonetaryType" Y VAT amount of the invoice in the currency HUF
F

invoiceGrossAmount type="MonetaryType" N Gross amount in the currency of the invoice

minOccurs="0"

CLE: Invoice Data Extract – XML

Customers will run the concurrent program called” CLE: Invoice Data Extract - XML”, which produces the XML
file required to submit to the Tax Authority. Please see the parameters below.
This program will automatically submit ‘CLE: Invoice Data Extract File Loader’ which will upload the file to a
specific location in the file system, $APPLTMP/HU_REALTIME/’Date’ in the format YYYY-MM-DD. For each
invoices selected in the above program the separate XML file is generated.
File name convention is LegalEntityId-RequestId-InvoiceId.xml
Example: 3966-6554543-1063104.xml

Rules and Examples

1. The XML File will be generated for Transactions where GDF ‘Invoice Validation Result Code’ on
transaction header is NULL and transaction is PRINTED or ACCOUNTED and transaction cannot be
modified. For Re-extract, the parameter Value should be set to ‘Yes’ and on the transaction header the
GDF ‘Invoice Validation Result Code’ value is ‘WARN’ or ‘ERROR’ and the GDF ‘Re-extract Invoice
XML’ is set to ‘Yes’.
2. The XML File will be generated only for domestic and foreign customers where on transaction Bill to
Site -> Address -> Country code is value ‘Hungary’. The CLE: Invoice Data Extract – XML is checking
on transaction Bill To -> Address -> Country code value ‘Hungary’ and is selecting only the invoices with
a Bill To address country code ‘Hungary’.

Page 20 of 35
 3. The XML File will be generated only for the AR Invoices that have at least one line with chargeable
VAT. There is no need to report invoices that have all the lines with exempt supplies, zero-rated
supplies or with reverse charges.
4. The XML File will be generated only for the invoices with VAT more than the HUF amount defined on
Legal Entity, in the LDFF segment ‘Threshold Amount’.
5. The XML File will be generated only for B2B invoices. Supplies to private individuals do not need to be
reported.
6. The XML file will not be generated for transactions with tax code defined with LDFF VAT Rate type ‘NR’
(Non Reportable).
7. The XML file will not be generated for transactions with ‘Invoice Validation Result Code’ set to
‘Extracted’.
8. The XML file will not be generated for transactions with a date earlier than the LDFF ‘Hungary Real-
Time Reporting Start Date defined on Legal Entity.
9. The XML file will be generated for all transaction types with LDFF ‘Exclude from Real Time Reporting
and Data Provision Extract’ value null or No.
10. Adjustment transactions on Invoices will not effect and change the original transaction line amounts Net
Amount, VAT and Gross amount.

Parameters

Parameter Required Default LOV

Value

Legal Entity Yes NULL List of Legal Entities the user has access to.
Transaction Date No NULL Beginning of the date range to provide
From transactions for
Transaction Date To No NULL Ending of the date range to provide transactions
for
Transaction Number No NULL Beginning of the numbers range to provide
From transactions for.
The LOV displays:
 Transaction Number
 Transaction Type
 Transaction Source
Transaction Number No NULL Ending of the numbers range to provide
To transactions for.
The LOV displays:
 Transaction Number
 Transaction Type
 Transaction Source
Re-Extraction No NULL Value ‘Yes’ indicates to Re-extract the invoices,
using different request numbers, for the
transactions with a GDF ‘Invoice Validation Result
Code’ value ‘WARN’ or ‘ERROR’ and the GDF ‘Re-
extraction Invoice XML’ is set to ‘Yes’.

Page 21 of 35
XML file example

Page 22 of 35
Process – PL/SQL API

As part of the Oracle EBS solution, we will be providing a PL/SQL API that will be called by the partner
or custom solutions, when they receive the Business validation results back from Tax Authorities. This API can
be called in order to update the invoice validation status with either ‘OK’, ‘WARN’ or ‘ERROR’ at the Invoice
header level in the Global Descriptive flexfield “JG_RA_CUSTOMER_TRX”.
Partners and Customers can use this API along with the extraction of Receivables transactions details in order
to integrate their solutions in EBS with the other Real time reporting steps like requesting Token, electronically
hashing messages and manage Tax Authority invoice validation response messages.
This status update in the ERP system is required in order to extract the receivables transactions. Partners and
Customers can also query the receivables transactions from the application by providing the required status
value in the GDF.

GDF Title: JG_RA_CUSTOMER_TRX

Table Name: RA_CUSTOMER_TRX_ALL
Application: Regional Localizations.
Cotext Code: JE.HU.ARXTWMAI.BANK_INFO
Segment Name: INVOICE_VAL_RES_CODE
API will be updating the following Segment (GLOBAL_ATTRIBUTE8 ) in the GDF columns of the Receivables
Transactions table “RA_CUSTOMER_TRX_ALL”.
GLOBAL_ATTRIBUTE8 – Invoice Validation Result Code

Invoice Validation
Result Code

OK

WARN

ERROR

 API will not update any status related to submission of transactions to the Hungarian Tax Authorities
and it will also not update any Invoice return error codes & messages from the HTA if any received by
Partners or customers.
 The Function will return a status for the API call indicating the status of the update.

Page 23 of 35
API Signature:
The API consists of the following attributes:
1. Invoice ID - This is the unique identifier of the invoice to update.
2. Invoice Validation Result Code -- This is the invoice status with either OK, WARN or ERROR.

The API signature mentioned below is a FUNCTION and it returns appropriate text message on the invoice
status updated.

CLE_F510_INVDEXML_PKG.invoice_status_update
( invoice_id IN NUMBER,
inv_val_res_code IN VARCHAR2 ) RETURN VARCHAR2;

Page 24 of 35
Installation
Assignment of Concurrent Programs to Request Groups
Request Group setup provides access to the Concurrent Program/Concurrent Program Set to the user
responsibilities. Assign the following program/set to the request group attached to the responsibility from which
you want to access the functionality.

Reports
Serial Number Program Name

1 CLE: Invoice Data EMEA Add-on CLEF510INVDATAEXT

Extract - XML Localizations

Localization and Global Descriptive Flexfields

Application Regional Localizations

Flexfield Name JG_HZ_CUST_ACCOUNTS
JE.HU.ARXCUDCI.CUSTOMER
Context _INFO

Segmen Segment Name Segment Valueset Description Note

t# Column
Segment1 CLE_GROUP_TAX_NUM GLOBAL_ATTRIBU Group Tax Number
BER TE1

Application Regional Localizations

Flexfield Name JG_RA_CUSTOMER_TRX_LINES
Context JE.HU.ARXTWMAI.REGISTER_INFO

Segmen Segment Name Segment Valueset Description Note

t# Column
Segment1 CLE_INTRMDRY_SERVI GLOBAL_ATTRIBU Yes_No Intermediary
CE TE1 Service

Application Regional Localizations

Flexfield Name JG_RA_CUSTOMER_TRX
JE.HU.ARXTWMAI.BANK_INF
Context O

Segme Segment Segment Valueset Description Note

nt # Name Column
Segment Payment_Met GLOBAL_AT CLE_F275_Paymen Invoice Print Program derives payment LDFF on
Page 25 of 35
 1 hod TRIBUTE1 t_Method method information from here (Bank Receipt
Transfer, Cash, Voucher etc.) Method =
paymentMet
hod
Segment Bank_Account GLOBAL_AT CLE_F275_Bank_A Invoice Print Program use this bank Tag =
2 _Number TRIBUTE2 ccount account as remit to bank account. supplierBan
kAccountNu
mber
Segment Original GLOBAL_AT CLE_F280_DRS_A This field to be used in case of standalone Tag =
3 Invoice TRIBUTE3 R_TXNS Corrective Invoices only (invoice type 40) originalInvoi
Number to identify the original transaction being ceNumber
adjusted/corrected.
Segment Payment GLOBAL_AT CLE_F510_PAYME This field is used to indicate if the invoice is
4 Option TRIBUTE4 NT_OPTION issued for a prepayment received from
customer (value: 1) or representing a final
invoice (value: 2) prepayment is applied
against.
Segment CLE_F510_IN GLOBAL_AT CLE_F510_INVOIC Pre-defined lookup codes identifying the tag =
5 VOICE_CATE TRIBUTE5 E_CATEGORY tax invoice type being reported. invoiceCate
GORY Following values will be supported: gory
- NORMAL - Normal invoice

Segment CLE_F510_IN GLOBAL_AT CLE_F510_INVOIC Predefined lookup codes identyfing the tag =
6 VOICE_APPE TRIBUTE6 E_APPEARANCE physical appearance of the invoice invoiceAppe
ARANCE document: arance
- PAPER - Paper invoice
- ELECTRONIC - Electronic, non-EDI
invoice
- EDI - Electronic, EDI invoice
- UNKNOWN - The software is unable to
identify the type of invoice, or the type is
i=unknown at the time the invoice was
issued.
Segment CLE_F510_IN GLOBAL_AT CLE_F510_INVOIC This field is used to control the submission
8 VOICE_VAL_ TRIBUTE8 E_VAL_RES_COD status to tax authority:
RES_CODE E - EXTRACTED : XML extract has been
generated
-OK
-WARN
-ERROR
Segment CLE_F510_IN GLOBAL_AT Yes_No Values:
9 VOICE_REEX TRIBUTE9 -Yes
TRACTION -No

Value Sets
Lookup Value Description EN Start Lookup Note
Date
CLE_F510_INVOICE_APP PAPER Invoice issued on 1.1.10 CLE_F510_INVOICE_APPE
EARANCE paper ARANCE
CLE_F510_INVOICE_APP ELECTRONIC Electronic invoice 1.1.10 CLE_F510_INVOICE_APPE
EARANCE (not EDI) ARANCE
CLE_F510_INVOICE_APP EDI EDI invoice 1.1.10 CLE_F510_INVOICE_APPE
EARANCE ARANCE
CLE_F510_INVOICE_APP UNKNOWN The software 1.1.10 CLE_F510_INVOICE_APPE
EARANCE cannot be identify ARANCE
the form of
appearance of the
invoice
CLE_F510_INVOICE_VAL EXTRACTED Extracted 1.1.10 CLE_F510_INVOICE_VAL_
_RES_CODE RES_CODE
CLE_F510_INVOICE_VAL OK OK 1.1.10 CLE_F510_INVOICE_VAL_
_RES_CODE RES_CODE
CLE_F510_INVOICE_VAL WARN Warning 1.1.10 CLE_F510_INVOICE_VAL_
Page 26 of 35
_RES_CODE RES_CODE
CLE_F510_INVOICE_VAL ERROR Error 1.1.10 CLE_F510_INVOICE_VAL_
_RES_CODE RES_CODE
CLE_F510_INVOICE_CAT NORMAL Normal invoice 1.1.10 CLE_F510_INVOICE_CATE
EGORY GORY

Application EMEA Add-on Localizations

Flexfield Name CLE: Additional Info On Receipt Methods
Context HU

Segment Segment Segment Valueset Description Note

# Name Column
Segment1 CLE_F510_ ATTRIBUTE CLE_F510_PAYMEN Payment Method Type for Tag =
PAYMENT_ 1 T_METHOD_TYPE Online Invoice XML file paymentMethod
METHOD_T
YPE
Lookup Values
Start
Lookup Value Description EN Date Note
TRANSFE
CLE_F510_PAYMENT_METHOD_TYPE R Bank transfer 1.1.10
CLE_F510_PAYMENT_METHOD_TYPE CASH Cash payment 1.1.10
CLE_F510_PAYMENT_METHOD_TYPE CARD Debit card 1.1.10
CLE_F510_PAYMENT_METHOD_TYPE VOUCHER Voucher 1.1.10
CLE_F510_PAYMENT_METHOD_TYPE OTHER Other 1.1.10

Application EMEA Add-on Localizations

Flexfield Name CLE: Additional Info On Lookup Values
Context HU

Segmen Segment Name Segment Valueset Description Note

t# Column
Segment1 CLE_F510_PRODU ATTRIBUTE CLE_F510_PRODUCT_CODE Segment1 Tag =
CT_CODE_TYPE 1 _TYPE productCodeCategor
y
Lookup Values
Lookup Value Description EN Start Note
Date
CLE_F510_PRODUCT_CODE_TY VTSZ Customs tariff number 1.1.10
PE
CLE_F510_PRODUCT_CODE_TY SZJ Business service list number 1.1.10
PE
CLE_F510_PRODUCT_CODE_TY KN KN code (Combined 1.1.10
PE Nomenclature, 2658/87/ECC
Annex I
CLE_F510_PRODUCT_CODE_TY AHK AHK number of e-TKO 1.1.10
PE defined in the Act LXVIII of
2016 on Excise Duties
CLE_F510_PRODUCT_CODE_TY CSK Packaging product catalogue 1.1.10
PE code of the product
according to the Title A) in
the Schedule No.1 of the
Government Decree No.
343/2011.
CLE_F510_PRODUCT_CODE_TY KT Environmental protection 1.1.10

Page 27 of 35
PE product code of the product
according to the Title B) in
the Schedule No.1 of the
Government Decree No.
343/2011.
CLE_F510_PRODUCT_CODE_TY EJ Classification of Inventory of 1.1.10
PE Construction
CLE_F510_PRODUCT_CODE_TY OWN The own product code of the 1.1.10
PE enterprise
CLE_F510_PRODUCT_CODE_TY OTHER Other product code 1.1.10
PE

Application EMEA Add-on Localizations

Flexfield Name CLE: Additional Info On Legal Entity Profiles
Context HU

Segmen Segment Name Segmen Valueset Description Note

t# t
Column
Segment1 CLE_GRP_TAX_REGN_N ATTRIBUT 20 Characters Group Tax groupMemberTaxNumbe
UM E2 Registration Number r -> taxpayerId, vatCode,
countyCode
Segment2 CLE_THRESHOLD_AMO ATTRIBUT FND_NUMBER Threshold Amount
UNT E3
Segment3 CLE_REALTIME_START_ ATTRIBUT FND_STANDARD_D Hungary Real-Time
DATE E4 ATE Reporting Start Date

Application EMEA Add-on Localizations

Flexfield Name CLE: Additional Info On ZX Tax Rates
Context HU

Segmen Segment Name Segment Valueset Description Note

t# Column
Segment1 CLE_F510_VAT_R ATTRIBUTE CLE_HU_VAT_RATE_T Vat rate Type lineVatRate ->
ATE_TYPE 3 YPE vatPercentage,
vatExemption,
vatOutOfScope,
vatDomesticReverseChar
ge,
marginSchemeNoVat,

Lookup
Lookup Value Description EN Start Date Note
CLE_HU_VAT_RATE_ vatPercentage Applied tax rate - 1.1.17
TYPE section 169 (j) of the
VAT law
CLE_HU_VAT_RATE_ vatExemption Marking tax exemption - 1.1.17
TYPE section 169 (m) of the
VAT law
CLE_HU_VAT_RATE_ vatOutOfScope Out of scope of the 1.1.17
TYPE VAT law
CLE_HU_VAT_RATE_ vatDomesticReverse Marking the national is 1.1.17
Page 28 of 35
 TYPE Charge reverse charge taxation -
section 142 of the VAT
law
CLE_HU_VAT_RATE_ marginSchemeVat Margin scheme 1.1.17
TYPE including input tax
CLE_HU_VAT_RATE_ marginSchemeNoVa Margin scheme not 1.1.17
TYPE t including input tax
CLE_HU_VAT_RATE_ NR Will not be included in 1.1.17
TYPE Online Invoice
Submission

Application EMEA Add-on Localizations

Flexfield Name CLE: Additional Info On Transaction Type
Context HU

Segmen Segment Name Segment Valueset Description

t# Column
Segment1 CLE_F510_EXCLUDE_TXN_TY ATTRIBUTE1 Yes_No Exclude from Real Time Reporting and
PE Data Provision Extract

Forms Personalization

1. Define Personalization on Legal Entity

Navigation:
Legal Entity Manager -> Legal Entity Configurator -> Legal Entities -> Search Country and Legal Entity
1.Click on UPDATE

2.Click on Personalize "Identification Information"

Page 29 of 35
3.Click On Create Item (corresponding to Identification Information)

4. Fill the values as shown below

Page 30 of 35
Change the Item Style to Static Styled Text,
Fill the following as given
ID: AddLegalDetails
Comments: Additional Legal Entity Information
Data Type: Varchar2
Destination URI:
OA.jsp?OAFunc=CLE_F220_PG&pExtendedPage=/oracle/apps/xle/legalsystem/legalentity/webui/LegalEntityD
etailsPG&pLegalEntityId={@LegalEntityId}&pEntityPartyId={@PartyId}&retainAM=Y&pExtendedTable=CLE_X

Page 31 of 35
LE_ENT_PRFLS_EXT&pConnectString=DFF_ID1={@LegalEntityId}&pCountry=COUNTRY=fnd_profile.value('
JGZZ_COUNTRY_CODE')
Prompt: CLE Additional Legal Entity Information
View Instance: GeneralUpdateVO
Click On apply Button and navigate to the Update legal entity screen.
Note: Please ensure you copy Destination URI text in a notepad , make sure there no spaces in between and
copy the text.

Select Context HU

2. Define personalization on Tax Rates

The following Personalization setup is needed for the CLE: Invoice Data Extract – XML. The setup
steps for personalization of ZX Rates OAF page are as follows:

Navigation Path:
Tax Manager -> Tax Configuration -> Tax Rates
a) Query for the Tax Rates:

Page 32 of 35
b) Click on the Tax Rate Code for which personalization is required:

c) Click on the Personalize Rate Period:

Page 33 of 35
 d) Click on the Create Item:

e) Enter the following fields: Item Style: Static Styled Text ID: CLEVAT
Destination URL:
OA.jsp?OAFunc=CLE_F220_PG&pExtendedPage=/oracle/apps/zx/taxcontent/regime/webui/ZxTaxRatesView
PG&retainAM=Y&pExtendedTable=CLE_ZX_RATES_B_EXT&pConnectString=DFF_ID1={@TaxRateId}&pCo
untry=COUNTRY=fnd_profile.value('JGZZ_ COUNTRY_CODE')

Prompt : CLE: Additional Information

View Instance : MaintainRatesVO

f) Click on the Apply button.

Note:Territory is a profile name, which will be set to the territory code.

Page 34 of 35