-**Core Banking System (CBS)** - Our internal system for managing fiat balances and transfers.
-**Bank of Lithuania (BoL)** - Bank providing us SEPA euro payment access via PAS system.
-**Sepa Connector (SC)** - System responsible for communication between CBS and Bank of Lithuania.
#### Notes
**Notification** - could be an email, admin panel notification (when implemented) or special message in log management panel (when implemented). Could also be a chat message on special channel, if we go that way. The way of delivering notification to the designated people is still under discussion.
#### Messages
-**Payment** - transfer of funds between accounts.
-**Return** - returns funds sent previously in transfer. Can be transfer rejection or response to a recall.
-**Recall** - request for transfer cancellation, can be accepted (with return) or rejected.
-**Recall rejection** - negative response to a cancellation request (recall) includes rejection reason.
-**Status update request** - if previous message (recall, inquiry) will not receive response within deadline, this is a reminder from the sender.
-**Claim non-receipt** - request to investigate transfer not reaching the recipient.
-**Claim for value date correction** - request to investigate transfer being processed too late.
-**Inquiry response** - response to Claim messages.
-**Pacs.002** - status update for other messages (e.g. transfer).
#### Scenarios
**1. Incoming message from Bank of Lithuania could not be processed by the Sepa Connector.**
Admin will receive notification from the Sepa Connector when one of the incoming messages will have an error, which makes it impossible to process and send to the Core Banking System.
**Note:** Incorrect message will never reach Core Banking System. Admin must resolve this manually.
**Deadline:** ASAP
---
**2. Outgoing message is technically incorrect according to the Bank of Lithuania or processing on Bank's side is impossible for other reasons.**
Admin will receive notification from the Sepa Connector when outgoing message will be rejected by the Bank of Lithuania for one of the following reasons:
- SYNRES (message syntax error)
- AUTHRES (invalid signature)
- CONRES (likely technical problem on the BoL's side)
Most of the time, this type of error would indicate a serious problem with either our certificates, infrastructure, network or software. Admin should investigate with developers immediately.
**Note:** Instructions in that scenario will still have status "Pending" in CBS as CBS is not notified about this category of errors. Admin should handle message status change on his end (e.g. resend transfers) after resolving aforementioned technical problems.
**Deadline:** ASAP
---
**3. Outgoing message is rejected.**
Core Banking System will notify admin when message is rejected by the Sepa Connector or by the Bank of Lithuania. Admin has to decide whether message should be completely rejected or retried and then take appropriate actions if necessary (e.g. contact the customer).
**Deadline:** None
---
**4. Incoming Transfer or Return have status Rejecting**
Admin will be notified by the Core Banking System that incoming message could not be processed. Depending on type of error Admin will have to decide if the return should be sent and which reason code should be used for rejection.
**Deadline:** 3 Banking Business Days from settlement date.
---
**5. Admin needs to investigate and respond: Incoming Cancellation request (recall)**
For incoming cancellation requests we need to either accept the request and send Return message or reject and send the Response message with rejection reason.
**Deadline:** 15 Banking Business Days from settlement date..
---
**6. Admin needs to investigate and respond: Incoming Inquiry (Claim Non-receipt)**
When user of some other bank (sender) sends a transfer to our client (recipient) and our client claims he did not receive it, sender can ask his bank to send to us the Inquiry asking to investigate. We need to respond by either confirming status of the transfer in our system.
**Deadline:** 10 Banking Business Days from settlement date..
---
**7. Admin needs to investigate and respond: Incoming Inquiry (Claim for value date correction)**
When user of some other bank (sender) sends a transfer to our client (recipient) and our client claims that transfer was settled on his account with a delay, he can ask sender for explanation. Sender can then ask his bank to investigate and they can send Inquiry request to us, asking to investigate and correct the transfer settlement date. We can respond by confirm date change, asking for a fee before we change, refuse the change.
**Deadline:** 10 Banking Business Days from settlement date.
---
**8. Admin needs to investigate: Incoming Status Update Request**
If we exceed the deadline for responding to a Recall or an Inquiry sender can send a Status Update Request to ask for explanation behind the delay. There is not banking message that carry the response to that in the SEPA system. Bank, which sent the request may expect update on investigation outside of the banking system (e.g. via email).
**Deadline:** None
---
**9. Admin can send: Request for outgoing transfer cancellation (recall)**
Admin has ability to request to cancel the transfer that was previously sent for for technical reason (e.g. duplicated transfer) or on customer's request (e.g. wrong IBAN).
**Deadline:** 10 days after transfer settlement date for cancellation because of technical reasons, 13 months for request on behalf of the customer.
---
**10. Admin can send: Inquiry message to investigate missing transfer on customer's request.**
When our user (sender) sends a transfer and the recipient claims, that he did not receive it, sender will ask his bank (us) to investigate. As part of investigation we can send an Inquiry request to the recipient's bank for them to check if they received the transfer and if it was processed successfully.
**Deadline:** 13 months after transfer has been settled
---
**11. Admin can send: Inquiry message to investigate invalid settlement date on customer's request.**
When our user (sender) sends a transfer and the recipient claims, that he receives the transfer too late, sender will ask his bank (us) to investigate. As part of investigation we can send an Inquiry request to the recipient's bank for them to check reasons behind the delay and to correct the settlement date if needed.
**Deadline:** 13 months after transfer has been settled
---
**12. Admin can send: Status update request to remind other bank about previous message, for which deadline for response has passed.**
If we send Recall or Inquiry messages and did not receive the response within the deadline for those messages, we can send Status Update Request to ask for explanation behind the delay in response.
**Deadline:** none
---
**13. Admin needs to investigate undelivered end-of-day messages.**
Sometimes Core Banking System may not receive End of Day reports from the Bank of Lithuania. In that case admin will have to either resolve the issue, so that the reports will reach CBS or validate transfer from that day manually and resolve the found issues.
**Deadline:** 3 banking business days (time to send return)
