SEPA CTO Payment Engine

The purpose of the SEPA Engine is to receive bulk or single-shot SEPA CT Out payment instructions,
store them, process them and produce output files for transfer to the mainframe (for on-us transactions)
or for SWIFT Alliance (for not-on-us transactions).

The SEPA Engine will also receive bulk SEPA DD Out instructions that it will import, validate and
make available for authorisation. Once authorised, DDO files are transferred for processing by GPPMP.

SEPA Engine Import Processes

1. SEPA CT Out
a. Import Pain001 – the ISO format for Customer-initiated bulk or single-shot credit transfer
instructions. These are consumed by the SEPA Engine and validated at the file or message
level.
b. STD18 – the legacy Standard 18 format for Customer-initiated bulk credit transfer
instructions. These are consumed by the SEPA Engine and validated at the file or message
level.
c. CVF – the Credit Validation File received from BOI’s SEPA agent, JPMC, providing
details on the processing outcome of an ICF file (see below) submitted by BOI. These are
consumed by the SEPA Engine. The status of the corresponding ICF file is updated and
any reversals specified by the CVF file are processed.
d. SCF - the Settled Credits File received from BOI’s SEPA agent, JPMC, providing details
on payment returns and payment status updates. On consumption by the SEPA Engine,
contents are verified, reversals (Pacs004) are processed and payment status updates
(Camt029) are stored.
2. SEPA DD Out.
a. Pain008 – the ISO format for Customer-initiated bulk or single-shot direct debit
instructions. These are consumed by the SEPA Engine and validated at the file or message
level.
b. Camt028 – these are issued bby Core Services to provide the PICN identifier gebnerated
by GPP. The PICN is applied by the SEPA Engine to the Pain008 payment and
transactions as received on the Pain008 file.
c. Bulk Credit Settlements – the file of credit settlements issued from Core Services
reporting bulk credits for DDO payments and the transactions to which they apply. These
are stored in the SEPA Engine Db for query purposes.
3. SEPA DD In.

At end-of-day, the file of Pacs003 messages that have been processed by the Direct Debit In (DDI)
solution are transferred to the SEPA Engine. Each file is consumed and the messages are stored in
the SEPA Engine Db for query purposes.

SEPA Engine Validate Process

On authorisation of a CTO bulk file, either through use of the SEPA Commercial Channel (SCC) or
automatically under STP rules, the Validate process retrieves the details associated with the file and
performs more detailed validation on Payment and Transaction information.

When Cut Over Control status (see below) is “Open”, the Validate process will submit valid Payments
to the Prepare process.

SEPA Engine Prepare Processes

The Prepare processes use Payment and Transaction information received on Pain001 and STD18 that
has been validated and prepares the data that will be copied to the relevant output files when the Export
processes are run.
1. Prepare SOD – this process is executed at a scheduled time as controlled by OPC on the
mainframe. Its purpose is to insert a new Cut Over Control record at “Open” status, retrieve
Payments that have previously been validated and are due to be processed today and submit them
to the Prepare process. Separate processes are executed for Payments that require Same Day and
Next Day settlement.
2. Prepare On Us Next Day – this process accepts a Pain001 Payment identifier and prepares
Bookkeeping posting data for all required mainframe postings and IBIS postings where a
beneficiary account is held on Bookkeeping or IBIS.
3. Prepare Not On Us – this process accepts a Pain001 Payment identifier and prepares Pacs008
messages for associated Transactions that specify a beneficiary in a bank other than Bank of
Ireland. For cross-border transactions, this process also submits a compliance check request to the
Compliance Engine. As compliance check responses are received, the Transaction is updated to
reflect Hit or No Hit. IBIS Postings are also prepared for the IBIS JPMC Nostro Account,
Compliance Suspense Account and other accounts.
4. Prepare on Us Same Day – this process accepts an identifier for a File Header record that has been
stored for CVF and SCF files. For Pacs004 messages that have been received cross-border, a
compliance check request is submitted to the Compliance Engine. As compliance check responses
are received, the Transaction is updated to reflect Hit or No Hit. Postings are generated to reflect
the rejection or return of Transactions and the SEPA Status of the relevant Pacs008 and Pain001
Transactions are updated.

SEPA Engine Export Processes

The Export processes use Posting and Pacs008 information that has been created by the Prepare
processes. Export processes are executed at pre-determined times as scheduled by OPC on the
mainframe.

1. Export ICF – this process creates an ICF (Input Credit File). A File Header record and Pacs008
Group Header record are created for the ICF file and all Pacs008 Transactions that, either, don’t
require a compliance check or have a compliance result of No Hit are retrieved. This data is used
to create the ICF file. On successful completion, SEPA Engine Db status values are updated to
signify completion for the records included. IBIS Postings associated with the ICF file are sent to
IBIS using MQ. The ICF file is subsequently copied by Connect:Direct to a location where it is
processed by SWIFT Alliance and transmitted to JPMC for onward processing and settlement.
2. Export BKK Next Day – this process inserts a Posting Header record and retrieves all Posting
records associated with the Bookkeeping system and are due for posting as part of the next day
cycle, i.e. transactions that have been received on Pain001 or STD18. This data is used to create
separate files for Credit Postings and Debit Postings. Some of the Postings are bulked as required.
On successful completion, SEPA Engine Db status values are updated to signify completion for the
records included. The BKK files are subsequently copied by Connect:Direct to the mainframe for
processing.
3. Export BKK Same Day – this process inserts a Posting Header record and retrieves all Posting
records associated with the Bookkeeping system and are due for posting as part of the same day
cycle, i.e. transactions that have been received on SCF and CVF files. This data is used to create
separate files for Bookkeeping postings. Some of the Postings are bulked as required. On
successful completion, SEPA Engine Db status values are updated to signify completion for the
records included. The BKK file is subsequently copied by Connect:Direct to the mainframe for
processing.
4. DDO Export – this process receives an authorise instruction identifying a Pain008 message that
has been imported to the SEPA Engine Db. It copies the original Pain008 file to a folder for
transfer to GPPMP. The file is subsequently copied by Connect:Direct to a folder for processing by
GPPMP.

DDI Export
SEPA Engine Cut-Over Processes
Cut-Over Control is used within the SEPA Engine Db to control when Payments can be submitted to
the Prepare process, thereby controlling when they can be exported to a BKK or ICF file for
posting/settlement.

1. On a scheduled basis, a Cut-Over Control record is inserted by Prepare SOD with status of “Open”
as described above.
2. On a scheduled basis as controlled by OPC on the mainframe, Cut-Over Control is updated from
“Open” to “CutOver” to indicate that the SEPA Engine has been placed in the cut-over window
and Validate will no longer submit Payments to the Prepare process. ICF will continue to operate
during Cut-Over.
3. On a scheduled basis as controlled by OPC on the mainframe, Cut-Over Control is updated from
“CutOver” to “Closed” to indicate that the SEPA Engine has been placed in a Closed state meaning
that Pain001, STD18 will continue to be imported and validated but not submitted to the Prepare
process. ICF Export will not operate when Cut-Over Control status is Closed.

SEPA Engine RESTful Services

The SEPA Engine provides a number of RESTful servies that are exposed over HTTPS and can be
invoked by processes that require data retrieved from within the SEPA Engine Db.

1. SEPAServiceCreditorSettlementDates. /sepa/settlementReportDates/*
2. SEPAServiceCreditorSettlementReport. /sepa/settlementReport/*
3. SEPAServiceFileList. /sepa/groupList/submitterId/*
4. SEPAServiceFileRejectionList. /sepa/groupRejections/*
5. SEPAServiceFileStatus. /sepa/report/group/*
6. SEPAServicePaymentList. /sepa/paymentList/*
7. SEPAServiceTransaction. /sepa/transaction/PICN/*

SEPA Engine Get Adaptors

SEPA Get Adaptors are message flows that consume a message from an MQ queue and update or insert
the data to the SEPA Engine Db, to ensure the local data remains up-to-date.

1. Get File Limits Update – this process receives updates to customer daily file limit details for
use by the SEPA import processes. This data originates from the mainframe EFT application.
2. Get Pacs002Update – this process receives Pacs002 messages for Bookkeeping postings that
have been rejected. The original Pain001 Transaction status is updated to Rejected. These
messages originate from the mainframe EQ application.

SEPA Engine Put Adaptors

SEPA Put Adaptors are message flows that provide data (business events) to the Semantic Hub, thereby
making it available to any BOI applications that require that information. Put Adaptors are developed
to provide data for which a demand has been established.

1. SEPAPutGroupHeaderUpdate – issues a message every time a GroupHeader record or its status is

updated.
2. SEPAPutPaymentUpdate – issues a message every time a Payment record or its status is updated.
3. SEPAPutTransactionUpdate – issues a message every time a Transaction record or its status is
updated.
4. SEPAPutFileHeaderUpdate – issues a message every time a FileHeader record or its status is
updated.
5. SEPAPutPostingHeaderUpdate – issues a message every time a PostingHeader record or its status
is updated.
6. SEPAPutPostingUpdate – issues a message every time a Posting record or its status is updated.
7. SEPAPutCutOverControlUpdate – issues a message every time a CutOvercontrol record or its
status is updated.