Future date

The accounting date on the transaction is more than one month into the future from the current month in Job Cost.

Manual posting

You need to manually post the transaction. Causes include:

• A transaction previously not posting due to a rejection
• In the transaction's application of origin, the interface settings to Job Cost designate a manual post
• A task in Job Cost uses manual posting of transactions, such as imports

Software aborts

The software suddenly closed, or aborted during data entry, and there's a locked file at the server.

Check for unposted entries

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. Condition the inquiry as needed. 

Confirm cause of entries not posting

1. In Job Cost, go to Tasks, Post Entries.
2. In the Print Selection window, select Printer Setup.
3. Select the printer you want to use or select the Print to file option.
4. Click OK.
5. Use the Ranges button to limit which entries post if you don't want to post everything in the new file.
6. Click the Start button and wait for the task to complete.
7. Check your posting journal. If you selected Print to file, go to File, Printouts, and browse to the file you designated.
8. On the posting journal, transactions that read Rejected couldn't post. With each rejected transaction, there's a reason printed that states why the transaction couldn't post.

Solutions for unposted files

Future date

If the reason states "[date] is beyond next month", go to File, Company Settings, JC Settings, Current Month. Compare the current period there to the accounting date on the transaction. Job Cost will only post one month ahead of the current month. See possible solutions for the date issue.

Post manually

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

Check for locked files

If your entries don't post and there's no rejection on the journal, the file may be in use or locked at the server. 

1. Have everyone exit the software and attempt to post your entries. If your entries don't post, continue to step 2.
2. While everyone is out of the system, use the Pervasive Software or Zen Monitor Utility to unlock files on the server.

Error: "File in Use" or "Record in use"

I posted in Job Cost, but the batches are still in the ranges in the posting task.

AP transactions are not showing in Job Cost