Additional optional services applied in Greece to SEPA Direct Debits  

DIAS provides SEPA Direct Debit services to the SEPA community through the DIAS Direct Debit System (henceforth called DDD), which is compliant to the SEPA Core Direct Debit Scheme Rulebook v3.4 and SEPA B2B Direct Debit Scheme version 1.3. Furthermore, DIAS is going to provide complementary services based on the rules and standards of the EPC SDD Schemes (Core and B2B), in order to meet further specific customer’s expectations which are described as additional Optional Services (AOS).
 
The SDD AOS which DIAS offers through the DIAS Direct Debit service, are the following:
 

1. The DMF AOS

 
 In SEPA DDD a Mandate is created and forwarded from a Creditor to a Debtor Bank through the Creditor Bank and DIAS. According to Greek practice, it was common in previous years to collect the client/debtor Mandates directly through their Bank network. As a result, Debtor Banks now carry all the information and the know-how to collect the Mandates.
 
The DMF AOS is a direct debit service according to which the Debtor Bank, rather than the Creditor, receives and retains the Mandates.
 
The DMF service is based on the interbank excange of Mandate data related information transfered from the Debtor Bank to the Creditor through the Creditor Bank.
 
It should be pointed out that the Creditor retains the option to collect Mandates on its own.

1.1   Roles of the participants

This chapter illustrates the participants and their role in DMF.
 
•  Creditor:
Informs the Creditor Bank and the Client/Debtor that accepts the DMF process.
The creditor is the one who generates all the data required to create the Mandate (eg. Mandate Id) for his Client/Debtor, in accordance with the Rulebook provisions.
For the issuing of Mandates using the DMF process, the use of check digits in the unique Mandate identifier is mandatory for Creditors.
 
•  Client/Debtor:
The Client/Debtor, as the account holder, signs the Mandate at the Debtor Bank and ensures that the requisite information is complete in the Mandate document. The Debtor Bank must follow all the customer identification and verification procedures and check that the signature belongs to the Debtor.
 
•  Debtor Bank:
The Debtor Bank dematerializes the paper Mandate without altering its contents and sends the information (Mandate part of pacs.003.001.01) to DIAS.
The paper Mandate must be stored intact by the Debtor Bank as long as the Mandate exists. Even if the Mandate is cancelled, it must be stored by the Debtor Bank for a period according to the law provisions.
 
•  DIAS:
Receives the Mandate message from the Debtor Banks.
Registers the Mandates to the Database and validates them according to the specifications that enable Creditor Banks to create a pacs.003.001.01 message at a later stage.
Informs the Creditors involved for every collection gathered in Debtor Banks, through their Creditor banks.
 
•  Creditor Bank:
Informs the Debtor Bank that a Creditor accepts the DMF option.
Receives the Mandate Information, acquired in the Debtor Bank, through DIAS.
Informs the Creditor about the Mandate created.
 
 

1.2   Business justification, definition and process

 
This chapter describes the flows exchanged in DMF between the Debtor Bank, DIAS and Creditor Bank.
 
• Debtor Mandate flow
• Creditor Bank flow
 
1.2.1   Debtor Mandate Flow
 
The Debtor Bank receives the Mandate data from the Client/Debtor, creates the Mandate and after the required verifications sends it to DIAS.
DIAS receives the Mandate from the Debtor Bank, correlates the specific Mandate information and accepts or rejects the Mandate accordingly.
Upon rejection DIAS sends a rejection message to the Debtor Bank, while on acceptance, updates its database and sends the Mandate data to the Creditor Bank.
The same procedure is followed by the Debtor Bank in case an amendment is executed (always according to AT-24 - The Reason for Amendment of the Mandate
of the Core and B2B SEPA Direct Debit Rulebooks). DIAS validates the data, updates its database and creates the new collections with amendment.
 
1.2.2   Creditor Bank Flow
 
The Creditor Bank receives the DMF Mandates and amendments from DIAS and informs the Creditors.
After the DMF process and after the Mandate reaches the Creditor Bank, the creation and the dispatch of the Collection follows the flow described in the SEPA Direct Debit Rulebook (Core and B2B) specifications.
The following image depicts the workflow of the participants involved in the Debtor Mandate Flow and their individual actions:
 
1.3   Participation in the AOS
 
A Bank participates in the AOS as Debtor Bank and optionally as Creditor Bank by accepting the functional rules of DDD.
As a prerequisite for participating in the DMF AOS a Bank has first to adhere the SEPA Core Direct Debit Scheme (and additionally the SEPA B2B Direct Debit Scheme).  
If a Bank declares that wants to participate in the AOS, as Debtor Bank, then it is obligatory to serve any Creditor willing to use the AOS through its Creditor Bank.
On the other hand a Bank, participating in the DMF AOS as a Creditor Bank, chooses to provide or not it’s Creditors with the functionality of the DMF AOS.  
 
For information about participating in this AOS, you can contact DIAS through the following e-mails:
 
 

1.4   Final Remarks

The DMF flow is currently in use and almost every Bank in the Greek community is employing it.
At this point we should emphasize that in order for the DMF AOS to function, the following must apply:
•     The Debtor Bank must participate in the DMF AOS.
•     The Creditor Bank, of the specific Creditor the Mandate was created, must also participate in the AOS.
Despite this, the use of the DMF AOS does not affect the participation of Banks (Creditor or Debtor) in the flows described by the SEPA Direct Debit rulebook.
In detail the following can apply:
- A Debtor Bank participating in the DMF AOS can also service a Creditor, and it’s Creditor Bank, that does not participate in the AOS.
- A Creditor and its Creditor Bank participating in the DMF AOS can also be serviced by a Debtor Bank that does not participate in the AOS.
-  A Creditor Bank and a Debtor Bank participating in the DMF AOS can also service a Creditor that does not participate in the AOS.
 
  

2.    The "CMF reception by Debtor Bank prior to collection" AOS

In the SEPA scheme the responsibility of collecting a mandate is solely that of the Creditor’s. The Creditor then forwards the mandate and its corresponding collection to the Debtor Bank, through the Creditor Bank.
On the other hand, the Debtor Bank has to do a series of predefined assessments, in order to enable its systems to handle a mandate which the Debtor Bank hasn’t collected itself.
Their goal to provide better services towards its Clients/Debtors encouraged Debtor Banks to request DIAS to create an AOS to optimize this procedure. Within the scope of this request the CMF reception by Debtor Bank prior to collection AOS (henceforth called “CMF RPC”) was created.
According to the SEPA Direct Debit scheme, Debtor Banks must receive a mandate or an Amendment with its respected collection. The use of our CMF RPC AOS enables Debtor Banks to receive a Mandate or an Amendment prior to collection.
This functionality is combined with the obligation that the Debtor Bank will receive the collection on D-1, through a different flow than the mandate. This separate flow does not affect the Creditor Bank’s operation.
With the described procedure, Debtor Banks have a longer period to confirm the details contained in the mandates, in order to achieve a successful collection.

  
2.1    Roles of the AOS participants

This chapter illustrates the participants and their role in CMF RPC AOS.
 
• DIAS:
DIAS in the context of this AOS operates as an intermediate between the Creditor Bank and the Debtor Bank. Its role is summarized in the following:
- receives electronic flows from the Creditor Bank
- sends electronic flows to the Debtor Bank
 
• Debtor Bank:
The Debtor Bank, in the CMF RPC, functions as described below:
- receives and validates Mandate/Amendment messages (according to the Mandate Amendment Procedures described to PT-02.02 of the Core and B2B SEPA Direct Debits Rulebooks) from DIAS
- sends reply messages to DIAS
 
Note:
The Creditor Bank sends the Mandates/ Amendments to DIAS along with the respected collections, according the Rulebook’s timetable for both products (Core and B2B).
In the CMF RPC AOS the Creditor Bank acts according to the Rule Book functionality.
The AOS does not affect the Creditor Bank. 

                    
2.2   Business justification, definition and process

This chapter describes the flows exchanged in CMF RPC, between the Creditor Bank, DIAS and the Debtor Bank.
 
• Creditor Bank flow
• DIAS flow
• Debtor Bank flow
  
2.2.1   Creditor Bank Mandate Flow
 
The Creditor Bank sends to DIAS Mandates or Amendments along with the respected collections.
 
 
2.2.2   DIAS Flow
 
DIAS receives the Mandate/Amendment message and the respected collection (pacs.003.001.01) from the Creditor Bank somewhere between (D-14, D-2) for the CORE product and (D-14, D-1) for the B2B product (see the scheme above).
Dias then registers the Mandate/Amendment to the Database and validates them according to the xml message regulations.
Categorizes the data of the Mandate/Amendment and its respected collection.
Sends the Mandate/Amendment to the Debtor Bank immediately after the validation while the collection on D-1.
After receiving the replies from the Debtor Bank, DIAS correlates them with the corresponding Mandate/Amendment message and updates its system with the successful transactions.
On the occasion that a transaction can’t be correlated, then it is registered in an exception report which is send to the Debtor Bank.
If a Mandate/Amendment message is rejected by the Debtor Bank, DIAS will not send the corresponding collection.
 
2.2.3   Debtor Bank Flow
 
The Debtor Bank receives the Mandates/Amendments from DIAS, registers them to its database and validates them according to the specifications of the corresponding chapter in the Rulebook.
Creates messages for both accepted and rejected transactions and sends them to DIAS.
Finally receives the rejected transactions in the exception report created by DIAS.
  

2.3   Participation in the AOS

As a prerequisite for participating in the CMF RPC AOS a Bank has to adhere the SEPA Core Direct Debit Scheme (and additionally the SEPA B2B Direct Debit Scheme).
A Bank can participate in the AOS only as Debtor Bank.
For information about participating in the AOS, you can contact DIAS through the following e-mails:
  

2.4 Final Remarks

We should emphasise that, in order for the CMF RPC AOS to function, the Debtor Bank must participate in it.
Finally, the fact that a Debtor Bank participates in the AOS, will not affect the function of the Creditor Bank.
 
 

3.   Dispatch of recurrent collection (CORE product):

Business justification, definition and process
 
According to the SEPA Direct Scheme (concerning CORE products) when Debtor banks receive the first collection, along with the Mandate information, they correlate the data of collections in their database, cross reference and validate the debtor’s personal data (e.g. account number) contained in the mandate.
Debtor Banks receive all recurrent collections without amendment on D-2. DIAS, taking into account all the validations above, has created a community AOS for its members that allows them to receive every recurrent collection without amendment on D-1 instead of D-2.
All the necessary validations have been already executed upon the arrival of the first collection, so it would be optimal for Debtor Banks to manage future collections only for a minimum amount of time.
Finally, no further processing requirements are needed in order to participate in this AOS.
 

4.   Acceptance period of Reversal by Debtor Banks 

Business justification, definition and process
 
The SEPA scheme has given the functionality of Reversal to the Direct Debit System. For the needs of this particular service, the EPC has established an effective Reversal request period of maximum 2 days after the collection’s settlement date (D+2).
 
Creditors identified through their operations that they are in need of a longer Reversal request period in order to cross reference the payment dues for a specific collection. As a result, DIAS, in accordance with Debtor Banks, provides a community AOS to Creditors through their participating Creditor banks. This AOS enables the Creditors to forward Reversals, through their Creditor Banks, as far in the future as D+20 instead of D+2 (as described above).
 
Finally, the functionality of this AOS does not require any further processing requirements for the participating Banks.
 
 

5.   National Character Set

Business justification and definitions
 
Banks operating in Greece consider essential, for cultural and political reasons, to continue supporting the Greek character set for SEPA DDD messages, as described below.
DIAS is supporting a multilateral agreement which permits every SEPA bank who will become a member of the multilateral agreement:
 
a) To support Greek character set for exchanged SEPA DDD messages  between banks who are members of the aforementioned multilateral agreement and
b) To support Latin character set for exchanged SEPA DDD messages between any SEPA bank
Concerning the pacs.003.001.01 file, the fields in which the National Character Set is used are the following:
 
2.27
Original Creditor / Name
2.43
Creditor / Name
2.43
Credito / Postal Address
2.47
Ultimate Creditor / Name
2.57
Debtor / Name
2.57
Debtor / Postal Address
2.61
Ultimate Debtor / Name
2.81
Remittance Information

Characters supported by Greek character set:

a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9
/ - ? : ( ) . , ’ +
Space
α ά β γ δ ε έ ζ η ή θ ι ί ϊ ΐ κ λ μ ν ξ ο ό π ρ ς σ τ υ ύ ϋ ΰ φ χ ψ ω ώ
Α ¶ Β Γ Δ Ε Έ Ζ Η Ή Θ Ι Ί Ϊ Κ Λ Μ Ν Ξ Ο Ό Π Ρ Σ Τ Υ Ύ Ϋ Φ Χ Ψ Ω Ώ
= ! % * ; # _ $ \ { } [ ]
 
 
 

 

We use cookies to improve your experience and security on our website. More Info