If the future Job Cost entry has the correct date, close Job Cost until it is in the current month. To close the month in Job Cost, from the Tasks menu, select Close Month.
If the future Job Cost entry has an incorrect date, complete the following steps:
Note: This solution is for future entries created in Job Cost. If the entry is from an interfacing application, the entry needs to be corrected in the originating application. If you complete the following steps for entries from interfacing applications, your corrections may cause interfacing Sage Timberline Office applications to become out of balance.
- In Job Cost select Tasks, Post Entries
- From the Inquiry menu, select Entries, Entries by Batch.
- Select New and then click [OK].
- If the new file contains more than the batch with the future Job Cost transaction, review the posting journal for errors. Correct any errors and post again. The batch with the future Job Cost transaction should be the only batch that appears in this inquiry.
- If the new file contains only the batch with the future Job Cost transaction, rename the new file only after verifying that nobody is using any Sage 300 CRE applications that may post to Job Cost during the rename:
- In Job Cost select Tools, File Tools.
- Select Rename and then click [Next].
- Verify the Look in directory is the correct data folder and then select the New.jct file.
- In the New file name box, type a new name for the file. For example, New10-24-13. Do not include the file extension.
- Click [Next], and then click [Start].
- When a message appears to indicate that the file was successfully renamed, click [Finish].
- Print a Job Cost report (such as the Job Cost as of a Specific Date report) to verify that the correct cost transactions print.
DocLink: Enter direct costs in Job Cost and how it affects General Ledger
|