Service tool Transactions (General Ledger) is located in Accounting section (Accounting - Service Tools - Transactions (general Ledger):
Document's form:
Main tab:
General Ledger tab (with Add command it is possible to record transactions):
Using this document allows for the creation of accounting and tax entries.
Caution: Before proceeding with manual adjustments, keep in mind:
Manual adjustments should only be made in exceptional circumstances where automatic reflection of a business transaction via a configuration document is not possible (e.g., the necessary document is unavailable). In such cases, a manually entered operation should be used.
Note that manual adjustments using the Transactions (General Ledger) document do not record any entries into system registers (Information registers, Accumulation registers).
This is how the document is implemented in the ERP system:
The Transactions (General Ledger) document cannot be posted, which means it cannot write data to information registers and accumulation registers that are used for generating internal reports in the system. It can only be saved. Once the data is saved in the Transactions document, it will be recorded in the General Ledger Accounting register only.
To review records in the General Ledger Accounting register in a custom mode, the user should use the Dr/Cr command:
The correctness of accounting in the program may depend on manual editing of entries in a posted document. Such operations require special attention and responsibility for the changes made. Before making adjustments, it is necessary to analyze the situation, think about which documents will automatically generate the necessary transactions and movements of accounting registers.
The main way to reflect business transactions in the program is to enter configuration documents corresponding to the primary accounting documents. In some cases, for individual business transactions, it is necessary to change the postings and/or movements in registers generated when posting a document. Data about entered transactions is stored not only in accounting accounts, but also in special registers that the program needs for correct operation. Data duplication is necessary for reporting.
For example, if an accountant decided to record a business transaction manually. The result was a correct balance sheet, visually everything was in its place.
What could go wrong? Submitting reports. When the accountant generates reports, he will be able to see the results of such operations entered manually. Data entered manually will change, but the information in the registers will remain the same. One of the options for negative development: the turnover data in the accounting accounts will differ from the data in the regulated reporting, which is submitted to the regulatory authorities (reporting in the program is generated on the basis of database registers, postings practically do not play a role in generating reporting).
For most of commot typical operations, there are standard configuration documents that will form the correct movement of accounting registers. While manual operations are static – they are recorded in the form in which they were recorded. As we have entered the data, they will be reflected in accounting; the program will not make changes to them when re-posting Transactions tools (it does not matter - group or automatic).
Amended -
The accuracy of accounting within the program may rely on manually editing entries in a posted document. Such edits require careful attention and responsibility. Before making adjustments, it's essential to analyze the situation and consider which documents will automatically generate the required transactions and movements in the accounting registers.
Typically, business transactions are reflected in the program through configuration documents that align with primary accounting documents. In some instances, it may be necessary to adjust postings and/or movements in the registers that are created when a document is posted. The data for these transactions is stored not only in accounting accounts but also in special registers essential for the program’s functionality and reporting requirements.
For instance, if an accountant opts to manually record a business transaction, the balance sheet might appear correct, but issues could arise when generating reports. Manually entered data may not update the registers, leading to discrepancies between the turnover data in accounting accounts and the data in regulated reports submitted to authorities. Reports are generated based on database registers, not postings, so manual entries might not be accurately reflected.
Standard configuration documents typically handle most common transactions, ensuring proper movement in accounting registers. In contrast, manual entries are static and remain as initially recorded. The program does not alter these entries during re-posting using Transactions tools, whether group or automatic.