A company address mismatch should be investigated field by field before changing either record. Determine which address is different, the source of each entry, and whether the difference reflects a correction, relocation, or separate operational location.
An AHU OSS company address mismatch occurs when information displayed in Indonesia’s corporate administration system differs from information in the Online Single Submission (OSS) system. The difference may involve a registered company domicile, detailed office address, business-operator profile, or individual operating location.
The correct response is not necessarily to change both records. First, determine which address fields are being compared, what the company’s latest supporting documents establish, and whether the discrepancy reflects outdated information, a data-transfer issue, or a genuine change in business circumstances.
For PT PMA and PT PMDN companies operating in Bali, this investigation can help avoid unnecessary amendments and reduce uncertainty when reviewing business licensing records.
What an AHU and OSS Company Address Mismatch Means
AHU and OSS support different administrative functions. AHU concerns corporate legal-administration records, while OSS maintains information used in business licensing and associated business activities.
An apparent conflict may arise when one system displays the company’s registered office while another displays the address of a particular project or business operation.
For example, a company may maintain its corporate office in Denpasar but operate a business activity at premises in Badung. These addresses are not necessarily contradictory merely because the geographical locations differ.
The first diagnostic question is therefore: Are both systems describing the same legal or operational address field?
If the answer is no, the apparent mismatch may be explained by the different purposes of the records. If the fields should contain equivalent information, further investigation is appropriate.
Identify Which Address Is Different
Before reviewing correction options, obtain the latest available company information and identify the exact field that differs.
Registered Company Domicile vs Office Address
A company’s registered domicile is not necessarily interchangeable with every detailed address associated with its business.
The official AHU guidance for limited liability companies identifies changes to a company’s registered place of domicile as a distinct category of corporate amendment.
For diagnostic purposes, compare the company’s establishment deed, subsequent amendments, and most recent AHU information. Identify what the corporate documents actually record and whether an address change has already been formally processed.
Do not presume that a different street address automatically establishes a change of registered corporate domicile.
OSS Company Profile vs Business Location
OSS information should be reviewed at the correct administrative level.
The official OSS portal maintains guidance for changes to corporate business-operator data, establishing a relevant administrative category for reviewing entity information.
OSS separately publishes guidance for business-activity data changes, so a company-profile discrepancy should not automatically be treated as an operational project-address discrepancy.
When examining an OSS record, identify whether the address appears in the corporate profile, a particular KBLI activity, or an individual project location.
This distinction matters especially where one company manages several operational sites. Comparing a registered office against the address of a separate business project may produce a false impression of inconsistent records.
Common Causes of Address Differences
An address discrepancy can have several possible explanations. The following are diagnostic scenarios rather than confirmed findings about any particular company.
Outdated OSS information. The company may have completed an earlier corporate amendment without the corresponding information appearing in the expected OSS field.
Incorrect comparison. The reviewer may be comparing the registered company domicile with an actual business operating location.
Address formatting differences. One record may contain an abbreviated street name, different building description, or older administrative naming convention.
Incomplete corporate administration. The company may have changed premises without establishing whether its underlying corporate records also require modification.
Incorrect project information. The company profile may be accurate, but an operating location or project record may contain an outdated address.
The objective of the investigation is to identify which scenario best fits the documents, not to assume the cause from the screen display alone.
How to Investigate the Mismatch
A structured review should establish the correct reference information before any amendment is requested.
Check the Latest Corporate Documents and AHU Record
Begin by collecting the available company documents, including the establishment deed, relevant amendments, and latest AHU corporate information.
Compare the company name, legal identity, registered domicile, and address details where recorded.
Then establish a timeline. Did the company change its office location? Was a corporate amendment completed? Does the newer information appear in the latest corporate documents but not in the OSS interface?
The AHU FAQ also addresses situations where the latest company information has not appeared in OSS and describes contacting the investment administration authority for a manual data-retrieval attempt.
This is published administrative guidance, not confirmation that a particular manual retrieval procedure remains available in every case. Any current support route should be checked through the relevant official service.
Compare the Correct OSS Data Fields
Open the company’s existing OSS information and identify the exact record displaying the questioned address.
Record the relevant business-operator details and, where applicable, the KBLI or project information associated with that address.
Compare equivalent fields rather than unrelated ones. A corporate domicile should be compared with the corresponding legal-entity information, while an operational site should be compared with the actual registered business location.
Where multiple projects exist, review each affected project independently. Avoid changing an unrelated location simply to make the overall company records appear visually consistent.
Decide Whether Correction or Data Refresh Is Appropriate
Once the source of the discrepancy is understood, classify the required response.
If AHU is correct but OSS displays older equivalent company data, investigate the currently supported data-update or synchronization mechanism before proposing a new corporate amendment.
If the underlying AHU information is incorrect, ask the responsible notary or legal professional to identify the appropriate corporate-record procedure.
If the corporate profile is correct but an operational location is wrong, concentrate on the relevant OSS business-activity or address data.
The OSS portal also provides a Business Address Correction Guide, but the availability of that guide does not establish that every address mismatch qualifies for the same correction process.
The correct procedure depends on the record affected, the nature of the change, and the options currently available in the relevant administrative system.
AHU and OSS Address Mismatch Decision Matrix
Use this table to distinguish the most likely investigation paths.
| Observed discrepancy | First evidence to examine | Recommended investigation |
|---|---|---|
| AHU has a newer company address than OSS | Latest AHU profile and amendment documents | Check whether the corresponding OSS company data has been updated or retrieved |
| AHU and OSS show different cities | Registered domicile and specific OSS address field | Determine whether the OSS address belongs to a separate operating location |
| Street spelling differs but premises are identical | Original premises documents and address evidence | Identify whether the difference is only descriptive |
| OSS project location differs from the corporate office | Project record, KBLI activity, and actual site details | Verify whether the separate addresses are intentional and accurate |
| AHU information itself appears incorrect | Corporate deed and official company record | Request professional assessment of the underlying corporate-data correction route |
| Company relocated but records remain unchanged | Relocation history and existing registered data | Determine which legal-entity and operational records are genuinely affected |
This matrix is a practical classification tool. It does not establish a mandatory filing route or guarantee that a particular amendment will be accepted.
Example: Different Company and Business Addresses in Bali
Consider a hypothetical company incorporated as a PT PMA with its registered corporate office in Denpasar. The company operates a separate hospitality-related business activity in Badung.
During an administrative review, its owner notices that AHU displays Denpasar while an OSS business-location record displays Badung.
At first glance, the addresses appear inconsistent. However, the records may be describing different things.
The owner should examine the latest corporate documents to establish the registered domicile and office information. Next, the owner should identify the relevant OSS data field and determine whether Badung is recorded as an operational project location.
If the OSS location accurately describes the actual project while AHU accurately describes the corporate office, changing either address merely to make them match could create a new inconsistency.
Now consider a different scenario: the company has formally relocated its corporate office, the current AHU documents reflect the new address, but the corresponding company information in OSS remains unchanged.
That situation points toward reviewing the data-update or synchronization process rather than automatically repeating the corporate amendment.
Both examples illustrate why document context is more important than visual equality between two address fields.
Check Related Tax and Property Records
Although the immediate investigation concerns AHU and OSS, other company documents can help establish whether the underlying address is accurate.
DJP maintains a taxpayer data changes information page that can serve as an initial reference when a company reviews its tax registration address. The current legal basis and applicable procedure should be confirmed separately through the relevant official tax services rather than inferred solely from this guidance page.
A mismatch between AHU and OSS does not by itself prove that the taxpayer’s address is incorrect.
Review the tax record independently instead of treating one system as an automatic substitute for another.
Premises documents can also clarify the investigation. A lease agreement, property description, or other available occupancy document may help determine whether an address describes the registered office, a secondary office, or an operational business site.
Where the company operates from leased premises in Bali, compare the property description, contractual parties, intended use, and relevant dates with the records being investigated.
How to Confirm the Discrepancy Is Resolved
The investigation should end with documented conclusions rather than merely a statement that the company submitted a correction.
Prepare a simple reconciliation record containing:
- The original mismatch: Identify the systems, exact fields, and different values.
- The supporting evidence: Record the corporate documents, OSS entries, and premises information examined.
- The diagnosed cause: State whether the difference concerns incorrect data, outdated information, separate address functions, or a genuine unprocessed change.
- The required action: Identify whether clarification, synchronization support, corporate amendment review, or OSS correction review is appropriate.
- The responsible party: Assign follow-up to the relevant company representative, notary, or administrative adviser.
- The completion evidence: Retain updated records, official acknowledgments, or confirmation that the differing addresses are correctly used for distinct purposes.
Where a correction has been processed, obtain the latest available records and compare the same fields again.
If the addresses remain different because they describe separate legitimate business locations, the resolution should document that distinction rather than force artificial uniformity.
Do not assume that submitting information in one system automatically verifies the accuracy of another system.
Compare the inconsistent entries with the records discussed in the business address change guide. If the discrepancy forms part of a wider company amendment, use the AHU and OSS company update review to organize the related changes.
Conclusion
An AHU and OSS company address mismatch should be investigated before any correction is filed. The essential questions are whether the two records refer to the same address function, which underlying document establishes the correct information, and whether the discrepancy is caused by outdated data, administrative inconsistency, or an actual change in the company or its operations.
For business owners and investors in Bali, a careful comparison of corporate documents, AHU records, OSS company and project data, and relevant supporting information provides a stronger basis for selecting the next administrative step. The goal is accurate, consistent records—not simply making unrelated address fields display identical text.
Need Help Investigating an AHU and OSS Address Difference?
If your company’s AHU and OSS information appears inconsistent, Bali Legal ID offers business legal, company incorporation, licensing, and tax-related services that may be relevant to reviewing the issue.
Request a consultation to discuss your corporate documents, OSS records, and the address discrepancy you have identified. The appropriate review and service scope can then be determined before making unnecessary changes.
Read More: Business Setup Bali for PT PMA, PT PMDN & OSS RBA Registration
Discuss the scope and supporting records with Bali Legal ID through our business setup services before deciding the next step for your Bali business or transaction.
FAQ company address mismatch
Why does my company address in AHU differ from the address shown in OSS?
The systems may display different categories of address information, or one record may be outdated or incorrect. First identify whether each address refers to the registered company domicile, the corporate office, or an operational business location. Compare the relevant fields with the latest supporting documents before deciding whether correction is necessary.
Should I amend my company deed if OSS shows an older address?
Not automatically. If the latest corporate documents and AHU records are accurate, investigate whether the OSS information requires updating or administrative synchronization. A new corporate amendment should not be assumed necessary merely because equivalent OSS data appears outdated.
Can AHU and OSS show different addresses for the same company?
Yes, where the records legitimately describe different address functions, such as a registered corporate office and a separate operating project. The key question is whether the specific fields are accurate for their intended purposes.
Does correcting an OSS address automatically correct AHU?
Automatic correction across systems should not be assumed. Check the affected records independently and verify whether the relevant corporate or OSS information actually changed.
What evidence should I prepare when requesting help with an address mismatch?
Prepare the latest establishment deed and relevant amendments, available AHU corporate information, the company’s NIB and OSS data, the exact conflicting address fields, and supporting premises documents where relevant. Include a brief timeline of any actual relocation or previously completed amendment.
References & Sources
- AHU Frequently Asked Questions on Limited Liability Companies — portal.ahu.go.id
- OSS Guide to Corporate Business Operator Data Changes — oss.go.id
- OSS Guide to Business Activity Data Changes — oss.go.id
- OSS Business Address Correction Guide — oss.go.id
- Taxpayer Data Changes — pajak.go.id