| 1. Check decimal places in posts (2 decimal places allowed at most) |
Either due to a malfunction of the program in the previous build, either because user processes can be between accounting entries such with more than two decimal places. These entries can then be candidates for the calculation of the exchange rate differences, accrued exchange differences are so small that calculation shows the value of 0,00. Control allows automatic correction of such entries. |
|
2. Check debit/credit amounts in posts - where debit and credit are both 0
|
The absence of these controls in previous versions of Pantheon (eg. 5.0) allowed to be located between the accounting entries such as where debit and credit simultaneously 0. Such postings need to be manually fixed (delete or insert or debit or credit).
|
| 3. Check for differences between debit/credit amounts and foreign currency debit/credit amounts if using primary currency |
Due to an error in the program or user procedures may be incurred entries, where debit and foreign debit or credit and credit foreign currency are the same, but currency exchange rate different. These entries can lead to false translation of open receivables/payables on opening journal entries! Check allows automatic correction of such entries. |
| 4. Checks for unbalanced accounts |
Account locates entries, which should according to the account settings in the script or chart of accounts balances (debit - credit = 0), respectively in the scenario, or the chart of accounts indicate that the account must have set Balance must be 0. |
| 5. Referential integrity check |
Checks whether there is the chart of account, contra account, subject department, cost center and the currency being at positions journal, so if we have the rof example: the cost center from journal in cost center register , etc. Control allows automatic correction.
Check referential integrity (a tool for that is in the Administration Panel) enables program a truly functioning correctly and that all accounts and reviews really capture the true data. To alert the user that they are not put in place all the relationships in the database to enable the proper functioning of the program. |
| 6. Check for exchange differences |
There are users that exchange differences credited manually. In this usually bring some internal code to link document information. Checking the end of the year or the automatic posting of exchange rate differences in the program, despite manual posted exchange rate differences such entries showing among the candidates for the calculating of foreign exchange differences.
Proper manual posting of exchange rate differences will be available in the next build. It is currently necessary to use automatic procedure for exchange rate differences.
|
| 7. Check debit/credit amount in posts - mark those where debit and credit are both non-zero |
Similar check as check 2. Here we have to manually fix the entries where both debit and credit is different from 0. |
| 8. Check debit/credit and foreign currency debit/credit - mark those where debit is not zero and foreign currency credit is not zero and vice versa |
Mark those where debit is not equal 0,00 and foreign credit not equal 0,00 and vice versa.
Similar checks as 2 and 7. It is necessary to manually fix the entry.
|
| 9. Check for open set-offs by comparing due dates |
When set off is not confirmed due date at journal is blank. Unconfirmed set-offs must be deleted before the end of the year and remake them after the end of the year. |
| 10. Remove unnecessary trilling spaces in columns |
The database, program and user processes are enabled (permit) in addition to the data are stored with a space, they followed. This leads to abnormalities in the collection and presentation of data, for example unnecessary gaps in the print account cards etc.. Check also allows automatic deleting these extra spaces.
Controls can be exploited to control data of the current year, not to make the closure of the year. Automatic Error Correction allows corrections of those errors in the current year. |
| 11. Checks whether the account exists in the scenario - post exist |
It is possible that document for closure of fiscal year is opened in advance. In document type we have not marked that Scenario Harmonized with Chart of Accounts. Then insert a new account in the chart of accounts and use it for booking. At the end of the year that account is not in scenario when preparing closing of fiscal year. Control will be alerted us.The account can be entered in scenario manually or by clicking on the button Prepare Scenario. Scenario will be in line with chart of accounts. |
| 12. Checks whether exchange rates for Dec 31 exist (in case of FCY posts) |
In order to calculate exchange rate differences for open items it is necessary to have exchange rates for foreign currencies in the register. Courses need to be entered manually or downloaded from the internet. |
| 13. Check accounts designated as subsidiary accounts and compare between the Chart of Accounts and the Administration Panel |
Many users have in administration panel entered suppliers and customers accounts. In the chart of accounts and the scenario has same accounts marked as general ledger account, that subject is not mandatory information. For this reason, it may happen that the entries in the closing and opening journal wrote in the summary amount and not at subjects and the linked documents. Therefore, closing the open positions in the next fiscal year will not be possible. This control will warn us and to enable to manually fix the settings in the chart of accounts respectively scenario. |
| 14. Checks posts for incorrect or incomplete keys |
The program finds 'weird' records, for example. 10- -000001, etc.. These records are in the program not visible (they are not taken into account in the printouts gross balances, open items, etc.). They are likely to be incurred due to an error. |
| 15. Checks posts that are not included in year-end. The first year-end must include all posts in the program since the last change of the primary currency. Are the dates set correctly? |
 If the user works from before 2007 (before EUR), must first finish for several years together (2007-2011, in the case of the first end of the year).
|
|
16. Check if exchange rates for primary currency are specified. Exchange rates for the primary currency must be specified in the journal entry. This checks and automatically adds missing exchange rates.
|
 Entered should be currency exchange rates for EUR on 1st of January, 2007, when the state gets new local currency. EUR on 1st of January, 2007 =1. |
| 17. Checks posts for missing currencies. Posts without a currency can leas to problems with some calculations and reports. |
Control is result of the error in the program, as some wrote some entries with empty value of the foreign exchange rate. |
| 21. Checks if exchange rates contain the rate 0. Because of such exchange rates, year-end might not be correct. |
Check verify if register contains exchange rate 0. If the currency exchange rate is entered 0, year-end will not be made properly. |