After a financial transaction document has been saved or submitted, the General Ledger Pending Entries tab displays the entries that will be posted to the General Ledger when the document is fully approved and the batch has run. In addition to the entries the user created, the General Ledger Pending Entries tab may include system-generated offset transactions.
Before save or submit, after posting to the GL, on cancel or disapprove
The tab contains the message: There are currently no General Ledger Pending Entries associated with the Transaction Processing document. This message will display when:
- The document is newly opened and has not been saved or submitted.
- The document is fully approved and the entries have posted to the General Ledger after batches have run
- The document is canceled or disapproved.
After Save or Submit
When the document is saved or submitted, the pending entries are displayed in the General Ledger Pending Entries tab. If offset entries are generated they are also displayed in this tab.
Lines 1 and 3 were entered on the document. Lines 2 and 4 are the generated offsets. Offsets are defined in the Offset Definition table.
The Offset Definition table establishes the types of offset entries that are generated for each document type on transactional documents and in batch. When a generated offset is required, the document type, fiscal year, and chart code of the transaction are matched to the offset definition entries. The offsetting transaction is built using the balance type and object code in the Offset Definition table. The Offset Definition table is also used by the Scrubber process.
General Ledger Pending Entries lookup
After a transaction is fully approved and the entries are posted to the General Ledger the general ledger pending entries are removed from this tab of the document.
Pending entries will also be removed if the document is cancelled or disapproved.
Pending entries that have been processed by batch are listed in the gl_glentry_kfs.data file which is generated when the nightlyOutJob runs.