REGISTRATION AGENT KYC
Indonesia Registration Agent KYC Checklist for Founders
A decision-led briefing on agent identity, ownership, authority, professionals, payment account, data, credentials, deliverables, and exit, for foreign investors who need evidence they can verify before acting in Indonesia.
Founders should perform KYC on an Indonesia registration agent before engagement. Verify the legal entity, registration, address, directors, beneficial owners, bank beneficiary, invoice capacity, domain and contacts, actual notary and specialists, authority, subcontractors, conflicts, data handling, and past regulatory issues. The contract should limit access, define deliverables and liability, protect payments, and return credentials, originals, and data at termination. Before founders sign a deed, pay a provider, submit an application, or begin operations, the responsible team should reconcile the corporate facts, current official requirements, supporting evidence, approval owner, and unresolved conditions. The practical answer changes when the activity, sector, location, ownership chain, role, or transaction changes, so decisions should be recorded rather than passed along as provider assurances.
Key takeaways
- Founders should perform KYC on an Indonesia registration agent before engagement.
- Build the agent KYC from current official requirements and recipient-accepted evidence.
- Treat the agent KYC as incomplete until its corporate, regulatory, payment, and operating records agree.
- Keep official outputs, source data, payments, credentials, and unresolved conditions under company control.
Perform KYC on the registration agent before sharing documents or money
Founder KYC should begin with the agent's full legal name, registration number, address, directors, beneficial owners, bank account, tax invoice capacity, website and domain, named contact, professional role, notary or specialist relationships, and authority to handle filings. Compare the contract, invoice, bank beneficiary, email domain, WhatsApp identity, and official registry evidence. A logo, office photograph, social-media following, or copy of another client's certificate does not prove authority. For the agent KYC, the immediate acceptance point is to verify independently against the documented entity, owners, directors, address, and domain.
Risk-screen the agent for sanctions, adverse regulatory history, conflicts, unexplained changes of entity, personal payment requests, reused contact details, unrealistic approval promises, pressure to sign blank documents, and refusal to identify subcontractors. Limit the personal and corporate data supplied to the verified task, use secure transfer, watermark copies where appropriate, record recipients, and require deletion or return at termination. The company should control official email, phone, credentials, recovery methods, and originals from the start. Within the agent KYC file, the responsible officer should preserve role, professionals, systems, and limits as evidence for the decision to know who performs the work.
Agent KYC
| Control | Evidence | Decision |
|---|---|---|
| Identity | Entity, owners, directors, address, and domain | Verify independently |
| Authority | Role, professionals, systems, and limits | Know who performs the work |
| Exposure | Money, documents, credentials, and data | Apply least access |
Validate the evidence before the next commitment
Convert the open questions into a dated review file with named owners, accepted evidence, and a clear stop condition.
Verify provider authority, custody, and correction liability
Provider due diligence should establish identity, contracting entity, professional role, authority, payment account, and responsibility for every filing. An agent may coordinate work without being the notary, lawyer, tax adviser, immigration sponsor, or bank decision-maker. The engagement should identify each actual performer and the limits of their authority. For the agent KYC, the immediate acceptance point is to control deposits and disbursements against the documented entity bank account, invoice, tax, and receipt.
Before payment, verify official company and registration evidence and use a controlled contract. An independent document and payment check should support the provider review. Require no guaranteed approvals, no unexplained personal accounts, no withholding of company credentials, and no substitution of screenshots for downloadable official records. State how errors, rejected submissions, missed deadlines, and termination will be handled. Within the agent KYC file, the responsible officer should preserve originals, credentials, and official outputs as evidence for the decision to set handover and recovery rights.
Provider checks
Identity and role
Contracting entity and actual professionals
Verify authority and conflictsMoney
Entity bank account, invoice, tax, and receipt
Control deposits and disbursementsCustody
Originals, credentials, and official outputs
Set handover and recovery rightsProtect the registration deposit with scope and payment evidence
A company-registration deposit should pay an identified contracting entity for defined work under an invoice and contract. Before transfer, verify the provider's legal name, authority, bank account, tax treatment, notary or specialist roles, deliverables, third-party disbursements, cancellation rights, refund basis, correction duty, and custody of originals and credentials. A personal account, cash request, crypto transfer, urgency claim, or unexplained split payment needs escalation. For the agent KYC, the immediate acceptance point is to link money to evidence against the documented milestone, receipt, refund, and correction terms.
Tie the deposit to an initial acceptance package such as the signed engagement, approved fact sheet, ownership and KBLI review, document matrix, filing plan, and itemized disbursement budget. State which fees are earned on commencement and which remain refundable or held for later milestones. Never combine paid-up capital, government charges, address rent, bank opening funds, and professional fees into one undefined transfer. Reconcile every payment to an invoice, receipt, deliverable, and remaining balance. Within the agent KYC file, the responsible officer should preserve verified contracting entity and bank account as evidence for the decision to do not use unexplained recipients.
Resolve the decision gaps before filing
Reconcile the corporate, regulatory, payment, and operating facts before they become amendments or rejected submissions.
Define acceptance evidence for every deliverable
Every service promise should end in an acceptance document. Registration submitted is not equivalent to legal-entity approval; NIB issued is not equivalent to every license being verified; bank assistance is not equivalent to account approval; and visa preparation is not equivalent to immigration approval. The contract should use the correct endpoint. For the agent KYC, the immediate acceptance point is to check names, roles, shares, and capital against the documented approved deed and AHU legal-entity record.
Define acceptance against official outputs from AHU business-entity services , OSS, DGT, and any sector authority. Include downloaded files, QR or record checks, source data, issue dates, account ownership, payment receipts, originals, and an exceptions log. Where an authority makes the final decision, require complete submission evidence and a correction or escalation process instead of a guarantee. Within the agent KYC file, the responsible officer should preserve NIB and required verified output as evidence for the decision to read status and conditions.
Acceptance evidence
Corporate. Approved deed and AHU legal-entity record; check names, roles, shares, and capital.
Licensing. NIB and required verified output; read status and conditions.
Handover. Files, credentials, originals, and open-item log; test independent company control.
Take control of documents, credentials, and open obligations
A registration engagement is not complete until the company can operate without dependence on the provider's personal accounts or device. Handover should cover final documents, source data, credentials, registered email and phone details, authentication methods, originals, payment receipts, filing history, and unresolved obligations. Access should be tested by an authorized company officer. For the agent KYC, the immediate acceptance point is to transfer and test control against the documented OSS, tax, email, phone, and authentication.
Remote matters need an especially clear revocation and recovery plan. Reconcile the deed, AHU approval, tax record, NIB, licenses, shareholder register, beneficial-owner data, and bank application before acceptance. Record who holds each original, how each credential can be recovered, and when any power of attorney or temporary access must end. Within the agent KYC file, the responsible officer should preserve conditions, renewals, and corrections as evidence for the decision to assign owner and due date.
Handover register
| Control | Evidence | Decision |
|---|---|---|
| Documents | Final files, originals, and filing receipts | Inventory and verify |
| Access | OSS, tax, email, phone, and authentication | Transfer and test control |
| Open work | Conditions, renewals, and corrections | Assign owner and due date |
Verify the agent before sharing passports, corporate files, authority, credentials, or money
The approval decision for the agent KYC should name the selected route, responsible company officer, accepted source data, supporting documents, official outputs, payment limits, unresolved conditions, and the event that permits the next commitment. For agent identity, ownership, authority, professionals, payment account, data, credentials, deliverables, and exit, a conditional result should remain a visible gate rather than being absorbed into a broad statement that setup is complete.
The founders or board should sign a short agent KYC mandate that records the current facts, authority, required corrections, evidence location, system and credential owners, review date, and first transaction that the company intends to perform. Treat every important claim as an evidence question: who has authority, which rule applies, what official output is required, what status makes it usable, and who owns the next action. Recheck current official and institution-specific requirements immediately before filing, funding, signing, employing, or operating.
Put the approved route under company control
Record the decision, authority, documents, access, payment limits, and follow-up calendar in one owner-approved mandate.
Frequently asked questions
What is the fastest independent agent check?
Compare the contract, invoice, bank beneficiary, email domain, named people, company records, and claimed professional roles. Any unexplained mismatch should stop payment and document transfer.
Can a registration provider guarantee approval?
No. The notary, AHU, OSS, tax authority, sector authority, bank, and Immigration make their own decisions; contracts should use evidence-based endpoints.
Who should own the OSS and tax credentials?
The company should control registered contacts, authentication, recovery, downloads, and filing history through authorized officers, with limited provider access.
How should third-party charges be paid?
Use an itemized approval, verified beneficiary, official or supplier evidence, receipt, unused-balance treatment, and reconciliation to the relevant deliverable.
What should happen at termination?
Stop authority and access, return data and originals, transfer credentials and work files, reconcile money, identify pending submissions, and record correction and cooperation duties.
