CEISA Documents Required for Company Systems
Companies involved in import-export activities, bonded zones, and customs operations must understand the various CEISA documents used in Indonesian customs processes. Learn about essential documents such as BC 2.3, BC 2.5, BC 2.7, BC 4.0, and why your company system must be capable of processing them automatically.
With the increasing digitalization of customs in Indonesia, companies are no longer solely focused on internal operational activities like inventory management, purchasing, production planning, warehouse operations, or accounting. For businesses dealing with customs activities, there's a crucial additional layer: digital customs administration through the CEISA Bea Cukai system. The challenge is that many companies still don't realize that customs systems do more than just send data to the government. There are various document types with different data structures, workflows, field validations, and submission requirements. All these documents must be processed accurately. When a company's internal system cannot handle customs document formats effectively, the risk of compliance issues increases. This is why modern companies need to understand all the CEISA documents that their enterprise systems must support.
Why is Understanding CEISA Documents Crucial?
Each customs transaction involves a different type of document. Documents for goods entry differ from those for goods exit. Bonded zone documents are distinct from normal export documents. Each document type has a different payload structure when processed through a digital customs system. Without a system capable of automated document processing, companies will face complex manual workflows. If you are new to the basics of Indonesia's digital customs system, first learn what CEISA Bea Cukai is to fully grasp the foundation of this platform.
Challenges without a system supporting CEISA documents:
Excessive manual input process
Frequent incorrect submission formats
Customs field data errors
Delays in document approval
Difficult compliance monitoring
Increased human error during high transaction volumes
Types of Documents Processed in the CEISA System
In Indonesian customs operations, companies can process many different document types depending on their business activities. Manufacturing companies, bonded zones, importers, exporters, distributors, and logistics providers typically use a combination of several documents simultaneously. The more complex a company's supply chain, the more documents need to be processed.
BC 2.3
BC 2.5
BC 2.7
BC 4.0
BC 4.1
PEB
PIB
Manifest
BC 2.3 Document
BC 2.3 is a customs document used for the entry of goods into a bonded zone. Companies with bonded zone facilities must process this document when receiving specific goods according to customs regulations. Each transaction must contain detailed data about the goods, quantity, supplier, transaction value, and other supporting data. Errors in the data structure can lead to submission rejection.
BC 2.3 typically includes:
Supplier data
Item details
Goods quantity
HS Code
Invoice value
Shipping information
Customs declaration data
BC 2.5 Document
BC 2.5 is used for the entry of goods with specific facilities according to Indonesian customs regulations. Certain companies that receive special facilities will utilize this document as part of their customs compliance process. The data processed must adhere to the customs system's validation standards. Field mapping discrepancies can cause rejection during submission.
Supplier Information
Item Classification
Tax Data
Shipping Detail
Product Quantity
Document Validation
BC 2.7 Document
BC 2.7 is one of the commonly used documents for the exit of goods from a bonded zone. This document is typically related to the distribution of goods to customers or specific destinations as per customs regulations. Data must be processed accurately as it directly relates to the company's inventory movement. When companies still use manual processes, the risk of data mismatch is quite high. This is why many companies are building CEISA integration with ERP to ensure inventory data is synchronized automatically.
BC 4.0 Document
BC 4.0 is used for the entry of local goods into a bonded zone. This document is commonly used by manufacturing companies that receive materials or goods from local suppliers into specific facilities. Each transaction requires accurate data validation. Companies with high transaction volumes typically need an automation engine so that submission processes are not done manually one by one.
Common fields in BC 4.0:
Vendor data
Invoice number
Item information
Quantity data
Transaction amount
Tax declaration
Delivery information
BC 4.1 Document
BC 4.1 is generally used in specific scenarios related to the movement of goods according to applicable customs regulations. Although not all companies process this document daily, internal systems must be ready to support the required data format when transactions occur. Enterprise companies usually prepare a flexible architecture so that all customs documents can be processed without major system changes in the future.
PEB (Pemberitahuan Ekspor Barang - Export Declaration)
PEB is the primary document in the process of exporting goods from Indonesia. Exporter companies must ensure that export data complies with customs regulations. Invoice data, shipping details, buyer information, goods quantity, and various additional information must be sent accurately. Small errors can delay the export process.
Exporter Information
Buyer Information
Invoice Data
Shipping Detail
Export Value
Container Information
PIB (Pemberitahuan Impor Barang - Import Declaration)
PIB is used for import activities. Importer companies must process import data through the customs workflow according to regulations. The higher a company's import transaction volume, the greater the need for system automation to ensure the entire workflow runs efficiently. Manual submissions often create operational bottlenecks.
Why is a Manual System a Major Risk?
Some companies still operate customs workflows semi-manually. Operators extract data from the ERP, transfer it to customs documents, and then submit them one by one. This approach may be feasible for small transaction volumes. However, for enterprises with hundreds of daily transactions, a manual model will lead to significant problems.
Risks of manual processes:
Duplicate input process
High human error rate
Delayed customs documents
Errors in quantity data
Field mapping errors
Increased compliance risk
Difficult transaction monitoring
Why is Middleware an Important Component?
The more customs documents a company needs to process, the more crucial it is to build a stable automation layer. Middleware allows internal systems to extract transaction data from the ERP, perform field mapping, transform payloads, validate data, and then automatically send documents to the customs system. In an enterprise environment, CEISA middleware becomes a vital foundation for maintaining the reliability of customs submissions.
Document Automation
Payload Transformation
Queue Processing
Retry Mechanism
Response Validation
Error Monitoring
Audit Logging
API Communication
How Do Enterprises Automate All Documents?
Modern companies no longer process each customs document manually. Most enterprises build automation architectures that allow all documents to be processed automatically based on business transactions occurring in the ERP. Every purchase order, receiving transaction, shipment process, or inventory movement triggers an automated customs workflow. Solutions like CEISA Middleware Integration enable this entire process to run without duplicate work and without repetitive manual input.
Automation Flow:
ERP Transaction
↓
Data Extraction
↓
Document Identification
↓
Field Mapping Engine
↓
XML / JSON Transformation
↓
CEISA API Submission
↓
Response Validation
↓
Dashboard Monitoring
FAQ About CEISA Documents
What is BC 2.3?
A document for the entry of goods into a bonded zone.
What is the function of BC 2.7?
A document for the exit of goods from a bonded zone.
Why must company systems support multiple documents?
Because each customs transaction has a different workflow and format.
How can all customs documents be automated?
Companies can use automation middleware to process submissions automatically.
Conclusion
Understanding various CEISA documents is a critical step for companies with customs activities in Indonesia. Each document type, such as BC 2.3, BC 2.5, BC 2.7, BC 4.0, PEB, and PIB, has a different workflow that must be processed accurately. The higher a company's transaction volume, the more difficult it is to maintain manual processes. Automation through ERP and middleware integration is the best approach to ensure all customs workflows run efficiently, securely, and scalably.
Automate All Your Company's CEISA Documents
Build enterprise customs automation to process all CEISA documents automatically through production-ready middleware integration.