7. Common Group Messages
7.1 Outbound Manual Input Screens
Outbound Common Group Messages
The Common Group Messages Input screens are used for initiating the following messages manually:
l MT 190, MT 290 – Advice of charges
l MT 191, MT 291 – Request for charges
l MT 192, MT 292 – Request for cancellation
l MT 195, MT 295 – Queries
l MT 196, MT 296 – Answers
l MT 198, MT 298 – Proprietary Message
l MT 199, MT 299 – Free Format Message
This message types are exchanged between banks for investigations regarding payment messages and initiating non-value requests like cancellation.
Outbound messages gets generated and linked to the Original Transaction once its Sanctions scanned & Sanctions response is Success.
You can invoke “Advice of Charges” screen by typing ‘PXDCMN90’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Specify the following details.
Branch Code
Displays the selected branch of the logged-in user.
Reference Number
Displays the Reference Number by default.
Receiver
Specify the Receiver from the list of values.
Receiver Name
The system displays the name of the Receiver upon the selection of Receiver.
SWIFT Message Type
Specify the SWIFT Message Type from the list of values.
Host Code
Displays the Host code of the user’s logged in branch.
Related Reference
Specify the Related Reference Number from the list of values.
UETR
For UETR pick up logic for Common group messages, refer to Section 7.3.3, "UETR population in Outbound Common Core Messages".
Account Identification(25)
Specify the account from the list of values.
Value Date, Currency, Amount (32)
Specify the Value Date and amount and select the Currency from the list of values.
Ordering Institution(52)
Specify the Ordering Institution details.
Details of Charges(71B)
Specify the Details of Charges(71B) details.
Sender to Receiver Information(72)
Specify the Sender to Receiver Information(72) details.
7.1.1.1 Viewing Advice of Charges Summary
You can invoke “Advice of Charges Summary” screen by typing ‘PXSCMN90’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Authorization Status
l Record Status
l Branch Code
l Host Code
l Reference Number
l Related Reference
l Receiver
l SWIFT Message Type
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or click the ‘Details’ button after selecting a record to view the detailed screen.
7.1.2 Request for Payment of Charges
You can invoke “Request for Payment of Charges” screen by typing ‘PXDCMN91’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Specify the following details.
Branch Code
Displays the selected branch of the logged-in user.
Host Code
Displays the Host Code of the logged-in user.
Reference Number
Displays the Reference Number by default.
Receiver
Specify the Receiver from the list of values.
Receiver Name
The system displays the name of the Receiver upon the selection of Receiver.
SWIFT Message Type
Specify the SWIFT Message Type from the list of values.
Related Reference(21)
Specify the Related Reference Number from the list of values.
UETR
For UETR pick up logic for Common group messages, refer to Section 7.3.3, "UETR population in Outbound Common Core Messages".
Currency, Amount (32B)
Specify the Currency and Amount from the list of values.
Ordering Institution(52)
Specify the Ordering Institution details.
Account with Institution(57)
Specify the Ordering Institution details.
Details of Charges(71B)
Specify the Details of Charges(71B) details.
Sender to Receiver Information(72)
Specify the Sender to Receiver Information(72) details.
7.1.2.1 Viewing Request for Payment of Charges Summary
You can invoke “Request for Payment of Charges Summary” screen by typing ‘PXSCMN91’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Authorization Status
l Record Status
l Branch Code
l Host
l Receiver
l SWIFT Message Type
l Reference No
l Related Ref(21)
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
7.1.3 Request for Cancellation
You can invoke “Request for Cancellation” screen by typing ‘PXDCMN92’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can generate a Cancellation request n92 message for a payment message sent earlier from this screen.
Specify the following details.
Branch Code
Displays the selected branch of the logged-in user.
Host Code
Displays the host code of the selected branch of the logged-in user.
Transaction Reference Number
System defaults this field with an internal reference number or user can specify.
Reference Number
Displays the reference number of the generated Common Group message when viewed in the Query mode.
Receiver
Specify or search and select the BIC code of the bank which is desired to be the Receiver of the generated Common Group message.
Receiver Name
Displays the name of the bank corresponding to the selected BIC.
SWIFT Message Type
Specify the required Common Group message type from the list of values. The available values for selection include the following:
l 192
l 292
l 992
UETR
For UETR pick up logic for Common group messages, refer to Section 7.3.3, "UETR population in Outbound Common Core Messages".
Related Ref(21)
Specify or search and select the transaction (contract) reference number of the associated customer or bank transfer transaction.
11S: MT and Date of the Original Message
Specify the following details of the original (referenced) outward/inward message.
MT Number
Specify the MT number of the original message e.g. 103, 202, 102 etc.
Date
Specify or select date (from calendar LOV) of original message
Session Number
Specify Session number (1st 4 digits from the last 10 digits in Block1 of ACK received) of original message
ISN
Specify ISN (last 6 digits from the last 10 characters in Block1 of ACK received) of original message.
Narrative (79)
Specify narrative text for describing the original message, or all transactions in the original multi-credit Customer/Bank transfer message that is being referenced by this Common Group message. Alternatively, this field can also be used for specifying free format text in case of MT 199/MT 299. This field can contain up to a 1750 characters.
Copy of at least the Mandatory Fields of the Original Message
Specify at least the mandatory fields of the original message that is being referenced by this Common Group message. This field can be input instead of ‘Narrative 79’ field but never both.
Narrative (79) Line 1
For Narrative(79) field, in addition to the narrative text, two line formats are introduced
l Line1: Cancellation Reason)(Narrative)
l Line2-35: Narrative
This field is applicable for MT 192, MT 292, MT 992 cancellation messages both inbound and outbound.
Following are the Cancellation Reason codes supported:
|
Reason Code |
Acronym |
Usage |
|---|---|---|
|
AGNT |
Incorrect Agent |
Agent in the payment. |
|
CURR |
Incorrect Currency |
Currency of the payment is incorrect. |
|
CUST |
Requested by Customer |
Cancellation requested by the ordering customer. |
|
CUTA |
Cancel upon Unable to Apply |
Cancellation requested because an investigation request has been received and no remediation is possible. |
|
DUPL |
Duplicate Payment |
Payment is a duplicate of another payment. |
|
FRAD |
Fraudulent Origin |
Cancellation requested following a transaction that was originated fraudulently. The use of the Fraudulent Origin code should be governed by jurisdictions. |
|
TECH |
Technical Problem |
Cancellation requested following technical problems resulting in an erroneous transaction. |
|
UPAY |
Undue Payment |
Payment is not justified. |
This field Narrative(79) Line 1 or copy of atleast the mandatory fields of the original message or both will be mandatorily present in the MT 192, MT 292 & MT 992 messages.
If Cancellation Reason is the only information in Narrative(79) Line 1 field, then a copy of atleast the mandatory fields of the original message must be present.
7.1.3.1 View Message
Click View Message to view the outgoing message details in ‘View Outgoing Message’ sub screen.
7.1.3.2 Viewing Request for Cancellation Summary
You can invoke “Request for Cancellation Summary” screen by typing ‘PXSCMN92’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Authorization Status
l Record Status
l Branch Code
l Host Code
l Reference Number
l Receiver
l SWIFT Message Type
l Related Ref(21)
l Transaction Reference Number
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or click the ‘Details’ button after selecting a record to view the detailed screen.
You can invoke “Queries” screen by typing ‘PXDCMN95’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Specify the following details.
Branch Code
Displays the selected branch of the logged-in user.
Host Code
Displays the host code of the selected branch of the logged-in user.
Reference Number
Displays the Reference Number by default.
Transaction Reference Number
System defaults this field with an internal reference number or user can specify.
Receiver
Specify or search and select the BIC code of the bank which is desired to be the Receiver of the generated Common Group message.
Receiver Name
Displays the name of the bank corresponding to the selected BIC.
SWIFT Message Type
Specify the required Common Group message type from the list of values. The available values for selection include the following:
l 195
l 295
l 995
Related Ref(21)
Specify or search and select the transaction (contract) reference number of the associated customer or bank transfer transaction.
Related Message
Specify the related SWIFT message.
Linked Reference Number
Specify the Linked Reference Number from the list of values. Lists all the Outbound/Inbound Cross Border Transaction References of the user logged in host.
UETR
For UETR pick up logic for Common group messages, refer to Section 7.3.3, "UETR population in Outbound Common Core Messages".
Option
Select ‘R’ or ‘S’ from the drop down.
11 A: MT and Date of the Original Message
Specify the following details of the original (referenced) outward/inward message.
Option
Select either “11S” or “11R” depending on whether original message being referred was sent or received.
MT Number
Specify the MT number of the original message e.g. 103, 202, 102 etc.
Date
Specify or select date (from calendar LOV) of original message
Session Number
Specify Session number (1st 4 digits from the last 10 digits in Block1 of ACK received) of original message
ISN
Specify ISN (last 6 digits from the last 10 characters in Block1 of ACK received) of original message.
Queries (75)
Specify or search and select (using LOV) a standard Query code. You can then input additional text or query following the selected Query code, You may specify up to 6 different queries in each of the 6 text boxes.
Narrative (77A)
Specify additional details about the Queries or Answers input in one of the above mentioned fields. The Narrative text can contain up to 700 characters.
Narrative (79)
Specify narrative text for describing the original message, or all transactions in the original multi-credit Customer/Bank transfer message that is being referenced by this Common Group message. Alternatively, this field can also be used for specifying free format text in case of MT 199/MT 299. This field can contain up to a 1750 characters.
Copy of at least the Mandatory Fields of the Original Message
Specify at least the mandatory fields of the original message that is being referenced by this Common Group message. This field can be input instead of ‘Narrative 79’ field but never both.
7.1.4.1 View Message
Click View Message to view the outgoing message details in ‘View Outgoing Message’ sub screen.
7.1.4.2 Viewing Queries Summary
You can invoke “Queries Summary” screen by typing ‘PXSCMN95’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Authorization Status
l Record Status
l Branch Code
l Host Code
l Receiver
l SWIFT Message Type
l Reference Number
l Transaction Reference Number
l Related Ref(21)
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or click the ‘Details’ button after selecting a record to view the detailed screen.
You can invoke ‘Answers’ screen by typing ‘PXDCMN96’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Specify the following details.
Branch Code
Displays the selected branch of the logged-in user.
Host Code
Displays the host code of the selected branch of the logged-in user.
Reference Number
Displays the Reference Number by default.
Transaction Reference Number
System defaults this field with an internal reference number or user can specify.
Receiver
Specify or search and select the BIC code of the bank which is desired to be the Receiver of the generated Common Group message.
Receiver Name
Displays the name of the bank corresponding to the selected BIC.
SWIFT Message Type
Specify the required Common Group message type from the list of values. The available values for selection include the following:
l 196
l 296
l 996
Related Ref(21)
Specify or search and select the transaction (contract) reference number of the associated customer or bank transfer transaction.
Linked Reference Number
Specify the Linked Reference Number from the list of values. Lists all the Outbound/Inbound Cross Border Transaction References of the user logged in host.
UETR
For UETR pick up logic for Common group messages, refer to Section 7.3.3, "UETR population in Outbound Common Core Messages".
11A: MT and Date of the Original Message
Specify the following details of the original (referenced) outward/inward message.
Option
Select either “11S” or “11R” depending on whether original message being referred was sent or received.
MT Number
Specify the MT number of the original message e.g. 103, 202, 102 etc.
Date
Specify or select date (from calendar LOV) of original message
Session Number
Specify Session number (1st 4 digits from the last 10 digits in Block1 of ACK received) of original message
ISN
Specify ISN (last 6 digits from the last 10 characters in Block1 of ACK received) of original message.
Answers (76)
Specify the answers if any in the text boxes.
For Answers(76) field, in addition to the narrative text, two line formats are introduced
l Line1: Answer Number)(Narrative1)(Narrative2)
l Lines2-6: (Narrative) or (Answer Number)(Narrative 1)(Narrative 2)
This field is applicable to MT 196, MT 296 & MT 996 Answers messages
As part of SWIFT 2018 changes, 2n is changed to 4c so that ISO reason codes can be incorporated in the answers
Answers contains one or more of the following codes:
|
Reason Code |
Acronym |
Usage |
|---|---|---|
|
CNCL |
Cancelled As Per Request |
Used when a requested cancellation is successful |
|
PDCR |
Pending Cancellation Request |
Used when a requested cancellation is pending. |
|
RJCR |
Rejected Cancellation Request |
Used when a requested cancellation has been rejected. |
In the case if Answer indicates RJCR or PDCR, then Narrative1 may contain one or more of the following reason codes:
|
Reason |
Acronym |
Usage |
|---|---|---|
|
AC04 |
Closed Account Number |
Account number specified has been closed on the receiver's books. |
|
AGNT |
Agent Decision |
Reported when the cancellation cannot be accepted because of an agent refuses to cancel. |
|
AW04 |
Insufficient Funds |
Amount of funds avail- able to cover specified message amount is insufficient. |
|
ARDT |
Already Returned |
Cancellation not accepted as the transaction has already been returned. |
|
ARPL |
Awaiting Reply |
A reply is expected from either the customer or the next agent. |
|
CUST |
Customer Decision |
Reported when the cancellation cannot be accepted because of a customer decision. |
|
INDM |
Indemnity Requested |
Indemnity is required before funds can be returned. |
|
LEGL |
Legal Decision |
Reported when the cancellation cannot be accepted because of regulatory rules. |
|
NOAS |
No Answer From Customer |
No response from beneficiary (to the cancellation request). |
|
NOOR |
No Original Transaction Received |
Original transaction (subject to cancellation) never received. |
|
PTNA |
Past To Next Agent |
Cancellation has been forwarded to the next agent in the payment chain. |
|
RQDA |
Requested Debit Authority |
Authority is required by the Creditor to return the payment. |
Narrative (77A)
Specify additional details about the Queries or Answers input in one of the above mentioned fields. The Narrative text can contain up to 700 characters.
Narrative (79)
Specify narrative text for describing the original message, or all transactions in the original multi-credit Customer/Bank transfer message that is being referenced by this Common Group message. Alternatively, this field can also be used for specifying free format text in case of MT 199/MT 299. This field can contain up to a 1750 characters.
Copy of at least the Mandatory Fields of the Original Message
Specify at least the mandatory fields of the original message that is being referenced by this Common Group message. This field can be input instead of ‘Narrative 79’ field but never both.
7.1.5.1 View Message
Click View Message to view the outgoing message details in ‘View Outgoing Message’ sub screen.
7.1.5.2 Viewing Answers Summary
You can invoke “Answers Summary” screen by typing ‘PXSCMN96’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Authorization Status
l Record Status
l Branch Code
l Host Code
l Receiver
l SWIFT Message Type
l Reference Number
l Related Ref(21)
l Transaction Reference Number
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria for the following:
l Authorization Status
l Record Status
l Branch Code
l Host Code
l Receiver
l SWIFT Message Type
l Reference Number
l Related Ref(21)
You can invoke “Proprietary Message” screen by typing ‘PXDCMN98’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Specify the following details.
Branch Code
Displays the selected branch of the logged-in user.
Host Code
System defaults the Host code of the user’s logged in branch.
Reference Number
Displays the Reference Number by default.
Receiver
Specify the Receiver from the list of values.
Receiver Name
The system displays the name of the Receiver upon the selection of Receiver.
SWIFT Message Type
Specify the SWIFT Message Type from the list of values.
Sub Message Type(12)
Specify the value for Sub Message Type(12).
Narrative(77E)
Specify the value for Narrative(77E)
Allowed Character set and validation for n98 Proprietary messages:
For inbound and outbound n98 proprietary message (MT 198, MT 298 and MT 998), field 77E, allows Z and X character sets.
l Special characters allowed in X character set
– / -?: ()., ' +
l Special characters allowed in Z character set
– ., - () / = ' +:?! “% & * < >; { @ # _
– Other characters are not allowed, including the curly bracket '}
7.1.6.1 Viewing Proprietary Message Summary
You can invoke “Proprietary Message Summary” screen by typing ‘PXSCMN98’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Authorization Status
l Record Status
l Branch Code
l Host Code
l Receiver
l SWIFT Message Type
l Reference Number
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or click the ‘Details’ button after selecting a record to view the detailed screen.
You can invoke “Free Format Message” screen by typing ‘PXDCMN99’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Specify the following details:
Processing Branch
Displays the selected branch of the logged-in user.
Host Code
Displays the host code of the logged-in user.
Reference Number
Displays the Reference Number by default.
Transaction Reference Number
System defaults this field with an internal reference number if user input is not entered.
Note
The user is not allowed to change the value of the field 'Transaction Reference Number' in the Free Format Message Detailed (PXDCMN99) screen when launched from Cross Border/RTGS Outbound/Inbound Transaction View Summary (PXSOVIEW/PXSIVIEW) screens using ‘Generate n99’ user action.
7.1.7.1 Main Tab
Click the Main tab in the ‘Free Format Message’ screen.
Specify the following details:
Related Ref(21)
Specify the related reference from the list of values.
Receiver
Specify the Receiver from the list of values.
Receiver Name
The system displays the name of the Receiver upon the selection of Receiver.
SWIFT Message Type
Specify the SWIFT Message Type from the list of values.
UETR
For UETR pick up logic for Common group messages, refer to Section 7.3.3, "UETR population in Outbound Common Core Messages".
Linked Reference Number
Specify the Linked Reference Number from the list of values. Lists all the Outbound/Inbound Cross Border Transaction References of the user logged in host.
Narrative(79)
Specify the value for Narrative(79).
Transaction Details
Transaction Reference
Displays the Transaction Reference if the selected Related Ref is a transaction.
Transaction Type
Displays the Transaction Type/message direction value as either ‘Incoming’ / ’Outgoing’ of the selected Related Ref.
Source Code
Specify the Source Code from the list of values.
Transfer Currency
Displays the Transfer Currency if the selected Related Ref is a transaction.
Original SWIFT Message Type
Displays the SWIFT Message Type of the selected Related Ref for which Free Format message needs to be generated.
Receiver
Displays the Receiver of the original message of Transaction type / Message direction as Outgoing.
Sender
Displays the Sender of the original message of Transaction type / Message direction as Incoming.
Network Code
Displays the Network code of the original Transaction /Message.
7.1.7.2 Pricing Tab
Click the Pricing tab in the ‘Free Format Message’ screen
Specify the following details.
Charge Account
Specify the Charge Account from the list of values which belongs to all valid customer accounts in the host
Charge Currency
System defaults the charge currency of the provided Charge Account
Pricing Code
Specify the Pricing Code from the list of values defined in the SWIFT MT n99 Pricing Maintenance (PXDPRN99) which matches the network code, selected transfer currency (or) *AL transfer currency and transaction type of the ‘Related Ref(21) selected’ and the MT n99 SWIFT message type selected.
Calculate
System enables this button on click of ‘New’ action. On click of this ‘New’ action, if the Charge Account and Pricing Code fields have values then system calculates the charge amount and displays the Pricing component details available under the Charge Amount block [ Refer the ‘Processing Changes ‘ section for more details on charge amount calculation]
Charge Amount block
System populates the values for the below fields on click of ‘Calculate’ button.
l Pricing Component – Displays the Components defined for the provided Pricing Code
l Pricing Currency – Displays the Currency of the each Pricing Component
l Pricing Amount – Displays the calculated charge amount
l Waived – System checks the Waiver flag by default
l Debit Amount – Displays the Equivalent amount which gets debited from Charge Account
7.1.7.3 Accounting Entries
Click the Accounting Entries screen in the ‘Free Format Message’ screen to view the charge accounting entries posted for the MT n99 message.
By default, the following attributes of the Accounting Entries screen are displayed:
l Event Code
l Transaction Date
l Value Date
l Account
l Account Branch
l TRN Code
l Dr/Cr.
l Amount Tag
l Account Currency
l Transaction Amount
l Netting
l Offset Account
l Offset Account Branch
l Offset TRN Code
l Offset Amount Tag
l Offset Currency
l Offset Amount
l Offset Netting
l Handoff Status
Note
System displays the MT n99 message reference number in the Reference number field of this Accounting Entries screen.
7.1.7.4 MIS Tab
Click the ‘MIS’ link to invoke the ‘MIS’ sub-screen to view the MIS details. MIS details of the Related Ref no is defaulted. . You are allowed to change the defaulted MIS value.
Note
System should not default the MIS details if Related ref number isn’t available or not Cross border / RTGS a transaction reference number.
Specify the following details
Transaction Reference
System displays the MT n99 message reference number in the Reference number field of this MIS Tab.
MIS Group
Defaults the MIS group of the Related reference number,. Alternatively, you can select the MIS group code from the option list. The list MIS group displays all valid MIS groups maintained in the system for different sources in the Source maintenance. By default, the MIS group linked to the ‘Manual’ source is populated while booking a transaction from this screen.
Default button
Click this button after selecting a MIS group different from the default MIS Group (which was populated) so that any default MIS values can be populated from to link to the Transaction MIS and Composite MIS classes.
Transaction MIS
The default MIS values for Transaction MIS classes are populated for the MIS group. You can change one or more default MIS values or specify more MIS values. Alternatively, you can select MIS values from the option list.
Composite MIS
The default MIS values for Composite MIS classes are populated for the MIS group. You can change one or more default MIS values or specify more MIS values. Alternatively, you can select MIS values from the option list.
7.1.7.5 View Message
Click View Message to view the outgoing message details in ‘View Outgoing Message’ sub screen.
7.1.7.6 MT n99 Generation Processing Changes
You can invoke the Free Format message screen (PXDCMN99) to generate MT n99 message for a Cross Border/RTGS transaction from the Cross Border/RTGS Inbound/Outbound View Summary screen using this ‘Generate MT n99’ button.
7.1.7.7 Free Format Message – Values Population Logic
On click of ‘Generate MT n99 button’, system launches the screen in ‘New’ operation mode and the N99 Reference Number gets generated and transaction details are auto populated as below:
|
MT n99 Field |
Value Population Logic |
Remarks |
|
Related Ref(21) |
Outbound Transactions – Transaction Reference Inbound Transactions – Source Reference Pass through Transactions – Transaction Reference |
Field is disabled after defaulting |
|
Processing Branch |
Branch from which the message generation is initiated |
Field is disabled after defaulting |
|
SWIFT Message Type |
MT 199 – If transfer type of transaction is ‘Customer Transfer’ MT 299 – If transfer type of transaction is ‘Bank Transfer’ (or) ‘Bank Transfer for Own A/c’ (or) ‘Cover Transfer’ |
Field is disabled after defaulting |
|
Receiver |
For Outbound transactions – Receiver of the Original payment message sent out For Inbound transactions – Sender of the Original payment message received For Pass-through transactions – Receiver of the Original payment message sent out |
Field is disabled after defaulting |
|
Pricing Code |
Default Pricing code will be defaulted from the MT n99 Pricing Preference maintenance based on the transaction’s network code, transaction type, transfer currency and on the defaulted SWIFT message type. This defaulting will not be done if the transaction is a Prefunded-GL transaction |
Defaulted Pricing Code can be changed |
|
Charge Account |
For Outbound transactions – Charge Account if available otherwise Debit Account For Inbound transactions – Credit Account For Pass-through transactions – No defaulting will be done This defaulting will not be done if the transaction is a Prefunded-GL transaction |
Defaulted Charge Account can be changed |
Note
l System implements the above logic if the PXDCMN99 screen launches from the Cross Border/RTGS Inbound/Outbound summary screens.
l System doesn’t allow you to change the Pricing Code, Charge Account, Calculated charge amount and Waiver flag during Unlock action.
7.1.7.8 Charges on Free Format Messages
l Charge Calculation:
On click of ‘Calculate’ button, if the Charge Account and Pricing Code fields have values then system calculates the charge amount .System does this charge amount calculation based on the Pricing Value maintenance. You need to maintain Pricing code value as a flat charge amount.If you maintain Pricing code type other than flat charge amount [E.g. Slab based / Rate base] then system calculates charge amount as Zero.
System considers the STANDARD MID rate in arriving the equivalent charge amount if the Pricing currency is different from the Charge account currency.
You can view the charge amount in the Pricing block.You are allowed to waive the charge component.
Note
System doesn’t consider the Transaction Amount during charges amount calculation.
l Accounting Entries:
– System posts charge accounting entries on authorization of Free format messages input. During the accounting entries posting, system considers the Debit/Credit account pick up, transaction code of the charge component defined using the ‘Accounting Code/Template’ and displays it.
– System passes the posted Accounting entries to the Accounting System. You can view the accounting entries posted for the MT n99 message in the ‘Accounting Entries’ sub –screen.
|
Reference Number |
Event Code |
Debit / Credit Indicator |
Account |
Transaction Code |
Amount |
|
N99 Message Reference |
DRLQ |
Dr |
Charge Account |
Main Transaction Code |
Charge Amount/ Equivalent amount |
|
N99 Message Reference |
DRLQ |
Cr |
Offset Account |
Offset Transaction Code |
Charge Amount |
l MT n99 message Sanctions screening remains as per the existing functionality
l System doesn’t provide any type of support for ECA check before posting charge accounting entries
7.1.7.9 Viewing Free Format Message Summary
You can invoke “Free Format Message Summary” screen by typing ‘PXSCMN99’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using one or more of the following parameters:
l Authorization Status
l Record Status
l Branch Code
l Host Code
l Receiver
l SWIFT Message Type
l Reference No
l Related Ref(21)
l Transaction Reference Number
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or click the ‘Details’ button after selecting a record to view the detailed screen.
If a Non STP Rule with MT 195 triggering preference is maintained, transaction gets logged in an internal table for MT 195 message generation.
A scheduler EOD job refers to new internal table to check if any transaction is populated for which the MT 195. System will trigger the appropriate MT 195 message generation fetched from the static table by linking the field 'Advice ID'.
MT195 message generation are suppressed for the payments with below listed Transaction statuses:
l 'Returned'
l 'Return Requested'
l 'Return Initiated'
l 'Reversed'
l 'Cancelled'
l 'Seized'
7.3 Outbound Common Group Messages - Processing
7.3.1 Network Character Validation for Outbound Common Group
Since Outbound Common Group Messages are manually initiated by Operational users from the relevant screens for claims, advises or investigations; the system does not support automatic replacement of dis-allowed characters input by user.
l On saving a transaction in any Common Group Message screen, the system performs Network characters validation for the presence of dis-allowed characters as per the SWIFT “X” character set.
l Error message is displayed on failure of this validation, and the transaction is not saved unless the user corrects the error(s).
7.3.2 Sanction Scanning of Outbound Common Group Messages
On authorization of any Common Group message Outbound transaction, system generates the Common Group message and initiates Sanction check.
The generated message is embedded in a message block of Sanctions request XML to Sanctions system.
On receiving an Approved response from Sanctions system, the Common Group message is generated and sent to SWIFT.
If any status other than Approved is received from Sanctions system then system moves the Common Group message transaction to the existing Sanctions queue.
l In the queue screen, a new column in the grid called “SWIFT Message Type” would have a value of the message type of the common group message. E.g. MT 195, MT 199. For payment transactions, this column would be empty. This would help in filtering or sorting on this column to view all Common Group message transactions.
l You would be able to take appropriate action on the transaction in the queue like in the case of payment transactions in the queue.
l If Auto-cancellation has been configured for a Reject response from Sanctions then the Common Group message transaction would be auto-cancelled similar to payment transaction.
7.3.3 UETR population in Outbound Common Core Messages
If the UETR value is present in the related payment transaction (or message) reference(21) then on enrich or select of the related payment reference (or message reference), system populates this UETR field value in the corresponding common group messages screens.
This field is disabled.
For the messages i.e.,MT 190, MT 191, MT 192 (292/992), MT 195 (295/995), MT 196 (296/996), MT 199 (299/999), system copies the UETR field value in the field 121 of the user header block 3.
For the n92, n96 messages (non-gSRP) generates through Outbound Cross Border Cancellation Request (PXDTRNCL), Inbound Cancellation Browser (PXSICLBR > PXDCLREQ) screens, system copies UETR value in the field 121 of the user header block 3 of the messages.
7.4 Inbound Common Group Messages
Support is available to process the below Inbound Common group messages received from SWIFT and to link the same to the Original transaction reference based on the Related Reference Number
l MT 190, MT 290, MT 990 – Advice of charges
l MT 191, MT 291, MT 991 – Request for charges
l MT 192, MT 292, MT 992 – Request for cancellation
l MT 195, MT 295, MT 995 – Queries
l MT 196, MT 296, MT 996 – Answers
l MT 198, MT 298, MT 998 – Proprietary Message
l MT 199, MT 299, MT 999 – Free Format Message
Inbound messages gets uploaded once its Sanctions scanned & Sanctions response is Success. For more details, refer Section 7.4.1, "Sanction Scanning of Inbound Common Group Messages" on Sanctions scanning for Inbound messages.
7.4.1 Sanction Scanning of Inbound Common Group Messages
On receipt of any Inbound Common Group message and subsequently matching it with a payment transaction, the system sends the actual received message to Sanctions system for scanning.
l This involves sending of the actual SWIFT message embedded in the Sanctions request XML to Sanctions system.
l During matching, if match is found then the transaction reference number of the original transaction is updated in the "Cross Border Contract Reference Number" field against the MT n99/MT n96/MT n91/MT n92 message record present in the Common Group Message Sanction Summary (PQSSNCST) screen.
Note
The above second bullet point is only applicable after receiving the incoming MT n99, MT n96, MT n91 and MT n92 messages.
l If the received message was repaired in the Inbound Message Browser then the repaired message is sent for Scanning.
On receiving an Approved response from Sanctions system, the Inbound Common Group message is linked to the matched payment transaction and processed further when it is applicable (e.g. MT 191 claim processing).
For status except Approved from Sanctions system, system moves the Inbound Common Group message to the Sanctions queue.
l In the queue screen, ‘SWIFT Message Type’ identifies the Inbound Common Group message transactions.
l You can take up appropriate action on the message in the queue.
l Configure Auto-cancellation for a Reject response from Sanctions to auto cancel the Inbound Common Group message.