TPS Online (Indonesian Customs): what it is, who must report and how it works

TPS Online is the electronic data exchange between a customs office and a temporary storage place (Tempat Penimbunan Sementara, TPS) for data on goods moved into and out of the TPS, plus related administration. Peraturan Direktur Jenderal Bea dan Cukai Nomor PER-10/BC/2020 defines it in Pasal 1, and Peraturan Menteri Keuangan Nomor 109/PMK.04/2020 sets the wider rules for customs areas and TPS.

The name confuses people because "TPS" also means a physical place. A TPS is a building, a yard or another place inside a customs area where goods wait temporarily for loading or release. A storage tank can be that place. This guide explains what TPS Online carries, who has to connect, what a fuel terminal reports, what to do when the link or the response fails, and how the data relates to the terminal's other systems. Regulation status is given as of 13 November 2026.

A TPS is a place where goods wait under customs supervision before they are loaded or released. TPS Online is the data line between that place and customs.

PER-10/BC/2020 describes the TPS Online system as an exchange of electronic data between the customs office and the TPS about goods entering and leaving, and about other administration. On the customs side it runs on the office's service computer system, called SKP TPS Online (Sistem Komputer Pelayanan). On the TPS side the operator needs its own electronic system for managing stored goods that can talk to it.

Three things travel through the line. The operator reports what has been stored and what has left. Customs sends the approvals that allow goods to enter or leave. Each exchange is answered by a response that says whether the data was received.

The duty falls on the TPS operator (pengusaha TPS), and it depends on the customs office that supervises the TPS.

Pasal 19 of PER-10/BC/2020 covers TPS operators under a customs office that has applied SKP TPS Online as mandatory. They must have an electronic system for managing the goods stored and an electronic data link to the customs office's system. The link must send and receive responses and data in real time and stay connected 24 hours a day, seven days a week.

The mandatory application is phased. Annex III lists customs offices and dates, and the timeline below summarises the TPS Online part. A terminal should read Annex III for its own office and ask the supervising customs office, instead of assuming that a date applies.

Customs designates a TPS, and for a tank the application has to carry measurement evidence.

Under Pasal 12 of PER-10/BC/2020, an operator asks the regional office or the main service office to designate a building, yard or other place as a TPS. The application states who is responsible, the business entity, the location, and the size or capacity (volume) and boundaries of the storage.

When the storage is a tank, the application also carries the tank's calibration (tera) result from the authorised agency. It adds a list of measuring instruments with their tera results, or a statement that adequate instruments will be provided.

Pasal 18 adds a link to the physical plant. For a tank TPS, the place for physical inspection is where the measuring instrument and the discharge line are installed, so that a sample can be taken. In plain terms, customs expects a tank TPS to have trustworthy measurement and a way to sample, and every TPS Online report rests on those readings.

How level readings become volume is the work of the tank management system. The INTEGRA TMS page shows how Citia handles it.

Most reporting trouble starts in master data, not in the interface.

The same tank appears under two names, so the report shows a location customs does not recognise. A product is renamed in the terminal system but not in the reporting application. A bill of lading number is typed in one format at receiving and another at delivery, and the balance stops matching. Each of these looks like a communication fault until someone compares the records.

• Keep one list of tanks, products and vessels, and let every system read from it.
• Validate document numbers when they are entered, not when they are sent.
• Freeze the data of a submitted report. Changes go through a correction with a new reference.
• Compare, every day, the items sent, the items answered and the items in the terminal records.

The daily comparison is cheap. It is also the fastest way to find a missing response before the reporting window closes.

A report starts in the physical world: a vessel discharges into a tank, or a truck loads from one. The data follows.

The movement is recorded in the terminal's own systems, such as the tank management system for receipts and the terminal automation system for loading. A TPS Online application prepares the report from those records, checks it against master data, sends it to the customs system and waits for the response. If something is wrong, the operator corrects it and submits again, keeping the link between the original and the correction.

Roles matter as much as software. Usually one person prepares a report, a supervisor reviews and releases it, and an administrator maintains master data. When one login can do all three, an error or a deliberate change is hard to trace afterwards.

Each step leaves evidence. The prepared data, the time of sending, the response and the status shown by the customs system are different records, and keeping them apart is what makes a later investigation possible.

INTEGRA TPS Integration, the Citia product for this task, follows the same order: Excel import of receiving data, validation, report preview, submission, status check and correction history. The interface version and the customs endpoint are agreed during implementation, because they depend on the site and the customs office.

Links fail, and the regulation expects it. The task is to keep the record straight while the link is down.

If the customs system is disrupted, Pasal 24 lets the operator submit the list of goods manually, and requires the same list to be sent again through TPS Online once the system works. Pasal 32 and 33 cover approvals: customs officers can record entry and release approvals manually, and the operator asks a customs officer to confirm an approval while TPS Online is down.

The automatic gate has its own fallback in Pasal 34. After confirmation from customs, the operator serves goods manually, records what actually happened when the gate is back, and sends that record through TPS Online.

Rehearse these fallbacks before they are needed. A short drill with the operators, using the manual forms and the confirmation request, shows who holds the contact details of the customs officer and where the manual records are kept.

A terminal application meets one more case that the regulation does not describe: the request leaves the terminal and no response comes back. The Citia article on TPS submission status and corrections explains why that is not the same as a failed submission.

TPS Online reports documents and goods movements to customs. It does not replace the systems that run loading or measure tanks.

The terminal automation system runs orders, gates and loading. A tank management system reads gauges and keeps physical stock. The TPS application sits beside them and reports to customs. Each has its own source of truth, and the numbers can differ for good reasons: a document balance changes when a delivery is booked, while a tank level changes when product physically moves.

A practical routine is a daily reconciliation with three columns: what the terminal systems recorded, what the TPS application sent, and what customs answered. Each difference gets a reason code, such as timing, correction or missing response. A difference without a reason is the one to investigate first, because it is either a data fault or a gap in the link.

The Citia article TAS, TMS and TPS compared sets out these boundaries, and what a terminal automation system is covers the loading side. The link to the business system is described in integrating TAS and TMS with SAP.

A terminal gets ready for TPS Online by fixing its data first and its software second.

Start with the obligation. Ask the supervising customs office whether SKP TPS Online is mandatory for your TPS and from when, and read Annex III of PER-10/BC/2020 for your office. Then look at the link. Pasal 19 asks for real-time exchange and a connection available 24 hours a day, seven days a week, so network design, power backup and monitoring belong in the project, not only the application.

Data quality decides the rest. Tank numbers, product names, bill of lading numbers and BC 1.1 references must match across the terminal's records and the report. A mismatch found at submission costs more than one found when master data is set up. Pasal 23 also asks the operator to keep records, including electronic data, for ten years, so the application needs history that can be exported.

Before go-live, test the unhappy paths. Run a normal submission and response, a response that arrives late, a rejected record, a deliberate duplicate attempt and a link loss in the middle of a batch of reports. Write the result of each into the acceptance record, the same way a loading bay is tested by unplugging the network during a batch.

The engineering is the same as in any TAS project. TAS architecture shows how the layers fit, and the Citia projects at the Jambi fuel terminal and Padalarang show the kind of terminal data, from shipment to filling and gate-out, that such reports draw on.