Most of a company's working capital sits in two lists: what customers owe you (accounts receivable, AR, piutang usaha) and what you owe suppliers (accounts payable, AP, utang usaha). In a spreadsheet these are usually a sheet of unpaid invoices that somebody marks "LUNAS" when money arrives, and they rarely agree with the bank or with the accountant's ledger.
In an ERP both are sub-ledgers: the list of open invoices per customer or supplier is the detail, and a single control account in the general ledger (1-1100 Accounts Receivable, 2-1100 Accounts Payable) holds the total. Because invoices and payments post to both at the same time, the two always agree. When they do not, something was posted by hand where it should not have been.
The life of an invoice
Customer invoices and supplier bills share one document type in Voltrus, with a direction (receivable or payable) and these statuses:
| Status | Meaning | Posted to the ledger? |
|---|---|---|
| draft | Being prepared; amounts can change | No |
| issued | Sent to the customer, or accepted from the supplier | Yes: AR or AP |
| partially_paid | Some payments applied, a balance remains | Yes |
| paid | Fully settled | Yes |
| void | Cancelled before it had effect | Final |
Once an invoice is issued its amounts are locked. Only the notes, the due date and the tax (faktur) fields can change. A wrong issued invoice is corrected with a credit note, which reverses all or part of it, and both documents stay on the record. Goods a customer sends back are recorded as a customer return on the sales order; for anything already invoiced, it drafts the credit note for you.
At go-live, the invoices and bills still unpaid in your old system are loaded through Onboarding as open invoices and open bills. They arrive already issued, with no journal of their own; the opening balance books them to AR and AP once, and payments then settle them like any other invoice (see Migrating from Excel).
Invoices normally come from the flow, not from a blank form: Create invoice on a shipped sales order bills what was shipped and not yet invoiced, and Create supplier bill on a received purchase order bills what was received and not yet billed. See Invoicing and revenue recognition and Supplier invoices and the three-way match.
Payment terms and due dates
The payment terms on the customer or supplier (for example "Net 30") set the due date when the invoice is issued. Voltrus reads the first number in the terms text as the number of days, and uses 30 days when there is none. The due date drives everything that follows: aging, overdue alerts, credit control and the supplier payment run.
Aging: the report that matters
An aging report groups open invoices by how far past their due date they are. It is the first report a CFO, a bank or an auditor asks for.
| Customer | Current | 1–30 | 31–60 | 61–90 | 90+ | Total |
|---|---|---|---|---|---|---|
| PT Alpha | 40,000,000 | 12,000,000 | 52,000,000 | |||
| CV Beta | 8,500,000 | 8,500,000 | ||||
| PT Gamma | 5,000,000 | 22,000,000 | 27,000,000 | |||
| Total | 45,000,000 | 12,000,000 | 8,500,000 | 22,000,000 | 87,500,000 |
How to read it:
- Current is healthy. 1–30 is normal friction; a reminder usually fixes it.
- 31–60 needs a phone call and a reason. 61–90 needs a manager.
- 90+ is a credit risk. PT Gamma's Rp 22,000,000 should already have stopped new orders, and finance should consider whether an allowance for doubtful debts (cadangan kerugian piutang) is needed under PSAK 71.
The same report on the payables side tells you what you must pay and when, and shows any supplier you are paying late.
Credit control
Receivables are cheapest to manage before they exist. Voltrus checks credit when a sales order is confirmed:
- Exposure = open receivables + orders confirmed but not yet invoiced + this order.
- The order fails the check if the customer is on credit hold, has any overdue invoice, or would exceed its credit limit.
- When customers are paid for by a parent company (the bill-to customer), the payer's limit covers all of them.
What happens on failure is a company setting (off, warn, or send for approval; approval is the default). See Customers and credit control.
Down payments and advances
A customer down payment (uang muka) is invoiced before delivery and sits in 2-1400 Customer Advances, a liability, until later invoices on the same order deduct it. If the order is closed or cancelled, the unused part can be refunded with a credit note or moved to another open order of the same customer. The journals are in How operations post to the general ledger.
Payments and allocation
A payment always settles specific invoices. That is the main discipline an ERP adds over a spreadsheet: money is never just "received from PT Alpha", it is received against invoices INV-001 and INV-004, so every invoice's open amount is exact.
- A single payment row settles one invoice. When the invoice is fully covered it becomes paid; part payment leaves it partially_paid.
- One bank transfer that settles several invoices is a payment batch: pick the party, tick the invoices, adjust the amounts.
- Payments are never edited. A wrong payment is corrected with a reversing payment.
- If the company has set an approval limit for payments, money going out above it (a supplier payment, a refund, a batch or a whole payment run) needs an admin; anyone else sends it as a proposal. See Internal controls.
- PPh 23 that the customer withheld is recorded on the receipt; it reduces what the bank receives and becomes Prepaid PPh 23 (see PPh withholding).
Money on account
Sometimes money arrives and you cannot tell which invoices it pays: a round-sum transfer, an overpayment, a payment before the invoice is issued. Do not force it onto the wrong invoice. Hold it on account: it is posted to 2-1250 Unapplied Receipts against the customer, then applied to invoices once you know, unapplied if you got it wrong, or refunded.
| Step | Debit | Credit |
|---|---|---|
| Money received on account | Cash & Bank | Unapplied Receipts |
| Applied to an invoice | Unapplied Receipts | Accounts Receivable |
| Refunded to the customer | Unapplied Receipts | Cash & Bank |
Reconciling the sub-ledger to the ledger
At each month end, three numbers must agree:
- the total of open customer invoices (aging total),
- the balance of 1-1100 Accounts Receivable,
- what customers would confirm if you asked them.
The first two agree automatically in Voltrus as long as nobody posts manual journals to AR or AP. The third is the job of customer statements and, for auditors, balance confirmations: send key customers their list of open invoices and resolve differences early. Do the same on the supplier side: compare each major supplier's statement with your open bills.
In Voltrus
Checklist
- Set payment terms and credit limits on every active customer before go-live.
- Review the receivables aging every week; act on anything over 30 days.
- Record every receipt against invoices on the day the money arrives; use on-account only when you truly cannot tell.
- At month end, confirm the aging totals equal the AR and AP balances on the balance sheet.
- Send statements to your largest customers quarterly and resolve differences.