| G/L Integrity Solution for JDEdwards
|
GRNI ("Goods Received Not Invoiced") is a self-contained general ledger based integrity solution that reconciles receipts, vouchers and routing entries, giving visibility of your GRNI accounts down to order line at a given As-Of date, allowing you to qualify values for auditing purposes.
The GRNI Gateway
Using GRNI you can generate your As-Of position at any given date comparing the purchasing system with your general ledger. Once the As-Of position has been attained the GRNI Gateway provides a simple user interface which details the reconciled and non-reconciled amounts by company. From here, drill downs are available to the general ledger or receipt detail so that you can fully understand your GRNI position. |
 |
Data Matching, Cleansing and Tolerance Checking
The As-Of build process matches down to order line level with comprehensive handling of partial receipts and multiple voucher line matching. GRNI also has functionality to cleanse/reconcile your data, including the ability to close receipts without affecting inventory but with optional impact on G/L and the provision of mass data cleansing tools allowing the write-off of values to clearance accounts using user defined tolerance values.
Approvals and Auditability
GRNI uses an audited batch approval process to control the closure of receipts and the posting of clearance accounts to the general ledger.
Why do I need GRNI?
If GRNI functionality in an ERP system works well, the role of the user is to review the GRNI reports, investigate old and significant items and if it’s apparent that they are not going to be invoiced, to make the appropriate corrections within the system using standard entries. Unfortunately, standard JDEdwards functionality in this area is weak and users generally find it difficult to maintain the GRNI account because of the following issues:
 |
There are no standard JDEdwards GRNI “As-of” reports. With receipts and vouchers having different cut offs there is no point in time at which a report can be run that will balance with the general ledger. |
| |
|
 |
There are no standard integrity reports in JDE to verify the information reported in the general ledger for the purchasing system, however, integrity problems do occur between these modules and it is important to identify the offending orders and transactions. |
Further reconciliation problems can be can be caused by:
|
 |
Multi-currency differences between the receipt and voucher in the domestic currency ledger (AA). |
| |
|
 |
When vouchers created by the JDEdwards voucher match function are incorrectly voided or deleted through the standard voucher entry program. |
| |
|
 |
Integrity defects caused by "system crashes" whilst using receipt entry or voucher match functions. |
For more information, see the frequently asked questions about GRNI
|