There are many reasons why a transaction may not post in Job Cost, some common causes are:

• The transaction has a future accounting date.  (The accounting date on the transaction is more than one month into the future from the current month in Job Cost).
• The transaction needs to be manually posted. (Some transactions may be available to post, but need to be manually posted. This can be caused by a transaction previously not posting due to a rejection, the transactions application of origin has the interface settings to Job Cost set to manual post, or a task in Job Cost is setup for manual posting of transactions such as imports.)
• The software suddenly closed, or aborted during data entry and there is a locked file at the server.

To check if you have unposted transactions in the new file, perform the following:

1. In Job Cost, go to Inquiry, Entries, All Entries.
2. On the Transaction File Selection window, select New, then click OK.
3. The Inquiry window that appears will list all unposted transactions.
4. If there are a large number of unposted transactions, and you are searching for a specific job/transaction/batch/etc, this inquiry can be conditioned just like other inquiries. 

To see why unposted transactions haven't posted, perform the following:

1. In Job Cost, go to Tasks, Post Entries.
2. In the Print Selection window, select Printer Setup, and either select the printer you would like the posting journal to print to, or you can select the Print to file option for the posting journal to be created as a text file, and use the Select File button to choose the name and file location. Click OK once you've made your selections.
3. The next step will post all available entries that are able to post. If you have entries that you don't want posted, or you would like to test a specific transaction, use the Ranges button and make your selections before proceeding.
4. Click the Start button and wait for the task to complete.
5. Check your posting journal. If you selected Print to file, go to to File, Printouts, and browse to the file you designated.
6. On the posting journal, transactions that read Rejected could not be posted.  With each rejected transaction, there is a reason printed that states why the transaction could not post.
   Note: If the reason states the accounting date on the transaction is further than one month into the future from the current month in Job Cost, go to File, Company Settings, JC Settings, Current Month, and compare that value to the accounting date which is associated with the transaction. Job Cost will only post out one month from the current month, so closing the month(s) to get the desired transaction with the correct time frame may be appropriate.

Note: If your journal printout doesn't show any rejections, the unposted transactions may have just required a manual post, and all items posted normally.

If your job cost entries are not posting and there is no rejection reason on the Posting journal, it is possibly due to a file in use, or a lock file at the server level. 

To determine if it is a file in use issue:

1. Have everyone exit the software and attempt to post your entries. If your entries do not post, attempt step 2.
2. While everyone is out of the system either remote in or go to the file server machine and open the Pervasive Monitor Utility and  check for open sessions.  For detailed information on how to do this, refer to How do I use the Pervasive Software Monitor utility (PMU/PSMU) to unlock or close a file on a remote file server from a workstation? linked below.