Goods Issue

A Goods Issue records stock leaving a warehouse when there is no sales order, no delivery, and no customer behind the movement. It is the mirror image of a Goods Receipt: where the receipt brings stock in against an offset account, the issue takes stock out and charges it to an expense account.

In the Service Layer this is the GoodsIssues service, object code oInventoryGenExit (60) — internally an Inventory General Exit, an exit of goods from stock. It is created at /b1s/v1/InventoryGenExits.

Like the Goods Receipt, a Goods Issue has no CardCode and no CardName. The stock is not going to a customer — it is being consumed, scrapped, or written down. The counterparty is a general ledger expense account, chosen against a warehouse and an item, never a trading partner.

When it is used

A Goods Issue is the right document whenever stock must decrease for a reason that is not a sale:

• Scrap and damage — units are broken, expired, or spoiled and must come off the books at cost.
• Internal consumption — stock used by the company itself (office supplies, workshop parts, materials consumed in a task) rather than sold.
• Shrinkage write-down — a count shows fewer units than the system holds, and the shortfall is written off.
• Samples and giveaways issued to prospects or staff with no invoice.
• Disposal of obsolete inventory that will never sell.

If the goods are actually being shipped to a customer, the correct document is a Delivery (oDeliveryNotes, 15), which carries the CardCode and posts cost of goods sold against that sale. The Goods Issue exists for every stock-out that is not a customer shipment.

Key fields

The document is a small header over one or more DocumentLines. Each line names its own warehouse and quantity, so one Goods Issue can remove several items from several warehouses.

Header

Notably absent: CardCode, CardName, ShipToCode — no business partner.

Line (DocumentLines)

The AccountCode here is the meaningful choice: it names which expense the loss lands on — scrap, consumption, write-off — so the P&L reflects the real reason stock left.

GL and stock effect

Stock: the on-hand quantity of each line’s ItemCode in its WarehouseCode decreases by Quantity. This is an unconditional stock-out movement.

Accounting (perpetual inventory): the issue posts a journal entry that debits an expense and credits inventory:

DR  Expense / Write-off account   (value of goods issued)
CR      Inventory                          (same value)

The credit lowers the inventory balance-sheet account by the cost of the goods removed; the debit charges that cost to the expense account chosen by the item group’s G/L determination or the line’s AccountCode override. The value is the item’s carrying cost under its valuation method (moving average, standard, or FIFO), not a sale price — no revenue and no customer are involved.

Under non-perpetual inventory no journal entry is generated; only the quantity falls, and finance values the stock reduction periodically.

Service Layer

A minimal create payload names the reason, the item, the quantity, and the warehouse — no partner:

POST /b1s/v1/InventoryGenExits
{
  "Comments": "Scrap — water-damaged stock, warehouse 01",
  "DocumentLines": [
    { "ItemCode": "A00001", "Quantity": 3, "WarehouseCode": "01", "AccountCode": "610000" }
  ]
}

Norma’s connector and mock use the /b1s/v1/ paths shown here; a live SAP B1 on Feature Pack 2405 or later exposes the same entity under /b1s/v2/ with identical shape.

The response returns the assigned DocEntry and DocNum, and — under perpetual inventory — a TransNum pointing at the journal entry the issue created.