Government Banking Service (GBS) require a Financial Transaction Reporting (FTR) solution that can report intraday position data using transactional data which is used to supply HM Treasury with key financial information, allowing them to effectively deliver government cash management objectives. GBS require a solution that can capture and consolidate data for multiple entities (i.e. The Government Departments bank accounts) and return the information in a format acceptable to GBS and HMT. The solution must be banking industry standard, scalable, flexible, easy to maintain and must have the ability to debt and credit customers’ accounts using various file uploads. Additionally, it must have the ability to ‘zero’ customer accounts, GBS currently utilises a SWIFT bureau and continues to require this method of connecting to the banks.

The current application has been modified to allow GBS to create the required reports, however the intention is, where possible, to move to a more standardised solution.

The current system produces the following:

— 6 intraday transactional based swing reports (utilising intraday transactional data),

— 1 next day swing report (utilising next day reports of bacs debits and credits supplied by the banks plus bacs grade 3),

— 2 cash management files (utilising end of day transactional data to allow actual v forecast comparison),

— end of month balances of all sterling accounts (utilising end of day statements cleared balance information),

— 2 overdrawn reports (utilising end of day statements balance information),

— 2 reconciliation reports Sterling and Euro pools (utilising end of day statements balance information),

— the creation of journal payment files specific to each electronic banking system from Bank of England files (i.e. Bacs Grade 3),

— the creation of journal payment files specific to each electronic banking system from HM Treasury files (i.e. Vote Funding, HMT Interest).

The key output requirements are summarised below:

— the production of 6 intraday banking activity reports on an agreed schedule and one next day report for HMT using data received from supplier banks,

— creation of one cash management files for HMT (to enable them to compare actual movements with those forecast by the Government Departments),

— creation of journal (internal transfers) files specific to each electronic banking system from Bank of England files (i.e. bacs grade 3),

— creation of journal (internal transfers) files specific to each electronic banking system from HM Treasury files (i.e. Vote Funding, HMT Interest),

— ability to recreate historical reports of specific files (i.e. cash management files),

— zeroing customers’ and government banking accounts,

— reporting monthly balances of all Government Banking accounts for HMT using an agreed structure,

— overdraft monitoring (intra and end of day),

— Volumes and values of government banking customers,

— audit reports,

— reconciliation reports (Euro and Sterling pool’s),

— ability to create ad-hoc reports,

— management information reports,

— file/feed monitoring alerts (missing files from data feeds etc.) can be visual or e-mail based.

Full details of the requirements are included in the specification document attached to the eSourcing event, however the minimum requirements for bidders wishing to provide an initial tender are:

— the key output requirements listed above,

— the functional requirements,

— HMT interest (passing of HMT interest to Governemtn Department accounts),

— HMT Vote (passing of HMT Voted money to Government Departments accounts),

— miscellaneous transfer (internal transfers),

— intraday swing reports,

— next day swing reports,

— cash management daily file,

— cash management monthly file,

— end of month balance report and reconciliation,

— GBS functional requirements,

— GBS functionality,

— daily sterling reconciliation,

— daily Euro reconciliation,

— additional security functions (in addition to the security section).