Posting and Unposting Functionality

Posting is a standard accounting function that enables you to enter accounting transactions in the Transaction journal and other system journals. Those accounting transactions have direct impact on financial statements of your business.
Note: In Codejig ERP, only documents can be posted.
For more details, see
Managing Data in Codejig ERP.
The posting process transfers data from documents to system journals and to the Transaction journal. As a result, two states of documents are distinguished in the system. Documents can be either posted or unposted. When you post a specific document it makes accounting journal entries to journals associated with this document type and to the Transaction journal. Posted data is processed by the system according to its internal logic. Documents that have not been posted or have been unposted can be treated as drafts. They can be used for storing and displaying information, but they do not affect any journals or The transaction journal.  

Previously posted documents can be unposted if necessary.
Unposting a document equals canceling it because only posted documents have an accounting or inventory impact. 

Unposting functionality removes postings triggered by a document or documents from journals affected and reverts accounting changes invoked by those postings.
Note: To ensure the correctness and validity of the year-end financial statements, all recorded documents that impact your financial activities have to be posted. 
Deleting a posted document equals unposting it. For more information about deleting data in Codejig ERP, see Deleting Data in Codejig ERP

If you update a posted document, it gets unposted and then is automatically posted once again with modifications made to the document being reflected in the resulting posting entries. 

Unposting, update or removal of a posted document or posting an unposted document may also affect all other posted documents in the system that have later posting date and time.
Note: Posting date and time is the date and time specified in the date field of a document. 
Depending on the posting parameters specified for the system, the batch reposting of such documents may be triggered.
Note: Batch reposting is a process when all posted documents that have later posting date and time than the document causing the batch reposting process get unposted, all transactions made by them being canceled and removed from system journals, and then they are automatically posted once again. New transactions and resulting journal entries will be affected by modifications made to the document that has triggered the batch reposting or its removal from the system. As a result, despite the fact that the reposted documents have not been modified in any way, new transactions they make may differ from the original ones as they are based on new accounting data.
In Codejig ERP, the following posting modes are available:

  • Post/Unpost single document

If you enable this mode in Codejig ERP, unposting, update or removal of a posted document or posting an unposted document will not cause the batch reposting of all other posted documents in the system that have later posting date and time. 

Note: Batch reposting affects not only documents of a specific type but all documents recorded in the system.
All created documents can be found in the Timeline section of Codejig ERP. For more information about the Timeline, see Timeline.   

Advantage of the Post/Unpost single document mode: you benefit from working in this mode if you have to store, process and handle large volumes of data that are entered by a number of different users simultaneously. This mode allows you to eliminate the time-consuming batch reposting process. 

Disadvantages of the Post/Unpost single document mode:

  • It is not recommended to use this mode on a regular basis as it cannot guarantee the correctness and integrity of your accounting data. Since manipulations with posted documents do not trigger reposting of other posted documents in the system, your transactions may be invalid as there is a possibility that they based on either false or already changed information. It may result in inaccurate financial reporting. 
  • You can use it temporarily, provided that you periodically batch repost all documents created in the current accounting period by switching to one of the posting modes described below. You should do that to detect errors occurred and bring your accounting data into consistency.

 If you do not use this mode, manipulations with posted documents or retroactive posting of documents will cause batch reposting all documents created across the  system that have later posting date and time. 

  • Post all documents in single transaction

If you work in this mode, all posting entries created during the batch reposting or batch posting processes will be canceled if a posting error occurs at least for one document. For example, if during the process of batch reposting/batch posting the system establishes that a number of sales transactions are not based on associated purchase transactions, the batch reposting/posting will be stopped, all postings made will be canceled and removed from journals, and, as a result, all the documents that were to be posted will become unposted.  You will have to manually correct the error either by deleting sales documents that have made erroneous transactions or by retroactively creating purchase documents required for the sales transactions to become valid. Then, you will have to run the batch reposting/posting once again. 

For information about batch posting process, see Batch Posting and Unposting

  • Post each document in separate transaction

If you turn on this mode, posting entries created during the batch reposting or batch posting processes prior to error occurrence will not be canceled, but a document for which a posting error has been encountered and other documents that have later date and time will not be posted. This mode is useful if you have to post or repost large amounts of documents, and if you expect at least a part of those documents to be posted in case an accounting error is detected. It is particularly helpful when you revise documents and transactions before preparing financial statements. 

For information about batch posting process, see Batch Posting and Unposting

By default, one of the last two positions has to be chosen. 

More information

Manage Data in Codejig ERP. Data Classes and Data Files
Delete Data
Batch Posting and Unposting