Creating and Declaring e-Ledgers with Nebim V3 e-Ledger, an Application with the Software Compatibility Approval by the Revenue Administration
Parameter Settings
e-Signature Settings
Time Stamp Settings
Create Data (Creating e-Ledger Data)
Create e-Ledger (Creating e-Ledger)
Creating Pro-rata Ledger
Creating Ledger Certificate
Using the Time Stamp
Accepting the Approved Certificate
Document Viewer
By entering the program user group, user name and password information, you enter the Nebim V3 e-Ledger program from the server of Nebim V3 ERP accounting registry. The application screen opens.
In Parameters, the following needs to be entered: the information pertaining to the enterprise for which the e-Ledger is going to be prepared, the information regarding the independent accountant/independent accountant financial advisor/certified public accountant, financial period, and the index where the ledger files are to be archived.
e-Signature Settings enable you to enter the smart card and certification information necessary for the e-Signature.
Time Stamp Settings let you define the address and passwords where the time stamp is to be obtained.
In the Create Data section, a connection is established to the server where the Accounting registers of Nebim V3 ERP are kept, “Ledger Data” is brought into compliance with e-Ledger scheme registers and entered into e-Ledger tables. The correctness of the created data is checked. In case there is an error, the registers with errors are listed and the data is asked to be created one more time. In case there are no errors, the transaction is concluded with the message that the data has been created correctly and verified. In this manner, the Grand Ledger and Payment Ledger data has been created and the user gets a list of their end total.
After the data has been created, a data report is shown on the screen. There is a summary report for both the grand ledger and the payment ledger.
In the section Create Ledger, an appropriate index is created by adding Tax Number/Ledger Year/Ledger Month to the Registry Path previously stated in the parameters. Afterwards, e-Ledger XML files (Payment Ledger and Grand Ledger) are created from the previously produced and controlled data; and are sealed.
Create Pro-Rata Ledger is used when the Auditor demands a ledger for the current month before the month is finished. In this section, one selects the day of the given month and the payment number so that the ledger is created up to that point.
When a pro-rata ledger is created, the month is not closed. The user gets a warning related to this.
Create Ledger Certificate creates certificates for the previously created e-Ledger XML files (Payment Ledger and Grand Ledger). These files undergo a check regarding scheme and schematron. The certificate files are created in the registration path specified in the parameters, in the index named Tax Number / Ledger Year / Ledger Month / Created Certificate.
The option Use Time Stamp is used when there is no connection to the website for declaring the Ledger Certificates to the portal of the Revenue Administration.
In the section Accept the Approved Certificate, the files are selected which have been uploaded to the portal of the Revenue Administration and sealed by the Revenue Administration; then these files are compared to the sent certificate files in the archive. In case the file is not empty and no error is encountered, it is archived in the registration path specified in the parameters, in the index named Tax Number / Ledger Year / Ledger Month / Approved Certificate.
The Document Viewer lets you view the created Grand Ledger, Payment Ledger, and the Certificate Files approved by the Revenue Administration and downloaded.
Sample: A sample Grand Ledger viewed with the Ledger Viewer.
* In order to ensure NebimV3 software to run up-to-dated, maintenance and support services of the software should be procured from “Nebim”. In any case, Nebim shall not be hold liable for any losses including but not limited to third party claims, tax sanctions, administrative or judicial monetary fines, which are occurred when maintenance and support services are not procured from Nebim, and the user’s software does not have the latest version or is not supported due to reasons out of Nebim.