Many small companies record revenue when they write the invoice, and some only when the money arrives. Both are wrong under Indonesian accounting standards for any business that sells on credit. Revenue is recorded when you have earned it, and for goods that is usually when they are delivered. The invoice is the paperwork that asks for payment; it is not what makes the sale real.
Getting this right is what makes your monthly profit mean something. If revenue follows invoices, a month where the accountant was on leave looks like a bad month for sales.
Revenue recognition: PSAK 115 in plain words
PSAK 115 (formerly PSAK 72), Indonesia's version of IFRS 15, gives one model for every kind of sale, in five steps:
- Identify the contract. A confirmed sales order with agreed terms is a contract.
- Identify the performance obligations. What you promised to deliver: the goods, and sometimes separate services such as installation.
- Determine the transaction price. What you expect to receive, after discounts, excluding PPN (PPN is collected for the state, not your revenue).
- Allocate the price to each obligation if there is more than one.
- Recognise revenue when each obligation is satisfied, that is, when the customer obtains control of the goods. For a normal goods sale, that is delivery.
For a manufacturer or trader shipping goods on standard terms, steps 2 and 4 are simple and step 5 means: recognise revenue on delivery.
Delivered but not yet invoiced
If revenue is recognised at delivery but the invoice goes out later, something has to hold the amount in between. That is unbilled receivables (sometimes called accrued revenue): an asset meaning "earned, not yet billed".
Example: 100 units at Rp 50,000 shipped on 30 June, invoiced on 2 July, PPN 11%.
| Date | Debit | Credit | Amount |
|---|---|---|---|
| 30 June, ship | Unbilled receivables | Revenue | 5,000,000 |
| 30 June, ship | Cost of goods sold | Inventory | (at cost) |
| 2 July, invoice | Accounts receivable | Unbilled receivables | 5,000,000 |
| 2 July, invoice | Accounts receivable | Tax payable (PPN) | 550,000 |
June's profit and loss shows the sale and its cost in June, where they belong. The invoice in July changes only the balance sheet. At any month end, the unbilled receivables balance is exactly the value of goods shipped but not invoiced, which makes it a good control: it should be small and explainable line by line.
PPN is posted with the invoice, not at delivery. This follows the tax rule that output PPN is due when the faktur pajak is made, which for a delivery of goods should be no later than the end of the month of delivery.
Invoicing from shipments
The invoice should bill what was shipped, at the price agreed on the order. Voltrus creates invoices from the sales order:
- Create invoice bills everything shipped on the order that has not been invoiced yet, priced from the order. Repeat invoices are numbered
INV-<order>, then-2,-3. - An invoice can never bill more than has shipped.
- If the invoice price differs from the order price, the difference goes to revenue when the invoice is issued.
- Order charges (freight, packing) are added according to their billing mode: all on the next invoice, or pro rata. They post to other income; charges passed on at cost, outside the tax base, go to a reimbursable-costs account instead.
Invoice statuses
| Status | Meaning |
|---|---|
| Draft | Prepared, not yet sent. Editable. Posts nothing. |
| Issued | Sent to the customer. Posts the receivable and PPN, and fixes the issue and due dates. |
| Partially paid | Some payment applied. |
| Paid | Fully settled. |
| Void | Cancelled. Final. |
Once issued, an invoice's amounts cannot be edited. Only notes, the due date and the faktur pajak fields can still change. A wrong invoice is corrected with a credit note that reverses all or part of it; both stay on the record.
Down payments
For custom or large orders, ask for a down payment (uang muka) before you start. In accounting terms a down payment is not revenue: you have not delivered anything. It is a liability, customer advances, until goods ship.
Example: a Rp 100,000,000 order with a 30% down payment, PPN 11%.
| Step | Debit | Credit | Amount |
|---|---|---|---|
| Issue down payment invoice | Accounts receivable | Customer advances | 30,000,000 |
| Accounts receivable | Tax payable (PPN) | 3,300,000 | |
| Customer pays | Bank | Accounts receivable | 33,300,000 |
| Final invoice deducts the advance | Customer advances | Accounts receivable | 30,000,000 |
PPN is due on the down payment when it is invoiced, which is why the down payment invoice carries it. The final invoice deducts the advance so the customer pays only the balance.
If the order is then closed or cancelled with part of the down payment unused, the remainder can be refunded with a credit note or moved to another open order of the same customer.
In Voltrus
Limits to plan around:
- Invoices are created from the sales order, covering everything shipped and not yet billed. There is no invoice from one specific delivery order in the console; if a customer insists on one invoice per surat jalan, invoice right after each shipment.
- Voltrus does not email invoices. Print or save the PDF and send it.
- Credit notes are invoices of kind credit note. Prefer them over voiding an issued invoice, so the reversal is explicit in the ledger.
- Goods coming back are recorded with Record return on the order: shipped-but-unbilled quantity is taken off unbilled receivables and revenue, and invoiced quantity gets a draft credit note to check and issue. See Sales orders, schedules and delivery.
For the faktur pajak side, see e-Faktur and the Coretax export.
Checklist
- Record shipments on the day goods leave; revenue depends on it.
- Invoice everything shipped before month end.
- Review the unbilled receivables balance at every close.
- Take a down payment on custom orders, and invoice it with PPN.
- Correct issued invoices with credit notes, never by editing.