You use this report to identify an imbalance between the sub-ledger and the General Ledger arising from the posting of incomplete or incorrect transactions.
| Field | Description |
|---|---|
| GL Year | Indicate the year for which to generate the report.
This can only be the current or previous year. Note that the previous year can only be selected when the current period is in a new year in period 1 or in period 2. |
| GL Period | Indicate the period for which to generate the
report. This can only be for the current period, the previous period 1 or previous period 2. |
| Report type | |
| Detail | Prints detailed information about each transaction causing an imbalance between the sub-ledger and General Ledger, as well as a summary page of subtotals and totals. |
| Summary | Prints only subtotals and totals indicating an imbalance. |
| Options | |
| Check normal journal entries | Identifies abnormal journal entries posted to the GL
control account(s). This tests that all transactions posted to the Control account(s) in the GL originated from sub modules only, and not from other journal types posted using the GL Journal Entry program for example. |
| Check unposted GL journal entries | Identifies sub module GL journals created, but not posted
into the general ledger. This occurs when the Create general ledger Journal option is enabled, but the Post general ledger journal option is not enabled in the General Ledger Integration program. The sub module GL journal is created, but must manually be posted using the GL Post Multiple Normal Journals or GL Journal Entry programs. |
| Check unposted sub-module entries | Identifies sub module journals for which the corresponding
GL journal has not been created. When you successfully process a transaction in a sub-module, the sub-module journal is automatically created, but the corresponding GL journal is not automatically created when the Create general ledger Journal option in the General Ledger Integration program is not enabled. In this case, the GL journals for transactions processed in the sub-modules are only created when you run the GL Integration program(s) in each sub-module:
|
| Check GL transaction to journal | Identifies entries where the Journal and the GL transaction do not match. |
| Check GL journal to sub-module | Identifies entries where the GL Journal amount and sub-ledger journal transaction amount do not match. |
| Check duplicate posted GL transactions | Identifies duplicate posted GL transactions in the
GENTRN table. Note that duplicate GRN Adjustment journals cannot be reported, as there is currently no zoom key available. This only applies if the sub-ledger is integrated to General Ledger in detail. |
| Check duplicate unposted GL transactions | Identifies duplicated un-posted GL transactions in the
GENJND table. This only applies if the sub-ledger is integrated to General Ledger in detail. |
| Check AP journal to GRN matched | This compares the AP journal amounts to the amounts in the GRN entries table (GRNMAT) for each entry. The difference between the amounts is reflected. Note that this is not added to the last calculated balance, because the system cannot ascertain whether the GRN control account was updated with the AP transaction amount or the GRNMAT amount. This could lead to a value in the Unexplained difference total on the report. This only applies to the GL Balance GRN program. |
| Check Inventory journal to GRN detail | This checks whether the Inventory journal amounts in the INVJND table match the amounts in the GRN entries table GRNDET for each entry. The difference between the amounts is reflected. Note that this is not added to the last calculated balance, because the system cannot ascertain whether the GRN control account was updated with the Inventory transaction amount or the GRNMAT amount. This could lead to a value in the Unexplained difference total on the report. This only applies to the GL Balance GRN program. |
| Unposted sub-module entries | |
| Include zero value transactions | Disable this to shorten the report by excluding un-posted zero balance journals. These journals will never be posted and do not affect the balancing process. |
| Inventory control total | |
| Use FIFO costing method | You can enable this to use the FIFO costing method to
calculate the Inventory Control total if your Costing
method is set to FIFO or
LIFO (Inventory Setup). This is only available for
the GL Balance Inventory program when running SYSPRO in a SQL
environment. The Current cost is used instead of the FIFO cost when this option is not enabled. |
These options enable you to apply a theme to the report and to define multiple output destinations for the report once it has been compiled (SRS Output Options).
This report does not support the FIFO costing method when calculating the Inventory Control Total if you are running SYSPRO in a C-ISAM environment.
The report uses the INVQVE (Inventory Valuation Summary Query) business object to determine the Inventory Control Total, but this business object is a SQL only business object.