Goods Delivery Note (Internal)

The record you hand a customer when goods are delivered against a sales order, a jobsheet or an outbound delivery order: it knocks off the upstream document’s open lines so the order shows what has gone out. It is a non-posting document — FINAL moves no stock and writes nothing to the ledger; stock leaves through the stock-out document you raise alongside it. The only lasting effect of FINAL is on the open-line queue, and that depends on the company’s Knock Off Configuration; the journal error the job queue logs for every FINAL note is expected, not a missing entry.

Your job, and the screen for it

Overview

The Goods Delivery Note (Internal) is the document you raise when goods are handed to a customer against a sales order, a jobsheet or an outbound delivery order. It carries the customer, the delivery address, the sales agent and the itemised lines, and it knocks off the open lines of the upstream document so that the order shows what has been delivered. It is a non-posting document: FINAL neither moves stock nor writes to the general ledger (both signums are fixed at 0 in the backend — see Lifecycle and effects). Stock leaves the location through the stock-out document you use alongside it (delivery order stock-out or sales GIN).

The applet was cloned from the Sales Credit Note applet. That is why the create/edit screens still carry a Settlement tab and a Contra tab, and why the success toast after Create reads Sales CreditNote created successfully. These are cosmetic leftovers; the document created is always a Goods Delivery Note (Internal).

Where it fits

Module: Inventory.

Screens and menus

Left menu

• Internal Goods Delivery Note — the document listing. Columns: Goods DeliveryNote No, Posting Status, Status, Branch, Customer Name, Sales Agent, Created Date, Created by. The listing has a + button (create), a column toggle, and a FINAL button that finalises every selected row that is not yet FINAL (bulk FINAL).
• Line Items — a cross-document listing of delivery-note lines (Goods DeliveryNote No, Item Code, Item Name, Qty, Unit Price, SST/VAT/GST, Txn Amount) with a line editor. That editor does not check whether the note is FINAL: its SAVE and DELETE stay available on the lines of a finalised note. Treat a FINAL note’s lines as the record handed to the customer and do not edit them from here.

Create screen — buttons RESET and CREATE (CREATE is disabled while the Main Details form or the Account > Entity Details form is invalid). Tabs: Main Details, Account (sub-tabs Entity Details, Bill To, Ship To), Lines, Settlement, Department Hdr, Contra.

Edit screen — buttons RESET, FINAL, SAVE. Tabs as on the create screen plus Attachments and Export. A DELETE button (two-click confirm) appears below the tabs only when the setting SHOW_DOCUMENT_DELETE_BUTTON is on and the document is not FINAL.

Adding a line — the line picker opens with tabs Search Item, KO By Sales Order Item, KO For Sales Order Item, KO By Jobsheet Item, KO For Jobsheet Item, KO By Delivery Order Item, KO For Delivery Order Item, Copy Quotation Item. The item form then shows Main Details, Delivery Instruction, Department, Costing Details (hideable), Pricing Details and Issue Link, plus a Serial Number, Batch Number or Bin Number tab depending on the item’s sub-type. On a line that has been saved, two more tabs appear: Doc Link, and Delivery Details, which lists every delivery job carrying the line — trip, driver, vehicle, job dates, delivery status and the recipient’s name. That makes the note the place to answer “which van took it, and who signed for it?” without opening the delivery applets.

Settings menu (System Configuration): Application Settings, Default Selection, Printable Format Settings. Settings also has Webhook, Feature Visibility, Client-Side Permission, Permission Set, User / Team / Role Permission screens from the shared library; the settings landing page redirects to Feature Visibility.

Personalization menu: Default Selection, Sidebar.

Screenshots of this applet have not been added to this page yet (the previous page had none either).

Configuration

Before you can use it

• Company, branch and location in the Organisation applet. Branch, Location and Company are required on the Main tab; selecting a branch fills the company.
• Knock-off configuration on the company (Organisation → Company → Knock Off Configuration). The KO For tabs only list lines that the upstream document’s FINAL placed in the open-line queue; without an enabled source → Goods Delivery Note row there is nothing to knock off.
• Customers in Customer Maintenance — Entity Id is required on the Account tab; the customer’s credit terms feed the Credit Terms drop-down.
• Employees in the Employee applet — the Sales Agent field is required by the form.
• Member cards in Membership Admin — the Member Card field is declared required by the form (see Troubleshooting).
• Items in Doc Item Maintenance; serial / batch / bin sub-types drive the extra line tabs. Tax codes for the line SST/GST/VAT and WHT selectors come from Tax Configuration.
• Permissions — BigLedger checks the targeted permissions TNT_API_DOC_INTERNAL_GOODS_DELIVERY_NOTE_CREATE_TGT_GUID, …_UPDATE_TGT_GUID, …_READ_TGT_GUID and …_DELETE_TGT_GUID, assigned through the Permission Set / User / Team / Role screens under Settings.
• A printable format uploaded under Settings → Printable Format Settings for this document type, if you want to print or export the note.

Applet settings

Settings live in three places. Anyone with access to the applet’s Settings menu can change them; there is no per-setting authority.

1. Application Settings is the shared field-configuration screen. The screen does not know this applet’s tab layout, so the ten tab-level toggles other document applets get (the KO For, Main Payment, Delivery Details, Department, AR/AP, Trace Document, Doc Link and Export tab hides, plus Enable multiple KO and Enable edit payment date) never render for this applet — you cannot switch them here, and nothing in this applet would read them if you could. What remains is 138 toggles and inputs, saved together when you press Save.
2. Default Selection (applet-local, and the same screen again under Personalization) shows Default Branch and Default Location. It is not functional: it neither loads nor saves, no form in the applet reads DEFAULT_BRANCH / DEFAULT_LOCATION, and changing a value produces an error in the browser console. Leave it alone.
3. Printable Format Settings (applet-local) lists the formats uploaded for this document type and lets you mark one as default (PRINTABLE).

Of the 138 controls rendered on Application Settings, 24 have an effect in this applet: the 21 line-level hides below (the twenty price, quantity and amount boxes and the Costing Details tab), the delete button, the listing’s default posting status and the Sales Man employee categories. PRINTABLE, set from its own screen, is the twenty-fifth. The line-level ones:

The rest of the price and amount hides work the same way, one switch per box on the line form, each reopened by the permission of the same name: Unit Price STD by UOM (exclusive and inclusive of tax), Unit Discount and Unit Discount by UOM, Unit Price Net and Unit Price Net by UOM, Unit Price Transaction and its by-UOM version, and the four amounts — STD Amount, Discount Amount, Amount Net and Txn Amount.

A hide removes the box, not the figure. The line still works out every price and amount behind a hidden box and saves it with the note. So a hide tidies the form for people who do not need the pricing chain; it is not an access control over selling prices. If a role must not see prices, that is the administrator’s decision about who is given this applet at all, and the check is to sign in as that role and look through a saved note.

Every HIDE_* setting is overridden by the client-side permission of the same name (SHOW_*) — a tenant-wide hide can be reopened per role (all 22 SHOW_* codes exist for this applet, see Feature visibility).

Also honoured

• SHOW_DOCUMENT_DELETE_BUTTON — rendered on Application Settings (section Doc Settings), saved with the rest, and honoured by the edit screen. On: the DELETE button appears on non-FINAL documents. Off / unset: no delete from the UI.
• DEFAULT_POSTING_STATUS (Default Posting Status, listing group) — pre-selects the Posting Status filter in the listing’s Advanced Search; it applies when the user runs that search, not when the listing first opens.
• Sales Man (Doc Settings) — limits the Sales Agent list to employees in the chosen categories (see Fields).

Rendered and saved, but with no effect in this applet — the remaining ~116 controls on Application Settings: the rest of the listing group (the Final and Void button hides, default transaction date, sort order, Show draft button …), the header field hides (tracking ID, permit number, reference, remarks, credit terms, location, currency …), the Vertical UI, External Documents, Entity Details, Billing / Shipping, Department, Contra and Email groups, Enable auto popup, Print final documents only, the line-item sub-tab hides (delivery instruction, department, doc link, delivery details, attachments, batch number, issue link), Disallow line item edit, the forex data-source and currency-rate lock, and the AR/AP and knock-off hides. Switching any of them changes nothing on this applet’s screens. Two of them deserve a sentence of their own, because a reader switches them on for a reason: Print final documents only does not stop a draft note printing here (the Sales Invoice applet honours it), and Disallow line item edit leaves every line editable (the Purchase Order, Purchase Invoice and Purchase Requisition applets honour it). One toggle does something, but only on the settings screen itself: Hide bin number hides and clears the Mandatory bin number checkbox beside it; the bin column on the line is untouched. Many of the same keys are live in sibling document applets, so the claim is about this applet, not the keys.

Document behaviour settings

• Status flow — not configurable. The only transition offered is to FINAL (edit screen button, or the listing’s bulk FINAL). No workflow setting applies.
• Posting — not configurable and, for this document type, absent: see Lifecycle and effects.
• Printables — Settings → Printable Format Settings uploads printable formats for this document type and stores the default in PRINTABLE. The Export tab prints the selected format and downloads <document no>.pdf.
• Approval / e-Invoice — no controls.

Settings in other applets that control this applet

Feature visibility / permissions

The applet has 22 client-side permission codes: SHOW_AMOUNT_NET_EXCL_TAX, SHOW_AMOUNT_STD_EXCL_TAX, SHOW_AMOUNT_TXN, SHOW_COSTING_DETAILS, SHOW_DISCOUNT_AMOUNT_EXCL_TAX, SHOW_LAST_PURCHASE_PRICE, SHOW_QTY_BASE, SHOW_QTY_UOM, SHOW_TAX_CONFIG_SELECTION, SHOW_UNIT_DISCOUNT, SHOW_UNIT_DISCOUNT_UOM_EXCL_TAX, SHOW_UNIT_PRICE_NET_EXCL_TAX, SHOW_UNIT_PRICE_NET_UOM_EXCL_TAX, SHOW_UNIT_PRICE_STD_EXCL_TAX, SHOW_UNIT_PRICE_STD_INCL_TAX, SHOW_UNIT_PRICE_STD_PRICING_SCHEME, SHOW_UNIT_PRICE_STD_UOM_EXCL_TAX, SHOW_UNIT_PRICE_STD_UOM_INCL_TAX, SHOW_UNIT_PRICE_TXN, SHOW_UNIT_PRICE_TXN_UOM_INCL_TAX, SHOW_UOM_TO_BASE_RATIO, SHOW_WHT_CONFIG_SELECTION.

• 21 of them re-enable the line field hidden by the HIDE_* setting of the same suffix for the roles that hold them; SHOW_COSTING_DETAILS re-enables the Costing Details tab.
• SHOW_LAST_PURCHASE_PRICE exists but has no effect in this applet (the field it would reopen is not on the line form).
• The delete button is governed by the setting SHOW_DOCUMENT_DELETE_BUTTON, not by a permission; no SHOW_VOID_BUTTON / SHOW_TRANSACTION_DATE codes exist for this applet.
• The Feature Visibility screen under Settings is the shared menu-hiding component; the applet has only two menu items (listing, Line Items).
• Server-side (targeted) permissions: TNT_API_DOC_INTERNAL_GOODS_DELIVERY_NOTE_{CREATE,UPDATE,READ,DELETE}_TGT_GUID, granted through Permission Set / User / Team / Role Permission. Without READ the listing is empty; without CREATE, creating is refused.

Fields

Main Details

Account

Lines (line Main Details)

Settlement, Department Hdr, Contra

• Settlement — inherited from the credit-note clone. Add Settlement asks, per settlement method type, for Date and Amount (all types), Cash Back, Card No / Name on Card / Card Issuer / Type / Card Expiry / CVV, Voucher #, Transaction No, points; the starred ones are required by the form. Nothing turns these into receipts for this document type.
• Department Hdr — Segment, G/L Dimension, Profit Centre, Project (all optional; stored on the header).
• Contra — select another document to contra against. Inherited; no ARAP balance exists for a signum-0 document, so there is nothing to contra.

Lifecycle and effects

Statuses. A new note is saved as DRAFT — the applet sends no posting status and BigLedger fills in DRAFT on creation — until you press FINAL (the advanced search offers DRAFT / FINAL / VOID as filter values). Transitions available in the applet:

• Create / Save — saved through the generic document engine, which forces amount signum 0 and quantity signum 0 on every line.
• FINAL — the edit screen’s FINAL button (refused client-side with This document has been posted if already FINAL) or the listing’s bulk FINAL. Rejections: Generic Document has already been posted to FINAL; The selected date falls within a locked fiscal period when the transaction date sits in a period locked LOCK_ALL or LOCK_TXN. Serial and batch quantity checks are skipped for signum-0 lines, the bin check runs only for lines that carry bin numbers, and the stock-balance check ignores signum-0 lines. The blacklisted-customer check applies to cashbill / invoice / order / outbound DO only, not to this type.
• After FINAL — the Main tab controls are disabled except Sales Agent and Remarks; RESET is refused; the SAVE button stays enabled. Whether the server keeps a changed agent or remark on a FINAL note was not established: if it matters, change the remark on one FINAL test note, SAVE, close and reopen it. Until then, treat a FINAL note as the record handed to the customer — whoever finalises checks the agent and remarks first, and a later correction is a note on the customer’s file, not an edit.
• VOID — no VOID control exists in this applet. There would be nothing to reverse for this type.
• DELETE — with SHOW_DOCUMENT_DELETE_BUTTON on and the document not FINAL, DELETE (click twice within 3 seconds) deletes the document: the delete permission is checked, attached files are removed, and header, lines, extensions and events are deleted, then the INTERNAL_GOODS_DELIVERY_NOTE_DELETED webhook fires.

Posting proof block

Why the journal queue shows an error for every FINAL note. The journal-posting step runs for every FINAL document regardless of type. For a Goods Delivery Note the job then fails with NO_JOURNAL_CREATED (or earlier with COMPANY_DEFAULT_GL_CODE_NOT_EXIST when the company has no default GL mapping). The failure is confined to the job queue: the document is already FINAL, and the missing journal is correct. A company can silence it by excluding the journal step — at the cost of every other document type, so in practice the failed job is left alone.

Related applets

• Sales Order (Internal) — the usual source; its open lines are consumed by KO For Sales Order Item.
• Jobsheet (Internal) — alternative source through KO For Jobsheet Item.
• Delivery Order (Internal) — alternative source through KO For Delivery Order Item; alongside Sales GIN (Stock Out), which is what actually moves the stock a delivery note describes.
• Customer Maintenance — customer, credit terms, billing and shipping addresses.
• Employee — sales agent.
• Membership Admin — member card.
• Doc Item Maintenance — items, sub-types (serial / batch / bin), pricing schemes.
• Organisation — company, branch, location, Knock Off Configuration.
• Warehouse Management — locations and bins referenced on the lines.
• Tax Configuration — SST/GST/VAT and WHT codes on the lines.

Troubleshooting

Related documentation

• Inventory module
• Standard sales workflow and Partial delivery workflow — where delivery documents sit in the sales flow (these guides do not yet cover the Goods Delivery Note itself).
• Sales Order (Internal), Delivery Order (Internal), Sales GIN (Stock Out)