Supplier Delivery Order Applet
Let a supplier’s own staff raise delivery orders inside your BigLedger. What they create is your ordinary delivery order, which moves no stock and posts nothing, and it cannot be finalised here: finalising, voiding and printing happen in the internal Delivery Order applet.
Your job, and the screen for it
| The job | Screen or tab | Read |
|---|---|---|
| Announce a delivery as the supplier’s clerk — quantities are typed, unchecked against your purchase order | Supplier Delivery Order Listing › +, then Account › Select Customer, Lines › Search Item, Delivery Driver, SAVE | A delivery in two lots to GS-KV-01 |
| Read what the supplier announced, as the buyer | in the Delivery Order (Internal) applet, among your outbound delivery orders, with the supplier as the party | What success looks like: one delivery, two screens |
| Receive the goods and reduce the purchase order — the supplier’s delivery order never does either | in the Purchase GRN (Internal) applet, a GRN against the purchase order | What it will not do, and who does it instead |
| Finalise, void or print — not here; leave supplier-raised orders as drafts, since finalising can open their lines for invoicing | in the Delivery Order (Internal) applet; VOID is refused once another document has knocked it off, or with e-Invoice switched on | Lifecycle and effects |
| Name the driver who brings the van — with no driver linked to the supplier, name the driver in Remarks | Delivery Driver, after the supplier is picked on Account | Troubleshooting |
| Give the supplier’s clerk access | Supplier Applet › Login tab; the supplier record also flagged as a customer; Settings › Permission Wizard | Before you can use it |
Overview
The Supplier Delivery Order Applet is a supplier-access applet. A user whose login is linked to a supplier record (see Supplier Applet) opens it to create and keep delivery orders on that supplier’s behalf. The document it writes is your company’s ordinary outbound delivery order (screen code OBDODR), with the supplier as the document’s party — the same document the Delivery Order Applet (Internal) works on, seen through a supplier’s window.
What it is to you, the buyer. It is advance notice in your own system, typed by the supplier, and nothing more until somebody on your side acts on it:
- It does not reach your purchase order. The document has no link to purchase orders at all: the only tabs that pull lines from another document read sales orders and sales invoices. Your order’s outstanding quantity falls when your store finalises a goods received note (GRN) against it, never because of a supplier’s delivery order.
- It does not reach your GRN or your stock. BigLedger stores every line of this document with no stock or money effect, so saving it — or finalising it — moves no unit and posts no journal. Finalising is not without effect, though: where your knock-off rows let a delivery order be invoiced, it opens the lines, which then show in Stock Availability and the supplier’s open credit (see Lifecycle and effects).
- You see it in Delivery Order (Internal), among your own outbound delivery orders, with the supplier as the party; and a driver named on it sees it in the Driver Delivery Order Applet. Naming one needs a driver already linked to the supplier record, and this build cannot create that link (see Troubleshooting).
The scenario it serves. A distributor that delivers to your branches every week sends a dispatch clerk’s list ahead of every van anyway. Giving that clerk a login lets the list arrive inside BigLedger, under your branch and location, with the driver named, so your receiving clerk reads it where the GRN is raised. The finalise, void and print handlers are in the applet but switched off, so the design leaves every decision about the document with you; whether a supplier was ever meant to finalise here has not been settled, so treat what they send as notice, not as a receipt.
The build your tenant runs is older than the applet’s current source. It has one menu entry, Supplier Delivery Order: the Driver Listing that registers a supplier’s drivers, the supplier-only account picker and the Vehicle No and Delivery Date fields exist in the source but are not in the deployed build. This page describes the deployed build.
Where it fits
| Kind | Document / applet | What it means here |
|---|---|---|
| Upstream — access | Supplier → Login tab | The login must be linked to the supplier record before anything shows. The link decides which delivery orders the login lists. |
| Upstream — the party | Supplier record flagged as a customer too | The deployed picker is the customer listing, so the supplier record must also be flagged as a customer, or Select Customer is empty. The login may also need permission to read customers. |
| Upstream — drivers | A driver linked to the supplier record | The Delivery Driver picker offers only drivers already linked to the document’s supplier. This build has no Driver Listing to create that link. |
| Upstream — company | Organisation | Company, branch and location are required; the company’s knock-off rows decide which pull-in tabs appear. |
| Downstream — finalise | Delivery Order (Internal) | Your staff finalise, void or print there. Read Lifecycle and effects before anyone does: finalising treats it as goods going out to the supplier. |
| Downstream — driver | Driver Delivery Order | The named driver sees the order and can update the vehicle number and delivery date there — only where a driver is already linked to the supplier, since this build cannot make the link. |
| Sibling — confirm the order | Purchase Order Supplier Access | Use that applet, not this one, when the supplier must read your purchase order or acknowledge it. Use this one only when you want the supplier to type up what is on the van. |
| Sibling — see the receipt | Purchase GRN Supplier Access | The supplier sees your finalised goods received notes there; a receipt you book as GRN Stock In is not listed there, so for that delivery the supplier asks your purchasing team. Either way your receipt, not this delivery order, is the record that counts. |
| Blast radius | Your Stock Availability, the supplier’s credit, your delivery-order listing | Saving changes none of them. Finalising in the internal applet affects inventory and sales figures: the units appear as delivery-order quantity at the location, and as open credit against the supplier’s account. |
| Pairing | Your GRN, and a call or e-mail with the supplier | Used alongside the GRN your store raises against the purchase order, and an agreed way for the supplier to say the van is coming. |
Screens and menus

Supplier Delivery Order Listing shows the outbound delivery orders whose party is a record linked to the login. It has no posting-status column: the Status column is the record status, so a supplier cannot tell from the listing whether you have finalised a document.
Edit Supplier Delivery Order has SAVE and, where switched on, DELETE (two clicks). FINAL, DISCARD, VOID and CLOSE are not shown to anyone.
Line Item Create offers Search Item, plus KO For Sales Order when the company has an enabled sales-order-to-delivery-order line flow, and KO For Sales Invoice when an enabled delivery-order flow exists. Neither reads a purchase order. Treat KO For Sales Invoice as unsupported here.
Configuration
Before you can use it
- A login linked to the supplier record, on the Supplier Applet’s Login tab. With no link the listing and picker are empty, whatever the permissions.
- The supplier record also flagged as a customer — the deployed picker reads the customer listing, so the login may also need permission to read customers.
- Permission on outbound delivery orders: create for +, update for SAVE, delete for DELETE; the listing shows branches the login may read. Assign them through Settings → Permission Wizard.
- Items with transaction class
PNSfor Search Item. - No GL codes, tax codes or numbering are needed: the document has no journal and the numbers are assigned by the server.
Applet settings
Settings live under Settings → Application Settings and apply to every user of the applet. Only the ones that change behaviour are listed; the rest show or hide a field you can see.
| Setting | What it does here |
|---|---|
HIDE_LOCATION | Hides the Location picker, but Location stays required, so a document without one cannot be saved. Set DEFAULT_LOCATION under Default Selection so the hidden control is filled. |
HIDE_GENDOC_SAVE_BUTTON | Removes SAVE. A new document still becomes a draft automatically (step 2 of A delivery in two lots to GS-KV-01, below), but edits made after that are not stored. |
SHOW_DOCUMENT_DELETE_BUTTON | Shows DELETE on documents that are not FINAL. Read when the screen opens. |
DEFAULT_POSTING_STATUS | Has no effect in this build: the listing’s search does not send it. |
Default Selection (applet-wide) and Personalization → Default Selection (per login) pre-fill company, branch and location; the personal value wins.
Settings in other applets that control this applet
| Setting | Where it is set | Effect here |
|---|---|---|
| Supplier ↔ login link | Supplier Applet → Login | Which documents the login lists, and which records it can pick |
| Sales order → delivery order line flow | Organisation → Company → Knock Off Configuration | The KO For Sales Order tab is shown when the line screen opens and finds this row enabled for the document’s company. If the row is missing or switched off, the tab is absent and nothing on the screen says why. The screen reads the row as it opens, so reopen it after the configuration changes |
| Delivery order → sales invoice line flow | Organisation → Company → Knock Off Configuration | Decides whether finalising (in the internal applet) opens the lines for invoicing — and so whether they count in Stock Availability and the supplier’s credit |
| Printable formats and e-mail templates | Delivery Order Applet (Internal) | Shared with this applet’s settings screens; this applet prints and sends nothing |
Fields
Only the fields with a consequence you cannot see are listed.
| Field | What to know |
|---|---|
| Doc No (Tenant / Company / Branch) | Assigned by the server; blank until it does. Use Doc No when the supplier and your clerk compare documents. |
| Location | Required even when hidden. It is the location your receiving clerk will search under, so the supplier should pick the receiving location, not their own warehouse. |
| Delivery Driver | Disabled until the supplier is chosen on Account; then offers the drivers linked to that supplier. Naming one is what puts the order in that driver’s applet. |
| Currency Rate | SAVE is refused when the currency differs from the base currency and the rate is zero or less (“The currency rate cannot be ZERO or negative.”), except on the first save. |
| Account → Entity Id | Picked through Select Customer, which lists the records linked to the login that are also flagged as customers. |
| Lines → Quantity | Typed by the supplier. It is not checked against your purchase order. |
| Lines → UOM ratio | The UOM and its ratio to the base unit come from the item and cannot be typed; the ratio is shown read-only. |
The supplier on this delivery order is a copy
When the supplier is picked, BigLedger copies its name, code, contact, identity and addresses onto the document, and never refreshes them. Correcting the supplier record changes the next document, not this one. The one thing that reaches documents already raised is an entity merge, which rewrites the copies on every document pointing at the surviving record.
Lifecycle and effects
| State | How you get there | What happens behind the screen |
|---|---|---|
| Placeholder | + on the listing | A temporary document exists before anything is typed. |
| Draft | Automatically once branch, location, currency, supplier and one line are set and Main Details changes; or SAVE | Stored with every line at no stock and no money effect. Lines pulled from a sales order are linked to it; the sales order’s open quantity does not fall yet. |
| Final | Only in Delivery Order (Internal) | See below. |
| Deleted | DELETE, with delete permission | The row disappears from the listing. |
What finalising does — and why to think before doing it. Finalising in the internal applet locks the document and runs its follow-on jobs. It posts no journal and moves no stock, because the lines carry no stock or money effect. But where your company’s knock-off rows let a delivery order be invoiced, finalising opens its lines for invoicing: from then on, Stock Availability shows them as open delivery-order quantity at the location, and they count toward the supplier’s open credit as a customer. A supplier’s delivery order finalised by mistake — in the worked example below, the first lot — therefore shows 120 wireless-audio units on an open delivery order to the distributor that just delivered them to you. Leave supplier-raised orders as drafts unless you have a reason to invoice against them. Void one finalised by mistake in the internal applet; VOID is refused once another document has knocked it off, and on tenants with e-Invoice switched on.
Where its figures come from. Nothing on this document is read from your purchase order. The quantities are typed, or taken from the open sales-order lines when KO For Sales Order is used; the supplier details are a snapshot taken at the time the supplier was picked; the document numbers are the server’s.
A delivery in two lots to GS-KV-01
GadgetSphere Sdn Bhd (GS) has ordered 200 wireless-audio units from a regional accessory distributor on a finalised purchase order for branch GS-KV-01. The distributor’s dispatch clerk has a login linked to the distributor’s supplier record, with this applet installed. The distributor delivers 120 units this week and 80 the next.
- The clerk raises a delivery order for the first lot. + creates the document straight away. The clerk picks branch
GS-KV-01and its location, the distributor on Account → Select Customer, the item on Lines → Search Item with quantity 120, and the driver on Delivery Driver. The quantity is what the clerk types: nothing on this screen reads your purchase order’s 200 or what is still outstanding on it — the clerk gets those from the Purchase Order Supplier Access applet. - It becomes a draft before the clerk presses SAVE. In this build, once branch, location, currency, the supplier and one line are all set, the next change on Main Details turns the document from a placeholder into a draft on its own. SAVE then stores the rest. Nothing posts.
- Your receiving clerk at GS-KV-01 sees it in Delivery Order (Internal) as a draft outbound delivery order with the distributor as the party. Read it as the packing list: 120 wireless-audio units, which driver. The driver sees the same order in their own applet.
- The van arrives. Your clerk counts the units, then finalises a GRN for 120 against the purchase order in Purchase GRN (Internal). That GRN, not the supplier’s delivery order, takes 120 off the order: 80 remain outstanding. Stock and the payable are booked by the purchase invoice that knocks off the GRN, or at receipt if you use Purchase GRN Stock In.
- The second lot. The clerk raises a second delivery order for 80; your store finalises a second GRN for 80. The purchase order now has nothing outstanding.
- Leave both supplier delivery orders as drafts, or delete them once received if your company allows it. Do not finalise them to “close” them: see Lifecycle and effects.
If the counts differ — 118 in the van against 120 on the delivery order — the GRN says 118. Nothing reconciles the two documents for you: comparing what the supplier announced with what arrived is your receiving clerk’s job, at the door, before the GRN is finalised.
What success looks like: one delivery, two screens
Run this the first time a supplier uses the applet. It takes a minute with the supplier on the phone.
- The supplier opens their newest delivery order and reads out its Doc No, branch, location and each line’s item and quantity.
- On your side, open Delivery Order (Internal), find the same Doc No, and check the party is the supplier and the lines match.
- Open the matching purchase order. Its outstanding quantity has not moved because of the delivery order. It moves only when your GRN is finalised.
- If a driver was named, the driver opens the Driver Delivery Order applet and sees the same Doc No.
You pass when all four agree. If the supplier cannot find the document, they have opened the listing under a login linked to another supplier record. If you cannot find it, check you are in the company and branch the supplier picked.
What it will not do, and who does it instead
- Confirm or change your purchase order. Your buyer reads the delivery order and decides; if the supplier is shipping fewer units, your buyer changes or closes the order in Purchase Order (Internal).
- Receive the goods. Your receiving clerk does, with a GRN against the purchase order, after counting what came off the van.
- Register a driver in this build. Ask BigLedger support who can link the supplier’s driver to the supplier record for your tenant; until then, the supplier names the driver on the delivery order’s remarks and your clerk checks the driver at the gate.
- Finalise, void, print or e-mail. Your own staff do those in Delivery Order (Internal), if at all; the supplier prints their own paperwork from their own system.
Related applets
- Delivery Order Applet (Internal) — the same document with the full action set.
- Purchase GRN (Internal) — the receipt that counts against your purchase order.
- Purchase Order Supplier Access and Purchase GRN Supplier Access — the supplier’s view of your order and your receipt.
- Driver Delivery Order Applet — the named driver’s view.
- Sales Order Applet (Internal) — the source of KO For Sales Order.
- Supplier Applet and Organisation Applet — the login link, the customer flag, company, branch, location and knock-off rows.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The listing is empty though documents exist | The login has no link to the supplier record | Link the login on the Supplier Applet’s Login tab |
| Select Customer shows nothing | The supplier record is not also flagged as a customer, or the login may not read customers | Flag the supplier record as a customer; grant customer read |
| Delivery Driver is greyed out | No supplier picked yet | Pick the supplier on Account first |
| Delivery Driver offers nobody | No driver is linked to that supplier record, and this build has no Driver Listing | Ask BigLedger support; name the driver in Remarks meanwhile |
| + is greyed out | No create permission on outbound delivery orders | Grant it in Settings → Permission Wizard |
| SAVE stays disabled | Company, branch, location or supplier missing (red tab), or no line, or no update permission | Complete the red tab; add a line; grant update |
| “The currency rate cannot be ZERO or negative.” on SAVE | The currency differs from the base currency with no rate | Enter the rate |
| SAVE refused with a serial-number lock message | Another draft holds that serial; the server refuses it until that draft is finalised or releases it | Pick another unit, or settle the other draft |
| Your purchase order still shows everything outstanding after the supplier’s delivery | Expected: the delivery order never touches the purchase order | Finalise a GRN against the purchase order |
| Stock Availability shows open delivery-order units for a supplier | Someone finalised a supplier-raised delivery order | Void it in Delivery Order (Internal) if nothing has knocked it off |
| No FINAL, VOID, print or e-mail | Their buttons are switched off in this applet | Use Delivery Order (Internal) |
Related documentation
- Purchase Workflow applets — the supplier-access family this applet belongs to.
- Delivery Order Applet (Internal) — full lifecycle of the same document.
- Purchase Order Supplier Access — the same kind of part delivery, seen from the order.
- Supplier Applet — supplier ↔ login links.