# Incoming Bacs Credit Notification

## Service Description

The Incoming Bacs Credit Notification Service provides customers with advance notification of upcoming inbound Bacs payments. Unlike the standard notification process, where customers are informed on Day 3 of the Bacs cycle when the actual settlement occurs, this service allows customers to receive notifications earlier, on Day 2 of the cycle.

This service is ideal for customers who wish to gain earlier visibility of incoming payments to improve planning and operational efficiency. Notifications on Day 2 provide preliminary information about the payment before settlement is finalized.

The regular process of sending credit and debit notifications on Day 3 remains unchanged, ensuring that customers still receive confirmation of settled transactions. This service complements the standard notification flow, offering additional flexibility for customers who require earlier payment insights.

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

## Incoming Bacs Credit Notification

Incoming Bacs Credit Notification can be requested via the [Messages Services](/home/connect/services/messages.md).

{% hint style="info" %}
HTTP Header Message-Response-Type: BACS\_INCOMING
{% endhint %}

### Body

<table><thead><tr><th width="371">Field</th><th width="84">M/O</th><th>Description</th></tr></thead><tbody><tr><td>Payment.Beneficiary.AccountName</td><td>M</td><td>Name of beneficiary as given with account.</td></tr><tr><td>Payment.Beneficiary.AccountNumber</td><td>M</td><td>Beneficiary account number.</td></tr><tr><td>Payment.Beneficiary.AccountNumberCode</td><td>M</td><td>The type of identification given with beneficiary account number. Always <strong>BBAN.</strong></td></tr><tr><td>Payment.Beneficiary.Bank.BankId</td><td>M</td><td>Beneficiary agent identification. Beneficiary sort code.</td></tr><tr><td>Payment.Beneficiary.Bank.BankIdCode</td><td>M</td><td>The type of identification given with beneficiary BankId. Always <strong>GBDSC</strong>.</td></tr><tr><td>Payment.Debtor.AccountName</td><td>M</td><td>Name of debtor as given with account.</td></tr><tr><td>Payment.Debtor.AccountNumber</td><td>M</td><td>Debtor account number.</td></tr><tr><td>Payment.Debtor.AccountNumberCode</td><td>M</td><td>The type of identification given with debtor account number. Always <strong>BBAN.</strong></td></tr><tr><td>Payment.Debtor.Bank.BankId</td><td>M</td><td><p>Debtor agent identification.</p><p>Debtor sort code.</p></td></tr><tr><td>Payment.Debtor.Bank.BankIdCode</td><td>M</td><td>The type of identification given with debtor BankId. Always <strong>GBDSC</strong>.</td></tr><tr><td>Amount</td><td>M</td><td>Amount of money moved between the instructing agent and instructed agent. Format uses decimal point.</td></tr><tr><td>ClearingId</td><td>O</td><td>Bacs Service User Number (SUN) of the payment originator. Must be a numeric 6-digit value.</td></tr><tr><td>Currency</td><td>O</td><td>Currency of the transaction amount. Always <strong>GBP</strong>.</td></tr><tr><td>NumericReference</td><td>O</td><td>Numeric reference field.</td></tr><tr><td>SchemeTransactionId</td><td>M</td><td>Transaction ID.</td></tr><tr><td>UniqueSchemeId</td><td>M</td><td>Bacs transaction reference, only present for incoming payments. Field 14 of the Bacs 18 standard mapping. Bacs do not guarantee this field to be unique and warn the format is subject to change.</td></tr><tr><td>PaymentScheme</td><td>M</td><td> Always <strong>BACS.</strong></td></tr><tr><td>ProcessingDate</td><td>M</td><td>Day 3 of the Bacs cycle. The day on which settlement occurs.</td></tr><tr><td>SchemeProcessingDate</td><td>M</td><td>Day 2 of the Bacs cycle. The day on which the notification of an upcoming payment is received.</td></tr><tr><td>Reference</td><td>M</td><td>Payment reference.</td></tr><tr><td>SchemePaymentType</td><td>M</td><td>Always <strong>Credit</strong>.</td></tr><tr><td>AccountServicerReference</td><td>M</td><td>Unique payment ID assigned by the bank. Refer to the AcctSvcrRef value in the <a href="/pages/HBt7DL80zOAE6HTVdKPi">camt.054 </a>message.</td></tr></tbody></table>

#### Example

```json
{
  "Payment": {
    "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"
      }
    },
    "Amount": "10.01",
    "ClearingId": "280421",
    "Currency": "GBP",
    "NumericReference": "0002",
    "SchemeTransactionId": "48837929983960560",
    "UniqueSchemeId": "260AAFCE",
    "PaymentScheme": "BACS",
    "ProcessingDate": "2024-11-30",
    "SchemeProcessingDate": "2024-11-29",
    "Reference": "REFERENCE",
    "SchemePaymentType": "Credit",
    "AccountServicerReference":"F5D9C19EC528475B88C0E142978E822B"
  }
}
```

### Example of the flow

<img src="/files/DxGktK6f1BlM7NGSYI0v" alt="Receive incoming Bacs Credit Notification" class="gitbook-drawing">

<table><thead><tr><th width="109">Step</th><th>Action</th><th>Description</th></tr></thead><tbody><tr><td>1.</td><td>Receive Payment Admission</td><td>LHV receives payment admission information from the Bacs scheme on <strong>day 2</strong> of the Bacs cycle. This step confirms that a payment is expected for settlement.</td></tr><tr><td>2.</td><td>Notification of Upcoming Payment</td><td>LHV sends a notification of the upcoming payment to the PSP on <strong>day 2</strong>, providing early visibility of the payment.</td></tr><tr><td>3.</td><td>Complete the Settlement</td><td>Settlement for the payment is completed by LHV on <strong>day 3</strong> of the Bacs cycle, following the Bacs scheme process.</td></tr><tr><td>4.</td><td>Credit-Debit Notification</td><td>LHV sends the credit-debit notification to the PSP on <strong>day 3</strong>, after the payment has been settled. More information about Credit-Debit information can be found <a href="/pages/HBt7DL80zOAE6HTVdKPi">here</a>.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lhv.com/home/connect/services/account-reports/transaction-notification/incoming-bacs-credit-notification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.