Documents, statuses and the document flow

Why a purchase order goes draft → approved → received, and what each step locks.

Baca dalam Bahasa Indonesia

On this page
  1. What a status does
  2. The main life cycles in Voltrus
  3. The document flow
  4. Corrections: never edit, always counter
  5. Dates matter as much as statuses
  6. Checklist

In a spreadsheet, a purchase order is a row, and its "status" is whatever someone typed in the last column. In an ERP, a purchase order is a document with a life cycle: it starts as a draft, gets approved, receives goods and is finally closed. Each status allows certain actions and forbids others. This is the single biggest habit change for people coming from Excel, and once it clicks, the rest of the system makes sense.

What a status does

A status is not a label. It is a rule about what may happen next.

  • It decides what can be edited. A draft can be changed freely. An approved PO has been promised to a supplier, so its lines are frozen. In Voltrus, lines can only change while a document is in its first status.
  • It decides the next steps. An approved PO can be received or cancelled. A received PO can be returned to the supplier or closed. Nothing else.
  • It decides what posts. Moving to some statuses moves stock or posts journals. Approving a PO posts nothing; receiving it puts stock in the warehouse and posts inventory against GRNI (goods received, not invoiced).
  • It tells everyone where things stand. "Confirmed sales orders not yet shipped" is a list, not a meeting.

The main life cycles in Voltrus

These are the statuses as Voltrus stores them.

DocumentStatusesWhere
Purchase orderdraft → approved → received → closed (or cancelled)Purchase orders
Supplier quotationdraft → received → converted (or rejected, expired)Supplier quotations
Sales quotationdraft → sent → accepted → converted (or rejected, expired)Sales quotations
Sales orderdraft → confirmed → shipped → closed (or cancelled)Sales orders
Invoice (customer or supplier)draft → issued → partially_paid → paid (or void)Invoices
Work orderdraft → released → in_progress → done (or cancelled)Work orders
Stock transferdraft → done (or cancelled)Stock transfers
Stock countdraft → posted (or cancelled)Stock counts
Subcontract orderdraft → sent → received → closed (or cancelled)Subcontract orders
Fixed assetdraft → in_service ⇄ under_maintenance → disposedAssets

Some steps can happen in parts. A PO stays approved while goods arrive in several receipts and becomes received only when every line is fully in. A sales order stays confirmed through several partial shipments, each of which creates its own delivery order (surat jalan), and becomes shipped when every line is shipped or short-closed.

The document flow

Documents do not live alone. Each one is created from the previous one and keeps a link to it. SAP calls this the document flow; it is how you answer "what happened to this order?" in one click.

Sales quotation ──convert──▶ Sales order ──ship──▶ Delivery order(s)
                                   │
                                   ├──create down payment──▶ Down-payment invoice
                                   ├──create invoice──▶ Invoice ──▶ Payment(s)
                                   └──return──▶ Customer return ──▶ Credit note

Supplier quotation ──convert──▶ Purchase order ──receive──▶ Stock movements
                                   └──create bill──▶ Supplier bill ──▶ Payment(s)

Following the flow forward or backward is how you investigate anything: a customer disputes an invoice, you open it, go back to the delivery order with the driver's signature, back to the sales order with the agreed price, back to the quotation.

Corrections: never edit, always counter

Once a document has had an effect (stock moved, a journal posted, a promise made to a third party), you do not edit it. You create a document that counters it. This keeps the history complete and the ledgers in balance.

MistakeWrong fixRight fix in Voltrus
Received the wrong quantityEdit the receiptReturn to supplier from the PO (with a reason), then receive correctly
Invoice amount wrong after issueChange the amountIssue a credit note, then a new invoice
Manual journal posted to the wrong accountEdit the journalReverse it (admin), then post a correct one
Customer sent goods backEdit the delivery or the invoiceRecord a customer return from the sales order: stock comes back, a credit note is drafted for what was invoiced
Customer paid the wrong invoiceDelete the paymentPost a reversing payment; payments are never edited
Order no longer wantedDelete the orderCancel it (allowed before the first shipment or receipt)

Voltrus enforces these rules. Document numbers are fixed once created. Delivery orders can only be created by shipping a sales order. Journals and accounting periods cannot be written directly. A document can only be deleted while it is in its first status or a final one (cancelled, void, rejected and so on).

Dates matter as much as statuses

Every document that posts carries a date, and that date decides the accounting period. Post the receipt on the day the goods arrive, the invoice on the day it is issued. Voltrus decides the calendar day of a posting in the company's timezone (set in Settings → General), so a receipt at 23:30 in Jakarta lands on the right day. Once finance closes a month, nothing can post into it.

Checklist

  • Learn the statuses of the three documents your team touches most.
  • Agree when each step happens in real life (for example: receive on unloading, not at the end of the day).
  • Use cancel, return and credit note for corrections; never ask for an edit to a posted document.
  • When something looks wrong, follow the linked records back to the source before changing anything.

Run it in Voltrus ERP

Everything in these guides is built in: documents that post to the ledger as they happen, Indonesian tax, MRP and costing, with AI agents that propose and people who approve.

See Voltrus ERP