Transaction Entry and Posting

Use the Transaction Center to enter and post accounting transactions.

You can enter transactions daily, weekly, or whenever you have a number of transactions to process. How often you enter transactions depends on your accounting and reporting requirements and procedures.

After you enter transaction data, it becomes available for posting. When you post the transaction files created during Transaction Entry, you make the data a permanent part of your DPS database. You can then use this data for additional processing, such as overhead allocation and revenue generation, and for reporting.

You do not need to post transaction files each time that you enter data. If you have unposted transaction files, you can open them and add more data. For example, you may want to enter accounts payable vouchers daily, but post them weekly or biweekly. You can create an accounts payable vouchers transaction file for the selected period and open it daily to add new data. At the end of the period, you post the file, which contains all transactions for the period.

Because transaction data must be posted to be available for reporting, the financial data on reports is only as current as the most recent postings.

Review Transaction List

You can review transaction data by printing a Transaction List report, which displays all transactions in a transaction file. You should print and review a Transaction List report prior to posting any transaction file to your database.

The Transaction List report provides you with a tool to check the validity of the data that you entered. Data is usually valid at the time of entry; however, there can be a gap between when transactions are entered and when they are posted. In this period of time, changes may be made to the database (for example, a project number that you referenced may be closed out), rendering transactions invalid.

Review Posting Log

DPS produces a posting log each time that you post a transaction file. Use the Posting Log to review all information for a batch of transaction files posted to your database. You may find this information useful for tracking specific groups or types of transactions. You can print a posting log immediately after posting a transaction file or at a later date.