Note:
The journal entry printout is a legal requirement, usually done each month. It is a history list based on the Italian G/L transaction summary file indicating all accounting transactions done in the fiscal year, day by day. The printout can be performed in simulation mode or definitive mode. When it is printed in definitive mode, the system updates the Italian Opening balance value file with the page number, the journal line number, the last accounting period printed in definitive mode and the credit and debit balances. For each transaction, the following is displayed:
- journal line number
- transaction date (voucher date)
- document number
- document date
- ledger accounts
- transaction description
- debit and credit amounts for each separate ledger account
The page numbering is consecutive for each year and is indicated on each page (e.g. 2011/1, 2011/2, 2011/3, etc.).
If errors exist in the journal, then you delete the accounting period in the Journal entry printout – cumulative data program, and re-print the period in definitive mode. In this program you can maintain the opening balance for a printed accounting period.
The Journal entry printout functionality is also used for a company about to “go live” with a new software system. In the Journal entry printout – cumulative data program, you manually enter the journal’s first accounting period that should apply for the company in the new system. The last balance, the last journal line and the last page printed in definitive mode in the “old” system must also be set up and retrieved into the new system.
Prerequisites
Activate the Italian journal selection (IT-BTRSEL) function in the Function control file to have the possibility of selecting a routine ID when retrieving transactions from the Accounting file for printouts. If this function is inactivated, then all routine ID’s are selected.
When you run this program, the system checks if the following exists for the specified accounting period:
- Transactions that have not been transferred into the accounting
- Interrupted batches
- Journals in error
- Interface accounting transactions from pre-systems
- A/P batch input file, invoices
- A/R batch input file, invoices
If any of these transactions are found, then the system first prints a detail list. The second printout contains the journal entry transactions.