Indonesia LLD Reporting: Foreign Exchange and Company Loans

Does a Company Loan Create an LLD Reporting Duty

Indonesia’s 2024 LLD framework defines LLD broadly as the movement of foreign financial assets and liabilities between residents and non-residents. It gives Bank Indonesia the basis to require residents to provide LLD data directly or through designated parties. That framing matters because a company’s question is wider than whether it has opened a foreign-currency bank account: it must identify financial relationships with non-residents and then test the applicable operational reporting rules. Bank Indonesia Regulation 9 of 2024 is the current general framework for that analysis.

For company borrowing, the detailed LLD regime is commonly encountered through ULN (external debt) reporting. The 2019 reporting regulation and its implementation rule include non-bank companies among reporting parties that conduct LLD in the form of ULN or certain related-party transactions. ULN is defined in the implementation rule as a resident’s debt to a non-resident in foreign currency and/or rupiah, including sharia financing. Currency does not decide the issue by itself; the resident–non-resident debt relationship is the starting fact.

The scope boundary is equally important. Bank Indonesia’s DHE/DPI rules govern export proceeds and foreign-exchange import payments, whereas a shareholder loan, overseas lender facility or intercompany payable presents an LLD/ULN analysis. A single transaction may appear in multiple internal reconciliations, but the company should not merge these regimes into one filing checklist. The official DHE and DPI regulation provides the separate export-and-import payment context.

Use this first screen before assigning a reporting owner.

This article focuses on company loans and similar debt events. It is a filing-control guide, not an opinion that every cross-border balance is reportable. Before the company relies on a conclusion, confirm the latest Bank Indonesia instructions, portal treatment and any amendments with the person responsible for the submission.

Map the Loan Event to the Correct Report

The detailed implementation rule divides the operational picture into core ULN/related-party data, a recapitulation report, and new-ULN planning information. Core data records the instrument; the recapitulation tracks planned and actual drawdowns and payments, the position and its changes. The rule lists loan agreements, debt securities, trade credit and other ULN among the relevant instruments. The discipline is to map each event once, then let the responsible team populate the connected report rather than recreating the story from email at month end.

The first core-data report is tied to the month after the loan agreement is signed, the debt security is issued or the obligation is recognised. That means a signed facility with no initial drawdown can already belong on the reporting calendar. The implementation rule is published as PADG 21/4/2019 ; use the current implementation instructions when configuring the actual submission fields.

Treat signing, recognition, drawdown, repayment and plan change as separate reportable-data events—not as one annual financing event. The distinction prevents a legal team from filing away an executed agreement while finance waits for bank movement data that does not yet exist.

The event-to-report matrix is the article’s decision tool; maintain it per instrument, not only per lender.

Where the Indonesian borrower is newly established or its financing is still being documented, link the event record to the entity file from day one. A review of Indonesia incorporation requirements can help align the legal-entity, tax and OSS records that must match the finance workflow; it does not determine LLD coverage on its own.

Build the Monthly Foreign Exchange Ledger

A defensible monthly file starts with the signed instrument, not the general ledger alone. Capture lender and borrower identity, relationship, instrument type, currency, original amount, maturity, pricing, security, drawdown schedule and payment terms. Then reconcile those contract facts to the accounting balances and bank evidence. A mismatch may be legitimate—for example, accrued interest or a foreign-exchange remeasurement—but it should be explained before the reporting data is prepared.

The recapitulation is most useful when it has both a forward-looking and an actual column. Planned drawdowns and payments answer whether the financing plan is still current; actual movements and the month-end position answer what happened. Do not let an accounting close substitute for a loan reconciliation: the reported data needs the agreement-level explanation for each balance movement.

Monthly close pack

• Instrument register with agreement number, counterparty, currency, status and first-report date.
• Opening balance, current-month drawdowns, principal repayments, interest payments, fees and closing balance by instrument.
• A planned-versus-actual schedule that explains timing changes and undrawn amounts.
• Bank records, payment instructions, accounting journals and current amendment documents linked to each material movement.
• A sign-off log showing who prepared, reviewed and submitted the LLD data, plus any post-filing correction.

The record should also identify what did not happen. If no drawdown occurred, record the zero movement against the facility rather than leaving the instrument silent. PADG 21/4/2019 contains limited planning-report situations where a nil report can be relevant; confirm the exact current condition and channel before relying on a nil outcome.

Treat Amendments and Intercompany Changes as Reporting Events

Loan amendments create reporting risk because they often change several fields at once: lender identity after an assignment, ceiling, currency, maturity, repayment profile, interest, guarantees or purpose. The business may call the change a housekeeping exercise, while the reporting record sees a different financial obligation or a changed forecast. Make legal’s amendment notice an automatic trigger for the LLD owner to assess both the core data and the next recapitulation.

Intercompany balances deserve the same discipline. A payable may begin as trade credit, be extended repeatedly, attract interest or be converted into a shareholder loan. Each step can alter how the company describes the instrument and its planned payment data. The safest control is to record the legal and economic change on the day it is approved, rather than trying to infer it from a later balance sheet.

Use a short event review before the monthly reporting file is locked.

This change log should feed the same monthly ledger used for reporting. It is more reliable than asking each department at close whether anything material happened, because it creates a named handoff from the transaction owner to the person who prepares the Bank Indonesia data.

Use the Deadline Calendar and Correction Window

Under the detailed implementation rule, a monthly LLD report is due no later than the 15th day of the following month. The first core-data and recapitulation submissions follow the month in which an agreement is signed, an instrument is issued or a debt is recognised. If a deadline falls on a weekend or Bank Indonesia holiday, the rule moves it to the next Bank Indonesia working day. Put those dates in the finance calendar before any financing agreement is executed.

New-ULN plan information has its own timetable: the published rule uses 15 March for a new external-debt plan and 15 June for a plan change. The same implementation rule sets a correction deadline of the 20th day of the relevant reporting month. These are operational dates, so the filing owner should verify the live portal guidance and current amendments rather than relying on a historic spreadsheet.

Deadline calendar for the reporting team; use it as a control calendar, not a substitute for current BI instructions.

The escalation threshold should be earlier than the external deadline. For example, require legal to send new or amended financing documents within two business days, treasury to certify actual flows by close plus five, and the filing owner to resolve exceptions before the internal submission cutoff. That sequence leaves time to test the data rather than merely transmit it.

Decide When to Escalate the Filing

Escalate the filing when the agreement and ledger describe different instruments, a balance moved without treasury evidence, the counterparty changed, a planned drawdown is materially delayed, the company is unsure whether an obligation is debt or trade credit, or a previous submission needs correction. These are classification and evidence questions, not routine formatting issues.

Bank Indonesia’s general framework allows administrative sanctions for reporting failures, including written warnings, payment obligations and other measures under the applicable rules. The practical response is not to guess at the consequence after a missed date; it is to document the exception, obtain the current filing instruction and correct the record without delay. The 2019 LLD reporting regulation is a useful reference point for the detailed regime, but the live instruction should govern the actual submission.

When the monthly workbook supports later tax or finance review, preserve its connection to the underlying evidence. Our guide to corporate tax audit records in Indonesia explains why traceable records matter across finance controls. The decision rule is straightforward: if the business event cannot be reconstructed from the agreement, ledger and payment evidence, pause the filing path and resolve the gap with the responsible advisers.