isu Services Impact Release 3 - Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE, Date: 31-August-049""
September 2004
FUJ00090247
FUJ00090247
Document Title: Impact Release 3 - Declaration, Correction and Revaluation
User Interface
Document Type: User Interface Design Proposal
Release: S80
Abstract: This document presents a description of the changes to the
dialogue, activity flows, screen flows, reports and receipts to be
developed for the Horizon Counter Application as a result of the
introduction of Impact Release 3
Document Status: DRAFFAPPROVED
Originator & Dept: Pete Jobson — Development Unit
Contributors:
Internal Distribution: Fujitsu Services Document Management, Reviewers
External Distribution: Reviewers
Approval Authorities:
Name Position Signature Date
Gareth Jenkins Fujitsu Services
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 1 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/O12
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date:
September 2004
FUJ00090247
FUJ00090247
9
0.0 Document Control
0.1 Document History
Version No. I Date Reason for Issue Associated
CP/PinICL
01 27" May 2004 I First official draft for formal comments
0.2 23" June 2004 I Updated following comments on version 0.1
0.3 315! Aug 2004 I Updated following comments on version 0.2 I -{ Formatted
Lo 98 Sept 2004 _I Updated following comments on version 0.3 (Formatted
0.2 Review Details
Review Comments by: I 30""June 2004N/A
Review Comments to: I Originator
Mandatory Review Authority
‘Name
Fujitsu Services
Gareth Jenkins, Walter Wright, Helen Pharoah, Trish
Morris, Neil Gormley, Phil Hemingway, Phil Orton,
Martin Nixon, Linda Miller
Post Office Ltd
Karen Hillsden 0
Ben Gilderslev
John Dutton
Alan Oxpe
eae
Optional Review / Issued for Information.
(*) = Reviewers that returned comments
Janusz Hollender, Matt Arris, Roger Donato, Chris
Bailey, Dave Johns, Trevor Leahy, Duncan MacDonald
0.3 Associated Documents
Reference I Version I Title Source
EA/CDE/002 IMPACT - Branch Trading Reporting, POL
Management and Control and Transaction
Management
EA/DPR/004 Impact Release 3 Design Proposal Fujitsu
Services
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 2 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal 0.31.0
COMMERCIAL IN-CONFIDENCE Date: 31 -August-049""
September 2004
Reference I Version I Title Source
EAMES/O11 Impact Release 3—Report Production User I Fujitsu
Interface Services
FAMFS/013 Impact Release 3 — Balancing and Trading Fujitsu
Statement Production User Interface Services
SD/DES/005 Horizon OPS Reports and Receipts — Post Fujitsu
Office Account Horizon Office Platform Services
Service
SD/DOC/009 Horizon OPS Desktop Messages and Help Text I Fujitsu
Services
SD/SPE/022_ I 222 Horizon OPS Menu Hierarchy: Changes Fujitsu
Supplement for SD/SPE/016 v33.0 Services
SD/SPEOIG [34.0 Horizon OPS Menu Hierarchs Fujitsu
Services
FBASUSTR Impact Programme S80 Migration Strategy Fajitse
/007 ‘ cesPOL
FAMFS/002 AIS Transaction Correction Interface Prism Alliance
Unless a specific version is referred to above, reference should be made to the current
approved versions of the documents.
0.4 Definition of Terms
Term
Definition
Branch
A Post Office or any other location where Post Office Ltd (whether
directly or by means of agents) transacts business with customers.
Button
Icon on the Riposte Desktop that can be selected by the user via the
touch-screen or equivalent keyboard function key to invoke a
particular action.
Clerk
Any person who serves customers at a Counter Position in a Post
Office.
Counter
A serving position in a Post Office, where a Customer transacts
business with a Counter Clerk. Within this document, the term
‘Counter’ also refers to a personal computing device used within the
Horizon system for the purposes of Branch Back-office
functionality.
Counter Application
‘An application resident within the counter processor that contains
the business logic controlling the dialogue with the Clerk.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 3 of 62
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EA/IFS/(012
Revaluation User Interface
User Interface Design Proposal 031.0
COMMERCIAL IN-CONFIDENCE, Date: 31-August-049!"
September 2004
FUJ00090247
FUJ00090247
Term Definition
Horizon The service implemented by Fujitsu Services for Post Office Ltd
Mode Environment within the Riposte Desktop where a transaction is
processed.
Office Receipt The transaction receipt retained in the Outlet.
Receipt A printed record of the transaction at the office. Both office and
customer receipts may be produced.
Reference Data A set of agreed parameters and relationships controlling the
operation of Post Office Ltd Services.
Transaction A recorded and auditable instance of business activity, involving
service provision or stock movement across organisational or
service boundaries.
User Interface The dialogue between the Post Office Clerk and the Horizon
platform in the Post Office.
0.5 Abbreviations
‘Abbreviation Definition
CBDB Counters Business DataBase. Post Office Limited’s current
Accounting Systems
CRM Credit Note
DP Design Proposal
MOP Method of Payment
0.6 Changes in this Version
Version Changes
61.02 Various changes following comments on version 0.34, These
changes are highlighted using Word™ change tracking, Changes to
screen pictures are not change-marked.
0.7 Changes Expected
Changes
‘sChaige-ta-section 2-41-3-f00k lass fieasenoe tend. te-chi
oh: is 24 PPEOP
control.
» (Cinagete stan s seo tt larification.ofreq {and appropriate chang
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 4 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EA/IFS/(012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE, Date: —_31-August-049!" i}
September 2004
contol
© Change to section 4.3.5 to include a Debit Card option following appropriate change
control._This will probably be implemented at release $90
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 5 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/O12
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049{"
‘September 2004
FUJ00090247
FUJ00090247
0.8 Table of Contents
1.0 I INTRODUCTION.
1.1 Report Production.
1.2 Declaration, Correction and Revaluation
1.3 Balancing and Trading Statement Production
14 Scope. . a .
14.1 DP Cross. Reference...
1.4.2 Migration Points .
15 Structure of this document
2.0 GRAPHICAL USER INTERFACE DESIGN .....ssssssssssssseseeseeeeeseeseeesesssstennsnnen
21 Overview...
2d Stock Processing.
21.1.1 Remittances and Transfers
21.12 Stock Revaluation
2.113 Merging Value and Non-Value Stock
2.1.2 Changes to Cash’Stock Declarations and Varianee Handling .
212.1 Changes to Cash Declarations.
2122 Check for Variances
2123 Cash Variance Report
2124 Cash Variance Processing
2125 Stock Declarations and Variances.
2126 Cash Declaration Check.
2.1.3 Processing Transaction Corrections
2.13.1 Transaction Correction Check
2.132 Selecting and Processing Transaction Corrections
2.133 Reporting on Transaction Corrections
2.1.4 — Conventions used within the dialogue flowcharts...
2.2. Check For Variances
2.3 Make Good Variances..........
24 Select and Process Transaction Corrections
3.0 REPORTS AND RECEIPTS.
3.1 Counter Daily Revaluation Slip ..
3.2 Non-Value Stock Reports .....
3.3, Cash Variance Report.
3.3.1 Purpose
3.3.2. Frequency...
33.3. Notes...
Sequence...
Layout and Example Content
Description nnn
336.1 General
3362 Reporting Period
3363 Variances, Derived and Declared Figures and SU Breakdowns Declarations 28
3364 Known Discrepancies 28
3.3.6.5 Adjustments to physical cash on hand 28
3.36.6 Transaction Corrections 28
336.7 Missing Declarations (‘x’) 28
3368 Pagination 29
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 6 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/O12
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049!"
September 2004
FUJ00090247
FUJ00090247
_—[Formatted
34
341
342
343
344
345
346
3.47
348
4.0 SCREEN LAYOUTS
4.2.10 Seren 10 ~ Enter Amount Made Good or Removed...
4.3
431
432
433
434
2 Screen 11 ~ Previous Make Good Advice.
4.2.13 Sereen 12 ~ Cash Declaration Check
Transaction Corrections ns Reports.
PUPOSE sa
Frequency...
Notes...
Sequence ae a
Outstanding Transaction Corrections Layout. 31
Processed Transaction Corrections Layout 33
‘Transaction Corrections Additional Information 35
Pagination w.nsnnonnn
Stock Processing
Sereen 19 — Revaluations Reminder
Cash and Stock Declarations ...
Sereen I ~ Shared SU Cash Declaration Report.
Sereen 2 — Individual SU Advice......
Sereen 3 — List SU Declarations...
Sereen 4 —No Declarations Advice
Sereen 5 — No Variance Message .....
Sereen 6 ~ Advice Variance.
Sereen 7 — Display Variance.
Sereen 8 — Variance Report Dialogue
Sereen 9 — Variance Report Reprint Dialogue
Screen 10a ~ Identify Shared SU Declaration...
Transaction Corrections
Screen 13 ~ Transaction Correction Check,
Sereen 14 — List Transaction Corrections
Sereen 15 —No Outstanding Transaction Corrections
Sereen 16 — Display Transaction Correction .....
Sereen 16b — Display Transaction Correetion Options
Sereen 16a — Display Locked Message...
Sereen 17 — Invalid Transaction Correction
Sereen 18 — Transaction Correction Report Criteria...
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 7 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: ul
September 2004
FUJ00090247
FUJ00090247
1.0 Introduction
This document is one of a set of three documents that describe the changes to the Horizon
User Interfaces resulting from the introduction of Impact Release 3 at the Post Office counter
(at BI3 $80). Each of the three documents covers a distinct set of requirements that are
documented in the high-level process models within the Conceptual Design EA/CDE/002
Each process within the requirements document is depicted by a reference beginning with the
letter ‘A’. ‘The requirements that have an impact on the Graphical User Interface, Reports or
Receipts are documented below:
1.1 Report Production
This is covered in EA/FS/011 - Impact Release 3 - Report Production User Interface which
covers the following topics:
* A4.1.2.2 Produce Periodic Summaries
‘Changes to the production of the office summary reports (with cut-offs). New reports,
removed reports and changes to report selection criteria,
* A4.1.2.3 Produce Sales Report to Assist Remuneration Check
New functionality around the entry and validation of reporting criteria.
* 4.1.2.6 Produce Other Horizon Reports
Changes to report layouts as a result of changes to the management of Stock and
changes associated with the menu hierarchy in regard to additional and removed reports.
* A4.1.7.1.3 Review Stock Held Across Branch
‘Changes incurred to the Office Snapshot Report
+ Report Reprints — (Identified in section 20.19 within EA/CDE/002)
1.2. Declaration, Correction and Revaluation
This is covered by this particular document and covers the following topics:
* 4.1.5.1 Receive Automated Message
‘Changes to the Logon process related to the presence of outstanding Transaction
Corrections.
* 4.1.5.2 Handle Transactions Corrections
Selection and processing of Transaction Corrections.
* 4.1.6.1 Compare Generated with Actual Cash Held for Stock Unit
Cash Declarations and Cash Variance identification for both Individual and Shared Stock
Units.
* 4.1.6.2 Create Variance Report
‘Menu, Dialogue and Report format for the Cash Variance Report.
+ A4.1.6.3 Make Good or Hold Any Cash Variance & A4.1.7.4 Make Good any Outstanding
Variances
‘Menu items and dialogues associated with the recognition and resolution of Cash
Variances.
* 4.1.7.8 Stock Revaluation (Stamps)
Messages for user when revaluations are approaching,
1.3. Balancing and Trading Statement Production
This is covered in EA/FS/013 - Impact Release 3 - Balancing and Trading Statement
Production User Interface which covers the following topics:
Formatted
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 8 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/O12
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049!"
September 2004
FUJ00090247
FUJ00090247
+ A4.1.7.2 Produce Trial Balance & 4.1.7.5 Produce Final Balance
Dialogue for order and content of warnings around new roll-over constraints. This will
include all changes associated with both Individual and Shared Stock Unit period rollovers
as well as changes to the Office Rollover process.
+ A4.1.7.6 Produce and Confirm Trading Statement
The report layout of the of the new Trading Statement and dialogues associated to the
rollover confirmation
1.4 Scope
This document describes the changes to the flow of activities, screen displays and prompts,
and report/receipt layouts at the counter a result of the introduction of Impact Release 3. This
document shall limit that description to those items listed under section 1.2 above.
‘The primary purpose of the flow charts in this document is to define the User Interface, and in
some cases, to define the sequence of screens displayed. They are not intended to be
definitive statements of the low-level design of the counter application.
This is a delta document that only describes changes incurred as a result of the
implementation of Impact Release 3. This document does not intend to narrate any part of the
system that exists at Release $75 and which remains unchanged as a result of Impact Release
3.
This document covers all aspects of the timeliness of change to the User Interfaces as a result
of the necessity to migrate the counter functionality across more than one migration boundary.
Itis felt that standard dialogues that show progress (for example: ‘Print in progress’) or show
failure of peripherals would simply confuse the readability of this document. Therefore, not
all of the possible error or exception conditions are shown or described within the diagrams
and dialogues within this document.
1.4.1 DP Cross Reference
‘The scope of this document can be further defined by cross-reference to the Impact Release 3
Design Proposal EA/DPR/004. ‘This document covers the following sections of the Design
Proposal:
DP UIDP Section I Section Heading
Section
25.14.24 I 2.4.1.1 Remittances and
Transfers
25.1.423 I 24.1.2 and ‘Stock Revaluation Messages for user when
44 revaluations are approaching
25.1.2 2.1.2, 2.2, 23, I Changes to Cash/Stock
3.3 and 4.2 Declarations and
Handling Variances
25.161 I 2.1.26 and ONCH Run for Cash Declaration Check
42.13 Yesterday
25.163 I 2.1.3.1 and Outstanding ‘Check for outstanding Transactions
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 9 of 62
FUJ00090247
FUJ00090247
Impact Release 3 - Declaration, Correction and Ref: EA/IFS/(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE, Date: 31-August-049""
September 2004
434 ‘Transaction Corrections I at Logon
2517 I24,34and I Process Transaction I Includes Transaction Correction
43 Correction Reports
1.4.2 Migration Points
The migration to the new dialogues at Release $80 will occur at three points.
a The first point occurs when the counter software and associated reference data is
distributed and made available to the Branches. With reference to TBA, this
migration point is referred to as “Point 20”
a The second point occurs when the final cash account is produced for the CBDB
accounting system and will have an effect on the Menu Hierarchy as well as incurring
some changes to the number and type of suspense products. With reference to TBA,
this migration point is referred to as ‘Point 30°
a The third point occurs when the final cash account occurs at the Branch and this phase
incurs the majority of the changes described within this document. With reference to
TBA, this migration point is referred to as ‘Point 50”
1.5 Structure of this document
This document is structured as follows:
Section 2 provides the list of new or changed User Interfaces that are within the scope of this
document. Where the dialogue involves more than one Screen (alternatively known as
‘Form’ or “Tablet’), then there is a top-level flow chart that depicts the interactions and routes
between the Screens.
Section 3 provides the layout of the Office and Customer Receipts and Reports that are new
or have changed and are within the scope of this document.
Section 4 shows the Screen layouts for any Screens that are new or have been impacted by the
changes within the scope of this document.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 10 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049," i}
September 2004
2.0 Graphical User Interface Design
The transaction flows in this section describe the points at which screens are displayed to the
Clerk. Although automated processes are shown within the diagrams, they are for clarity only
and do not attempt to fully or accurately show the underlying logic of transaction processing.
The Screens are used to inform and prompt the Clerk at appropriate steps in the process of
each transaction.
2.1 Overview
This document describes the User Interfaces that are required to support Declaration,
Correction and Revaluation. In summary, this includes:
a Stock Revaluation
a Cash Declaration and Cash Variance Check
a Cash Variance Report
a Stock Declaration (No change)
a Cash Declaration Logon Reminder
a Transaction Corrections Logon Reminder
a Process Transaction Corrections
a Transaction Corrections Report
2.1.1 Stock Processing
This section covers the changes necessary to support the processing of stock by volume rather
than by value. It also describes the impact of merging the distinction between value and non-
value stock. All changes to the stock processing described in this section will be
implemented at migration Point 50.
2.1.1.1 Remittances and Transfers
‘The $75 stock remittances and transfers functions generally require volumes to be entered for
stock movements. However, the existing system is capable of handling remittances by value
or by volume. No change is therefore required to the User Interface mechanisms.
2.1.1.2 Stock Revaluation:
The stock revaluation function is no longer required since stock will be handled by volume
rather than by value. However, the existing mechanism of alerting the postmaster of
imminent product revaluations will be retained. This mechanism informs the user of
revaluations at logon, the message that appears will be modified as described in section 4.1.1
‘The mechanism by which stock revaluations were invoked is via the menu hierarchy
(Transactions/Reval-Up, Transactions/Reval-Down). These menu items will be removed as
shown SD/SPE/022 in section “TRAN L2/S1 Transactions’
‘The Counter Daily Revaluation Slip will also be no longer required. ‘This will be removed
(Refer to Section 3.1).
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 11 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EA/IFS/(012
Revaluation User Interface
User Interface Design Proposal 631.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049{" i}
‘September 2004
‘Note: removal of the stock revaluation will deny access to the revaluation of Exceptional
Products (EA/DPR/004 section 2.5.1.1.2.4) and these products will therefore have no
mechanism for revaluation.
Refer to EA/DPR/004 section 2.5.1.1.2.3.
2.1.1.3 Merging Value and Non-Value Stock
It is expected that non-value stock will be changed, via reference data, to appear as
value/volume stock. Alternatively, the non-value stock will be retired as a stock-type
product. However, the requirements for how non-value stock will be processed is not fully
defined in either EA/CDE/002 or EA/DPR/004. There are two options considered in this
document:
1. Ifnon-value stock is retired as a stock product, then no stock processing will be
required within the system and it will be removed.
2. Ifnon-value stock is to be converted to value/volume stock, then the non-value stock
processing will be retired and new menu items will be required to enable these
products to be remitted in/out and transferred out.
Since there are no specific requirements then it is assumed that all Non-value stock
processing functionality will be removed. This involves the removal of the following:
Menu items:
F4/F11 — Non-value stock Declaration (refer to SD/SPE/022 section ‘SBAL
4 Stock Balancing’)
F8/E2 — Confirm Non-Value Stock (refer to SD/SPE/022 section ‘OBAL
1.2/S6 Office Balancing’)
FI/E3/FS/F3/F16 — Remit-Out ADC Non-Value Stock (refer to SD/SPE/022
section “[XFR/REMS L5/S21 Stock’)
Rollover Checks
Since Non-Value stock will no longer be managed by the Horizon system, the
checks for completed Non-Value stock declarations at Stock Unit rollover will
be removed.
Reporting:
All Non-Value Stock Reports will be removed (refer to section 3.2)
ie Ch ek eae haan He ia
i a
# Prop!
Refer to EA/DPR/004 section 2.5.1.1.3
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 12 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS(012
Revaluation User Interface
User Interface Design Proposal 031.0
COMMERCIAL IN-CONFIDENCE ul i}
‘September 2004
2.1.2. Changes to Cash/Stock Declarations and Variance Handling
This section covers the requirements for the removal of the daily Overnight Cash Holding
(ONCH) declaration and the replacement of this with a daily cash declaration and daily cash
variance report, It also describes the new functions for the processing of cash variances,
This section covers all changes to the User Interface as a result of implementing the design
stated in section 2.5.1.2 of EA/DPR/004. All of the changes described within this section will
be implemented at migration Point 20.
2.1.2.1 Changes to Cash Declarations
‘The requirement for Overnight Cash holdings on a daily basis will be replaced by the
requirement to make Cash Declarations on a daily basis. The dialogues for both these
processes are the same, however the underlying functionality is different. The existing
ONCH declaration button will therefore be replaced with the Cash Declaration button (refer
to SD/SPE/022 section ‘REPS L3/S8 Counter Daily’).
It is not expected that the word ‘Discrepancy’ be changed to ‘Variance’ within the Cash
Declaration process.
‘The only-change-4o-the Cash-declaration-process-is-duringFor a Shared Stock Unit
declaration:, -Aa new button will appear on the Report Dialogue that appears at the end of the
declaration process that will allow the user to proceed directly to the ‘Check For Variances’
function described in section 2.1.2.2. The new screen design is shown in section 4.2.1
Where an amount has been Made Good or Excess Cash has been removed from a Stock Unit
(or from a Declaration Id in the case of Shared Stock Units) since the last declaration, then the
net amount Made Good/Removed will be presented to the user. This will be presented on the
declarations screen that is used to enter the denominational amounts of cash. The amount
Made Good or Removed will be presented in the denominational picklist heading. This
heading reads ‘Declare Cash on Hand’ at $75, this will be changed as follows:
If an amount has been made good since the last declaration the title will read:
Declare Cash (£xxxxx.xx Made Good}
ss cash has been removed since the last declaration the title will read:
Declare Cash (£xxxxx.xx Removed)
Ifno adjustment has been made to the declared amount then the title will read:
Declare Cash
Ifexe
Ina shared stock unit where a new declaration is being made, or in an individual stock
unit where this is the first declaration, then the title will read:
Declare Cash
Refer to EA/DPR/004 section 2.5.1.2.1
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 13 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049{" i}
September 2004
2.1.2.2 Check for Variances
This is a new function that will be available to Shared Stock Units and will be invoked from a
new button ‘Cash Variance’ on the Stock Balancing menu (refer to SD/SPE/022 section’
SBAL L2/S4 Stock Balancing’) or from the Report Dialogue as described above.
The new process will act in a similar manner to the existing Stock Unit balancing function
and will present a list of all cash declarations made within the current Stock Unit.
Acceptance of the list will cause the system to check the sum of the declared cash values with
the system calculated Stock Unit cash value. The user is then informed whether there is a
variance and, if so, the value (+/-) of the variance. Refer to section 2.2 for a description of the
dialogue flows.
This new function may also be invoked from the Cash Declarations report dialogue (refer to
2.1.2.1)
Refer to EA/DPR/004 section 2.5.1.2.1.1
2.1.2.3. Cash Variance Report
A new report will be available that will show all declarations made by each Stock Unit and
any variances that exist between the declared value and the system-calculated value.
‘The new report will be invoked by an additional button on the Office Daily reporting menu
(refer to SD/SPE/022 section ‘REPS L3/S9 Office Daily’). The report will show the data for
the current trading month and week. Refer to section 3.3 for report layout and description.
A re-print function will be made available that will allow re-prints of previous trading
month/weeks. The reprint will be invoked from the Report Reprint Menu (SD/SPE/022
section ‘ REPS L3/S11 Reprints’ and section 4.2.9)
Refer to EA/DPR/004 section 2.5.1.2.2.
2.1.2.4 Cash Variance Processing
Ifa variance exists within any Stock Unit, amendments can be made by either adding cash to
the till or by removing cash from the till until the value of the till and the system-calculated
figures are in agreement.
There is a requirement that these activities are logged within the system and two new
functions will be provided to either Make Good a Loss or Remove Excess Cash. These
functions will be invoked by menu buttons on the stock balancing menu described in
SD/SPE/022 section ‘SBAL L2/S4 Stock Balancing”
The user interface is defined in more detail in sections 2.3, 4.2.10 and 4.2.12.
Refer to EA/DPR/004 section 2.5.1.2.3.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 14 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049,"
September 2004
FUJ00090247
FUJ00090247
2.1.2.5 Stock Declarations and Variances
The existing mechanism for stock declaration and adjustment will be retained. Although
most stock will now be handled by volume rather than by value this has no impact on the
mechanisms by which declarations and adjustments are performed.
Also, although the optional “Loss Price’ may be used when adjusting stock levels, the user
interface is not visibly different to the existing system. However the price displayed
alongside a product will be the Loss Price rather than the Sale Price (if the product reference
data has a loss price specified against it).
Refer to EA/DPR/004 section 2.5.1.2.4.
2.1.2.6 Cash Declaration Check
‘The S75 counter performs a check at Logon that the ONCH declaration for the current Stock
Unit has been performed for the previous Trading Day. If the ONCH declaration had not
been performed for the previous Trading Date, a message will be displayed to inform the
clerk that an ONCH declaration must be made and the clerk is forced into the ONCH Declare
Cash dialogue.
At S80, the ONCH declaration is removed and replaced by Cash Declarations. At Logon, a
check will be made to determine whether a Cash Declaration has been performed for the
previous Trading Day. If the Cash Declaration had not been performed for the previous
Trading Date, a message will be displayed to inform the clerk that a Cash Declaration is
outstanding. This dialogue will force a Cash Declaration to be made in the same manner as
the ONCH declaration.
Since the logical sequence of the Logon process has not changed (the Cash Declaration
reminder has simply replaced the ONCH reminder), then this document will constrain itself to
the description of the reminder screen only and will not re-describe the full logon process (see
section 4.2.13).
This process will change during migration Point 20.
Refer to EA/DPR/004 section 2.5.1.6.1.
2.1.3 Processing Transaction Corrections
‘This section covers the requirements for the display, selection, processing and reporting of
automated Transaction Corrections. All of the dialogues within this section are only
applicable to those Roles who can do an Office Balance (ie Manager, Supervisor, Migrate,
Auditor and Auditor - Emergency Manager). This will be controlled using normal Menu
Security functionality and reference data.
This section covers all changes to the User Interface as a result of implementing the design
stated in section 2.5.1.6.3 and 2.5.1.7 of EA/DPR/004.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 15 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049{"
September 2004
FUJ00090247
FUJ00090247
2.1.3.1 Transaction Correction Check
At Logon, a new check will be made to determine whether there are any outstanding
Transaction Corrections. This new check will be performed after the check for Cash.
Declarations described in section 2.1.2.6 and will be the last check to be made as part of the
Logon process.
If there are outstanding Transaction Corrections a message will be displayed to inform the
Postmaster that one or more Transaction Corrections are outstanding. This dialogue will
allow the Postmaster to choose whether to process the Corrections now or will allow the
Postmaster to continue with the Logon process. This check will only be made for users of
role Manager or Supervisor
Since this new dialogue is simply an additional check within an existing process, then this
document will constrain itself to the description of the reminder screen only and will not re-
describe the full logon process (see section 4.3.1)
This check will be implemented as part of migration Point 50.
Refer to EA/DPR/004 section 2.5.1.6.1.
2.1.3.2 Selecting and Processing Transaction Corrections
A new dialogue will be introduced to process automated Transaction Corrections that are
distributed to Branches by the new financial system. The dialogue will be invoked as a result
of Transaction Corrections being outstanding at the point of user logon or by touching the
appropriate menu button (SD/SPE/022 section ‘HKPG L3/S5 Housekeeping’).
A list of all outstanding transaction corrections will be presented to the user. A transaction
correction may then be selected and the detail of the correction may then be viewed. Within
the transaction correction detail screen, a number of options will be made available for the
user to choose from in order to action the transaction correction. In certain circumstances, a
further options screen will be presented (see section 4.3.5). In addition, a cancel button will
be available should the user decide not to process the transaction correction at this time.
Refer to section 2.4 for a diagram of the process flow and sections 4.3.4 and 4.3.5 for screen
layouts and descriptions.
Refer to EA/DPR/004 section 2.5.1.7.1 and 2.5.1.7.2.
2.1.3.3. Reporting on Transaction Corrections
Two new buttons will be available on the main reporting menu that will invoke the
transaction corrections reports (refer to SD/SPE/022 section ‘REPS L2/S2 Reports’). One of
the buttons will be used to invoke the Outstanding Transaction Corrections report and the
other will be used to invoke the Processed ‘Transaction Corrections report. Each will invoke a
dialogue that will request the start and end dates to define the scope of the report (refer to
4.3.8)
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 16 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref:
Revaluation User Interface
User Interface Design Proposal Version:
COMMERCIAL IN-CONFIDENCE Date:
EA/IFS(012
0.31.0
Jo
September 2004
FUJ00090247
FUJ00090247
2.1.4 Conventions used within the dialogue flowcharts
‘The flowcharts within this document use the conventions described below.
Symbol Description
Terminator
( Indicates the start or completion of a
process flow
Process
Represents a processing function,
Decision
Represents a decision or switching function in a
flowchart. This may represent either a system or
‘manual decision.
Display
Represents displayed data, such as data, display panels
and prompts on a monitor sereen,
Multiple Process Container
Represents a common set of processes and displays
that are described in detail within another section
of the document
[ Document
Represents readable data, such as printed output. Where it s a print, the
standard options around print failure come into play and as a last resort,
print preview will be used to allow a manual transcription of the print.
Off Page Connector
Represents a flow of information that is continued on a separate page.
Solid lines indicate communication between the elements of the flowchart.
> _ The arrow indicates the direction of the communication,
Figure 1: Flow chart conventions used in this document
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Page: 17 of 62
isu Services Impact Release 3 - Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049{"
‘September 2004
FUJ00090247
FUJ00090247
2.2. Check For Variances
Pre conditions
‘There should not be any other transaction in progress since the check for variances
relies on no trading being performed between declarations and the check for variance
function. However the system
© will not check/prohibit a swapped session on this terminal
© will not check/prohibit anyone else who is logged in and attached to this SU
© will not check for any activity since most recent declarations
It should be made clear that, in the above circumstances, the variance may not be
accurate if there are transactions in the Stock Unit on a till after it has made a
declaration.
Post conditions
None
Description
This session is invoked by either a menu button (refer to SD/SPE/022 section ‘SBAL L2/S4
Stock Balancing’) or from the Shared Stock Unit cash declarations report dialogue (refer to
4.2.1).
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 18 of 62
FUJ00090247
FUJ00090247
Fujitsu Services _Impact Release 3— Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal 631.0
COMMERCIAL IN-CONFIDENCE 31-August-0490" _[ Formatted
September 2004
[Formatted
I
I
I
The retrieve latest declarations function will retrieve the last declaration for each till id within
the SU regardless of when it was made. This is the current functionality for the Discrepancies
function.
The dialogue flowchart does not show ‘in-progress’ screens. The final deliverable will
display a “checking for discrepancies” message after screen 3 before showing 5 or 6. This
message is displayed temporarily during the calculation of the discrepancy.
COMMERCIAL IN-CONFIDENCE Page: 19 of 62
© 2004 Fujitsu Services
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049," i}
September 2004
2.3. Make Good Variances
Pre conditions
None
Post conditions
Update complete, or Update cancelled
Description
Ifa cash variance is reported for any individual Stock Unit, the clerk may opt to either Make
Good by adding money to the Till or to remove the Excess Cash. Two new buttons allow one
of either of these options to be declared and recorded (SD/SPE/022 section ‘SBAL L2/S4
Stock Balancing’). If either one or other of these buttons is chosen more than once since the
last declaration, then a warming will be given that cash variance has already been processed.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 20 of 62
Fujitsu Services
Impact Release 3 — Declaration, Correction and
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
Version:
Date:
EA/IFS(012
0.31.0
Jo
September 2004
FUJ00090247
FUJ00090247
_—[Formatted
Previous Make
rAaice I
Screen tt)
—
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 21 of 62
FUJ00090247
FUJ00090247
Impact Release 3 - Declaration, Correction and Ref: EA/IFS/(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049{"
‘September 2004
2.4 Select and Process Transaction Corrections
Pre conditions
None
Post conditions
Transaction complete, or Transaction cancelled.
Description
This function is invoked from either the logon check or by touching the relevant menu button.
A list of outstanding transaction corrections is presented to the user from which one may be
selected for detailed display and processing. Up to three options may be presented to the user
depending on the type of transaction correction. A further option will allow the user to exit
without processing the correction. Refer to the individual screens described in section 4.3 for
further details.
Select and Process Transaction Corre:
tepencrecr )
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 22 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049{" i}
September 2004
3.0 Reports and Receipts
This section depicts the layout of the Reports and Receipts following the introduction of
requirements introduced by the Impact Release 3 Conceptual design (Fujitsu reference
EA/CDE/002) and constrained to the functionality described in section 1.2.
It should be noted that the examples below attempt to reflect the final formats of the Reports
and Receipts although changes to layouts depicted below may or may not be incurred by other
influences or requirement changes. The definitive statement of Report and Receipt layout is
documented in SD/DES/005.
3.1 Counter Daily Revaluation Slip
Since stock is to be treated by Volume, the mechanisms for revaluation and the reporting of
revaluations is no longer required. This report will be removed at migration Point 50.
[ Note: This assumption may be incorrect if some stock products still require revaluations _I
3.2 Non-Value Stock Reports
Since Non-Value Stock will no longer be managed by the Horizon system, the following
Non-Value Stock reports will be removed.
a Non-Value Declaration for Shared SU
a Non-Value Declaration for Individual SU
a Non-Value Confirmation Report
These reports will be removed at migration Point 50.
3.3. Cash Variance Report
3.3.1 Purpose
This is an office report and provides a comparison between declared values of cash with the
derived values of cash across all stock units within the Branch. The total value of
adjustments within the branch and number of transaction corrections made complement the
figures to provide an office-wide picture of the Branch cash position.
3.3.2 Frequency
Manually invoked on a daily basis from the Office Daily menu (Refer to SD/SPE/022 section
‘REPS 1.3/S9 Office Daily’). Reports may be reprinted for previous weeks by using the
Report Reprint menu button (Refer to SD/SPE/022 section ‘REPS L3/S11 Reprints’)
3.3.3 Notes
Optional
Details of the cash declarations made within each Stock Unit across a period.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 23 of 62
Fujitsu Services Impact Release 3 - Declaration, Correction and
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
Version:
Date:
EA/IFS/012
0.31.0
9
September 2004
FUJ00090247
FUJ00090247
Filed locally.
3.3.4 Sequence
Listed in Stock Unit alphabetical sequence within each portion of the report that has stock
unit content,
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Page: 24 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal 0.31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049"
September 2004
3.3.5 Layout and Example Content
1 2 3 4 5 6 g 8 1 2 3
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012
FUJ00090247
FUJ00090247
(Formatted
Feltham Post Office FAD 123456K Page 1
11:42 21/06/2004 -* Reprint for week ending 23/06/2004 *-
Cash Variances Report - Office Copy
B ‘Thursday Friday Saturday Sunday Monday Tuesday _ Wednesday
Dates 16/06/2004 17/06/2004 18/06/2004 19/06/2004 20/06/2004 21/06/2004 22/06/2004 23/06/2004
CASH VARIANCES
SU AA x 0.00 x 0.00 0.00 0.00
SU BB 50.00 60.00- 40.00- 0.00 2.00 0.00
su cc 0.00 0.00 0.00 0.00 0.00 0.00
su DD 0.00 0.00 0.00 40.00- 0.00 x
Total x 60.00- x 40.00- 2.00 *
DERIVED FIGURES
SU AA x 700.00 x 700.00 700.00 300.00
SU BB 50.00 310.00 190.00 200.00 98.00 200.00
su cc 0.00 350.00 450.00 500.00 200.00 250.00
su DD 0.00 150.00 200.00 190.00 200.00 x
Total x 1510.00 x 1590.00 1198.00 x
DECLARED FIGURES
SU AA (Shared) x 700.00 x 700.00 700.00 300.00
SU BB (Individual) 200.00 250.00 150.00 200.00 100.00 200.00
sU CC (Shared) 400.00 350.00 450.00 500.00 200.00 250.00
SU DD (Individual) 100.00 150.00 200.00 150.00 200.00 x
Total x 1450.00 x 1550.00 1200.00 x
T 2 3 a 5 G a 3S T a 3
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012
Continued on next page..
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE,
rage: 25 of 62
Fujitsu Services Impact Release 3 - Declaration, Correction and
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
Versi
Date:
EA/IFS/012
0.31.0
31-August-049""
September 2004
Continued from previous page...
u
1 2 3 5 6
123456789012345678901234567890123456789012345678901234567890123456789012345678:
8
90:
1 2 3
1234567890123456789012345678901234567890123456789012
FUJ00090247
FUJ00090247
(Formatted
‘SU BREAKDOWNS
SU AA
Decl. ID 01 100.00 200.00
Decl. ID 02 x 250.00
Decl. ID 03 200.00 100.00
Decl. ID 04 250.00 150.00
su cc
Decl. ID 01 400.00 350.00
KNOWN DISCREPANCIES
Local Suspense 0.00 0.00
Other Suspense 100.00 100.00
ADJUSTMENTS TO PHYSICAL CASH ON HAND
Total 0.00 60.00
TRANSACTION CORRECTIONS
Number Processed ° °
Number Outstanding ° 1
300.
350.
400.
450.
40.
0.
0.
00
00
00
00
00
00
00
1
°
250.
200.
150.
100.
500.
jo END OF REPORT ***
100.
150.
200.
250.
200.
2°
50.
00
00
00
00
00
-00
-00
100.00
200.00
x
250.00
0.00
0.00
7 2 3 a 5 6 7g 8 T 2 3
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012
The data shown in the example is illustrative only —
the exact text can change, and so differ from that in the example.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE,
rage: 26 of 62
Fujitsu Services
Impact Release 3 — Declaration, Correction and
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE,
Ref: EA/IFS/012
Version: 0:31.0
Date: 31-August-049{"
‘September 2004
FUJ00090247
FUJ00090247
Field Name Line I Character I Length I Contents/Notes
No. I Positions
Heading Section
Reprint Indicator 03 93-132 39 Shown only for report
re-prints
Days 0s 32-41 10 Showing the day
45-54 descriptions above the
58-67 respective dates
71-80
84-93
97-106
110-119
123-132
Dates 06 32-41 10 Showing the date
45-54 related to the
58-67 declarations
71-80
84-93
97-106
110-119
123-132
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 27 of 62
Fujitsu Services Impact Release 3 - Declaration, Correction and
Revaluation User Interface
COMMERCIAL IN-CONFIDENCE,
User Interface Design Proposal
Ref: EA/IFS/012
Version: 0:31.0
Date: 31-August-049,"
FUJ00090247
FUJ00090247
Field Name Line] Character I Length I Contents/Notes
No. _ I Positions
Cash Variances, Derived
Figures and Declared Figures
Section
su 08-24 I 1-19 19 Text ‘SU followed
by the Stock Unit Id
followed by the word
“(Shared)’ or
‘(individual)’
depending on the
stock unit type
Variance 08-24 I 31-42 2 Showing the
44-55 variances, declared
21-68 and derived values for
a each stock unit, by
83-94 day, across an eight-
96-107 day period
109-120
122-133
Total 08-24 I As for 12 Daily total for all
Variance stock units
SU Breakdowns
os 26-32 I 1-6 6 Text ‘SU followed
by the Stock Unit Id
Declaration 27-32 I 1-11 ul Text ‘Decl. ID *
followed by the
declaration Id
Declared Values 27-32 12 Showing the declared
value for each
declaration within a
shared stock unit, by
day, across an eight-
day period.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 28 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/O12
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049," i}
September 2004
Field Name Tine I Character I Length I Contenis/Notes
No. I Positions
Known Discrepancies and
Adjustments
luce 3437 I 31-42 2 Showing the
a 44-55 Discrepancy and
57-68 Adjustment value, by
70-81 day, across an eight-
83-94 day period
96-107
109-120
122-133
Transaction Corrections
haoeaad 39-40 I 31-42 2 Showing the quantity
44-55 of Transaction
57-68 Corrections processed,
70-81 by day, across an
83-94 eight-day period
96-107
109-120
122-133
3.3.6 Description
3.3.6.1 General
Negative values will be depicted by the use of a ‘“-* symbol as a suffix to the number. Ie:
456.78-.
3.3.6.2 Reporting Period
The report shows up to eight days of data. ‘The first and last date-column of the report will
always be a Wednesday with the first column showing the Brought Forward figures from the
previous week.
The report does not attempt to align to a Trading Period. The report simply shows the cash
declared, derived and variances for the current week (or previous weeks for re-prints)
‘The report will not show any data for the current day since the calculation of the figures is
performed by the End of Day processing.
oles_Ehists Likely to oh He . POLAK howe
ish Soman CR sie hannad ooh his
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 29 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049{"
September 2004
FUJ00090247
FUJ00090247
3.3.6.3 Variances, Derived and Declared Figures and SU Breakdowns Declarations
‘The Cash Variance for any day is the difference between the Derived and Declared figures for
each Stock Unit.
The derived figures represent the system-calculated cash total at the time the declaration was
made. The time of declaration for a Shared Stock Unit is assumed to be the time when the
Check for Variances process was performed. If trading has occurred between the time the
declaration has been made and the time the Check for Variance function is executed, then it is
expected that there will be a variance between the declared and the derived figures
‘The declared figures are the values declared on the day, or are the values declared on the
previous day if the stock unit was not logged-on in the day. For Shared Stock Units, the
declared figures are the sum of the declarations of the individual Declaration Ids (tills).
The SU Breakdown section shows the individual Declaration Ids within each of the Shared
Stock Units
Declarations made as part of the log-on process (including those done by an associated Check
for Variances function) will be recorded as having taken place “yesterday”.
3.3.6.4 Known Discrepancies
Two lines show the total values of the ‘Local’ Suspense Account and the sum of the total
values for all ‘Other’ suspense accounts.
3.3.6.5 Adjustments to physical cash on hand
This section shows the total values of all adjustments made on the day. Adjustments are the
nett values recorded as ‘Made Good’ or ‘Excess Cash’ as described in section 2.1.2.4
3.3.6.6 Transaction Corrections
This section reports on the number of Transaction Corrections that have been processed on
each day of the report and the number of Transaction Corrections Outstanding on each day of
the report.
3.3.6.7 Missing Declarations (‘x’)
Where a stock unit has not logged-on on a Trading Date then the figures for the previous day
are used today (or “x” where the previous day shows *x’).
‘An ‘x’ will be shown in a cell of the report if a declaration has not yet been completed for the
Stock Unit on the day in question.
For Shared Stock Units, an ‘x’ will be shown against each Declaration Id for which a
declaration has not been made on the day (in the SU Breakdowns section). When the Check
for Variances function has been run, then the most recent previous declarations will be
brought forward for those tills that have not yet declared and therefore no ‘x’ will be shown
against that Stock Unit. Also, an ‘x’ will appear on the Variance, Derived and Declared
sections of the report until the Check for Variances function has been performed for the
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 30 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAMIFS(012
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049," i}
September 2004
shared stock unit for that day. If the Check for Variances function is not executed on any day,
then the report will always show *x’ against the Variance, Derived and Declared sections of
the report for that day.
An ‘x’ will be shown on any ‘Total’ line where there is an ‘x’ present in the column
immediately above it.
3.3.6.8 Pagination
No special pagination rules will be enforced except that a new page will occur once alll lines
have been used on the previous page. There are no obvious rules for pagination since the
number of stock units per Branch will vary as will the ratio of shared:individual stock units
and the number of clerks per shared stock unit.
Following a page-feed, the heading section will be repeated in full
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 31 of 62
su Services Impact Release 3 — Declaration, Correction and
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
Ref:
Version:
Date:
EA/IFS/012
0.31.0
9
September 2004
FUJ00090247
FUJ00090247
3.4 Transaction Corrections Reports
3.4.1 Purpose
There are two transaction correction reports. One shows those transaction corrections that are
still outstanding and the other shows those transaction corrections that have been processed.
They both show transaction corrections that were received between the two dates specified
within the report criteria.
3.4.2 Frequency
Ad-hoc
3.4.3 Notes
Details of the transaction correction.
No need to retain.
3.4.4 Sequence
Listed by order of receipt from POL Financial System.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Page: 32 of 62
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EAMIFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE, Date: ——-34-August-049!"
September 2004
3.4.5 Outstanding Transaction Corrections Layout
1 2 3 4 5 6 1 a 9 10 1 2 3 4
123456789012345678901234567890123456789012345 6789012345 678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345
Feltham Post Office FAD 123456X Page 1
11:42 08/04/2004 7p 12
outstanding Transaction Corrections Report - Office Copy
Allowed Options
Date —_— Reference Affected Credit/ Amount Quantity Client -
Received Product Tnvoics Reference
18/03/04 N123456789012345678 123456789012345678901234 _ CRM _123456789.12 12345678 1234567890123456 12345678901234 12345678901234 12345678901234
‘The description will take up the remaining characters on the right-hand side of the page and will wrap on either a space or
hyphen. Again, the I character will be interpreted as a new-line character
19/03/04 N000003242099940000 Cash inv 554.23 TX5455PY5544 Accept Now _— Settle Centrly Seek Evidence
The description will take up the remaining characters on the right-hand side of the page and will wrap on either a space or
hyphen. Again, the I character will be interpreted as a new-line character.
‘This example shows three lines of text.
‘++ END OF REPORT *#+
7
z J 5 T z J
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012 3456789012345,
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE, Page: 33 of 62
FUJ00090247
FUJ00090247
(Formatted
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal 0.31.0
COMMERCIAL IN-CONFIDENCE Date: <a
September 2004
Field Name Tine I Character I Length I Contents/Notes
No. _I Positions
Date Received 08 1-8 8
Reference 08 10-28 19 The reference number is prefixed by
the iteration flag that will either be
<N’ (new) or ‘E’ (evidence provided)
Affected Product 08 30-53, 24 Product Long Name
Credit/Invoice 08 57-59 3 Indicates credit note or
‘Amount 08 I 62-73 12 invoice CRM=Credit note,
IN’ Voic’
tit 08 75-82 8
Quantity £s and Pence
Client Reference 08 84-9899 16
Allowed Options 08 101- 14
443144
This will contain up to 3 options that
Descripti 10-11 126
— 30-145 ” I are described below.
The maximum number of characters
within the description will be 500.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 34 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version:
COMMERCIAL IN-CONFIDENCE Date: 31-August-049"
September 2004
3.4.6 Processed Transaction Corrections Layout
1 2 3 4 5 6 1 a 9 1 2 3 4
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345
Feltham Post Office FAD 123456x Page 1
11:42 08/04/2004 ‘TP 12
Processed Transaction Corrections Report - Office Copy
Date Date outcome Reference Gredit/ Affected Settlement Amount Quantity Client
Received Processed Invoice Product Product Reference
18/03/04 22/03/04 12345678901234 N123456789012345678 CRM 1234567890123456 1234567890123456 123456789.12 12345678 1234567890123456
The description will take up the remaining characters on the right-hand side of the page and will wrap on either a space
or hyphen. Again, the I character will be interpreted as a new-line character
18/03/04 22/03/04 Accept Now _N123456789012345678 INV Burglary cash 6789.12 ‘TcPc1236
‘The description will take up the remaining characters on the right-hand side of the page and will wrap on either a space or
hyphen. Again, the I character will be interpreted as a new-line character.
This example shows three lines of text.
**# END OF REPORT ##+
+
z 3 7 5 z
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345
© 2004 Fujitsu Service COMMERCIAL IN-CONFIDENCE, Page: 35 of 62
FUJ00090247
FUJ00090247
(Formatted
Fujitsu Services
Impact Release 3 - Declaration, Correction and Ref: EA/IFS/(012
User Interface Design Proposal
Revaluation User Interface
Version: 0.31.0
COMMERCIAL IN-CONFIDENCE, Date: 31-August-049""
September 2004
FUJ00090247
FUJ00090247
Field Name Tine] Character I Length I Contents/Notes
No. I Positions
DateReceived I 08 I 1-8 8
Date Processed [08 I 10-1897 I 8
Outcome 0s I 20-33 I 14 I This describes the mode in which the
correction was transacted and will be
one of the allowed Options described
below.
Reference 0s I 35-53 19 _I The reference number is prefixed by
the iteration flag that will either be
°N? (new) or “F” (evidence provided)
Creditinvoice fog I sess I 3 Values of CRM=Credit note or,
Affected Product I 08 I 63-78 16 INVelnvoice
Settlement Product I 08 I 80-95 16 Product Medium Name
Amount os Io7-10s I 12 Product Medium Name
Quantity os Ii0-117 I 8 Ss and pence
Client Reference I 08 I 119-134 I 16
Deseription 10-11 I 20-145 I 126
‘The maximum number of characters
within the description will be 500.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 36 of 62
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref:
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
EA/IFS(012
0.31.0
9
September 2004
FUJ00090247
FUJ00090247
3.4.7 Transaction Corrections Additional Information
The Allowed Options on the Outstanding report refer to the possible choices that the clerk
may have when attempting to process a transaction correction, The Outcome on the
Processed report refers to the actual choice made by the clerk when the correction was
processed. These fields on the report may have one of the following values:
Mode Allowed ID_[ Mode Report Text
MG Make Good ‘Accept Now
HS Assign to Centre Settle centrly
EV Request Evidence Seek Evidence
wo Write Off Send To P&l.
‘AN Assign to Nominee Assign To HO
SW Stock Write On/Off _I Stock WO
In addition, if the Transaction Correction failed due to the constraints applied during
processing (due to inconsistent reference data for example), then the Outcome text would be
shown as “Txn Error’._The settlement product would, in this case, be blank.
Both reports show both Amount and Quantity fields. Each transaction correction will have
either an amount or a quantity (but not both). Zero amount or quantity will therefore be
suppressed and shown as spaces.
‘The description will word-wrap if longer than 126 characters and will wrap on a space
character or a hyphen. Vertical bar characters ‘I’ in the text will be treated as line-feed
characters.
‘The headings will be repeated in full at the start of each page.
3.4.8 Pagination
No special pagination rules will be enforced except that a new page will occur once all lines
have been used on the previous page. There are no obvious rules for pagination since the
number of lines of text accompanying each transaction correction may vary widely.
Following a page-feed, the heading section will be repeated in full.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Page: 37 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004
4.0 Screen Layouts
This section depicts the new screens introduced as a result of release $80 and also describes
the changes to existing screens.
Where new buttons are introduced, new icons may be introduced at the discretion of Fujitsu.
Services.
4.1 Stock Processing
4.1.1 Screen 19 - Revaluations Reminder
Revaluation Reminder
Please remember to ensure
that stock volumes are
declared correctly before
revaluation takes place
later this week.
This is an existing screen that appears during the logon process. The text of the message
originally read:
Please remember to ensure that stock volumes and values are declared correctly, and that all
transfers and remittances of affected products are carried out, before Revaluation takes place
later this week.
Since stock will be handled by volume, then the reference to Value stock and to the transfer
and remittance processes is now irrelevant and the new message will read as shown.
MSG232 Revaluation Reminder OK
Please remember to ensure that stock volumes are Touch this button to continue,
declared correctly before Revaluation takes place
later this week
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 38 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/O12
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049," i}
September 2004
(Ifthe text is changing then we need a new message number and a test in the code to display
the correct one depending on migration point).
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 39 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref:
Revaluation User Interface
User Interface Design Proposal Version:
COMMERCIAL IN-CONFIDENCE Date:
EAIFS/012
031.0
FUJ00090247
FUJ00090247
StAugust-049!" _—{ Formatted
September 2004
4.2. Cash and Stock Declarations
4.2.1 Screen 1 — Shared SU Cash Declaration Report
ProducelReport
DeclaredicashmlOfticelcopy,
‘Anew button will appear on the report dialogue that appears following a shared Stock Unit
cash declaration. This button will allow the user to proceed directly to the ‘Check For
Variances’ function described in section 2.1.2.2.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Page: 40 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EAMFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: _31-August-049!"__{ formatted
September 2004
4.2.2: Screen 2 - Individual SU Advice
k Varianc
This check is not required
for Individual stock units.
This screen appears if an Individual Stock Unit attempts to invoke the Check For Variances
function.
MSGxxx Check Variances OK
This check is not required for Individual stock Touch this button to continue.
units.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 41 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00090247
FUJ00090247
Ref: EA/IFS/012
O=81.0
Date: 31-August-049)" _—[ Formatted
September 2004
4.2.3 Screen 3 - List SU Declarations.
MOUSER TET
This screen presents the latest declarations made for the current Shared Stock Unit. The list
can be inspected to ensure that it is complete and that declarations have been made in a timely
manner. Following inspection of the list, the clerk may exit by touching the ‘Prev’ or
“Desktop” buttons or may continue with the Check for Variances function by touching the
“OK” button.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Page: 42 of 62
Fujitsu Services
Impact Release 3 - Declaration, Correction and Ref: EAIFS/012
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00090247
FUJ00090247
Version: 0.31.0
Date: _31-August-049!"__{ formatted
September 2004
4.2.4 Screen 4 — No Declarations Advice
No declarations have been
made for the current stock
unit.
If no declarations have been made in the current Stock Unit then the above screen will be
displayed. This screen may be reached either during the check for variances function or
during the Make Good or Remove Excess Cash function. Touching Ok will exit the Cheek
forVariances-functionfunction.
MSGrox
No Declarations
No declarations have been made for the current
stock unit,
OK
Touch this button to continue.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE Page: 43 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EAMFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: _31-August-049!"__{ formatted
September 2004 }
4.2.5 Screen 5 — No Variance Message
No Variances
There are no
variances with the
system derived figures.
If there is no variance between the declared cash position and the derived cash balance for
this stock unit then the clerk is presented with the above screen. Touching Ok will exit the
Check for Variances function.
MSGxxx ‘No Variances
There are no variances with the system derived
figures.
OK
Touch this button to continue.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 44 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EAMFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: _31-August-049!"__{ formatted
September 2004 }
4.2.6 Screen 6 — Advise Variance
Gain
Theldeclaration di
match\the system
Continuing Iwill presenta
list of Variances for
Confirmation
If there is a variance between the declared cash position and the derived cash balance for this,
stock unit then the clerk is presented with the above screen. Touching Ok will present the
Clerk with the variance amount.
MSGxxx Confirm Loss/Gain OK
‘The declaration does not match the system derived Touch this button to continue.
figure. Continuing will present a list of variances
for confirmation.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 45 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004 }
4.2.7 Screen 7 — Display Variance
Once the Clerk has acknowledged that a variance exists, they will be presented with the
variance amount.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 46 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and
Revaluation User Interface
User Interface Design Proposal
COMMERCIAL IN-CONFIDENCE
FUJ00090247
FUJ00090247
Ref: EAMFS/012
Version: 0.31.0
Date: _31-August-049!"__{ formatted
September 2004
4.2.8 Screen 8 — Variance Report Dialogue
ProducelReport
Warianices officelCopy
TP: i
Week Ending: 23/06/2004
The variances report is invoked from the Office Daily reporting menu. The clerk will be
presented with the normal reporting dialogue as shown above.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE
Page: 47 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal O=81.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004
4.2.9 Screen 9 — Variance Report Reprint Dialogue
Select Reprint Date
Week ending 05/08/2004
Week ending 12/05/2004
Week ending 26/05/2004
The variances reprint report is invoked from a sub-menu of the report reprints menu (see
SD/SPE/022 section ‘REPS L3/S11 Reprints’). The sub-menu is a standard feature of report
reprints and this example will have the following three buttons:
Select Reprint Date Allows selection of the date from which the report is to start. In
steady-state, five prior dates will be displayed for selection
corresponding to the Wednesday of the five prior weeks.
Display Displays the criteria entered
Continue Displays the report dialogue as shown in section 4.2.8.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 48 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004 }
4.2.10Screen 10 — Enter Amount Made Good or Removed
ii
Amount Remove Exi
Enter Amount
This screen is presented following selection of the menu buttons to ‘Make Good’ or ‘Remove
Excess Cash’. A value to be added or removed from the Stock Unit must be entered.
‘The heading at the top of the right-hand tablet will be one of:
a Remove Excess Cash
a Make Good Cash
This is determined by which menu button invoked the process.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 49 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAIFS/012
Revaluation User Interface
FUJ00090247
FUJ00090247
User Interface Design Proposal O=81.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004
4.2.11Screen 10a — Identify Shared SU Declaration
AAMC \ GCE
This screen is presented following entry of the amount made good or excess removed from a
Shared Stock Unit. The declaration Id (Till number) that is being adjusted must be identified
by touching the relevant declaration id and touching Ok.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 50 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EAMFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: _31-August-049!"__{ formatted
September 2004 }
4,2.12Screen 11 - Previous Make Good Advice
Cash Variances
‘An amount has already been
made good or removed from
this stock unit since the last
declaration.
Touch Continue to enter an
additional amount or Cancel
to cancel.
This screen is presented if the clerk attempts to Make Good or Remove Excess Cash more
than once since the last declaration. Touching the Continue button will provide the option to
continue to enter an additional amount. Touching the Cancel button will cancel the activity
and return the Clerk to the menu.
MSGxxx Cash Variances Continue
‘An amount has already been made good or Touch this button to continue.
removed from this stock unit since the last Gas
declaration.I[Touch Continue to enter an additional
amount or Cancel to cancel. ‘Touch this button to cancel.
eel
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 51 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Versi 031.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004
FUJ00090247
FUJ00090247
4.2.13Screen 12 - Cash Declaration Check
v
Declaration Check
Accash declaration was
not made for this stock
unit at the last end of
day.
Touch Continue to make
a cash declaration.
This screen is presented if the clerk logs-on and a cash declaration has not yet been performed
for the previous trading date. The screen will be presented during the logon process.
‘Touching Continue will continue with the cash declaration process
On logon, a check is made to see whether any Cash declarations were made for the current
Stock Unit "yesterday".
Provided at least one such Cash declaration was made (for the current Stock Unit), the logon
is allowed to continue. If no Cash declarations were made, then the user is forced to make a
declaration as part of the logon sequence.
Note that it is not sensible / possible to check if such a declaration was made at the current
counter or by the current user. There is no knowledge within Horizon as to which user /
counter uses any given Till Id when making a declaration.
No check is made that the Check Variances function has been run the previous day, only that
at least one user has made a Cash Declaration for the current stock unit.
Ifno user has made a Cash Declaration for this Stock Unit "yesterday" then the user will be
prompted at logon to make one immediately.
‘There is now no option to bypass this declaration.
In particular, this has the following implications:
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 52 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/O12
Revaluation User Interface
User Interface Design Proposal Version: 0:31.0
COMMERCIAL IN-CONFIDENCE Date: —-31-August-049,"
September 2004
FUJ00090247
FUJ00090247
_—[Formatted
Once any user has logged on to the shared stock unit and made a Cash Declaration for
"yesterday", all subsequent users of the same Stock Unit will not be prompted to make
a cash Declaration.
Any attempt to invoke the Check Variances function will check the variance against
the most recent declarations and record the variance as a figure for “Today’.
MSGxxx Declaration Check Continue
A cash declaration was not made for this stock unit T°Ueh this button to continue,
at the last end of day.[Touch Continue to make a
cash declaration.
‘The existing ONCH declaration reminder reads as follows:
Declaration Outstanding Ok
‘The overnight cash holding declaration for this Tue this button to continue.
stock unit was not entered, Please enter it now
It is not proposed that this wording is used in the above dialogue
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 53 of 62
Fujitsu Services
Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012,
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date:
FUJ00090247
FUJ00090247
StAugust-049!" _—{ Formatted
September 2004
4.3 Transaction Corrections
4.3.1 Screen 13 — Transaction Correction Check
u
Correction Check
There are outstanding
transaction corrections
to process.
Touch Continue to review
transaction corrections
‘or Cancel to cancel.
‘This screen is presented if the Postmaster logs-on (strictly any user with a Role of Supervisor
or Manager) and there are outstanding Transaction Corrections to be applied. Touching
Continue will continue with the selection and processing of ‘Transaction Corrections (see
section 4.3.2), Touching Cancel will ignore the warning and continue with the Logon
process.
MSGxxx Correction Check Continue
There are outstanding transaction corrections to Touch this button to continue,
process.[Touch Continue to review transaction Gap
corrections or Cancel to cancel.
Touch this button to cancel.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 54 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004
4.3.2 Screen 14 - List Transaction Corrections
Transaction Corrections
1N123456789012348678 1405/04 [Article/Product description
123450000012345678 19/05/04. Article/Product description
'100000000077100002 26/08/04 Artcle/Product description
All outstanding Transaction Corrections will be listed on this screen in the order of date
received followed by Transaction Correction reference. The data shown on each line of the
screen is as follows:
a Transaction Correction reference preceded by “N’ (new) or ‘E? (evidence provided).
a Date when transaction correction was made available to the data centre
a Product description of transaction correction article
Any line on the screen may be selected and the detail of the transaction correction may be
viewed by then touching the OK button.
Use of the ‘Prev’ Button:
When this dialogue is reached following the logon prompt, the ‘Prev’ button will
cause the logon process to resume.
When this dialogue is reached from the housekeeping menu, the ‘Prev’ button will
always retum to the housekeeping menu
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 55 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAIFS/012
Revaluation User Interface
FUJ00090247
FUJ00090247
User Interface Design Proposal Version: 033
COMMERCIAL IN-CONFIDENCE Date: _31-August-049!"__{ formatted
September 2004
4.3.3 Screen 15 — No Outstanding Transaction Corrections
Transact tions,
There are no outstanding
transaction corrections
to process.
‘The above is shown if there are no outstanding transaction corrections to process.
MSGxxx ‘Transaction Corrections OK
‘There are no outstanding transaction corrections to Touch this button to continue
process.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 56 of 62
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EAIFS/012
Revaluation User Interface
FUJ00090247
FUJ00090247
User Interface Design Proposal O=81.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004
4.3.4 Screen 16 — Display Transaction Correction
Amount: 423496789012
Reference: N123456789012345678 Quantity: 123456
Product: Sc Client Ref: 1234567890123456
InviCredit: INV
‘This is an example ofthe Transaction Correction message that
will appear in this dialogue. The message will be restricted to
five hundred characters in length and there wil be no facility
{for any form of textual formatting except for the use of a line
feed. The line feed must come across the inter
‘special character and its agreed that the "c
10 may vary from this
The above screen is displayed following the selection of a single transaction from the
transaction corrections selection screen.
The details of the transaction correction are shown in the lefl-hand tablet. If there are a
significant number of paragraphs in the textual description of the correction then the text will
extend beyond the bottom of the screen. In this case, the ‘Up’ and ‘Down’ buttons on the
right-hand side of the screen will not show the no-entry signs and will be used to page the
screen up or down.
Either the Amount or Quantity will contain a value for any one Transaction Correction.
‘There will be no instances when both will be non-zero or both will be zero. If the Amount is
zero then it will not be displayed and if Quantity is zero it will also not be displayed. Amount
will be shown in pounds and pence.
Above the Up/Down buttons are up-to three other buttons that are optionally presented
depending on the mode of the transaction correction, Refer to EA/IFS/002 for a full
definition of the mode combinations allowed.
Mode Allowed ID I Mode Button Text
MG Make Good Accept Now
HD Plead Hardship ‘Accept Now
EV Request Evidence Seek Evidence
wo Write Of Send To P&l.
‘AN Assign to Nominee ‘Assign To HO
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 57 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EA/IFS/(012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE, Date: —_31-August-049!" i}
September 2004
[ sw [ Stock Write On/Off Stock WO ]
The different modes allowed in each transaction correction circumstance will be recorded on
the transaction correction message and is fully documented in EA/IFS/002. If the button text
does not fit on the buttons shown in the example, then the right is reserved to enlarge the
buttons or to abbreviate the button text.
Ifeither the modes MG or HD are present on the Transaction Correction, then the button
‘Accept Now’ will be displayed. This button will lead to the screen described in section
4.3.5, All other buttons will transact the Transaction Correction immediately without any
ther prompt.
‘The Cancel button will be used if the postmaster wishes to defer processing until another
time.
“Date Revd” is the Riposte message date. This will normally be the day after it was
generated in POL FS.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 58 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004
4.3.5 Screen 16b — Display Transaction Correction Options
Transaction Corrections
Make Good: Cash
Make Good: Cheque
Settle Centrally
This screen displays further transaction correction options for ‘Other Branches*transaction
correction modes of ‘Make Good’ or ‘Plead Hardship’. The screen is invoked by pressing the
“Accept Now’ button on the screen shown in section 4.3.4. The screen operates as a pick-list
whereby the user selects the option required followed by touching the ‘Ok’ button. The
‘Prev’ key can be used if the user wishes to defer making any choice.
‘The following options are available:
Mode ‘Make Good"
There is an option to Make Good with the product that is recorded against the
Instruction of the Transaction Correction. The product Long Name will be
displayed against the text ‘Make Good:’
If the accounting sense of the transaction is an Invoice (TCINV) and the product
indicated by the Instruction on the Transaction Correction is product 1 (Cash) then
there will be an additional option given to make good by using a Cheque.
Mode ‘Plead Hardship’
If the Transaction Correction has mode ‘Plead Hardship’, then the option will be
given to ‘Settle Centrally”
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 59 of 62
Fujitsu Services
Impact Release 3 - Declaration, Correction and Ref:
Revaluation User Interface
EAIFS/012
FUJ00090247
FUJ00090247
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: _31-August-049!"__{ formatted
September 2004
4.3.6 Screen 16a — Display Locked Message
Transaction Corrections
The selected transaction
correction is locked
by
another user. Please try
‘The above screen is displayed following the selection of a single transaction from the
transaction corrections selection screen and having determined that the transaction correction
is being viewed or processed by another user.
MSGxxx
‘Transaction Corrections
The selected transaction correction is locked by
another user. Please try later.
OK
Touch this button to continue.
© 2004 Fujitsu Services
COMMERCIAL IN-CONFIDENCE
Page: 60 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 - Declaration, Correction and Ref: EAMFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: _31-August-049!"__{ formatted
September 2004
4.3.7 Screen 17 - Invalid Transaction Correction
Transaction Correction
The transaction correction
N123456789012345678
failed. No change has
been made to the branch
accounts.
Please contact the NBSC
quoting the above
reference.
‘The above is shown if the attempt to process a transaction correction fails due to
discrepancies between the validation of a transaction at the counter and the values held within
the transaction correction message.
MSGxxx
Transaction Correction Exit
‘Transaction Correction %1 failed. No change has Touch this button to continue.
been made to the Branch accounts. ‘
Print
Please contact the NBSC quoting the above Touch this button to print this error message
reference.
%
= Iteration Flag+TC Reference
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 61 of 62
FUJ00090247
FUJ00090247
Fujitsu Services Impact Release 3 — Declaration, Correction and Ref: EA/IFS/012
Revaluation User Interface
User Interface Design Proposal Version: 0.31.0
COMMERCIAL IN-CONFIDENCE Date: 31-August-049)" _—[ Formatted
September 2004 }
4.3.8 Screen 18 - Transaction Correction Report Criteria
Report Criteria
Pieaseentenadatelnthe
format ddimmiyy,
format ddimmiyy
The above dialogue allows entry of the start and end date for the transaction corrections
report. Standard date validation ensures that future dates are not allowed and also ensures
that the “from’ date is not greater than the ‘to’ date.
© 2004 Fujitsu Services COMMERCIAL IN-CONFIDENCE Page: 62 of 62