Oracle® EMEA Add-on Localizations

User Guide for Finland

Release 12.2
Part No. E49867-01

December 2015

I
 Oracle EMEA Add-on Localization User Guide for Finland, Release 12.2

Part No. E49867-01

Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author: Chytanya Galam

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.

This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf
of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication,
disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the
applicable Government contract, and, to the extent applicable by the terms of the Government contract, the
additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle
USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.

This software and documentation may provide access to or information on content, products and services
from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third party content, products and services. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third
party content, products or services.

II
 Contents

Oracle® EMEA Add-on Localizations User Guide for Finland .................................................................. I

1. Add-on Localizations Overview ................................................................................................... 1-1

2. General Setup Steps ........................................................................................................................ 2-1

3. SEPA Payment Formats ................................................................................................................... 3-1

4. Index…………………………………………………………………………………………………………………………………………………………………4-1

III
 Send Us Your Comments

Oracle EMEA Add-on Localization User Guide for Finland, Release 12.2
Part No. E49867-01

Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?

If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.

IV
 Preface

Intended Audience
Welcome to Release 12.2 of the Oracle EMEA Add-on Localization User Guide for Finland.
This user guide is intended for a customer in Finland.
See Related Information Sources on page vii for more Oracle E-Business Suite product
information.

Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/us/corporate/accessibility/

Structure
1 Add-on Localizations Overview
2 General Setup Steps
3 SEPA Payment Formats

V
 Related Information Sources

Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content appropriate
for the precise revisions of interfaces in your environment.

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.

VI
VII
 1

C ha pt er 1 Add-on Localizations Overview

Add-on Localizations for Finland

Oracle® EMEA Add-on Localizations provide additional functionalities to help
customers in Finland meet legal and business requirements. This user guide provides
details about setups and functionality of the following Payment Formats:
Payments
• CLE: SEPA Domestic Payment Format for Finland

• CLE: SEPA International Payment Format for Finland

Add-on Localizations Overview 1-1

1-2 Oracle® EMEA Add-on Localizations User Guide for Finland
 2

C ha pt er 2 General Setup Steps

Assumption

It is assumed that all the required setups for Payables including the basic setup for
SEPA including IBAN bank account numbers and BIC codes are properly done.

Prerequisites
Before testing the solution developed for "CLE: SEPA Domestic Payment Format for
Finland" and "CLE: SEPA International Payment Format for Finland", user is required
to make sure that few of the following setups are available in the application after the
patch application. The setups that are available through the patch are mentioned
accordingly.

Internal Bank Account Setup

Note: The BankPartyIdentification BkPtyId> is given in the EFT
Number field.

General Setup Steps 2-1

 As shown in the below screen, Allow Zero Payments need to be disabled.

2-2 Oracle® EMEA Add-on Localizations User Guide for Finland

Creation of XML Publisher Format Templates
Verify that the XML Publisher Format Templates are available after the patch
application as shown in the below screens, one for Domestic and one for International.
These will be associated with the Payment Format by the user manually
Use the following navigation to see the created template.
Responsibility: Payables responsibility
Setup > Payment > Payment Administrator > Click on GO To Task against XML
Publisher Format Templates
Enter the following details and query:
Name - CLE: SEPA Domestic Payment Format For Finland

General Setup Steps 2-3

 Similarly verify that the international XML publisher format template is also created
Enter the following details and query:
Name - CLE: SEPA International Payment Format For Finland

Creation of Concurrent Programs

Verify that the concurrent programs are available after the patch application as shown
in the below screens, one for Domestic and one for International.
Use the following navigation to see the created concurrent program

2-4 Oracle® EMEA Add-on Localizations User Guide for Finland

Responsibility: System Administrator
Concurrent > Program > Define
Enter the following details and query:
Program - CLE: SEPA Domestic Payment Format For Finland

Similarly verify that the concurrent program for international Payment Format is
created

General Setup Steps 2-5

Creation of Payment Format
The user is required to complete the setups for "CLE: SEPA Domestic Payment Format
for Finland" and "CLE: SEPA International Payment Format for Finland"
Create a Payment Format "CLE: SEPA Domestic Payments for Finland" and associate
the XML Publisher Template created the above step and Data Extract which comes
through the patch as shown in the below screen.
Use the following navigation.
Responsibility: Payables responsibility
Setup > Payment > Payment Administrator > Click on GO To Task against Formats
Enter the following details:
Name: CLE: SEPA Domestic Payment Format for Finland
Code: CLE_F359_SEPA_DOM_PAYMENT_FI (max 30 char)
Data Extract: CLE: SEPA Finland Domestic Payments Instruction Extract
XML Publisher Template: CLE: SEPA Domestic Payment Format For Finland

Note: Both Data Extract and XML Publisher Template values are
available from the LOV, after the patch application

The user is required to add the following validations under the Pre-defined Validations
area

2-6 Oracle® EMEA Add-on Localizations User Guide for Finland

SEPA Payer Legal Entity Identification
SEPA Invoice Legal Entity Identification
SEPA Payee Bank Branch BIC
SEPA Payee IBAN Validation
SEPA Payer IBAN Validation
SEPA Payer Address Validation
SEPA Bank Charge Bearer Validation

Note: Bank Charges Bearer indicates whether you or your supplier will
pay for any bank charges associated with payments to your suppliers.

SEPA Bank Charge Bearer Validation is an optional validation and it is set to SLEV
behind the supplier and supplier site and also BEHIND ALL OPEN INVOICES.
Removing this validation from the payment format will not have any impact on CLE
SEPA output.
If you have any other value in the Bank Charge Bearer field behind the supplier than
SLEV (for example because of old LUM payment format), you can always Override
Bank Charge Bearer value when you submit Payment Process Request

Similarly create a Payment Format "CLE: SEPA International Payment Format for
Finland" and associate the XML Publisher and Data Extract which will be available
through the patch as shown in the below screen.
Use the following navigation.

General Setup Steps 2-7

 Responsibility: Payables responsibility
Setup > Payment > Payment Administrator > Click on GO To Task against Formats
Enter the following details:
Name: CLE: SEPA International Payment Format for Finland
Code: CLE_F359_SEPA_INT_PAYMENT_FI (max 30 char)
Data Extract: CLE: SEPA Finland International Payments Instruction Extract
XML Publisher Template: CLE: SEPA International Payment Format For Finland

Note: Both Data Extract and XML Publisher Template values are
available from the LOV, after the patch application

The user is required to add the following validations under the Pre-defined Validations
area
SEPA Payer Legal Entity Identification
SEPA Invoice Legal Entity Identification
SEPA Payee Bank Branch BIC
SEPA Payee IBAN Validation
SEPA Payer IBAN Validation
SEPA Payer Address Validation
SEPA Bank Charge Bearer Validation

Note: Bank Charges Bearer indicates whether you or your supplier will
pay for any bank charges associated with payments to your suppliers.

SEPA Bank Charge Bearer Validation is an optional validation and it is set to SLEV
behind the supplier and supplier site and also BEHIND ALL OPEN INVOICES.
Removing this validation from the payment format will not have any impact on CLE
SEPA output.
If you have any other value in the Bank Charge Bearer field behind the supplier than
SLEV (for example because of old LUM payment format), you can always Override
Bank Charge Bearer value when you submit Payment Process Request

2-8 Oracle® EMEA Add-on Localizations User Guide for Finland

 Note: If you have the old Finnish LUM EFT Format saved behind every
foreign supplier site you need to clear that value.

Navigation: Payables Manager Suppliers > Inquiry

Enter the Supplier name and click Update
Click on 'Payment Details'
Click Update for the Site in question
Click on the 'Payment Specifications' tab
Take note of the value in 'Payee-specified Payment Format' field
If you have there the value Finnish LUM EFT Format you need to clear this value

Creation of Payment Process Profile

The user is required to enter the setups for "CLE: SEPA Domestic Payment Process
Profile for Finland" and "CLE: SEPA International Payment Process Profile for Finland".
The payment format created above will be associated with this payment process profile.
Use the following navigation to create the Payment Process Profile
Responsibility: Payables responsibility
Setup > Payment > Payment Administrator > Click on GO To Task against Payment

General Setup Steps 2-9

 Process Profile
Enter the following details:
Code: CLE_F359_SEPA_DOMESTIC_PPP_FI
Name: CLE: SEPA Domestic Payment Process Profile for Finland
Description: SEPA Payment Process Profile with Unstructured and Structured
Remittance Information
Processing Type: Electronic
Electronic Processing Channel: Oracle Payments
Payment Completion Point: When the Payment Instruction is formatted
Allow manual setting of payment completion: No
Grouping Mode: Mixed
Payment Instruction Format: CLE: SEPA Domestic Payment Format for Finland

2-10 Oracle® EMEA Add-on Localizations User Guide for Finland

Note: For Bank Instruction 1 and 2 setup please see the chapter Set-up
of the number of occurrences

General Setup Steps 2-11

 Similarly the user is required to enter the setups for "CLE: SEPA International Payment
Process Profile for Finland" and associate the International payment format with this
PPP.
Use the following navigation to create the Payment Process Profile
Responsibility: Payables responsibility
Setup > Payment > Payment Administrator > Click on GO To Task against Payment
Process Profile

2-12 Oracle® EMEA Add-on Localizations User Guide for Finland

Enter the following details
Code: CLE_F359_SEPA_INTERNATIONAL_PPP_FI
Name: CLE: SEPA International Payment Process Profile for Finland
Description: SEPA Payment Process Profile with Unstructured Remittance Information
Processing Type: Electronic
Electronic Processing Channel: Oracle Payments
Payment Completion Point: When the Payment Instruction is formatted
Allow manual setting of payment completion: No
Grouping Mode: Mixed
Payment Instruction Format: CLE: SEPA International Payment Format for Finland

General Setup Steps 2-13

2-14 Oracle® EMEA Add-on Localizations User Guide for Finland
OA page personalization and entering LDFF information on Payment
Process Profile Screen (PmtProcProfViewPG.XML)

The following OA Page personalization needs to be defined on Payment Process Profile

screen for Finland Localizations.

Note: If the below personalization is already available on the page, please ignore
personalization setup section.

Use the below navigation steps for accessing Payment Process Profile screen:

General Setup Steps 2-15

 Navigate to Payment Process Profile screen and follow the steps

Click on Go To task for Payment process Profile.

In the above page, select Code “CLE_F359_SEPA_DOMESTIC_PPP_FI” and then click

on Go (Button)

2-16 Oracle® EMEA Add-on Localizations User Guide for Finland

Click on Name

Select the Additional Information Tab in the Payment Process Profile

Additional Information region is the region that needs to be personalized.

Enabling the Framework Personalize Links

Check whether personalization is enabled on this OAF Page, If personalization is

enabled the "personalize page" link will be shown on the page.

If personalization is not enabled, follow the below steps to enable the personalization
Set the profiles 1. FND: Personalization Region Link Enabled = "Y"
2. Personalize Self-Service Defn = "Y"

Page and region to add an Extension Link

Region to personalize
After choosing, the region in the page that needs to be personalized is the Additional
Information region.

Once the region is identified, click on "Personalize Additional Information" link.

This link takes us to the personalize page.

* Please note that from version 12.2.5 the "Personalize Page" link is moved under
settings as shown in the below screenshot. This is not specific to CLE or LDFF, this is
a generic change in accessing Personalization pages.

General Setup Steps 2-17

 Region in the personalize page
Now, in the personalize page, we need to Identify the region that we want to add a link
and click on "Create Item".
Click on Create item adjacent to the Name Header: Additional Information.
This takes us to the create item page where in we specify the item properties.
Build a link to call the DFF.

This step shows how to fill all necessaries properties for the new item.

Item Style
Choose the Item Style Field to "Static Styled Text" as shown in the below picture.
ID
Give the ID as PaymentProfileExt.
Prompt
Give the prompt value as "CLE: Additional Payment Profile Information". This is the
prompt that will appear on the personalized page.
Destination URI
Give the Destination URI value as
OA.jsp?OAFunc=CLE_F220_PG&pExtendedPage=/oracle/apps/iby/disbursement/setup/
paymentprocessprofile/webui/PmtProcProfPG&pExtendedTable=CLE_IBY_PAY_PROC
_PROF_EXT&pConnectString=DFF_ID1='{@SystemProfileCode}'&pCountry=COUNTRY
='FI'&retainAM=Y
View Instance
Give the view instance value as "PaymentProcesProfilesViewVO"

2-18 Oracle® EMEA Add-on Localizations User Guide for Finland

If the setup is done properly as per the above mentioned steps then the link "CLE:
Additional Payment Profile Information “will appear on the Payment Process Profile
Screen. If the link is not coming, please verify whether the setup steps are followed
properly.

General Setup Steps 2-19

 Now click on CLE: Additional Payment Profile Information then another screen will
display where you have to provide the path and file details for Sepa domestic and
international payments as shown in the below screen.

Click on CLE: Additional Payment Profile Information : select Context as FI.PPP, enter
output path and file name.

Enter the values and click on save and apply.

These Localization descriptive flex fields values are required for transmission protocol to
transfer the SEPA payment files to server directory automatically without user
intervention.

For Domestic payment format to capture the maximum number of

occurrences allowed for both intrabank and interbank transactions
According to the SEPA Rulebook, only one Remittance information data element is
allowed. Either the Structured or Unstructured form may be used, including a
maximum of 140 characters.
It has been agreed with EBA Clearing and banks operating in Finland that the
Remittance information element may be repeated a maximum of 10 times (entry 1: max
140 characters; entries 2–10: max. 280 characters). This means that the payer may specify
a maximum of 9 debit/credit invoices on the same payment message.

Some banks have made it possible that when the debtor and creditor have the bank

2-20 Oracle® EMEA Add-on Localizations User Guide for Finland

 account in the same bank, even more than 9 occurrences can be bundled.
To provide flexibility to the user to change the number of allowed occurrence Payment
Format global descriptive flex fields will be used to host the number of occurrence
information.
Number of interbank occurrences - for a particular bank in Finland - limit on number
of invoices and credit memos that can be put in one bundle while doing the bank
transfer to external bank
Number of intrabank occurrences – for a particular bank in Finland - limit on number
of invoices and credit memos that can be put in one bundle while doing the bank
transfer within the same bank.

Setup of the number of occurrences

The numbers of occurrences for internal (intrabank) and external (interbank) payments
must be confirmed with a particular bank and set-up properly before the payment
formatting program is run.

Bank Instruction Codes

General Setup Steps 2-21

 This can be modified by the user as per the regulations.
To identify the same bank transaction, the solution compares the BIC code of the
debtor and creditor. If they are the same they are considered as the same bank
transaction.

Note: It is advised to use a specific Pay group for Finnish Domestic and
International SEPA payment format.

The above setup for both Intrabank Transactions and Interbank Transactions is
linked in the Domestic Payment Process Profile as shown in the below screen

2-22 Oracle® EMEA Add-on Localizations User Guide for Finland

Assignment of Payment Format to Payables Documents in Bank Accounts
Payables Documents allow the user to make payments for the invoices created in
Payables. The Payment Format created and assigned to the Payables Document fulfils
the Finland Banks' Remittance Requirements when the payment is made.

The user is required to create a payable document and associate it with the payment
format "CLE: SEPA Payment Format for Finland" as shown in the below screen.
Navigate to Bank Accounts Screen. Query for your Internal Bank account and create a
Payables Document using the payment format "CLE: SEPA Domestic Payment Format
for Finland"

General Setup Steps 2-23

2-24 General Setup Steps
 3

C ha pt er 3 SEPA Payment Formats

Requirement
As per the Finland specific remittance requirements for SEPA Payments, two new
formats "CLE: SEPA Domestic Payment Format for Finland" and "CLE: SEPA
International Payment Format for Finland" are developed.
The remittance information in the SEPA payment output will differ when Payment
made with "CLE: SEPA Domestic Payment Format for Finland" from payment made
with "CLE: SEPA International Payment Format for Finland".
As per the requirement, the SEPA payment output must have the remittance
information containing both unstructured and structured information when a credit
memo exists, which allows bundling. The payment output allows an alterable number
of occurrences. This is when the user uses CLE: SEPA Domestic Payment Format for
Finland and checks with their own bank for the number of occurrences both for
intrabank and interbank payments. To identify the same bank transaction, the solution
compares the BIC code of the debtor and creditor. If they are the same they are
considered as the same bank (intrabank) transaction.
In case of CLE: SEPA International Payment Format for Finland, there is no limitation
on the number of occurrences and there is no special bundling requirement for
international payments, SEPA Payment output will have either structured remittance
part or unstructured remittance part.

Definitions

Number of interbank occurrences - for a particular bank in Finland - limit on number

of invoices and credit memos that can be put in one bundle while doing the bank
transfer to external bank
Number of intrabank occurrences – for a particular bank in Finland - limit on number
of invoices and credit memos that can be put in one bundle while doing the bank
transfer within the same bank.

Structured and Unstructured Remittance information – All invoices in SEPA must

have their own structured or unstructured Remittance information depending on the
invoice reference type. If Invoice reference type is Unique Reference Identifier then
remittance part will contain structured message. If Invoice reference type is
Remittance Message then remittance part will contain unstructured message.

SEPA Payment Formats 3-1

 Overview

A new payment format has been created to meet the Finnish bank requirements related
to remittance information for SEPA Payments. The new payment format contains the
remittance information in AOS2 bundling where both Structured and unstructured
data will exist in a format acceptable by Finnish banks. Bundling happens only if credit
memo exists.
When beneficiary issues invoices and credit notes, the Originator will make payments
for the net amount of the invoices and credit notes in order to settle the credit notes,
using a standard EBS functionality. The number of invoices to be bundled to one
payment depends on the amount of the invoices and credit notes. The net amount of a
payment and documents put in one bundle needs to be more than zero.
• The beneficiary issues invoices and credit notes to the originator.

• The user enters invoices and credit memos and validates it

• A payment is initiated from the originator side for the net amount of invoices and
credit notes (should be more than zero) to settle the payment batch.

• While making payment, the user selects the Payable document to which the newly
designed payment format is assigned.

• The formatted payment XML output will have the remittance information
containing both the unstructured and structured components if it is a domestic
payment and there is a bundling and there exists a credit memo

• In the absence of a credit memo, bundling will not take place. The SEPA payment
output will have unstructured remittance information if invoice reference text is
provided at the invoice level.

• In the absence of a credit memo, bundling will not take place. The SEPA payment
output will have structured remittance information if invoice reverence number is
provided at the invoice level.

• This information would be sent to the Originator's bank by different modes of

communication for funds disbursement to the beneficiary's bank.

• The originator bank will transfer either the structured or unstructured part of the
remittance information based on the type of the beneficiary bank (either AOS bank
or non-AOS bank).

Note: It is advised to use a specific Pay group for Finnish Domestic

SEPA payment format.

3-2 Oracle® EMEA Add-on Localizations User Guide for Finland

Transaction Processing

Invoice Creation
Responsibility: Use any standard Payables responsibility
Navigation path: Invoices -> Entry ->Invoice Batches or Invoices
Create an invoice or an invoice batch using appropriate screen in Payables as shown
below:

Note: Please refer to the Oracle Payables User Guide R12.2 for
additional information related to the creation of invoices in Accounts
Payables.

Providing Domestic Invoice Reference Number in Unique Remittance Identifier

For the invoice, provide the Domestic Reference number whose length should be
maximum of 20 digits in Unique Remittance Identifier using the following navigation
in the invoice header form. Give the check digit in the Unique Remittance Identifier
Check Digit –field.
Navigation path: (Menu) Folder ->Show Field -> Unique Remittance Identifier

SEPA Payment Formats 3-3

 Providing Domestic Invoice Reference Text in Remittance Message 1
For the invoice, provide the Domestic Reference Text in Remittance Message 1 using the
following navigation in the invoice header form.
Navigation path: (Menu) Folder -> Show Field -> Remittance Message 1

3-4 Oracle® EMEA Add-on Localizations User Guide for Finland

 Note: In the Remittance Message 1 field, only the complete text can be
provided or text along with numbers can be provided. In both cases, it
is considered as Invoice Reference Text.

Providing Domestic International Reference Number in Unique Remittance Identifier

For the invoice, provide the Domestic International Reference number whose length
will be maximum of 25 digits and start with 'RF' followed by a number in Unique
Remittance Identifier using the following navigation in the invoice header form. Give
the check digit in the Unique Remittance Identifier Check Digit –field
Navigation path: (Menu) Folder- >Show Field -> Unique Remittance Identifier

SEPA Payment Formats 3-5

Making the Payment
After validating the Invoice, make the Payment using either invoice screen or payments
screen.
a. Click "Actions" button and flag 'Pay in Full' Check box and click "OK" Button.
Or navigate to Payments > Entry > Payments
a. In the Payment Window, select the Payment document that is associated with the
payment format CLE: SEPA payment Format for Finland. Select Payment Process
Profile CLE: SEPA Payment Process Profile for Finland and all other required fields and
save
Or navigate to Payments > Entry > Payment Manager
In the Payment Manager Screen, enter the Payment Process Request name which
is unique and provide the necessary parameters. Select the Payment document that is
associated with the payment format CLE: SEPA payment Format for Finland. Select
Payment Process Profile CLE: SEPA Payment Process Profile for Finland and all other
required fields and submit the payment process.
Payment Process automatically launches four programs namely:

For Domestic Payments:

1.Format Payment Instructions with Text Output.
2. CLE: SEPA Domestic Payment Format for Finland.
3. CLE: SEPA Output File Transfer Program.
4. CLE: SEPA Output File Load Program.

3-6 Oracle® EMEA Add-on Localizations User Guide for Finland

 For International payments:
1.Format Payment Instructions with Text Output.
2. CLE: SEPA International Payment Format for Finland.
3. CLE: SEPA Output File Transfer Program.
4. CLE: SEPA Output File Load Program.

Note: 1) Please refer to the Oracle Payables User Guide R12.2 for
additional information related to the creation of payments in
Accounts Payables.

2) The selection of the payment format during payment is

absolutely a user choice. There will be no additional validations
done to check whether the correct payment format has been
selected for making the payment.

How to Launch XML Output File

To generate the XML Output file, click "Actions" button in the Payments/Payment Batch
window, enter the bank account and payment document you would like to use and
save. If the user selects Domestic payment format, Domestic payment format is
called as shown in the below screen

SEPA Payment Formats 3-7

Bundling rule
Whenever there is/are credit note(s) in a payment, AOS2 bundling feature applies.
1) If there is/are one or more credit memos in a payment, the credit notes are considered
first along with the invoice(s).
2) The bundling considers the max possible number of credit memos along with one
(or) more invoices to make the bundling amount positive. The left over invoices or
credit memos will considered in the next bundling.
3) Number of credit memos and invoices considered in a bundle is based on the value
setup for Intra/Inter bank transactions behind the Payment Format. Bundling will
consider the invoices and credit memos as per this value.
Note: Payments made between banks with same BIC are considered as Intra-bank
transactions.
4) If there are less than 'n' credit notes in the payment (assuming the value setup for
Intra/Inter bank transactions behind the Payment Format is set to 'n'), then the standard
invoices starting with the invoices with the biggest amounts will be considered for
bundling along with the credit memos. If there are invoices that will make the payment
more than zero then it payment is considered ok for processing, but if not then
formatting this payment will end in error.
5) Only those standard invoices with the biggest amounts and taking that we get the
payment amount more than zero will be considered. It does not matter if the invoice has
a domestic reference number or reference text. All the other standard invoices that we
do not need for settling the credit notes will get their own C-part Credit Transfer
Transaction Information.
6) When the bundling amount is negative (or) zero, the formatting will end in error and
in the log of the program, you will find the log messages mentioned in the Log
messages section.
For example – If there is one payment in AP and that payment can includes 100
invoices from which one is credit memo.

Log Messages
a. When bundling amount is Zero
Log Message - Zero Bundling Cannot be Done for the Payment Number <PMTNUM>
and for the Supplier <SUPP>
b. When bundling amount is negative
Log Message - Negative Bundling Cannot be Done for the Payment Number
<PMTNUM> and for the Supplier <SUPP>.
c. When the invoice(s) total amount is less than the credit note(s) amount
Log Message - Sum Of Invoice Amount should not be less or equal to sum of Credit
Memo Amount

3-8 Oracle® EMEA Add-on Localizations User Guide for Finland

Sample output

Domestic Payment
An XML output is generated when the user make a payment for an invoice in Payables.
The below example describes a remittance information element of a credit transfer
transaction, where the payment includes one credit note and two invoices with
reference and AOS2 with message. The amount of the credit transfer transaction is the
net amount of the invoice and the credit note.

• The invoice has a creditor reference "00000000000000010016" and the amount "EUR
2600.00"

• The invoice has a Additional Remittance Information "INVOICENARRATIVE" and

the amount "EUR 500.00"

• The credit note has a creditor reference "RF00000000000000010032" and the amount
"EUR 1500.00".

SEPA Payment Formats 3-9

3-10 Oracle® EMEA Add-on Localizations User Guide for Finland
 Note: 1. The structured occurrence marked in Blue color mentioned
above is displayed when the value is populated in the "Invoice
Reference Number" Context.
2. The structured occurrence marked in Green color mentioned above
is displayed when the text is populated in the "Invoice Reference
Text" Context.

International Payment
The below example describes a remittance information element of a credit transfer
transaction.
There are 2 invoices for international payment INVTEST2 and INVTEST3. Then in that
case the remittance information is unstructured and invoice information is separated
by a colon ':'.

SEPA Payment Formats 3-11

3-12 Oracle® EMEA Add-on Localizations User Guide for Finland
 C ha pt er 4 Index

Symbols
Creation of XML Publisher Format Templates, 2-
3

A
Add-on Localizations Overview, 1-1
Assumption, 2-1
Assignment of Payment Format to Payables
Documents in Bank Accounts, 2-18

B
Bundling Rule, 3-7

C
Creation of XML Publisher Format Templates, 2-3
Creation of Concurrent Programs, 2-4
Creation of Payment Format, 2-6
Creation of Payment Process Profile, 2-9

D
Definitions, 3-1

F
For Domestic payment format to capture the maximum number of occurrences allowed for both
intrabank and interbank transactions, 2-15

G
General Setup Steps, 2-1

H
How to Launch XML Output File, 3-7
I
Internal Bank Account Setup, 2-1

L
Log Messages, 3-8

Index 4-1
 M
Making the Payment, 3-6

O
Overview, 3-2

P
Prerequisites, 2-1

S
SEPA Payment Formats, 3-1
Setup of the number of occurrences, 2-16
Sample Output, 3-8

R
Requirement, 3-1

T
Transactions Processing, 3-3

4-2 Oracle® EMEA Add-on Localizations User Guide for Finland