Goods receipt/invoice receipt (GR/IR) is one of those accounts that can look routine until month-end: a large balance, old purchase-order items, a debit/credit mix that no one can explain, or a late adjustment that changes inventory or expense. For controllers, the objective is not simply to make the clearing account reach zero. It is to establish what the balance represents, confirm the underlying goods or invoices, and ensure any correction is supported, properly approved and posted to the right period.
In SAP, the GR/IR account is an interim account between receiving goods and recording the supplier invoice. SAP explains that a goods receipt generally creates a GR/IR offset, and the invoice receipt clears it; differences remain when quantities, values or timing do not align. See SAP’s invoice-verification account guidance and Reconcile GR/IR Accounts app documentation.
Why GR/IR matters at close
Unresolved GR/IR items can signal a missing invoice, a missing goods receipt, a quantity or price mismatch, incorrect delivery-cost treatment, an outdated purchase-order price, or a process failure. They can also affect the timing or classification of inventory, expense, liabilities and price differences. The right accounting outcome depends on the facts, the company’s accounting policy and the applicable reporting framework—not just the age of the line item.
Consider a simple example: a company receives 100 units at an expected net price of $50 each, but the supplier invoice received by close covers only 90 units. The unmatched $500 may represent goods received but not yet invoiced, a partial invoice, a disputed quantity, or a receiving error. The controller should not clear it simply because it is old. The team needs evidence of what was delivered, what was invoiced, and what remains owed or disputed.
10 GR/IR controls to strengthen month-end close
1. Reconcile the GR/IR subledger to the general ledger
At each close, reconcile the relevant GR/IR G/L accounts to the detailed open-item population by company code, account and purchasing document/item. Investigate any difference between the report and the G/L balance before reviewing individual exceptions. Retain the report parameters, run date, totals and reviewer sign-off so the reconciliation can be reproduced.
2. Use a risk-based aging view—not only a total balance
Segment open items by age, value, company code, supplier, purchasing group, material or service, and debit/credit direction. Define escalation bands appropriate to the business—for example, items over 30, 60 and 90 days—and set lower thresholds for high-value or unusual items. Age is a prioritization signal, not proof that a balance is wrong or safe to write off.
3. Distinguish missing invoices from missing receipts
For a credit balance that appears to represent goods received but not invoiced, check the receipt document, delivery evidence, purchase order, contract terms and subsequent invoice activity. For a debit balance that may indicate an invoice before receipt, inspect the invoice, receipt status, returns, reversals and any permitted advance or service arrangements. Confirm the underlying business event before deciding on the accounting treatment.
4. Investigate quantity and price differences separately
Compare ordered, received and invoiced quantities, then compare purchase-order price, invoice price, freight and other planned delivery costs. A quantity difference may require receiving or supplier follow-up; a price difference may require a valid purchase-order change, invoice correction or posting under the organization’s configured accounting logic. Do not use a generic write-off to conceal a recurring purchasing or master-data issue.
5. Review reversals, returns and duplicate activity
Search for reversed goods receipts, return deliveries, credit memos, invoice cancellations and repeated invoice postings. Confirm that the related documents have been reversed or corrected consistently. A receipt reversed after an invoice is posted can create an apparent mismatch that is not resolved by chasing the supplier alone.
6. Confirm cutoff around the reporting date
Review receipts and invoices posted immediately before and after period-end, especially high-value deliveries, late warehouse postings, services and goods in transit. Match receiving dates and evidence to the relevant contractual and accounting facts. Where goods or services have been received but the supplier invoice has not arrived, assess whether a separate accrual or other adjustment is required under the entity’s accounting policy. Avoid double-counting amounts already reflected through GR/IR.
7. Use SAP reconciliation tools as an exception workflow
SAP documents the Reconcile GR/IR Accounts app (F3302) as a way to compile open items that need clarification and display relevant procurement and accounting information. Availability and functions depend on the SAP product, release, configuration and enabled scope. Use the tool to prioritize and document exceptions; do not assume an automated suggestion is itself sufficient evidence for an adjustment.
8. Restrict and review manual clearing or write-offs
Manual clearing can be appropriate when no further receipt or invoice is expected, but it should follow a documented decision. SAP’s Clear GR/IR Clearing Account guidance (MR11) describes clearing differences when no more goods or invoices are expected. Define who can propose, approve and post a clearing; set materiality and escalation rules; and require supporting evidence and a reason code. Separate preparation from approval where practical, and review unusual postings after the fact.
9. Assign each exception to a named owner and due date
Give each material or aged item an accountable owner in procurement, receiving, accounts payable, inventory accounting or the business. Record the cause, action required, expected resolution date, evidence and escalation status. The close team should review overdue items at a regular cadence and carry forward only those that remain valid and adequately explained.
10. Trend root causes and test whether fixes work
Track total open balance, value and count by aging band, recurring suppliers, quantity-versus-price differences, manual clearing entries, post-close reversals and repeat exceptions. Use trends to identify training needs, late receiving, poor purchase-order discipline, supplier invoicing problems or configuration defects. After a process fix, test a later period to confirm that the exception rate actually falls.
A practical controller review matrix
| Review area | Evidence to retain | Escalate when |
|---|---|---|
| G/L-to-detail reconciliation | Reconciliation, report parameters, totals and reviewer approval | Unexplained difference or incomplete population |
| Aged open items | PO/item-level analysis, owner, age, value and expected resolution | Material item exceeds policy threshold or has no owner |
| Cutoff and subsequent activity | Receipt/acceptance evidence, invoice, reversal and posting dates | Possible period misstatement or duplicate accrual |
| Manual clearing | Reason, supporting documents, approval and posting reference | Repeated, unusual or unsupported adjustment |
| Root-cause monitoring | Trend dashboard, action log and follow-up testing | Recurring issue persists across closes |
Keep the accounting conclusion separate from the system balance
GR/IR is a process account, not a substitute for a documented accounting conclusion. For inventory, the IFRS Foundation’s IAS 2 overview explains that inventory cost includes purchase and other qualifying costs, and that inventory cost is recognized as an expense when the inventory is sold, subject to the standard’s requirements. US GAAP and Canadian ASPE have their own authoritative requirements and company-specific policies; do not assume that a single SAP configuration resolves every reporting question across frameworks.
For SEC registrants subject to an ICFR audit, controls and supporting evidence should be designed with the company’s risk assessment and reporting assertions in mind. The PCAOB’s AS 2201 discusses the auditor’s evaluation of internal control over financial reporting, including the severity of control deficiencies. It is an auditing standard, not a GR/IR accounting rule, but it reinforces why a controller should retain evidence that key reconciliations and approvals actually operated.
Month-end GR/IR sign-off checklist
- ☐ Reconcile the detailed open-item report to the relevant G/L accounts.
- ☐ Review material and aged items by direction, quantity, value and root cause.
- ☐ Test cutoff and inspect subsequent invoices, receipts, returns and reversals.
- ☐ Confirm each exception has an owner, resolution date and supporting evidence.
- ☐ Review and approve manual clearings or adjustments under documented rules.
- ☐ Confirm the resulting inventory, expense, liability and price-difference treatment is appropriate under the entity’s accounting policy.
- ☐ Track recurring causes and verify that corrective actions reduce future exceptions.
Conclusion
A disciplined GR/IR process improves close quality by turning an aged balance into a traceable list of business questions. The controller’s role is to ensure the population is complete, exceptions are prioritized, evidence supports the conclusion, and any adjustment is approved and recorded correctly. In SAP, reconciliation apps can make the investigation more efficient—but accountability, sound cutoff judgments and documented review remain essential.
Informational only: This article provides general process and control guidance, not accounting, audit or legal advice. Apply the authoritative standards, contractual facts, SAP configuration and approved accounting policies relevant to your entity.
