BATAM FILING & HANDOVER
Batam Business Registration Services: Local Filing Support and Document Handover
Set a clear local mandate and accept each filing against records your company can verify and use.
Batam business registration services should leave the Indonesian company with verifiable filing results and usable control of its records. Local submission support and a completed government approval are different deliverables. Before accepting the engagement, match every agreed filing to its official status, test company access and record any outstanding correction or permission with a named owner. A document folder alone is insufficient when the company cannot retrieve its own records or continue an unfinished application.
Key takeaways
- Choose a representative for defined filings and local coordination; keep corporate decisions and official approval responsibilities explicit.
- Retain the submission reference and the current official result separately, so a pending application is never described as an issued permission.
- A Batam address does not establish which local or national channel applies; map the actual activity, premises and requested approval.
- Close accepted deliverables individually and assign unresolved work, account recovery and document custody before the representative exits.
Define the Batam filing mandate before appointing support
Start with a written mandate that names the Indonesian entity, its proposed activities, the Batam project location and the exact filing outputs. For a foreign investment company (PT PMA), the decision maker should already know which ownership and activity route is being pursued. A local filing representative can coordinate information and follow up applications; a convenient Batam contact cannot settle an unresolved legal structure or change the approved business purpose.
The underlying corporate record is the foundation for later local applications. Compare the approved company name, registered address, shareholders, management and business scope with the company registration requirements in Indonesia before those details are copied into Batam project forms. Keep the source document behind each field, rather than circulating several competing versions of a spreadsheet.
Agree who prepares, checks, signs, submits and receives each output. Identify the notary, the company representative and any local technical adviser separately. Define whether support covers only submission, responses to corrections, retrieval of an issued document or follow-up through a specified status. The service contract should identify the evidence that closes each deliverable. This is a recommended acceptance control, not a government filing rule.
- List included applications and excluded project work, such as land, environmental, building, goods-traffic or sector matters.
- Set the company approval needed before data changes, further submissions or payments to third parties.
- Specify where records are stored, who receives originals and how open matters continue if the engagement ends.
Clarify the Batam filing mandate
Identify the proposed entity, activity, site and intended outputs before local submissions are authorized.
Match each filing to its owner and local channel
Separate national corporate work from business licensing and Batam-specific services. AHU’s limited-company service requirements identify the notary and the Sistem Administrasi Badan Hukum (SABH) as the corporate application route, with an establishment deed and a Ministry decision output. Ask the local coordinator for those corporate outputs; do not request the notary’s professional account credentials as part of company account handover.
For business licensing, Government Regulation 28 of 2025 is the current risk-based framework and replaces Government Regulation 5 of 2021. Company establishment and the permissions for its actual activity have separate completion evidence. Record the Business Identification Number (NIB) and each applicable Standard Certificate, Business Licence or supporting approval separately, including whether a required verification remains outstanding.
Batam work may involve Online Single Submission (OSS), BP Batam and a service-specific local channel. BP Batam’s September 2026 licensing report confirms that OSS, LMS and Indonesia Batam Online Single Submission (IBOSS) remain parts of its service ecosystem. It also distinguishes issued or handled applications from incomplete, returned-for-correction and verification cases. The practical implication is to name the relevant channel and current state for each application; one portal screenshot cannot establish that all local work is complete.
For each proposed local filing, record the activity description and KBLI business classification, project site, requesting entity, filing channel, responsible applicant and expected output. If the representative proposes a change of site or activity, obtain a revised route before submission. Local support is coordination, not delegated approval authority. The government issuer determines the result, while the company must approve the information submitted in its name.
The official materials linked here were checked on October 20, 2026; refresh the applicable requirements and live results before submission and handover. The two tracks meet at handover: the company needs both credible official status evidence and practical control of the files used to obtain it.
Use an acceptance register for files, access and open work
Use the register below as an acceptance worksheet for your engagement. It is an editorial control tool derived from the different official roles and application states, not a prescribed Indonesian government form. Add a dated evidence location and a named company reviewer to every row. Mark an item accepted only after the reviewer has performed the stated check.
| Workstream | Representative transfers | Company verifies | Keep open when |
|---|---|---|---|
| Corporate identity | Deed copy, Ministry approval and any subsequent amendments included in scope | Match entity name, deed number, dates and management to the approved source records | An unexplained mismatch or an unavailable corporate output |
| OSS activity and project | NIB, relevant licence outputs, submitted data and current application references | Match activity and location; distinguish issuance from outstanding requirements or verification | A required permission remains pending, returned or unverified |
| Batam local application | Service name, channel, reference, receipt, response history and final output if issued | Match the site and applicant; read conditions attached to the specific result | Local submission evidence exists but no supported closure status |
| Files and custody | Searchable electronic index plus an itemized receipt for physical documents delivered | Open files; identify originals, copies and the current custodian of retained records | Missing items or unrecorded custody prevent later use |
| Control and open work | Company access test, recovery route, mandate record and exception list | Confirm the company can retrieve results and assign the next authorized action | Only the departing representative can act or recover access |
Use the hold-open condition to make partial completion visible. A returned application can be a valid submission-stage deliverable if that was the agreed scope, but it is not an issued approval. Record what the contract promised and what the evidence proves in separate fields. That distinction allows an honest partial handover without losing the next action.
Do not insist that every physical document must leave its lawful custodian. Specify which executed copies or certified copies the company receives, which records remain with a notary or other holder and how the company requests a usable copy later. An itemized custody record is more useful than an unexplained assertion that “all originals” have been delivered.
Resolve gaps in the acceptance register
Bring the file inventory and open application references to a review of what the company can already verify and use.
Run the handover with your company representative
Conduct the handover with a company director or another properly authorized company representative , rather than letting the departing filer certify their own work. Use a scheduled session in which the recipient checks the evidence index against the live records that are available to the company. Keep confidential identity material in an access-controlled repository; do not distribute passwords through the general document index.
- Reconcile the record set. Open the deed and approval files, compare the approved source data, and identify any amendment that supersedes an earlier version. Record missing pages or unreadable scans before signing the receipt.
- Test company access. Have the authorized recipient use the company’s own access and recovery arrangements, view the correct entity and project, and retrieve an available official output. Record that the test succeeded without retaining a password or one-time code in the sign-off document.
- Review every open application. Capture its reference, current state, latest official request, response owner and any stated deadline. Confirm who receives future notices after the local representative stops monitoring the case.
- Settle continuing authority. Inventory powers of attorney and other authorizations, identify the institutions or systems they cover and agree what must continue, be replaced or end. Obtain advice on the required steps for the particular instrument rather than treating a password change as revocation.
- Sign the delivery record. Identify the delivered items, evidence locations, company recipient, date and exceptions. Keep acceptance of received files distinct from approval to start the business activity.
The official OSS portal publishes a guide for changing account email data . Use the procedure applicable to the company’s account when the recovery address needs correction. The more detailed controls for transferring control of the OSS account complement the Batam filing register, especially where an outside representative created or maintained access. A successful login is a control test, not evidence of licence approval.
Recover an incomplete or disputed handover
Recover a handover by identifying the missing control before changing records. If a file is absent, request the exact document number, issuer, date and custodian, then obtain an accessible copy through the appropriate holder or system. Preserve the previous delivery inventory and correspondence. Avoid recreating a certificate or editing an official PDF to make the folder appear complete.
When an application has been returned
Obtain the official correction request and the exact submitted version. Compare the rejected field with its source: a company-record error belongs with the relevant corporate correction process, while a project-data error needs the appropriate application correction. Assign the response to an authorized person and keep the replacement version with its new receipt. Do not overwrite the history or submit a duplicate application simply to obtain a cleaner status screenshot.
When the representative controls the recovery route
Preserve the entity and application references, establish who is authorized to manage the company account and follow the platform’s applicable recovery or email-change process. Keep necessary pending work assigned while access is corrected. Never solve the problem by asking for a notary’s unrelated professional login, reusing another client’s account or continuing to share the former representative’s personal authentication channel.
If documents, money or authority are disputed, separate items already received from disputed items and document the company’s instructions. Escalate legal questions about a mandate or entitlement to records to qualified counsel. Leave the affected deliverable open until its evidence or lawful access route is established; a commercial dispute should not disappear from the compliance handover log.
Accept the Batam engagement against recorded exceptions
Accept the Batam engagement when the company can identify what was filed, verify the status of each promised output and continue using the delivered records without undocumented dependence on the departing representative. Approve closure item by item. A signed exception schedule may carry pending applications forward if it names the next owner, notice recipient and outstanding action.
Pause closure where the entity or project data do not match, access cannot be recovered or a required approval is being presented as complete without supporting evidence. Resolve the controlling gap first. Service acceptance does not authorize operations. The company’s operating decision must still follow the conditions of its actual activity, site and permissions, even after the filing-support contract has ended.
Prepare a documented engagement closure
Settle the accepted deliverables, continuing authority and named ownership of every unresolved Batam filing.
Frequently asked questions
Does hiring a Batam representative require transferring the company’s decisions?
No. Specify the representative’s permitted actions and which decisions require company approval. Filing coordination should follow a documented mandate; legal questions about who can bind the company need review of the actual authority documents.
Should the service promise a fixed government completion date?
A proposal should distinguish its own preparation and response commitments from an authority’s processing or verification. Ask which event starts each commitment and what happens when an official correction request or missing company input interrupts the work.
Can the company accept digital delivery instead of a physical folder?
Digital delivery can be useful when the recipient can open and retrieve the required records. Agree separately which physical executed copies are to be delivered and how retained documents can be obtained from their proper custodian.
Does a registration handover include bank or tax account approval?
Only include a separate workstream if it was expressly scoped, with its own evidence and responsible person. The bank and tax administration have their own requirements; a corporate filing receipt does not prove those processes are complete.
