> For the complete documentation index, see [llms.txt](https://docs.lhv.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lhv.com/home/connect/services/indirect-scheme-access/payment-collection-services/bacs-direct-debit/incoming-bacs-credit-notification.md). # 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](/home/connect/services/messages.md). {% hint style="info" %} HTTP Header Message-Response-Type: DIRECT\_DEBIT\_MANDATE\_SCHEME\_CANCEL {% endhint %} ### 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 ```json { "Mandate": { "Beneficiary": { "AccountName": "Creditor Name", "AccountNumber": "25677513", "AccountNumberCode": "BBAN", "Bank": { "BankId": "600102", "BankIdCode": "GBDSC" } }, "Debtor": { "AccountName": "Debtor Name", "AccountNumber": "20266221", "AccountNumberCode": "BBAN", "Bank": { "BankId": "600102", "BankIdCode": "GBDSC" } }, "OriginalMandateId": "dfd78e01-de34-4b62-9fb3-e80b992332a3", "Reference": "D/1234567890123400", "ClearingId": "280421" } "Status": "CANCELLED_BY_SCHEME", "ReasonCode": "MD17", "Reason": "Cancelled by Service User/creditor", "DateClosed": "2024-02-23" } ``` 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

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lhv.com/home/connect/services/indirect-scheme-access/payment-collection-services/bacs-direct-debit/incoming-bacs-credit-notification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.