Incoming Bacs Credit Notification
Description of Incoming Bacs Credit Notification service.
Last updated
Description of Incoming Bacs Credit Notification service.
Last updated
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.
| Field | M/O | Description |
|---|---|---|
| Step | Action | Description |
|---|---|---|
Payment.Beneficiary.AccountName
M
Name of beneficiary as given with account.
Payment.Beneficiary.AccountNumber
M
Beneficiary account number.
Payment.Beneficiary.AccountNumberCode
M
The type of identification given with beneficiary account number. Always BBAN.
Payment.Beneficiary.Bank.BankId
M
Beneficiary agent identification. Beneficiary sort code.
Payment.Beneficiary.Bank.BankIdCode
M
The type of identification given with beneficiary BankId. Always GBDSC.
Payment.Debtor.AccountName
M
Name of debtor as given with account.
Payment.Debtor.AccountNumber
M
Debtor account number.
Payment.Debtor.AccountNumberCode
M
The type of identification given with debtor account number. Always BBAN.
Payment.Debtor.Bank.BankId
M
Debtor agent identification.
Debtor sort code.
Payment.Debtor.Bank.BankIdCode
M
The type of identification given with debtor BankId. Always GBDSC.
Amount
M
Amount of money moved between the instructing agent and instructed agent. Format uses decimal point.
ClearingId
O
Bacs Service User Number (SUN) of the payment originator. Must be a numeric 6-digit value.
Currency
O
Currency of the transaction amount. Always GBP.
NumericReference
O
Numeric reference field.
SchemeTransactionId
M
Transaction ID.
UniqueSchemeId
M
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.
PaymentScheme
M
Always BACS.
ProcessingDate
M
Day 3 of the Bacs cycle. The day on which settlement occurs.
SchemeProcessingDate
M
Day 2 of the Bacs cycle. The day on which the notification of an upcoming payment is received.
Reference
M
Payment reference.
SchemePaymentType
M
Always Credit.
1.
Receive Payment Admission
LHV receives payment admission information from the Bacs scheme on day 2 of the Bacs cycle. This step confirms that a payment is expected for settlement.
2.
Notification of Upcoming Payment
LHV sends a notification of the upcoming payment to the PSP on day 2, providing early visibility of the payment.
3.
Complete the Settlement
Settlement for the payment is completed by LHV on day 3 of the Bacs cycle, following the Bacs scheme process.
4.
Credit-Debit Notification
LHV sends the credit-debit notification to the PSP on day 3, after the payment has been settled. More information about Credit-Debit information can be found here.
