Beruflich Dokumente
Kultur Dokumente
ERP CLOUD
Table of Contents
1
Payables .................................................................................................................................................................36
Receivables ............................................................................................................................................................37
6. Modelo Reporting ..............................................................................................................................................38
Turnover Reporting Selection Process ...................................................................................................................38
Turnover Report Parameters .............................................................................................................................39
Modelo 340 ............................................................................................................................................................39
Modelo 340 Report Parameters ........................................................................................................................40
Payables Attributes ............................................................................................................................................41
Receivables Attributes .......................................................................................................................................41
Modelo 347 ............................................................................................................................................................42
Modelo 347 Report Parameters ........................................................................................................................42
Payables Attributes ............................................................................................................................................44
Receivables Attributes .......................................................................................................................................44
Modelo 349 ............................................................................................................................................................45
Modelo 349 Report Parameters ........................................................................................................................45
Payables Attributes ............................................................................................................................................46
Receivables Attributes .......................................................................................................................................46
Modelo 415 ............................................................................................................................................................47
Modelo 415 Report Parameters ........................................................................................................................47
Payables Attributes ............................................................................................................................................48
Receivables Attributes .......................................................................................................................................48
7. Appendix ............................................................................................................................................................49
2
1. Purpose of the document
This document explains the implementation and usage guidelines for the following Modelo reports:
Business purpose, configuration, and transaction attributes for Modelo reporting for Spain concerning:
o Modelo 340
o Modelo 347
o Modelo 349
o Modelo 415
Reporting
The Turnover Reporting Selection Process Selection process extracts transactions from Oracle Fusion
Payables and Oracle Fusion Receivables to be reported by Modelo for the options of invoice and payment
detail for the transactions.
The Modelo Verification Report for Spain lists all payable invoices and receivables transaction reported in
the Modelo 340, 347, 349, or 415 declarations. Modelo reporting is run between a period of time
specified by entry into the period parameters (From and To).
The Modelo Electronic File Generation for Spain Prepares the electronic file for Modelo 340, 347, 349 or
415 declarations.
The four Modelo Types (340, 347, 349, and 415) are based on transactions entered in Payables and Receivables
and selected to a Turnover Reporting Selection Process Data Extract. Transactions entered directly into the Tax
Repository outside of Payables and Receivables are not included in the Turnover Reporting Selection Process
Data Extract.
Proper Transaction Tax set-up (Transaction Business Category, Document Fiscal Classification, User defined Fiscal
Classification), necessary to select the transactions correctly, is a key prerequisite for Modelo reporting. For
Modelo 349 Tax Rule applying proper tax determinants for Intra EU operations is needed. Tax Rule will use Party
Address, Source (Payables or Receivables), Intended Use, and Product Type set-up items to generate proper
values for Transaction Key.
To deliver Modelo reports in Fusion new selection process is delivered: Turnover Reporting Selection Process. This
is a process that transfers key data concerning Modelo transactions to the separate tables to allow different
Modelo Types generation. This is a separate solution described in other documents. The following important
rules apply for this process
1. Turnover Reporting Selection Process is run for a range of dates, selecting all Payables or Receivables
transactions in which either Accounting Date or Transaction Date is within the date range entered as
selection parameter.
3
2. Calendar used for the first run of Turnover Reporting Selection Process in a given year is used for Modelo
reporting for the entire year. It is possible to change the calendar only at year end, after all the periods
for the year are Finally selected.
3. This process is run in Draft and Final mode and allows freezing periods for Modelo reporting. However
it is possible to run Modelo report for next period, even if the previous period was not Finally reported.
When transactions are entered and finally reported for a period, transactions not marked as final in that
period and all newly created transactions are entered in the next period.
4. The process may be re-run for previous months and assures that only not selected transactions will be
added to the transactions pool.
5. It is required that the Turnover Reporting Selection Process will be completed for all the months within
the reported period before a Modelo Electronic File Generation for Spain or Modelo Verification Report
will be run for the period or range of periods. It is a user procedure to verify if all the transactions were
selected for adequate periods by Turnover Reporting Selection Process. Some check will be done at
report parameters entry:
a. The Modelo Verification Report Period parameters only contain values for periods that have
been extracted by the turnover selection process
b. The Modelo Electronic File Generation Year parameter only contains values if one of more
periods for that year are extracted by the turnover selection process.
4
The flow can be summarised as follows:
Correct source
No
data or set-up
Yes
END
(Optional) Run the Generate the
Is the Tax Selection process
verification reports
and store the result
for future reference
Modelo file and
send to Tax
Authorities
Yes
OR
final for all the reported
periods?
No
completed
No
Data Security
Geographies
Enterprise Structure
Tax Regime to Rate
Tax Party Profiles
Tax Rules
Suppliers
Customers
Procurement Business Function
Common Options for Payables and Receivables
5
3. Feature Specific Setup
Note: There is a matrix in the transaction section of this document explaining what setup features will be
incorporated into each Payables and Receivables transaction for proper transaction placement each Modelo
report (Transaction Matrix).
A tax jurisdiction is the geographic area where a tax is levied by a specific tax authority. Jurisdictions are setup
for a tax using geographies or tax zones for the application of surcharges.
Defining Taxes
Setup and Maintenance Manage Taxes
Rate Type Tax Rate
6
Defining Tax Rates
7
Transaction Business Categories are used for determination of the transaction will be reported on the Modelos
340, 347, 349, or 415.
Navigation: Navigator > Setup and Maintenance -> Manage Tax Rates
Tax Rates for Modelo rates need to be updated based on Spanish legislation.
8
Tax Rates for all of Modelo reporting:
9
ES VAT Standard on Services Rate
10
ES RdE STANDARD SERV RATE (Surcharges)
11
Defining Recovery Tax Rates
Setup and Maintenance Manage Tax Rates
Rate Type Tax Recovery Rate
Transaction Business Categories are used for determination of the transaction will be reported on the Modelos
347, 349, or 415.
12
Task name: Manage Transaction-Based fiscal Classifications
Navigation: Navigator > Setup and Maintenance -> Manage Transaction-Based Fiscal Classifications -> Search
For: Transaction Business Category codes
A parent child relationship is configured for the Transaction Business Category Codes prior to transaction
entry. Codes that are the parent or child values in the hierarchy are placed on the Payables or Receivables
transactions. The Fiscal Classification Code Path on each code is picked up by the tax rules marking the
transaction for placement on the correct Modelo report.
The parent column explains which Transactions Business Categories are associated to each application by both
the table SALES for Receivables and PURCHASE for Payables.
For Receivable transactions:
Code Name Parent
B B- MOD347 Deliveries of goods and services above minimum amount SALES_TRANSACTION/INVOICE TYPE/MOD347
F F- MOD 347 Travel Agents Sales: Services documented by means of SALES_TRANSACTION/INVOICE TYPE/MOD347
issued invoices by travel agencies
13
Code Name Parent
B B- MOD415 Deliveries of goods and services above minimum amount SALES_TRANSACTION/INVOICE TYPE/MOD415
14
Code Name Parent
The document fiscal classifications placed on the Payables and Receivable transactions containing 340 are
selected for reporting on the Modelo 340 Report. Inversely, the transactions with the code MOD340_EXCL are
not be picked up for 340 reporting. Those transactions with codes listed as Issued will be placed in the Issued
section of the Modelo 340 and those with Received will be placed in the Received section of the report.
Navigation: Navigator > Setup and Maintenance -> Manage Transaction-Based Fiscal Classifications -> Search
For: Document Fiscal Classification Codes
15
MOD340 Modelo 340 Spain 1-Jan-51
UA UA- Declaration of certain Inter EU Transactions (Type A Sending or Spain 1-Jan-51 MOD340
reception of certain goods)
UB UB- Declaration of certain Inter EU Transactions (Type B Transfers or Spain 1-Jan-51 MOD340
acquisitions of certain goods)
Oracle Applications use the Fiscal Classification (Book Type) as R (Declaration of Received Invoices), for invoices
entered through Oracle Payables and E (Declaration of Issued Invoices), for transactions entered through Oracle
Receivables, therefore there is no further action required.
Invoice Type (Context field) Modelo Document Modelo 340 Transaction Code
340 Fiscal Classification (Book
Type)
Modelo 340 N/A No default Blank
Modelo 349 Yes AR = U Blank
AP = U
Modelo 347 Yes AR = E Blank
AP = R
Modelo 347 Property Rental Yes AR = E Blank
AP = R
Modelo 415 Yes AR = F Blank
AP = S
Modelo 415 and Modelo 347 Yes No default (*) Blank
Modelo 415 and Modelo 347 - Property Rental Yes No default (*) Blank
Party Fiscal Classifications are used to signify which to customers are to have the additional surcharge associated
to Receivables transactions.
16
Assigning Party Fiscal Classifications to Customers
AR_MGR_SPAIN
User-Defined Fiscal Classifications are used to associate the correct purpose of the transaction for the Modelo
340. The values entered in the tax determinants of the Payables and Receivables transactions are category
values supplied by Spanish tax legislation.
17
Navigation: Navigator > Setup and Maintenance -> Manage Transaction-Based Fiscal Classifications -> Search
For: User-Defined Document Fiscal Classification Codes
Fiscal
Classification
Code Fiscal Classification Name Country Start Date
MOD340C C- Invoice with several journals (several tax codes) Spain 1-Jan-51
MOD340G G- Special regime of VAT group entities (includes real counter-assistance to cost) Spain 1-Jan-51
MOD340N N- Invoicing of travel agencies services that act as mediators in name of and on behalf Spain 1-Jan-51
of others
MOD340O O- Invoice issued in replacement of invoices and declared tickets Spain 1-Jan-51
18
Fiscal
Classification
Code Fiscal Classification Name Country Start Date
MOD340Q Q- Special regime of used goods, art, antiques and collection articles Spain 1-Jan-51
MOD340S S- Grants and assistance provided or received by public or private sector entities Spain 1-Jan-51
MOD340T T- Collections on behalf of third parties of professional fees or rights derived from Spain 1-Jan-51
intellectual property, industrial, authoring or others
MOD340W W- Transactions subject to Production, Services and Import Tax to the cities of Ceuta Spain 1-Jan-51
and Melilla
MOD340X X- Agricultural Transactions, having issued the pertinent receipt Spain 1-Jan-51
MOD3402 2: Deferred VAT. Invoice with several journals (several rates) Spain 1-Jan-51
MOD3404 4: Deferred VAT. Acquisitions performed by travel agencies for travelers (special Spain 1-Jan-51
regime of travel agencies)
MOD3407 7: Deferred VAT. Invoicing for services rendered by travel agencies that act as Spain 1-Jan-51
mediators on behalf of someone else
MOD3408 8: Deferred VAT. Business / office space rental transaction Spain 1-Jan-51
Navigation: Navigator > Setup and Maintenance -> Manage Tax Reporting Types
The following Tax Reporting Type/Codes are defined to be associated with the Intra-EU transactions.
19
For Modelo 349:
G (Goods) Payables A
S (Services) Payables I
S (Services) Receivables S
When product type of Goods or Services in combination of Intended-Use of Triangulation is placed on the
transaction will determine which of the above values is placed on the report.
Tax Reporting Codes are used to group transactions for reporting purposes. In this example a tax reporting code
is configured for the INTRA_EU_VAT_TRANSACTION_TYPE. This will allow the reports to be run by Tax
Reporting Code for Modelo 349. The Tax Reporting Code can then be assigned to the tax status that relates to
your transactions.
20
Tax Reporting Type Codes are also defined for Modelo 349 to mark customer transactions with additional
surcharges. EMEA_VAT_REPORTING_TYPE of Services are assigned to the surcharge tax rate.
Triangulation:
If a business is an intermediate supplier to a Spanish buyer of goods purchased from a business in another EU
Member State and that are delivered from there to Spain, VAT due can be accounted for by the Spanish
customer.
Task name: Manage Product-Based Fiscal Classifications
Navigation: Navigator > Setup and Maintenance -> Manage Product-Based Fiscal Classifications Search For:
Intended Use Fiscal Classification Codes
21
The Intended Use Fiscal Classification is placed the appropriate Receivables transactions for the Modelo 349
report.
The ability to add additional property rental attributes to a Receivables transaction is done through seeded
Global Descriptive Flexfields for property localizations.
1. Sales operations concerning goods and services (including domestic, certain Intra-EU and certain IGIC
transactions)
2. Purchases operations concerning goods and services (including domestic, certain Intra-EU and certain
IGIC transactions)
3. Operations relating to property rentals
4. Cash Receipts above a legally set limit - displays the sum of the cash receipts (above minimum
amount) for each Customer, by Cash Received Year (GDF attribute at transaction header level)
Navigation: Navigator > Setup and Maintenance > Manage Receivables Descriptive Flexfields
Descriptive Flexfields are used for Modelo 340, 347, 349, and 415 for Receivables transactions.
22
Field Purpose Modelo Modelo Modelo Modelo
340 347 349 415
Product Type
Oracle supplies lookup codes for GOODS and SERVICES within the lookup type Product Type. The Product
Type value in conjunction with Intended Use is utilized to generate proper values for Transaction Key for Modelo
reporting.
Navigation: Navigator > Setup and Maintenance > Manage Standard Lookups
The Product Type of Goods or Services are used for the Modelo 349.
Tax Status Rules will be configured for Modelo 349 customer transactions. Three condition sets follow for each
of the following:
Goods
Services
Triangulation
24
25
26
27
Place of Supply Rules
Setup and Maintenance -> Manage Tax Rules -> Place of Supply Rules
Change the drop down to Place of Supply Rules to create a new Tax Rule with the following attributes.
28
New Tax Condition Sets need to be added to the Tax Rule. The three condition set attributes follow.
29
30
Tax Registration Rules
Change the drop down to Tax Registration Rules to create a new Tax Rule with the following attributes.
It is important to note that the rule listed below is the ONLY enabled rule. Other registration rules as depicted
below should be disabled. Rules that are defined as ES VAT REGISTRATION should both have an end date and
unchecked for Enabled.
31
32
33
Locations
Property address is defined for each transaction related to property rental and used in Modelo 347 for
transactions related to property rental for 340 and 347 for Receivables transactions.
34
Suppliers
For each supplier to be eligible for Modelo reporting, that Supplier is marked as a registered taxpayer, having
only one Tax Reporting Site. Only one Supplier Site is marked as Federal reportable. The Modelo program
groups transactions by Supplier, Taxpayer Id/ Tax Registration Number. For each group of transactions with
same Taxpayer ID/Tax Reporting Number and Supplier ID, a Tax Reporting Site is recognized (Federal
reportable is checked).
4. Transaction Matrix
For the proper placement on the Modelos, the transactions must contain the correct attributes for accurate
reporting. The tax configuration and transaction attribute values provided by Oracle in the Feature Specific
Setup section of this document are used for the Payables and Receivables transactions.
35
Transaction Attributes 340 347 349 415 Deferred Payables Receivables
Product Type
Tax Rule
Outside
Customer/Supplier Site of Spain
5. Transactions
Payables
The proper attributes determine which report(s) each transaction is reported. The following are fields populated
with proper values and placed on the correct Modelo. Those individual values for the fields on the invoice are in
each report section.
For Supplier transactions to be included in Modelo reporting, the Federal Reportable Flag must be marked.
36
A Payables transaction contains the following attributes:
Receivables
The proper attributes determines which report(s) each transaction is reported. The following are fields
populated with proper values and placed on the correct Modelo. Those individual values for the fields on the
invoice are in each report section.
37
Receivables Values 340 347 349 415
6. Modelo Reporting
A process which prepares data for Modelo reporting. It needs to be run before Modelo reports are generated.
This process applies selection criteria to allow selection of transactions by Accounting Date or Transaction Date
(transactions are selected if any of the dates fall within selection period) , independently from Tax Selection
process. Each Modelo run selects transactions by the appropriate accounting calendar date depending on the
Modelo and Source selection.
38
Navigation: Navigator > Tools -> Scheduled Processes
The Selection Mode is run in Preliminary or Final. If no changes need to be made to the transactions prior to
transmission of the report, the Turnover Reporting Selection Process is run in Final, freezing the transactions for
the period.
Modelo 340
A report showing received and issued transactions: domestic transactions, some Intra-EU operations and
IGIC transactions. Some of the transactions might show up in Modelo 349 or Modelo 415 as well.
39
Modelo 340 Report Parameters
40
Payables Attributes
Field Modelo 340 Values
Document Fiscal Classification E- Declaration of Issued Invoices
F- Declaration of Issued Invoices IGIC
Modelo 340
Exclude from Modelo 340 Declaration
U- Declaration of certain Inter EU Transactions
UA- Declaration of certain Inter EU Transactions (Type A Sending or reception of certain goods)
UB- Declaration of certain Inter EU Transactions (Type B Transfers or acquisitions of certain
goods)
User-Defined Fiscal A- Invoices Summary Journal
Classification Codes
Receivables Attributes
Field Modelo 340 Values
Document Fiscal Classification E- Declaration of Issued Invoices
F- Declaration of Issued Invoices IGIC
Modelo 340
Exclude from Modelo 340 Declaration
R- Declaration of Received Invoices
S- Declaration of Received Invoices IGIC
U- Declaration of certain Inter EU Transactions
UA- Declaration of certain Inter EU Transactions (Type A Sending or reception of certain goods)
UB- Declaration of certain Inter EU Transactions (Type B Transfers or acquisitions of certain
goods)
41
User-Defined Fiscal A- Invoices Summary Journal
Classification Codes
Modelo 347
The Modelo 347 report shows all the domestic and *IGIC Payables and Receivables transaction in a selected
period. Summary by Customer/Supplier.
*IGIC (Impuesto General Indirecto Canario) is a is a state indirect tax levied on the supply of goods or services
supplied by entrepreneurs and professionals made in the Canary Islands and imports of goods in the Territory. It
has a structure and operation similar to VAT. It was established by Law 20/1991, of June 7, amending the tax
aspects of Economic and Fiscal Regime of the Canary Islands (BOE No. 137 of June 8, 1991). It entered into force
on January 1, 1993.
42
43
Payables Attributes
Field Name Parent
Receivables Attributes
Field Name Parent
44
Modelo 349
The Modelo 349 is a summary by supplier of Inter-EC purchases of physical goods. For transactions that correct
previous declarations, the report separately lists the relevant suppliers and invoice amounts with the period and
year of the correction.
45
Payables Attributes
Field Name Parent
Receivables Attributes
Field Name Parent
46
Modelo 415
The Modelo 415 is a summary domestic purchases and sales (both goods and services) in the Canary Islands that
are subject to the Canary Islands transactions.
47
Payables Attributes
Field Name Parent
E- Grants PURCHASE_TRANSACTION/INVOICE
TYPE/MOD415
G Travel Agents Purchases: Services rendered of traveler PURCHASE_TRANSACTION/INVOICE
transportation and their luggage by air travel TYPE/MOD415
Receivables Attributes
Field Name Parent
Business Transaction Code B- Deliveries of goods and services above minimum amount SALES_TRANSACTION/INVOICE
TYPE/MOD415
F- Travel Agents Sales: Services documented by means of SALES_TRANSACTION/INVOICE
issued invoices by travel agencies TYPE/MOD415
48
7. Appendix
Here are some useful information sources to assist with the implementation :
The OER provides content relating to the report parameters and sample report output. Log in as guest
from OER first.
The web site contains links to subscriptions, understanding Oracle Financials Cloud and Implementation
advice.
This document contains additional information relating to this feature and other Fusion Financials
features and capabilities
The web site contains links to spotlights, release content documents, product documentation and
training)
49