USE CASE SPECIFICATION

UNIVERSAL BANKING
UseCase # : UCDFTISS00UseCase Name : Draft Type Instrument issuance UseCase Ver
sion : V2.00
UseCase Description : The existing draft issuance account/cash and Banker s Chequ
e Issuance account/cash process in Teller will be consolidated into one process.
Issuance will update draft inventory and the screen to be modified MERGEFIELD Pk
g.Notes
UCDFTISS001 - 'Draft Type' monetary instrument issuance with debit to account
UCDFTISS002 - Draft Type Instrument Issuance with debit to Cash
UCDFTISS003 - Draft Issue Validation Service
UCDFTISS004 - Draft Issue Inventory and Stock Update Service
UCDFTISS006- Duplicate (Replacement) Draft Issue
Change Log
DateVersionUC Activity StepChange DescriptionAuthor / ApproverMERGEFIELD ElemChan
ge.ResolvedDateShort15/9/2010DMERGEFIELD ElemChange.Version1.0UC Draft Type Instrumen
ts createdDraft versionGeetha Vishwanath MERGEFIELD ElemChange.ResolvedDateShort14
/10/2010
25/11/2010
01/12/2010D1.1UC D1.014/10/10 - Discussions with SM/James Bushell/CR/Vikas incor
porated
25/11/10 - Based on PPT and discussion of 18/11/2010 with John Power
01/12/10 Based on discussions with John Power/VikasRefer details06/12/2010VMERGEF
IELD ElemChange.Version1.0UC modifiedAs per reviews (artf662934)Geetha Vishwanath/
John Power/Vikas18/01/2011D2.0UC D2.0As per points noted during HCL reverse walk
through. See Points-HCLReverseWalkthrough-Issuance.xls in Annexure for details of
changes.Geetha Vishwanath19/01/2011V2.0UC D2.0Reviewed D2.0 John Power
MERGEFIELD ElementTagVal.NameBRD ReferenceMERGEFIELD ElementTagVal.Notes UB_BRD_BCB_D
raft_Managament ID11BREQ002 (Draft Issuance)
HYPERLINK "http://sp.onemisys.com/SiteDirectory/BankFusionSolutionsManagement/Cha
nge%20Requests%202/CR_BCB_DRAFT_BRD%20CLARIFICATIONS.doc"CR_BCB_DRAFT_BRD CLARIFI
CATIONS  MERGEFIELD ElementTagVal.NameLevelMERGEFIELD ElementTagVal.NotesPrimary (Low-
level - Detailed)MERGEFIELD ElementTagVal.NameProject DescriptionMERGEFIELD ElementTa
gVal.NotesBermuda Commercial BankMERGEFIELD ElementTagVal.NameSA ReferenceMERGEFIELD E
lementTagVal.NotesNA

Currently UB supports issuance of Drafts and Banker s Cheque by debit to cash/acco

unt. These are provided as separate transactions. The Draft number or Banker s Che
que number is entered manually with no Inventory concept.
The functionality described in this Use Case and related ones provide for the fo
llowing:
1. Instrument Inventory which will hold different monetary instruments falling u
nder two broad Instrument Types called Draft and TC
2. Instrument Stock Register which will track events in each instrument
3. Since Demand Draft and Banker s Cheque are variants of the same instrument type
Draft , the existing separate processes in Teller will be merged.
4. Draft issuance by Correspondents is out of scope for this release
Note that to cater to a centralized Printer scenario where the instrument number
available in Printer may not match with the actual draft number being printed,
it was originally conceived to provide for automatic defaulting of draft number
during draft printing stage with a provision to edit the same during printing of
draft. A separate transaction reference was also provided to track the transact
ion through its lifecycle along with draft number. This would also allow Teller
to modify the sequence in which instruments will be actually printed rather than
go by the sequence in which issuance is triggered. This was removed during revi
ew sessions.
The solution was then modified to provide for automatic defaulting of draft numb
er during draft issuance stage with a provision to edit the same during issuance
. This has also been removed.
The final solution as envisaged is to provide for a configuration to have either
automatic numbering or manual; wherein in case of automatic numbering there wou
ld be no provision to edit the draft number while manual numbering would allow Tel
ler to enter the draft number. Hence the solution can cater to a centralized Pri
nter scenario where Blank instruments with manual numbering is opted for. This fin
al solution however does not cater to modification of printing sequence and henc
e instruments can only be printed in the sequence in which they are issued.

UseCase # : MERGEFIELD Pkg.Alias UCDFTISS001UseCase Name : 'Draft Type' monetar

y instrument issuance with debit to accountUseCase Version :V2.00
UseCase Description: The existing draft and bankers cheque issuance process wit
h debit to Account (in Teller) to be consolidated and modifiedMERGEFIELD Pkg.Note
s
M ERGEFIELD ElemConstraint.TypePreconditionsDraft Type Instrument Inventory exists
MERGEFIELD ElemConstraint.NotesMERGEFIELD ElemConstraint.TypeSuccess End Cond1. Draft
type instrument issuance, validation against Draft instrument inventory during
issuance
2. ISSDRFTACC transaction should now cater to issuance of all draft type instrumen
ts such as Demand Draft, Banker s Cheque
MERGEFIELD ElemConstraint.NotesMERGEFIELD ElemConstraint.TypeFailed End CondiInventor
y validation/update/draft issuance failsMERGEFIELD ElemConstraint.Name
MERGEFIELD ElemConstraint.Notes
Scenario : MERGEFIELD ElemScenario.TypeMain Success
Draft Issuance Pre-Numbered Instrument/Blank instrument with auto number generat
ion
MERGEFIELD ElemScenario.Notes
010 - Teller selects existing Teller 'ISSDRFTACC' process from the menu and proc
eeds to issue
a 'Draft Type' instrument such as Demand Draft or Banker's Cheque
020 - System displays the following modified screen:

030 - Teller enters/selects the following details (uses 'tab' to navigate):
1. Debit Account (can be an internal account)
2. Customer Name where default customer name has to be changed
3. Draft currency and amount
4. Draft instrument name where default instrument name has to be changed
5. Beneficiary Name and Address
6. Narrative
7. Payable At (optional; search criteria provided which will display list of bra
nches)
8. Draft/Bank Cheque Number (when blank instrument is used without auto draft nu
mber generation)
9. charge details in the 'charges' button

040 - System performs the following activities : (defaulting upon tab out from/t
o respective fields)
1. Defaults Primary account holder in 'Customer Name' field
2. Displays joint holders of the account in the drop down of 'Customer
Name' field for
selection of a non-primary customer by Teller
3. finds instrument attached to the transaction (in Teller Transaction
configuration) is in the
specified draft currency
a) defaults this instrument in the 'Instrument' field AND
b) finds Pre-Numbered and Blank Instruments for the following co
mbination and displays
them in the 'Instruments' field drop down :
1) in the specified draft currency AND
2) in the logged in branch AND
3) in the logged in Holding Location
4. Defaults business date in Value Date field (Not editable;existing)
5. Defaults Total Charge Amount and charge currency in the 'Charge Amount' field
(existing)
6. Defaults Total Debit Amount in transaction currency in 'Debit Amount' field (
existing;
currency editable)
7. Defaults Exchange Rate (existing; where transaction currency not equal to deb
it
amount currency)
8. Defaults Buy Equivalent Amount (existing)
050 - System calls the Draft Issue validation Service and provides the following
values to it:
1. Draft currency and amount
2. Draft instrument name
3. Logged in Holding Location
4. Logged in Branch
060 - System finds Draft Issue validation Service has returned a 'Success' messa
ge along with
the following details:
1) Draft Number with indicator as non-editable
2) Credit Account Number with indicator as 'nostro' OR 'non-nostro'
3) Template ID
070 - System defaults the values received in the following fields :
1. Draft/Bank Cheque Number field (Draft number) as Non-editable
2. Contra Account field (credit account number)
3. Template ID field (template ID received)
080 - Teller proceeds to save the transaction
090 - System performs the following activities:
1. Finds transaction does not require Supervisor approval
2. Calls Posting engine to perform the following validations:
A) Debit customer account
a) has sufficient balance
b) is not closed
c) is not stopped
d) is set to 'No Password Required'
3. Finds Posting engine has returned success message
4. Calls Draft Issue Stock Update Service for updating Instrument Stock
Register and
 provides the following values to it:
1. Instrument Name
2. Draft Number
3. Issue Branch
4. Holding Location
5. draft currency and amount
6. Debit Account Number
7. Customer Name
8. Payee Name
9. Payee Address
10. Payable At
11. Narrative
12. User ID = Teller User ID/Inward Clearing Process
13. Auth By = Supervisor User ID if authorised by supervisor
14. Event = Draft Issue (if credit account number indicator is 'non-nos
tro') OR
Event = Draft Issue to Nostro (if credit account number indicator
is 'nostro')
5. Finds Draft Issue Stock Update Service has returned a 'success' mess
age
6. passes the following accounting entries:
Debit Customer Account
Credit contra account
7. Displays the following confirmation message to the Teller "Draft/Ban
k Cheque
Number <draft/bank cheque number> issued. Proceed to Print - Yes
/No"
8. Teller selects 'No' to print the instrument later
9. System performs the following activities:
1. sends the instrument details to 'Print Instrument Queue'.
2. Displays the following confirmation message to the Teller "Draft/Ba
nk Cheque
Number <draft number> queued for Printing"
10. exits
{Note: instruments should not be permitted to remain in Print Instrument queue o
vernight without being printed. During EOD trigger if instruments are found pend
ing in Print Queue, a warning must be shown to the user and the EOD process must
be sent to Supervisor for approval with this reason indicated}

Scenario : Alternate

MERGEFIELD ElemScenario.Scenario060(1)a - Issuance of Blank instrument - manual in

put of Draft number
MERGEFIELD ElemScenario.Scenario060(1)a10 - System finds Draft Issue validation Ser
vice has returned a 'Success' message along with
the following details:
1) Nil Draft Number with indicator as editable(for Teller to input the
draft number)
2) Credit Account Number with indicator as 'nostro'
3) Template ID
060(1)a20 - System defaults the values received in the following fields :
1. Draft/Bank Cheque Number field (blank value) in editable mode
2. Contra Account field (credit account number)
3. Template ID field (template ID received)
060(1)a30 - Teller proceeds to enter the Draft Number
060(1)a40 - System finds status of draft number entered by Teller = Available
060(1)a50 - System marks the status of draft number entered by Teller = Reserved
060(1)a60 - System exits to step 80

Scenario : Error

MERGEFIELD ElemScenario.Scenario060(1)a40a - Entered draft number not available fo

r issue

060(1)a40a10 - System finds status of draft number entered by Teller not equal t
o 'Available'
060(1)a40a20 - System displays the following error message "Entered Draft number
already used"
060(1)a40a30 - System exits to step 30
MERGEFIELD ElemScenario.Scenario

Scenario : MERGEFIELD ElemScenario.TypeAlternate

MERGEFIELD ElemScenario.Scenario080b - Teller cancels instrument issuance by select
ing to exit without
saving issuance/ by closing issuance abruptly/ by abandoning it af
ter supervisor rejection
080b10 - Teller selects to abandon/abandons instrument issuance (by selecting to
exit without
saving or by closing issuance abruptly or abandoning it after supe
rvisor rejection)
080b20 - System finds status of Draft/Bank Cheque number in abandoned instrument
issuance =
'Reserved'
080b30 - System performs the following activities:
1) In case of Pre-Numbered instruments with currency AND Blank instrume
nts with currency +
auto draft number generation:
a) releases the number for usage in the next instrument issuance of the
same
currency + instrument combination
2) In case of Pre-Numbered without currency AND Blank instruments withou
t currency + auto draft
number generation:
a) releases the number for usage in the next issuance for the same inst
rument
3) In case of Blank instruments without auto draft number generation (w
ith or without currency):
a) releases the number and removes the record from Stock Register
080b40 - System exits

Scenario : MERGEFIELD ElemScenario.TypeAlternate

MERGEFIELD ElemScenario.Scenario090(1)a - Supervisor approval required for instrum
ent issuance
090(1)a10 - System finds Supervisor approval required for instrument issuance
090(1)a20 - System sends the issuance details to Supervisor for approval
090(1)a30 - System finds issuance authorised by Supervisor
090(1)a40 - System exits to step 090(2)

Scenario : MERGEFIELD ElemScenario.TypeAlternate

MERGEFIELD ElemScenario.Scenario090(1)a30a - Supervisor rejects instrument issuanc
e
090(1)a30a10 - System finds instrument issuance rejected by Supervisor
090(1)a30a20 - System sends rejection notification to originating Teller
090(1)a30a30 - System exits

Scenario : MERGEFIELD ElemScenario.TypeAlternate

MERGEFIELD ElemScenario.Scenario090(1)a30a20a - Amendment of instrument issuance de
tails after Supervisor rejection
090(1)a30a20a10 - Teller selects the draft transaction from the rejected transac
tions list to modify details
090(1)a30a20a20 - System displays the issuance screen with pre-populated values
based on
data entered earlier (new Draft/Bank Cheque number
must NOT be generated AND
existing draft number must not be allowed to be cha
nged)
090(1)a30a20a30 - Teller modifies the following values:
1. Debit Account
2. Customer Name where default customer name has to be changed
3. Draft amount
4. Beneficiary Name and Address
5. Narrative
6. Payable At (optional; search criteria provided which will display list of bra
nches)
7. charge details in the 'charges' button
090(1)a30a20a40 - System performs the following activities :
1. Defaults Total Charge Amount and charge currency in the 'Charge Amount' field
(existing)
2. Defaults Total Debit Amount in transaction currency in 'Debit Amount' field (
existing;
currency editable)
3. Defaults Exchange Rate (existing; where transaction currency not equal to deb
it
amount currency)
4. Defaults Buy Equivalent Amount (existing)
090(1)a30a20a50 - System exits to step 080

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario060a - AML threshold amount breach
060a10 - System finds Draft Issue validation Service has returned 'AML threshold
amount
breach' message along with the following details:
a) Instrument
b) Draft Number
c) Draft Currency and amount
d) Template ID
e) status = AML threshold breach
060a20 - System performs the following activities:
1. Displays the following warning message "AML threshold breached"
2. sends the Customer name and address and Beneficiary name and address
details to the AML solution
3. receives the response from AML solution and displays to Teller
4. exits to step 70

{Note: AML check works currently in UB as under:

1. Under AML configuration, Sub Products + transaction code combination eligible
for AML check is set. When a financial transaction is done for this combinatio
n AML check message is triggered to Fircosoft/AML Application.
2. threshold amount is maintained in the AML solution
3. Based on this UC and Instrument Configuration UC, threshold amount will need
to be introduced in the existing UB AML configuration or separately in UB.
4. UB will check if threshold is breached and then send the details to the AML s
olution and get the details.
5. User would then decide to proceed or abort.

Scenario : MERGEFIELD ElemScenario.TypeAlternate

MERGEFIELD ElemScenario.Scenario090(8)a - Print instrument upon issuance
090(8)a10 - Teller selects to print instrument now
090(8)a20 - System sends information on the following to Dynasty (which in turn
appends the
received details in the instrument as per specified draft template
and sends to Draft
Printer which has MICR code line printing capability)
1. Template ID
2. Draft/Bank Cheque Number
3. Draft/Bank Cheque currency and amount
4. Draft/Bank cheque amount in words
5. Beneficiary Name
6. Payable At
7. Contra Account
8. Nostro Bank (if contra account = nostro account then the bank linked
to the nostro account
must be sent as Nostro Bank)
9. Sort code of Nostro Bank
10. Draft Issue Date
090(8)a30 - System performs the following activities:
1. Updates Draft Instrument Stock Register with the following details:
1. Draft Number
2. Current Status = Issued and Printed OR 'Issued to Nostro and Pr
inted' (overwrite)
2. Updates Instrument History with the following details:
1. Instrument Number
2. Instrument Status = Issued and Printed OR 'Issued to Nostro and Printed'
3. Status Date = status date (when changed to 'Issued and Printed'/'Issued to No
stro and
 Printed')
4. Narrative = narrative entered in draft issuance
5. Correspondent Bank = Nostro
6. Swift Message Issued Indicator to
i. Yes if MT110 is generated
ii. Not Applicable if instrument currency = Local currency
7. stop/caution reason = nil
8. User ID = Teller User ID
9. Auth By = Supervisor User ID if authorised by supervisor
10. Branch
11. Holding Location
3. finds instrument currency = local currency
4. Displays the following confirmation to the User Draft Number <Draft Numb
er> sent to
Printer <Draft Printer Name> for printing
090(8)a40 System exits to step 110

Scenario : MERGEFIELD ElemScenario.TypeAlternate

MERGEFIELD ElemScenario.Scenario090(8)a30(3)a - Instrument currency = foreign curre
ncy

090(8)a30(3)a10 - System finds instrument currency = foreign currency

090(8)a30(3)a20 - System generates MT110 based on draft details to the Nostro Ba
nk specified
in the instrument issued record (existing functio
nality)
090(8)a30(3)a30 - System exits to step 090(8)a30(4)

Scenario : MERGEFIELD ElemScenario.TypeAlternate

010a - Bulk draft issuance (expected to be done using upload only)
010a10- User uploads batch file containing draft issuance related accounting ent
ries and the
following details(through existing batch file upload)
1. Draft Issue Main Transaction Code
2. Draft Issue Contra Transaction Code
3. Debit Account
4. Customer Name
5. Draft/Bank Cheque currency and amount
6. Draft Instrument
7. Beneficiary Name and Address
8. Narrative
9. Payable At (search criteria provided which will display list of branches and
corresponding branch name)
10. Draft/Bank Cheque Number (optional;)
11. Contra Account
12. Exchange Rate
13. Holding Location
14. Issue Branch
010a20 - Batch processing dentifies the debit leg as a Draft Issue Transaction
010a30 - Batch processing calls the Draft Issue validation Service and provides
the following
 values to it:
1. Draft currency and amount
2. Draft instrument name
3. Logged in Holding Location
4. Logged in Branch
5. Draft Number (optional)
010a40 - Batch processing finds Draft Issue validation Service has returned a 'S
uccess'
message along with the following details:
a) Draft Number(if provided by service)
b) Template ID
010a50 - Batch processing updates the debit leg with the Draft number and Templa
te ID
010a60 - Batch processing calls batch validations process
010a70 - Batch processing finds batch validations successful
010a80 - Batch processing calls Posting engine
010a90 - Batch processing finds Posting engine successful
010a100 - Batch processing calls Draft Issue Stock Update Service for updating
Instrument Stock Register and provides the following values to it:
1. Instrument Name
2. Draft Number
3. Issue Branch
4. Holding Location
5. draft currency and amount
6. Debit Account Number
7. Customer Name
8. Payee Name
9. Payee Address
10. Payable At
11. Narrative
12. User ID = Teller User ID/Inward Clearing Process
13. Auth By = Supervisor User ID if authorised by supervisor
14. Event = Draft Issue
010a110 Batch processing finds Draft Issue Stock Update Service has returned a '
success' message
010a120. Batch processing performs the following activities:
1. sends the instrument details to 'Print Instrument Queue'.
2. Displays the following confirmation message to the Teller "Draft/Ba
nk Cheque
Number <draft number> queued for Printing"
010a130. Batch processing exits to other batch processing activities


UseCase # : MERGEFIELD Pkg.Alias UCDFTISS002UseCase Name : Draft Type Instrument

Issuance with debit to CashUseCase Version :V2.00
UseCase Description: The existing draft and bankers cheque issuance processes i
n Teller (debit to cash) to be consolidated and modified to capture additional i
nformation and perform validation against Draft Type Instrument Inventory. MERGEF
IELD Pkg.Notes
M ERGEFIELD ElemConstraint.TypePreconditionsDraft Type Instrument Inventory exists
MERGEFIELD ElemConstraint.NotesMERGEFIELD ElemConstraint.TypeSuccess End Cond1. Draft
type instrument issuance with additional information capture and validation aga
inst Draft Type instrument inventory is done during issuance
2. ISSDRFTCSH transaction should now cater to issuance of all draft type instrumen
ts such as Demand Draft, Banker s Cheque
MERGEFIELD ElemConstraint.TypeFailed End CondiInventory validation/update/draft iss
 uance failsMERGEFIELD ElemConstraint.Name
MERGEFIELD ElemConstraint.Notes
Scenario : MERGEFIELD ElemScenario.TypeMain Success
MERGEFIELD ElemScenario.Scenario Demand MERGEFIELD ElemScenario.ScenarioDraft and Ba
nker's Cheque Issuance  
MERGEFIELD ElemScenario.Notes
010 - Teller selects existing Teller ' ISSDRFTCSH' process from the menu and pro
ceeds to issue a 'Draft Type' instrument such as Demand Draft or Banker's Cheque
by debit to Cash:
020 - System displays the following existing screen with additional and re-arran
ged fields as indicated:
 EMBED PBrush 
030 - Teller enters/selects the following details (uses 'tab' to navigate):
1. Customer Name
2. Draft currency and amount
3. Draft instrument name
4. Beneficiary Name and Address
5. Narrative
6. Payable At (optional; search criteria provided which will display list of bra
nches)
7. Draft/Bank Cheque Number (when blank instrument is used without auto draft nu
mber g
eneration)
8. charge details in the 'charges' button
040 - System defaults the following values: (upon tab out from/to respective fie
lds)
1. finds instrument attached to the transaction (in Teller Transaction
configuration) is in the
specified draft currency
a) defaults this instrument in the 'Instrument' field AND
b) finds Pre-Numbered and Blank Instruments for the following co
mbination and displays
them in the 'Instruments' field drop down :
1) in the specified draft currency AND
2) in the logged in branch AND
3) in the logged in Holding Location
4. Defaults business date in Value Date field (Not editable;existing)
5. Defaults Total Charge Amount and charge currency in the 'Charge Amount' field
(existing)
6. Defaults Total Debit Amount in transaction currency in 'Debit Amount' field (
existing;
currency editable)
7. Defaults Exchange Rate (existing; where transaction currency not equal to deb
it
amount currency)
8. Defaults Rounding Indicator
9. Defaults Buy Equivalent Amount (existing)
10. Pay/Receive Local Currency
11. Local Currency Charge
050 - System calls the Draft Issue validation Service and provides the following
values to it:
1. Draft currency and amount
2. Draft instrument name
3. Logged in Holding Location
4. Logged in Branch
060 - System finds Draft Issue validation Service has returned a 'Success' messa
ge along with
the following details:
 1) Draft Number with indicator as non-editable
2) Credit Account Number with indicator as 'nostro' OR 'non-nostro'
3) Template ID
070 - System defaults the values received in the following fields :
1. Draft/Bank Cheque Number field (Draft number) as Non-editable
2. Contra Account field (credit account number)
3. Template ID field (template ID received)
080 - Teller proceeds to save the transaction
090 - System performs the following activities:
1. Finds transaction does not require Supervisor approval
2. Calls Draft Issue Stock Update Service for updating Instrument Stock
Register and
provides the following values to it:
1. Instrument Name
2. Draft Number
3. Issue Branch
4. Holding Location
5. draft currency and amount
6. Debit Account Number
7. Customer Name
8. Payee Name
9. Payee Address
10. Payable At
11. Narrative
12. User ID = Teller User ID/Inward Clearing Process
13. Auth By = Supervisor User ID if authorised by supervisor
14. Event = Draft Issue (if credit account number indicator is 'non-nos
tro') OR
Event = Draft Issue to Nostro (if credit account number indicator
is 'nostro')
3. Finds Draft Issue Stock Update Service has returned a 'success' mess
age
4. Calls Posting engine to pass the following accounting entries:
Debit Cash Account
Credit contra account
5. Displays the following confirmation message to the Teller "Draft/Ban
k Cheque
Number <draft/bank cheque number> issued. Proceed to Print - Yes
/No"
6. Teller selects 'No' to print the instrument later
7. System performs the following activities:
1. sends the instrument details to 'Print Instrument Queue'.
2. Displays the following confirmation message to the Teller "Draft/Ba
nk Cheque
Number <draft number> queued for Printing"
8. exits


UseCase # : MERGEFIELD Pkg.Alias UCDFTISS003UseCase Name : Draft Issue Validati

on ServiceUseCase Version :V2.00
UseCase Description : Draft Issue Validation Service does draft related validat
ions during draft issueMERGEFIELD Pkg.Notes
MERGEFIELD ElemConstraint.TypePreconditionsIdentified information for Draft Issue V
alidation Service are providedMERGEFIELD ElemConstraint.NotesMERGEFIELD ElemConstra
int.TypeSuccess End CondDraft Issue Validation Service provides relevant message t
o the calling functionMERGEFIELD ElemConstraint.NotesMERGEFIELD ElemConstraint.TypeF
ailed End CondiDraft Issue Validation Service fails to perform the identified val
idations and does not return suitable message
Scenario : MERGEFIELD ElemScenario.TypeMain Success

010 Draft Issue Validation Service is called through Teller Issue draft transact
ion to account or by cash
020 Draft Issue validation Service receives the following details:
1. Draft currency and amount
2. Draft instrument name
3. Logged in Holding Location
4. Logged in Branch
030 Draft Issue validation Service performs the following activities:
1. Finds specified instrument = Pre-Numbered
2. Finds Pre-Numbered instruments in the draft currency
3. Fetches next available draft number for the specified instrument + c
urrency based on the
following condition:
a. next available draft number in logged in holding location (if instru
ment is assigned to
the holding location) (logged in Holding Location can either be the
TILL or the Vault)
4. simultaneously updates status of this instrument number as 'rese
rved' to disallow its usage in a
parallel draft issuance
5. Fetches the credit account based on GL Pseudonym defined for the curr
ency
+ instrument
6. Finds credit account = Nostro account
7. Fetches 'Template ID' defined in Dynasty for the specified curren
cy and instrument
8. Finds instrument amount less than or equal to AML threshold amoun
t
9. Returns a Success message to the calling function with the follow
ing details:
a) Draft Number with an indicator as non-editable (the deriv
ed next available number in
point 1 above)
b) Credit Account Number with an indicator as Nostro
 c) Template ID
d) Instrument
e) Currency
040 Draft Issue validation Service exits

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(6)a - Credit account not equal to Nostro
030(6)a010 - Draft Issue Validation service finds credit account not equal to nos
tro
030(6)a020 Service earmarks to send the Credit Account Number with indicator as N
on-Nostro in step
30(9b)
030(6)a030 Service exits to step 30(7)
Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(1)b - Blank Instrument with currency and auto
number generation
030(1)b010 - System finds specified instrument = Blank instrument
030(1)b020 System finds Blank instrument in specified currency with auto number
generation
030(1)b030 System fetches the next available draft number for the specified inst
rument + currency (taking into account any released draft numbers)
030(1)b040 System exits to step 30(4)

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(1)b020a - Blank Instrument without auto number
generation
030(1)b020a010 - System finds Blank instrument without auto number generation (wi
th or without
currency)
030(1)b020a020 System earmarks to send the Draft Number value as NIL and indicator
as editable in
step 30(9a)
030(1)b020a030 System exits to step 30(5)

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(1)b020b - Blank Instrument without currency -
with auto number generation
030(1)b020b010 - System finds Blank instrument configured without currency and wi
th auto number
generation switched on
030(1)b020b020 System fetches the next available draft number for the specified
instrument (taking into
account any released draft numbers)
030(1)b020b030 System exits to step 30(4)
Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(2)a - Pre-Numbered Instrument without currency

030(2)a010 - System finds Pre-Numbered instruments configured without currency

030(2)a020 System fetches next available draft number for the specified instrume
nt based on the
following condition:
a. next available draft number in logged in holding location (if instru
ment is assigned to
the holding location) (logged in Holding Location can either be the
TILL or the Vault)
030(2)a030 System exits to step 30(4)

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(3)a - Instrument not available in the Holding
location
030(3)a010 - Draft Issue Validation service finds draft instruments not available
in the logged in Holding Location (instrument number range/instrument count not
available)
030(3)a020 - Returns a Failure message to the calling function with the followin
g
details:
a) Instrument
b) Currency (if currency is required for the instrument)
c) logged in Holding Location
d) Message = Instruments not available in the Holding location
e) exits

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(5)a - Credit account not available for the Pse
udonym

030(5)a010 - Draft Issue Validation service finds account not available for the c
urrency
+ pseudonym
030(5)a020 - Returns a Failure message to the calling function with the followin
g
details:
a) Instrument
b) Currency
c) Draft Number
c) Message = Credit account for the instrument and currency n
ot available
d) exits

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(7) a - Template not found for the Instrument a
nd currency
030(7) a010 - Draft Issue Validation service finds Template not available for th
e currency
+ instrument
030(7) a020 - Returns a Failure message to the calling function with the followi
ng
details:
a) Instrument
b) Currency
c) Draft Number
d) Credit Account
e) Message = Template not available for this instrument and c
urrency
f) exits
Scenario : Alternate
MERGEFIELD ElemScenario.Scenario030(8)a - Draft Issue - AML threshold amount breac
hed
030(8) a010 - Service finds draft issue amount in draft currency is greater than
AML threshold
amount specified for the currency
030(8)a020 - Service returns AML threshold amount breach message to the calling
function with the following details:
a) Instrument
b) Draft Number
c) Draft Currency and amount
d) Template ID
e) status = AML threshold breach
030(8)a030 - System exits

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario010a - Draft Validation Service called through Bat
ch
010a010 -  Draft Issue Validation Service is called by Batch processing function
010a020 Draft Issue validation Service receives the following details:
1. Draft currency and amount
2. Draft instrument name
3. Logged in Holding Location
4. Logged in Branch
5. Draft Number (to be entered only where instrument = blank with no aut
o
generation of draft number)
010a030 Draft Issue validation service performs the following activities:
1. finds Draft number not received
2. Finds specified instrument = Pre-Numbered
3. Finds Pre-Numbered instruments in the draft currency
4. Fetches next available draft number for the specified instrument + c
urrency based on
the following condition:
a. next available draft number in logged in holding location (if instru
ment is
assigned to the holding location) OR
b. next available draft number in logged in branch (when instruments ar
e
available at 'vault' only)
5. simultaneously updates status of this instrument number as 'rese
rved' to disallow its
usage in a parallel draft issuance
6. Fetches the credit account based on GL Pseudonym defined for the curr
ency
+ instrument
7. Finds credit account = Nostro account
8. Fetches 'Template ID' defined in Dynasty for the specified curren
cy and instrument
9. Finds instrument amount less than or equal to AML threshold amoun
t
10. Returns a Success message to the calling function with the followin
g
details:
a) Draft Number (the derived next available number
in point 1 above)
b) Template ID
11. exits

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario010a30(1)a - Draft Number entered (Blank instrumen
t issuance through batch WITHOUT auto number generation)
010a030(1)a010 -  System finds Draft Number available in batch file for the recor
d
010a030(1)a020 System finds status of draft number = Available
010a030(1)a030 System exits to step 010a30(5)

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario010a30(2)a - Blank instrument issuance through bat
ch AND auto number generation
010a030(2)a010 -  System finds specified instrument = Blank with auto number gene
ration
010a030(1)a020 System finds Blank instruments in the draft currency
010a030(1)a020 System exits to step 010a30(4)

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario010a30(2)a20a - Blank instrument issuance through
batch - auto number generation and no currency
010a30(2)a20a10 - System finds Blank instruments configured without currency
010a30(2)a20a20 System fetches next available draft number for the specified ins
trument based on
the following condition:
a. next available draft number in logged in holding location (if instru
ment is
assigned to the holding location) OR
b. next available draft number in logged in branch (when instruments ar
e
available at 'vault' only)
010a30(2)a20a30 System exits to step 010a30(5)

Scenario : Alternate
MERGEFIELD ElemScenario.Scenario010a30(2)b - Draft Number received for Pre-Numbere
d/Blank with auto number generation
010a030(2)b010 -  System finds draft number available in batch file for the recor
d even though specified instrument = Pre-Numbered/Blank with auto number generat
ion
010a030(2)b020 System overwrites the draft number received in batch file with th
e system allocated
draft number
010a030(1)a020 System exits to step 010a30(3)

UseCase # : MERGEFIELD Pkg.Alias UCDFTISS004UseCase Name : Draft Issue Inventor

y and Stock Update ServiceUseCase Version :V2.00
UseCase Description : Draft Issue Inventory and Stock Update Service does inven
tory and stock updates upon issuanceMERGEFIELD Pkg.Notes
MERGEFIELD ElemConstraint.TypePreconditionsIdentified information for Draft Issue I
nventory and Stock Update Service are providedMERGEFIELD ElemConstraint.NotesMERGEF
IELD ElemConstraint.TypeSuccess End CondDraft Issue Inventory and Stock Update Ser
vice provides relevant message to the calling functionMERGEFIELD ElemConstraint.N
otes
MERGEFIELD ElemConstraint.TypeFailed End Condi
Draft Issue Inventory and Stock Update Service fails to perform the identified u
pdates and does not return suitable message
Scenario : MERGEFIELD ElemScenario.TypeMain Success
010 Draft Issue Inventory and Stock Update Service is called through Teller (iss
ue draft
transaction to account or by cash)
020 Draft Issue Inventory and Stock Update Service receives the following detail
s:
1. Instrument Name
2. Draft Number
3. Issue Branch
4. Holding Location
5. draft currency and amount
6. Debit Account Number
7. Customer Name
8. Payee Name
9. Payee Address
10. Payable At
11. Narrative
12. Nostro (optional)
13. User ID = Teller User ID/Inward Clearing Process
14. Auth By = Supervisor User ID if authorised by supervisor
15. Event = Draft Issue/Draft Issue to Nostro
030 - Service performs the following activities:
1. updates Draft Inventory for the instrument + currency + branch + hol
ding
location combination in which the issued draft number falls with th
e Total Count of
Unused Leaves as 'total count of unused leaves' = outstanding count
- 1
2. Updates Draft Instrument Stock Register with the following details:
1. Instrument Name
2. Draft Number
3. Issue Branch
4. Holding Location
5. draft currency and amount
6. Debit Account Number
7. Customer Name
8. Payee Name
9. Payee Address
10. Current Status = Issued (overwrite)
11. Payable At (optional)
3. Updates Instrument History with the following details:
1. Draft Number
2. Instrument Status = Issued (where event = Draft Issue) / Issued to Nostro (wh
ere event
= Draft Issue to Nostro)
3. Status Date = status date (when changed to 'Issued'/Issued to Nostro)
4. Narrative = narrative entered in draft issuance
5. Correspondent = Nostro (optional)
6. SWIFT Message Issued Indicator = Yes OR Not Applicable as indicated
a) if MT110 is generated, indicator = Yes
b) if MT110 not applicable for the transaction, then indicator = Not
Applicable
7. User ID = Teller User ID
8. Auth By = Supervisor User ID if authorised by supervisor
040 Returns Success message to the calling function

UseCase # : MERGEFIELD Pkg.Alias UCDFTISS005 UseCase Name : Duplicate (Replacem

ent) Draft Issue UseCase Version :V2.00
UseCase Description : Duplicate (Replacement) Draft IssuanceMERGEFIELD Pkg.Notes
M ERGEFIELD ElemConstraint.TypePreconditionsDraft already issuedMERGEFIELD ElemConstr
aint.TypeSuccess End CondExisting Draft MERGEFIELD ElemConstraint.Notesnumber is can
celled, new draft number allocated and marked as cancelled and replaced against
the old number
MERGEFIELD ElemConstraint.TypeFailed End CondiStatus marking for existing draft num
ber and new number fails
Scenario : MERGEFIELD ElemScenario.TypeMain Success

010 Teller initiates Duplicate (Replacement) Draft Issue process

020 System displays the following screen with options as under:
 EMBED PBrush 
1) Date Range (default = Business Date; mandatory; can be changed to pas
t date )
2) Instrument Currency (mandatory; ALL not available)
3) Draft/Bank Cheque Number (optional; list of drafts with status = Issu
ed and Printed / Issued to
Nostro and Printed)
030 Teller specifies the following details and selects to proceed:
1) date range
2) Instrument Currency
3) Draft/Bank Cheque Number
040 System lists out all instruments for the specified filter criteria with curr
ent status = Issued/
Issued To Nostro / Issued and Printed /Issued to Nostro and Print
ed /Stopped /Cautioned
/Stale
050 Teller selects the instrument number for which duplicate is to be issued
060 - System calls the draft cancellation process and displays the draft cancell
ation screen with
draft number pre-populated as the draft number be cancelled. This will
not be editable.
(refer UB_Teller_UC_Draft_Others for cancellation)
070 Teller enters/specifies the following details in cancellation (excluding Dra
ft Number; refer
Cancellation UC for details)
080 System cancels the existing draft number (as per Draft Cancellation UC) with
status of draft
number = Cancelled Replacement Issued
090 System calls the Draft issuance process (as per Draft Issue UC) with pre-pop
ulated details from
original draft issuance EXCEPT Draft Number (Draft number will be gen
erated as per draft issue
UC)
100 - exits

Annexure:
1) Details of changes in D2.0 attached here
 EMBED Excel.Sheet.12 
_____________________________________________________________________________
? Copyright Misys plc 2009
Page PAGE8 / NUMPAGES24