Oracle® Retail Invoice Matching Cloud Service Oracle® Retail Invoice Matching Cloud Service Implementation Guide Release 21.0.000 F41704-02 |
|
Previous |
E-Invoicing is the electronic exchange of financial documents between a business and a government agency, a business to another business, or a business to a consumer. Invoice Matching uses a configurable approach to identifying documents to be extracted for E-invoicing. The configurable approach allows the user to identify documents by country or by country/set of books combination and map transaction types to be included in the extract for integration with third-party solutions which manage local tax reporting.
The E-Invoicing functionality is an optional batch process and can be configured at a country or country set of books level, and is only applied to specific documents. Therefore, you can configure the system to only extract specific documents created for specific countries. The list of document types eligible for E-Invoicing is listed below.
The batch job generates Oracle Retail Bulk Data Integration (BDI) tables containing the data for the documents which meet the extract criteria. The BDI tables are sent to a third-party which manages the process of distributing the documents to the appropriate government agencies in the required format. See the Oracle Retail Invoice Matching Operations Guide for additional details on the batch job.
The configuration data for creating and maintaining a document sequence is entered via the Data Upload / Data Download process in the Merchandise system.
Perform the following procedure to initially create the configuration for E-Invoicing:
Download the E-Invoicing Configuration (this creates an empty spreadsheet).
Populate the spreadsheet to identify documents to be extracted for E-Invoicing.
Upload the E-Invoicing Configuration.
Detailed steps:
Download the E-Invoicing Configuration.
Log in to the Merchandise system.
Navigation: Foundation Data > Download Foundation Data
Select Template Type: Finance Administration
Select Template: E-Invoice Mapping
Click the Download button
Populate the E-invoices worksheet on the spreadsheet. The table below shows the columns on the worksheet, and provides information on the usage.
Upload the E-Invoicing Configuration:
Log in to the Merchandise system.
Navigation: Foundation Data > Upload Foundation Data
Select Template Type: Finance Administration
Select Template: E-Invoice Mapping
Select: Choose File and browse to the spreadsheet to be uploaded.
Click the Upload button.
Table 6-1 E-Invoices Worksheet Columns
Columns | Field Type | Mandatory | Comments |
---|---|---|---|
Worksheet: E-Invoices |
|||
Country Id |
Free Text |
Yes |
The Country ID associated with the documents to be extracted. The country of the location on the document will be one of the criteria to determine if the document should be included in the extract. |
Set of Books |
Free Text |
No |
The Set of Books associated with the documents to be extracted. This optional field allows an organization to specify that only documents for a particular set of books for a particular country should be extracted. |
Receiving Authority |
Drop Down |
No |
Receiving Authority is an optional field which is passed with the extracted document to identify the 3rd party who should be receiving the document The values available to be used for the Receiving Authority are stored in a codes table in the Merchandise system: Code Type - IMRA - Trusted Third Party |
Transaction Type |
Drop Down |
Yes |
The transaction type identifies the types of documents to be included in the extract. The values available to be used for the transaction types are stored in a codes table in the Merchandise system: Code Type - IMTT -
The values shown are the only value values for Transaction Type, user cannot create additional values. |
Extract Point |
Drop Down |
Yes |
The extract point determines when a document will be extracted for E-invoicing. Creation means at the time when the document was first saved in Ready to Match, Tax Discrepant, or Approved status. Posted means at the time the document is sent to the financial system. The values available to be used for the Extract Point are stored in a codes table in the Merchandise system: Code Type - IMEP -
Creation and Posting are the only valid values for Extract Point. |
The BDI tables will contain document header and line information as well as taxes and comments associated with the document. The tables will generally be those which are included when a document is created, these include:
Table 6-2 BDI Tables
Table | Description |
---|---|
IM_DOC_HEAD |
Document Heading information, such as the supplier and/or supplier site, location, terms, amount. |
IM_INVOICE_DETAIL |
Invoice line (item) level detail. Includes quantity and unit cost. |
IM_DOC_DETAIL_REASON_CODES |
Line level for other types of documents such as debit memos, credit memos, and credit notes. |
IM_DOC_TAX |
Header level tax information |
IM_INVOICE_DETAIL_TAX |
Invoice line (item) level tax details. |
IM_DOC_DETAIL_RC_TAX |
Line level taxes for other types of documents such as debit memo, credit memo, and credit notes. |
IM_DOC_NON_MERCH |
Holds non-merchandise codes associated with the document. |
IM_DOC_NON_MERCH_TAX |
Tax associated with non-merchandise_codes. |
IM_DOC_HEAD_COMMENTS |
Comments associated with the document (at header level). |
IM_INVOICE_DETAIL_COMMENTS |
Comments associated with invoice lines. |
IM_DOC_DETAIL_COMMENTS |
Comments associated with lines on other documents such as debit memos, credit memos, and credit note requests. |
See the Oracle Retail Invoice Matching Operations Guide for additional information on the BDI Tables.