Step 4: Amendments and bank files

Concept

The purpose is to generate the SDD bank file with amendments.

All relevant mandate information has to be sent by the creditor with every collection, in the elements of the “pain.008” XML message.

Electronic remittances (FICMAG)

Open: A/P-A/R accounting>Remittances>Electronic remittances

Electronic remittances

Use this function to issue electronic remittance files related to already generated remittances.

Structure of SDD XML bank file

Message structure

The Customer Direct Debit Initiation message contains structured data grouped in blocks. The main building blocks of Customer Direct Debit Initiation message are defined as schema “pain.008.001.02” that is used for CORE/COR1 as well as for B2B.

	Message item	Meaning
A	GroupHeader
	MessageIdentification	Message ID
	CreationDateTime	Actual Date/Time of creation
	NumberOfTransactions	Number of transactions for any DirectDebitTransactionInformation
	ControlSum	Sum of all the InstructedAmount elements
	InitiatingParty	Party that initiates the payment
B	PaymentInformation	Payee Information
	PaymentInformationIdentification	Remittance ID
	PaymentMethod	DD
	BatchBooking	True/False
	CodeScheme	SEPA
	CodeInstrument	CORE or COR1 or B2B
	SequenceType	FRST or RCUR or FNAL or OOFF
	RequestedCollectionDate	Due date of remittance
	Creditor	Name of creditor account owner
	CreditorAccount	Creditor account number (IBAN)
	Currency	Currency of creditor account
	CreditorAgent	Creditor’s Bank (BIC)
	UltimateCreditor	Name of final creditor
	ChargeBearer	SLEV
	CreditorSchemeIdentification	SEAP creditor identifier (CI)
C	DirectDebitTransactionInf.	Payment detail
	PaymentIdentification	Payment ID
	EndtoEndIdentification	Payment reference
	Amount	Payment amount
	MandatIdentification	Unique mandate reference (UMR)
	DateOfSignature	Mandate signature date
	AmendmentIndicator	True/False
	OriginalMandateID	Used if AmendmentIndicator = True
	OriginalCreditorName	Used if AmendmentIndicator = True
	OriginalCreditorID	Used if AmendmentIndicator = True
	OriginalDebtorAccount	Used if AmendmentIndicator = True
	OriginalDebtorAgent	Used if AmendmentIndicator = True
	DebtorAgent	Debtor’s Bank (BIC)
	Debtor	Name of debtor account owner
	DebtorAccount	Debtor account number (IBAN)
	UltimateDebtor	Name of final debtor
	Purpose	Purpose of the collection
	RemittanceInformation	Remittance information from creditor

Process

The original mandate information also has to be included in the message and match the details for the previous collection.

If these data are absent, the creditor is exposed to the rejection of its operations.

In case of an amendment, the system must present the next SEPA Direct Debit instruction as follows:

If one or several amendable fields have been modified:

• The Amendment indicator field (<AmdmntInd>) shows the value True.

• The original and the amended data are both delivered with the instruction:

  • OriginalMandateIdentification <OrgnlMndtId>

  • OriginalCreditorSchemeIdentification <OrgnlCdtrSchmeId>

  • OriginalDebtorAccount <OrgnlDbtrAcct>

  • OriginalDebtorAgent <OrgnlDbtrAgt>

In case of a change of debtor bank (if the IBAN and BIC are different):

• The field OriginalDebtorAgent shows the SMNDA code (same mandate new debtor agent).

• The field Sequence Type shows the value FRST.

• The original debtor IBAN must not be provided.

The original and the amended data are delivered from the OLDVAL and NEWVAL fields of the amendments table (HISTOAMD).

If there is no amendment related to the receipt entry, the original data are not provided. The other information is fetched from the company and payment tables.

Exception

If an amendment about the company name or creditor identifier is created after the receipt entry, the bank file presents the company/creditor identifier information from the amendments table (OLDVAL field), in order to guarantee information consistency.

Limitations

Management of amendments must be done carefully.

Before starting the collection processing, it is necessary to define the rules.

Approved/adjourned mandates:

• If a SMNDA amendment is deleted, the sequence of the related receipt entry remains FRST. There is no roll-back to the initial sequence.

  • In this case, the receipt entry must be deleted and re-created in order to have the correct sequence.

• If a IBAN amendment exists and is related to a receipt entry, the modification of the IBAN and BIC fields does not imply the presentation of the SMNDA code nor the forcing of the sequence to FRST value.

  • In this case, the receipt entry must be deleted and re-created after the modification of IBAN/BIC fields in the mandate.

Expired/revoked mandates:

If the company name (CPYNAM) or the creditor identifier (SCINUM) is changed and if there is no amendment related to the mandate, the system does not create a new amendment.

But the creditor name (<Nm>) and the creditor identifier (<Id>) shows the last entered values in the company table.

In this case, the bank file must be generated before the modification.