What Is a Goods Issued Note (GIN)? Definition and Uses

Contents

• What a goods issued note actually is
• What goes on a GIN: the fields that matter
• GIN vs GRN vs delivery note
• The three reasons stock gets issued
• Why untracked issues break your stock figure
• A worked example: the drift nobody logged
• Where the GIN breaks down on spreadsheets and paper
• The owned-system fix: log the issue at the point it happens
• Do you even need a formal GIN?

What a goods issued note actually is

A goods issued note is created at the point stock leaves a location, and it records what physically went out and where it went. It is the exit counterpart to receiving. When goods arrive, a business raises a goods received note to confirm what actually turned up against the order. The GIN does the same job at the other end of the shelf: it is the confirmed, dated statement that a specific quantity of a specific item has left, so the stock record can be reduced by exactly that amount and no more.

The reason the document has to exist as a discrete record is that stock leaves for reasons that are not always a sale. A sale generates an invoice and usually a delivery note, so it leaves a trail. But stock also goes to the shop floor to be consumed in production, gets drawn for samples or internal repairs, is written off as damaged, or is moved to another site. None of those necessarily produce an invoice. If the only thing that reduces your stock figure is a sale, then every non-sale issue is invisible to the system — the goods are gone from the shelf but still sitting in the numbers. The GIN is the mechanism that makes a non-sale departure as visible as a sale.

What goes on a GIN: the fields that matter

A goods issued note does not need to be elaborate, but it needs to carry enough to reduce stock correctly and be traced later. Stripped to essentials, it holds a small set of fields, each doing a specific job:

• GIN number — a unique reference so the issue can be found and matched, and so the same issue isn’t booked out twice.
• Date and time of issue — when the stock actually left, which governs the stock timing and the accounting period it falls in.
• Item code and description — what was issued, in your own terms, not a loose description someone has to interpret later.
• Quantity issued — the exact number that left. This is the figure that reduces the stock record.
• Issued from (location) — the bin, rack, or store the stock came out of, so multi-location figures stay right.
• Reason / destination — production job, sales dispatch, internal use, sample, write-off, transfer. This is the field that turns a bare deduction into a traceable movement.
• Reference — the works order, sales order, or job number the issue belongs to, so cost and consumption tie back to the right place.
• Issued by / authorised by — who released the stock, so there is accountability if a discrepancy surfaces weeks later.

The two fields people leave off are the two that cost the most: the reason/destination and the reference. Drop those and the GIN degrades into “some stock left” — which reduces the count but tells you nothing about why, which job to charge it to, or whether the issue was even legitimate. A reason-less issue is how genuine consumption and quiet shrinkage end up looking identical in the numbers.

GIN vs GRN vs delivery note

These three get confused constantly, usually because the delivery note looks like it already does the job. They are three different documents, doing three different jobs, at two different ends of the shelf:

The delivery note is the trap, and for the opposite reason it’s a trap in receiving. A delivery note only exists for a sale — it’s the customer-facing paperwork that travels with a dispatch. It says nothing about stock issued to production, drawn for internal use, or written off. So if you treat the delivery note as your only outbound record, every non-sale issue vanishes, and even for sales the delivery note is written for the customer, not structured to reduce your stock by line and location. The GIN is the internal document that covers every reason stock leaves, sales included. A dispatch generates both: a delivery note for the customer and, behind it, an issue that reduces your own stock figure.

The three reasons stock gets issued

Almost every issue falls into one of three buckets, and a GIN should make clear which one it is, because each one behaves differently in your numbers.

Issued to production

Raw materials and components leave the store to be consumed in a manufacturing or assembly job. The GIN here is what backs the material consumption against a works order — it’s how you know a job actually drew the quantity the recipe said it would, and it’s the raw feed for accurate job costing. Issue material without a note and the job’s true material cost is a guess, and your raw-material stock reads high because the consumption never came off.

Issued for dispatch

Finished goods are picked and sent to a customer. This is the issue most businesses do track, because a sale forces the deduction. But even here the issue and the pick can drift: a picker pulls an extra unit to replace a damaged one, a short-pick goes out without the shortfall being logged, and the stock reduces by the ordered quantity, not the picked quantity. The GIN records what physically left, which is not always what the order said.

Issued for internal use or write-off

Stock drawn for samples, marketing, R&D, staff use, repairs, or written off as damaged or expired. This is the bucket that leaks hardest, because none of it generates an invoice and none of it is anyone’s job to record. A unit taken off the shelf for a photoshoot and never booked out is, from the system’s point of view, still on the shelf — forever, until a stock count finds the hole.

Why untracked issues break your stock figure

Here is the core mechanic, and it’s worth being blunt about it. Your system stock figure is a running total: opening stock, plus everything booked in, minus everything booked out. Receiving is usually booked in with reasonable care — there’s a supplier invoice chasing it, so someone has a reason to record it. The out-side is where the discipline collapses, because a lot of what leaves has nothing chasing it.

Every issue that happens physically but isn’t recorded creates a positive error in your stock figure — the system thinks you have stock you don’t. And because issues are far more frequent, more distributed, and less invoice-backed than receipts, untracked issues are the single largest contributor to the gap between your system figure and the physical shelf. This is a leading cause of stock discrepancies: not theft, not miscounting on receipt, but stock that left the building with no note behind it.

The knock-on effects compound:

• You oversell. The system shows stock that isn’t there, so an order is accepted that can’t be fulfilled. Untracked issues are a direct route to overselling — the customer buys air.
• Reorder points misfire. A min/max or reorder-point rule triggers off the system figure. If that figure is inflated by unlogged issues, the reorder fires late, and you stock out on something the system swore you had.
• Your stock record stops being trusted. Once staff learn the stock record is wrong “often enough,” they stop believing it and start checking the shelf by hand — which is the exact manual work the system was supposed to remove.
• Costs land in the wrong place. Material issued to production but not logged against the job means that job looks cheaper than it was, and every quote built off that costing is understated.

A worked example: the drift nobody logged

The clearest way to see the point of a GIN is to watch a stock figure drift over a single month. Say you hold a component with a clean opening figure — system and shelf agree at 500 units.

Over the month, the following happens:

• 420 units are picked and dispatched against sales orders. These are recorded, because each sale forces the deduction. System reduces to 80.
• 40 units are issued to a production job to build a sub-assembly. The material is drawn from the shelf, but the issue is never booked out — the shop floor “just took what they needed.”
• 6 units are pulled as samples for a trade show. Nobody raises a note.
• 4 units are damaged in the rack and quietly binned. No write-off is recorded.

At month-end the system says 80 units. The shelf holds 30. Fifty units — ten percent of the opening figure — have left the building with no goods issued note behind any of them. Nothing was stolen. Every single unit went somewhere legitimate. But because 50 units left without an issue being logged, the system is overstated by 50, and the first person to find out will be either a stock counter during a cycle count, or worse, a customer whose order the system accepted against 80 units that were really 30.

That is the entire failure mode in one paragraph: the out-side wasn’t recorded, so the figure inflated, so the shelf and the system diverged by exactly the quantity nobody wrote down. A GIN on each of those three non-sale issues would have kept the two numbers locked together at 30.

Where the GIN breaks down on spreadsheets and paper

The GIN concept is sound. What fails is the way most growing businesses run it. The typical setup is: sales dispatches reduce stock through the sales system (if you’re lucky), and everything else — production draws, samples, write-offs, transfers — is either recorded on a paper pad that gets typed up “later,” or not recorded at all. Each has the same fault: the moment stock leaves and the moment it’s recorded are separated, and in that gap the record is lost.

The failure modes are predictable:

• The issue never gets entered. Material is drawn for a job, the note sits in a pocket, and the spreadsheet update waits until an evening that never comes. The stock figure stays high.
• Non-sale issues have no home. There’s a route for a sale to reduce stock, but no obvious place to record a sample, a write-off, or an internal draw — so those issues simply don’t happen in the system.
• Production consumption is estimated, not counted. The job is closed against the recipe quantity, not the actual quantity issued, so overuse and scrap never surface and the raw-material figure drifts.
• Transfers between sites go one-legged. Stock leaves site A but the corresponding receipt at site B is entered days later, so for a window the same units are either double-counted or missing — a classic multi-location failure.
• There’s no authorisation. Anyone can take anything off the shelf, and because the deduction and the taking are separate acts, nobody notices the pattern until the annual count exposes the hole.

None of these are people being careless. They are a document being asked to do a real-time job in a tool with no memory and no way to force the record at the moment stock moves. The paper GIN doesn’t break because the team is lazy — it breaks because recording the issue is a separate second action, and separate second actions are the first thing to get dropped when the floor is busy.

The owned-system fix: log the issue at the point it happens

The fix is not a stricter rule about filling in the pad. It is to make recording the issue the same action as making the issue — so the stock figure moves at the exact moment the stock does, and there is no gap for the record to fall into.

In a right-sized operations control system that you own, issuing stock is a single logged action rather than a physical event plus a paperwork event. When material is drawn for a job, a picker scans it against the works order; when a dispatch is picked, the pick is the issue; when a sample or write-off happens, it’s booked out against a reason code on the spot. That one action does several jobs at once:

• It creates the GIN as a permanent, dated, referenced record of what left and why.
• It reduces stock immediately, so the system figure equals the shelf in real time — no overnight lag, no re-keying.
• It ties the consumption to a job or order, so material cost lands where it belongs and job costing runs on real quantities.
• It enforces a reason, so every departure is classified — sale, production, sample, write-off, transfer — and shrinkage can’t hide inside “miscellaneous.”

Capture the issue once, at the point reality happens, and the same fact drives the stock record, the job cost, and the reorder trigger. Nothing is re-typed, so nothing drifts. This is the practical meaning of an inventory system that logs movements as they occur rather than reconstructing them afterwards: the goods issued note stops being a form someone might fill in later, and becomes a by-product of the act of issuing that you can’t skip. It’s the same discipline that a proper goods-receiving process applies to the in-side — and the same principle behind three-way matching on the buying side, where the control only works because the physical event is captured, not assumed.

Do you even need a formal GIN?

Honest answer: not always, and it’s worth saying so. If you hold very little stock, issue it rarely, and the same person who picks it also owns the numbers, a formal goods issued note can be more ceremony than control. A careful eye at low volume may genuinely be enough.

The point where you do need one is fairly sharp. It arrives when stock leaves for reasons other than sales — production draws, samples, write-offs, transfers — because those are the issues nothing else records. It arrives when picking and record-keeping are done by different people; when volume is high enough that nobody can hold the day’s movements in their head; or when a stock count has already found a gap you couldn’t explain. Any one of those, and the GIN stops being paperwork and becomes the thing that keeps your system figure equal to your shelf.

If that’s where you are — too busy for the paper version, not ready for a full ERP — the question isn’t whether to keep a goods issued note. It’s whether every issue, sale or not, is being logged at the point it happens, or reconstructed later from memory and a pad. Because the second version doesn’t keep your stock accurate. It just tells you, once a year, how far it drifted.