Pacs.003 Message Upload
File level Validations
- File format validations - This is done based on the XSD maintained in the 'Schema Definition File Path' for the file type 'ACHDDReceipt' in File Parameters Detailed screen PMDFLPRM.
- Validation of Number of transactions and control sum in the file, if available
- Uniqueness of Message ID of the incoming message
If any of the above listed validations fails, the file is rejected.
- Host Code
- Transaction Branch
- Network Code - It is assumed that Network Code is provided for inward files received from clearing houses. The Network code received is mapped to every transaction record.
- If the file is received without Network code, individual transactions are sent directly to the ACH DD Receipts processor without Date derivation and File accounting checks
- Source Code
You can receive the settlement date in the Group Header ((FIToFICstmrDrctDbt/GrpHdr/ / IntrBkSttlmDt) or as part of Transaction Information in the tag (FIToFICstmrDrctDbt/ DrctDbtTxInf/ /IntrBkSttlmDt) in the inbound pacs.003 message. The Settlement Date received at transaction level is given priority and if this is not available, the Settlement date received in the group header is considered. This date is considered as the instruction Date received.
Instruction Date Derivation
Processing dates derivation is done for each transaction record, provided Network code is available. If Instruction Date received is a past date, the handling is based on the preference 'Back Value Date Handling' in ACH DD Receipt preferences (Function ID: PZDINPRF). If the preference is to Retain as Original Value date, the Instruction Date is the Settlement Date received, even if it is a Back Date.
If the Instruction Date is a back date and the preference is maintained as 'Adjust to current date', the Instruction Date is considered as current date. If current date is a Network holiday, the instruction date is rolled over to next Network working day.
Both Network holiday check and transfer currency holidays is applied if the Network preference is 'Adjust to Current Date'. The instruction date is moved forward accordingly Holiday checks are not applicable if the preference is 'Retain as Original Value Date'.
Activation Date Derivation
- Instruction date is not a back date
- Instruction Date is not Branch Holiday
If instruction date is a Branch holiday, Activation Date is moved forward or back ward (provided it is not a back date) to next working date based on preference maintained for Activation Date Movement in ACH DD Receipts Preferences (Function ID:PZDINPRF).
If the Instruction Date is a back date, the Activation Date is derived as current date provided current date is a Branch working date. If current date is a holiday, Activation date is the next Branch working date.
File Accounting
System checks whether file accounting required flag is checked for the Network. If file accounting is not applicable, the transaction records are send for individual transaction processing.
If Receipt accounting is applicable, File Accounting Code is fetched from ACH Debit Receipts Preferences PZDINPRF - Main Tab is used for accounting entries generation. The transactions with same Instruction Date and currency is grouped and file accounting is posted for the consolidated amounts for each group.
| Receipt Accounting | Event | Dr/Cr | Account | Account Type | Amount Tag |
|---|---|---|---|---|---|
| DD Receipts - Collection | ZIRC | Dr | Network Clearing GL | GL | PMT_STTL_AMT |
| DD Receipts - Collection | ZIRC | Cr | Nostro Account | Account | PMT_STTL_AMT |
The interbank settlement amount FIToFICstmrDrctDbt/ DrctDbtTxInf/ IntrBkSttlmAmt for each transaction is considered for arriving at the consolidated Amount for the Amount Tag PMT_STTL_AMT.
Sending the transaction records to ACH Debit Receipts Processor
The individual receipt transaction records of the message is sent for processing to ACH Debit Receipts processor.
Parent topic: Upload of pacs.003 Messages