Overview

Once delivery tickets have been posted, they are no longer viewable in the Delivery Ticket List View and cannot be edited. In order to reprice a delivery ticket tax or premium, the user must choose the appropriate function from the More Actions toolbar drop-down menu in the Delivery Ticket List View and follow the steps laid out below. Using the Premium Reprice function will reprice a specific premium or tax based on criteria on the applicable delivery tickets within the criteria parameters.

Understanding the data flow

When delivery ticket premiums and/or taxes are repriced, upon updating to “Ready to Post,” a NorthScope journal entry will be created and sent to the host system’s Financial module for every affected Delivery Ticket and the affected NorthScope settlement transaction(s) will be updated to reflect the new balance(s).

Step 1: Repricing the delivery ticket premium and/or tax.

In order to reprice a delivery ticket premium or tax, the user must first expand the Purchasing module in the navigation menu and select 'Tickets'. This will open the Tickets List View.

...

• Accrual Date: This field defaults to today’s date and determines the date the changes will affect the general ledger.
• Comment: This field is for manual entry of any notes regarding the reprice, such as the reason for the reprice.
• Date From: This field defaults to the date a year prior to today’s date and determines the earliest premium(s) and/or tax(es) shown.
• Date To: This field defaults to today’s date and determines the latest premium(s) and/or tax(es) shown.
• Delivery Number: This field is for manual entry of the delivery number to which the premium(s) and/or tax(es) for reprice correspond.
• Fisherman: This field is to select the fisherman to which the premium(s) and/or tax(es) for reprice correspond. This field displays a drop-down menu and offers a list of all active fishermen.
• Gear Type: This field is to select the gear type to which the premium(s) and/or tax(es) for reprice correspond. This field displays a drop-down menu and offers a list of all active gear types.
• Include Tickets: This field is to set the criteria for the premium(s) and/or tax(es) included in the grid based on whether or not they have an RSW temperature associated with them.
• Net # Tickets: This field auto-populates once a line item has been selected and validated to display the number of tickets to which the line item applies.
• Premiums: This field is to select the premiums to which the premium(s) and/or tax(es) for reprice correspond. This field displays a drop-down menu and offers a list of all active premiums configured in the system including both manually and auto assigned premiums.
• Season: This field is to select the season to which the premium(s) and/or tax(es) for reprice correspond. This field displays a drop-down menu and offers a list of all active seasons.
• Specie: This field is to select the specie to which the premium(s) and/or tax(es) for reprice correspond. This field displays a drop-down menu and offers a list of all active species.
• Stat Area: This field is to selection the stat area to which the premium(s) and/or tax(es) for reprice correspond. This field displays a drop-down menu and offers a list of all active stat areas.
• Temp Range: This field is for manual entry of the lowest and highest temperatures associated with the premium(s) and/or tax(es) included in the grid.
• Tender – Delivered: This field is to select the tender that delivered the item(s) associated with the premium(s) and/or tax(es) for reprice. This fields displays a drop-down menu and offers a list of all active tenders.
• Ticket Class: This field is to select the ticket class to which the premium(s) and/or tax(es) for reprice correspond. This field displays a drop-down menu and offers a list of all active ticket classes.
• Ticket Number: This field is for manual entry of the ticket number to which the premium(s) and/or tax(es) for reprice correspond.

...

After processing, the user may close out or continue to reprice items as the Ticket Reprice window will remain open.

Note: Once a ticket has been repriced, the original version of the ticket will be updated to a status of Replaced and the new version of the ticket will be Posted. 

Step 2: Posting the journal entry in the host system.

Upon processing, a NorthScope journal entry is created for each affected Delivery Ticket and each journal entry is then sent to the host system if the Purchasing Preference for “Enable Real Time Integration” is set to “Yes”integration for journal entries is turned on. The journal entry will appear in the host system's Financial module as a Transaction Entry in the batch titled NS followed by the year, month, and day with the following format: NS: YY_MM_DD. For example, if the reprice was integrated on July 14, 2015, the Batch ID for the transaction entry would be NS: 15_07_14. 

Each Delivery Ticket reprice journal entry description will be the NorthScope journal entry number followed by the NorthScope transaction ID followed by the NorthScope transaction name (i.e. 12345: Ticket Adj: (Ticket Number)-v(version number)).

Journal entries for repriced taxes

One credit line summarizing the difference between the original tax amount and the repriced tax amount for each unique repriced tax’s “Credit Account.”

One debit line summarizing the difference between the original Delivery Ticket amount and the repriced Delivery Ticket amount to the fisherman’s “Settlement Accrual” account.

Note: If the tax reprice reduces the price of the tax, the accounts debited and credited will be the opposite.

Journal entries for repriced premiums

One debit line summarizing the difference between the original premium amount and the repriced premium amount for each unique repriced premium’s “Debit Account.”

...

One credit line summarizing the difference between the original Delivery Ticket amount and the repriced Delivery Ticket amount less the difference in taxes for the fisherman’s “Settlement Accrual” account.

 Note: If the premium reprice reduces the price of the premium, the accounts debited and credited will be the opposite. 

Once the user is satisfied that all the GL Distributions are correct, the user can post the batch in the host system.

Note: Although this step is required, it does not need to be done for each transaction. Posting can be done nightly or as needed.

Step 3: Reviewing in NorthScope.

Whether or not Step 2 is complete, the following will occur in NorthScope:

...