For the complete documentation index, see llms.txt. This page is also available as Markdown.

Incoming BACS Mandate Cancelled Notification

Description of Incoming BACS Mandated Cancelled Notification service.

Service Description

The Mandate Cancellation Notification Service provides customers with prompt notification when a Direct Debit Mandate is cancelled by a Service User via AUDDIS (the Automated Direct Debit Instruction Service). This alerts the customer as soon as a cancellation instruction has been processed, rather than customers only discovering the change when an expected payment fails to collect.

This service should be used by the customer to maintain full visibility over their Direct Debit instructions, helping them stay informed of changes made by Service Users and reducing the risk of confusion, missed payments, or unexpected gaps in scheduled collections.

The standard AUDDIS process for managing mandate cancellations remains unchanged. This service complements that process, offering customers an additional layer of awareness whenever a mandate they hold on behalf of their customers is cancelled.

If you would like to subscribe to incoming Bacs notifications, please contact your relationship manager.

Incoming BACS Mandate Cancelled Notification

Incoming Bacs Mandate Cancelled Notification can be requested via the Messages Services.

HTTP Header Message-Response-Type: DIRECT_DEBIT_MANDATE_SCHEME_CANCEL

Body

Field

M/O

Description

Mandate.Beneficiary

M

Beneficiary / creditor party details.

Mandate.Beneficiary.AccountName

M

Creditor name stored on the mandate.

Mandate.Beneficiary.AccountNumber

M

Creditor account number part only, without sort code.

Mandate.Beneficiary.AccountNumberCode

M

Always BBAN.

Mandate.Beneficiary.Bank

M

Beneficiary bank details.

Mandate.Beneficiary.Bank.BankId

M

Creditor sort code part of the stored local account number.

Mandate.Beneficiary.Bank.BankIdCode

M

Always GBDSC.

Mandate.Debtor

M

Debtor party details.

Mandate.Debtor.AccountName

M

Debtor name stored on the mandate.

Mandate.Debtor.AccountNumber

M

Debtor account number part only, without sort code

Mandate.Debtor.AccountNumberCode

M

Always BBAN

Mandate.Debtor.Bank

M

Debtor bank details

Mandate.Debtor.Bank.BankId

M

Debtor sort code part of the stored local account number

Mandate.Debtor.Bank.BankIdCode

M

Always GBDSC

Mandate.OriginalMandateId

M

Internal/original mandate identifier

Mandate.Reference

M

Mandate reference

Mandate.ClearingId

M

Service User Number / clearing identifier

Status

M

Mandate status at notification time, for this flow CANCELLED_BY_SCHEME

ReasonCode

M

Always MD17

Reason

M

Always Cancelled by Service User/creditor

DateClosed

M

Date the mandate was closed, formatted as yyyy-MM-dd

Example

Example of the flow

Step

Action

Description

1

Receive Mandate Cancelation

LHV receives mandate cancelation from the Bacs scheme. This step confirms that there is an active mandate in the system that can be cancelled

2

Notification

LHV will cancel the Mandate and send a notification to the customer

Last updated

Was this helpful?