The moment you buy from a supplier in China or sell to a customer in Singapore, your books have to cope with two currencies at once. The invoice is in USD, but your ledger, your tax returns and your financial statements are in Rupiah. In a spreadsheet this usually ends with somebody converting at "roughly 16,000" and the difference disappearing into a plug figure. An ERP handles it with three simple ideas: every document remembers the rate it was booked at, the difference when you pay is a realised gain or loss, and at month end you restate what is still open as an unrealised gain or loss.
Functional currency and document currency
Every company has one functional currency: the currency of the economy it mainly operates in, and the one its books are kept in (PSAK 221, formerly PSAK 10, the Indonesian equivalent of IAS 21). For an Indonesian company that is almost always the Rupiah, and Indonesian tax law requires books in Rupiah unless you hold a permit to keep them in USD.
A document currency is the currency a single invoice, bill or order is written in. A USD purchase order is still recorded in your IDR ledger; the system just converts it, and keeps the original USD amount alongside.
Which rate, on which day
Indonesia uses two kinds of rate, and they serve different purposes:
| Rate type | Source | Used for |
|---|---|---|
| Transaction rate | Your bank's rate, or Bank Indonesia's JISDOR | Booking receipts, shipments, invoices, payments and revaluation |
| Tax rate (kurs pajak) | The weekly Minister of Finance decree (KMK) | Converting DPP and PPN on a foreign-currency faktur pajak, and withholding |
The rule of thumb: the transaction rate drives the accounting, the tax rate drives the tax documents. They differ slightly, and both are correct for their own purpose.
Realised gains and losses
Say you buy materials for USD 10,000. The goods arrive on 3 March, when the rate is Rp16,000, and the supplier's bill is booked at the same rate. You pay on 2 April, when the rate is Rp16,300.
| Date | Event | USD | Rate | IDR |
|---|---|---|---|---|
| 3 Mar | Bill booked (AP) | 10,000 | 16,000 | 160,000,000 |
| 2 Apr | Paid from bank | 10,000 | 16,300 | 163,000,000 |
| Difference | 3,000,000 |
You owed USD 10,000 and paid USD 10,000, but it cost you Rp3,000,000 more than you booked. That is a realised exchange loss: realised because the transaction is finished and the money has moved.
2 Apr Accounts payable 160,000,000
FX gain/loss 3,000,000
Bank 163,000,000
Voltrus posts the payment at the payment's rate and, when it differs from the bill's booking rate, a second journal that moves the difference to FX gain/loss. The same applies to customer receipts, in the other direction.
Unrealised gains and losses: month-end revaluation
Now suppose the bill is still unpaid on 31 March, when the rate is Rp16,200. The liability on your balance sheet says Rp160,000,000, but if you paid today it would cost Rp162,000,000. PSAK 221 says monetary items in a foreign currency (receivables, payables, foreign-currency bank balances) are reported at the closing rate. So at month end you restate the open balance and book the Rp2,000,000 difference as an unrealised exchange loss.
31 Mar FX gain/loss 2,000,000
Accounts payable 2,000,000
The standard ERP practice, and the one Voltrus follows, is to reverse this entry on the first day of the next month. The bill then sits at its original rate again, so when it is finally paid the realised gain or loss is calculated against the original booking and nothing is counted twice. Over March and April together the total loss is exactly the Rp3,000,000 from the table above: Rp2,000,000 shown in March, and in April the reversal (+Rp2,000,000) and the realised loss on payment (−Rp3,000,000).
Non-monetary items are not revalued. Inventory bought in USD stays at its Rupiah cost from the receipt date, and so do fixed assets and prepayments.
Purchases in foreign currency, step by step
Foreign-currency purchasing has one subtlety: the receipt and the bill usually happen on different days, at different rates.
- Goods receipt. Inventory and GRNI (goods received not invoiced) are booked in IDR at the transaction rate of the receipt date. Inventory keeps this cost.
- Supplier bill. The bill clears GRNI at the receipt's rate. The bill itself is booked at the bill date's rate. If the supplier's price differs from the PO price, that part goes to purchase price variance; the part caused by the rate moving goes to FX gain/loss.
- Freight. Freight on the PO can be in its own currency (a USD shipment with Rupiah trucking). Each receipt accrues its share to GRNI; the forwarder's bill, linked to the PO as a freight bill, clears it, with a rate difference to FX gain/loss when it is billed in the freight's foreign currency.
- Payment. Settles AP, with any realised difference to FX gain/loss as shown above.
The value of the goods is therefore fixed on the day they arrive, which is what PSAK 221 requires for the purchase of a non-monetary asset.
What to watch for
- Missing rates. If nobody loads the rate for a day, a foreign-currency receipt is refused. Either switch on the nightly fetch or make loading rates part of somebody's morning routine.
- Currencies the fetch does not cover. The nightly JISDOR fetch is USD only. For EUR, SGD, CNY or JPY, enter the transaction rate yourself (the KMK tax rates do cover them).
- Approval limits are in Rupiah. If your company sets approval limits, a USD purchase order or payment is compared with them at its own rate, or the day's transaction rate.
- Open foreign invoices at go-live. When you import open invoices and bills at cut-over, give each foreign-currency one its original rate (
fx_rate), so the receivable or payable starts at the Rupiah amount your old books carried. - One FX account. Voltrus posts both realised and unrealised differences to the single FX gain/loss account (5-9100). If your auditor wants them split in the notes, the revaluation journals are easy to identify by their source, so you can separate the two when preparing the statements.
Checklist
- Decide your transaction rate source (your bank or JISDOR) and use it consistently.
- Load or fetch rates every working day you post foreign-currency documents.
- Set a default currency on each foreign customer and supplier.
- Revalue open foreign-currency balances at every month end, before closing the period.
- Keep USD and other foreign cash in a ledger bank account held in that currency, so it is revalued too.