NOTES on Bordereaux PhaseII - Technical Specification

Pg 5
Database Changes
Does User Specific Flag 5 needs new value Y added? ow do we !now if the" are not alread" using this
field for so#ething?
Pg $
% notice "ou changed the Progra# &u#ber position on screen'was that deliberate? % would not thin! it
was proble#(
)(*(*( % thin! +,% Participant should also be a valid &a#e usage for -ro!er,%nsurer and -ro!er,%nsurer
flag re.uired if &a#e not /-lan! or /011(
Pg 22
)(5(3(5
&o indication on changing .uer"4 that it should onl" be done if an +% Participant has been selected(
Pg2*
)(5(3(3
% thin! it would be good to have so#e polic" reference on the #essage and #a"be the stats stuff on second
level te6t( % doubt an"one loo!ing at this report will !now an"thing about these fields(
Pg2)
)(7()(2
8his function should onl" be called for Pre#iu# 8ransactions( %s this worth adding?
0s well as not outputting the 8ransaction Details4 care should be ta!en to ensure eader and 0ddress
records are created where no transaction have been paid for a given +% Polic" etc(( 9therwise blan! e#pt"
reports will be produced as the" are driven b" the eader file(
Pg 25
)(2:(3(2
8he sa#e as above applies where onl" transactions belonging to a given participant onl" are selected4 to
ensure unnecessar" address and header records are not created( % thin! the previous function though will
be a bit tric!ier(
Pg 3:
)(25(3
For each inwards pre#iu# t"pe one(( sounds a bit strange'(
Footnote )4 Pre#iu# Flag? Set to ;;;'(
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
8wo new bits as per =>#ail4
2( Set the Control Flag 0d>hoc on if a Progra# &u#ber selected(
3( Change &arrative Update call so that it is also onl" done if no participant selection has occurred(