Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel3
indent50px
stylecircle

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.

...

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 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.”

...

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.”

...

 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:

...