Raffles Consulting Services
Design a Johor-Singapore SEZ operating model by assigning activities, people, assets, contracts, approvals, tax and cross-border flows to each location.
A Johor-Singapore Special Economic Zone plan should begin with the operating split, not an assumption that one new entity or incentive solves the expansion. The bilateral initiative is intended to improve connectivity, movement and the regional business ecosystem, while each company still needs separate corporate, tax, licensing, customs, employment and commercial decisions in both jurisdictions.
Assign real activities to each location
List headquarters decisions, research, design, manufacturing, warehousing, logistics, sales, finance, support and customer service. For each activity, record the people, premises, assets, systems and authority needed. Use the twinning concept only where the two locations add a real operational advantage and the handoffs can be governed.
The current EDB JS-SEZ page describes complementary Singapore and Johor operations, nine Johor zones, eleven sectors and the Singapore project office. The official agreement summary states the bilateral aims of goods connectivity, people movement and a stronger business ecosystem. These are policy facts, not automatic company approvals.
Map cross-border flows before choosing entities
Trace goods, services, data, intellectual property, cash, employees and management decisions between the locations. Identify customs, transfer pricing, indirect tax, withholding tax, immigration, payroll, data protection and licensing questions. Obtain Malaysian and Singapore professional advice where the conclusion depends on local law.
Compare a Singapore company, Malaysian subsidiary, branch, contract manufacturer or service arrangement against the actual risk and decision model. Avoid using a paper allocation that does not match people and assets. Link the Singapore side to the Singapore entry-options cornerstone.
Build the implementation sequence and evidence
Sequence site selection, licences, banking, contracts, hiring, mobility, systems, customs readiness, pilot production and customer commitments. Keep incentives conditional until the relevant authority confirms them. A project-office introduction or adviser meeting is not an approval, permit or tax ruling.
Run a pilot handoff with realistic volumes and exceptions. Measure border time, inventory visibility, quality, rework, decision latency and cost. Record which assumptions failed and revise the operating design before scaling. Preserve dated source checks because facilities, procedures and support routes can change as implementation develops.
Turn the decision into a controlled file
Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.
Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.
Review before commitment and again before closeout
Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.
Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.
Handle exceptions without rewriting history
Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.
If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.
Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.
Verify the final outcome independently
Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.
Use the Singapore market-entry cornerstone for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.
Practical review checklist
- Activities assigned by location
- Entities follow operating facts
- Cross-border flows mapped
- Licences and tax questions owned
- Pilot handoffs tested
A JS-SEZ operating model is ready when activities, people, assets, contracts and decisions are assigned to real locations and every cross-border flow has an owner, legal route and tested handoff.