Procurement

Supplier Returns for Multi-Site Restaurants: How To Recover Every Credit You Are Owed

Curran Dye

August 12, 2026

When a delivery arrives short, spoiled, or wrong, the money you are owed only comes back if the return is raised cleanly and the credit note matches what you actually received. The fastest way to get there is to raise the return from the goods received note (GRN) itself, so the items, quantities and prices are already locked to that delivery and the credit claim writes itself. That one change turns returns from a re-typing exercise into a two-minute confirmation, and it is where multi-site groups stop leaking credit they are entitled to.

Raise the Return From the Received GRN, Not a Blank Form

A supplier return is the document you raise to send received stock back to a supplier and claim the credit for it. Raised from the goods received note, it opens pre-filled with the delivery's real items, quantities and locked prices, so the credit note reflects exactly what was booked in - not a figure someone re-keys from memory. You set the return quantity, and the credit calculates against the price you were actually charged.

That matters because the alternative is a blank form. When a team member types a return from scratch, they guess the price, round the quantity, and reconcile it later against an invoice that may already be paid. Pulling the return from the GRN removes the guesswork: the beef striploin you booked in at $4.20 per kg comes back as a credit at $4.20 per kg, and a 6 kg return off a 40 kg receipt lands as a $25.20 credit with no arithmetic on anyone's part. Across dozens of deliveries a week and several branches, that is the difference between credits that match and a month-end reconciliation that never quite ties out.

Four-step flow showing a supplier return raised from the received goods received note

Where Hand-Keyed Returns Leak: Over-Returns and Credit That Never Matches

The two failure modes that quietly drain returns are over-returns and mismatched prices, and both come from raising returns detached from the receipt. An over-return is a return for more than you were delivered - a team member claims 10 units back against a receipt of 8, either by mistake or because two people raised the same return. The supplier rejects the excess, the credit note and the claim disagree, and you are now in a discrepancy dispute that costs more staff time than the credit was worth.

Raising from the GRN closes both gaps. The return is capped at the received quantity, so a claim can never exceed what the delivery actually contained, and the credit-note allocation is validated before the return is submitted rather than caught weeks later. The result is that every return line agrees with its receipt on both quantity and price the moment it is created - the validation happens up front, not in a month-end investigation.

Return validation table checking each return line against the receipt, with an over-return blocked

Central Kitchen Returns: Closing the Credit-Note Gap Into Accounting

For groups that run a central kitchen supplying their own outlets, returns have historically been where the numbers fall out of the ledger. Operators described the same gap repeatedly: supplier returns raised from the central kitchen did not post to accounting, and there was no clean credit-note flow for returns coming back from the outlets the kitchen serves. Every one of those credits became a manual journal entry, keyed a second time into the accounting system, which is exactly where duplicate-entry errors creep in.

Closing that gap means the credit note posts itself. When a central-kitchen return is confirmed, its credit note is pushed to the connected accounting system automatically - the count of manual journal entries for those credits drops to 0. Finance stops re-keying returns, the ledger reflects the credit the same day it is confirmed, and the two sides of the business stop drifting apart between close cycles.

Stat callout showing zero manual journal entries for central-kitchen return credits

Decide Which Returns Need Approval and Which Should Just Clear

Not every return should move at the same speed, and treating them the same is its own kind of friction. A return to an outside supplier is a claim against another company's account, so it should carry an approval step before it is confirmed - someone signs off that the goods really are going back and the credit is correct. An internal return from an outlet to your own central kitchen is a movement inside one business, so making a manager chase an approval for it just slows the kitchen down for no control benefit.

The workable rule is to route external supplier returns through approval and let internal central-kitchen returns auto-approve and clear. External claims get the scrutiny they warrant and post to accounting on confirmation; internal returns clear the same day without an approval queue. Because returns can be raised and posted from the mobile app, the person actually holding the stock at the receiving dock can start the return on the spot, and it follows whichever path its type calls for.

Table comparing external supplier returns and internal central-kitchen returns by approval, accounting and clearing time

Before your next delivery week, pull one supplier return your team raised by hand last month and check it against its GRN: does the quantity exceed what was received, and does the credit match the price you were charged? If either is off, that is the leak this workflow closes - start by raising your next return straight from the receipt and let the credit note validate itself. If you want to see how returns fit the wider procurement workflow, explore the Supy platform.

Book a Demo with Supy - supplier returns and credit claims

Get weekly insights and tips delivered straight to your inbox.

Ready to optimize your restaurant operations?

Book a demo



Blog

Our operational insights





No items found.

Your questions  answered

Everything you need to know about Supy — from setup to integrations, pricing, and daily use. If it’s not covered here, just ask.

What is a supplier return in restaurant inventory?

A supplier return is the document a restaurant raises to send received stock back to a supplier and claim the credit for it, usually because the delivery was short, spoiled, wrong, or over-supplied. Raised well, it records which items are going back, in what quantity, and at the price you were actually charged, then produces a matching credit note. The cleanest way to raise one is directly from the goods received note for that delivery, so the return carries the real items, quantities and locked prices rather than figures re-typed from memory or guessed against an invoice that may already be paid.

How does raising a return from the GRN prevent over-returns?

An over-return is a claim for more stock than the supplier actually delivered, and it usually happens when a return is typed from a blank form with no link to the receipt. Raising the return from the goods received note caps the return quantity at what that delivery contained, so a claim can never exceed the received amount. If someone tries to return 10 units against a receipt of 8, the system blocks the excess before submission rather than letting it surface as a rejected credit weeks later. The credit-note allocation is validated up front, which keeps the claim and the credit note in agreement.

Why do central-kitchen credit notes often miss the accounting system?

In many multi-site groups, returns raised from a central kitchen were never wired into accounting, so each credit became a manual journal entry keyed a second time by finance. There was also no clean credit-note flow for returns coming back from the outlets the kitchen supplies. Because the credit lived in the inventory system but not the ledger until someone re-entered it, the two sides drifted apart between close cycles and duplicate-entry errors crept in. Closing the gap means a confirmed central-kitchen return posts its credit note to the connected accounting system automatically, so finance stops re-keying and the ledger reflects the credit the same day.

When should a supplier return require an approval step?

A return to an outside supplier is a claim against another company's account, so it should carry an approval step before it is confirmed. Someone reviews that the goods genuinely are going back and that the credit is correct, which protects you in any later dispute. An internal return from an outlet to your own central kitchen is a movement inside one business, so an approval queue adds delay without adding control. The practical rule is to route external supplier returns through approval and let internal central-kitchen returns auto-approve and clear the same day, matching the level of scrutiny to the risk each return actually carries.

Can supplier returns be raised from a mobile device at the receiving dock?

Yes. Returns can be created, managed and posted from a mobile app, which means the person physically receiving the delivery can start the return at the dock the moment they spot a problem, rather than making a note to raise it later at a desk. That timing matters, because a return raised while the delivery is still in front of you is far more accurate than one reconstructed from memory hours later. The return still follows whichever path its type calls for once submitted: an external supplier return moves into the approval step, while an internal central-kitchen return clears automatically.

How is the credit amount on a supplier return calculated?

When the return is raised from the goods received note, the credit is calculated against the price you were actually charged on that delivery, not a current list price or a re-keyed figure. The item's booked-in price is locked to the return line, so returning 6 kg of an item received at $4.20 per kg produces a $25.20 credit with no manual arithmetic. Because the price and quantity both come straight from the receipt, the credit note matches what the supplier's own records show, which is what keeps the claim from turning into a back-and-forth over how much you are actually owed.

Which returns post to accounting automatically and which post on confirmation?

Both external and internal returns reach accounting, but on different triggers. An external supplier return posts its credit to the connected accounting system once it clears its approval step and is confirmed, so the ledger updates as soon as the claim is signed off. An internal central-kitchen return is auto-approved and posts its credit note automatically, so it reaches accounting the same day without a manual step. In both cases the point is that the credit lands in the ledger from the returns workflow itself, rather than waiting for finance to re-enter it by hand, which is what previously let inventory and accounting drift apart.