Processing Transactions
This topic presents a brief overview of how posting, day-end processing, and audit trails relate to transaction processing in Inventory Control. The types of transactions in Inventory Control are receipts, shipments, adjustments, stock transfers, and item assemblies.
Online posting or batch processing
Inventory Control lets you choose between online transaction processing or batch processing for posting all kinds of transactions.
You can either:
-
Post each transaction when you enter it.
or
-
Save transactions after entering them for later editing or posting (using the Post Transactions form).
When you post a transaction, the program immediately updates item quantities so you always know your inventory levels. This is especially important when you are using Order Entry and need to know whether an item is in stock.
Costing — during posting or at day end
Depending on your program settings, posting will also update the cost of goods in stock and the cost of goods that you've sold. Posting, however, does not update accounting and statistical information—those procedures are performed by Day End Processing.
Note: With Inventory Control, you can choose in I/C Options whether you want the program to recost items based on newly posted transactions, or whether it should wait until you run day-end to cost items.
If you have a large transaction volume, we suggest that you cost items during Day-end.
You must run Day End Processing to update item and sales statistics, audit information, and to generate general ledger transactions.
If necessary, you can run Day End Processing several times a day to keep this information more current.
As well as posting transactions to the current session date and reporting period, you can post them to past or future dates and reporting periods.
Printing the audit trail
To view your audit trail for transactions, print the posting journal for the type of transaction you want, after running day-end processing.
If you selected the Keep Transaction History option in the Options form, the program keeps another copy of the audit trail information that is printed on the posting journal. You can then print the Transaction History report to list audit trail information that you may have cleared from the posting journal.
See also
Processing internal usage transactions