See the NOVUS Walkthrough Guide for further information.
Table of Contents
Outward Bordereau - Overview
There are two options for outwards bordereau in the OUTBORD program: access an existing bordereau or create a new bordereau.
This program offers the following bordereau types to be produced for a given account code:
- Risk (exposure) format (if using risk details)
- Premium booked or paid
- Claim booked or paid bordereau
These options must be configured correctly in the Bordereau Styles codeset (GID26) in the CODES programme.
A bordereau is a report containing the data required to report an account to underwriters or insurers informing them how much they expect to receive or remit.
The NOVUS rules are that an exposure/risk bordereau will report one row per location as entered in the risk details screen. Without risk details, an exposure bordereau using risk details can not be selected. There must be an accounting transaction on the risk, i.e. a firm order has been processed before a record will be available in OUTBORD. If there are no transactions on a risk, the results will show a zero bordereau.
A starting guide for this is based on the London Market glossary for the data elements per class that should be reported if possible. This data is collected via class-specific risk details screens. Additional data can be submitted for inclusion in future releases by specific request and will be reviewed in line with the system data structure plans.
A premium (booked or paid) and claims (booked or paid) bordereau will report one row per section of a transaction.
The paid status requires the record to have had cash movement since the last time the transaction was reported.
NOVUS supports a number of export styles. These are the presentation styles that are either predefined by an industry-standard such as Lloyd's premium reporting standard or may be specifically designed to your company's or one of your underwriters' requirements. These bespoke bordereaux formats will require additional specification and costing, priced on the level of automation and complexity. It should also be noted that bespoke bordereaux may be better considered within the REPGEN reports program.
Taxes for soft currency transactions will show in source currency after conversion in both CR0064 and CR0083 Lloyds bordereau reporting styles
A bordereau can be created from records that match a number of criteria. Selection options appear in the top panel of the screen. The grid will report the relevant records found and will tag those records with the defined Bordereau ID (consult your own internal naming guidelines for this).
A bordereau can be saved, deleted, re-run and checked before posting.
NOTE: Once a bordereau is posted, the transaction records are not available to other bordereaux for the same combination (except for further cash movements on the same transactions). The posted bordereau will be available in the MATCH program for bulk matching cash.
NOTE: If the Bordereau ID has been posted in error, it will become locked and it will be necessary to contact a member of the Morning Data support staff via the support log.
Accessing an existing Bordereau
To access an existing bordereau, select the required bordereau ID from the drop-down list control. A LOV shows existing bordereaux and the yellow bar at the top of the results grid can be used to filter the list of results to quickly find an existing bordereau. . Once a particular bordereau has been selected, the fields are displayed with the original criteria used when the bordereau was created, and the lower part of the screen shows the transactions associated with the Bordereau ID. This screen could also potentially show a zero bordereau when no transactions exist for the selected Bordereau ID.
Once the results appear a label will appear to the right of the Bordereau ID field indicating whether the ID is a 'saved bordereau' or a 'posted bordereau'.
Once the set of transactions is displayed, a Bordereau Style can be selected from the LOV and the records can be viewed in an Excel spreadsheet on the selected style by clicking the Export button.
Saved bordereaux are automatically saved to the system when a query is run.
Clicking the delete button will delete the saved bordereau which has not been posted. Clicking delete will not delete the transaction(s); rather, the transactions are released to the system in order to be returned on another Bordereau ID if required.
Clicking the post button will lock the bordereau. Posted bordereaux can not be deleted as the delete button is disabled. It is also possible to post a zero bordereau. Posted bordereaux have a padlock icon to show that the details can not be modified or deleted.
Create a new Bordereau
To create a new bordereau, select the relevant parameters: partner, destination (banking) currency and other details from the drop-down lists. It is not necessary to enter any details into the Bordereau ID field; the Bordereau ID will auto-create with elements of the selected fields and can be customised once the user has selected a build option. The build option field becomes active as soon as the cut-off date field has been completed. Select the required build option and associated parameters before creating the bordereau.
|Bordereau ID||When creating a new bordereau, it is not necessary to enter any details into the Bordereau ID field, the Bordereau ID will auto-create with elements of the selected fields and can be customised once the user has selected a Build Option.|
|Partner||Select the account code of the party receiving this bordereau and whose transactions will appear on the bordereau. The drop-down list shows existing accounts. The Partner list of values excludes any partner records with a null suffix or revenue flag set to yes.|
|Currency|| Select the destination (banking) currency from the drop-down list. The bordereau program retrieves transactions in this destination (banking) currency.
The currency field refers to a single destination (banking) currency. A booked bordereau will report in destination currency. A paid (settlement) bordereau will report in destination currency e.g. a USD paid bordereau will report on all currencies that have been settled in USD and include return premiums converted to USD at the booked rate.
|Division||Select the division code from the drop-down list.|
|Type||Select the bordereau type from the drop-down list. The choice will affect the build options drop-down list in the build criteria section|
|Period||Enter the period associated with this bordereau in a valid format e.g. 1Q2021, 1H2021, 2M2021, 202102.|
|Supplementary|| Splitter (A-Z) - for supplementaries. Leave blank unless this is supplementary for a period already processed. To create a supplementary bordereau in an existing reporting period, the original bordereau should be loaded to the grid using the Bord ID list of values. The header fields will be read-only, and the ‘create supp’ button will display to enable the user to create a
supplementary bordereau to pick up new transactions for the reporting period that meet the original parameters. The bordereau ID for the supplementary bordereau will consist of the original bordereau ID appended with the sequential supplementary letter (e.g. LYDEURAPB-202107-A).
|Cut_off date||Select the required cut-off date. The 'incepting before' (date to) field includes items incepting up to and including the date entered.|
|Build criteria||The relevant criteria must be selected in the fields in this section. After completing the appropriate fields, the program performs the build and displays the transaction numbers in the lower section of the screen.|
|Build Option|| The build option field becomes active as soon as the cut-off date field has been completed. Select the required build option and associated parameters before creating the bordereau with optimised create time. Select the build option from the drop-down list. There are several ways to build the required set of transactions. For example, if Load by Facility UMR is the option, selected all appropriate transactions on this facility will appear. Greyed out entries indicate there are no transactions for these options. When the user tabs away from the Period field on a saved or posted bordereau, the Build Options are not cleared from the form.
Where master contracts span multiple years of account, all appropriate years are returned to the list of values (LOV), rather than a single year. The validation will check that the division parameter selected is included either in the risk header or in the binder scope for the master contract. If no transactions exist for the parameters selected, a null bordereau can be produced.
|Auto-ID Type:||Select custom or account, and - depending on the build option selected - contract number and year, facility ref or master ref to customise the bordereau ID on the new bordereau. Changing this type will change the format of the Bordereau ID as shown in the screenshot below. Choosing the custom option enables the creation of text input to the Bordereau ID to further customise the Bordereau ID.|
|Build Criteria||The build criteria field is visible from the program launch. If load by Facility/UMR or load by master reference is selected in the build option drop-down box, depending on the build option selected the criteria will display the relevant facilities or master references to select from the list.|
|Contract/Year||If Load by Lineslip or Load by Binder is selected in the build option drop-down box, depending on the build option selected the criteria will display the relevant lineslips or binders to select from the list.|
|Date From/To||If load by transaction entry date or load by inception date is selected in the build option drop-down box, then add the date(s) required|
|Bordereau style|| Select the required style. The styles have been configured by Morning Data in the CODES program. Each style is associated with a particular type of bordereau and only styles which match the current bordereau type can be selected.
NB: Bordereau Styles LK – Lloyd’s Premium Booked v5.2 and LN – Lloyd’s Premium Paid v5.2 have been aligned to each other and to the latest Lloyd’s coverholder premium Reporting standards. The earlier Bordereau Styles LB – Lyd Prem Reporting Tool Booked and LP – Lyd Prem Reporting Tool Paid have been retired and should no longer be used.
Once the criteria have been chosen clicking the Create button will build the bordereau with its associated transactions. If there are no transactions for the criteria, a zero bordereau will be created.
For all bordereau types except (paid), a transaction will only appear on a single bordereau. For paid bordereau the transactions appear by instalments, and if the previous bordereau has not been settled (matched on the underwriter side) the transaction/instalment will still be outstanding and will appear on the next bordereau.
Once the set of transactions is displayed, a bordereau style can be selected from the LOV and the records can be viewed in an Excel spreadsheet on the selected style by clicking the Export button.
The drop-down list will only offer the styles appropriate to the bordereau type (i.e. a booked style can not be selected for a paid bordereau type). If a zero bordereau is displayed on the screen the zero bordereau style will be the only option offered for export to Excel.
Whilst it is in the un-posted state the bordereau indicator will show the 'saved bordereau' indicator next to the Bordereau ID.
NOTE: The bordereau can be deleted up until the point it is posted. The delete bordereau button will remove an unposted bordereau from the system. After posting, the bordereau can no longer be edited or deleted.
NOTE: The bordereau cannot be reproduced after posting and cash is matched as if fully settled there is nothing new to report. Bordereaux should be saved if they are to be preserved.
Claims settlement bordereau
On the claim bordereau types in OUTBORD, where the policy basis on a risk is 'claims made', column CR0119 'date of loss from' and CR120 'date of loss to' will output the dates captured in the incident dates fields in the claim entry.
On the claims bordereau, all underwriter debit amounts can be shown on the claim settlement bordereau regardless of whether or not they have been settled by the client. This is so that the underwriter can offset refunds of claims against claims.
Where the row being reported on the claims bordereaux is in respect of a declaration attached to a Lineslip, or an off-policy attached to an in-house binder, the dates being output in CR0008 binding authority contract inception date and CR0009 binding authority contract expiry date will output the inception/expiry of the master contract.
Claims settlement bordereau now includes all credits, whether the opposite side is settled by the client or not. If any partners are missing their suffix, they will be missing from the partner list of values.
v 6.3.0 – Updated to the latest version
v 6.2.0 – Updated to the latest version
v6.1.0 – Updated to the latest version
v6.0.0 – Updated to the latest version
v4.4.0 – Updated to the latest version
v4.2.0 – Updated to latest version
v59K - Warning added. Records may be added with the second build.
v58K - Div_code reinstated. v57J- Bug in insert_date fixed for booked claims. v56J - Current version of this form
v55K - change not known
v54K - Insert to bdr trigger statement split into two for booked and paid
v53M - Inward bordereau implemented. Splitter displayed in lower block
v31T - First version of this form to use the new style. No other updates except the restyle.