Payment hub for temenos centralised system

Krishna239429 30 views 91 slides Aug 27, 2025
Slide 1
Slide 1 of 91
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39
Slide 40
40
Slide 41
41
Slide 42
42
Slide 43
43
Slide 44
44
Slide 45
45
Slide 46
46
Slide 47
47
Slide 48
48
Slide 49
49
Slide 50
50
Slide 51
51
Slide 52
52
Slide 53
53
Slide 54
54
Slide 55
55
Slide 56
56
Slide 57
57
Slide 58
58
Slide 59
59
Slide 60
60
Slide 61
61
Slide 62
62
Slide 63
63
Slide 64
64
Slide 65
65
Slide 66
66
Slide 67
67
Slide 68
68
Slide 69
69
Slide 70
70
Slide 71
71
Slide 72
72
Slide 73
73
Slide 74
74
Slide 75
75
Slide 76
76
Slide 77
77
Slide 78
78
Slide 79
79
Slide 80
80
Slide 81
81
Slide 82
82
Slide 83
83
Slide 84
84
Slide 85
85
Slide 86
86
Slide 87
87
Slide 88
88
Slide 89
89
Slide 90
90
Slide 91
91

About This Presentation

Temenos


Slide Content

1
1

2
TPH Training - Day 4

3
3
Understand the Clearing Framework
Inward Framework
Outward Framework
Credit Transfer
Direct Debit
Single Transfer
Bulk Transfer
Clearing Tables
PP.CLEARING
PP.CLEARING.SETTING
PP.CLEARING.NATURECODE
Process SEPA Credit Transfer Payments
Learning Objectives
O
b
j
e
c
t
i
v
e
s

4
4Clearing Framework
Inward Framework
Generic local
clearing payment
processing
Outward
Framework

5
5Inward Framemwork
Enables receiving
XML file using IIB (ESB from IBM)
XML files using an ESB other than IIB
XML files without ESB
Non XML files

6
Inward Framework – XML files - High Level Overview
Receive XML file
XSD Validation
Transform to generic
format
(XSLT)
Parse and store file,
bulk and transaction
details
Debulk File
Checksum
/Controlsum
validation
Process based on
BatchBooking
Indicator
Payment processing
Raise settlement Entry
Generate outgoing file
Inward Framework
Outward Framework

7
An XML file received could result in
XSD validation failure and/or
XSLT transformation failure and/or
Checksum validation failure
File Duplicate
Send ACK/NACK based on configuration
File Acceptance

8
Enable or disable based on PP.MSG.ACCEPTANCE.PARAM
If file level duplicate check is enabled, system will verify based on
Internal file that holds the message IDs to check for duplicates –
PRF.DUPLICATEFILECHECK
File Validations – File Duplicate

9
Total number of transactions
The total number of transactions specified in the message should be
equal to the number of transactions received in the message
Total number of transactions in the Group Header = Sum of (‘Total number
of transactions’ per bulk.)
Total amount
Total amount specified in the message should be equal to the sum of
the individual payments in the file
Control Sum of the GroupHeader = Sum of (Control Sum per bulk)
File Validations

10
Batch Booking Indicator (In pain.001)
“True” - Total amount for all payments within the segment is mentioned.
Currency check
Currencies of all transactions within a bulk should be the same.
Total number of transactions within a bulk
Total number of transactions specified at the bulk level should be equal to
the number of transactions received within the bulk.
Value of tag NoOfTxs (in PmtInf) = Count of individual payments within the bulk
Total amount of the bulk
Total bulk amount specified in the message should be equal to the sum of
individual transaction amounts in the batch.
ControlSum in PmtInf = Sum of amounts of all individual transactions within a
bulk
Bulk Validation

11
User Menu > Received Files
Viewing status of files received

12
Batch Processing – Flow Diagram

13
Batch Processing – Flow Diagram

14
Process Flow – Message Acceptance
Message
Received
in Queue
Message
Acceptance
Service

15
View accepted and de-bulked messages

16
Debulked as ‘P’arent and ‘C’hild messages

17
De-bulked ‘C’hild payments

18
Parent Processed till Fee Determination
Parent mapped in POR.TRANSACTION

19
Start payment processing for ‘C’hild
Mapping
Service
(Children)
Mapping
Service
(Children)

20
Start payment processing for ‘C’hild

21
Start payment processing for ‘C’hild-Child Payment Scenarios
Scenario 1-First Child is reversed due to some failure and reach 993 status

22
View processed details for First ‘C’hild

23
Start payment processing for ‘C’hild-Child Payment Scenarios
Second Child Payment is successful

24
View processed details for Second ‘C’hild

25
View processed details for Second ‘C’hild

26
Start payment processing for ‘C’hild-Child Payment Scenarios
Third Child Payment is successful

27
View processed details for Third ‘C’hild

28
Start payment processing for ‘C’hild-Child Payment Scenarios
Scenario 2- Child payment is captured with reversal reason in statement text also.

29
Start payment processing for ‘C’hild-Child Payment Scenarios

30
Payment processing for ‘C’hild
Payment Completion
1.Payment Reversed (993)
2.Payment Generation Successful (687)
3.Payment Generation Successful (687)

31
Resume ‘P’arent processing
Resume Parent Processing – Check if all children have calculated fee

32
View status of parent

33
Batch Processing – Parent held due to insufficient funds
Payment is Accepted
Payment is parked due to insufficient funds-Whole Batch Parked
It goes to Status 49 (Waiting-Balance check DDA Approval)
Approve release of funds for parent transaction

34
Approve release of funds for parent transaction

35
Authorise request for funds
•Payment gets released to move to the next stage
•Child transactions are released and processed

36
Payment Processing
Receive XML file
XSD Validation
Transform to generic
format
(XSLT)
Parse and store file,
bulk and transaction
details
Debulk File
Checksum
/Controlsum
validation
Process based on
BatchBooking
Indicator
Payment processing
Raise settlement Entry
Generate outgoing file
Inward Framework
Outward Framework

37
Credit
Transfer
Direct Debit Cheque
Settlement
Type
Clearing Type
File
/Transaction
Based
Clearing
Transaction
Type
Clearing
Nature Code
Debit
Authority
Mandates
Reachability
Channel
Validations
Cancellation
Queries and
Answers
Investigation
Understanding the key words
37

38
PP.CL
EARI
NG
•Define the clearing
PP.CL
EARI
NGSE
TTIN
G
•Define the attributes of the clearing
PP.CL
EARI
NGNA
TURE
CODE
•Define the variations in clearing messages
Main Configuration Tables
38

39
39PP.CLEARING
Admin Menu > Payment Hub >Local Clearing GUI > Clearing

40
40PP.CLEARING.SETTING
Admin Menu > Payment Hub >Local Clearing GUI > Clearing Setting

41
41PP.CLEARING.SETTING - Contd

42
42PP.CLEARING.NATURECODE
Admin Menu > Payment Hub >Local Clearing GUI > Clearing
Nature Code
Company ID
It is the company code for which the clearing nature record is created.
Clearing
NatureCodeDescription
This field defines the code identifying the nature of clearing payment (sub
product type).
It is updated in the payment order during mapping.
Cheque Type
This field indicates the cheque type that is known in T24, relating to the given
clearing nature code.
It is used for cheque debits products during validation of the cheque status.

43
43PP.CLEARING.DIRECTORY
Admin Menu > Payment Hub >Clearing Directory GUI > Clearing
Directory

44
44PP.SOURCE.SETTING
Transaction Type
Indicates the Transaction Type for which the record is created.
Example : CT,DD
Message payment type
Indicates the message type of the Payment.
AutomatedCancel Indicator
 Indicates Whether the payment has to be automatically cancelled by
STP flow or not
Createcustomerstatusmsg
Create Customer Status Message for which the record is created – Indicates
whether Customer Status Report to be generated for the payment
Batchfeeholdindiactor
This field is to decide if the parent is to be held at fee or if children should be
released after payment finalization is specified. Set to ‘Y’ to hold parent at
fee.
Maxalloweddays
The number of the maximum allowed days to process the payment

45
Outward Clearing Framework is responsible for generating payment
messages/files to be sent to the Clearing and settlement entries for
successfully processed files.
Outward Framework

46
Define in PP.CLEARING
Takes as input
ClearingTransactionType
BankOperationCode
OutgoingMessageType
ClearingCurrency
Output (Values that form the bulking criteria. To be set to ‘Y’ if the field is
a deciding factor to form a bulk)
ClearingCurrency
ClearingNatureCode
OutgoingMessageType
ClearingTransactionType
CreditValueDate
DebitValueDate
BulkSendersReference
Outward Clearing Framework - Bulking Criteria API

47
Other values to be returned
File Format
Example for SEPA RPSSCL :
Valid file formats for RPSSCL : ICF, IDFC, IDFB
File format is decided based on ClearingTransactionType and
BankOperationCode
When PP.CLEARING.FileGenerationRequires is ‘N’, FileFormat would
be set to NOFILE by the system
Payment TypeIndicator
Specifies if the payment is a credit transfer or a direct debit
Outward Clearing Framework - Bulking Criteria API
Clearing Transaction Type Bank Operation Code File Format
CT or RT or RV Not Applicable (NA) ICF
DD or RD or RJ or RF or RV or
CR-DD
CORE IDFC
DD or RD or RJ or RF or RV or
CR-DD
B2B IDFB
Clearing Transaction Type Bank Operation Code
CT or RT or RV C
DD or RF or RD D

48
Exception Handling
Causes
Bulking Criteria API not defined
Bulking Criteria API defined but API does not exist
Result
System will log an ‘INF’ormational error in POR.HISTORYLOG
System will exit processing
Outward Clearing Framework - Bulking Criteria API

49
49
Accept Customer to Bank (C2B) Payment Orders
Clear Customer to Bank (C2B) Payment Orders [Inter-bank leg]
Settle Customer to Bank (C2B) Payment Orders
Exceptions and Investigations relating to C2B Payment Orders
Provide Customer Status Reports on C2B Payment Orders
Credit Transfers
$
Clearing House
$
Bank
Credit Transfer (pacs.008) – Incoming/Outgoing
Cancellation Requests (camt.056) – Incoming/Outgoing
Resolution of Investigation (camt.029) – Incoming/Outgoing
Payment Return (pacs.004) – Incoming/Outgoing
Payment
Initiation
Pain.001
Customer
Status
Report
Pain.002

50
50Clearing Transaction Types – Credit Transfer
Business Event Transaction Type ISO Message Version
Credit Transfer Initiation CI pain.001 05
Credit Transfer CT pacs.008 02
Credit Transfer Return RT pacs.004 02
Credit Transfer Cancellation Request CR camt.056 01
Resolution of Investigation RI camt.029 03
Clearing Status Report  pacs.002 03S2
Rejections RJ  
Customer Status Report 
 
pain.002 05

51
51Credit Transfer Initiation

52
52Credit Transfer Initiation - Booking
Single Payments – Sent immediately to Clearing (example RTGS payment)
Debit Customer/Debtor Account - For Principal
Debit Customer/Debtor Account - For Charges
Credit Clearing Nostro Account - For Principal
Credit PL- For Charges
Credit Tax Account - For Taxes
Single Payments – Sent in a Clearing Batch (ACH Payments)
Debit Customer/Debtor Account - For
Principal
Debit Customer/Debtor Account - For Charges
Debit Customer/Debtor Account - For Tax
(example VAT)
Credit Clearing Suspense Account -For Principal
Credit PL- For Charges
Credit Tax Account - For Taxes
Batch Payment – Parent Transaction – Book
Debit Customer/Debtor Account - For
Principal
Debit Customer/Debtor Account - For Charges
[Can be netted into a Single Debit entry]
Debit Customer/Debtor Account - For Tax
(example VAT)
Credit Batch Suspense Account - For Principal
Credit PL - For Charges
Credit Tax Account - For Taxes

53
53Credit Transfer Initiation – Booking (Cont.)
Batch Payment – Child Transaction - Sent immediately to Clearing (example RTGS payment)
Debit Batch Suspense Account - For
Principal
Credit Clearing Nostro Account- For
Principal
Batch Payment – Child Transaction - Sent in a Clearing Batch (ACH Payments)
Debit Batch Suspense Account - For
Principal
Credit Clearing Suspense Account-For
Principal
Settlement Entry with Clearing House (In case of ACH Payments)
Debit Clearing Suspense Account -
For Bulk Total
Credit Clearing Nostro Account-For Bulk Total
Suspense and Nostro accounts to be used can be configured –
PP.CLEARINGSETTING

54
54Credit Transfer – Receive and Execute

55
55Credit Transfer - Booking
Settlement Entry (For Batch/Bulk payments)
Debit Clearing Nostro Account Credit Clearing Suspense Account
Individual Transactions (which belong to batch/bulk) – Incoming
Debit Clearing Suspense Account Credit Beneficiary
Individual Transactions (which belong to batch/bulk) – Redirect
Debit Clearing Suspense Account Credit Vostro Account of correspondent bank (Net
of charges)
Credit PL (if charges are applied)

56
56Credit Transfer Initiation – Booking (Cont.)
Settlement Entry with Clearing House (In case of ACH Payments)
Debit Clearing Nostro Account - For Bulk TotalCredit Clearing Suspense Account - For Bulk Total
Suspense and Nostro accounts to be used can be configured –
PP.CLEARINGSETTING
Individual Transactions – Single – Incoming
Debit Clearing Nostro Account Credit Beneficiary
Credit PL (For charges if any)
Individual Transactions – Single – Redirect
Debit Clearing Nostro Account Credit Vostro of correspondent
Credit PL (For charges if any)

57
57Credit Transfer – Returning an incoming credit transfer

58
58Credit Transfer Return – Booking
Settlement Entry with Clearing House (In case of ACH Payments)
Debit Clearing Suspense Account Credit Clearing Nostro Account
Suspense and Nostro accounts to be used can be configured –
PP.CLEARINGSETTING
Returning an incoming credit transfer
Debit Return Suspense Account Credit Clearing Suspense Account

59
Workshop – Process PAIN 001

60
SEPA CREDIT TRANSFER- Open the IBM Integration Toolkit
Open the IBM integration Toolkit – 10.0.0.9 in the folder IBM
Integration BUS – 10.0.0.9

61
SEPA CREDIT TRANSFER – OUTGOING
Select the XML message from the folder C:\Temenos\R19\Env\Slot01\Data\T24\
UD\PP\OriginalBackupMsgFolder

62
SEPA CREDIT TRANSFER
Edit the selected message with Msg ID, Ctrl Sum(Check the individual
transaction amount and the total amount of the file is tallied)

63
SEPA CREDIT TRANSFER
Paste the edited message in the folder C:\Temenos\R19\Env\Slot01\Data\T24\
UD\PP\BulkCTIInput
Note:
•After you paste in the above folder, the message should
disappear.
•If the message disappears in the folder, check the mqsibackout
folder in the same location to find out for any failure files.

64
SEPA CREDIT TRANSFER
Check the status of the file in the PPT.RECEIVEDFILEDETAILS. UserMenu >
Payment Hub > Received Files > Received Message / File Details List

65
Run STPFLOW.MEDIUM Service
Run BNK/PAYMENT.STPFLOW.MEDIUM service

66
66Run STPFLOW.MEDIUM Service
Pending and Processed Payment Status moved to 706 Waiting – Clearing

67
PP.CLEARING.FREQUENCY
Set the cut off time in PP.CLEARING.FREQUENCY

68
68Run BNK/CLEARING.SETTLEMENT.SERVICE
Run BNK/CLEARING.SETTLEMENT.SERVICE

69
View Dashboard
Pending and Processed Payment Status changed to 999 – Payment Complete

70
70View Dashboard
Check Sent File Details

71
SEPA CREDIT TRANSFER – PACS008
Sent message to Clearing House can be viewed in the folder C:\Temenos\R19\
Env\Slot01\Data\T24\UD\PP\CTOutput

72
VIEW PAYMENT DETAILS – Pain 001(View Screen)

73
73VIEW PAYMENT DETAILS – Pain 001(View Screen)-Contd

74
View Posting Lines – PAIN 001
Posting Entries (PAIN 001) :
Debit Client Account
Credit Suspense Account
Credit P&L account for charges
PACS 008 (Settlement) :
Debit Suspense Account
Credit Clearing Nostro Account

75
Understand Audit Trial

76
Workshop – Process incoming PACS 008

77
SEPA CREDIT TRANSFER- Open the IBM Integration Toolkit
Open the IBM integration Toolkit – 10.0.0.9 in the folder IBM
Integration BUS – 10.0.0.9

78
SEPA CREDIT TRANSFER - INCOMING PACS 008
Select the XML message from the folder C:\Temenos\R19\Env\Slot01\Data\T24\
UD\PP\OriginalBackupMsgFolder

79
SEPA CREDIT TRANSFER
Edit the selected message with Msg ID, Ctrl Sum(Check the individual
transaction amount and the total amount of the file is tallied)

80
SEPA CREDIT TRANSFER
Paste the edited message in the folder C:\Temenos\R19\Env\Slot01\Data\T24\
UD\PP\STEP2Input
Note:
•After you paste in the above folder, the message should
disappear.
•If the message disappears in the folder, check the mqsibackout
folder in the same location to find out for any failure files.

81
SEPA DIRECT DEBIT
Check the status of the file in the PP.INPUT.FILE

82
View Dashboard
Pending and Processed Payment Status - Message Mapping

83
Run STPFLOW.LIGHT Service
Run BNK/PAYMENT.STPFLOW.LIGHT service
Pending and Processed Payment Status moved to 999 - Payment
Completed

84
VIEW PAYMENT DETAILS – Pacs 008IS

85
VIEW PAYMENT DETAILS – Pacs 008 - Contd

86
View Posting Lines – PACS 008 Settlement
PACS 008 (Settlement) :
Debit Clearing Nostro Account
Credit Suspense Account

87
View Posting Lines – PACS 008
Posting Entries (PACS 008) :
Debit Suspense Account
Credit Client Account

88
Understand Audit Trial

89
89Understand Audit Trial

90
90
Overview of Clearing Framework
PP.CLEARING
PP.CLEARING.SETTING
PP.CLEARING.NATURECODE
PP.CLEARING.DIRECTORY
PP.SOURCE.SETTING
Process SEPA Credit Transfers
What Did We Learn?
C
o
n
c
l
u
s
i
o
n

91
Thank You
www.temenos.com
91
Tags