Compliance obligations across India, the US, Korea and Taiwan in one register

Why do multi-country groups end up with several registers?

A group headquartered in the US with an engineering centre in India and plants in Korea and Taiwan usually has four compliance owners, four spreadsheets and four calendars. Each is right about its own country. None can answer the board's question: what is overdue across the group, and who owns it?

The obligations differ, but the shape of the work does not. Every obligation binds a specific legal entity, comes from a citable instrument, falls due under some rule, and needs an owner and evidence. A single register works when it keeps those fields consistent while letting the content vary by country.

What is a jurisdiction pack in IntelloComply?

A pack is a library of obligations and frameworks for one jurisdiction. Each library obligation carries a citation to its source, a frequency, and a due-date rule where the obligation recurs on a fixed cycle. Frameworks group related controls, such as occupational safety, employment, tax or data protection, with an owner role and the evidence expected.

Packs are additive and idempotent. Adding a pack to an entity that already has some of its obligations does not create duplicates, and an "Add Location Pack" action lets a team add a country to a register that is already in use.

Which jurisdictions are covered today?

The packs currently shipped are:

• India: the national pack covering the Companies Act, GST, income tax and TDS, labour law, EPF and ESI, shops and establishments, POSH, factories, environment, DPDP and sector regulators such as SEBI, RBI and IRDAI, with state-level obligations for every state and union territory you operate in, configured for your locations at onboarding.
• United States, federal: occupational safety, environment, export controls, employment and federal tax.
• California: employment, environment, and corporate and privacy obligations.
• Arizona: employment, environment and corporate tax.
• South Korea: corporate, tax, labour, occupational safety and health, and personal information protection, with trade and chemicals frameworks added for manufacturing and semiconductor entities.
• Taiwan: the same structure — corporate, tax, labour, occupational safety and health, and personal data protection, with trade and chemicals frameworks for manufacturing and semiconductor entities.

How does one register work across entities in different countries?

Packs are seeded per legal entity, not per organisation. When a team chooses where an entity operates, the matching packs are selected from the entity's jurisdiction, so a Korean subsidiary gets the Korea pack and not India's by default. For industries such as semiconductors and manufacturing, the Korea and Taiwan packs add trade, chemicals and quality frameworks on top of the universal set.

The same federal filing is separate work for each site that owes it, so obligations are tracked per entity: two US entities each get their own copy of a federal obligation, with their own owner and evidence. Frameworks and controls stay at group level, because a control design is usually shared. The register has a jurisdiction column and an entity selector, and the calendar filters the same way, so a country lead sees their entity and the group head sees everything.

Statutory obligations from the packs sit in the same unified register as obligations from contracts and items from frameworks, each labelled by source.

How are due dates handled when every country's rules differ?

Each recurring obligation has a due-date rule rather than a fixed date: a day of the month after the period, a number of days after quarter end, a date in the calendar year. Rules can express conventions such as "end of the following month", which the Taiwan pack uses for pension and insurance contributions.

Obligations that do not recur on a fixed cycle, such as those triggered by an event or tied to an anniversary the system does not know, are left undated rather than given an invented date. They stay in the register and are activated when the trigger is recorded. A calendar that fills those gaps with guesses looks complete and is not.

How do you know an obligation in a pack is right?

Every pack obligation carries its citation, and seeded obligations start as pending review rather than active. Nothing is presented as a live obligation of your company until someone on your team accepts it. That matters more across jurisdictions than within one, because the person accepting a Korean labour obligation should be someone who knows Korean labour law.

Source review is restricted. A record can only be marked verified against a source on an official domain that responds, such as a government gazette, a regulator's site or a legislation portal.

What do the packs not do?

They are a starting library, not a complete statement of every obligation an entity has in a country. Applicability depends on headcount, turnover, activities, licences and location within a country, and a pack cannot know all of that. Expect local counsel or the country compliance owner to mark some items not applicable and add others.

Jurisdictions without a pack are handled with custom obligations and frameworks, which use the same fields, calendar and evidence model. And a pack is not legal advice: it records what the law requires as cited, and the citation is there so that someone qualified can check it.