SAFT Functionality For Portugal

EMEA Add-On Localization for Portugal
SAFT Extract File & Invoice Printing
Author: Saurabh Sanklecha

Creation Date: 29-MAR-2019
Last Updated: 28-APR-2019 Document
Ref:
Version: 1.1
Organization: Oracle India Private Limited.
Page 1
Document Control
Change Record
5
7
Date Author Version Change Reference
29-MAR-19 Saurabh 1.0 Initial document

Sanklecha
28-APR-19 Saurabh 1.1 Final Review
Sanklecha
Reviewers
Name Position
Pawan Panwar Manager, Product Support
Sumit Dhariwal Team Lead
Audience
Name Position
12.1 & Above Product Support Team External
12.1 & Above Customers External
Contents
Document Control ......................................................................................... 2
1. Installations ......................................................................................... 4
2. Introduction ......................................................................................... 4
3. Legal Requirement .............................. Error! Bookmark not defined.
4. Overview of SAFT Functionality in Oracle ... Error! Bookmark not defined.
4.1 Prerequisites ....................................................................................... 6
4.2 Assumptions ....................................................................................... 7
4.3 Mandatory Setups .............................................................................. 9
4.4 Transaction Flow .............................................................................. 20
4.5 Report Submission and Parameters ........................................... 23
4.6 File Structure and Reporting Levels ........................................... 26
4.7 Report Output Analysis .................................................................. 28
4.8 Important Notes with regard to SAFT-PT Functionality ......... 59
5. Invoice Printing for Portugal Invoices ........................................ 60
6. References ......................................................................................... 61
EMEA Add On- Technical Brief for Portugal

3
1. Installations
These Add-On Localization Features are installed after the base install of Oracle E-Business Suite.
Following is the step by step process for installation of EMEA Add on - Portugal Localizations:
I) The Portugal Add-On Localization mandatory patches are available for download from MOS (R12
EMEA Add-on Localizations - Portugal (Doc ID 473622.1)). Please ensure the prerequisites are followed
before installing the patch, especially the product splicing for CLE (EMEA Consulting Localizations). For
any CLE patch, the pre-requisite patch creates and installs the product EMEA Consulting Localizations.
This process is called product splicing. In the readme for this splicing patch, detailed instructions are
given for splicing. Once the patches are installed, please ensure that the Post-installation steps are
completed.
II) Once the Patchset for Portugal Add-on Localizations are applied, go to the SAFT Extract File &
Invoice Printing section of the same Note ID and the latest patches mentioned for these features are to
be applied. These patches creates the Localization Descriptive Flexfields (LDFFs) definitions for users to
store additional information required for those features. The details are specified in the Readme of each
Add-On Localizations Feature Patch.
III) After that, follow the steps in the 'Portugal Add-On Localization Installation Manual' (Download
Installation Instructions Document from Section: Portugal Add-on Localizations - Complete Set on the
same Note ID) to enable the Localization Descriptive Flexfields. These installation steps are required to
invoke Localization Descriptive Flexfield from the additional Menu extension on the related application
forms/ pages.
IV) Once above Installation steps are completed, the setups explained in 'General Setups' section of
this Document are to be completed to enable the specific segments that capture the additional
information. It is necessary to provide the additional information for these Localization Descriptive
Flexfield segments either as a setup prerequisite or during the transaction entry depending on where
this additional information is required.
2. Introduction
This Technical Brief provides detailed information about the SAFT Functionality for Portugal in Oracle,
mandatory setups, transaction flow and process to generate the XML Output.

4
3. Legal Requirement for SAFT-PT
SAFT-PT(Standard Audit File for Tax Purposes) is the adoption to the Portuguese law of a directive from
OCDE and is applied to all information register after January 1st 2008. The details of SAFT-PT were first
described in Portuguese law n. º 321-A/2007 of 26 of March. According to this law every organization
needs to submit information to tax authority regarding transactions in the prescribed SAFT-PT file
format (XML format) to the local tax authority for tax audit purpose. This is a legal requirement in
Portugal.
Later, the necessity to adapt the file to the System Accounting Standards (Sistema de Normalização
Contabilística - SNC), as well as the certification of billing software, required changes in data structure.
The Decree 1192/2009 of 8th October approved a new file structure, with effective date of 1st January
2010. After structure introduced by Decree 160/2013 of the 23rd April , the latest XML structure has
been introduced by Decree 274/2013 of the 21st August and it is effective as off the 1st of October
2013.
Decree 302/2016 of 2nd December 2016 approved a new file structure and then after 1st July 2017
onwards-new file structure is introduced according to Certification Law Portaria nº302/2016. The new
requirement, including the mapping between SNC accounts and Taxonomy codes, is mandatory only
from 1st July 2017.
Until 1st July, customers don’t need to have the taxonomy setup as they are exporting the “old
structure” without taxonomy.

5

4. Overview of SAFT Functionality in Oracle
Oracle E-Business Suite 12 satisfies the "Portuguese Billing Software Certification" requirements if all
components/patches listed below are applied and if the required setup is completed. Customers who would like
to use only PT-SAFT solution can download the relevant patch.
DGCA Billing Certification Number for Oracle Applications Release 12 is 1332.
The SAF-T Audit File [CLE: Generate SAFT-PT Audit File XML Data] in Oracle has been developed in order to meet
the above-mentioned requirement. The concurrent program is used to meet the following business
requirements:
• Generation of an SAFT-PT Audit File XML format for electronic submission to the tax authorities.
• Display of the information regarding transactions from General Ledger Module, customers, receivables
transactions, Shipping documents, suppliers, product (Inventory items/Receivables Memo Lines) and tax.
• Display of additional information stored in Localization Descriptive Flex fields (LDFF).
• Selection of the data based on the GL period from and period to.
• The XML needs to be generated either for a particular Ledger/legal entity. This must be depending on the
respective parameter values.
• Based on profile options address structure should be displayed in the file.
• Meeting the legal/statutory needs for reporting accounting information and transactions data
• Showing the detailed information of accounting and transactions data, which is under Portuguese law in
two different sections.
4.1 Prerequisites
Please refer to the MOS note 1274628.1 for JE (Oracle Financials for EMEA) for Portuguese Billing Software
Certification. Please note that this solution is mandatory prerequisite before installing SAFT-PT solution provided
by EMEA Add on Localization Development.
Please refer to the note 1597808.1 for Import Externally Signed Transactions.
Please refer to the note 1603994.1 for Portuguese Billing Software Certification-Shipping (Please install this patch
if using Oracle EBS Shipping for Portugal only).
For 12.2, please make sure that the Seed patch is applied before applying the individual feature patch.
4.2 Assumptions
• Accounting data is created at Reporting Ledger level and transactional data either at Reporting Ledger
level or at a Primary Ledger level, depending on existing setup and parameters entered on Concurrent
Program.
• It is not possible to filter data by Operating Unit.
• Ledger functional currency should be EUR and chart of accounts should be in line with SNC.
• Posting from Sub-ledgers to General Ledger is done in DETAIL mode only.
8
• All customers and suppliers are expected to have a taxpayer ID assigned to them.
• Only the documents (journal entries and source documents) whose GL Date / Transaction Date is
comprised between the periods expressed by the parameters “Period From”/”Period To” are considered.
• Only posted journal entries / transactions are included.
• Users are responsible for choosing the correct value for the Report Generation Level parameter, as well
for the remaining parameters, including period/date ranges.
• Start / End date is represented by full accounting periods. It is not possible to enter date ranges;
• Account hierarchies are defined.
• All accounts 1% to 8% are considered to belong to SNC. All the remaining are considered to be Analytical.
• 1st degree GL accounts are represented by 2 digits. Single digit GL parent accounts can be excluded.
• 1st degree Analytical accounts are identified as being the top level account.
• For every account having more than 1 parent account, a Localization Descriptive Flexfield (LDFF) is
populated with the parent account chosen to be reported in SAFT. If the child has multiple parents then
it is mandatory to provide the LDFF details on Key Account Flexfield (KFF) Values.
• Each customer bill to site / supplier site is represented as a different party.
• For VAT exempt tax codes, exemption reason is entered in tax description field.
• Stamp values code and description are entered in printed name in description fields.
• Customers who have the Billing Certification patch installed must enter ‘Yes’ on parameter ‘Billing
certification Installed’ in order to get certification information exported on the file.
• Customers using shipping documents and who have the Shipping Certification patch installed must enter
‘Yes’ on parameter ‘Shipping certification Installed’ in order to get shipping documents information
exported on the file.
• Receipts should have sequential numbering assigned, either by standard document sequences or by
Receipt Acknowledgment Letter sequence setup.
• Cash VAT regimes are setup by using VAT tax rates with Deferred Recovery Settlement.
• Cash VAT Regimes are identified at customer level and for specific situations at receipt level.
• Tax information on Receipts depends on Miscellaneous System Option ‘Application Rule Set’ which
should be set to ‘Prorate All’.
• When a receipt doesn’t have active applications at the time of export, it is not exported, but it can be
exported later, if SAFT-PT runs again for the same receipt date period, if active applications are done on
subsequent months.
In other words, SAFT-PT exports receipts for each period based on the receipt date, with the situation it
has at the time it is exported, regardless of the dates of the active applications. Hence to be fully
compliant with SAFT requisites and its validation by Tax Authorities, users should create a new receipt
for new applications instead of creating new applications on different periods for the same receipts.
9
4.3 Mandatory Setups
The following steps need to be completed in order to generate “CLE: Generate SAFT-PT Audit File XML Data‟
output successfully.
1. Assignment of Concurrent Program to Request Group

Below are the steps for adding a concurrent program to a request group. You may please refer to System
Administrator User Guide for detailed steps regarding Request Group.
a. Go to the responsibility System Administrator.

b. Use the navigation Security --> Responsibility --> Define.
c. Query for the responsibility from which you want to provide the access to the concurrent program.
d. Note down the name and application of the request group attached to the responsibility.
e. Go back to the main navigation using View -->Show Navigator.
f. Use the navigation Security --> Responsibility --> Request.
g. Query for the request group and application noted down in step 4.
h. Click on one of the records shown in Requests region.
i. Add a new record by choosing File --> New.
j. Choose the Type of the request as program, name as concurrent program name(CLE:Generate
SAFT-PT Audit File XML Data) and application as concurrent program application (EMEA Consulting Localizations).
k. Save the record by choosing File --> Save.
10
2. General Setups:
1. Setup for CAE Primary Activity Code: Navigate to Accounting Setup Manager -> Legal Entities -> Country:
Portugal -> Tab General -> Update -> CAE Primary Activity.
CAE Activities are selected from AR lookup code "LEGAL_ACTIVITY_CODE_PT", User needs to insert CAE codes in
order to populate the value set and setup the LE accordingly.
2. Functions: User should check if functions ‘CLE_F220_PG’ and ‘CLE Localization DFF Form’ (CLE_F220_DFFX)
are inserted on the menu associated to the responsibility being used.
11
3. User should compile the menus using ADADMIN utility from UNIX.
4. User should ensure that Profiles defined at the responsibility (GL) level has same values which are mentioned
below:
JG: Application - General Ledger
JG: Product - European Localizations
JG: Territory – Portugal
5. Change profile FND: Enable Industry Editing profile is set to Yes and check if all CLE Forms personalization are
created (Navigate to Setup -> Transaction Types -> Help / Diagnostics / Custom code / Personalize).
6. Users should compile LDFF's and ensure that programs are finished with success.
12
3. Profile Options
System Administrator Responsibility > Profile > System
Setup of profile options is mandatory in order to generate a correct SAFT file. These profiles indicate which table
column (customer and supplier sites addresses) will be used to populate the Postal Code, District, City, Address
and Country elements and which Tax Type is used to identify Tax “Imposto de Selo”.
Define and check the values of the following CLE profile options:
1. CLE: PT Customer Address Style (CLE: Estilo de Morada do Cliente – Portugal)

2. CLE: PT Customer City (CLE: Localidade do Cliente – Portugal)
3. CLE: PT Customer Postal Code (CLE: Código Postal do Cliente – Portugal)
4. CLE: PT Customer Region (CLE: Distrito do Cliente – Portugal)
5. CLE: PT Customer Country (CLE: País do Cliente – Portugal)
6. CLE: PT Supplier Address Style (CLE: Estilo de Morada do Fornecedor – Portugal)
7. CLE: PT Supplier City (CLE: Localidade do Fornecedor – Portugal)
8. CLE: PT Supplier Postal Code (CLE: Código Postal do Fornecedor – Portugal)
9. CLE: PT Supplier Region (CLE: Distrito do Fornecedor – Portugal)
10. CLE: PT Supplier Country (CLE: País do Fornecedor – Portugal)
11. CLE: PT Stamp Tax Type (CLE: Tipo de Imposto de Selo - Portugal)
12. CLE: PT Tax Code not subject to VAT
13. CLE: PT Use AR Transaction Number for SAFT
Possible values for profiles 1 to 10 are:
ADDRESS1
ADDRESS1 + ADDRESS2
ADDRESS1 + ADDRESS2 + ADDRESS3
ADDRESS1 + ADDRESS2 + ADDRESS3 + ADDRESS4
ADDRESS2
ADDRESS3
ADDRESS4
CITY
COUNTRY
COUNTY
POSTAL_CODE
PROVINCE
STATE
Possible values for profile 11 are the Tax types defined on Lookup “ZX_TAX_TYPE_CATEGORY” and from that list,
tax type currently being used for the purpose of Stamp Tax should be picked for this profile.
If no specific TAX_TYPE is being used, you may create Tax Type “Imposto de Selo” as a lookup value that should
be added to lookup “ZX_TAX_TYPE_CATEGORY”.
13
Regarding Profile 12, "CLE: PT Tax Code not subject to VAT" is used when AR transactions doesn't have tax lines.
Since SAFT legal requirement, Portuguese Law changed and it is mandatory to have tax details.
As the old transactions or upgraded transactions do not have this information, SAFT program will associate these
transactions to the tax rate associated to this profile option.
In this case we should setup the tax rate LDFF 'CLE: Additional Information' as 'NS' - Not Subject to VAT or IS.
Context Value = PT
LDFF on Tax rates for PT = NS
*Tax value = NS
*Country = PT
Export to SAFT = Yes
Profile 13 has the possible values of Yes or No, to indicate if AR transaction number will be used for SAFT.
Profile 14: CLE: PT SAFT Taxonomy Reference - Users need to assign Taxonomy Reference that will be used by
Portuguese Legal Entity.
List of available values:
S – SNC the entered Chart of Accounts

N – International Standards Chart of Accounts
M – SNC for Smaller Units
O – Other
4. Localization Descriptive Flex fields (LDFFs)
Please ensure that the following Localization Descriptive Flexfields (LDFFs) are in place when the patch is
installed. These needs to be verified once the patch installation has been completed.
Query for the below mentioned Localization DFF titles and enable the ‘PT’ context for them, in case
it is not already enabled.
Responsibility: Application Developer

Navigation: Flexfield > Descriptive > Segments
Application: EMEA Add-on Localizations
• CLE:Additional Info on Journal Categories

• CLE: Additional Information on PO Vendors
• CLE: Additional Info On Transaction Type - Added new values so that we can have different sources:
a) AR: LDFF that already exist for AR, invoice type. We need to include the following codes on AR LDFF -
CM/CC/FC/PF/RP/RE/CS/LD….
If the AR trx have this LDFF then it will not be printed on AR block, but on this block.
If AR trx have this LDFF with the old values, then it will be printed on the AR side. b)
OM: Codes NE/OR (Debit Memos not signed- pending from AT)
c) Shipment: It will print OU if ship trx date is > 30.06.2017
14
• CLE: Additional Info On HZ Parties
• CLE: Additional Info On ZX Tax Rates
• CLE: Additional Info On Receipt Methods
• CLE: Additional Info On Memo Lines
• CLE: Additional Info On Transaction Lines – This new LDFF will have the Administrative Reference number
to be printed on ARCNo Tag in case of an Exempt tax
• CLE: Additional Information on Inventory Item to identify the Excise Duty item.
5. Global Descriptive Flex fields (GDFFs)

Please ensure that the following Global Descriptive Flex fields are in placed when the patch is installed. These
needs to be verified once the patch installation has been completed.
Responsibility: Application Developer

Navigation: Flexfield > Descriptive > Segments
Application: Regional Localizations
• JG_RA_CUSTOMER_TRX (Context Code - JE.PT.ARXTWMAI.CLE_SAFT)

• JG_RA_CUSTOMER_TRX_LINES (Context Code - JE.PT.ARXTWMAI.CLE_INV_INFO)
• JG_RA_BATCH_SOURCES (Context Code - JE.PT.RAXSUMSC.BATCH_SOURCES)
• JG_WSH_NEW_DELIVERIES – (Context Code - JE.PT.WSHFSTRX.CLE_SAFT)
15
• JG_AR_CASH_RECEIPTS – (Context Code - JE.PT.ARXRWMAI.RA_INFO)
6. Define SNC Accounts with LDFF values

Account's hierarchy must be defined always, since it is required to obtain each account's balance. In case of
"Grouping Category" and "Parent Account" data, also the account’s hierarchy must be defined.
Only in cases that it is necessary to override the account’s hierarchy definition, the values on DFF should be filled.
Also if the child account has multiple parents or in cases of orphaned accounts, then it is mandatory to provide
the Localization Descriptive Flexfield details on the LDFF.
So, if set up of DFF is done, program will export the setup, if not it will export account's hierarchy definition.
Responsibility: Receivables > Setup > Financials > Flexfields > Key > Values>
Select the SNC Accounts Flexfield and for each account, enter the LDFF information.
Note: If SNC Chart of accounts setup is not available, SAFT-PT Extract file still works and produce XML output in
desired format, but it may not be accepted by the legal authorities, as SNC COA is mandatory legal requirement
in Portugal since 2010.
7. Define LDFF values at Customer Level
Responsibility: Receivables
Navigation: Customers > Standard
Query for the existing customer or define a new customer. Click on Account Name and then click on “CLE:
Additional Information” to enter the LDFF values.
16
8. Define LDFF values at Tax Rate Level
Responsibility: Tax Managers

Navigation: Tax Configuration > Tax Rates
Query for the tax rates defined for Portugal. Click on Tax Rate Name and then click on “CLE: Additional
Information” to enter the LDFF values.
17
9. Define LDFF values at Supplier Level
Responsibility: Payables
Navigation: Suppliers > Entry
Query for the existing supplier defined for Portugal. Move cursor Right to CLE: Foreign Supplier
18
10. OAF Page Personalization Steps
Localization DFF’s, Global DFF’s and Form based personalizations are automated and are part of the patch. OAF
page personalizations needs to be created manually at Customers, Suppliers and Tax Rates Level by following the
steps mentioned in the user guide (Refer section - OA Page Personalization Steps).
11. AR Transaction Source
Define an AR Transaction Source on which SAFT will be applicable.
Navigation: Setup > Transactions > Sources
Enter all the mandatory details and click on GDFF to enter the details as shown below:
19
11. AR Transaction Type
Define an AR Transaction Type on which SAFT will be applicable.
Navigation: Setup > Transactions > Transaction Types
Enter all the mandatory details and click on Actions > CLE: Additional Info on Transaction Type to enter the
details as shown below:
20
Note: For more details on the setup, please refer the User Guide for R12 EMEA Add-on Localizations - Portugal
4.4 Transaction Flow
a. Create an AR Transaction using Transaction Source enabled for SAFT
Line level details
21
b. Enter the values in GDFF at Transaction Header Level
c. Enter the values in LDFF – Actions > CLE: Additional Info on Transactions
22
d. Complete the Transaction
e. Account the Transaction and post entries to GL
23
4.5 Report Submission and Parameters
The users will be provided with a concurrent request that will generate the SAFT File in XML format for
electronic submission to the Tax authorities.
The XML output will be generated on server and placed in the utl_file_dir based on the parameters entered
in the concurrent request.
Responsibility: General Ledger

Navigation: View-->Request-->Submit a New Request-->Single Request
Program Name: CLE: Generate SAFT File XML Data
24
25
Parameters:
Parameter Required Default Description

Values
Primary Ledger Yes Yes It shows all the ledger names based on the profile option “GL Data
Access Set‟ then it shows all the ledgers associated with that
ledger set name.
Reporting Ledger No No It shows all reporting ledgers (secondary/consolidation ledgers).
In case of Portuguese Reporting Ledger being other than the
Primary Transactional Ledger, this parameter should be entered.
Legal Entity Yes N/A It shows associated legal entities of the selected ledger.
Balancing Segment No N/A It shows associated balancing segments of selected legal entity
and it is filtered based on the legal entity selection.
Inventory No N/A It shows all Inventory organizations available in the environment.
Organization
Business Name Yes N/A This field needs to be entered by the user.
26
Report Yes N/A The List of Values(LOV) contains:
Generation Level C – Contabilidade
(C – Accounting)
F – Facturação
(F – Billing)
I – Integrado
(I – Integrated)
P1 - Dados parciais de Facturação – Integrado
(P1 – Partial data Billing – Integrated)
P2 - Dados parciais de Facturação – Não Integrado
(P2 – Partial data Billing – Not Integrated)
S – Autofacturação
(S – Selfbilling)
R – Receipts
T – Shipping Documents
E – Billing issued by third parties
File Version Yes N/A This parameter shows a constant value “1.04_01‟ as
default.
Company Name Yes N/A This field needs to be entered by the user.
Registration Yes N/A This field needs to be entered by the user.
Number
Fiscal Yes NA This field needs to be entered by the user.
Registration
Number
Address Yes N/A This field needs to be entered by the user.
City Yes N/A This field needs to be entered by the user.
Postal Code Yes N/A This field needs to be entered by the user.
Region Yes N/A This field needs to be entered by the user.
Country Yes N/A This field needs to be entered by the user.
Period From Yes N/A The List of Values (LOV) for the periods attached to ledger.
Period To Yes N/A The List of Values (LOV) for periods attached to ledger.
First Period of the Yes Yes It should show all the periods not Future neither Never Opened
Fiscal Year based on the ‘Ledger Name’ parameter selection.
By default it should show the first non adjustment period of the
Fiscal year containing the period inserted on parameter Period
From
Comments No N/A This field needs to be entered by the user.
Telephone No N/A This field needs to be entered by the user.
Fax No N/A This field needs to be entered by the user.
Email No N/A This field needs to be entered by the user.
Website No N/A This field needs to be entered by the user.
XML solves PT Yes Yes By default this parameter is set to YES, but If for some reason
Char Set the XML is not being able to generate Portuguese characters this
parameter should be set to NO.
Billing Yes N/A For environments which do not have the billing
certification certification installed, it should be set to NO, if certification
Installed is installed it should be set to YES.
27
Shipping Yes N/A For environments which do not have the Shipping certification
certification installed, it should be set to NO, if certification is installed it
installed should be set to YES. This parameter determines if shipping
documents information is exported on SAFT file. When set to
‘YES’, SAFT blocks 4.2 and 4.3 will be exported, when set to ‘NO’,
these 2 blocks will not be exported.
Receipts Yes N/A This parameter defines whether type of Receipts Sequence
Sequence numbering is from either standard document sequences or
numbering type Receipt acknowledgment Letter sequence setup.
File Directory No N/A It is not a mandatory parameter .PT Saft XML output file is saved
in the path specified in the parameter and can be moved to only
one directory at a time.
4.6 File Structure and Reporting Levels

Structure:
The SAFT-PT XML file has the following 4 main groups wherein data is shown and these are called elements:
a. Header
b. Primary Files
1. General Ledger
2. Customer
3. Supplier
4. Product
5. Tax Table
c. General Ledger Entries
d. Source Documents
1. Sales Invoice
2. Movement of Goods
3. Working Documents
4. Payments
Reporting Levels:
The SAFT-PT file has the following reporting generation levels:
a. Accounting (C)
b. Billing (F)
c. Self-billing (S)
d. Integrated (I)
e. Partial data billing – Integrated (P1)
f. Partial data billing - Not Integrated (P2)
g. Receipts (R)
h. Shipping documents (T)
i. Billing issued by third parties (E)
4.7 Report Output Analysis
28
SAFT-PT_7378269.x
ml
XML Tags
The following table describes the XML tags generated as a part of the XML file and relative description of
the tags.
Tag Name Description
<AuditFile> This tag contains the fixed text

xmlns="urn:OECD:StandardAuditFile-Tax:PT_1.04_01".
<Header> This element is displayed at the top level in the XML file which
shows all the data related to parameters.
<AuditFileVersion> This tag contains the fixed text of the file version : 1.04_01
<CompanyID> This tag contains the value of the parameter 'Registration Number
'.
<TaxRegistrationNumber> This tag contains the value of the parameter 'Fiscal Registration
Number'.
<TaxAccountingBasis> This tag contains the value of the parameter 'Report Generation
Level'.
<CompanyName> This tag contains the value of the parameter ‘Company Name'.
<BusinessName> This tag contains the value of the parameter 'Business Name'.
<CompanyAddress> This tag contains information of the company address.
<BuildingNumber/> This tag is empty.
<StreetName/> This tag is empty.
<AddressDetail> This tag contains the value of the parameter 'Address'.
<City> This tag contains the value of the parameter 'City'.
<PostalCode> This tag contains the value of the parameter 'Postal Code '.
<Region> This tag contains the value of the parameter 'Region'.
<Country> This tag contains the value of the parameter 'Country'.
29
<FiscalYear> This tag is the year of the 'Period From and Period To' parameters.
<StartDate> This tag contains the value of the parameter 'Period From '.
<EndDate> This tag contains the value of the parameter ' Period To'.
<CurrencyCode> This tag shows the currency as constant value “EUR”.
<DateCreated> This is the date of creation (sys date) in the format 'YYYY-MM-
DD”.
<TaxEntity> This tag contains a value depending on the Tag:
'<TaxAccountingBasis>'
1. If the tag Tax Accounting Basis is having the values “F”,
“C”, or “S”, or “P1”, this tag contains a value as “Global”.
2. If Tax Accounting Basis is having the value “I” or “P2”,
it will display the value “Sede”.
<ProductCompanyTaxID> This tag shows constant value as “502186771”.
<SoftwareCertificateNumber> This tag shows constant value as “0” If the parameter value is null.
Otherwise, it shows value from parameter “Software Certificate
Number”.
<ProductID> This tag shows constant value as “ORACLE/EBUSINESS SUITE”.
<ProductVersion> This tag contains the value of software version of the product.
<HeaderComment> This tag contains the value of the parameter “Comments”.
<Telephone/> This tag contains the value of the parameter 'Telephone'.
<Fax/> This tag contains the value of the parameter 'Fax'.
<Email/> This tag contains the value of the parameter 'Email'.
<WebSite/> This tag contains the value of the parameter 'Website'.
<MasterFiles> Primary files block displays information related to the following

elements and which should be followed Header level element:
• General Ledger
• Customer
• Supplier
• Product
• Tax Table.
<GeneralLedger>. This is the General Ledger block started tag.
<AccountID> This tag shows every natural account segment values whether it
allows posting or not.
<AccountDescription> This tag shows the description of the above account.
30
<OpeningDebitBalance> This tag contains value of the opening debit balance for the first
non adjustment period of the Fiscal year chosen on parameter
“First Period of the Fiscal Year”
<OpeningCreditBalance> This tag contains value of the opening credit balance for the first
non adjustment period of the Fiscal year chosen on parameter
“First Period of the Fiscal Year”
<ClosingDebitBalance> This tag contains value of the closing debit balance (for the Last
non adjustment period of the fiscal year chosen on
parameters).
<ClosingCreditBalance> This tag contains value of the closing credit balance (for the Last
non adjustment period of the fiscal year chosen on parameters).
<GroupingCategory> It will identify both the account types (General Ledger and
Analytical) and whether if it is a 1st degree account (“Conta do
Razão”),parent account (“Conta Agregadora”) or a movement
account (“Conta de Movimento”):
- GR – 1st degree GL account;
- GA – GL parent account;
- GM – GL movement account;
- AR – 1st degree analytical account;
- AA – Analytical parent account;
- AM - Analytical movement account.
<GroupingCode> This tag contains value of the parent account (AccountID).
<Customer> This is the customer’s block started tag.
<CustomerID> This tag contains the concatenated value of the customer’s account
number and party site ID.
<AccountID> This tag shows Receivables natural account segment value setup at
customer site level.
<CustomerTaxID> This tag contains a constant value “999999990‟, if the customer is
generic customer. Otherwise, it shows customer’s taxpayer ID for
normal customers.
<CompanyName> This tag contains a constant value “Final consumer, “l”, if the
customer is generic customer. Otherwise, it shows customer’s
taxpayer name for normal customers.
<Contact> This tag contains a value of customer’s contact name, which is
concatenated of Title, First name and Last name.
<BillingAddress> This is billing address element started tag.
<BuildingNumber/> This is the empty tag.
<StreetName/> This is the empty tag.
31
<AddressDetail> This tag is the address details of the active customer and its
structure depends on the CLE: PT Customer Address Style Profile
value.
<City> This tag is the City of the active customer and its structure depends
on the CLE: PT Customer City Profile value.
<PostalCode> This tag is the Postal code of the active customer and its structure
depends on the CLE: PT Customer Postal Code Profile value.
<Region/> This tag is the Region of the active customer and its structure
depends on the CLE: PT Customer Region Profile value.
<Country> This tag shows a constant value as “PT”.
<ShipToAddress> This is Ship to address element started tag.
<BuildingNumber> This is the empty tag.
<StreetName> This is the empty tag.
structure depends on the CLE: PT Customer Address Style Profile
value.
<City> This tag is the city of the active customer and its structure depends
on the CLE: PT Customer City Profile value.
<PostalCode> This tag is the postal code of the active customer and its structure
depends on the CLE: PT Customer Postal Code Profile value.
<Region/> This tag is the region of the active customer and its structure
depends on the CLE: PT Customer Region Profile value.
<Country> This tag is a constant value as “PT”.
<Telephone/> This tag is the telephone number of the customer.
<Fax/> This tag is the fax number of the customer.
<Email/> This tag is the e-mail of the customer.
<Website> This tag is the website of the customer.
32
<SelfBillingIndicator> This tag contains either one of the following values depending on
the
Localization DFF for customer information on the customer’s OA
page:
0
<Supplier> This is the supplier’s block started tag.
<SupplierID> This tag contains the concatenated value of the supplier’s number
and site ID.
<AccountID> This tag shows Liability natural account segment value setup at
supplier site level.
<SupplierTaxID> This tag contains the supplier’s tax payer ID.
<CompanyName> This tag is the supplier’s name.
<Contact> This tag contains a value of supplier’s’ contact name, which is

concatenated of Title, First name and Last name.
<BillingAddress> This is billing address element started tag.
<AddressDetail> This tag is the address details of the active Supplier and its structure
depends on the CLE: PT Supplier Address Style Profile value.
<City> This tag is the City of the active Supplier and its structure depends on
the CLE: PT Supplier City Profile Value.
<PostalCode> This tag is the Postal code of the active Supplier and its structure
depends on the CLE: PT Supplier Postal Code Profile Value.
<Region> This tag is the Region of the active Supplier and its structure depends
on the CLE: PT Supplier Region Profile Value.
<Country> This tag shows a constant value as “PT‟.
<ShipFromAddress> This is ship to address element started tag.
33
<AddressDetail> This tag is the address details of the active Supplier and its structure
depends on the CLE: PT Supplier Address Style Profile value.
<City> This tag is the city of the active Supplier and its structure depends on
the CLE: PT Supplier City Profile value.
<PostalCode> This tag is the postal code of the active Supplier and its structure
depends on the CLE: PT Supplier Postal Code Profile value.
<Region> This tag is the region of the active Supplier and its structure depends
on the CLE: PT Supplier Region Profile value.
<Country> This tag is a constant value as “PT”.
<Telephone/> This tag is the telephone number of the Supplier.
<Fax> This tag is the fax number of the Supplier.
<Email> This tag is the e-mail of the Supplier.
<Website> This tag is the website of the Supplier.
<SelfBillingIndicator> This tag contains either one of the following values depending on the
Localization DFF for Supplier Information on the supplier’s OA page:
<Product> This is product’s block started tag.
34
<ProductType> This tag contains one of the following values:
P (If the data comes from inventory items and item is stockable or
AR memo lines that line type is “Line” and it has no setup on memo
Lines LDFF. IF Memo lines LDFF is setup it will export value setup on
LDFF).
S (If the data comes from inventory items and item is not stockable
or if the data comes from AR memo lines, which are having the line
type as “Freight”).
O (If the data comes from AR memo line, which is having the line
type as “Charges” or it is dummy product).
<ProductCode> This tag is the one of the following concatenated values: INV-
Inventory ID (if it is related to inventory item)
ML-Memo Line ID (if it is related to Memo line item)
“000000” (if it is not related to inventory and memo lines)
<ProductGroup> This tag is the one of the following values:
Produtos (if it is related to inventory item) (Products)
Linhas de Nota Standard (if it is related to Memo line item) (Memo

lines)
Artigo Genérico (if it is related to Dummy Product)
(Generic Article)
<ProductDescription> This tag is the one of the following values:
Description of products (if it is related to inventory item)
Description of the Standard Memo Lines (if it is related to Memo

line item)
Constant value “Artigo Genérico‟ (if it is related to Dummy Product)
<ProductNumberCode> This tag is the value of the “<Product code>” tag.
<TaxTable> This is tax table’s block started tag.
35
<TaxTableEntry> This is the tax tables entry element started tag.
<TaxType> This tag is the one of the following values:
IVA ( if tax type is VAT)
IS (if tax type is SELO)
<TaxCountryRegion> This tag contains the value depending on the Localization DFF for Tax
Rate Code Information on the standard Tax rates OA page.
<TaxCode> This tag contains the value depending on the Localization DFF for Tax
Rate Code Information on the standard Tax rates OA page.
<Description> This is the description of the tax type code.
<TaxExpirationDate> This is the end date of the inactive tax rate codes.
<TaxPercentage> This is the percentage rate of the Tax and instead of this if
the taxable_basis is QUANTITY only the <TaxAmount> tag
will be filled mentioned below.
<TaxAmount> This is the Tax amount of the Tax rate code, if the taxable basis is
QUANTITY. Otherwise, only <TaxPercentage> tag will be displayed.
<GeneralLedgerEntries> This is General Ledger’s block started tag.
<NumberOfEntries> This is the number of manual journal headers (actual journals) +

Receivables transactions + Payables invoices which are having the
status as posted in the ledger falling into the periods express in the
parameters “Period From and Period To”.
<TotalDebit> This is the total debits in EUR for the journals running totals of the
debit.
<TotalCredit> This is the total credit in EUR for the journals running totals of the
credit.
<Journal> This is journal’s block started tag.
<JournalID> This is the journal category name.
<Description> This is the description of the journal category.
36
<Transaction> This is the transactions element beginning tag. It contains AR
and AP subledger transactions when journals are transferred
to General Ledger in detail mode.
<TransactionID> This is the transaction ID, which contains concatenated

value of Effective Journal Date (YYYY-MM-DD), the category
name and the transaction ID (Customer trx ID, invoice ID or
Journal ID).
<Period> This is tag shows period number based on transaction falling
between the “From Period and To Period” parameter values.
<TransactionDate> This is the GL Journal default effective date.
<SourceID> This is the user name of the last updated.
<Description> This is the description of the Journal Header.
<DocArchivalNumber> This is the Customer trx ID, invoice ID or Journal ID depending on the
origin of the entry.
<TransactionType> This tag contains a value depending on the Localization DFF for
Journal Category Information of the journal category.
<GLPostingDate> This is the date the journal entry is posted.
<CustomerID> This tag contains concatenated the customer’s account number and
party site ID with reference to Receivables Invoices, Credit Memos
or Debit
Memos, Deposits and Guarantees. . Otherwise, it will not show.
<SupplierID> This tag contains supplier number with reference to Payables

Invoices, Credit Memos, Debit Memos or Mixed. Otherwise, it will
not show.
<Line> This is the beginning element of the journal line tag.
<RecordID> This tag contains a unique ID for each GL line on the file.
<AccountID> This is the General Ledger Account Code.
<SourceDocumentID> This tag contains concatenated value of the transaction type

name||'-'||transaction number in case of a Receivables transaction,
otherwise it will not be exported.
37
<SystemEntryDate> This is the date, which is captured by the system at the time of
journal creation.
<Description> This tag contains concatenated value of the Journal Header ID and
Journal Line number and journal line description.
<DebitAmount> This is the debit amount of the journal line. The credit amount
mentioned below will not be shown, if it exists.
<CreditAmount> This is the credit amount of the journal line. The debit amount will
not be shown, if it exists.
<SourceDocuments> This is the beginning block of the source documents, which shows
information relating to following receivable transactions only:
Invoices Debit
Memo Credit
Memo Deposit
Guarantee
Charge Back
<SalesInvoices> This is the beginning element of the sales invoice.
<NumberOfEntries> This tag shows number of sales documents.
<TotalDebit> This tag contains total debit amount (Only Line, Freight and Charges)
of the transactions and it will not include tax values.
<TotalCredit> This tag contains Total Credit amount (Only Line, Freight and
Charges) of the transactions and it will not include tax values.
<Invoice> This is beginning tag of the invoice element.
<InvoiceNo> This is the invoice number which shows as concatenated value of

RA_CUST_TRX_TYPES_ALL.type||'
'||nvl(RA_CUSTOMER_TRX_ALL.doc_sequence_id,
RA_BATCH_SOURCES_ALL.batch_source_id)||'/'||
nvl(RA_CUSTOMER_TRX_ALL.doc_sequence_value,
RA_CUSTOMER_TRX_ALL.customer_trx_id)
38
<DocumentStatus> This is the beginning element of the sales invoice document status
info.
<InvoiceStatus> This tag contains the following values:
'N' - Normal;
'S' - Self Billing;
'A' - Voided;
'R' - Summarized documents created in external systems;
‘F' - Already billed.
<InvoiceStatusDate> Date and time of the last update of the InvoiceStatus (YYYY-MMDD
Thh:mm:ss)
<Reason> This tag shows the reason for the status change.
<SourceID> User identifier of the last status update.
<SourceBilling> Possible values are:
-'P' for documents created in EBS;
-'I' for imported documents;
-'M' for invoices created manually outside the system (in paper) and
then replicated in the system.
Values are picked from the Transaction Source GDFF.

<Special Regimes> Parent Tag.
<Cash VAT Scheme Indicator> This tag contains values based on the Localization DFF for Customer
Information of the bill to customer OA page.
<ThirdPartiesBillingIndicator> This tag contains values based on the Localization DFF for Customer
39
<Hash> This tag contains value “0” if the transaction is not certified.
Otherwise, if transaction is certified, this tag shows transaction
signature.
<HashControl> This tag contains value “0” if the transaction is not

certified.Otherwise, if transaction is certified, this tag shows
the private key version.
<Period> This tag contains the accounting period number.
40
<InvoiceDate> This tag contains the invoice date in YYYY-MM-DD format.
<InvoiceType> This tag contains values based on the Localization DFF for AR
Transaction Type Information of the AR transaction form.
<SelfBillingIndicator> This tag contains values based on the Localization DFF for Customer
<SourceID> User identifier of the document creation.
<EACCode> This tag contains value of ‘CAE Primary Activity’ Code (CAE)
retrieved from the Legal Entity definition page. ‘CAE Primary activity
code’ Lov values are retrieved from AR_LOOKUPS where
LOOKUP_TYPE is 'LEGAL_ACTIVITY_CODE_PT'.
<SystemEntryDate> This is the transaction creation date and its format is 'YYYY-MM-
DD'T'hh24: mi:ss’.
<TransactionID> This tag contains the same value of the <TransactionID> tag of the
general ledger entries block.
<CustomerID> This tag contains the customer ID, which will match in the entire file.
Element 2.2.1 should match elements 3.4.3.9 and 4.1.4.11.
<ShipTo> This is the “Ship To” address details beginning element. These
cannot be empty tags. If no information exists for any tag of this
block, then it will not show tags.
<DeliveryID> This is the delivery ID number if no reference exists, and then it will
not show in the file.
<DeliveryDate> This is the Delivery Date if no reference exists, and then it will not
show at all in the file.
<Address> This is the beginning tag of the address.

structure depends on the CLE: PT Customer Address Style profile
value.
If Address does not exist, tag will not be exported.
39
on the CLE: PT Customer City profile value. If Address does not exist,
tag will not be exported.
depends on the CLE: PT Customer Postal Code profile value. If
Address does not exist, tag will not be exported.
<Region> This tag is the region of the active customer and its structure
depends on the CLE: PT Customer Region profile value. If
<Country> This tag shows a constant value as “PT”. If Address does not exist, tag
will not be exported.
<ShipFrom> This is the “Ship From” address details beginning element. These
cannot be empty tags if no information exists for any tags of this
block, and then it will not show tags.
<DeliveryID/> This is the delivery ID number if no reference exists, and then it will
not show tags in the file.
<DeliveryDate/> This is the delivery date if no reference exists, and then it will not be
shown in the file.
<Address> This is the beginning tag of the address.
<BuildingNumber/> This is the empty tag.
<AddressDetail/> This tag is the address details of the active customer and its
structure depends on the CLE: PT Customer Address Style profile
value.
If Address does not exist, tag will not be exported.
42
on the CLE: PT Customer City profile value. If Address does not exist,
depends on the CLE: PT Customer Postal Code.
<Region> This tag is the region of the active customer and its structure
depends on the CLE: PT Customer Region profile value. If
<Country> This tag shows a constant value as “PT‟. If Address does notexist,
<Line> This is the beginning tag of the lines.
<LineNumber> This is the line number of the transaction.
<OrderReferences> This is the beginning element of the sales order information.
<OriginatingON> This is the sales order number if exists. Otherwise, it will not be
exported.
<OrderDate> This is the sales order date if exists. Otherwise, it will not be
exported.
<ProductCode> This tag is the one of the following concatenated values: INV-
Inventory ID (if it is related to inventory item)
ML-Memo Line ID (if it is related to Memo line item)
“000000” (if it is not related to inventory and memo lines)
<ProductDescription> This tag is the one of the following values:
Description of Products (if it is related to inventory item).
Description of the Standard Memo Lines (if it is related to Memo

line item).
Constant value “Artigo Genérico (if it is related to Dummy

Product).
<Quantity> This is the quantity of goods and services supplied (absolute
value).
43
<UnitOfMeasure> This is the above quantity of measure.
<UnitPrice> This is unit price of the selected quantity of goods and services
supplied (absolute value).
<TaxPointDate> This is the date of supply of goods (transaction date) and its
format as YYYY-MM-DD.
<References> This is the references beginning element.
<CreditNote>. This is the credit note beginning tag.
<Reference> This is the credit note reference, applicable to original invoice. If

no information exists, then it will not be exported. This is also used
as the reference filed for Debit Memos to report the original
invoice the DM refers to.
<Reason> This is the credit note reason. If no information exists, then it will
not be exported.
<Description> This is the transaction line description.
<DebitAmount> This is the debit amount of the transaction (absolute value).
<CreditAmount> This is the credit amount of the transaction (absolute value).
<Tax> This is the beginning tag of the tax element.
<TaxType> This tag is the one of the following values related to transaction:
IVA ( if tax type is VAT)
IS (if tax type is SELO)
<TaxCountryRegion> This tag contains the value related to tax of transaction, which
depends on the Localization DFF for Tax Rate Code Information
on the standard Tax rates OA page.
<TaxCode> This tag contains the value related to tax of transaction, which
depends on the Localization DFF for Tax Rate Code Information
on the standard Tax rates OA page.
44
<TaxPercentage> This is the percentage rate of the Tax and instead of this if
the taxable_basis is QUANTITY, only the <TaxAmount> tag
mentioned below, will be filled.
<TaxAmount> This is the Tax amount of the Tax rate code if the taxable basis is
QUANTITY. Otherwise, <TaxPercentage> tag is displayed only.
<TaxExemptionReason> This is the tax exemption reason, which is mandatory only, if Tax
Percentage or Tax Amount is 0. Otherwise, it is not shown at all.
<SettlementAmount> This is an empty tag.
<DocumentTotals> This is the beginning tag of the document totals element.
<TaxPayable> This tag contains total tax payable (absolute value).
<NetTotal> This tag contains a value total sales excluding tax (absolute
value).
<GrossTotal> This tag contains a value of gross total of sales (tax payable + total
sales excluding tax) (absolute value).
<Currency> This is the beginning tag of the currency for foreign currency
transactions.
<CurrencyCode> This is the invoice currency code. It shows the currency of

Transactions if other than EUR.
<CurrencyAmount> Gross total in foreign currency.
<Exchange rate > Exchange rate used.
<Settlement> This is the beginning tag of the settlement.
<SettlementDiscount> This is the settlement discount. If the references do not exist, tag will
not be exported.
<SettlementAmount> This is the settlement amount. If the references do not exist, tag will
not be exported.
<SettlementDate> This is the date of settlement namely term due date.
45
<PaymentTerms> Payment terms negotiated (text).
<Payment> This is the beginning tag of the payment information.
<PaymentMechanism> This is the transaction payment method, which contains a value

based on the Localization DFF for AR Receipt Method Information
of Receipt class form. If the references do not exist, tag will not be
exported.
<PaymentAmount> Paid amount grouped by Payment Mechanism.
<PaymentDate> Payment Date.
<WithholdingTax> There is no withholding tax in receivables. This part of the structure

will not pick up any values. Tag will not be exported.
<WithholdingTaxType> There is no withholding tax in receivables. This part of the structure

<WithholdingTaxDescription> There is no withholding tax in receivables. This part of the
Structure will not pick up any values. Tag will not be exported.
<WithholdingTaxAmount> There is no withholding tax in receivables. This part of the structure

<MovementOfGoods>
<NumberOfMovementLines> Total number of exported lines.
<TotalQuantityIssued> Sum of element 4.2.3.19.5 (Quantity)
<StockMovement>
<DocumentNumber> Concatenate "Internal Document Code"||"(Space)"||"Sequence

Identifier"||"/"Document Number"
46
<DocumentStatus>
<MovementStatus> Should be filled with one of the following values:
- "N" - Normal / Normal
- "T" - By third party / Por conta de terceiros;
- "A" - Voided / Documento anulado;
- "R" - Summarized documents from other systems.
<MovementStatusDate> Date and time of the last update of the document status (YYYY-MM-
DD
Thh:mm:ss)
<Reason> This tag is empty.
<SourceID> User identifier of the last status update
<SourceBilling> Value ‘P’ by default if Additional Delivery Information DFF not filled
47
<Hash> Certification digital signature. "0" if not digitally signed.
<HashControl> Private key version used to digitally sign the document.
<Period> Period number from 1 to 12.
<MovementDate> Document date.
<MovementType> Must be filled with:
- "GR" - Packing Slip / Guia de Remessa;
- "GT" - Bill of Lading / Guia de Transporte;
- "GA" - Guia de movimentação de activos próprios;
- "GC" - Guia de consignação;
- "GD" - Guia ou nota de devolução efectuada pelo cliente.
<SystemEntryDate> Entry date at the time of the document signature generation

(YYYY- MM-
DD Thh:mm:ss)
<TransactionID> Mandatory under Perpetual Inventory and if element 1.4

TaxAccountingBasis = "I" (Integrated/Integrado). Filled
with the unique reference of the General Ledger entry
used to post the corresponding entry (TransactionID).
<CustomerID> Unique customer identifier (same as 2.2.1 - CustomerID). If not

identifiable then the 'Generic Customer' should be used.
<SupplierID> Unique supplier identifier (sames as 2.3.1 - SupplierID).
48
45
<SourceID> User identifier of the document creation .
<EACCode> This tag contains value of ‘CAE Primary Activity’ Code (CAE) retrieved
from the Legal Entity definition page. ‘CAE Primary activity code’ Lov
values are retrieved from AR_LOOKUPS where LOOKUP_TYPE is
'LEGAL_ACTIVITY_CODE_PT'.
<MovementComments> Additional comments.
<ShipTo> Information about the place and date of the delivery of the goods.
<DeliveryID> Delivery identifier.
<DeliveryDate> Delivery date.
<WarehouseID> This tag is empty.
<LocationID> Warehouse locator of the goods.
<Address>
<BuildingNumber> This tag is empty.

<StreetName> This tag is empty.
<AddressDetail> Must include the street name, number and floor (if applicable).
<City> City.
<PostalCode> Postal Code.
<Region> Region.
<Country> Filled with the 2 digit country code (ISO 3166 1-alpha-2).
<ShipFrom> Information about the place and loading date for the shipping of the
goods.
<DeliveryID> Delivery identifier.
<DeliveryDate> Delivery date of the goods.
<WarehouseID> Warehouse identifier.
<LocationID> Warehouse locator of the goods.
<Address>
50
<BuildingNumber> This tag is empty.
<StreetName> This tag is empty.
47
<AddressDetail> Must include the street name, number and floor (if applicable).
<City> City.
<PostalCode> Postal Code
<Region> Region
<Country> Filled with the 2 digit country code (ISO 3166 1-alpha-2).
<MovementEndTime> Date and time of the end of the movement of goods.
<MovementStartTime> Date and time of the start of the movement of goods.
<ATDocCodeID> Shipping document identification code given by the tax authorities.

(Law Decree 198/2012).
<Line>
<LineNumber> Line number (ordered by ascending order).
<OrderReferences> Reference to the source document (same as element 4.1.4.18.2).
<OriginatingON> Link to the order reference.
52
<OrderDate> Date of the order.
<ProductCode> Link to the product table (element 4.2.2 - ProductCode).
<ProductDescription> Link to the product table (element 4.2.4 - ProductDescription).
<Quantity> Quantity.
<UnitOfMeasure> Unit of measure.
<UnitPrice> Unit price.
<Description> Description in the document line.
<DebitAmount> Filled if the document is valued for incoming items. If not valued
filled with "0.00".
<CreditAmount> Filled if the document is valued for outgoing items. If not valued
filled with "0.00".
<Tax> This structure is filled only if the document is valued.
<TaxType> Similar to 4.1.4.18.13.1 – Tax Type.
<TaxCountryRegion> Similar to 4.1.4.18.13.2 – Tax Country Region.
53
<TaxCode> Similar to 4.1.4.18.13.3 – Tax Code.
<TaxPercentage> Similar to 4.1.4.18.13.4 – Tax Percentage.
<TaxExemptionReason> Similar to 4.1.4.18.14 – Tax Exemption Reason.
<SettlementAmount> Sum of all given discounts that influence the value of 4.2.3.20.3 –
GrossTotal.
<DocumentTotals>
<TaxPayable> Sum of taxes in the document. If the document is not values filled
with "0.00".
<NetTotal> Sum of amounts in the document excluding taxes. If the document

is not valued filled with "0.00".
<GrossTotal> Gross total of the document. If the document is not valued filled
with "0.00".
<Currency>
<CurrencyCode> Similar to 4.1.4.19.4.1 – Currency Code.
54
<CurrencyAmount> Similar to 4.1.4.19.4.2 – Currency Amount.
<ExchangeRate> Similar to 4.1.4.19.4.3 – Exchange Rate.
<WorkingDocuments>
<NumberOfEntries> Total number of documents.
<TotalDebit> Sum of the amounts of tag 4.3.4.11.10 (DebitAmount).
<TotalCredit> Sum of the amounts of tag 4.3.4.11.11 (CreditAmount).
<WorkDocument>
<DocumentNumber> Concatenate "Internal Document Code"||"(Space)"||"Sequence

Identifier"||"/"Document Number".
<DocumentStatus> Should be filled with one of following values:
- "N" - Normal / Normal;
- "A" - Voided / Documento anulado;
- "F" - Already billed / Documento facturado (whenever for

this working document a corresponding document exists in table
4.1).
<WorkStatus>
55
<WorkStatusDate> Date and time of the last update of the document status (YYYY-
MM- DD Thh:mm:ss).
<Reason> This tag is empty.
<SourceID> User identifier of the last status update.
<Source Billing> Possible values are:
-'P' for documents created in EBS;
-'I' for imported documents;
-'M' for invoices created manually outside the system (in paper) and
then replicated in the system.
Values are picked from the Transaction Source GDFF.

<Hash> Certification digital signature. "0" if not digitally signed.
<HashControl> Private key version used to digitally sign the document.
<Period> Period number from 1 to 12.
<WorkDate> Date of the document.
<WorkType> Fixed value "DC" meaning Working Document / Documento de

Conferência.
<SourceID> User identifier of the document creation.
56
<EACCode> This tag contains value of ‘CAE Primary Activity’ Code (CAE)
retrieved from the Legal Entity definition page. ‘CAE Primary activity
code’ Lov values are retrieved from AR_LOOKUPS where
LOOKUP_TYPE is 'LEGAL_ACTIVITY_CODE_PT'.
<SystemEntryDate> Entry date at the time of the document signature generation (YYYY-
MMDD Thh:mm:ss).
<CustomerID> Unique customer identifier (same as 2.2.1 - CustomerID).
<Line>
<LineNumber> Line number (ordered by ascending order).
<OrderReferences> Reference to the source document (same as element 4.1.4.18.2).
<OriginatingON> Link to the order reference.
<OrderDate> Date of the order.
<ProductCode> Link to the product table (element 4.2.2 - ProductCode).
<ProductDescription> Link to the product table (element 4.2.4 - ProductDescription).
<Quantity> Quantity.
57
<UnitOfMeasure> Unit of measure.
<UnitPrice> 0 as Working documents are not valued.
<TaxPointDate> Shipment or service delivery date.
<Description> Description in the document line.
<DebitAmount> 0 as Working documents are not valued.
<CreditAmount> 0 as Working documents are not valued.
<Tax> This structure is filled only if the document is valued, if not it will not
be filled for Working Documents.
<TaxType> Similar to 4.1.4.18.13.1 – TaxType.
<TaxCountryRegion> Similar to 4.1.4.18.13.2 – Tax Country Region.
<TaxCode> Similar to 4.1.4.18.13.3 – Tax Code.
<TaxPercentage> Similar to 4.1.4.18.13.4 – Tax Percentage.
<TaxAmount> Similar to 4.1.4.18.13.5 – Tax Amount.
58
<TaxExemptionReason> Similar to 4.1.4.18.14 – Tax Exemption Reason.
<SettlementAmount> This tag is empty.
<DocumentTotals>
<TaxPayable> Total tax payable – 0 as Working documents are not valued.
<NetTotal> Total net of taxes - 0 as Working documents are not valued.
59
<GrossTotal> Gross total of the document - 0 as Working documents are not

valued.
<Currency> This block will not be exported as Working documents are not
valued.
<CurrencyCode> Similar to 4.1.4.19.4.1 – CurrencyCode.
<CurrencyAmount> Similar to 4.1.4.19.4.2 – CurrencyAmount.
<ExchangeRate> Similar to 4.1.4.19.4.3 – ExchangeRate.
<Payments> Only Receipts with date >= 01-10-2013 is exported.
<NumberOfEntries> Total Number of Receipts exported, including reversed receipts.
<TotalDebit> Sum of the amounts of tag 4.4.4.8.1 (DebitAmount), excluding
values related to reversed documents.
<TotalCredit> Sum of the amounts of tag 4.4.4.8.2 (CreditAmount), excluding
values related to reversed documents.
<Payment> Parent Header tag.
<PaymentRefNo> Concatenates Receipt Payment Type Code||' '||receipt sequence
identifier||'/'||receipt sequential number within the sequence.
Duplicate records are not allowed.
60
<Period> This tag contains the accounting period number.
<TransactionID> Filled with the unique reference of the General Ledger entry used
to post the corresponding entry (TransactionID).
<TransactionDate> Receipt date.
<PaymentType> RC' for VAT Cash Regime ; 'RG' for the basic VAT regime; Vat Cash
Regime is set at customer/receipt level (through DFF’s as
described previously on the DFF’s section).
<Description> Null.
<SystemID> Unique receipt identifier.
<DocumentStatus> Parent tag.
<PaymentStatus> 'N' for Normal, 'A' for canceled or reversed.
<PaymentStatusDate> Date and time of the latest status update "AAAA-MMDDThh:
mm:ss".
<Reason> Reason why the status has been changed.
<SourceID> User identifier of the latest status update.
<SourcePayment> Document source: 'P' for created in EBS ; 'I' for imported receipts
; 'M' for manually issued and later created in the system.
<PaymentMethod> Parent tag
<PaymentMechanism> This is the transaction payment method, which contains a value
based on the DFF Payment Method Information for AR Receipt
Method Information of Receipt class from.
<PaymentAmount> Payment amount in EUR.
61
<PaymentDate> Payment date.
<SourceID> User identifier of latest.
<SystemEntryDate> Date and time of the document creation "AAAA-MMDDThh:
mm:ss".
<CustomerID> Customer identifier (same format as tag 2.2.1).
<Line> Parent Tag.
<LineNumber> In EBS there are no receipt line number. Uses internal number.
<SourceDocumentID> Parent Tag.
<OriginatingOn> Transaction number in the same format as 4.1.4.1 (if the
transaction is in SAFT).
<InvoiceDate> If the receipt application refers to a 4.1.4.1 document enter the
transaction date. If not, enter the application date.
<Description> Null.
<SettlementAmount> Total line discount.
<DebitAmount> Line value excluding taxes and discounts (Debit).
<CreditAmount> Line value excluding taxes and discounts (Credit).
<Tax> Not mandatory. Structure should be filled only for RC receipts
and/or when Tax information exists;
<TaxType> Similar to Tag 2.5.1.1.
<TaxCountryRegion> Similar to Tag 2.5.1.2.
62
<TaxCode> Similar to Tag 2.5.1.3.
<TaxPercentage> Similar to Tag 2.5.1.6.
<TaxAmount> Similar to Tag 2.5.1.7.
<TaxExemptionReason> Similar to Tag 4.1.4.18.14.
<DocumentTotals> Parent Tag.
<TaxPayable> Receipt Total Tax.
<NetTotal> Receipt Net Total (Gross Total – Total Tax).
<GrossTotal> Receipt Gross Total.
<Settlement> Total of payment discounts.
<SettlementAmount> Sum of 4.4.4.14.3.
<Currency> Mandatory if currency!= EUR.
<CurrencyCode> Currency code (3 char).
<CurrencyAmount> GrossTotal in original currency.
<ExchangeRate> Exchange Rate.
63
4.8 Important Notes with regard to SAFT-PT Functionality
 SAFT can be executed by Primary Ledger (Primary Ledger parameter) or Secondary/Consolidated

Ledger (Reporting Ledger). In case of Portuguese Reporting Ledger being other than the Primary
Transactional Ledger, this parameter should be entered.
 All the transactions created in the application must be included on SAFT XML file.
 For mandatory monthly submission on e-fatura site, customers should run the Billing Level or
Integrated Level for single months. It's not supposed to import the SAFT XML executed with the
Accounting level on e-factura link.
 SAFT feature is compliant only with the latest version required by Portuguese Tax Authorities
(version 1.04_01) and the validation should be done against this version.
 SAFT should export disabled accounts, this is part of the designed functionality. Portuguese Tax
Authorities may request SAFT xml file for the last 5 years, so, SAFT program need to export this
account although the account is currently disabled.
 With the new legal requirement it is possible to have tax only lines. We consider a Tax only line
the below scenarios:
• Memo Line created with Memo type = Tax
• Transactions created with Unit Price=0 and Tax Amount <> 0
On both scenarios, SAFT will export the Taxable amount and will export the Unit Price as zero.
64
5. Invoice Printing for Portugal Invoices
In order to fulfill Local business requirements to print Invoices in Portuguese language, Oracle provides
standard invoice printing solution for Portuguese customers.
Once the AR invoice has been created successfully, users can print the same using following steps:
Navigation: View > Requests > Submit a New Request > Single Request
Program: Portugal: Invoice Print Selected Invoices (Multiple Languages)
Enter the transaction details and submit the program.
The program will trigger a child request to generate output in Portuguese language.
Click on View Output to review the details:
65
6. References:
• R12 EMEA Add-on Localizations - Portugal (Doc ID 473622.1)
66

SAFT Functionality For Portugal

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAFT Functionality For Portugal

Uploaded by

Copyright:

Available Formats

EMEA Add-On Localization for Portugal

SAFT Extract File & Invoice Printing

Author: Saurabh Sanklecha

Organization: Oracle India Private Limited.

Date Author Version Change Reference

29-MAR-19 Saurabh 1.0 Initial document

Pawan Panwar Manager, Product Support

Sumit Dhariwal Team Lead

EMEA Add On- Technical Brief for Portugal

EMEA Add On- Technical Brief for Portugal

EMEA Add On- Technical Brief for Portugal

EMEA Add On- Technical Brief for Portugal

DGCA Billing Certification Number for Oracle Applications Release 12 is 1332.

1. Assignment of Concurrent Program to Request Group

a. Go to the responsibility System Administrator.

1. CLE: PT Customer Address Style (CLE: Estilo de Morada do Cliente – Portugal)

List of available values:

S – SNC the entered Chart of Accounts

4. Localization Descriptive Flex fields (LDFFs)

Responsibility: Application Developer

• CLE:Additional Info on Journal Categories

5. Global Descriptive Flex fields (GDFFs)

Responsibility: Application Developer

• JG_RA_CUSTOMER_TRX (Context Code - JE.PT.ARXTWMAI.CLE_SAFT)

6. Define SNC Accounts with LDFF values

7. Define LDFF values at Customer Level

Responsibility: Tax Managers

Define an AR Transaction Source on which SAFT will be applicable.

Define an AR Transaction Type on which SAFT will be applicable.

4.4 Transaction Flow

a. Create an AR Transaction using Transaction Source enabled for SAFT

Line level details

e. Account the Transaction and post entries to GL

Responsibility: General Ledger

Parameter Required Default Description

4.6 File Structure and Reporting Levels

Tag Name Description

<AuditFile> This tag contains the fixed text

<CompanyAddress> This tag contains information of the company address.

<BuildingNumber/> This tag is empty.

<StreetName/> This tag is empty.

<AddressDetail> This tag contains the value of the parameter 'Address'.

<City> This tag contains the value of the parameter 'City'.

<Region> This tag contains the value of the parameter 'Region'.

<Country> This tag contains the value of the parameter 'Country'.

<CurrencyCode> This tag shows the currency as constant value “EUR”.

<HeaderComment> This tag contains the value of the parameter “Comments”.

<Telephone/> This tag contains the value of the parameter 'Telephone'.

<Fax/> This tag contains the value of the parameter 'Fax'.

<Email/> This tag contains the value of the parameter 'Email'.

<WebSite/> This tag contains the value of the parameter 'Website'.

<MasterFiles> Primary files block displays information related to the following

<Customer> This is the customer’s block started tag.

<BuildingNumber/> This is the empty tag.

<StreetName/> This is the empty tag.

<Country> This tag shows a constant value as “PT”.

<ShipToAddress> This is Ship to address element started tag.

<BuildingNumber> This is the empty tag.

<StreetName> This is the empty tag.

<Country> This tag is a constant value as “PT”.

<Telephone/> This tag is the telephone number of the customer.

<Fax/> This tag is the fax number of the customer.

<Email/> This tag is the e-mail of the customer.