Advanced Search

Funds Administration Agent Interface Definition and Design Part 1 V24.0

Effective From Date:
Status:LIVE
Other versions
Download

complex image of process

Funds Administration Agent

Interface Definition and Design Part 1

Synopsis

This document contains details for interfaces which do not involve BSC Parties and their Agents.

Part 1 contains the definition and design of interfaces between the FAA Service Systems and other Systems.

Version

24.0

Effective date

08 April 2025

Prepared by

ELEXON Design Authority

Intellectual Property Rights, Copyright and Disclaimer

The copyright and other intellectual property rights in this document are vested in ELEXON or appear with the consent of the copyright owner. These materials are made available for you for the purposes of your participation in the electricity industry. If you have an interest in the electricity industry, you may view, download, copy, distribute, modify, transmit, publish, sell or create derivative works (in whatever format) from this document or in other cases use for personal academic or other non-commercial purposes. All copyright and other proprietary notices contained in the document must be retained on any copy you make.

All other rights of the copyright owner not expressly dealt with above are reserved.

No representation, warranty or guarantee is made that the information in this document is accurate or complete. While care is taken in the collection and provision of this information, ELEXON Limited shall not be liable for any errors, omissions, misstatements or mistakes in any information or damages resulting from the use of this information or action taken in reliance on it.

DOCUMENT CONTROL

Date

Version

Details of Change

Mods/ Panel/ Committee Refs

06 November 2008

20.0

Implementation of P214

Panel

23 February 2012

21.0

February 2012 Release, CP1352 (Document modified and rebadged)

ISG129/02

7 November 2013

22.0

November 2013 Release, CP1399

ISG149/04

07 November 2024

23.0

November 2024 Release, P415

P339/03

08 April 2025

24.0

April 2025 Release, P466

1 Introduction

1.1 Purpose

1.1.1 Summary

This document is Part 1 of the Interface Definition and Design deliverable that the service provider, EPFAL, is committed to deliver to the customer, the central CVA Programme.

The scope of the Interface Definition and Design document is, for the FAA service system, the definition and design of all interfaces between the FAA Service System and other Systems.

The scope of Part 1 is limited to the definition and design of interfaces between the FAA Service System and the BSC Parties and their Agents.

1.2 Scope

1.2.1 Status

This document replaces all previous drafts, taking into account the comments received on version 19 of this document.

This document is being prepared and approved in parallel time scales to the User Requirement Specifications (URS) for the EPFAL provided service. There is some overlap in the scope of these documents with regard to interface definition - note that for a common revision level where there is an identified difference then it is this document which prevails.

1.2.2 The Scope of the EPFAL Service Provision

EPFAL is contracted to provide the Funds Administration service defined as package 4 within the RETA Information To Tender document.

1.3 Change Forecast

This specification has been updated to reflect CVA Programme comments and is issued to be formally baselined.

This baseline specification will only be changed via formal change request processes.

1.4 References

1.4.1 ITT Documents

Service Description

Service Description for the Funds Administration Agent

Business Process Model

BSC Business Model

Schedule 3

Service Agreement Schedules: Other Services

Schedule 4

Service Agreement Schedules – Technical Requirements

Schedule 5

Service Agreement Schedules – Technical Standards, Quality Requirements and Health and Safety Requirements

1.4.2 Other Documents

FAA Interface and Definition and Design Part 2

Interface Definition for the FAA Service

FAA URS

User Requirements Specification for the FAA role

IDD Part 1

Interface Definition and Design, Part 1 – Interfaces with BSC Parties and their Agents

IDD Part 2

Interface Definition and Design, Part 2 – Interfaces to other Service Providers

SAA User Requirement Specification

Settlement Administration Agent User Requirement Specification

1.5 Volume Estimation Basis

The assumptions on which the ‘Volumes’ estimations have been based are detailed in the table below:

Assumption

Volumes

Number of BSC Parties

Low

Average

High

100

200

300

Number of BSC Debtors (50% of BSC Parties)

50

100

150

Number paying by Direct Debit (Based on current percentage)

30

60

90

Number of BSC Creditors (50% of BSC Parties)

50

100

150

2 Common Interface Conventions

Please refer to the Common Interface Conventions section in the NETA Interface Definition and Design Document Part 1.

3 Interfaces with BSC Parties and Agents

3.1 Outbound Interfaces

Agent-Id

Name

Dirn

User

Type

FAA-I002

Trading Charges Backing Sheet (Backing documentation)

To

Payment Party

Manual, Manual download via Elexon Portal

FAA-I004

Credit Cover Requirements

To

Payment Party

Manual, letter

FAA-I005

Credit Call Request

To

Payment Party

Manual, letter

FAA-I006

Payment Calendar (Agreed)

To

Payment Parties

Manual, data file (csv)

FAA-I007

Notice of Default

To

BSCCo

Manual, telephone by authorised personnel & confirmatory letter

FAA-I008

Payment Initiation Instructions

To

Clearing Banks

Manually initiated electronic transfer of files via FAA CHAPS & Business Master software

FAA-I009

Payment Instructions

To

Collection Account

Manual,

FAA-I010

Quarterly Statements

To

H.M. Customs & Excise

Manual, email

FAA-I010

Quarterly Statements

To

Payment Parties

Manual, email

FAA-I035

Reserve Account Interest Invoices

To

Payment Parties

Manual, email hardcopy by post

FAA-I038

Combined Advice Notes

To

Payment Party

Manual, Electronic transfer by Email

FAA-I039

Default Charges Backing Sheet (Backing documentation)

To

Payment Party

Manual download via Elexon Portal

FAA-I041

Ad-Hoc Charges backing sheet ( Backing documentation)

To

BSC Party

Manual download via Elexon Portal

3.2 Inbound Interfaces

Agent-Id

Name

Dirn

User

Type

FAA-I011

Completed Direct Debit Mandate

From

BSC Party

Manual, email

FAA-I012

Credit Limit

From

BSC Party

Manual, email letter

FAA-I013

Credit Cover Provision

From

BSC Party

Manual, Letter of Credit by registered post or courier, Cash via electronic bank transfer

FAA-I014

Bank Details

From

BSC Party

API

FAA-I015

Funds Accession Agreement & BSC Party Check List

From

BSC Party

Manual, email API

FAA-I016

Payment Confirmations

From

Collection Banks

Manual, telephone to authorised FAA personnel, confirmatory report from CHAPS software

FAA-I017

Non-receipt Notifications

From

Collection Banks

Manual, telephone to authorised FAA personnel

FAA-I036

Minimum Eligible Amount

From

BSC Party

Manual, e mail

3.3 FAA Outbound Interfaces

3.3.1 No longer used

3.3.2 Trading Charges Backing Sheets (Backing Documentation)

Interface ID:

FAA-I002

User:

BSC Party

BSCCo Ltd

Title:

Statements (Backing Documentation)

ITT reference:

FAA SD 10

FAA SD 9.1.1

RETA SCH 4

Mechanism:

Manual download via Elexon Portal

Frequency:

Daily

Volumes:

Low: 100 Statements dispatched per working day

Average: 200 Statements dispatched per working day

High: 300 Statements dispatched per working day

Interface Requirement:

Supporting information relating to the invoice, in particular details of previous settlement code amounts to enable verification of reconciliation calculations and interest calculations shown on the invoice.

Details will include:

  • Related Invoice

  • Payment Date

  • Calendar Payment Date

  • BSC Party ID

  • Totals showing:

  • Trading Charges Receivable (£)

  • Trading Charges Payable (£)

  • Total Trading Charges (£)

  • Reconciliation Interest Receivable ( £)

  • Reconciliation Interest Payable (£)

  • Total Reconciliation Interest (£)

  • Initial Settlement Run Details

  • Settlement Date

  • Settlement Code

  • Calendar Payment Date

  • Charge Type Description

  • Amount (£)

  • Total

  • Difference ( Trading Charges).This will always be the same as Total for Initial Settlement Run

  • Reconciliation Interest. This will always be zero for Initial Settlement Run

  • Reconciliation Run Details

  • Settlement Date

  • Previous Settlement Code

  • Previous Calendar Payment Date

  • Charge Type Description

  • Previous Amount (£)

  • Previous Total

  • Current Settlement Code

  • Current Calendar Payment Date

  • Charge Type

  • Current Amount (£)

  • Current Total

  • Difference (Trading Charges) (£)

Reconciliation Interest

3.3.3 No longer used

3.3.4 Credit Cover Requirements

Interface ID:

FAA-I004

User:

BSC Party

Title:

Credit Cover Requirements

ITT reference:

FAA SD 5.1.1

FAA SD 5.3

RETA SCH 4

Mechanism:

Manual - Letter

Frequency:

Ongoing as applicable

Volumes:

Low: 100 Notices of Security at Market start-up

Average: 200 Notices of Security at Market start-up

High: 300 Notices of Security at Market start-up

Interface Requirement:

Notice of security required from BSC Party in order to secure the agreed credit limit.

The security cover obligation may be discharged by one or more of the following methods:

  • Letter of Credit for a specified period

  • Cash

3.3.5 Credit Call Request

Interface ID:

FAA-I005

User:

BSC Party

Title:

Credit Call Request

ITT reference:

ECVAA SD: 5, A

ECVAA BPM: 3.3, 4.17

RETA SCH: 4, B, 3.3

FAA 5.3.3

Mechanism:

Manual - Letter

Frequency:

Ongoing as applicable

Volumes:

Not Known

Interface Requirement:

Request for additional collateral from a BSC Party who wishes to continue trading past the agreed credit limit.

Information sent will include:

  • BSC Party Name

  • BSC Party Identifier

  • Collateral required

  • Date required by

3.3.6 Payment Calendar (Agreed)

Interface ID:

FAA-I006

User:

BSCCo, Payment Parties’, SAA

Title:

Payment Calendar

(Agreed)

ITT reference:

FAA SD 4.3.2

RETA SCH 4

SAA SD: 2.8, A1

SAA BPM: 3.2, 4.27

Mechanism:

Manual

Data File (csv)

Frequency:

Annually

Volumes:

Payment Parties:

Low: 100 data files and hard copies sent per year

Average: 200 data files and hard copies sent per year

High: 300 data files and hard copies sent per year

1 data file and hard copy sent to the BSCCo and the SAA

Interface Requirement:

Agreed payment schedule detailing:

  • Settlement Date

  • Settlement code

  • Notification Date

  • Calendar Payment Date

  • Notification Period

  • Payment Period

3.3.7 Notice of Default

Interface ID:

FAA-I007

User:

BSCCo

Title:

Notice of default

ITT reference:

FAA SD 601

RETA SCH 4

Mechanism:

Manual

Telephone call by authorised FAA personnel and confirmatory letter

Frequency:

Ongoing as applicable

Volumes:

Not Known

Interface Requirement:

Notification of a credit default if the required Credit Cover has not been provided, or a payment default if the Credit Cover provided cannot cover an outstanding debt resulting from a non-payment.

Information will include:

  • Payment Party name

  • Payment Party Identifier

  • Nature of default (credit or payment)

  • Shortfall exposure

  • Calendar Payment Date of non-payment

  • Payment Date of Invoice

  • Invoice number

  • Invoice Date

  • Invoice number (if a payment default)

  • Action taken

3.3.8 Payment Initiation Instructions

Interface ID:

FAA-I008

User:

Clearing

Bank

Title:

Payment Initiation

Instructions

ITT reference:

FAA SD 11.1

FAA SD 11.4

RETA SCH 4

Mechanism:

Manually initiated electronic transfer of files via FAA CHAPS and Business Master Software

Frequency:

Daily

Volumes:

Direct Debit Instructions:

Low: 30 instructions to be sent each working day

Average: 60 instructions to be sent each working day

High: 90 instructions to be sent each working day

CHAPS/BACS Payments:

Low: 50 payments to be made per working day

Average: 100 payments to be made per working day

High: 150 payments to be made per working day

Interface Requirement:

Direct Debit instructions, CHAPS and BACS details:

Data will include:

  • Direct Debit Instructions

  • BSC Party Name

  • BSC Party Branch Sort Code

  • BSC Party Account Number

  • Payment Date

  • Amount Due

  • CHAPS Payments

  • BSC Party Name

  • BSC Party Branch Name

  • BSC Party Branch Address

  • Branch Sort Code

  • Account Number

  • Invoice Number

  • Net Amount Due to Party

  • BACS Payments

  • BSC Party Name

  • BSC Party Branch Name

  • BSC Party Branch Address

  • Branch Sort Code

  • Account Number

  • Invoice Number

  • Net Amount Due to Party

3.3.9 Payment Instructions

Interface ID:

FAA-I009

User:

Collection Account

Title:

Payment Instructions

ITT reference:

FAA SD 11.1

FAA SD 11.4

RETA SCH 4

Mechanism:

Manual with password security

Frequency:

Daily

Volumes:

Five reports (one per Collection Account) to be sent per working day

Interface Requirement:

Bank Advice Report containing details of funds due to be received on a Payment Date per Payment Party identifier into the Collection Account, and all amounts payable to the Payment Parties from the Clearing Bank.

Data in the Collection Account reports will include:

  • Payment Date

  • Collection Account name

  • Payment Party name

  • Payment Party bank branch name

  • Payment Party branch address

  • Branch sort code

  • Account number

  • Invoice number

  • Net amount payable

Data in the Clearing Bank reports will include:

  • Payment Date

  • Payment Party name

  • Payment Party branch name

  • Payment Party branch address

  • Branch sort code

  • Account number

  • Invoice number

  • Net amount receivable

3.3.10 Quarterly Statements

Interface ID:

FAA-I010

User:

H.M. Customs & Excise

BSC Parties

Title:

Quarterly Statements

ITT reference:

ECVAA SD: 5, A

ECVAA BPM: 3.3, 4.17

RETA SCH: 4, B, 3.3

FAA 5.3.3

Mechanism:

Manual

Frequency:

Quarterly and ad hoc as requested by H.M. Customs & Excise

Volumes:

BSC Parties:

Low: 100 Reports sent each quarter

Average: 200 Reports sent each quarter

High: 300 Reports sent each quarter

H.M. Customs & Excise:

Low: 1 report detailing 100 BSC Parties’ trade per quarter

Average: 1 report detailing 200 BSC Parties’ trade per quarter

High: 1 report detailing 300 BSC Parties’ trade per quarter

Interface Requirement:

Quarterly reports provided to H.M. Customs & Excise detailing the following for each BSC Party:

  • Settlement Period

  • BSC Party ID

  • BSC Party name

  • Settlement Date

  • Settlement code

  • Calendar Payment Date

  • Payment Date

  • Description

  • Invoice number

  • Amount excluding VAT

  • VAT amount

  • Interest amount

  • Income tax amount (only printed if non-zero)

  • Total paid or received

3.3.11 Reserve Account Interest Invoice

Interface ID:

FAA-I035

User:

BSC Party

Title:

Reserve Account Interest Invoices

ITT reference:

N/A

Mechanism:

Manual Hardcopy by post

Frequency:

Quarterly

Volumes:

Low: 100 Invoices dispatched quarterly

Average: 200 Invoices dispatched quarterly

High: 300 Invoices dispatched quarterly

Interface Requirement:

Document detailing amount of interest due to BSC Parties on a payment date.

Details will include:

  • Date of Issue

  • BSC Party Name

  • BSC Party Address

  • BSC Party facsimile Number

  • Invoice Number

  • Amount if Interest Due

3.3.12 Invoices

Interface ID:

FAA-I038

User:

Payment Party

BSCCo

Title:

Invoices

ITT reference:

N/A (Modification Proposal P214)

Mechanism:

Manual electronic transfer

Frequency:

Following threshold breach, or as manually triggered

Volumes:

Low: 1 Invoice per Payment Party per tax quarter

High: 300 Invoices dispatched per working day

Interface Requirement:

A uniquely identified invoice document containing data relating to a number of Trading Charges, Default charges, Ad-Hoc Charges, Reconciliation Interest and Late Payment Interest.

Header details will include the following:

  • Payment Party name

  • Payment Party address

  • Invoice number

  • Invoice Date

  • Payment Date

  • Party ID

  • Customer VAT Registration No

For each type of Charge, details for that charge will include the following:

  • Type

  • Description

  • Tax Code

  • Quantity

  • Net Charge (£)

The Invoice will also show

  • Total Net Charges (£)

  • VAT (£)

  • Total Charges including VAT (£)

  • VAT Breakdown

3.3.13 Default Charges Backing Sheet (Backing Documentation)

Interface ID:

FAA-I039

User:

Payment Party

BSCCo

Title:

Threshold Default Statement (Backing Documentation)

ITT reference:

Mechanism:

Manual download via Elexon Portal

Frequency:

Following threshold breach, or as manually triggered

Volumes:

Low: 1 Invoice per BSC Party per Tax Quarter

High: 300 Invoices dispatched per working day

Interface Requirement:

Supporting information relating to the Default Charges listed in the Invoice, in particular details of Default Share Amounts payable or receivable by a Payment Party with respect to multiple Payment Defaults.

These will be available to be manually downloaded via the Elexon Portal.

Header details will include the following:

  • Payment Party ID

  • Related Invoice

  • Payment Date

  • Default Charges Receivable (£)

  • Default Charges Payable (£)

  • Total Default Charges (£)

Report body details will include the following:

  • Details of Default:

    1. BSC Party ID

    2. Total Defaulted (Repaid) Amount £

    3. Affected Date

    4. Default Funding Share %

    5. Vatable Share (£)

    6. Non- Vatable Share (£)

    7. Interest Share (£)

    8. Total Amount Payable (Receivable)

    9. Amount in Default

3.3.14 No longer used

3.3.15 Ad-Hoc Charges Backing Sheet (Backing Documentation)

Interface ID:

FAA-I041

User:

Payment Party

BSCCo

Title:

Threshold Ad-Hoc Charges (Backing Documentation)

ITT reference:

New FAA

Mechanism:

Manual download via Elexon Portal

Frequency:

Following threshold breach, or as manually triggered

Volumes:

Low: 1 Invoice per BSC Party per Tax Quarter

High: 300 Invoices dispatched per working day

Interface Requirement:

Supporting information relating to the Ad-Hoc Charges listed in the Invoice

These will be available to be manually downloaded via the Elexon Portal.

Header details will include the following:

  • Payment Party ID

  • Related Invoice

  • Payment Date

  • Ad-Hoc Charges Receivable (£)

  • Ad-Hoc Charges Payable (£)

  • Total Ad-Hoc Charges (£)

Report body details will include the following:

  • Details of Ad-Hoc Charges

    1. Dispute Reference

    2. Counter Party

    3. Settlement Period

    4. Dispute Amount (£)

    5. Your Total (£)

3.4 FAA Inbound Interfaces

3.4.1 Completed Direct Debit Mandate

Interface ID:

FAA-I011

Source:

BSC Party

Title:

Completed Direct Debit Mandate

ITT reference:

Mechanism:

Manual

Frequency:

Ongoing as applicable

Volumes:

Low: 30 mandates to process at market start-up

Average: 60 mandates to process at market start-up

High: 90 mandates to process at market start-up

Interface Requirement:

Completed Direct Debit Mandate including the following:

  • Name of Account Holder

  • Branch Sort Code

  • Account Number

  • Bank Name and Address

  • Authorised Signature

If the BSC Party elects to pay by Direct Debit, the FAA initiates payment instructions to collect the amounts due. See outbound interface FAA-I008.

3.4.2 Credit Limit

Interface ID:

FAA-I012

Source:

BSC Party

Title:

Credit Limit

ITT reference:

FAA SD 5.2.1

Mechanism:

Manual

Letter

Frequency:

Ongoing as applicable

Volumes:

Low: 100 sets of values to process at market start-up

Average: 200 sets of values to process at market start-up

High: 300 sets of values to process at market start-up

Interface Requirement:

Data received will be the BSC Parties’ request for Desired Credit Limit.

Details received will include:

  • BSC Party Name

  • Credit Limit (MWh)

  • Effective Date

3.4.3 Credit Cover Provision

Interface ID:

FAA-I013

Source:

BSC Party

Title:

Credit Cover Provision

ITT reference:

FAA SD 5.3

FAA SD 5.4

RETA SCH 4

Mechanism:

Manual

Letter of Credit sent by registered post or courier

Funds will be received via electronic bank transfer

Frequency:

Ongoing as applicable

Volumes:

Low: 100 credit cover provisions to process at market start-up

Average: 200 credit cover provisions to process at market start-up

High: 300 credit cover provisions to process at market start-up

Interface Requirement:

Provision of security from BSC Party in order to secure the agreed credit limit.

Credit Cover may be in the form of :

  • Cash

  • Letter of Credit for a specified period

3.4.4 Bank Details

Interface ID:

FAA-I014

Source:

BSC Party

Title:

Bank Details

ITT reference:

FAA SD 8

FAA SD11.6

RETA SCH 4

Mechanism:

Manual

Letter or completed Funds Accession Agreement

Frequency:

Ongoing as applicable

Volumes:

Low: 100 sets of bank details to process at market start-up

Average: 200 sets of bank details to process at market start-up

High: 300 sets of bank details to process at market start-up

Interface Requirement:

Bank details required will include:

  • BSC Party Name

  • BSC Party Address

  • Elected Method of Payment

  • Bank Name

  • Bank Address

  • Branch Sort Code

  • Account Number

  • Bank Contact Details

  • Authorised Signature

3.4.5 Funds Accession Agreement and BSC Party Checklist

Interface ID:

FAA-I015

Source:

BSC Party

Title:

Funds Accession Agreement

ITT reference:

Mechanism:

Manual

Frequency:

BSC Party Registration & ongoing changes as applicable

Volumes:

Low: 100 Funds Accession Agreements to process at market start-up

Average: 200 Funds Accession Agreements to process at market start-up

High: 300 Funds Accession Agreements to process at market start-up

Interface Requirements:

BSC Party details will include:

  • Contact Details:

  • BSC Party Name

  • BSC Party Identifier

  • Contact Name

  • Address

  • Telephone Number

  • Contact Email Address (for general queries)

  • Delivery Email Address (for Invoices)

  • Registered Company Name

  • Company Number

  • Registered Address

  • VAT Country code and VAT Registration number (if applicable)

3.4.6 Payment Confirmations

Interface ID:

FAA-I016

Source:

Collection Banks

Title:

Payment Confirmations

ITT reference:

FAA SD 11.7

RETA SCH 4

Mechanism:

Manual

Telephone to authorised FAA personnel

Confirmatory reports produced from CHAPS terminal

Frequency:

Daily

Volumes:

5 confirmations received per working day

Interface Requirement:

Confirmation from Collection banks that all funds due for the payment date (as advised by the FAA in outbound interface ‘Payment Instructions’, FAA-I009) have been received and are available to be transferred to the Clearing account for distribution to creditors.

Information received will include:

  • Collection Bank Name

  • Payment Date

  • Total amount received

  • Confirmation that transfer to Clearing Account has been initiated

3.4.7 Non-receipt Notifications

Interface ID:

FAA-I017

Source:

Collection Banks

Title:

Non-receipt Notifications

ITT reference:

FAA SD 7

FAA SD11.2

RETA SCH 4

Mechanism:

Manual

Telephone to authorised FAA personnel

Frequency:

As applicable

Volumes:

Not Known

Interface Requirement:

Details of any non-payments or any variance in the payments received from the Bank Advice Report, (Outbound Interface Payment Instructions, FAA-I009).

Information received will include:

  • Collection Bank Name

  • Payment Date

  • BSC Party

  • Shortfall in funds received

  • Deadline for resolution

3.4.8 Minimum Eligible Amount

Interface ID:

FAA-I036

Source:

BSC Party

Title:

Minimum Eligible Amount

ITT reference:

FAA SD: 5.3.1

Mechanism:

Manual, fax, e mail

Frequency:

As per occurrence

Volumes:

Low

Interface Requirement:

Request from BSC Party to replace ECC value with Minimum Eligible Amount Value