This guide covers how to record actual profit on a government account ticket in HITS without changing the ticket total the customer sees.

1. Standard Workflow: Recording GP on a Government Ticket

Use this process any time a government account ticket is waiting on a vendor credit and GP needs to be tracked on the ticket without changing what the customer is invoiced.

1. Batch close the ticket so the customer sees it as an invoiced/closed ticket.
2. Internally, leave the ticket open (in Batch state) so GP can still be tracked against it.
3. When the vendor credit arrives, reopen the batch ticket.
4. Add a new line item using the NAC code (or your specific Government Credit Code).
5. Set the line item quantity to –1 (negative one).
6. Set the line item cost to the credit amount as a positive value and leave the price 0.00.
7. Save the ticket. The credit adjusts GP dollars without changing the ticket total.

 

Key reminder Quantity is negative. Cost is positive. This is the detail most likely to be entered backwards; double-check before saving.

2. If the Ticket Is Accidentally Closed First

Sometimes the batch-closed ticket gets fully closed before the vendor credit is posted. If that happens:

• Create a separate $0 ticket.
• Add the same line item to it: negative quantity, positive cost, 0.00 price, matching the credit amount.
• Reference the original ticket number in the comments of the new $0 ticket so it’s traceable back.

To reduce how often this happens, add a note directly on the ticket flagging that it’s awaiting a vendor credit, so it isn’t closed out prematurely.

3. GP % Permission Changes

GP visibility had previously been removed from view. Permissions can be updated to restore GP access for anyone who needs to view it on government account tickets and all other areas in HITS®, while keeping it restricted for roles that don’t require it.

• Grant GP access only to roles/users who need visibility into gross profit on these tickets.
• Users granted access need to log out and log back in for the permission change to take effect.
• If the permission change is made in a backup or test copy of the system, confirm it is also applied in the live/production system.