Japan market-entry GTM stack guide

Japan's Act on Regulation of Transmission of Specified Electronic Mail starts from prior request or consent for advertising email. The CAA summary also covers advertising SMS and advertising messages sent from overseas into Japan. Exceptions include qualifying business relationships, written notification of one's own address, and self-publication of an address by an organization or an individual conducting business. This is not a general B2B exemption. The separate Specified Commercial Transactions Act can also apply to mail-order advertising, so do not transfer exceptions between the two statutes.[2][1]

For the public-address exception, the organization or business individual must have made its own address publicly accessible online. The exception is unavailable where the address is accompanied by a statement rejecting advertising email. A data broker's result or a generated first-name address is not evidence of that self-publication. Our assessment is to retain the original publication URL, date, business context and refusal-language review before approving an exception. For consent-based sends, retain consent evidence. Include the required sender information and an accessible refusal route, and stop advertising sends following refusal, subject only to the narrow statutory exceptions.[1][2]

For manual live calling, the CAA telemarketing guide distinguishes consumer solicitation and excludes transactions between business operators. Where its consumer rules apply, the caller must identify the business, caller, service and solicitation purpose, and must not continue or repeat solicitation after refusal. An employee's or sole trader's personal purchase must not be classified as a business transaction merely because a work number was found. This guide does not establish permission for prerecorded calls, autodialing or call recording. Our assessment is to keep these disabled pending a separate review, with SMS on the email gate rather than the voice-call gate.[3][2]

For LinkedIn, manual relationship-building and InMail require their own assessment. The checked materials do not establish a blanket Japanese exemption for social direct messages, and a connection acceptance is not evidence of advertising-email consent. LinkedIn's agreement requires compliance with privacy and anti-spam law and prohibits unauthorized bots for sending messages and tools for scraping profiles. Our assessment is human-led account research and relevant individual outreach, with refusal handling shared across channels rather than automated connection-and-message sequences.[4][1]

APPI protects information identifying living individuals, which can include named business contacts. Specify the purpose of use, acquire data properly, and notify the person or publish the purpose unless an exception applies. Using information beyond the necessary scope of the specified purpose generally needs prior consent. These duties do not independently authorize an email. APPI also requires appropriate security and supervision of entrusted handlers. Third-party provision, qualifying outsourcing and purchased enrichment have different conditions. Article 30 generally requires confirmation of a third-party supplier's identity and acquisition background, with records and statutory exceptions. Our assessment is to make provenance review part of import approval, not a checkbox inferred from email validation.[5]

For personal-data provision to a foreign third party, Article 28 generally requires consent to that foreign provision unless an applicable exception or alternative applies. These include designated equivalent-protection destinations and recipients maintaining a qualifying equivalent-measures system. Before obtaining the Article 28 consent, provide the required information about the destination's protection system and recipient safeguards. The equivalent-measures route brings continuing oversight and information duties. A standard CRM contract is not automatically proof of those conditions. PPC guidance distinguishes overseas storage on a self-managed server, or a provider contractually barred from handling the data with appropriate access controls, from foreign third-party provision. Overseas security duties still remain.[5][6]

HubSpot's checked hosting FAQ lists US, Canadian, Australian and German regions, not Japan. It documents processing outside the selected region through integrations, subprocessors, support and user access. Our assessment is to map the existing CRM, enrichment tools and remote support together before promising residency. For an EU exporter, Japan is on the adequacy list, but confirm the transfer is within the decision's scope. Adequacy does not remove the exporter's processing legal basis, security, minimization or processor-contract duties. Reassess onward transfers separately rather than treating a Japanese subsidiary as a GDPR exit route.[7][8]

Apollo documents country and title filters, but distinguishes where a person lives from the employer's headquarters. Its People API Search does not return email addresses or phone numbers. Clay documents a work-email waterfall across providers, with configurable validation and an optional inferred-address step. Neither checked document establishes independently audited Japan-specific recall, current-employer accuracy or deliverable-contact coverage. An inferred address is especially unsuitable as evidence for the self-published-address exception. More waterfall providers do not resolve permission or provenance.[9][10][1]

Our assessment is to compare providers against a buyer-owned list of Japanese target companies before expansion. Separate domestic headquarters from Japanese subsidiaries of foreign groups. Review Japanese and romanized company names, current department, role seniority and domain ownership. Report account matches, correct-person matches and usable channel evidence separately, including missing records. Keep an uncontacted control sample so the team measures discovery quality rather than reply rates alone. Promote only records with an approved contact route to the CRM. A vendor's global database size is not the denominator for Japan coverage.[9][10]

Our assessment is to assign a Japanese-speaking AE before routing Japanese-language replies. Store the legal company name, Japanese display name, romanized alias and preferred contact name separately. Do not overwrite Japanese titles with a guessed English seniority. Prepare a Japanese discovery agenda, security explanation, pricing summary and implementation plan that a buyer can circulate internally. Have a fluent owner review terminology and product limitations, not merely machine-translate the English campaign.

Our assessment is to make the AE-to-CS handoff a deal requirement. Record the buyer's decision participants, procurement owner, security commitments, promised support language, Japan-time availability and agreed onboarding milestones. The CS owner should accept those commitments before signature. Carry the same company identity into the order form, invoice and support record. Review the first customer onboarding with the AE and finance owner so unsupported language promises or billing assumptions do not become permanent operating procedures.

Japan's qualified invoice system began on 1 October 2023. The NTA describes qualified invoices as part of the purchase consumption-tax credit system. Required descriptions include the registered issuer's name and number, transaction date and details, amounts by tax rate, applicable rates, consumption-tax amounts and recipient name. A registered issuer must issue an invoice when requested by a taxable customer and retain a copy. Registration also makes the issuer taxable irrespective of base-period taxable sales. Do not claim every foreign SaaS seller must register or that any PDF labeled invoice is qualified.[11][12]

The NTA distinguishes foreign-supplied B2B electronic services subject to reverse charge from B2C electronic services for which the foreign supplier generally files and pays, subject to exemptions and platform rules. Classification depends on the service's nature or enforceable business-only terms. Self-service cloud software is not necessarily B2B merely because a website says business use. Qualifying reverse-charge providers must notify the customer in advance. Our assessment is a finance-approved classification and invoice template for each selling entity and checkout path before quoting Japanese consumption tax.[12]

Stripe documents JPY bank transfers for businesses located in Japan. That does not establish availability for an EU merchant account. Transfers use virtual bank details and customer balances; recurring invoices require the customer to keep enough funds available, rather than an automatic bank debit. Our assessment is to agree currency, due date, remittance reference and reconciliation owner with procurement. Validate the actual merchant account's available rails before offering them, and keep the finance-approved tax invoice distinct from payment-method instructions.[13]