# GR/IR and Receipt Accrual Reconciliation at Month-End

> Reconcile GR/IR and accrued purchases one PO line at a time, tell timing from real errors, avoid double accruals, and give each open receipt an owner.

- Canonical page: https://procindex.com/blog/grir-receipt-accrual-reconciliation
- Author: ProcIndex Editorial Team
- Published: 2026-02-20
- Updated: 2026-11-10
- Topics: gr-ir, receipt-accruals, month-end-close, manufacturing, netsuite

A plant receives a shipment on the last Friday of the month. The supplier invoices it the following Monday. At close, the receipt sits in your GR/IR or accrued purchases account with no bill against it, and that is exactly what should happen. The trouble starts three months later, when the same account holds hundreds of lines and nobody can say which are Friday-to-Monday timing and which are bills that will never come.

The fix is to reconcile that account at month-end one purchase order line at a time, with each open item assigned to the person who can actually resolve it.

## What the account is doing

When goods are received against a PO, the ERP records the inventory or expense and credits a clearing account: GR/IR (goods received / invoice received) in SAP, Accrued Purchases in NetSuite, or an equivalent receipt accrual account elsewhere. When the supplier's bill posts, the clearing account is debited and accounts payable is credited. If receipt and bill agree in quantity and price, the line nets to zero.

So the balance on any PO line tells you something specific:

| Balance on the line | Usually means | First question |
| --- | --- | --- |
| Credit | Received, not yet billed (or billed for less) | Is a bill expected, and when? |
| Debit | Billed, not yet received (or billed for more) | Did the goods arrive, and was the receipt entered? |
| Zero but with a variance posted | Quantity or price differed and was resolved | Does the variance match an approved change? |

A credit balance from the last few days of the month is normal. Everything else needs an explanation.

## When a balance needs investigation

Normal timing looks like a recent receipt with a bill expected shortly. These patterns need work:

- The bill has arrived and posted, but the receipt still appears open.
- Receiving corrected a quantity, but the original entry is still there.
- A receipt was reversed or posted twice.
- The bill covers only part of the receipt, or more than was received.
- The open receipt is months old and the supplier says it has been paid.

## Work one PO line at a time

Group entries by PO line. Bring the original receipt, any reversals or corrections, the supplier bills, and the ledger entries into one view, all at the same cutoff, so a bill posted after close doesn't appear to clear a receipt in the earlier period.

1. **Start with the receipts.** Record the entity or subsidiary, plant, posting date, and quantity. Include corrections and reversals in the net received quantity.
2. **Find the linked bills.** Compare billed and received quantities in the same unit of measure. A bill for part of a shipment leaves different work than a bill for the full quantity at a different price.
3. **Check how the line handles variances.** Find out whether quantity, price, and exchange-rate differences post automatically or wait for a trigger (see the ERP section below).
4. **Record the reason and the next step.** Give the owner the specific line and source record.

### Decide what each open receipt needs

| What you see | Check next | Who can resolve it |
| --- | --- | --- |
| Goods received before close, bill still expected | Confirm the receipt and when the supplier expects to invoice | AP |
| Goods arrived before cutoff, but no receipt entered | Confirm delivery; controller decides cutoff treatment | Receiving and controller |
| Bill covers only part of the receipt | Compare net received and billed quantities in the same unit | AP and receiving |
| Bill posted, receipt still looks open | Check whether the bill used the right PO and receipt lines | AP |
| Receipt reversed or posted twice | Trace the reversal and which receipt the bill references | Receiving |
| Quantity agrees, cost differs | Compare agreed price, freight, and other charges with the bill | Purchasing |
| Goods rejected or returned | Find the return record, supplier credit, or replacement agreement | Quality and purchasing |
| Same supplier delivers to two plants | Compare locations and entities before moving an amount | AP and plant controllers |

Keep normal timing items visible with a review date. Give the others a reason and an owner. If AP can't tell which line to check, the next step is finding the records, not clearing the balance.

## Illustrative example: a partial shipment

A PO is for 100 units at $25 each. By month-end the plant has received 60 units and the supplier has billed 40.

| Event | Entry | GR/IR balance |
| --- | --- | --- |
| Receive 60 units | Dr inventory $1,500 / Cr GR/IR $1,500 | $1,500 credit |
| Bill 40 units at $25 | Dr GR/IR $1,000 / Cr AP $1,000 | $500 credit |

The $500 credit is 20 units received and not yet billed (20 × $25). The other 40 units on the PO haven't arrived. They are an open commitment, not an accrual, and should not appear in the account. Explain those two groups separately.

Next month the plant receives the remaining 40 units (Cr GR/IR $1,000) and the supplier bills the remaining 60 (Dr GR/IR $1,500). The balance is $500 + $1,000 − $1,500 = $0, and the line clears.

Now suppose the first bill had been for 40 units at $26 instead of $25. AP is credited $1,040, GR/IR is debited $1,000, and the $40 difference posts as a price variance or to inventory, depending on your costing method. Purchasing needs to confirm whether $26 was approved. That question belongs in your [purchase price variance](https://procindex.com/blog/purchase-price-variance) review, not in the accrual.

## Don't accrue what the ERP already accrued

A frequent close error with receipt accruals is double counting. A plant controller sees goods received on the 31st, no bill, and books a manual accrual for $500. But the receipt already credited GR/IR $500. The liability is now $1,000.

Before booking any manual accrual for received goods, export receipts through the cutoff with the plant, entity, PO line, receipt date, quantity, and amount already billed. Check what the receipt already recorded. Manual accruals belong to items the ERP doesn't capture, such as goods that arrived but weren't received in the system, or services with no receipt. If the controller does book a separate adjustment, verify next month how it reverses and what is still open. The [journal entries and accruals guide](https://procindex.com/blog/journal-entries-accruals-prepaids) covers reversing entries.

## How this works in NetSuite

With Advanced Receiving, receiving and billing a purchase order can happen separately. The account to inspect for the receipt-to-bill offset is **Accrued Purchases**. Oracle documents the accounting impact of receiving and billing and the separate treatment of quantity, price, and exchange-rate variances. [Oracle's guide to accounting for received purchase orders](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2408991.html)

Variance timing depends on the line. Oracle documents a receipt-based method for lines using **Match Bill to Receipt** and a PO-based method for other lines. Under the PO-based method, the line must be fully received and billed before variances are generated. A partially received line won't show a variance journal yet, which isn't evidence that the bill matched. Ask which method your account uses and where the variance will post. [Oracle's vendor bill variance guide](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2371184.html)

Oracle also documents a partial-receipt limitation for its three-way match approval workflow, so test the workflow your account actually uses with a partially received PO. [Oracle's three-way match documentation](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4096219721.html)

## How this works in SAP

In SAP S/4HANA Cloud, SAP documents how quantity differences between receipts and invoices leave a balance in GR/IR and how that balance is cleared. [SAP's GR/IR clearing guide](https://help.sap.com/docs/SAP_S4HANA_CLOUD/0e602d466b99490187fcbb30d1dc897c/72256b54f94c8f4ce10000000a4450e5.html) SAP also separates invoice variances for price and quantity at invoice entry. [SAP invoice variances](https://learning.sap.com/courses/invoice-verification-in-sap-s-4hana/entering-invoices-with-variances-1)

Clearing a GR/IR balance is an accounting decision. Use it for differences you have investigated and approved, not as a way to make an old line disappear.

## Two cutoff cases to agree on in advance

**Goods on the dock, no receipt.** The ERP has no accrual because nothing was received in the system. Receiving confirms delivery, and the controller decides whether to book a manual accrual or have the receipt backdated under your policy.

**Bill before receipt.** The supplier bills on shipment; goods arrive next month. The line shows a debit balance at close. Agree which date controls cutoff and who can correct a late receipt. Keep this close decision separate from whether to release the supplier's payment, which depends on your matching rules (see [three-way matching](https://procindex.com/blog/three-way-matching)).

## Review the close with two samples

Pick one receipt that stayed open and one that cleared. For the open item, confirm the amount still belongs in the account and explain when it will clear. For the cleared item, follow the entry to its bill or approved adjustment. Keep that evidence with the close file. A smaller aging balance tells you little if nobody can explain what changed.

Next month, choose an unbilled receipt and trace it until the supplier bill arrives. Check that the receipt balance clears, or that a supported difference remains.

## What a useful review screen shows

Put the PO line, receipts, reversals, and linked bills together. Show net quantities, dates, remaining balance, and who owns the next step, with a link to each source transaction so the reviewer can check a proposed disposition before it changes the ledger. When evaluating any tool for this, run a partial-receipt case twice: once as is, and once after receiving enters the missing delivery while the bill is still open. AP should see what changed without asking for another copy of the packing slip.

For receipt-based settlement, where there is no supplier invoice at all, see [ERS, consignment, and scheduled releases](https://procindex.com/blog/ers-consignment-scheduled-releases).

## Month-end checklist

- [ ] GR/IR or accrued purchases balance tied to the general ledger at the cutoff date
- [ ] Open items grouped by PO line with receipts, reversals, and bills at the same cutoff
- [ ] Credit and debit balances separated; open PO commitments excluded
- [ ] Each item older than one cycle has a reason, owner, and review date
- [ ] Manual accruals checked against what receipts already recorded
- [ ] Variance method confirmed for lines with price or quantity differences
- [ ] One open and one cleared sample traced to source and saved with the close file
- [ ] Any clearing entry supported by investigation and approval

## Sources

- https://help.sap.com/docs/SAP_S4HANA_CLOUD/0e602d466b99490187fcbb30d1dc897c/72256b54f94c8f4ce10000000a4450e5.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2408991.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N2371184.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4096219721.html
- https://learning.sap.com/courses/invoice-verification-in-sap-s-4hana/entering-invoices-with-variances-1

---

Published by ProcIndex, which builds AI accounting agents for construction and manufacturing finance teams. ProcIndex currently connects to NetSuite, Sage Intacct, and QuickBooks. Worked examples in this guide are illustrative, not customer results.