GL totals for RNI do not match RNI report - PO135

I've been asked by our Finance group about a few different GL totals at month end that don't match the Supply Chain report version.

I suspect it's years of neglect and ignoring, but Finance is asking why these don't match, and I'm wondering if any of you know the usual reasons why.

IC234/Period End Inventory Valuation: for a specific inventory location

PO135/RNI: for a specific company

PO136/INR: for a single company

dEPM-653 - Introduction to dEPM Office integration for Excel.mp4

Find more posts tagged with

Infor Lawson Supply Chain Group - Discussion

Comments

unknown

IC234 is the value of Stock on Hand. So assuming you are running it as part of IC month end close - the difference between the IC234 from previous month and this month should be the total of IC transactions appearing on GL90.

If you have AP or PO transactions on the inventory account - they should not be there and will affect the IC234 vs GL90. My company moves it to expense.

PO135/RNI reports what it posted AND reports what the IC130 posted. So the transactions for Non-Stock and Specials hit the GL as system code PO and the tranactions for Inventory hit the GL as IC.

PO136 is a report only - I'm not aware of it hitting the GL at all? If you run in update to write off - then it would hit the GL but I don't know what that looks like.

gtesche

Thanks this is pretty helpful. For the IC234 vs. GL90, the correction where AP or PO transactions are moved to expense, I'm assuming this is a Finance function to both look for and correct?

With PO135/RNI, I believe part of our difference is coming from the error in reporting RNI that was fixed a while back. Plus years and years of ignoring RNI altogether.

We don't run PO136 in update mode, so I'm a little confused about that one.

dan-georgsson

If you run PO136 in update it will create write-offs, so want to be sure that is what AP wants to do with the items that appear. Since there is more invoiced than received, there may be other issues that created the MNR, i.e. matched out of tolerance issues not using all of the available receipts. I would review before I wrote them off. :-)

unknown

If you don't run the PO136 in update mode - the money is currently sitting in whatever liability account shows on the report. The report is telling you what it *WOULD* do. Not what was actually posted. Hence - when they look at the GL, there's nothing there and they think it's a "discrepancy"

If you dump the RNI and the MNR - compare them. If the same PO Line appears on both - you can back out the receipt on PO33 and re-receive it on PO30 and that should clear both reports and close the PO Line.

gtesche

Thanks again, your responses make a lot of sense. The PO136 showing what WOULD post if we ran in update mode. I don't actually expect we'll be able to fix nearly two decades of not cleaning up, but I can at least explain why it doesn't match.

The Ultimate in Flexibility - Self-Scheduling in WFM _ Brian and Maciek Presenting to WFM User Group-20220713_100215-Meeting Recording.mp4

gtesche

@KatVila - related question about PO135 run at month end close in update mode. Is it normal for the the previous month's RNI posting in GL to be reversed? Meaning last month cost center X had $1000.00 post to GL for RNI, then next month that $1000 is reversed. Then a new posting for the new month's RNI amount would be created.

Is that normally how it works? I assumed only the amount invoiced would reverse, not the whole amount.

unknown

Yes, That is how that RNI process. At the beginning of the Month the GL system makes the assumption that invoices will be processed for everything that has been received but not invoiced including any new receipts. Then at the end of the month when PO135 is run it creates a new, auto reversing, gl entry for everything that has not been invoiced at the end of that new month.

0904080939293831.xls

gtesche

Thanks so much for your response.

com_proactive_201104.pdf

Copyright © 2025 Infor. All rights reserved.