SEPA Payment Status Report ISO 20022 Technical Specification



Similar documents
SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES

Payment Status Report

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report

SEPA Direct Debit Acknowledgement Danske Bank's interpretation of ISO pain (Payment Status Report)

Format Description XML SEPA CT

Format description XML SEPA Credit Transfer

SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES

XML Message for SEPA Direct Debit Initiation

Format description pain.002, technical. Rabo Cash Management, Rabo Direct Connect & Rabo Internetbankieren (Pro)

OUTGOING PAYMENTS ISO APPLICATION GUIDELINE

OUTGOING PAYMENTS ISO APPLICATION GUIDELINE

ISO PAYMENT GUIDE. Messages: Pain Pain

SEPA Direct Debit PAIN XML File Structure

Impact of SEPA on CODA2.3 for SEPA credit transfer (SCT) version April ing.be/sepa

ISO XML pain.001 implementation guide in Handelsbanken Estonia, Latvia, Lithuania

SEPA Direct Debit Initiation Danske Bank's interpretation of ISO pain (Direct Debit Initiation)

Format description XML SEPA Credit Transfer

Format Description XML SEPA DD

SEPA Direct Debit Cancellation Danske Bank's interpretation of ISO camt (Payment Cancellation Request)

XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands

SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

Appendix for BSK Implementerings Guides ISO 20022

ISO Message Implementation Guide for Payment Initiation

SEPA Direct Debit Unpaid Report File Format

Standards MX Message Implementation Guide and Rule Book

Format description SEPA DD ISO20022 (for Euro Direct Debits)

Format Description SWIFT MT940 Structured

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands

PAIN.002. Format description Functional

SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

Format description XML SEPA Credit Transfer. Format Description

Format description SEPA Direct Debit (for Euro Direct Debits) Rabo Cash Management

Danske Bank Message Implementation Guide Common Global Implementation (CGI) Customer Credit Transfer pain

SEPA Reason Codes. Direct Debit Customer to Bank Implementation Guidelines

XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands

Functional specification for Payments Corporate egateway

ISO ACCOUNT STATEMENT GUIDE. v 1.3

Guidance on reason codes for SDD R-transactions

Format Description MT940. Rabo Cash Management

ISO Message Implementation Guide for Cash Management Reports

Payments Market Practice Document. ISITC Settlements Working Group

Core Fittings C-Core and CD-Core Fittings

ERP SEPA readiness checklist

>

en (pf.ch/dok.pf) PF. EPO manual Electronic payment order via file transfer

March Euro Payment. Manual

Record description XML File Transfer Balance and Transaction list camt

SEPA BUSINESS-TO-BUSINESS DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES

en (pf.ch/dok.pf) PF. Manual PostFinance ISO messages for banks [pacs messages]

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

XML message for Payment Initiation Implementation Guideline. Version 1.02

Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010

Format Description. SWIFT MT103 Single Customer Credit Transfer

SEPA formats - an introduction to XML. version September

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

This translation has been prepared with the greatest possible care; however, in case of doubt, the German text is the authoritative version.

SEPA DATA MODEL. Reason for Issue Approved by the EPC Plenary on 13 December 2006

Format Description. SWIFT MT202: General Financial Institution Transfer

How To Create A Credit Card From A Creditcard In A Microsoft Web Server On A Microsql Web Server

DESCRIPTION OF SEPA XML FORMAT FOR ING BUSINESSONLINE IMPORT AND EXPORT TEMPLATES

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

Functional specifications for Nordea XML Direct Debit (NDD) Corporate egateway

SEPA Customer File Formats-Definition Proposals

KANSAS CITY SOUTHERN EDI On-Boarding Guide

SEPA Credit Transfer. Readiness Checklist

SEPA Direct Debit Creditor Guide

XML ACCOUNT STATEMENT. Service Description

SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands

VERSION: ANSI X

Oracle FLEXCUBE Direct Banking Release Retail Transfer and Payments User Manual. Part No. E

Occasions leading to mandate amendments

999 Implementation Acknowledgment. Version: 1.0 Draft

PaperCut Payment Gateway Module PayPal Website Payments Standard Quick Start Guide

Release Notes Metered, Switched, Metered-by-Outlet, and Metered-by-Outlet with Switching Rack PDUs

SEPA Credit Transfer. C2B Technical Specification Pain

ANSI X12 version Remittance Advice

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

SEPA Country Guide Italy. Introduction

Batch Validation Tool User Guide

Nokia Internet Modem User Guide

The Business Application Header is a header that has been defined by the ISO community,

Electronic Data Interchange

Single Euro Payments Area (SEPA) with Oracle E-Business Suite for German Banks

X12 Implementation Guidelines For Outbound Receiving Advice v (861O)

Customer Statement - MT940 with Structured Information To Account Owner

Contents of the ISO 9001:2000 Quality System Checklist

How to start Data Entry of Monographs and Books in e-granthalaya 3.0

SEPA CREDIT TRANSFER SCHEME RULEBOOK

Implementation Guideline

Deutsche Bank Global Transaction Banking. Internet Bankieren. Entering Payments and Collections.

ideal Merchant Integration Guide

Deutsche Bank Deutsche Bank MT940/942 format specifications

Formats for Internet Bank

pg. 2 pg. 6 pg.8 pg. 20

BEST client format supported by KB (valid from 28th November 2015)

Version 3.8, June 14th, 2015

SWIFT Certified Application - Exceptions and Investigations

Transcription:

SEPA Payment Status Report ISO 20022 Technical Specification

Message name pain.002.001.02 A Payment Status Report is produced when files fail the reception controls or every time the PmtInfo or Transaction fails booking attempts. Additionally a Payment Status Report is also produced when the SCCT material has passed technical and content validation. GrpSts shows the status of the material as one of the following ACTC, ACCP, RJCT, PDNG or PART. RJCT is a rejected file, PART is a partially accepted file, PDNG is a file where transactions are still pending, ACTC status is a file that has passed technical validation and ACCP is the status for a file that has also passed content validation. The status report uses the UTF-8 character set. For showing all characters correctly in the message it should be retrieved in Binary form. Ref. Message Item Definition/ Rules /Guidelines A Group Header A++ MessageIdentification A++ CreationDateTime <MsgId> <CreDtTm> A++ InitiatingParty <InitgPty> A+++ >> Identification (0..1) <Id> + {Or >>> OrganisationIdentification BankPartyId Or} >>> PrivateIdentification <OrgId> <BkPtyId> <PrvtId> A++ DebtorAgent <DbtrAgt> A+++ FinancialInstitutionId <FinInstnId> Unique identification of the message assigned by the Initiating Party. (max.35 Text) Date and time at which the status report was created by the instructing party. Must not be in the future. (ISO date time) Identification of a corporate Identification of a private person. (max.35 Text) BIC mandatory Ref. Message Item Definition/ Rules / Guidelines B. OriginalGroupInformatio nandstatus (Or >>OriginalMessageIdentifi cation <OrgnlMsgId > Point to point reference assigned by the original instructing party to identify the original group of individual transactions.(max35text) OrinalMessageNameIdent ification <OrgnlMsgN mid> Specifies the original message name identifier to which the message refers, eg. pain.001.001.02 (max35text) OriginalCreationDateTime (0..1) <OrgnlCreDt Tm> Original date and time at which the message was created (ISODateTime) OriginalNumberOfTransa ctions (0..1) <OrgnNbOfT xs> Number of individual transactions contained in the original message. (max15numerictext)

Ref. Message Item Definition/ Rules / Guidelines GroupStatus (0..1) <GrpSts> Specifies the status of a group of transactions. Valid statuses are ACTC, ACCP, RJCT, PDNG and PART. + StatusReason (0..1) <StsRsn> Specifies the reason for the status report (code) Ref. Message Item Definition/ Rules / Guidelines C. TransactionInformationA ndstatus OriginalPaymentInformati onidentification (0..1) OriginalInstructionId (0..1) OriginalEndToEndIdentific ation (0..1) TransactionStatus (0..1) >>StatusReasonInformati on (0..1) <OrgnlPmtInf Id> <OrgnlInstrId > <OrgnlEndTo EndId> <TxSts> <StsRsnInf> Unique identifier of the original payment information block as assigned by the original sending party. (max35text) Unique identification, as assigned by the original instructing party for the original instructed party, to unambiguously identify the original instruction. Original identification assigned by the initiating party to identify the original transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. (max35text) Specifies the status of a transaction, in a coded form. Valid statuses are RJCT, PDNG and ACSP. Detailed information on the status reason. + >>>StatusOriginator (0..1) <StsOrgtr> Party issuing the status. BIC mandatory + >>>StatusReason (0..1) <StsRsn> Specifies the reason for the status report + <Cd> >>>>Code Reason for the status in a coded form + >>>>AdditionalStatusRea <AddtlStsRs + osoninformation (0..1) ninf> Further details on the status (max105text) AcceptanceDateTime (0..1) <AccptncDtT m> Date and Time when the payment order from the initiating party meets the processing conditions of the account servicing agent. (ISODateTime)

Status Reason Codes in use: Code Name TxSts AC01 IncorrectAccountNumber RJCT AC04 ClosedAccountNumber RJCT AC06 BlockedAccount RJCT AG01 TransactionForbidden RJCT AG02 InvalidBankOperationCode RJCT AM01 ZeroAmount RJCT AM02 NotAllowedAmount RJCT AM03 NotAllowedCurrency RJCT AM04 InsufficientFunds RJCT AM05 Duplication RJCT AM07 BlockedAmount RJCT AM09 WrongAmount RJCT AM10 InvalidControlSum RJCT BE01 InconsistentWithEndCustomer RJCT BE04 MissingCreditorAddress RJCT BE05 UnrecognisedInitiatingParty RJCT BE06 UnknownEndCustomer RJCT BE07 MissingDebtorAddress RJCT C101 MaxAmountHasBeenReached RJCT C201 GroupheaderisMissingorIncorrect RJCT C202 InitiatingPartyMissing RJCT C301 PaymentInformationisMissing RJCT C302 PaymentMethodisMissingorIncorrect RJCT C303 DebtorisMissing RJCT C304 DebtorIdisMissing RJCT C305 DebtorCountryisMissing RJCT C308 DebtorNotaBLCustomer RJCT C309 DebtorAccountnotPayableinBL RJCT C310 NoRighttoIntermidiate RJCT C311 DebtornotOwnerofAccount RJCT C312 WrongDebtorAccountType RJCT C313 DbtrAccntBlockedforOutgoingTransac RJCT C314 DbtrNotRighttowithdrawfunds RJCT C315 PaymenMethodmissingorincorrect RJCT C316 DebtorHasNotServiceConnected RJCT C317 AccountHasLightWarning RJCT C318 ReqExecDateChanged ACSP C401 CreditTransferTransactInfoisMissing RJCT C402 PaymentIdentificationIsMissing RJCT C403 WrongFileFormatEndToEndIdMissing RJCT C404 CreditorisMissing RJCT C405 CreditorCountryisMissing RJCT C406 CreditorNameMissing RJCT C407 TAXSReferenceNotValid RJCT

C408 DbtrAcctSameasCdtrAcct RJCT C409 credtoraccountwrongcurrency RJCT C410 taxaccountwrongtype RJCT C411 taxaccountdemandsreference RJCT C412 taxaccountdemandsmessage RJCT C413 taxaccountwrongmessage RJCT C414 SALA_creditorNotValidSepa RJCT C415 SALA_debtorAccCcyNotValid RJCT C434 InsufficientFunds PDNG DT01 InvalidDate RJCT ED01 CorrespondentBankNotPossible RJCT ED03 BalanceInfoRequested RJCT ED05 SettlementFailed RJCT MD01 NoMandate RJCT MD02 MissingMandatoryInformationInMandat RJCT MD03 FileFormatIncompleteOrInvalid RJCT MD04 InvalidFileFormatForGroupingIndicat RJCT MD06 RefundRequestByEndCustomer RJCT MD07 EndCustomerDeceased RJCT MS02 NotSpecifiedReasonCustomerGenerated RJCT MS03 NotSpecifiedReasonAgentGenerated RJCT NARR Narrative RJCT PC01 MissingCreditororIncorrectAccountNo RJCT PC02 MissingDebtororIncorrectAccountNumb RJCT PC03 UnknownDebtorAccountNumber RJCT PC04 CancelledInstruction RJCT PC05 NotCancelledInstruction RJCT PC06 CreditorDemandOCR RJCT PC07 MissingOrErrorOCR RJCT RC01 BankIdentifierIncorrect RJCT RF01 NotUniqueTransactionReference RJCT RR01 RegulatoryReason RJCT TM01 CutOffTime RJCT NARR FailSchema RJCT