Job Transactions
Entering transactions is one of the more important activities you do in managing and tracking job costing. You enter transactions to record costs, such as charges directly associated with material or labor, and to record invoices or bills sent to the customer. Some transaction data must be entered through Job Cost windows, while other data must be entered through Microsoft Dynamics GP windows. These require that specific Microsoft Dynamics GP modules be installed. Once entered, individual transactions can be posted immediately (transaction-level posting) or saved in batches for posting later (batch posting). If transactions are saved in batches, they do not affect any general ledger or Job Cost accounts until the batches are posted. This allows you to review the transactions, print edit lists, and correct errors before posting.
IMPORTANT
- For purchase orders, inventory, payables, and job cost transactions, the job number and cost element will display with the general ledger account distribution associated with the transaction wherever account distributions are displayed. This applies only if the journal entry for each type of transaction is set up to be created per transaction, and not per batch.
- The general ledger account distribution for the job will not display if you change the account number during purchase order, receivings, or inventory transaction entry.
- Though you can void, copy, or correct a General Ledger transaction entered in Service Management or Job Cost, the transaction information will not be updated in Service Management or Job Cost.
IMPORTANT
With Cost Plus job transactions:
- A cost transaction can only be voided if you have not invoiced the job.
- A cost transaction cannot be voided once the job has been invoiced. If you need to void a transaction AFTER the invoice has been posted to the job, you must create a credit memo for the invoiced amount and apply the credit memo to the original invoice. See Applying Credit Memos to Job Invoices.
See also: