Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: What is the GRNI Reconciliation Process?

What is the GRNI (Goods Received Not Invoiced) Reconciliation Process?

The reconciliation process of the GRNI transactions consists of the following steps:

  1. Close the financial period so that no new transactions can be entered.
  2. Print the trial balance.
  3. Print a report of the invoices to be received.
  4. Compare the reports.
  5. Print the reconciliation data.
  6. Examine the reports.
  7. Rebuild the History.
  8. Print the trial balance and the reconciliation report again.
  9. Print the GRNI reconciliation checklist.
  10. Check the balances on the GRNI reconciliation checklist.
  11. Analyze the reconciliation data.
  12. Make corrections.
  13. Print the GRNI reconciliation checklist again.
  14. Post the reconciliation correction transactions.
  15. Accept the reconciliation data.


Have questions on this process or need some help? Contact us! Our experienced Finance consultants will be glad to assist you.

800.762.2077

Previous Article Infor LX & BPCS Tip: Capacity Planning – Resource Requirements Reports
Next Article By 2026, 75% of organizations will base their digital transformation model on the CLOUD!
Print
12544 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

Enhancement: Order Hold Audit Functionality

This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

First34568101112Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

123456810Last

Theme picker

Categories