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
12665 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

The Customer Tax Exemption Maintenance program, SYS160, allows you to specify customer declarations used by the Customer Order Entry (ORD) and Billing (BIL) applications to apply a tax rate code to specific order lines of an invoice.

With this program, Infor LX can invoice customers without value-added tax (VAT) if one of the following conditions occurs:

  • The cumulated...

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!...

First3031323335373839Last

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:

1345678910Last

Theme picker

Categories