The GR/IR Account Nobody Wants to Open at Year End

It is the second week of December. The controller at a mid-sized industrial manufacturer runs the GR/IR balance report for the first time since the half-year close. The open balance comes to €1.8 million, spread across 4,200 line items. Some of them date back to February.

Nobody in the room is surprised. Everyone is a little uncomfortable.

The auditors arrive in the third week of January. They will pull a sample of the oldest and largest items and ask the same question about each one. What is this, and why is it still here? Somebody has to answer for every line they pick. That somebody usually spends the last two weeks of December inside spreadsheets, emailing buyers who have since changed roles and warehouse leads who cannot remember a delivery from March.

The company in this story is a composite, and the figures are illustrative. The pattern is not. Almost every SAP finance team we talk to has a version of this account, and almost every one of them cleans it up the same way: late, by hand, under pressure. This post looks at why the GR/IR account fills up, what each stuck line actually means for the business, and how to clear it with evidence instead of guesswork.

What the GR/IR account is supposed to do

GR/IR stands for goods received, invoice received. It is a holding account. Its whole job is to sit at zero.

Think of it as a cinema ticket torn in half. The warehouse holds one half and accounts payable holds the other. When both halves turn up, they match, and the account is clean. A balance in GR/IR means somebody is holding half a ticket and the other half has gone missing.

Here is a real-world example. A manufacturer raises purchase order 4500012345 with a supplier in Stuttgart for 500 steel mounting brackets at €12.00 each, so €6,000 in total. On 14 March the brackets arrive at the dock and the warehouse posts the goods receipt. SAP adds €6,000 to inventory and records €6,000 as a credit in GR/IR. The company now owns the brackets and owes for them, even though no invoice has arrived yet.

On 22 March the supplier's invoice lands. Accounts payable posts it against the same purchase order. SAP moves €6,000 out of GR/IR and into the supplier's account as an amount to pay. The two halves have met. GR/IR for that line goes back to zero, and nobody thinks about it again.

In a healthy month, most lines behave exactly like this. They sit in GR/IR for a few days and leave on their own. The trouble comes from the lines that never complete the trip, because there is no natural moment when anyone goes looking for them. Accounts payable only touches an item when an invoice arrives. The warehouse only touches it when goods arrive. If one of those events never happens, the line just waits.

Five ways a GR/IR line gets stuck

After working through enough of these balances, the same five patterns show up again and again.

The goods arrived, and the invoice never posted. This is the most common pattern and usually the largest by value. The brackets came in on 14 March. The invoice went to an old accounts payable mailbox that nobody checks anymore. Or it quoted a purchase order that had been replaced. Or it was addressed to the wrong company code in a group with five legal entities. Sometimes the supplier did not send an individual invoice at all and billed the delivery on a consolidated monthly statement that someone filed without posting. The GR/IR line shows a €6,000 credit, and it will keep showing it until the invoice is found.

The invoice arrived, and the goods were never receipted. This one runs the other way and leaves a debit balance. A crane hire company invoices €14,350 for two days of work at a construction site. The crane came, the job was done, and the site manager signed a timesheet. That timesheet is sitting in a project folder. Nobody told the warehouse, so nobody posted a goods receipt, and the invoice either sits blocked or gets paid without any confirmation that the service happened. Direct deliveries to customer sites, drop shipments and services cause most of these.

Some of the goods arrived. The supplier shipped 480 brackets instead of 500. The warehouse receipted 480. The invoice says 500. Twenty brackets at €12.00 leaves €240 hanging. Was it a short shipment? Were 20 damaged and refused at the dock? Did the buyer agree to cancel the backorder by email? The answer exists somewhere, but not in SAP.

The invoice is stuck on price. The purchase order says €12.00 per bracket. The invoice says €12.40, because the supplier announced a price increase in January and nobody updated the purchase order. The difference is outside tolerance, so SAP blocks the invoice for payment. The full €6,000 receipt stays open in GR/IR while the invoice waits for someone to approve or reject the new price. If you have read our post on getting invoices unstuck from MRBR, you will recognize this queue.

The leftovers. Reversed receipts that were never re-posted. Purchase orders closed halfway through delivery. Freight charges on a separate invoice. Small currency and rounding differences of €3.17 that nobody wants to spend an hour on. Individually these lines are tiny. Together they are often a third of the line count, and they make the whole report look hopeless.

What a full GR/IR account costs the business

It is tempting to treat GR/IR as a cosmetic problem. The balance nets out eventually, so why worry about it in December? The answer is that every one of those five patterns has a real cost, and most of the costs land outside the finance team.

Start with the balance sheet. A credit balance in GR/IR is an accrued liability. The company is saying it owes money for goods it has received. If the invoice was actually posted to another company code or a different purchase order, that liability is counted twice. If the goods were returned and nobody reversed the receipt, the liability does not exist at all. A debit balance is even stranger. It says the company paid or owes for something it cannot show it received. Auditors pay close attention to both, and an old, unexplained GR/IR balance is one of the fastest ways to turn a routine audit into a long one.

Then there is cash. The supplier whose invoice went to the old mailbox has not been paid. Their credit team does not care which mailbox it went to. They see an overdue account, and after 60 or 90 days they start charging late fees or put your account on hold. The first time anyone in purchasing hears about it is when a shipment does not leave the supplier's warehouse. When that supplier finally re-sends the invoice, there is a fresh risk. If the original copy also surfaces and gets posted, you pay twice.

Short shipments carry their own quiet loss. If the supplier shipped 480 brackets and invoiced 500, and the year-end cleanup simply writes off the €240, the company has paid for 20 brackets it never received. Multiply that by a few hundred lines a year and it becomes real money that could have been recovered through a claim. We wrote about this in the supplier claims nobody chases, and GR/IR is where many of those unclaimed shortages end up hiding.

Finally, there is the time. A typical year-end GR/IR cleanup takes two or three people somewhere between two and four weeks, right in the middle of the close, when those same people are needed for accruals, intercompany and the audit file. Most of that time is not spent deciding anything. It is spent looking for documents.

Why the usual fix keeps failing

SAP gives finance teams good tools for seeing the GR/IR balance. The standard balance report (MB5S) lists every open item by purchase order. The period-end analysis (F.19, or its S/4HANA equivalent) regroups the balance so the financial statements show goods received but not invoiced separately from invoices received but not yet delivered. MR11 lets you clear differences and write off small amounts. Newer S/4HANA releases add a monitoring app that helps assign open items to people and track who is working on what.

All of these tools answer the question "what is open?" None of them answer "why is it open?" That answer does not live in SAP. It lives in the documents around SAP. The invoice is in a mailbox. The delivery note is a scanned PDF in a shared drive. The signed site timesheet is in a project folder. The price increase is an attachment in a buyer's email from January. The cancelled backorder is a two-line message in a supplier thread.

So the cleanup becomes a manual search. Someone exports the GR/IR list to Excel, adds a column called "Reason," and starts emailing. Buyers are asked about purchase orders from nine months ago. Warehouse staff are asked to dig out paperwork. Suppliers are asked for statement copies. Answers trickle back over two weeks, some lines get resolved, and the remainder gets cleared through MR11 on 30 December because the books have to close.

That last step is where the real damage happens. Writing off a balance to clear the account is sometimes the right answer. Writing off a balance because nobody had time to find out what happened is how short shipments go unclaimed, duplicate payments slip through and the same supplier problem repeats every year.

It is a bit like the lost luggage desk at an airport. The system can tell you the bag did not arrive. It cannot tell you that it is sitting on a carousel in Frankfurt. Someone has to go and look.

Every open line is a missing document

Here is the shift that makes GR/IR manageable. Stop treating the balance as an accounting problem and start treating it as a document problem. Each of the five patterns points to a specific piece of paper that would resolve it.

What the line shows

The document that explains it

Where it usually hides

Goods received, no invoice

The supplier invoice, or the supplier statement that lists it

An old AP mailbox, a different company code, a monthly statement

Invoice received, no goods

A delivery note, signed proof of delivery or service timesheet

Site folders, driver apps, the project manager's inbox

Quantity difference

Packing slip, damage report or backorder cancellation

Warehouse scans, carrier paperwork, buyer and supplier email threads

Invoice blocked on price

Price change notice, contract or updated quote

Buyer email attachments, contract repositories

Small leftovers

Reversal records, freight invoices, exchange rate notes

Usually inside SAP itself, plus carrier invoices

Once you see it this way, the work changes. The question for each line is no longer "who remembers this?" It becomes "where is the document, and what does it say?" That is a question software can answer at scale, because reading documents and matching them to SAP records is exactly the work Artificio's agents already do every day for supplier statement reconciliation, goods receipts at the dock and proof of delivery matching.

How an agent works through the GR/IR list

Let us take the manufacturer's 4,200 lines and walk through what happens when an agent works them instead of a spreadsheet.

The agent starts by reading every open GR/IR item out of SAP. For each line it records the vendor, the purchase order and item, the amount, whether it is a debit or a credit, the quantity received against the quantity invoiced, and how old it is. Nothing in SAP changes during this step. It is a read-only snapshot, and it gives the team a single, current list instead of an export that goes stale by Friday.

Next, it sorts the lines by pattern. Credits with no invoice go in one group. Debits with no receipt go in another. Lines where both sides exist but the quantities differ go in a third. Lines with a blocked invoice go in a fourth. Everything under a threshold the controller sets, say €50, goes in the leftovers group. This alone changes the mood in the room. A list of 4,200 mixed items feels impossible. Five groups, each with a clear next step, feels like a plan.

Then comes the part that used to take weeks. For each line, the agent goes looking for the missing document in the places the company has connected. It reads the accounts payable mailboxes, including the old ones. It reads supplier statements. It reads scanned delivery notes and signed proofs of delivery. It reads the email threads attached to the purchase order. It does not just search for the purchase order number, because suppliers often leave it off. It matches on supplier, amount, quantity, material description and date, the same way an experienced AP clerk would.

Go back to the €6,000 bracket line. The agent finds a supplier statement from the Stuttgart supplier dated 30 April. Line seven lists invoice 2026-0418 for €6,000, dated 21 March. The invoice itself turns up in the old accounts payable mailbox, still unread. The agent attaches both documents to the GR/IR line and proposes a single action: post invoice 2026-0418 against PO 4500012345. It also notes that the supplier's statement shows the invoice as 214 days overdue, so the line is marked urgent.

Now the €14,350 crane hire debit. There is no goods receipt in SAP, but the agent finds a signed timesheet in the project folder for the Leipzig site, showing two crane days on 8 and 9 May, signed by the site manager. It proposes posting the receipt for the service and routes the proposal to the project manager for approval, with the timesheet attached.

And the 20 missing brackets? The agent finds the delivery note, which says 480 units, and a carrier damage report noting one crushed carton. It proposes a debit note to the supplier for €240, with both documents attached, rather than a write-off.

Some lines will not resolve this way. The document might genuinely not exist, or the evidence might point two ways. Those lines go to a person with whatever the agent did find, so they start from a short list of facts instead of a blank screen.

This is the step that matters most for the audit. The agent never clears a balance on its own judgment. Every proposed action goes to the right person for approval. The buyer approves the price change. The warehouse lead confirms the receipt. The controller signs off on write-offs. Once approved, the agent posts the transaction and keeps a record of who approved what, when, and on the strength of which documents. Our post on what auditors actually look for in an automated audit trail goes into detail on why that record matters.

A six-week plan if you are starting now

If your fiscal year ends on 31 December, there are roughly ten weeks left as this post goes out. That is enough time to do this properly, if the work starts in November rather than the week before Christmas.

In the first week, get a clean snapshot of every open GR/IR line, with age and direction, and agree on the threshold for small differences. Decide who owns each pattern. Accounts payable usually owns missing invoices. Purchasing owns price blocks. The warehouse or site teams own missing receipts.

In the second week, clear the easy matches. In most companies, a large share of goods-without-invoice lines are resolved by an invoice that already exists in a mailbox or on a supplier statement. Finding and posting those first shrinks the list fast and builds momentum.

Weeks three and four are for chasing. Request missing invoices from suppliers, with the statement line attached so they know exactly what you are asking for. Ask site teams for missing receipts, with the invoice attached so they know what to look for. Raise claims for short shipments while the supplier relationship is still warm.

In week five, work through approvals. Price changes get accepted or rejected. Receipts get confirmed. Claims get sent.

In week six, deal with what is left. Write off the small leftovers through MR11, but with a reason recorded for each one. Build the audit pack, a simple list showing each remaining open line, why it is still open and what document supports it.

With an agent doing the searching and matching, this plan compresses. The snapshot and sorting happen in an afternoon. The document search runs overnight. The team spends its time on the decisions only people can make.

From year-end firefight to monthly habit

The biggest change is not the speed of the year-end cleanup. It is that the cleanup stops being a year-end event.

When an agent works the GR/IR account every month, lines rarely get old. An invoice that went to the wrong mailbox gets found in week three instead of month nine, while the supplier still remembers sending it and before anyone starts charging late fees. A missing receipt gets confirmed while the site manager still remembers the crane. A short shipment gets claimed while the carrier's damage report is fresh.

The monthly view also starts to show patterns that were invisible before. One supplier always invoices to the old mailbox, so you update their master data once. One construction site never posts receipts, so you fix the handover with the site team. One buyer never updates prices on purchase orders, so the price blocks keep coming. These patterns feed directly into supplier performance tracking, and they turn GR/IR from a balance you clean up into a signal you can act on.

The account also becomes a fair measure of how well purchasing, receiving and accounts payable work together. A GR/IR account that stays small is a sign that documents are flowing to the right place at the right time. A growing one is an early warning, months before it shows up as an audit finding or an angry supplier.

What the auditor sees in January

Go back to the controller from the opening. Imagine she started in early November instead of mid-December.

By the time the auditors arrive, the open balance is €310,000 across 380 lines. That is not zero, and it should not be. Some goods arrived in the last week of December and their invoices are genuinely on the way. Some disputes with suppliers are still being negotiated. What matters is that every remaining line has a cause, a supporting document and a named owner.

The auditor pulls 25 items. For each one, the controller opens the line and shows the delivery note, the supplier statement or the email that explains it. The conversation takes an afternoon instead of a week. Nobody has to call a buyer who changed roles in June.

The €1.8 million was never really an accounting problem. It was 4,200 small questions with answers sitting in mailboxes, folders and supplier statements. The work was always about finding those answers and putting them in front of the right person before the deadline. Starting now gives you enough runway to do exactly that.

If your GR/IR report is one you would rather not open this year, bring us a sample of open lines. We will show you what the paper trail behind them looks like.