FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
Document Title: NETWORK BANKING END TO END RECONCILIATION
REPORTING
Document Type: Reconciliation Report Specification (ATS)
Release: N/A
Abstract: This document specifies the reconciliation report output to satisfy
the end to end reconciliation of the Network Banking Stream
Document Status: APPROVED (delete appropriate status)
Originator & Dept: Richard Brunskill: Fujitsu Services Pathway Management Support
Contributors: Richard Hicks: Fujitsu Services Pathway, Linda Austin: POL
Internal Distribution: Fujitsu Services Pathway: Richard Hicks; Roger Donato; John
Pope; Pete Chandler; Dave Johns; Michael King; Angela Shaw;
Kevin Barrett; Pushparatnam Arasaratna; Harji Hothi; Mark
Taylor; Tony Drahota; Mik Peach; Anne Chambers.
External Distribution: POL: Linda Austin; Bob Booth; Peter Jones; Sue Harding; Glenys
Latham; Clive Reed; Steve Grayston; Claire Bennett; Jayne
Widdowson; Danny Bathmaker; Marion Dale; Tom Basquille.
Approval Authorities: (See PA/PRO/010 for Approval roles)
ame Position Signature Date
Bill Reynolds [Fujitsu Services Pathway
(Tony Drahota [Fujitsu Services Pathwa:
[ASD Manager
‘Sue Harding IPON / BDA
Clive Reed IPON / TDA
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: I of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
0.0 Document Control
0.1 Document History
\Version No. Date [Reason for Issue IAssociated
(CP/PinICL
0.1 16/06/01 First draft for review
(0.2 20/06/01 Second draft for review following POL discussio:
orkshop and other comments from reviewers.
0.3 2/08/01 [Third draft for review following POL discussion]
orkshop and other comments from reviewers.
0.4 27/09/01 [Fourth draft for review following POL discussion]
orkshop and other comments from reviewers.
0.5 3/12/01 Fifth draft for review following POL discussio:
\workshop and other comments from reviewers.
1.0 19/12/01 IREMOVED FROM APPROVAL CYCLE
Ll 8/01/02 IREMOVED FROM REVIEW CYCLE
2.0 16/01/02 IREMOVED FROM APPROVAL CYCLE
2.1 22/01/02 Sixth draft for review following amendmentsCR27
incorporated as a result of IBM interface changes}
land late POL comments received against Versio:
1.0 (now removed)
2.2 27/02/02 Seventh draft for review following amendments asI
la result of two workshops between Fujitsul
Services Pathway and POL on 6&7 February, andI
20/21 February 2002 and informal comments}
received from Fujitsu Services Pathway.
13.0 21/03/02 Eighth draft for approval following revie'
comments
3.1 12/07/02 Draft for review following:
le Correction of typos
le Inclusion of 3 definitions outstanding from]
V3.0
4.0 29/07/02 Final Version for approval
IPO comments: Marion Dale added to reviewers
Fujitsu Services comments:
le Tony Drahota to approval authority
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 2 of 1
Fujitsu Services NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
FUJ00001740
FUJ00001740
Ref: CS/SPE/O11
Version: 5.0
Date: 29/12/02
le Change of date format within ‘Receipt Time’
on NB102 sections from hhmmss to hh:mm:ss
(cosmetic change to
requiring review)
le ICL replaced with Fujitsu Services throughout
report only — not
Ichanges
4.1 1/11/02 Draft for review ICP 3348
(Changes are highlighted.
5.0 9/12/02 (Comments responded to with out the need for am
0.2 Review Details
[Review Comments by : 22/11/02
Review Comments to: ohn Moran, Richard Hicks
Mandatory Review Authority
Name
See Review Role Matrix in PA/PRO/010
Fujitsu Services Pathway
Bill Reynolds
[Fujitsu Services Pathway ASD Manager [Tony Drahota
IPOL / BDA Sue Harding
POL / TDA Clive Reed
POL Bob Booth*
POL arion Dale
Fujitsu Services Pathway john Pope
Optional Review / Issued for Information
Fujitsu Services Pathway TDA
[Roger Donato*
Fujitsu Services Pathway
[Pushparatnam Arasaratna for K Barrett*
Fujitsu Services Pathway CS
ik Peach*
Fujitsu Services Pathway CS
(Anne Chambers*
( * ) = Reviewers that returned comments
0.3. Associated Documents
Reference \Version (Date
(Title
Source
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE
Page: 3 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
IPA/TEM/001 7.0 2" April 2002 {Fujitsu Services Document IPVCS
(Template
[B/SPE/002 etwork Banking DRS On-lineFujitsu Service:
Workstation Specification Pathway PVCS
B/IFS/008 etwork Banking Engine NBEFujitsu Services
+ Horizon Application InterfacePathway PVCS
Specification
B/PRO/002 etwork Banking ReconciliationFujitsu Service
\& Incident Management Pathway PVCS
Unless a specific version is referred to above, reference should be made to the current
approved versions of the documents.
0.4 Abbreviations/Definitions
[Abbreviation Definition
\Authorised ClientThis signifies projected settlement awaiting the Confirmed Clien
(Transaction AwaitingTransaction. From a system perspective, an ‘S’ transaction — No
‘Confirmation ipplicable to Network Banking Reports.
[Bank_Transaction_Id lessage sequence number assigned by the message originator
except Horizon), to assist in identifying a transaction uniquely,
Stays unchanged through the life of the transaction.
C4 Processing Date [The System Processing Date on which the ‘C4’ was received by the
IDRS. Where a C4 is included on report NB101, the C4 Processing
[Date is the same as the Run Date for report NB101.
(C4 Settlement Date [The Settlement Date provided on the C4 transaction.
(Confirmed ClientFrom a ‘Client’ perspective, a transaction that has been authorised to}
(Transaction either debit or credit an account. From a system perspective, a ‘C4’
transaction.
(Counter Confirmations [From an outlet / POL perspective, a successfully completed
transaction at the counter. From a system perspective, a ‘C12’
Itransaction.
IExceptioned ClientFrom a Client perspective, a transaction reconciliation difference;
(Transaction highlighted within the NBE and notified to Horizon. From a system]
perspective, a ‘D’ transaction.
[Exception Types IWithin all reports the ‘Exceptions’ category will include:
le ‘Incomplete States’, i.e. those transactions where one or more
transaction component is missing — a C4 without a C12 ete
le Genuine exceptions where transaction components belonging to
the same high level transaction have been exceptioned, i.e. C12
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 4 of 1
Fujitsu Services
FUJ00001740
FUJ00001740
NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
le (amount) not = to C4 (amount) etc.
le NBE/ DRS corruption’s
[Horizon_Txn_Num
[Unique transaction number to be used in all messages betwee
[Horizon and the NBE relating to the transaction. Generated b
[Horizon and provided in the request message initiating the;
itransaction.
‘New’ Transactions
[Transactions that have had a change of state since they were last
reported, or have never been reported except in NB102 section 6]
ote that if a transaction appears in NB102 section 6 it is future
\dated as is reported in that section for information only. Once future
\dated transactions become current dated, they must be reported as
jthough they have not appeared on the reports before.
‘Old’ Transactions
[Transactions that have NOT had a change of state since they were
last reported.
[Receipt Date
[Receipt Date is the Date as printed on the transaction Receipt at the;
(Counter. It forms part of all transactions.
[Receipt Time
[Receipt Time is the Time as printed on the transaction Receipt at the
(Counter. It forms part of all transactions.
Reconciliation Date
[The Reconciliation Date is the date attributed to a transaction to)
low POL to reconcile. It will be set the first available Bank!
Settlement date from the transaction elements (C112, C12, C4, S &
ID) that make up a Network Banking transaction. If no Ban
Settlement date is available, the Reconciliation Date will be set to the
processing date that the Data Reconciliation Service first recorded
lany element of the transaction being received. If a Settlement date}
subsequently becomes available, the first available Bank Settlement
\date will replace the processing date. However, once a transaction)
lhas been accounted for on the reconciliation reports, the
[Reconciliation Date will never change.
Routing Gateway
Identifies a system, where the authorisation for a specific transactionI
should be sought. For Network Banking, this refers to the
[Routing Gateway as defined in Network Banking Engine NBE +
[Horizon Application Interface Specification (NB/IFS/008)
[Run Date
[This is the System Processing Date for which the report refers, i.e!
ll transaction components processed by the DRS on System)
Processing Date dd/mm/yyyy are accounted for on this report.
Settlement Date
Settlement Date is often the same as Run Date but some Financia
Institutions may assign a Settlement Date in the future: e.g. the
following Monday may be set on transactions processed on the
ipreceding Friday, Saturday and Sunday.
(TIP Transactions
[From an outlet / POL perspective, a transaction that has been sent
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE Page: 5 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
from TPS to POL TIP. From a system perspective, a “C1127
itransaction.
(CAP (Cash Account Period
(CBDB (Counters Business Data Base (POL)
ICS (Customer Service (Fujitsu Services Pathway)
IDRS [Data Reconciliation Service
IEFTPOS [Electronic Funds Transfer at Point Of Sale
IEPOSS Electronic Point Of Sale Service
SU Management Support Unit (Fujitsu Services Pathway)
POL Post Office Limited
(TIP \Transaction Information Processing (POL)
TPS [Transaction Processing Service
0.5 Changes in this Version
\Version ‘Changes
5.0 (0 changes from reviewed document version 4.1.
[Document for approval
0.6 Changes Expected
(Changes
jo further change expected
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 6 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/011
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
0.7 Table of Contents
1.0 INTRODUCTION 11
2.0 SCOPE 11
2.1 RECONCILIATION REPORTS SPECIFIED. 12
3.0 GENERAL REPORT SPECIFICATIONS 13
3.1 NBO00: SUMMARY REPORT. 15
3.1.1 NB000: Rules...
3.1.1.1 NBOOO: Report Layout.
3.1.1.2 NB000: Data Definitio
3.2 NBIOL:
3.2.1 NBIOI: Rules
3.2.1.1 NBIOL: Repor
3.2.1.2 NBIOI: Data Definition.........
3.3. NB102: EXCEPTION SUMMARY.
3 NB102: Rules
NB102: Section 1: All Uncleared Confirmed, Unconfirmed & TIP exception:
NBIO2: Section 2: Uncleared Exceptioned Client Transactions.
NB102: Section 3: Uncleared Corruption’s..
NB102: Section 4: Uncleared Timing Difference: vo
NBI02: Section 5: Uncleared Confirmed, Unconfirmed & TIP exceptions >24 hours
NB102: Section 6: Uncleared Future Dated Transactions by Client. .
NBIO2: Section 7: All Cleared Confirmed, Unconfirmed & TIP exceptions 32
NBI02: Section 8: Cleared Exceptioned Client Transactions.
NBI02: Section 9: Cleared Corruption’s........:00 .
NB102: Section 10: Cleared Timing Differences
NB102: Scetion 11: Cleared Confirmed, Unconfirmed & TIP ex: tons > 24 hours
NB102: Section 12: Cleared Future Dated Transactions by Client...
Incomplete and Discrepancy State: Report Matrix.
Exception State: Report Matrix.
3.4 NB1O3: SETTLED TRANSACTION / CASH AC ‘OUNT RECONCILIATION STATEMENT
3.4.1 NBI1O3: Rules...
3.4.1.1 NBI1O3: Report Layout.
3.4.1.2 NB103: Data Definition 47
SYSTEM STATES 48
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 7 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
1.0 Introduction
This document has been compiled to specify all Fujitsu Services Pathway outputs from
the Data Reconciliation Service (DRS) to enable a generic end to end reconciliation of
Network Banking transaction processing.
2.0 Scope
This document defines the format and content of all reconciliation reports, which
satisfy the Network Banking reconciliation requirement. It does not attempt to define
within the operating systems, including the Network Banking Engine, (NBE) how the
transactions are processed.
The following Network Banking requirements are satisfied by this document:
© Reconciliation: [NBR0040], [NBR0042], [NBR0183], [NBR0212], [NBR0227],
[NBR0229], [NBR0278], [NBR0294], [NBR0389].
Settlement: [NBR0230], [NBR0456].
e Error Resolution: [NBR0260]
It is assumed that each of the POL clients, as dictated by Routing_Gateway (assumed
to be at this point the Banks / LINK) will require a separate reconciliation report set.
Within this report set, separate reports will be provided as per the following table:
Report Number Deposit Transactions [Withdrawal Transactions
B101 Combined Report
B102 Combined Report
INB103 Y l Y
NBO000 is a combined report for all Routing Gateways.
The format and content of each client’s report is considered to be identical when
allowing for these specific requirements. It should therefore be understood that the
specifications documented here are applicable to each client report set. (Specific client
requirements outside of this reporting specification are not covered within this
document)
There must be a separate set of reports to provide for transactions for which the
Routing Gateway and/or Transaction Type is not known.
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 8 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
Balance Enquiries and PIN changes are explicitly excluded from the report set as ‘Not
Required by POL’
No report will mix currency, so if ever the transactions selected to appear on a set of
reports are not of a single currency, then a separate set of reports will be produced for
each currency. All the amounts in a single transaction will always use the same
currency
2.1. Reconciliation Reports Specified
NBO00: DRS Summary
NB101: Network Banking Settlement Statement
NB102: — Exception Summary
NB103: Settled Transaction / Cash Account Reconciliation Statement
ececee
Rows and columns are described in detail, together with the mathematical calculations
required to achieve reconciliation.
All general aspects relating to the production and transmission of the reports are
described.
This document does not attempt to define the business processes undertaken within
Fujitsu Services Pathway and POL with respect to the resolution of any exceptions,
which may arise, nor does it scope the requirement for any systems that may be
required to assist in this process. This information can be found in the associated
documents, reference:
e¢ NB/SPE/002: Network Banking DRS On-line Workstation Specification
¢ NB/PRO/002: Network Banking Reconciliation & Incident Management
NB: It should be noted that where a system ‘State’ definition is quoted, this takes
precedence over any narrative which has only been provided to help understand the
business processes.
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 9 of I
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.0 General Report Specifications
A separate set of reports is produced for each POL client as identified by the
Routing_Gateway. (LINK being a single client). The specification is general to all
reports sets.
1. For volumes and values the accounting sense for reporting purposes to allow
settlement totals to be correctly derived, will be:
Absolute volume
Net value
Where no value reported show “0.00”
Where no volume reported show 0
-ve values will be shown in brackets e.g. (nnn.nn)
2. Each report will show the following general information:
Report title — including the client name (derived from Routing_Gateway.)
Transaction Type — (if applicable)
Report ‘Run Date’ - i.e., the period for which the report refers
Production date and time
Fujitsu Services Pathway report number
Fujitsu Services Pathway reference
3. Where ‘Received’ and ‘Reconciliation Date’ are quoted against time parameters:
e ‘Received = New’: defines transactions that have had a change of state since
they were last reported, or have never been reported, except in NB102 section
6
¢ ‘Received = Old’: defines transactions that have NOT had a change of state
since they were last reported
4. Reports: NBO00, NB101, NB102 will be produced DAILY, NB103 will be
produced WEEKLY after Friday’s and prior to Saturdays TPS processing
schedule. They will be delivered by 08.00hrs the day following the Run Date to:
e¢ POL/ TIP gateway: The Host writes the reports to a directory. These are
picked up by FTMS and posted to the TIP gateway. (As per other Host to
external systems applications)
e Fujitsu Services Pathway CS / MSU, DRS Workstation.
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 10 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
5. Within report NB 102 the ‘Exceptions’ category will include:
e ‘Incomplete States’, i.e. those transactions where one or more transaction
component is missing — a C4 without a C12 ete
¢ Genuine exceptions where transaction components belonging to the same high
level transaction have been exceptioned, i.e. C12 (amount) not = to C4
(amount) etc.
e NBE/ DRS corruption’s
6. For clarity within this document, field sizes are shown within “Report Layout’ and
not within the ‘Data Definition’
7. All reports are run against a consistent data set.
8. All reports will be produced as ASCII text files — one for each report. The report
layout will be fixed format with space characters providing the blank space. This
will allow for ‘Excel’ input, using fixed field width facilities. The formatting (lines
& shading referred to in this document) will not be included within the file. Every
line will have the character ‘newline’, Hex '0A', as the last character. Each report
will have the text “End of Report” as the last line.
9. See also comments in Section 2: ‘Scope’
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 11 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.1. NB000: Summary Report
This report summarises all reconciliation reports produced by the DRS. It also
summarises all reports that were not produced by the DRS because there was no data
to report.
3.1.1 NBO00: Rules
1. Reports are listed by application type, routing gateway, and report number.
2. Where a report is produced, the filename will be shown.
3. Where for a routing gateway, there is some data to report, but for a specific report there is
no data, then the filename will be replaced by [NO DATA].
4. Where for a routing gateway there is no data at all, the application type cannot be shown
and the file name will be replaced by [NIL RETURN].
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 12 of 1
Fujitsu Services
NETWORK BANKING END TO EN!
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date: 29/12/02
3.1.1.1
NB000: Re
NBOOO: DRS Summary Report
port Layout
‘Tient: All
[Run Date: dd/mm/yyyy
Produced on: ddimnv/yyyy at hh:hh:ss
[Transaction Type: All
Application [Routing Gateway JRouting Gateway Name [Report IReport Filename
Type ‘umber Number _ [Section
[APP 9999999999 B0 character name INB999___b9 appyyyymmddggegegeoeeNBnnnsstttcur. PXT
End of Report
© 2002 Fujitsu Services
FUJ00001740
FUJ00001740
COMMERCIAL IN CONFIDENCE
Page: 13 of 1
Fujitsu Services
COMMERCIAL IN CONFIDENCE
NETWORK BANKING END TO EN!
RECONCILIATION REPORTIN
Ref:
CS/SPE/011
Version: 5.0
Date: 29/12/02
3.1.1.2
NBO000: Data Definition
NBOO0: DRS Summary Report
“Tient: All
[Produced on: (Date / Time of report production)
[Run Date: (The period for which the report refers)
[Transaction Type: All
ill be “-* where
hno application type
s known,
feach routing gateway
ithin application type
reports NB102 sections 6 INB102 sections 6 and 12 as there _fnumber for Isection for
hand 12 as there are single hare single reports for all routing ach routingleach report
ports forall routing gateways. Shown againsteach —_feateway —_faumber
leateways. Repeated for routing gateway number
[Application [Routing Gateway Routing Gateway Name [Report Report Filename
[Type jumber Number _ [Section
pplication Type [Routing Gateway [Routing Gateway name. Will be Shows each Shows each [Where there is data for a report the filename will be shown:
e.g. NBS or DCP). number. Will be“ for HALL CLIENTS for reports report report
appyyyymmddgggggeeeeeNBnnnssttteur. TXT, where
Vhere for a routing gateway, there is some data to report, but for a
specific report there is no data, then show [NO DATA]. Where forI
routing gateway there is no data at all (the application type is
show [NIL RETURN].
app is a 3 character application code (e.g. NBS or DCP)
yyyymmdd is the report run date
geegegegee is the routing gateway number. For report
‘NBI102 Sections 6 and 12 use ‘O000000ALL”
NBnnnss is the report number and section
ttt is the transaction group. For NB101, and NB102, this will
be ‘ALL’, for NB103, it will be ‘DEP? for deposits, or
“WDR’ for withdrawal
cur is the currency e.g. GBP
FUJ00001740
FUJ00001740
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 14 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.2 NB101: Network Banking Settlement Statement
This report identifies ‘C4’ transactions received against each ‘C4 Settlement Date’ as
reported to the DRS for the most recent processing date. The report will be used by
POL as a basis for settlement of Network Banking transactions with the Financial
Institutions.
3.2.1 NB101: Rules
1. NBI1O1 is run daily
2. NB1O1 is repeated for each Routing_Gateway
3. NB1O1 will show ‘C4’ transactions received from the NBE for ONE day only —
breaking these down into individual ‘C4 Settlement Dates’ There will be one line
for each ‘C4 Settlement Date’
4. NBI1OI will show Deposit and Withdrawal transactions in separate columns,
(headed ‘Receipts’ and ‘Payments’ respectively) derived from ‘Txn_Type’
5. NB101 will show a final settlement column derived in the following way:
¢ Volume: Volume of Deposits plus Volume of Withdrawals
e Value: Value of Deposits minus Value of Withdrawals
¢ Where the net total is negative i.e. the Value of Withdrawals exceeds the Value
of Deposits, the total will be shown as (xxx.xx)
6. Where the volume for a given ‘C4 Settlement Date’ is nil, the date will not be
reported.
7. ‘C4 Settlement Dates’ are shown in reverse chronological order.
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 15 of 1
Fujitsu Services
NETWORK BANKING END TO EN!
RECONCILIATION REPORTING
Ref: CS/SPE/011
Version: 5.0
COMMERCIAL IN CONFIDENCE
Date: 29/12/02
3.2.1.1 NB101: Report Layout
INB 101: Network Banking Settlement Statement
Client: Barclays ete
Produced on: dd/mm/yyyy at hh:mm:ss
[Run Date: dd/mm/yyyy
[Transaction Type: Deposit & Withdrawal
\Currency: GBP
FUJ00001740
FUJ00001740
Receipts Payments Net Settlement
C4 Settlement Date Volume Value Volume Value Volume Value
1. dd/mm/yyyy 99,999,999) 9,999,999,999.9' 99,999,999) 9,999,999,999.9' 99,999.99 9,999,999,999.99}
2. dd/mm/yyyy 99,999,999) 9,999,999,999.99 99,999,999) 9,999,999,999.99) 99,999,999 9,999,999,999.99}
3. dd/mm/yyyy 99,999,999) 9,999,999,999.9' 99,999,999) 9,999,999,999.9' 99,999,99 9,999,999,999.99}
4. dd/mm/yyyy 99,999,999] 9,999,999,999.99 99,999,999) 9,999,999,999.99 99,999,999 9,999,999,999.99}
{TOTAL 999,999,99 9,999,999,999.9! 999,999,999) 9,999,999,999.9' 999,999,99: 9,999,999,999,9:
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 16 of 1
Fujitsu Services
NETWORK BANKING END TO EN!
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date:
29/12/02
3.2.1.2 NB101: Data Definition
INB 101: Network Banking Settlement Statement
(Client: (Derived from ‘Routing_Gateway’)
Produced on: (Date / Time of report production)
IRun Date: (The period for which the report refers)
[Transaction Type: Deposit & Withdrawal
\Currency: (Derived from ‘currency’)
Receipts Payments Net Settlement
C4 Settlement Date Volume Value Volume Value Volume Value
1. Date 1 lo. of C4 DepositsValue of C4 DepositsNo. of C4 WithdrawalsValue of C4INo. of C4 DepositsValue of C4 Deposit
Rec'd Rec'd Rec'd \Withdrawals Rec’d Rec'd + No of C4Rec’d — Value of C4}
ithdrawals Rec’d ithdrawals Ree’d
2. Date 2 lo. of C4 DepositsValue of C4 DepositsNo. of C4 WithdrawalsValue of C4INo. of C4 DepositsValue of C4 Deposit
Rec'd IRee’d Rec'd Withdrawals Ree’d Rec'd + No of C4Rec’d — Value of C4}
(Withdrawals Rec’d Withdrawals Rec'd
3. Date 3 INo. of C4 Deposits\Value of C4 DepositsNo. of C4 Withdrawals\Value of C4INo. of C4 DepositsValue of C4 Deposit
Rec'd Rec'd Rec'd Withdrawals Ree’d Rec'd + No of C4Rec’d — Value of C4}
Withdrawals Rec'd Withdrawals Rec’d
4. Date 4 lo. of C4 DepositsValue of C4 DepositsNo. of C4 Withdrawals\Value of C4INo. of C4 Deposits\Value of C4 Deposit
Rec'd Rec'd Rec'd (Withdrawals Rec'd Rec'd + No of C4Rec’d — Value of C4}
Withdrawals Ree’d Withdrawals Rec’d
[TOTAL ITotal All Lines {Total All Lines (Total All Lines (Total All Lines {Total All Lines (Total All Lines
End of Report
FUJ00001740
FUJ00001740
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 17 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.3
3.3.1
NB102: Exception Summary
This report is divided into twelve sections:
Section 1: All Uncleared Confirmed, Unconfirmed & TIP exceptions
Section 2: Uncleared Exceptioned Client Transactions
Section 3: Uncleared corruption’s.
Section 4: Uncleared Timing Differences
Section 5: Uncleared Confirmed, Unconfirmed & TIP exceptions >24 hours
Section 6: Uncleared Future Dated Transactions by Client
Section 7: All Cleared Confirmed, Unconfirmed & TIP exceptions
Section 8: Cleared Exceptioned Client Transactions
Section 9: Cleared corruption’s
Section 10: Cleared Timing Differences
Section 11: Cleared Confirmed, Unconfirmed & TIP exceptions >24 hours
Section 12: Cleared Future Dated Transactions by Client
eooerererer eee eee
Liability issues are not covered within this document, nor are the business
processes involved in the resolution of any exception.
NB102: Rules
1. NB102 is run daily
2. NB102 is repeated for each Routing Gateway.
3. For each report section, the column ‘Values’ will be partitioned into 8 sub columns
to contain the values for: ‘C12’, ‘S’, ‘C4’, ‘C112’ & the four values from a ‘D’
which are: Amount Requested, Amount Authorised, Amount Confirmed, Amount
Discrepancy. The reports will populate all values that are available.
4. For reporting purposes, within NB102 sections 2, 3, 4, 5, 8,9, 10 & 11, the
column headed ‘CAP’ will report the Cash Account period obtained from the
‘C112’ transaction element. Where no ‘C112’ transaction element has been
received, the ‘CAP’ will be blank.
5. For reporting purposes within NB102 sections 2, 3, 4, 5, 8, 9, 10, 11, the column
headed ‘Discrepancy Type’ will report the ‘D’ discrepancy type and be populated
with the following codes:
(NB: For a list of Discrepancy Reason Codes for Network Banking, refer to
NB/IFS/008: NBE - Horizon Application Interface Specification)
Where no ‘D’ transaction element has been received, the ‘Discrepancy Type’ will
be blank
6. Where an exception is set to F99 by Fujitsu Services Pathway, clearance of this
exception within the appropriate NB102 section, (e.g. section 2 exceptions shown
as cleared within section 8), will always refer to the previously reported state
regardless of any change of state which may have occurred within the DRS.
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 18 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
7. All Uncleared Confirmed, Unconfirmed & TIP exceptions are reported as summary
totals by exception type - (NB102 section 1)
8. Uncleared Exceptioned Client Transactions are listed individually - (NB102
section 2)
9. Uncleared NBE/ DRS corruption’s exceptions are listed individually - (NB102
section 3)
10. Uncleared Timing Differences are listed individually — (NB102 section 4)
11. Uncleared Confirmed, Unconfirmed & TIP exceptions >24 hours are listed
individually — (NB102 section 5)
12. Uncleared Future Dated Transactions are reported as summary totals by Client
identified by Routing_Gateway — (NB102 Section 6)
13. All Cleared Confirmed, Unconfirmed & TIP exceptions are reported as summary
totals by exception type - (NBE102 section 7)
14. Cleared Exceptioned Client Transactions are listed individually — (NB102 section
8)
15. Cleared NBE / DRS corruption’s are listed individually — (NB102 section 9)
16. Cleared Timing differences are listed individually — (NB102 section 10)
17. Cleared Confirmed, Unconfirmed & TIP exceptions >24 hours are listed
individually — (NB102 section 11)
18. Cleared Future Dated Transactions are reported as summary totals by Client
identified by Routing_Gateway — (NB102 Section 12)
19. Within each section, exception summary totals / individual transactions are to be
grouped and sub totalled by reconciliation date with a total provided for the entire
section.
20. For reporting purposes:
¢ Timing Differences: relate to differences in the reconciliation date / settlement
date allocated where a settlement date on a transaction element is not the same
as the reconciliation date first reported on that transaction.
¢ Future Dated Transactions: relate to those transactions that have a
Reconciliation Date ahead of the Run Date of the report. For example, most
Clients will settle Friday, Saturday and Sunday transactions on the following
Monday. This means that each transaction completed on these days will have a
Reconciliation Date ahead of the Run Date of the report. These transactions
are expected to clear naturally once the Reconciliation Date and the Run Date
are in sync, however in the rare eventuality that a Reconciliation Date is
considerably ahead of the Run Date, POL may wish to clear the exception
manually. In this case, Fujitsu Services Pathway will set the transaction to
“F99".
21. For reporting purposes, within NB102 sections 2, 3, 4, 5, 8, 9, 10,11, the column
headed ‘Transaction Type’ will be populated by the following codes:
© 03 — Withdrawal (With PIN)
© 04 — Withdrawal with balance (With PIN)
© 05 — Withdraw all (With PIN)
e 13 — Withdrawal (With signature)
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 19 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
e 14 - Withdrawal with balance (With signature)
e 15 — Withdraw all (With signature)
¢ 2-Deposit (No verification)
22. For Network Banking reconciliation reporting, System States 8, 9, 10, 11, 16, 17,
18, 19, 20, 21,22,23, E05, E06, E07, E14, E22, E24, E31, E32, £33, E38 are
never expected within report NB102 because ‘S’ transactions are not used in NB.
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 20 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
FUJ00001740
FUJ00001740
Ref: CS/SPE/O11
Version: 5.0
Date: 29/12/02
3.3.1.1
3.3.1.1.1
NB102: Section 1 - Report Layout
NB102: Section 1: All Uncleared Confirmed, Unconfirmed & TIP exceptions
NB102 Section 1: All Uncleared
Confirmed, Unconfirmed & TIP
exceptions
Client: — Barclays etc
Produced on:
dd/mm/yyyy at hh:mm:ss
Run Date: dd/mm/yyyy
Transaction Type: Deposit &
Withdrawal
Currency: GBP
Exception I Reconciliation Volume Values ( 8 sub columns)
Type Date
State 1 ete dd/mmiyyy 99999999 9999999999.99
State 2 etc dd/mm/yyyy 99999999 9999999999.99
Sub total 999999999 9999999999.99
State E02 ete I dd/mm/yyy: 99999999 9999999999.99
Sub total 999999999 9999999999.99
Total Section 1 9999999999 9999999999.99
End of Report
3.3.1.1.2 NB102: Section 1 - Data Definition
NB102 Section 1: All Uncleared
Confirmed, Unconfirmed & TIP
Client: (Derived from
Routing_Gateway.)
Produced on:
(Date and time of report
exceptions production)
Run Date: (The period for which I Transaction Type: Deposit & Currency: (Derived from
the report refers) Withdrawal “currency’)
Exception Type / Reconciliation
Date
Volume
Values ( 8 sub columns)
Value of each transaction
component
One row for each system state
where exceptions are being
reported grouped within
reconciliation date with a sub total
for each reconciliation date and a
grand total for the section. Where
no data is being reported against
and exception state, the row for
that exception state is to be
suppressed. Where dates are shown
for the same exception type, list in
descending order
‘System State: 1-2, 4-11, 16-18,
E20-24, E32, E34-E36, E38
Received = New + Old
Reconciliation date: < = Run Date
E01-02 E04-06, E10-12, E14,
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 21 of 1
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/011
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.3.1.2 I NB102: Section 2: Uncleared Exceptioned Client Transactions
3.3.1.2.1 NB102: Section 2 — Report Layout
FUJ00001740
FUJ00001740
INB102 Section 2: Uncleared \Client: Barclays ete [Produced on: dd/mm/yyyy at hh : mm: ss
[Exceptioned Client Transactions
[Run Date: dd/mm/yyyy ITransaction Type: Deposit & \Currency: GBP
[Withdrawal
Exception Type I Reconciliation I Horizon Txn IdI Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
E13, id/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999..99
E13 id/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99I
State 12 dd/mm/yyyy Char 32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) _ I 9999999999.99
Sub Total 9999999999.99}
E13 dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) _ I 9999999999,99
Sub Total 9999999999.99I
[Total Section 2 9999999999.99I
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 22 of 1
Fujitsu Services
NETWORK BANKING END TO END Ref: CS/SPE/011
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.3.1.2.2 NB102: Section 2 — Data Definition
FUJ00001740
FUJ00001740
INB102 Section 2: Uncleared
IExceptioned Client Transactions
Client: (Derived from
[Routing Gateway.)
Produced on: (Date and time of production)
[Run Date: (The period for which the
jreport refers)
ITransaction Type: Deposit &
Withdrawal
\Currency: (Derived from ‘currency’)
Exception Type / Reconciliation] Horizon Txn Id I Transaction Bank Txn Id Receipt Date Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
One row for each exception, IHorizon_Txn_Nu ITxn_Type [Bank_TransactionlReceipt_TransactiIReceipt_TransactiIFrom C112 [Discrepancy_ReasIValue of each
with specific system states jm [Id n_Date jon_Time n_Codes itransaction
listed in order, grouped within component
reconciliation date with a sub
total for each reconciliation
date and a grand total for the
section. Where dates are shown
for the same exception type, list
in descending order.
System State: 12-15, 20-23, E03, E07 — E09, E13, E25 — E26, E33, E37
[Received = New + Old
[Reconciliation date: < = Run Date
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 23 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date: 29/12/02
3.3.1.3 NB102: Section 3: Uncleared Corruption’s
3.
.1 NB102: Section 3 — Report Layout
FUJ00001740
FUJ00001740
INB102 Section 3: Uncleared (Client: Barclays etc Produced on: dd/mm/yyyy at hh : mm : ss
\Corruption’s
[Run Date: dd/mm/yyyy [Transaction Type: Deposit & \Currency: GBP
[Withdrawal
Exception TypeI Reconciliation I Horizon Txn Id] Transaction I Bank TxnId I Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
IE28 (dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 999999999999}
IE29 (dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99I
E31 dd/mm/yyy' Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99
Sub Total 999999999999
E31 dd/mm/yyy: Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99
[Sub Total 9999999999.99I
[Total Section 3 9999999999.99I
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 24 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date: 29/12/02
3.3.1.3.2 NB102: Section 3 — Data Definition
FUJ00001740
FUJ00001740
INB102 Section 3: Uncleared
jcorruption’s
(Client:
Routing Gateway.)
(Derived from
Produced on: (Date and time of production)
[Run Date: (The period for which the
jreport refers)
ITransaction Type: Deposit &
Withdrawal
urrency: (Derived from ‘currer
ney’)
Exception Type / Reconciliation] Horizon Txn Id I Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
One row for each corruption, — Horizon_Txn_Nu [Txn_Type [Bank_TransactionlReceipt_TransactiIReceipt_TransactiIFrom C112 [Discrepancy_ReasIValue of each
with specific system states m I Id n_Date n_Time n_Codes transaction
listed in order, grouped within component
reconciliation date with a sub >
total for each reconciliation stem State: eon
date and a grand total for the eee
[Reconciliation date: < = Run Date
section. Where dates are shown
for the same exception type, list
in descending order.
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 25 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date: 29/12/02
3.3.1.4 I NB102: Section 4: Uncleared Timing Differences
3.
.1 NB102: Section 4 - Report Layout
FUJ00001740
FUJ00001740
INB102 Section 4:
: Uncleared
[Timing Differences
(Client: Barclays ete
Produced on: dd/mm/yyyy at hh : mm: ss
[Run Date: dd/mm/yyyy
[Transaction Type: Deposit &
(Currency: GBP
[Withdrawal
Exception TypeI Reconciliation I Horizon Txn Id] Transaction I Bank TxnId I Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
IE39 (dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 999999999999}
IE39 dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99I
E39 dd/mm/yyy' Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99
Sub Total 999999999999
E39 dd/mm/yyy: Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99
[Sub Total 9999999999.99I
[Total Section 4 9999999999.99I
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 26 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date: 29/12/02
3.3.1.4.2 NB102: Section 4 — Data Definition
FUJ00001740
FUJ00001740
INB102 Section 4: Uncleared
[Timing Differences
(Client:
Routing Gateway.)
(Derived from
Produced on: (Date and time of production)
[Run Date: (The period for which the
jreport refers)
ITransaction Type: Deposit &
Withdrawal
urrency: (Derived from ‘currer
ney’)
Exception Type / Reconciliation] Horizon Txn Id I Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
One row for each timing IHorizon_Txn_Nu ITxn_Type [Bank_TransactionlReceipt_TransactiIReceipt_TransactiIFrom C112 [Discrepancy_ReasIValue of each
difference, grouped within m I Id n_Date n_Time n_Codes transaction
reconciliation date with a sub component
total for each reconciliation =
date and a grand total for the S Stem State: E39
Received = New + Old
section. Where dates are shown we _
«_. [Reconciliation date: < = Run Date
for the same exception type, list
in descending order.
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 27 of 1
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/011
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.3.1.5 NB102: Section 5: Uncleared Confirmed, Unconfirmed & TIP exceptions >24 hours
3.
1 NB102: Section 5 — Report Layout
FUJ00001740
FUJ00001740
INB102 Section 5: Uncleared (Client: Barclays etc Produced on: dd/mm/yyyy at hh : mm: ss
(Confirmed, Unconfirmed & TIP
exceptions >24 hours
[Run Date: dd/mm/yyyy [Transaction Type: Deposit & ICurrency: GBP
[Withdrawal
Exception Type I Reconciliation I Horizon Txn IdI Transaction Bank Txn Id Receipt Date Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
State 1 (dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 999999999999}
State 2 (dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99I
State 6 dd/mm/yyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99
Sub Total 9999999999.9!
State 6 dd/mm/yyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99
Sub Total 9999999999.99I
[Total Section 5 9999999999.99I
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 28 of 1
Fujitsu Services
RECO
NETWORK BANKING END TO END
NCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date: 29/12/02
3.3.1.5.2 NB102: Section 5
— Data Definition
FUJ00001740
FUJ00001740
INB102 Section 5: Uncleared
(Confirmed, Unconfirmed & TIP
lexceptions >24 hours
(Clie
(Derived from
Routing_Gateway.)
Produced on: (Date and time of production)
[Run Date: (The period for which the
ITransaction Type: Deposit &
\Currency: (Derived from ‘currency’)
specific system states listed in order,
grouped within reconciliation date
with a sub total for each
reconciliation date and a grand total
for the section. Note: an extra
constraint for system states 2 & 18 is
that the outlet must have harvested
(TPS) successfully. Should an outlet
be confirmed as non-polling, system
states 2 &18 for that outlet on the
date(s) in question should not be
included on this report. Where dates
are shown for the same exception
type, list in descending order.
im
IId ion_Date tion_Time
‘eport refers) [Withdrawal
IException Type / Reconciliation DateI Horizon Txn Id) Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Type Type columns)
One row for each exception, with (Horizon_Txn_N ITxn_Type [Bank_Transaction IReceipt_Transac IReceipt_Transac IFrom C112 [Discrepancy_ReasIValue of each
n_Codes
itransaction
component
[Received = Old
Reconciliation date: < Run Date
System State: 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 16, 17, 18, E01-02 E04-06, E10-12, El4, E20-24, E32,
i.e. where transaction components have remained in the above incomplete states for >24 hours)
E34 -E36, E38
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 29 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.3.1.6 I NB102: Section 6: Uncleared Future Dated Transactions by Client
3.3.1.6.1_ NB102: Section 6 - Report Layout
NB102 Section 6: Uncleared All Clients Produced on:
Future Dated Transactions by dd/mm/yyyy at hh:mm:ss
Client
Run Date: dd/mm/yyyy Transaction Type: Deposit & Currency: GBP
Withdrawal
Client Reconciliation Date Volume Values ( 8 sub
columns)
Barclays dd/mm/yyyy 99999999 9999999999.99
Lloyds dd/mm/yyyy 99999999 9999999999.99
Total Section 11 9999999999 9999999999.99.
End of Report
3.3.1.6.2. NB102: Section 6 - Data Definition
NB102 Section 6: Uncleared All Clients Produced on:
Future Dated Transactions by (Date and time of report
Client production)
Run Date: (The period for which Transaction Type: Deposit & Currency: (Derived from
the report refers) Withdrawal “currency’)
Client / Reconciliation D:
One row for each Client derived from
Routing_Gateway where transactions have
been received with a reconciliatior
ahead of the run date. Where dates are
shown for the same exception typ
descending order.
ate Volume
Values (_8 sub columns)
Reconciliation date: >
n date
e, list in
System State: All States excluding F99
Run Date
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 30 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
FUJ00001740
FUJ00001740
Ref: CS/SPE/O11
Version: 5.0
Date: 29/12/02
3.3.1.7
3.3.1.7.1 NB102: Section 7 — Report Layout
NB102: Section 7: All Cleared Confirmed, Unconfirmed & TIP exceptions
NB102 Section 7: All Cleared
Confirmed, Unconfirmed & TIP
exceptions
Client: — Barclays etc
Produced on:
dd/mm/yyyy at hh:mm:ss
Run Date: dd/mm/yyyy
Transaction Type: Deposit &
Withdrawal
Currency: GBP
Exception Reconciliation Volume Values ( 8 sub columns)
Type Date
State 1 etc dd/mm/yyyy 99999999 9999999999.99
State 2 ete dd/mm/yyy: 99999999 9999999999.99
Sub total 999999999. 9999999999.99
State E02 etc dd/mm/yyyy 99999999 9999999999.99
Sub total 999999999. 9999999999.99
Total Section 1 9999999999 9999999999.99.
End of Report
3.3.1.7.2 NB102: Section 7 - Data Definition
NB102 Section 7: All Cleared
Confirmed, Unconfirmed & TIP
Client: (Derived from
Routing_Gateway.)
Produced on:
(Date and time of report
exceptions production)
Run Date: (The period for which I Transaction Type: Deposit & Currency: (Derived from
the report refers) Withdrawal “currency’)
Exception Type / Reconciliation
Date
Volume
Values ( 8 sub columns)
Value of each transaction
component
One row for each system state For last reported System States: 1-2, 4-11, 16-18, E01-02, E04-06,
where exceptions are being E10-12, E14, £20-24, E32, E34-36, E38
reported grouped within Set to F99: New
reconciliation date with a sub total I Reconciliation date: <= Run Date
for each reconciliation date and a
grand total for the section. Where
no data is being reported against
and exception state, the row for
that exception state is to be
suppressed. Where dates are shown
for the same exception type, list in
descending order.
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 31 of 1
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/011
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.3.1.8 I NB102: Section 8: Cleared Exceptioned Client Transactions
3.3.1.8.1 NB102: Section 8 — Report Layout
FUJ00001740
FUJ00001740
IExceptioned Client Transactions
'B102 Section 8: Cleared (Client: Barclays ete Produced on: dd/mm/yyyy at hh: mm: ss
[Run Date: dd/mm/yyyy [Transaction Type: Deposit & (Currency: GBP
Withdrawal
Exception Type I Reconciliation I Horizon Txn IdI Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
IE13 Idd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99)
E13 \dd/mm/yyy: Char (32) Code (99) Char (6) dd/mm/yyy Num (2) Code (99) 9999999999.99)
State 12 dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyy: hh:mm:ss Num (2) Code (99) 9999999999.99
Sub Total 9999999999.99)
EB dd/mm/yyyy Char 32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) I 9999999999.99
Sub Total 9999999999.9'
(Total Section 8 9999999999 .99
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 32 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref:
Version:
Date:
CS/SPE/011
5.0
29/12/02
3.3.1.8.2. NB102: Section 8 — Data Definition
FUJ00001740
FUJ00001740
INB102 Section 8: Cleared
[Exceptioned Client Transactions
(Client: (Derived from
Routing Gateway.)
Produced on: (Date and time of production)
Run Date: (The period for which the
report refers)
[Transaction Type: Deposit &
Withdrawal
‘Currency: (Derived from ‘currency’)
Exception Type / Horizon Txn Id I Transaction Bank Txn Id Receipt Date Receipt Time CAP Discrepancy I Values ( 8 sub
Reconciliation Date Type Type columns)
One row for each exception, Horizon_Txn_Nu ITxn_Type [Bank_TransactionIReceipt_Transacti IReceipt_Transacti IFrom C112 [Discrepancy_ReasIValue of each
with specific system states Id n_Date n_Time n_Codes transaction
listed in order, grouped component
within reconciliation date
with a sub total for each
reconciliation date and a
grand total for the section.
Where dates are shown for
the same exception type, list
in descending order.
[For last reported System States: 12-15, 2!
Set to F99: New
Reconciliation date: < = Run Date
3,
E03, E07 — E09, E13, E25 —E26, E33, E37
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 33 of 1
Fujitsu Services NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date:
29/12/02
3.3.1.9 I NB102: Section 9: Cleared Corruption’s
3.3.1.9.1 NB102: Section 9 — Report Layout
FUJ00001740
FUJ00001740
'B102 Section 9: Cleared (Client: — Barclays ete [Produced on: dd/mm/yyyy at hh: mm: ss
(Corruption’s
[Run Date: dd/mm/yyyy [Transaction Type: Deposit & (Currency: GBP
Withdrawal
Exception Type I Reconciliation I Horizon Txn IdI Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
[E28 Idd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99)
[E29 \dd/mm/yyy: Char (32) Code (99) Char (6) dd/mm/yyy Num (2) Code (99) 9999999999.99)
State 31 dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyy: hh:mm:ss Num (2) Code (99) 9999999999.99
Sub Total 9999999999.99)
E31 dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99.
Sub Total 9999999999.9'
(Total Section 9 9999999999 .99
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 34 of 1
Fujitsu Services
COMMERCIAL IN CONFIDENCE
NETWORK BANKING END TO END
RECONCILIATION REPORTING
Ref:
Version:
Date:
CS/SPE/011
5.0
29/12/02
3.3.1.9.2. NB102: Section 9 — Data Definition
FUJ00001740
FUJ00001740
INB102 Section 9: Cleared
‘orruption’s
\Client:
(Derived from
[Routing Gateway.)
Produced on: (Date and time of production)
IRun Date: (The period for which the
report refers)
[Transaction Type: Deposit &
Withdrawal
‘Currency: (Derived from ‘currency’)
Exception Type / Reconciliation} Horizon Txn Id I Transaction Bank Txn Id Receipt Date Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
One row for each corruption, — [Horizon_Txn_Nu ITxn_Type [Bank_TransactionReceipt_TransactiIReceipt_TransactiIFrom C112 [Discrepancy_ReasIValue of each
with specific system states im I Id n_Date jon_Time jon_Codes ransaction
listed in order, grouped within omponent
reconciliation date with a sub
total for each reconciliation
date and a grand total for the
section. Where dates are shown
for the same exception type, list
in descending order.
Set
to F99: New
Reconciliation Date: <= Run Date
For last reported System States: E27 —31
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 35 of 1
Fujitsu Services NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date:
29/12/02
3.3.1.10 INB102: Section 10: Cleared Timing Differences
3.3.1.10.1 NB102: Section 10 - Report Layout
FUJ00001740
FUJ00001740
INB102 Section 10: Cleared Timing.
Differences
(Client: Barclays ete
[Produced on: dd/mm/yyyy at hh: mm: ss
Run Date: dd/mm/yyyy
Withdrawal
\Transaction Type: Deposit &
(Currency: GBP
Exception Type IReconciliation
Horizon Txn IdI Transaction I Bank TxnId I Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
IE39 kdd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99
[E39 kid/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyy’ hh:mm:ss Num (2) Code (99) 9999999999.99
E39 dd/mm/yyy’ Char (32) Code (99) Char (6) dd/mm/yyy’ hh:mm:ss Num (2) Code (99) 9999999999.99.
Sub Total 9999999999.99
E39 dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99.
Sub Total 9999999999.9'
[Total Section 10 9999999999.99)
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 36 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref:
Version:
Date:
CS/SPE/011
5.0
29/12/02
3.3.1.10.2_ NB102: Section 10 — Data Definition
FUJ00001740
FUJ00001740
[Differences
INB102 Section 10: Cleared Timing
(Client: (Derived from
Routing Gateway.)
Produced on: (Date and time of production)
report refers)
[Run Date: (The period for which the [Transaction Type: Deposit &
Withdrawal
‘Currency: (Derived from ‘currency’)
reconciliation date with a sub
total for each reconciliation
date and a grand total for the
section. Where dates are shown
for the same exception type, list
in descending order.
Exception Type / Reconciliation] Horizon Txn Id I Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
One row for each timing [Horizon_Txn_Nu ITxn_Type [Bank_TransactionReceipt_TransactiIReceipt_TransactiFrom C112 [Discrepancy_ReasIValue of each
difference, grouped within m I Id n_Date jon_Time jon_Codes ransaction
component
For last reported System States: E39
Set to F99: New
Reconciliation Date: <= Run Date
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 37 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/011
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.3.1.11 NB102: Section 11: Cleared Confirmed, Unconfirmed & TIP exceptions > 24 hours
3.3.1.11.1 NB102: Section 11 — Report Layout
INB102 Section 11: Cleared (Client: Barclays ete [Produced on: dd/mm/yyyy at hh: mm: ss
(Confirmed, Unconfirmed & TIP.
lexceptions > 24 hours
[Run Date: dd/mm/yyyy \Transaction Type: Deposit & (Currency: GBP
(Withdrawal
Exception Type I Reconciliation I Horizon TxnI Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Id Type Type columns)
State 1 kid/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.95
State 2 kid/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mr Num (2) Code (99) 9999999999.99I
State 6 dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 999999999999.
Sub Total 9999999999.99)
State 6 dd/mm/yyyy Char (32) Code (99) Char (6) dd/mm/yyyy hh:mm:ss Num (2) Code (99) 9999999999.99.
Sub Total 9999999999.9'
(Total Section 11 9999999999.99)
End of Report
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 38 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/011
Version: 5.0
Date: 29/12/02
3.3.1.11.2 NB102: Section 11 — Data Definition
FUJ00001740
FUJ00001740
INB102 Section 11: Cleared
\Confirmed, Unconfirmed & TIP
lexceptions > 24 hours
(Client:
[Routing_Gateway.)
(Derived from
Produced on: (Date and time of production)
[Run Date: (The period for which the
report refers)
\Transaction Type: Deposit &
Withdrawal
(Currene
(Derived from ‘currency’)
Exception Type / Reconciliation [Horizon Txn Id) Transaction Bank Txn Id Receipt Date I Receipt Time CAP Discrepancy I Values ( 8 sub
Date Type Type columns)
One row for each exception, with IHorizon_Txn_NiTxn_Type [Bank_TransactionlReceipt_TransactiIReceipt_TransactiFrom C112 Discrepancy_ReasIValue of each
specific system states listed in jum I Id n_Date n_Time jon_Codes ransaction
order, grouped within component
reconciliation date with a sub total
for each reconciliation date and a
grand total for the section. Note:
an extra constraint for system
states 2 & 18 is that the outlet
must have harvested (TPS)
successfully. Should an outlet be
confirmed as non-polling, system
state 2 & 18 for that outlet on the
date(s) in question should not be
included on this report. Where
dates are shown for the same
exception type, list in descending
order.
Set
to F99: New
For last reported System States: 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 16, 17, 18, E01-02 E04-06, E10-12, El4, E20-24, E32, E34-E36, E38
{Transactions that were included on report NB102 Section 5 on ‘yesterday’s’ reports and are not included in NB102 Section 5 on
today’s’ reports.”
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 39 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/011
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 40 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.3.1.12 NB102: Section 12: Cleared Future Dated Transactions by Client
3.3.1.12.1 NB102: Section 12 - Report Layout
NB102 Section 12: Cleared All Clients Produced on:
Future Dated Transactions by dd/mm/yyyy at hh:mm:ss
Client
Run Date: dd/mm/yyyy Transaction Type: Deposit & Currency: GBP
Withdrawal
Client Reconciliation Date Volume Values ( 8 sub
columns)
Barclays dd/mm/yyyy 99999999 9999999999.99
Lloyds dd/mm/yyyy 99999999 9999999999.99
Total Section 11 9999999999 9999999999.99.
End of Report
3.3.1.12.2 NB102: Section 12 - Data Definition
NB102 Section 12: Cleared All Clients Produced on:
Future Dated Transactions by (Date and time of report
Client production)
Run Date: (The period for which Transaction Type: Deposit & Currency: (Derived from
the report refers) Withdrawal “currency’)
Client / Reconciliation Date
One row for each Client derived from
Routing_Gateway where transactions have
been received with a reconciliation date
ahead of the run date. Where dates are
shown for the same exception type, list in
descending order.
Volume
[Values (8 sub columns)
System State: All States
All transactions that wer
6 on ‘today’s’ reports.
e included on report NB102 Section 6
on ‘yesterday’s’ reports and are not included in NB102 Section
End of Report
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDE!
NCE Page: 41 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref:
Version:
Date:
CS/SPE/011
5.0
29/12/02
FUJ00001740
FUJ00001740
3.3.1.13
Incomplete and Discrepancy State: Report Matrix
This table identifies the NB102 series report section where incomplete and discrepancy
States are reported in detail.
Incomplete Transaction Components Exception report NB102
State Section
C112 C12 C4 Ss D Uncleared I Cleared
1 Vv 1&5 T&M
2 Vv V 1&5 7&1
4 Vv 1&5 7T&ll
3 V 1&5 T&M
6 v v 1&5 T&1
7 V Vv 1&5 7&1
8 v 1&5 7&1
9 v V 1&5 7&1
10 V Vv 1&5 T&11
in V V Vv 1&5 T&11
12 v 2 8
B V Vv 2 8
4 V V 2 8
15 V V V 2 8
16 Then V V 1&5 7&1
17 y Then ¥ V 1&5 T&IL
18 V Then V V 1&5 7&1
20 V Then V 2 8
21 V V Then V 2 8
22 v Vv Then V 2 8
23 Vv V Vv Then V z 8
Shaded lines represent System States not expected to be reported within the Network
Banking report set
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 42 of 1
Fujitsu Services
NETWORK BANKING END TO END
RECONCILIATION REPORTING
COMMERCIAL IN CONFIDENCE
Ref: CS/SPE/O11
Version: 5.0
Date: 29/12/02
FUJ00001740
FUJ00001740
3.3.1.14 Exception State: Report Matrix
This table identifies the NB102 series report section where an exception is reported in
detail.
Exception Description Exception report NB102
State Section
Uncleared Cleared
E01 IAdditional C112 1&5 7&1
E02 IAdditional C12 1&5 7&il
E03 IAdditional D 2 8
E04 Additional C4 1&5 7&1
E05 \Additional S 1&5 7&1
E06 IS after C4 1&5 T&M
E07 S after D 2 8
E08 (C4 after D 2 8
E09 ID after C4 2 8
E10 (C112 after final state 1&5 7&ll
Ell (C12 after final state 1&5 7&1
El2 (C4 afier final state 1&5 7&ll
E13 D after final state 2 8
El4 \S after final state 1&5 7&1
EIs lot Used
E16 lot Used
El7 lot Used
Els lot Used
E19 lot Used
E20 [Amount of C112#C12 1&5 7&1
E21 Amount of C112#C4 1&5 7&1
E22 [Amount of C112#S & C112#0 1&5 7&1
E23 Amount of C12#C4 1&5 7&1
E24 (Amount of C12#S & C12#0 1&5 FRU
E25 IAmount of C112#D 2 8
E26 [Amount of C12#D 2 8
E27 IIncomplete/corrupt C112 3 9
E28 __IIncomplete/corrupt C12 3 9
E29 [Incomplete/corrupt C4 3 9
E30 Incomplete/corrupt D 3 9
E31 [Incomplete/corrupt S 3 9
E32 IAmount of C4#S & C4#0. 1e5 7&il
E33 IAmount of D#S 2 8
E34 (C112 arrived after state F99 1&5 7&1
E35 12 arrived after state F99 1&5 7&ll
E36 (C4 arrived after state F99 1&5 7T&ll
E37 D arrived after state F99 2 8
E38 S arrived after state F99 1&5 7&1
E39 Settlement Date # Reconciliation Date 4 10
Shaded lines represent System States not expected to be reported within the Network
Banking report set
© 2002 Fujitsu Services
COMMERCIAL IN CONFIDENCE
Page: 43 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
3.4 NBI103: Settled transaction / Cash Account Reconciliation
Statement
This report allows POL to reconcile the settlement stream against the Outlet Cash
Account stream. This reconciliation is required as settlement with the individual POL
clients is based upon the ’C4 Processing Date’. To complete a full reconciliation, it is
important to know which Cash Account the settled transaction was posted to, to
enable a reconciliation of settlement to be made with the outlet records. This report
reconciles the transactions by ‘C4 Processing Date’ and Cash Account record.
3.4.1 NB103: Rules
1. NB103 is run weekly: In order to align with internal POL / TIP processing it is
required that this report is produced AFTER TPS and NB101 processing on
Friday and BEFORE TPS processing on Saturday. The report should include all
“C4 transaction values where:
e °C4 Processing Date’ = run date and,
© °C4 Processing Date’ = run date minus‘N’ (where ‘N’ = I to 13).
2. Where a C112 is available and the CAP is known, the ‘C4’ transaction value will
be posted against the appropriate CBDB CAP column
3. Where a C112 is available and the CAP is known, but there is no C4, it will not be
reflected in the report because this report includes C4 transaction values only.
4. Where no C112 is available and therefore the CAP is unknown:
e the ‘C4‘ transaction value should be posted to ‘No Cash Account Allocated’
e then, when the C112 becomes available, the entry should be deleted from ‘No
Cash Account Allocated’ and posted to the appropriate CBDB CAP column
e ifno C112 has been received after 14 days, the entry within ‘No Cash
Account Allocated’ should remain until the C112 becomes available even
if this exceeds 14 days
5. If a transaction is posted to the row ‘No C/A to TIP’ (according to rule 2 and 3
above:
¢ the transaction should remain in this row until the Cash Account has been delivered to TIP
and then move up into the row ‘C/A to TIP”
e ifno Cash Account has been delivered to TIP after 14 days, the entry within
‘No C/A to TIP’ should remain until the Cash Account is delivered to TIP
even if this exceeds 14 days
6. As the report is run each week, the transactions should move across the report
according to the CAP and the reconciliation date; for example, a transaction posted
to CBDB>=plus 2 in the first week, will move to CBDB plus 1 the second week
and then appear in CBDB the third week, until disappearing off the report after 14
days
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 44 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/O11
RECONCILIATION REPORTING
Version: 5.0
COMMERCIAL IN CONFIDENCE Date: 29/12/02
12
13.
14.
Where the columns headed ‘CAPXX’ are referred to, the actual report produced
with show the actual CAP number, for example CBDB CAP 40 is quoted, the
column ‘CAPXX<=-2’ will show “‘CAP40<=-2’
NB103 reports on VALUE only
A separate report NB103 will be produced for both Deposit and Withdrawal
transactions derived from “Txn_type’
. Five CAP’s will be shown, the ‘CBDB’, the ‘CBDB’ minus 1, the ‘CBDB’ <=
minus 2, the ‘CBDB’ plus I and the ‘CBDB’ >=plus 2. In addition, those settled
transactions which currently have not been allocated a Cash Account will be
shown.
. The ‘CBDB’ Cash Account period (CAP) equates to TWO CAP’s prior to the
CAP applicable to the run date of the report. For example: If the report was run on
Saturday 20" January within CAP42 (CAP 42 commenced on Thursday 17"
January), the ‘CBDB’ CAP would be CAP40 (CAP40 commenced Thursday 3"
January, ended Wednesday 9" January)
Where the CAP in which the Outlet is trading is numerically more than 2 weeks
prior to the “CBDB’ CAP, if this takes the Outlet CAP into the previous year, this
will be reported as such. For example: The ‘CBDB’ CAP is CAP I and the Outlet
is trading in CAP 51, this is assumed to be CAP 51 of the previous year,
(therefore ‘CBDB’ <=minus 2) and not reported ahead in the current year.
The C4 processing dates will be shown in reverse chronological order.
For a given C4 Processing Date, the sum of the two Total values (for the two rows
C/A to TIP and No C/A to TIP) should be equal to the Total corresponding
Receipts or Payments value on report NB101 for the same Run Date.
© 2002 Fujitsu Services COMMERCIAL IN CONFIDENCE Page: 45 of 1
Fujitsu Services NETWORK BANKING END TO END
RECONCILIATION REPORTING
Ref:
Version: 5.0
CS/SPE/11
FUJ00001740
FUJ00001740
Commercial in confidence Date: 11-DEC-2002
NB103: Report Layout
INB103: Settled Transaction / Cash Account (Client: Barclays ete Produced on: dd/mm/yyyy at hh:mm:ss
Reconciliation Statement
[Run Date: dd/mm/yyyy
(Transaction Type:
Deposits etc
(Currency: GBP
C4 Processing Date CAP ‘XX’ <=-2 CAP ‘XX’ -1 CBDB CAP ‘XX? +1 CAP ‘XX’ >= +2 I No Cash Account Total Value
CAP ‘XX’ Allocated
(Column 2) (Column 3) (Column 4) (Column 5) (Column 6) (Column 7) (Column 8)
\dd/mmv/yyyy (C/A to TIP. 9999999999.99I 9999999999.99I 9999999999.99I 9999999999.99I 9999999999.99I 9999999999 .99 999999999999)
jo C/A to TIP 9999999999.99I 9999999999.99I 9999999999.99I 9999999999.99I 9999999999.99I 9999999999 .99} 9999999999 .99I
\dd/mm/yyyy (C/A to TIP 9999999999.99I 9999999999.99I 9999999999.99) 9999999999.99I 9999999999.99I 9999999999 .99 999999999999)
0 C/A to TIP 9999999999.99I 9999999999.99I 999999999999) 9999999999.99I 9999999999.99I 9999999999 .99 9999999999 .99I
id/mn/yyyy, /A to TIP 9999999999.99I 9999999999.99I 9999999999.99} 9999999999.99I 9999999999.99I 9999999999 .99} 999999999999}
0 C/A to TIP 9999999999.99I 9999999999.99I 9999999999.99) 9999999999.99I 9999999999.99I 999999999999} 999999999999)
\dd/mmv/yyyy (C/A to TIP. 9999999999.99I 9999999999.99I 9999999999.99I 9999999999.99I 9999999999.99I 9999999999 .99} 9999999999.99I
0 C/A to TIP 9999999999.99I 9999999999.99I 9999999999.99) 9999999999.99I 9999999999.99I 999999999999} 9999999999 .99I
End of Report
© 2002 Fujitsu Services Commercial in Confidence
Page: 46 of I
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO END Ref: CS/SPE/11
RECONCILIATION REPORTING
Version: 5.0
Commercial in confidence Date: 11-DEC-2002
3.4.1.2 NB103: Data Definition
INB103: Settled Transaction / Cash Account (Client: (Derived from Routing_Gateway) Produced on: (Date and time of production)
Reconciliation Statement
[Run Date: (The period for which the report refers—post [Transaction Type: (Derived from Txn_Type) \Currency: (Derived from ‘currency’)
Friday pre Saturday TPS processing)
C4 Processing Date CAP ‘XX’ <=-2 CAP ‘XX’ -1 CBDB CAP ‘XX’ +1 CAP ‘XX’ >= +2 I No Cash Account Total Value
(The Run Date of NB101 that CAP ‘XX’ Allocated
included the C4)
(Column 2) (Column 3) (Column 4) (Column 5) (Column 6) (Column 7) (Column 8)
id/mm/yyyy V/A to TIP [Total value of all settled transactions (C4) where the Cash Account has been delivered to POL / TIP, according to C4 ‘Sum Columns 2, 3,
processing date to allocate rows and using the CAP available from the C112 component to allocate the appropriate column. #4, 5, 6, 7 for this C4
here no C112 transaction component is present, use the ‘No Cash Account Allocated’ column. processing date
IAll C4 values
[Use C4 processing date for 14 days prior to Run Date of the report, and where C4 transactions are still being shown against
‘No Cash Account Allocated’ or ‘No C/A Delivered to TIP’ show these days in addition.
\dd/mmi/yyyy oC/Ato TIP [Total value of all settled transactions (C4) where the Cash Account has not been delivered to POL / TIP, according to C4 Sum Columns 2, 3,
processing date to allocate rows and using the CAP available from the C112 component to allocate the appropriate column.
Where no C112 transaction component is present, use the “No Cash Account Allocated’ column.
IAll C4 values
[Use C4 processing date for 14 days prior to Run Date of the report, and where C4 transactions are still being shown against
[No Cash Account Allocated’ or ‘No C/A Delivered to TIP’ show these days in addition.
4, 5, 6, 7 for this C4
rocessing date
End of Report
© 2002 Fujitsu Services
Commercial in Confidence Page: 47 of 1
FUJ00001740
FUJ00001740
Fujitsu Services NETWORK BANKING END TO EN! Ref: CS/SPE/11
RECONCILIATION REPORTING.
Version: 5.0
Commercial in confidence Date: 11-DEC-2002
4.0 System States
wen
lorizicrzi ce os
Preswaion [ives en: reve
(n eemplteCorpl or go: E27 E28 E29 £10 EH
Valle on erry b Se means not equ) NSU Acton
Side Con Agert_NBE_TPS Wen vail, go Ste I—_ Anour:Acon Anourtscton I Arourtécton Setement Ose Acton I Set st
sat! 0 i142 @ -
1 oe € &2 2 1% 10 - : F29
2 co 3 Em EM E09 G06 I GrzwOH ES Ct Ste tes OLESS F39
Fr 3 iz ok atte Fro E11 E12 £13 E14] citzwciZE2 ——_cHt2HCHEI Ste twos LESS :
4 ce 7 2 €o E09 E06 : : : Foo
5 cma m6 7 9 : = Fo
6 oR ita fo EQ 3 18 M1 I cttewcrzz : F39
T ot on For 3 G4 E09 B06 I cIteHOREZL : Ste tes DEEDS F39
+ 8 9 10 16 20. 0s - : - F99
9 8 ong fol 11 17 21s [ottaws aciroweze - 8 Sete Cec O19 F39
oe 8 11 EQ 18 2 £05 I C12¥s acioweae - Sete Cer RES Fas
1 oe 8 ote Fol Em 19 2 eS I cItzHCIZE2 Claws aclaw Eze 8 Sete Coc [KES Fs9
12 ° 1413 E08 63, E07 - : : - F99
8 oR 15 Ei Eos E0G Eo? I CiLWD(CI2) E26 - Sete Rec OLED F9
14 © ote Eo 16 E08 E00 Eo? I ciawo(ctay eas = 0 Sate OtRer OLE39 F99
6 cb atte fot Ex Eos E0e or I cHtzHCIZER —_cHteAD(CIR) ERE : ete Otc OCE29 Fs9
16 8104 17 18 E04 £09, E06 I CA¥S BCAHOLESD - : i Ste Rec LEDS F39
” Sica ota foi 19 Eo E09 eos I CITzACHEA CANS BHM: z i Ste Rec LESS F39
tec sic8 19 EQ EO E19 £05 I CIQHOLER CHWS BCHNDERZ (Sate two: DEEDS F99
Fra 19 lz ice rte Bio E11 E12 £12 E14 I ctt2ACIZEI0 CieHOLEZS CHWS CHHDERZ I CA Sale tw DEES :
20 80 21 2 ee em 605 I DANSE : : Sate twRec OLE39 Fo9
2 8 o112 Ent 25 Eos E00 05 [CHOW ACIIQME —_D(AWBED Sete OtvRer OLEH Fs9
2 oR sD 2 EQ E08 E0S £06 I CIB ACIWEN —_OAWRERS 0 sete OtwRec OL E39 F39
Bok 9p ote Ent E02 Eos B06 0S I CIYZACIZERD CHWS ACLIQWDEZ DAHER sete Ror OLE39 F393
EDT tonal 112 ma z 5 : Fe
xe, Acional O12 fet: - - - F39
Anal D z[eI: : : Fag
04 Adonalo4 ee z a : Fs9
£06 Asia 3 ee - £39
E06 Sater OA 5 Fee
Eo? Sater D an F99
E08 Chater D ete i : a F9
£09 Date Ch t-te 5 - - £39
10 O12 tir ral de 5 Fae
V1 12 air alta : : F99
12 OM ar al ie hehe - = : F39
13. ater ral te eases : F39
E14 Sara le -t: : : £99
E16" Netused Tey >
E16. Notused ae : : :
EIT Notused a : : : :
E18 Notused - : - :
E19. Notused =t= : -
E20 Aneurtl CTT2HOI2 TT : : : Fe
E21 ancl C1204 Te : 5 Foe.
E22 sncurtl C1248 GCI . : : F99
Ez Aart 12404 : : F99
E24 nourtal C124 &CI2H) Te : zi Fo9
25. scr C1240 ae 5 5 : : F99
£26 Anus C120 - - : - F39
E27 irconpleetCoru C112 tats 5 Foe
£28 rcomplete/Corupt 12 ae : = Fs9
£29 ncomplee/Corupt C4 = [ete 5 5 : F39
£30, rcompletCorrugt 0 F39
ES1_reomplee/Corugt § =f Te F29
E52 Ancurtt CAH & C0 ete - : : Fae
E55 anu OF, _- : : 39
E4112 awed roe 29 Te F993
56.12 ave arse 99 a : : F9
96. ave cer se F99 eae : = : 5 Fs9
STD ave cer ste F993 ae : : : F39
St 8 ave ao te F9 : £99
Ero. Setiert Da # Recordar Dab ~t-t-]-1 = : Foe
Fal F99-MSU rested Ea 6 6 67 z z z zi
© 2002 Fujitsu Services Commercial in Confidence Page: 48 of 1