Skip Headers

Oracle Financials for Europe User Guide
Release 12.2
Part Number E48767-07
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Oracle Receivables

Using the Customer Interface Program

Use the Customer Interface program to import and validate customer information from other systems. Country-specific global descriptive flexfield content is imported and validated during this process.

You use SQL*Loader, or other import program, to load customer information into the interface tables. When you import customer information, the Customer Interface program validates the global attribute columns in the interface tables and transfers those values into the customer tables.

Before the Customer Interface program can properly validate your data file, you must:

  1. Assign the appropriate context code for your country to the appropriate global attribute category column.

  2. Map your global attribute columns from the interface tables to the corresponding global descriptive flexfield segment columns in the customer tables.

This table shows how the global attribute columns in the interface tables map to the global descriptive flexfield segment columns in the corresponding customer tables:

Interface Table.Global Attribute Column Customer Table.Global Attribute Column
RA_CUSTOMERS_INTERFACE_ALL. GLOBAL_ATTRIBUTE1-20 HZ_CUST_ACCOUNTS. GLOBAL_ATTRIBUTE1-20
RA_CUSTOMERS_INTERFACE_ALL. GDF_ADDRESS_ATTRIBUTE1-20 HZ_CUST_ACCT_SITES_ALL. GLOBAL_ATTRIBUTE1-20
RA_CUSTOMERS_INTERFACE_ALL. GDF_SITE_USE_ATTRIBUTE1-20 HZ_CUST_SITE_USES_ALL. GLOBAL_ATTRIBUTE1-20
RA_CUSTOMER_PROFILES_INT_ALL. GDF_CUST_PROF_ATTRIBUTE1-20 HZ_CUSTOMER_PROFILES. GLOBAL_ATTRIBUTE1-20

After you map your global attribute columns, run the Customer Interface program. The Customer Interface program will:

The following sections describe in detail how to import country-specific attributes into the customer tables in Receivables using the Customer Interface program.

Related Topics

Customer Interface, Oracle Receivables User Guide

Mapping Global Descriptive Flexfield Context Codes

To use the Customer Interface program to import and validate global descriptive flexfield content, you must first assign the appropriate global descriptive flexfield context code for your country to one of the global attribute category columns in the RA_CUSTOMERS_INTERFACE_ALL table.

For a given context code, the Customer Interface program confirms that the values of the global attribute columns in the interface table match the value sets that are defined for the global descriptive flexfield segments in the corresponding customer table. In other words, if the global attribute category has a context code, the required global attribute columns for that country must have the correct data.

For example, if your country is Greece and you want to import information for the JG_HZ_CUST_ACCOUNTS global descriptive flexfield from the interface tables to standard Receivables customer tables, then you must enter the JE.GR.ARXCUDCI.CUSTOMER context code in the GLOBAL_ATTRIBUTE_CATEGORY column and enter either Yes or No in the GLOBAL_ATTRIBUTE1 column.

This table shows you how to map this global descriptive flexfield context code for Greece to the GLOBAL_ATTRIBUTE_CATEGORY column in the RA_CUSTOMERS_INTERFACE_ALL table.

For this country… For this flexfield... Map this global descriptive flexfield context code…
Greece JG_HZ_CUST_ACCOUNTS JE.GR.ARXCUDCI.CUSTOMER

This table shows you how to map these global descriptive flexfield context codes for your country to the GDF_SITE_USE_ATTR_CAT column in the RA_CUSTOMERS_INTERFACE_ALL table.

For this country… For this flexfield... Map this global descriptive flexfield context code…
Greece JG_HZ_CUST_SITE_USES JE.GR.ARXCUDCI.RA
Portugal JG_HZ_CUST_SITE_USES JE.PT.ARXCUDCI.RA

Mapping Global Descriptive Flexfield Segments

Map these global attribute columns in the interface tables to the corresponding global descriptive flexfield segments. For each context code that you assign to a global attribute category column, confirm that the values of the matching global attribute columns are compatible with the designated value sets.

Greece

This table shows the valid values with descriptions for the JE.GR.ARXCUDCI.CUSTOMER Greek context.

Global Descriptive Flexfield: JG_HZ_CUST_ACCOUNTS

Context Code: JE.GR.ARXCUDCI.CUSTOMER

In this column... Oracle Receivables stores... For this location...
RA_CUSTOMERS_INTERFACE_ALL.GLOBAL_ATTRIBUTE1 Public sector company reporting. Valid values are Yes or No. HZ_CUST_ACCOUNTS.GLOBAL_ ATTRIBUTE1

This table shows the valid values with descriptions for the JE.GR.ARXCUDCI.RA Greek context.

Global Descriptive Flexfield: JG_HZ_CUST_SITE_USES

Context Code: JE.GR.ARXCUDCI.RA

In this column... Oracle Receivables stores... For this location...
RA_CUSTOMERS_INTERFACE_ALL.GDF_SITE_USE_ATTRIBUTE1 Receipt acknowledgment designation. Valid values are Yes or No. HZ_CUST_SITE_USES_ALL.GLOBAL_ ATTRIBUTE1

Portugal

This table shows the valid values with descriptions for the JE.PT.ARXCUDCI.RA Portuguese context.

Global Descriptive Flexfield: JG_HZ_CUST_SITE_USES

Context Code: JE.PT.ARXCUDCI.RA

In this column... Oracle Receivables stores... For this location...
RA_CUSTOMERS_INTERFACE_ALL.GDF_SITE_USE_ATTRIBUTE1 Receipt acknowledgment designation. Valid values are Yes or No. HZ_CUST_SITE_USES_ALL.GLOBAL_ ATTRIBUTE1

Customer Interface Transfer Report

Each time you run Customer Interface program, Receivables generates the Customer Interface Transfer report. If any validation fails, the Customer Interface program populates the INTERFACE_STATUS column in the interface tables with the concatenated error codes for the Customer Interface Transfer report. This report shows the rows with problems and related error descriptions.

Related Topics

Customer Interface Transfer Report, Oracle Receivables User Guide

Using the AutoInvoice Interface Program

The RA_INTERFACE_LINES_ALL interface table stores invoice information. You use SQL*Loader to load invoice information into the interface table for each invoice that you create.

When you initiate importing invoices, the AutoInvoice open interface validates global attribute columns in the RA_INTERFACE_LINES_ALL table according to country-specific requirements. AutoInvoice then transfers global attribute columns from the RA_INTERFACE_LINES_ALL table to the RA_CUSTOMER_TRX_ALL table and the RA_CUSTOMER_TRX_LINES_ALL table.

Before the AutoInvoice program can properly validate your data file and create invoice and invoice lines in Oracle Receivables, you must:

  1. Assign the appropriate context code for your country to the appropriate global attribute category column

  2. Map your global attribute columns from the interface table to the corresponding global descriptive flexfield segment columns in the transaction tables

This table shows how the global attribute columns in the interface table maps to the global descriptive flexfield segment columns in the corresponding transaction tables:

Interface Table.Global Attribute Column Transaction Table.Global Attribute Column
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE1-30 RA_CUSTOMER_TRX_ALL. GLOBAL_ATTRIBUTE1-30
RA_INTERFACE_LINES_ALL. LINE_GDF_ATTRIBUTE1-20 RA_CUSTOMER_TRX_LINES_ALL. GLOBAL_ATTRIBUTE1-20

Related Topics

Importing Invoice Information Using AutoInvoice, Oracle Receivables User Guide

Mapping Global Descriptive Flexfield Context Codes

To use the AutoInvoice program to import and validate global descriptive flexfield content, you must first assign the appropriate global descriptive flexfield context code for your country to one of the global attribute category columns in the RA_INTERFACE_LINES_ALL table.

For a given context code, the AutoInvoice program confirms that the values of the global attribute columns in the interface table match the value sets that are defined for the global descriptive flexfield segments in the corresponding transaction tables. In other words, if the global attribute category has a context code, the required global attribute columns for that country must have the correct data.

This table shows you how to map these global descriptive flexfield context codes for your country to the HEADER_GDF_ATTR_CATEGORY column in the RA_INTERFACE_LINES_ALL table.

For this country… For this flexfield... Map this global descriptive flexfield context code…
Poland JG_RA_CUSTOMER_TRX JE.PL.ARXTWMAI.TAX_DATE
Spain JG_RA_CUSTOMER_TRX JE.ES.ARXTWMAI.MODELO347PR
Spain JG_RA_CUSTOMER_TRX JE.ES.ARXTWMAI.MODELO349
Spain JG_RA_CUSTOMER_TRX JE.ES.ARXTWMAI.MODELO415_347PR

Mapping Global Descriptive Flexfield Segments

Map these global attribute columns in the interface table to the corresponding global descriptive flexfield segments. For each context code that you assign to a global attribute category column, confirm that the values of the matching global attribute columns are compatible with the designated value sets.

Poland

This table shows the valid values with descriptions for the JE.PL.ARXTWMAI.TAX_DATE Polish context.

Global Descriptive Flexfield: JG_RA_CUSTOMER_TRX

Context Code: JE.PL.ARXTWMAI.TAX_DATE

In this column… Oracle Receivables stores… For this location…
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE3 Bank account number. The value set for this segment is JGZZ_AR_BANK_ACT_NUM. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE3

Spain

This table shows the valid values with descriptions for the JE.ES.ARXTWMAI.MODELO347PR Spanish context.

Global Descriptive Flexfield: JG_RA_CUSTOMER_TRX

Context Code: JE.ES.ARXTWMAI.MODELO347PR

In this column… Oracle Receivables stores… For this location…
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE2 Rental location. The value set for this segment is JEES_RENTED_LOCATION. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE2

This table shows the valid values with descriptions for the JE.ES.ARXTWMAI.MODELO349 Spanish context.

Global Descriptive Flexfield: JG_RA_CUSTOMER_TRX

Context Code: JE.ES.ARXTWMAI.MODELO349

In this column… Oracle Receivables stores… For this location…
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE3 Correction year. The value set for this segment is JEES_YEARYYYY. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE3
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE4 Correction period. The value set for this segment is JEES_PERIOD_349. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE4

This table shows the valid values with descriptions for the JE.ES.ARXTWMAI.MODELO415_347PR Spanish context.

Global Descriptive Flexfield: JG_RA_CUSTOMER_TRX

Context Code: JE.ES.ARXTWMAI.MODELO415_347PR

In this column… Oracle Receivables stores… For this location…
RA_INTERFACE_LINES_ALL. HEADER_GDF_ATTRIBUTE2 Property location. The value set for this segment is JEES_RENTED_LOCATION. RA_CUSTOMER_TRX_ALL.GLOBAL_ATTRIBUTE2

Bills of Exchange

In Release 12, you cannot create new bills of exchange automatic receipts. You can continue to remit previously existing bills of exchange receipts using these Bills of Exchange receipt formats:

Italian Remittance EFT Format

Use the Italian Remittance EFT Format to produce a file that contains an automatic remittance for bills of exchange Italy for the open bills of exchange. This remittance format is sent to the bank to initiate the transfer of funds.

This EFT format is made up of a header record, detail records that describe the receipts, and an end record.

This table is a summary of the detail records:

Record Type Description
14 Receipt Details
20 Supplier Name
30 Customer Name
40 Customer Address
50 Invoice Details
51 Supplier Details
70 Additional information for the bank

You can generate the Italian Remittance EFT Format by running the Italian Remittance EFT concurrent program once the Remittance batch has been approved.

Regional and Country Reports

Regional Invoice Format

For the Czech Republic, Hungary, and Poland, use the Regional Invoice Format to print all Receivable documents for a given document type, document number range, and customer name. To assist in packaging and delivering your billings, you can order your printed transactions by document number, customer name, or postal code.

Based on your responsibility, you may print either original or duplicate invoice documents.

Use the Standard Request Submission windows to submit the Regional Invoice Format.

Setting Up the Duplicate Profile Option

For the Czech Republic, Hungary, and Poland, set the JG: Duplicate profile option at the responsibility level. This profile option value populates the Duplicate parameter in the Regional Invoice Format. The parameter lets you print either original or duplicate Receivables documents based on the profile option setting for your responsibility.

Prerequisites

Before running the Regional Invoice Format, you must complete these tasks:

Assign Product Fiscal Classifications to Items and Tax Product Categories to Memo Lines

You can assign product fiscal classifications to inventory items or tax product categories to standard memo lines, to represent statistical codes as determined by the Hungarian or Polish government.

Define Transaction Types

When you define transaction types for the Czech Republic, Hungary, or Poland, ensure that your naming standards comply with official document types as printed on the invoice.

Report Parameters

Order By

Enter one of the following:

The default is Transaction Number.

Batch (for the Czech Republic only)

Enter the batch number for the invoices you want to report on.

Document Type

Enter one of the active transaction types defined in Oracle Receivables.

Invoice Number Low

Enter the lowest invoice number that you want to print.

Invoice Number High

Enter the highest invoice number that you want to print.

Invoice Date Low

Enter the earliest invoice date that you want to print.

Invoice Date High

Enter the latest invoice date that you want to print.

Customer Name

Enter a specific customer name or leave this parameter blank for all customers.

Report Headings

In this heading… Oracle Receivables prints…
Bill To The billing site customer name, address, tax registration number, and purchase order number
Ship To The shipping site address
Remit To Your company's name, remittance address, tax registration number, and company number
VAT Date The tax invoice date
Invoice Date The invoice date
Invoice Num The invoice number
Invoice Type The name of the transaction type

Column Headings

In this column… Oracle Receivables prints…
Num The line number of the invoice.
Description The line item description.
Item Code The item statistical code associated with the line item. This column is not used in the Czech Republic.
UOM The unit of measure for a given line.
Unit Price The unit selling price of the line item.
Qty The quantity billed of the item.
Amount The net invoice line amount
VAT% The tax rate for any tax rate codes that do not have a zero rate. The report prints the tax name for any tax rate codes that have a zero rate.
VAT The VAT amount for the invoice line.
Total The total invoice line amount.
VAT by Rate Amount The total net invoice amount for each tax rate.
VAT by Rate VAT% The tax rate for any tax rate codes that do not have a zero rate. The report prints the tax name for any tax rate codes that have a zero rate.
VAT by Rate VAT The total tax amount for each tax rate.
VAT by Rate Total Amount The total invoice amount for each tax rate.
Invoice Amount The total invoiced amount.
In Words The total invoiced amount in words.
Payment Terms The payment terms for the invoice
Due Date The due date for the invoice.
Invoice Amount The total invoiced amount.
Curr The currency of the invoice.
Remittance Bank The remittance bank name.
Branch The remittance bank branch.
Bank Num The remittance bank number.
Bank Account Num The remittance bank account number.
Issuer A line for the issuer's signature.
Receiver A line for the receiver's signature.
Comments Optional additional invoice information.

Related Topics

Running Reports and Programs, Oracle Applications User Guide

Receipt Acknowledgment Letter

Use the Receipt Acknowledgment Letter report to confirm the receipt of any payment from a customer.

Note: This functionality is only used and active for Greece and Portugal.

Oracle Receivables produces a separate receipt acknowledgment for each receipt currency. You can produce:

You can match a receipt in a different currency to the invoice that the receipt is applied to when you manually enter a receipt.

Use the Standard Request Submission windows to submit the Receipt Acknowledgment Letter report.

Prerequisites

Before submitting the Receipt Acknowledgment Letter report, you must:

Related Topics

Running Reports and Programs, Oracle Applications User Guide

Defining Document Categories, Oracle Applications System Administrator's Guide

Defining a Document Sequence, Oracle Applications System Administrator's Guide

Assigning a Document Sequence, Oracle Applications System Administrator's Guide

Regional Dunning Letter

Use the Regional Dunning letter as a statement that you can send to customers advising them about open balances.

Use the Standard Request Submission windows to submit the Regional Dunning letter.

Prerequisites

To use the Regional Dunning letter, you must set up at least one dunning letter in the Dunning Letters window. Specify &F_AS_OF_DATE in the message text for the as of date and &F_TOTAL_BALANCE in the message text for the customer site total balance in the ledger currency.

Parameters

As of Date

Enter the effective date of the letter.

Dunning Letter

Choose the dunning letter that you would like to send.

Customer From

Enter the customer that you would like to run the letter from.

Customer To

Enter the customer that you would like to run the letter to.

Currency Code

Choose the currency for the letter.

Include Receipts at Risk

Choose Yes to include receipts at risk in the letter. Choose No not to include at risk receipts.

Report Headings

This table shows the report headings.

In this heading... Oracle Receivables prints...
Customer The customer's name
Tax ID The customer's tax identification number
Customer Site The customer's bill to site
<Note to Customer> The user-defined note that you specified in the dunning letter that you choose

Column Headings

This table shows the column headings.

In this column... Oracle Receivables prints...
Invoice Number The invoice number for this transaction. Only invoices with outstanding balances are printed.
Invoice Date The date of the invoice.
Invoice Type The type of the invoice.
Original Amount The original amount of the transaction in the entered currency. The currency code for the entered currency is shown in parentheses.
Amount Due Remaining The remaining amount due of the transaction in the entered currency. The currency code for the entered currency is shown in parentheses.
Original Amount The original amount of the transaction in the ledger currency. The currency code for the ledger currency is shown in parentheses.
Amount Due Remaining The remaining amount due of the transaction in the ledger currency. The currency code for the ledger currency is shown in parentheses.
Due Date The date that the transaction balance is due.
Days Late The number of days that payment of this invoice is overdue. A negative number indicates that the payment is not yet due.

Related Topics

Running Reports and Programs, Oracle Applications User Guide

Portuguese Receivables Taxpayer ID Exception Report

Use the Portuguese Receivables Taxpayer ID Exception report to produce a list of all customers without a taxpayer ID. You can run this report by the legal entity, ledger, or balancing segment value. The report only selects the suppliers for whom you inserted at least one transaction.

Use the Standard Request Submission windows to submit the Portuguese Receivables Taxpayer ID Exception report.

Prerequisites

Add a Legal or Contencioso line in each Customer Business Purpose Address Site.

Report Headings

In this heading… Oracle Receivables prints…
<Report Title> Portuguese Receivables Taxpayer ID Exception Report
Report Date The date that the report is run
Page The current and total pages of the report

Column Headings

In this column… Oracle Receivables prints…
Customer Name The customer's name
Customer Number The customer's number

Related Topics

Running Reports and Programs, Oracle Applications User Guide

Portugal - Import Externally Signed Transactions

Overview

Portuguese legislation requires all billing invoices to be reported as part of SAFT, regardless of where they were issued, along with their original electronic signature. Therefore, externally generated invoices created and signed outside Oracle E-Business Suite must be imported “as is”. The Oracle E-Business Suite does not regenerate the signature.

The Oracle E-Business Suite's Financials for Portugal complies with this legislation by meeting the following requirements:

Solution Components

The following components enable the import of externally signed transactions for Portugal.

Setup Steps

STEP 1 – Set Up the Sequential Numbering Profile Option

STEP 2 - Activate Document Sequence at the Transaction Completion Time

STEP 3 - Define Document Sequences

Additional Information: You must define different sequences to differentiate between internally signed transactions versus externally signed ones.

Important: Refer to the Oracle Receivables Implementation Guide for information about document sequence definition.

STEP 4 - Assign Document Sequence at Transaction Type level

Transaction types that that are eligible for signature generation must be assigned with a sequential, gapless numbering sequence. This is achieved by assigning a sequence to a Category via the Document Assignments window. Before assigning Sequences to Categories, you must define the Categories; they indicate the table name where the sequence is enabled.

Additional Information: You must define different Categories and assign distinct Sequences to each one of them.

STEP 5 - Set Up Manual and Imported Transaction Sources

This is an existing setup for Internally Signed Transactions:

For Externally Signed Transactions with the Already Billed checkbox set to Yes:

Additional Information: The system must be configured so that all batch sources used for a given transaction type have the same setup for the Already Billed GDF.

Tip: For a detailed explanation see Portuguese Billing Software Certification.

Transactions Entry

Externally Signed Transactions (for example, Already Billed set to Yes) are imported as completed transactions and do not trigger the signature generation process. These transactions cannot be incompleted or updated. You cannot incomplete the transaction or make any changes to it, because it may invalidate the signature imported from the legacy system.

Additional Information: Completed and signed transactions cannot be incompleted and/or changed. Use the Credit Memo type VOID functionality to cancel a transaction, whenever necessary.

Incomplete Process

Completed and signed transactions (whether the signature was generated by the Oracle E-Business Suite or imported from external sources) cannot be incompleted. This is to prevent signature issues because neither the document sequence nor the data elements involved can change in the signature generation

For these cases, the following warning message appears: “Transaction cannot be incomplete because an encrypted signature has been assigned to it. Use Credit Memo Void functionality to cancel this transaction and enter a new one, if necessary.”

Autoinvoice

You must populate the newly introduced columns in the extension interface table JE_PT_INTERFACE_LINES_EXTS to import the externally certified transactions, including the signature, certificate number and related elements.

Refer to Appendices I and II for more details about the import process and respective data model changes.

Important: You must populate all records of a transaction with the same Signature information in the extension table. The system takes the Signature information from the lowest interface_line_id.

Additional Information: When importing invoice information from Legacy Systems through AutoInvoice, you must load the Signature and related elements into the extension table JE_PT_INTERFACE_LINES_EXTS and populate the link column JE_PT_INTERFACE_LINK_ID with the ROWID from RA_INTERFACE_LINES_ALL.

Additional Information: When entering inconsistent information, the system will take the signature related information from the lowest interface_line_id without any cross-checking validation. It is your responsibility to populate the interface table correctly.

Copy Transactions (when source is an externally signed transaction)

The signature and related elements will NOT be copied from the source transaction to target transaction.

Create Invoice API/Create Credit Memo API

This processes uses the JE_PT_TRX_API_EXT_T, which is a temporary table introduced to capture the Signature details at the header level when creating externally signed transactions via the Create Invoice API or Create Credit Memo API.

Refer to Appendices I and II for more details.

Additional Information: When importing invoice information from Legacy Systems through the Create Invoice API/Create Credit Memo API, you must load the Signature and related elements into the extension table JE _PT_TRX_API_EXT_T and populate the TRX_HEADER_ID column for the Invoice API and populate the PREVIOUS_CUSTOMER_TRX_ID column for the Credit Memo API.

Italian B2G Electronic Invoicing

Overview

The Italian Law 244/2007 states that all invoices issued against all Italian public sector entities must be electronic and the electronic invoices must guarantee the issued date, the authenticity of the origin and integrity of the content by means of digital signature and time reference.

Technical Standards published by the Italian authority:

  1. All invoices issued against the Italian public sector entities must be in the XML format as defined by the Italian authorities;

  2. The electronic invoices must be transmitted to the Exchange System which collects and distributes the electronic invoices to the appropriate entity;

  3. Each public sector entity is identified by a receiver code.

Before reading this section, refer to the Italian B2G Electronic Invoicing Appendix.

Process Components

The Italian B2G Electronic Invoicing process includes the following components:

Process Flow

The Italian B2G Electronic Invoicing process includes the following steps:

  1. Define or update Legal Entity by setting up the newly introduced attributes (one-time setup);

    1. This information is reported in the First Party Identification a. section;

    2. Example: Fiscal Regime, REA Number, Share Capital, Single Member, etc..

  2. Define or update Bill-To sites by assigning the newly introduced B2G Bill-to Received Code;

  3. Define or implement the Descriptive Flexfield (DFF) segments at the invoice header and/or line levels in order to handle the additional pieces of information required, if applicable (Example: Withholding, Stamp Duty, etc.)

  4. Perform the eventual changes to the default XML template in order to include or exclude the additional pieces of information required, if applicable (Example: Withholding, Stamp Duty, etc).

  5. Enter and complete the B2G Receivables transactions (Example: invoices, credit memos, debit memos, etc.);

  6. Run the Italian B2G Electronic Invoices Generation for a given Customer Bill-to site, Transaction Number or Date Range.

    1. Verify the accuracy of the XML output file.

    2. Repeat Step 6 as necessary by making sure the B2G Electronic Invoice Generation Option is entered properly (Example: Original generation or regeneration).

  7. Name the XML output file as per the naming convention defined by the Italian Exchange System.

  8. Execute the next steps required: Apply a qualified electronic signature, transmit the signed XML, and electronically store the signed XML file.

Setup Steps

The following setup steps must be performed before entering new Receivables B2G transactions:

STEP 1 - Define/Update Legal Entity Reporting Attributes (Mandatory)

Five new attributes have been introduced as part of the Legal Entity´s Identification Information region. Those attributes are required to generate the B2G electronic Invoice and are reported under the first party identification section of the XML layout.

STEP 2 - Assign Received Code to B2G Bill-to Sites (Mandatory)

The attribute B2G Bill-to Received Code was introduced in the Account Site´s Business Purpose tab. This attribute is required to generate the B2G electronic Invoice and is reported under the Transmission Identification section of the XML layout.

Transaction Entry

New Global Descriptive Flexfields were added at the header level for the Receivables B2G transactions to capture some important reporting information and the electronic invoice status. The attributes are available and handled by the following transaction entry flows:

Receivables

The newly added Global Descriptive Flexfields are:

Manually Entered Transactions

New Global Descriptive Flexfields were added at the transaction header level. They can be viewed and optionally updated.

Imported Transactions

The newly added header level invoice attributes can also be imported by populating the corresponding Global Attribute columns in the following interface table:

Table: RA_INTERFACE_LINES_ALL

GDF Context: JE.IT.ARXTWMAI.INVOICE_INFO

New Attribues Mapped Global Attribute Values to be Populated
B2G Electronic Invoice Document Type Header_GDF_Attribute7 TD01, TD04, TD05
(Example: most common Receivables transactions)
B2G Electronic Invoice Status Header_GDF_Attribute8 NULL, GEN, TRAN, REJ, FAIL, REC, ACC, REF, UND, PASS
(see lookup codes seeded in JEIT_B2G_INV_STATUS)
B2G Transmission Progressive Number Header_GDF_Attribute9 (DO NOT POPULATE)
This field is populated automatically by the Concurrent Program.

Concurrent Programs

Italian B2G Electronic Invoices Generation

You can run the Italian B2G Electronic Invoices Generation concurrent program at any time to generate one of more electronic invoices (in XML format) belonging to the LE running the program, according to the selection criteria. The program is responsible for extracting the data according to the selection criteria provided in the Parameters window. If successful, the program will launch another concurrent program, Italian B2G Electronic Invoices XML File Output, that will actually generate the output file in XML format.

Parameters:

B2G Electronic Invoice Number of Invoices per File

Use One Invoice per File when there are just a few invoices in the selected date range. Otherwise, the Italian B2G Electronic invoices XML File Output concurrent program will spawn multiple times and you will have to save all output files.

When the program is entered without entering the transaction number, it is recommended to use the Multiple Invoices per File option. In this case, only one output file is generated with all invoices that fall in the date range.

Electronic Invoice Regeneration Scenarios

Scenario 1 - The electronic file is lost

To regenerate the same electronic file, you can run the program by selecting the option Regeneration with same Transmission Progressive Number and by entering the Transmission Progressive Number parameter.

Scenario 2 - Single invoice rejected from a file with multiple invoices

You can run the program by selecting the option Regeneration with new Transmission progressive Number and by entering the required transaction number.

Spanish B2G Electronic Invoicing

Overview

Oracle has modified the Oracle E-Business Suite and Oracle Financials for Spain to comply with the Spanish B2G Electronic Invoicing legislation. The solution meets the following requirements:

In Spain, electronic invoices are regulated by Royal Decree 1619/2012. The law 25/2013 of December 27 later imposed electronic invoicing as the sole invoicing method to be used by organizations and professionals when issuing invoices against all Spanish public sector entities.

Order HAP/1074/2014 of June 24 defines the latest technical and functional requirements of electronic invoices.

This documentation describes the solution provided to comply with the Spanish B2G Electronic Invoicing requirements on the sales invoice side (example: Oracle Receivables).

Seeded Lookups

Lookup Type: JEES_B2G_INV_STATUS (seeded, non user-definable)

Description: Spanish B2G Invoice Statuses

Code Meaning Description
CAN Cancelled Cancelled
GEN Generated Generated
TBR To Be Regenerated To Be Regenerated
TRAN Transmitted Transmitted
ACC Accepted Accepted
REF Refused Refused

Additional Information: This lookup type is not user-definable to preserve the invoice status consistency checks (refer to the Invoice Status Transition Scenarios for details).

LLookup Type: JEES_B2G_ NUM_INVOICES (seeded, non user-definable)

Description: Spanish B2G Number of Invoices per File

Code Meaning Description
1 One One Invoice Per File
2 One or More One or More Invoices Per File

LLookup Type: JEES_B2G_ ISSUER_TYPE (seeded, user-definable)

Description: Spanish B2G Document Type

Code Meaning Description
EM Issued by Company Invoice Issued by Company
RE Issued by the Receiver Invoice issued by the Receiver
TE Issued by an Intermediary Invoice issued by an Intermediary

LLookup Type: JEES_B2G_DOC_TYPE (seeded, non user-definable)

Description: Spanish B2G Document Type

Code Meaning Description
FC Complete Invoice Complete Invoice
FA Abbreviated Invoice Abbreviated Invoice
AF Self Invoice Self Invoice

LLookup Type: JEES_B2G_ GEN_OPTIONS (seeded, non user-definable)

Description: Spanish B2G Generation Options

Code Meaning Description
O Original Original
C Copy Copy of Original Accepted

LLookup Type: JEES_B2G_ INV_TYPE (seeded, non user-definable)

Description: Spanish B2G Invoice Class

Code Meaning Description
O Original Original
R Corrective Corrective
C Consolidated Consolidated

Lookup Type: JEES_B2G_ REASON_CODES (lookup codes not seeded, user-definable)

Description: Spanish B2G Reason Codes

The Codes and Description must be defined by the user (example: legal content):

LLookup Type: JEES_B2G_CORR_METHODS (seeded, user-definable)

Description: Spanish B2G Correction Methods

Code Meaning Description
01 Full items Full items
02 Corrected items only Corrected items only
03 Bulk deal Bulk deal in a given period
04 Authorized Authorized by the Tax Agency

Spanish B2G Electronic Invoicing Process

The Spanish B2G Electronic Invoicing Process includes the following:

  1. Review and update the Legal Entity information that must be reported under the Seller Party section.

  2. Perform the required one-time setup (example: Lookups, Reporting Types and Codes);

  3. Enter and complete B2G Receivables transactions (example: invoices, credit memos);

  4. Run the Spanish B2G Electronic Invoices Generation program as per the parameters criteria:

  5. Name the XML output file as per the naming convention defined by the Spanish Government;

  6. Execute the next steps (outside of the Oracle E-Business Suite solution):

Setup Steps

The following setup steps must be performed prior to entering new Receivables B2G transactions.

STEP 1 - Define Lookup Codes for the Following Seeded Lookup Type (Mandatory)

Lookup Type: JEES_B2G_ REASON_CODES (codes not seeded, user-definable)

Description: Spanish B2G Reason Codes

Additional Information: Lookup Codes, Meaning, and Description must be defined by the user (example: obtain legal content from Spanish Authority).

Example:

Codes from '01' to '16' errors according to regulation RD 1496/2003

Codes from '80' to '85' errors are according to Art. 80 Law 37/92 on the VAT.

STEP 2 - Define/Update Legal Entity Attributes (Mandatory)

Review and update (if required) the attributes that are reported under the <SellerParty> section of the XML file, such as Taxpayer ID, Corporate Name, and Address information.

STEP 3 - Define Tax Reporting Types and Codes (Mandatory)

The overall setup for the Spanish B2G solution assumes you are using Oracle E-Business Tax to define two specific Tax Reporting Types and respective Tax Reporting Codes that can be associated with the appropriate taxes and ultimately reported as part of the Tax sections of the XML file.

Within Oracle E-Business Tax, navigate to the Default and Controls tab and define two Tax Reporting Types and their respective Reporting Codes as follows:

B2G_TaxTypeCode - (Define Reporting Type and Codes, and Enable at Tax level)

Taxes are reported by TaxTypeCode, which are specific codes defined by the Spanish Authority (example: '01' = IVA). Define those codes as Tax Reporting Codes and associate them with the all Spanish taxes (example: IVA) that are required to be reported in the Spanish B2G XML file.

B2G_Additional_Info - (Define Reporting Type and Codes, and Enable at Tax Level)

When a transaction is 'not liable for tax' or 'exempt from tax', this justification must be reported under XML elements 3.1.9 and 3.1.9.3. Therefore, the association of the Tax Reporting Code belonging to the 'B2G_Additional_Info' Reporting Type to relevant Taxes is conditionally required; it is only required if this situation happens

The 'Description' field of the Tax Reporting Code belonging to the 'B2G_Additional_Info' Reporting Type is the actual text that appears in XML element 3.1.9.3, if the Tax Reporting Code was previously associated with the reported Tax.

Using the same page flow (demonstrated above), define the Tax Reporting Type 'B2G_Additional_Info', its corresponding Tax Reporting Codes, and enable it at the Tax level.

Additional Information: Both Tax Reporting Types ('B2G_TaxTypeCode' and 'B2G_Additional_Info') must be enabled at the 'Tax' level only.

Associate Tax Reporting Codes with Required Taxes

Within Oracle E-Business Tax, navigate to the Tax Configuration tab, and then the Taxes sub tab. Search for the desired Tax (example: IVA). Navigate to the Tax Reporting Codes region and locate the B2G Reporting Types (example: B2G_TAXTYPECODE) and ultimately make the association between the Tax and the Reporting Code value required for that Tax.

Additional Information: The association of Tax Reporting Codes belonging to B2G_TaxTypeCode with the appropriate Taxes is a mandatory setup step to have required tax information properly reported by TaxTypeCode. Refer to Spain Appendix for tax reporting details.

Transaction Entry

New Global Descriptive Flexfields were added at the header level for the Receivables B2G transactions, to capture important reporting information and the electronic invoice status.

The attributes are available and handled by the following transaction entry flows:

Receivables

The new Global Descriptive Flexfields are:

Manually Entered Transactions

The new Global Descriptive Flexfields were added at the transaction header level. They can be viewed and updated.

Imported Transactions

The new header level invoice attributes can also be imported by populating the corresponding Global Attribute columns in the following interface table:

Table: RA_INTERFACE_LINES_ALL

GDF Contexts:

New Attributes Mapped Global Attribute Values to be Populated
B2G Electronic Invoice Status Header_GDF_Attribute16 NULL, CAN, GEN, REF, TBR, TRAN, ACC
(Refer to the lookup codes in JEES_B2G_INV_STATUS)
Values: O, R or C
B2G Electronic Invoice Type Header_GDF_Attribute1 (Refer to the lookup codes in JEES_B2G_INV_TYPE)
Values: FC, FA or AF
B2G Electronic Invoice Document Type Header_GDF_Attribute17 (Refer to the lookup codes in JEES_B2G_DOC_TYPE)
B2G Electronic Invoice Language Header_GDF_Attribute18 Value ES for Spanish language
Values: <user definable as per legislation>
B2G Correction Invoice Reason Code Header_GDF_Attribute19 (Refer to the lookup codes in JEES_B2G_REASON_CODES)
Values: 01,02,03,04
B2G Correction Method Header_GDF_Attribute20 (Refer to the lookup codes in JEES_B2G_CORR_METHODS)

Concurrent Programs

Spanish B2G Electronic Invoices Generation

The Spanish B2G Electronic Invoices Generation' concurrent program was added under the Spanish AR Localizations responsibility. You can run it at any time to generate one of more electronic invoices (in XML format) belonging to the LE running the program, according to the selection criteria.

The program extracts the data according to the selection criteria provided in the Parameters window. If successful, the program will launch another concurrent program, Spanish B2G Electronic Invoices XML File Output, that actually generates the output file in a XML format

Parameters
Parameter Description
Legal Entity First Party Legal Entity, owner of the B2G sales transaction. The first party information is reported in the Seller section of the XML output file.
Invoice Issuer Type Select from the list of values. Default value: Issued by the Company
Customer Name -
Customer Bill To Site The XML file is generated per Customer Bill To Site
B2G Electronic Invoice Generation Option Select from the list of values. Default Value: Original

Additional Information: Select Copy upon request, to generate a copy of an Electronic Invoice already submitted and marked as Accepted.

Transaction Date From -
Transaction Date To -
Number of Invoices per File Select either: 1- One invoice per file, or 2 - One or More Invoices per file, from the list of values
When the B2G Electronic Invoice Generation Option is equal to Copy, the value 1 is defaulted and cannot be changed.
Transaction Number When the B2G Electronic Invoice Generation Option is equal to:
Original: The list of values displays completed invoices where the invoice status is either equal to NULL or To Be Regenerated.
Copy: The list of values displays completed invoices where the invoice status is equal to Accepted.
Maximum Number of Invoices per File Enabled if Number of Invoices per File is equal to 2 (One or More Invoices per File). The defaulted and maximum allowed value is 100.
If there are more eligible transactions than Maximum Number of Invoices per File, the log file shows the following message:
The reporting criteria provided identified more eligible invoices than the maximum number of invoices per file. Run the Concurrent Program again to report remaining invoices in a separate file.

User Procedures

Below is an outline of the complete list of user procedures related to the Spanish B2G Soluution

Refer to Setup Steps for more detail on some of these procedures.

1 - Manually Update the Electronic Invoice Status

For each XML message received from the Government, you should manually update the Electronic Invoice Status (GDF at the invoice header level) to ensure that the latest status is captured.

2 - File Naming

Name and save the Output file in your local directory. The file name must follow the instructions provided by the Spanish Public Administration.

3 - Daily Exchange Rate

Define and maintain Daily Exchange Rate details, according to government exchange rate guidelines.

4 - Steps to Cancel an Erroneous B2G Invoice and Prevent Both Invoice and Credit Memo from Being Reported

  1. Retrieve the B2G invoice to be cancelled and set the invoice status to CANCELLED, to prevent the invoice from being selected.

  2. Enter a Credit Memo (type VOID) against that B2G invoice and set the Credit Memo invoice status to CANCELLED, to prevent the Credit Memo from being selected.

5 - Setup Steps to Define Tax Reporting Types, Tax Reporting Codes and Associate Them at the Tax Level

Refer to Setup Steps, Step 3 for more details.

Example:

Descriptive Reporting Codes for the B2G_Addit_Info Reporting Type:

Within ZX_REPORT_CODES_ASSOC, associate the Tax Reporting Type (example: B2G_TaxTypeCode) and the Tax Reporting Code (example: 01) with a specific record in ZX_TAXES (example: VAT). This is the same for the reporting codes defined for the B2G_Addit_Info reporting type.

Spanish Online VAT Register

Effective July 1, 2017, the delivery of VAT Register information to the Spanish Tax Authorities must be performed electronically via a predefined xml-format and up to four days after the issuance or reception date. This is accomplished by sending all invoice and ticket information to the Tax Authorities. The requirement also has a component for processing the confirmation messages sent from the authority, updating the submitted data with the necessary details.

Setup Steps

The following setup steps must be performed before entering new Payables or Receivables transactions:

  1. New Customer and Supplier master file information: Taxpayer Identification Number Type, Special Regime and Exclude from SII Reporting.

    There is a Global Descriptive Flexfield to indicate the taxpayer identification number type, which must be included in the xml file. This Global Descriptive Flexfield must not be populated when the Supplier or Customer has a Spanish or European Union-assigned Taxpayer Number; in this case, this value is inferred and automatically populated by EBS. If the Taxpayer Number NOT be a Spanish or European Union number, one of the following values must be indicated in the customer / supplier master file:

    Note: The actual number is retrieved from the Tax Registration Number field on the Customer / Supplier master file.

    “02” is derived when applicable: “02” is automatically populated in the SII file, when it is an EU TRN.

    Special Regime: Select the special regime code that is applicable for the supplier/customer. This special regime code is used as the default value in the XML message for transactions created for the supplier/customer. You can change this value manually for each transaction, using the Global Descriptive flexfield. The Special Regime entered at the transaction level is given the highest priority.

    To indicate the Taxpayer Identification Number Type and Special Regime, you must first select “Spanish Customers Information” for AR and “Spanish Suppliers Information” for AP, in the Context Value field of Global Details window. These values can also be provided at the supplier/customer site. The value provided at the site level is given a higher priority than the value at the supplier/customer level.

    Exclude from SII Reporting: Select Yes for 'Exclude from SII reporting' to exclude all transactions of a supplier/customer or sites.

  2. Tax Setup:

  3. Add values in the Exemption Reasons table:

    The following lookup codes and descriptions must be added to the lookup type ZX_EXEMPTION_REASON_CODE, to populate the field CausaExencion (table L9 in the the Tax Agency XML message specifications): Navigation: Application Developer > Application > Lookups > Application Object Library > Search for ZX_EXEMPTION_REASON_CODE

    Code Description
    E1 Exempt due to article 20
    E2 Exempt due to article 21
    E3 Exempt due to article 22
    E4 Exempt due to article 23 and 24
    E5 Exempt due to article 25
    E6 Exempt due to other

    These exemption reason codes should be used in the Exemption reason during the tax exemption setup.

    Navigation: EBTax > Parties > Party Tax Profiles > Party Type = Third Party Site > Exemptions

  4. Document Sequence Setup (Mandatory): For Receivables (Issued Invoice) transactions, complete the Document Sequence setup for Invoice Identification. The Invoice identification of Issued invoice value depends on the “Copy Document Number to Transaction Number” check box.

    If the “Copy Document Number to Transaction Number” check box is selected, Invoice Identification will be Document Sequence Name <Delimiter>Document Number

    Delimiter is identified using LOOKUP JEES_SII_DELIMITER. By default, “/” is enabled. You can modify this lookup and choose/enter any other value.

    Only one value should be enabled for LOOKUP JEES_SII_DELIMITER.

    If this check box is not selected, Invoice Identification will be the transaction number.

  5. Supplier/Customer Taxpayer id and Tax registration Number (Mandatory): Set up the Taxpayer ID and Tax Registration Number for the Spanish Supplier and the Customer, in “Tax and Financial Information ”.

    You can enter your tax registrations at third party and/or third party sites. First preference is given to tax registration at the site level.

    Set up the Tax Registration Number in Parties: Party Tax Profiles > Party Tax Profiles > Party Type = Third Party > Query for the Party Name > Update Tax Profile > Tax Registrations > Default Reporting Registration Number

    Note: The actual number is retrieved from the Tax Registration Number field on the Customer / Supplier master file (billing site). Tax numbers commencing with a Spanish (“ES”) or another EU country code prefix are considered Spanish or EU tax numbers, respectively.”

  6. Setup for Cash Collections Register

  7. Setup for Payment Method Code

    Define a payment method with code “JE_ES_SII_DD”.

    Navigation: Payables Responsibility > Setup > Payment > Payment Administrator > Payment Methods

  8. Setup for Investment Goods Register

    Set “JG: Territory” profile option to Spain

    Set up Global Descriptive Flexfield at Asset Category

    Navigation: Asset Vision Spain >Setup > Asset System > Asset Categories

  9. Setup for Received Invoice Register for Periodo Tag

    The Online VAT Reporting Received Invoices template has a mandatory 'Periodo' tag. Businesses can either use the Invoice Date or Accounting Date to determine the period value for an invoice.

    Available options:

    Enable the preferred value: Navigation: Application Developer > Application > Lookups > Application Object Library > Search for JEES_SII_AP_PERIOD_OPTION

    TRX Invoice Date is enabled by default.

  10. Specify defaults for mandatory values per your business need (Optional).

    Navigation: Application Developer > Application > Lookups > Application Object Library > Search for JEES_SII_DEFAULT_RECEIVED_REG or JEES_SII_DEFAULT_ISSUED_REG

    You can enter other defaults in the description field across the corresponding field type. This is a free-entry text field; no list of values is provided.

    Enter the exact value that will be entered on the xml file.

    Note: Special Regime default and override values can be specified at multiple levels, therefore the hierarchy is followed to identify the Special Regime value to use for an invoice in the xml.

    The Invoice Type entered at the invoice header level in the Global Descriptive Flexfield is given the highest priority.

  11. Exclude Received Invoices from Reporting (Optional)

    Enter the Payable Source “Code” and “Meaning” in the lookup, to exclude the Payable Source from reporting.

    Navigation: Application Developer > Application > Lookups > Application Object Library > Search for JEES_SII_EXCLUDE_AP_SOURCE

    Note: Use the code and meaning from the Payables Lookups for the “SOURCE” type. Navigation: Payables > Setup > Lookups>Payables > Search for SOURCE

  12. Exclude Issued Invoices from Reporting for Transaction Source (Optional)

    Define “Exclude from SII Reporting” as 'Yes' in the “Transaction Source” Global Descriptive Flexfield, to exclude the transaction of the entire source from reporting.

Invoice Entry

Issued Invoices: fields to be populated for SII invoices

The following additional/modified fields are available in the EBS SII solution for Issued Invoices, which must be populated when appropriate.

“Comments” field:

The following Global Descriptive Flexfields must be populated, when pertinent.

Navigation: Receivables Responsibility > Transactions > Trasactions > Select GDFF ( )

The system dispplays the Additional Information for Spain window:

L12 Intracommunity Transaction Type

Values Description
A El envío o recepción de bienes para la realización de los informes parciales o trabajos mencionados en el artículo 70, apartado uno, número 7º, de la Ley del Impuesto (Ley 37/1992). (The sending or receipt of goods for the execution of the partial reports or works mentioned in article 70, section one, Number 7, of the Tax Law 37/1992)
B Las transferencias de bienes y las adquisiciones intracomunitarias de bienes comprendidas en los artículos 9, apartado 3º, y 16, apartado 2º, de la Ley del Impuesto (Ley 37/1992). (Transfers of goods and intra-Community acquisitions of goods covered by In articles 9, paragraph 3, and 16, section 2, of the Tax Law (Law 37/1992).)

The following status fields were added to invoices to control the submission process.

Received Invoices — fields to be populated for SII invoices

The following additional/modified fields are available in the EBS SII solution for Received Invoices, which must be populated when appropriate.

The following Global Descriptive Flexfields must be populated, when pertinent:

Navigation: Payables Responsibility > Invoices > Entry > Invoices > Click on GDFF ( )

L12 Intracommunity Transaction Type

Values Description
A El envío o recepción de bienes para la realización de los informes parciales o trabajos mencionados en el artículo 70, apartado uno, número 7º, de la Ley del Impuesto (Ley 37/1992). (The sending or receipt of goods for the execution of the partial reports or works mentioned in article 70, section one, Number 7, of the Tax Law 37/1992)
B Las transferencias de bienes y las adquisiciones intracomunitarias de bienes comprendidas en los artículos 9, apartado 3º, y 16, apartado 2º, de la Ley del Impuesto (Ley 37/1992). (Transfers of goods and intra-Community acquisitions of goods covered by In articles 9, paragraph 3, and 16, section 2, of the Tax Law (Law 37/1992).)

The following status fields were added to invoices to control the submission process.

Payment Entry

Receipt Entry

Note: For all 'Direct Debit Receipts', you must use Oracle Receivables' Direct Debit functionality. Refer to Oracle Receivables User Guide.

Note: Setting the ‘Cash Collection’ Global Descriptive Flexfield as Receipt Class is the recommended approach. The Receipt Method lookup and the receipt level Global descriptive flexfield are provided only for historical data.These will not be supported in the future.

Asset Entry

Enter the Global Descriptive Flexfield for Investment Goods Reporting.