An important feature of transactions is their ability to reference other transactions within the system. Referencing allows the system to back out, or liquidate, the appropriate accounting entries of the prior transaction that is being referenced. For example, a Purchase Order (PO) referencing a Requisition relieves the Pre-Encumbrance created by the Requisition and replaces it with an Encumbered Amount.
Referencing can have non-accounting consequences as well. A Receiver (RC) transaction referencing a Purchase Order records the Receipt of the goods on the Purchase Order. While the Receiver transaction does not register an accounting event, it does update the status of the Purchase Order to facilitate the Three-Way-Match processes. Finally, transaction referencing makes your data entry tasks easier and more accurate.
Each CGI Advantage site is able to manage and enforce its own specific policies and procedures by controlling what references are allowed, and the manner in which values are inferred from or validated against the referenced transaction. Whatever the site’s policies, the actions that the system takes when a transaction is referenced must first be defined.
For information on referencing setup & controls and inquiries not discussed in this user guide, refer to the following topics in the CGI Advantage - Financial Administration User Guide:
For more information on the referencing inquiries, refer to the following topics in this user guide:
For the different types of references, refer to the "Referencing" topic under "Accounting Model Delivered Configuration" in the CGI Advantage - Financial Administration User Guide.