In this transaction payment instructions are registered, the applicant'/originator's account is debited, the amount is credited to the specified account (beneficiary or correspondent account) and with “Payment Type” = “Outgoing Payments”:
Roll | Condition | Contents |
---|---|---|
Applicant (ORC) | If ORI = empty | * Debiting payment amount * Debiting our fees to applicant * Debiting external fees (if known) |
Applicant's bank (ORI) | If ORI is not empty (for all types of payment) | * Debiting received amount (payment amount - external fees) * Debiting our fees to applicant * Debiting our fees of interim bank(s) (if known) |
Paying Bank (PYB) | Outgoing or forwarded payment | * Crediting received amount, less our fees to paying bank, plus fees from interim bank(s) (if known) |
Beneficiary (PYE) | Incoming payment | * Crediting received amount * Debiting our fees |
In case a bank using the application activated further “Payment Types” based on individually implemented rules and requirements, then with
There might be scenarios where an outgoing payment should be booked/registered but requires an additional authorization for final settlement of the payment. In these situations a temporary settlement can be created via the standard settlement panel. On the settlement panel it is defined, whether it is a 'temporary' or a 'final' settlement. The settlement can be selected as 'Temporary' and the contract can be saved. For temporary settlement, the relevant payment messages are not yet generated. Also the accounting entries will not be posted.
Please refer to Preliminary (temporary) settlements for more details.
Once authorization is received, the user could return to this transaction (Settling a Clean Payment) and complete the payment by loading the temporary settlement and processing it as 'Final'. Thereafter, the relevant payment messages are generated and actual accounting entries are posted/booked.
This transaction creates a new Clean Payment contract.
If an existing Clean Payment contract is used, it may not be open or closed.
None
For more information see TRNDIA Diaries.
None
Details on creation of messages can be found under DOCEOT Messages.
Name of Message | Receiver | Message ID | SWIFT | Comment |
---|---|---|---|---|
Acknowledgment & Debit Advice | Ordering Customer | CPTORC1 | ||
Debit Advice | Ordering Institution | CPTORI1 | 199 | |
Credit Advice | Payee | CPTPYE1 |
Signature required
Overview
Liability
Settlement Details
Settlement
Bookings
Cash Cover
DTAEA Fields
DTALC Fields
Completion
Incoming Tag 72/79
Messages
Compliance
Attachments
Fee Conditions
allNETT Fields
DTAG Fields
Shipment Details
Datafield | Description |
---|---|
Own Reference | cf Appendix A, Table CPD field OWNREF |
Responsible User | cf Appendix A, Table CPD field OWNUSR |
Payment Type | cf Appendix A, Table CPD field PAYTYP |
Currency | cf Appendix A, Table CBB field CUR |
Nominal Amount | cf Appendix A, Table CBB field AMT |
Currency | cf Appendix A, Table CBB field CUR |
Maximum Amount | cf Appendix A, Table CBB field AMT |
Value Date | cf Appendix A, Table CPD field VALDAT |
Provide Shipment Details | cf Appendix A, Table CPD field SHPFLG |
Details of Charges | cf Appendix A, Table CPD field DETCHGCOD |
Our fees to be debited to | cf Appendix A, Table CPD field CHATO |
Goods Code (for Statistics) | cf Appendix A, Table CPD field STAGOD |
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
External Key | cf Appendix A, Table PTS field EXTKEY |
Address Block | cf Appendix A, Table PTS field ADRBLK |
Reference for Address (Optional) | cf Appendix A, Table PTS field REF |
Datafield | Description |
---|---|
Beneficiary Account No. | cf Appendix A, Table CPD field ANTINCBENACC |
Datafield | Description |
---|---|
Shipment from | cf Appendix A, Table CPD field SHPFRO |
Port of Loading | cf Appendix A, Table CPD field PORLOA |
Port of Discharge | cf Appendix A, Table CPD field PORDIS |
For Transportation to | cf Appendix A, Table CPD field SHPTO |
Transport Document Type | cf Appendix A, Table CPD field TRPDOCTYP |
Transport Document Number | cf Appendix A, Table CPD field TRPDOCNUM |
Date of Transport Document | cf Appendix A, Table CPD field TRADAT |
Mode of Transport | cf Appendix A, Table CPD field TRAMOD |
Vessel Name | cf Appendix A, Table CPT field VESNAM |
Identification of Goods | cf Appendix A, Table CPT field ROGGOD |
Incoterm Version | cf Appendix A, Table CPD field INCTRMVER |
Incoterm Code | cf Appendix A, Table CPD field INCTRMCOD |