If an electronic report submitted against your permit contains an error, all your ER contact persons will receive an email notification requesting that these errors be corrected within 15 days. If the error has not been corrected after 7 days, a reminder email will be sent. There will also be a widget on your Dashboard in the top right-hand corner called ‘Electronic Reporting Errors’.

Error Widget

This widget will show you the total number of errors found in your electronic reports.

Error Widget

The errors are broken down into age, with errors older than 15 days showing in red text to convey urgency as corrections should be made within 15 days to comply with regulation 44 of the Fisheries Reporting Regulations 2017 and, if not, will be referred to the MPI for further action.

Error Types

There are two types of errors:

Trip errors

Trip errors could relate to any of the reports within the trip and may not be specifically related to a report at all. An example of a trip error:

ErrorDetailAction
Trip has no Trip Start report This means that we have received a report with a trip ID that does not have a corresponding Trip Start report.
  1. If the Trip Start report has not been submitted for whatever reason, the skipper would need to refer to the eLogbook they use for reporting and submit the Trip Start report.
  2. It may be that the report has an incorrect trip ID, in this case a user with authority will need to amend the report and correct the trip ID in Kupe.

Report errors

Report errors are errors that are related to a specific report, this could be that incorrect data has been recorded or the data recorded is unusual and needs to be reviewed. An example of a report error:

ErrorDetailAction

Report type: Non-Fish or Protected Species report 

Error: This report has no associated catch report

This error relates to a Non-Fish or Protected Species (NFPS) report that does not have a valid fishing report event ID provided, but the date of the NFPS report falls inside the dates of a fishing report in the same trip e.g. Trawl report began at 8am, and finished at 11am and NFPS capture occurred at 10am.
  1. If the NFPS capture occurred outside of the fishing time, a user will need to amend the report and correct the report time in Kupe.
  2. If the NFPS capture occurred during fishing activity, a user will need to amend the NFPS report and provide the event ID of the fishing report in which the capture occurred.

Back to top

Viewing and Correcting Errors

Only users with ER Admin or ER Manager rights, or the ER Reporter who submitted the original report have access to correct errors on reports.

To view trips and reports that contain errors, you can click on the ‘View details’ link in the ER Errors widget.

Error Widget

Alternatively, you can navigate to this screen via your Dashboard > ER tab > Trip Summary in the left menu and tick the ‘Show trips with errors only’ filter.

All trips where an error has been found will show in a grid.

Hover your mouse over a trip and notice that each line will highlight slightly, and the cursor will become a hand icon. This means you can click anywhere on the line to expand the details. Click anywhere on the same line again to close.

Trip Summary

Trip errors will show above the individual reports as these errors may not be directly related to a specific report.

Report errors will show in the Errors column in the grid against the report they relate to.

Trip Summary

Each report will have a ‘View’ and ‘Amend’ option under the Action column. You will be able to amend a report within the ‘View’ mode however if you choose ‘Amend’ this will take you straight to the amend mode for the event. A list of errors will be displayed in a banner at the top of the report, and each error will also be highlighted within the report.

Banner Example

Back to top

Correcting, Confirming and Suppressing

Errors can be fixed in three ways, by correcting the data, confirming the data or suppressing the data.

Correct - Some errors can only be fixed by correcting the data to a correct value.

Error Example

Confirm - Other errors can be fixed by either correcting the data or confirming that the data that was provided is correct by clicking on the confirm button next to the error. These are usually errors where the data provided is outside of the normally expected range.

Confrim Error Example

Suppress - Some errors also have the option of being suppressed. You would suppress an error if the value that you provided is correct and is part of your everyday fishing practise. By suppressing the error, you will prevent the error from being generated on any reports that you provide for the next year. After a year, the error will be generated on your reports again and can then be suppressed for a further year, if it is still part of your fishing practise.

Suppress Error Example

After correcting any errors, you can tick the "" tick box instead of typing in a reason for amendment. You can also add additional text into the reason for amendment if you want to.

Tick Box

Once you have submitted your amendment, you can view the ‘Electronic Reporting Errors’ widget or the Trip Summary screen again and you will notice the number of errors has reduced.

If data that is causing an error is updated, but still does not fix the error, the error will remain in your Errors widget and the date by which it must be fixed will not change. If you change existing data and introduce a new error, you will be able to submit your amendment, but the errors will then appear in your Error List and you will receive an email advising you of new errors.

Important to note:

Notifications of errors are sent by FishServe once per day at 9pm. However, they will show in the widget and trip summary approximately half an hour after they have been submitted. You have 15 days from the date of this notification to correct any errors to avoid possible infringement by MPI.

Back to top

List of Checks

ErrorDescriptionTypePossible solution
This trip has no Trip Start report. An event has been reported, but there is no Trip Start record containing the same Trip ID. Trip Submit a Trip Start report or correct the trip ID of the Trip Start or other report
This report has a date that is before the Trip Start date The date/times provided for this event is prior to the date/time reported in the associated Trip Start record Event Correct the date or time of the Trip Start or the other report
This report has an invalid catch report associated with it. This event has an invalid catch event associated with it Event Correct the linked fishing event ID to an existing fishing event within the trip
This report has a date that is after the Trip End date The date/times provided for an event are after the date/time reported in the associated Trip End report. Event Correct the date or time of the Trip End or the other report
This report overlaps with effort in Trawl report - {trawl report} Vessel has more than one trawl catch event at a point in time. Event Check the dates and times of the two catch reports and correct the one in error to remove the overlap
This report has an invalid catch report associated with it. The catch event ID given for a disposal event is invalid. Event Correct the linked fishing event ID to an existing fishing event within the trip
This report has no associated catch report. The catch event ID has not been provided for a disposal event. Event Link the Disposal to a catch event within the trip
This trip has no Trip End report. A Trip End report has not been provided within {4} days of the last Event report for that 'Trip ID'. Trip Submit a Trip End if the trip has ended. If the vessel is still on a trip this error can be ignored and will go away when the next report is submitted for the trip
This report has no associated catch report. A NFPS Catch Report has been received that occurred during a reported Catch Event and does not provide a link to a Catch Event. Event Link the Catch Event to the NFPS event. If the NFPS interaction was not related to the fishing at the time, then use the confirm button to confirm this
The Codend Mesh Size {X}mm is outside the expected range of {Y}mm - {Z}mm. A non-precision trawl has reported a codend mesh size that is either less than {Min}mm or greater than {Max}mm. Event Correct, confirm or suppress the error
Vessel Pair number is not expected for the fishing method {fishing method}. A pair vessel ID should only be present when a pair method is used. May indicate incorrect method code or misuse of field. Event Check your fishing method - If you were not pair fishing then remove the paired vessel number
Target species {code} - {name} is not expected while trawling. The reported Target Species Code is unexpected for a Trawl event. Event Correct, confirm or suppress the error
Codend mesh size should be 0 for Precision trawling. A precision trawl has reported a codend mesh size that is not zero. Event Check your fishing method - If you were using precision trawling then the codend mesh size must be 0
The Total Estimated Catch is {X} than the sum of the estimated catches by species. Check to make sure that the reported Total Estimated Catch is greater than the sum of the reported estimated catches by species. Event Check your total estimated catch and your estimated catches by species and correct where necessary
Vessel Pair number is expected for the fishing method {fishing method}. A vessel pair number has not been provided when the reported fishing method indicates a pair trawl method was used. Event Check your fishing method - If you were pair fishing then provide the paired vessel number
Ground rope depth {X}m is more than the bottom depth {Y}m. A trawl event has reported a ground rope depth greater than the reported bottom depth. Event Check your ground rope depth and bottom depth and correct to ensure that the ground rope depth is not greater than the bottom depth
NFPS catch declared but no NFPS report has been submitted. A catch event report has “yes” for the ‘Is NFPS catch present?’ field, but there has been no NFPS Catch Report provided with a matching ‘Fish Catch Event ID’. Event If there was no NFPS interaction then change the Yes to No, otherwise go to the NFPS Protected species Report and link it to this report
Vessel pair number {vessel number} is same as main vessel number. A vessel pair number has been provided that is identical to the vessel number for a pair trawl event. Event Check your fishing method - If you were pair fishing then provide the correct paired vessel number
Calculated trawl speed {X} knots is over {Y} knots. The start and end positions and times of a trawl event indicates a speed exceeding {Max} knots, which is unlikely. Event Check your start and end date/times and positions and then correct, confirm or suppress the error
Number of nets {X} is more than {Y}. Check on unusual number of trawl nets reported. Event Correct, confirm or suppress the error
NFPS catch not declared but NFPS report has been submitted. A Catch Event Report has “no” for the ‘Is NFPS catch present?’ field, but a NFPS Catch Report has been provided that links to that catch report. Event If there was an NFPS interaction then change the No to Yes, otherwise go to the NFPS Protected species Report and remove the link to this report
Trawl bottom depth {X}m is not between {Y}m and {Z}m. A trawl event has reported a bottom depth that is either less than {Min}m or greater than {Max}m. Event Correct, confirm or suppress the error
Trawl headline height {X}m is more than {Y}m. A trawl event has reported a headline height that is either less than {Min}m or greater than {Max}m. Event Correct, confirm or suppress the error
Trawl wing spread {X}m is more than {Y}m. A trawl event has reported a wing spread that is either less than {Min}m or greater than {Max}m. Event Correct, confirm or suppress the error
Declared trawl speed {X} knots is not between {Y} knots and {Z} knots. The declared speed of a trawl event is outside a range of {Min} to {Max} knots. Event Correct, confirm or suppress the error
Calculated trawl duration {X} hours exceeds {Y} hours. Trawl duration exceeds {Max} hours. Event Correct, confirm or suppress the error

Back to top