Registry entry

Japan Stock Company Establishment Registration Application (Board of Directors Installed, Incorporation by Promoters)

The Legal Affairs Bureau (法務局, part of the Ministry of Justice)'s Stock Company Establishment Registration Application (株式会社設立登記申請書), filed with the local Legal Affairs Bureau/branch office/sub-office having jurisdiction over the company's registered head office, to legally bring a newly-incorporated kabushiki-gaisha (株式会社, stock company) into existence — Japanese company law makes incorporation effective only upon this registration (会社法第49条). This document models the 'board of directors installed, incorporation by promoters' (取締役会を設置する株式会社の発起設立) variant: the promoter(s) themselves subscribe for all shares to be issued at incorporation (発起設立, as opposed to 募集設立, a public-subscription variant where third-party subscribers are also solicited), and the company installs a board of directors (取締役会設置会社) — sibling document `jp/houmukyoku/stock-company-establishment-registration-application` models the simpler no-board-of-directors counterpart of this same promoter-subscription procedure; the two remaining published variants (board-installed + public subscription, no-board + public subscription) are each their own distinct template and remain out of scope here. Installing a board of directors changes two things this document models that the no-board sibling does not: (1) a representative director is elected by board resolution from among the incorporation-time directors, rather than designated directly by the promoters/shareholders, and (2) Companies Act art. 327(2) requires a board-installed company (outside the narrow committee-based or accounting-advisor structures this document does not model) to also appoint at least one auditor, whose statutory scope of audit may optionally be limited to accounting matters by the articles of incorporation. The application itself (this document's `fields[]`) is short: company identity, the 'matters to be registered' (登記すべき事項) content — trade name, head office, method of public notice, business purposes, share capital structure, the share-transfer-restriction clause, and officer particulars (directors, representative director, and auditor) — plus the signature/filing block. A real submission also encloses a substantial packet of supporting documents (articles of incorporation, promoters' resolutions/consents, capital-payment proof, identity/seal certificates, and, if an agent files on the company's behalf, a power of attorney) — modelled here only as `documents[]` attachment requirements; the internal content of each of those supporting documents is out of scope, a candidate for a future companion-schedule cycle. GovSchema is independent and is not affiliated with, endorsed by, or operated by the Government of Japan or the Ministry of Justice. See VERIFICATION.md for the full field-by-field source mapping, the mock-data test run, and every disclosed scope decision.

Registry entry

jp/houmukyoku/stock-company-establishment-registration-application-board-of-directors

Jurisdiction
Japan · national
Version
1.0.0
Verification
draft

Authoritative source 株式会社設立登記申請書(取締役会を設置する株式会社の発起設立)/Stock Company Establishment Registration Application (company with a board of directors, incorporation by promoters) — blank application template ('申請書様式'), item 1-1 of the Legal Affairs Bureau's own '商業・法人登記の申請書様式' ('Commercial/corporate registration application forms') index at https://houmukyoku.moj.go.jp/homu/COMMERCE_11-1.html.

Machine access

Registry catalog
registry/index.jsonone record per schema id

Field reference

23 fields, read from the published schema.json, with names, types, requiredness, and validation as the document states them. The live government form remains the authoritative source.

Fields

  • companyNameFurigana string required

    フリガナ — the katakana reading of the company's trade name, excluding the part denoting the company type ('株式会社'). Per the worked-example's own annotation, written left-justified with any internal spaces removed; this furigana is published via the National Tax Agency's corporate-number ('houjin bangou') publication site and does not itself appear on the resulting Certificate of Registered Matters.

    length: 0–100classification: pii
  • companyName string required

    商号 — the company's registered trade name, including '株式会社' (either as a prefix or suffix per the promoters' choice). Reused verbatim as the 「商号」 line of the 登記すべき事項 (matters to be registered) passage and again in the signature/filing block below.

    length: 0–200
  • headOfficeAddress string required

    本店 — the company's registered head office address. The source form provides one free-text block (no structured prefecture/city/block/number sub-boxes). Reused verbatim as the 「本店」 line of the 登記すべき事項 passage and again in the filing block ('申請人 (本店)').

    length: 0–300classification: pii
  • incorporationProcedureCompletionDate date required

    登記の事由 — the form's fixed reason-for-registration phrase is '[date]発起設立の手続終了' ('as of [date], the procedure for incorporation by promoters was completed'), i.e. the date every step of the 発起設立 procedure (share subscription, officer selection, capital payment, etc.) was finished. This is ordinarily the day before, or the same day as, the filing itself.

  • methodOfPublicNotice string required

    「公告をする方法」 — how the company will publish its legally-required public notices (e.g. of annual accounts). Both the worked example and the model articles of incorporation this source publishes show the same value, '官報に掲載してする' ('by publication in the Official Gazette'), the default method under Companies Act art. 939 when a company's articles do not otherwise specify one of the Act's other statutory methods (a daily newspaper, or electronic public notice). Since neither source document in this cycle's review enumerates those other statutory methods itself, this field is modelled as free text rather than a fabricated enum, mirroring the treatment of the same field on the no-board sibling document.

    length: 0–200
  • businessPurposes string required

    「目的」 — the company's numbered list of business objectives, as they will appear on the Certificate of Registered Matters. The worked example's own three-item list ends with the standard catch-all clause '前各号に附帯する一切の事業' ('any and all business incidental to each of the preceding items'), a customary final entry. Modelled as one free-text field (numbered items separated by newlines/semicolons), per this registry's established GSP-0009 treatment of a source's own repeating/numbered list where GovSchema v0.3 has no native array type.

    length: 0–2000
  • totalAuthorizedShares integer required

    「発行可能株式総数」 — the total number of shares the company is authorized to issue (its 'authorized capital' share ceiling), not the number actually issued at incorporation.

    range: 1–∞
  • totalIssuedShares integer required

    「発行済株式の総数並びに種類及び数」 — the total number of shares actually issued at incorporation. The source heading itself also asks for the shares' 'type(s)' when a company issues more than one class of share; the worked example populates only a single running total ('「発行済株式の総数」200株') consistent with a single class of ordinary shares (普通株式), the common case for a small closely-held incorporation. A multi-class share breakdown is out of scope for this v1.0.0, mirroring the same scope decision on the no-board sibling document.

    range: 1–∞
  • capitalAmount number required

    「資本金の額」 — the company's capital (share capital) at incorporation, in Japanese yen. Japanese company law has had no statutory minimum capital requirement since the 2006 Companies Act reform (a company may incorporate with capital as low as 1 yen), so no floor beyond a positive amount is enforced here.

    range: 1–∞classification: financial
  • hasShareTransferRestriction boolean required

    「株式の譲渡制限に関する規定」 — whether acquiring the company's shares by transfer requires the company's prior approval. Virtually universal for a small, closely-held incorporation of this kind (both source documents show the restriction clause present). Unlike the no-board sibling document, where approval defaults to the shareholders' meeting (the company's only decision-making body), Companies Act art. 139(1) makes the board of directors the default approving body for a board-installed company such as this one, unless the articles of incorporation specify otherwise — a distinction disclosed here rather than modelled as its own field, since neither source PDF prints the approving body's identity on this line.

  • shareTransferRestrictionClause string optional

    The restriction's exact wording as it will appear on the Certificate of Registered Matters. Both source documents show the identical standard clause: '当会社の株式を譲渡により取得するには、当会社の承認を受けなければならない。' ('A person who wishes to acquire the Company's shares by transfer must obtain the Company's approval.'), the same wording as the no-board sibling document.

    length: 0–500
  • directorNames string required

    「役員に関する事項」「資格」取締役「氏名」— the full names of every director (取締役) at incorporation, including whichever one is separately elected representative director below. Unlike the no-board sibling document (whose representative director is designated directly by the promoters/shareholders), this variant's representative director is elected by resolution of the incorporation-time directors themselves — see representativeDirectorSelectionDocumentFile below. The worked example lists three directors; the source's registry entry discloses only each director's name (not address), modelled as one free-text field (names separated by semicolons), per this registry's established GSP-0009 treatment of a source's own repeating officer table.

    length: 0–500classification: pii
  • representativeDirectorName string required

    「役員に関する事項」「資格」代表取締役「氏名」— the director elected by the board of incorporation-time directors to represent the company (代表取締役); one of the names already listed in directorNames, but registered a second time together with an address because a representative director's address (unlike an ordinary director's) is itself a matter of public registration.

    length: 0–200classification: pii
  • representativeDirectorAddress string required

    「役員に関する事項」「資格」代表取締役「住所」— the representative director's residential address, publicly registered (unlike an ordinary director's address, which is not).

    length: 0–300classification: pii
  • hasAuditor boolean required

    設立時監査役 — whether the company appointed an auditor (監査役) at incorporation. Unlike the no-board sibling document (where this is genuinely optional and absent from that document's own worked example), Companies Act art. 327(2) requires a board-installed company to have an auditor, unless the company instead adopts a committee-based governance structure (指名委員会等設置会社/監査等委員会設置会社) or is a non-public company with an accounting advisor (会計参与) installed — neither of those narrower alternative structures is modelled by this document, so this field is required rather than optionally gated, consistent with this variant's own worked example, which does show one auditor, and the source's own attachment note grouping the director's and auditor's identity-verification requirement together ('設立時取締役、設立時監査役(印鑑証明書を添付しない役員)について...本人確認証明書を添付します。').

  • auditorNames string required

    The name(s) of the auditor(s) (監査役) appointed at incorporation. Modelled as one free-text field (names separated by semicolons) for the same repeating-table reason as directorNames. The worked example shows a single auditor.

    length: 0–500classification: pii
  • auditorScopeLimitedToAccounting boolean optional

    「監査役の監査の範囲に関する事項」「監査役の監査の範囲を会計に関するものに限定する旨の定款の定めがある」 — whether the articles of incorporation limit the auditor's statutory scope of audit to accounting matters only (as opposed to the default, broader scope covering both accounting and the directors' general conduct of business). This registered matter has no counterpart on the no-board sibling document, whose own worked example has no auditor at all. Not present in either source PDF's blank template (which defers the entire 登記すべき事項 body to the annex/別紙), only in the worked example's own annex; modelled as optional since the underlying articles-of-incorporation clause it reflects is itself optional.

  • applicationDate date required

    The date printed directly above the destination Legal Affairs Bureau line: '上記のとおり、登記の申請をします。令和 年 月 日' ('As stated above, I hereby apply for registration. [date]').

  • legalAffairsBureauOffice string required

    「__法務局__支局/出張所 御中」— the specific Legal Affairs Bureau (or its branch/局, or sub-office/出張所) having jurisdiction over the company's registered head office, to which this application is physically or electronically filed.

    length: 0–200
  • contactPhoneNumber string optional

    連絡先の電話番号 — a daytime contact number printed directly under the filing block, with no explicit mandatory/optional marking on either source document; modelled as optional, consistent with how this registry treats an unmarked contact-number line on other Japanese government forms, including the no-board sibling document.

    length: 0–30classification: pii
  • filedByAgent boolean optional

    Whether an agent/proxy (代理人), rather than the representative director personally, files this application. The worked example's own annotation states the agent's block is 'completed only when an agent files the application' ('代理人が申請する場合にのみ記載し...'), and that in that case the representative director's own seal is not required on the application.

  • agentName string optional

    Agent — Name

    length: 0–200classification: pii
  • agentAddress string optional

    Agent — Address

    length: 0–300classification: pii

Verification record

This file is the source-review record for this document version, per the manual-source-review-v1 practice.

Current claim

  • status: draft
  • verification.method: manual-source-review-v1
  • verification.lastVerifiedAt: 2026-07-10
  • maturity.level: structural-reference

Why this candidate, this cycle

This is the recurring "GovSchema Standard Research" cycle (GOV-2049). The task brief itself is generic (catalog what exists, research what is missing, author a schema for a genuinely open gap) — per this registry's established pattern (see e.g. jp/houmukyoku/limited-liability-company-establishment-registration-application's own VERIFICATION.md), the brief's own named National ID candidates (DE Steuer-ID, SG NRIC loss/damage/re-registration, NZ RealMe, "remaining voter registration") were re-checked first against CATALOG.md and confirmed already resolved by prior cycles (de/finanzamt/tax-identification-number, sg/ica/identity-card-replacement + sg/ica/identity-card-reregistration, nz/dia/realme-verified-identity; every tracked voter-registration gap is either published or a confirmed dead end/legally-closed window). CATALOG.md's own Known Gaps item 6 was then re-read fresh and found to still flag the same three open Japan companion-schedule candidates it has flagged since GOV-2019: the Legal Affairs Bureau's three remaining sibling stock-company-incorporation variants (rows 1-1, 1-2, 1-4 of the houmukyoku.moj.go.jp index page already sourced for the published no-board sibling, row 1-3) and the Seal Registration Notification's own corporate-representative-member scenario (a narrower, already-partially-modelled companion, closed by GOV-2035 for its main case).

Of the three sibling incorporation variants, row 1-1 (board of directors installed, incorporation by promoters) was picked over row 1-2 (board installed, public subscription) and row 1-4 (no board, public subscription) because it is the strongest, most clearly differentiated candidate: installing a board of directors changes two things the application form itself surfaces as genuinely new fields/attachments relative to the already-published no-board sibling (a board-elected, rather than directly-designated, representative director; a Companies Act art. 327(2)-mandated auditor), whereas row 1-4 only changes the subscription mechanism (promoter-only vs. public), a distinction this specific application form does not itself surface as any distinct field — its only visible effect would be on the internal content of the articles of incorporation and promoters' consent documents, both already out of scope as undecomposed documents[] attachments. Row 1-2 (board installed + public subscription) would combine both axes but was not picked this cycle, left as a candidate for a future cycle once this simpler board-axis variant establishes the officer-particulars/auditor pattern.

Sources examined

  • Document (id, version): jp/houmukyoku/stock-company-establishment-registration-application-board-of-directors / 1.0.0
  • Spec version: GovSchema 0.3.0
  • Authority: Legal Affairs Bureau (法務局), Ministry of Justice (houmukyoku.moj.go.jp).
  • Blank template (fetched live, HTTP 200, 623400 bytes, with a browser User-Agent): https://houmukyoku.moj.go.jp/homu/content/001249314.pdf — item 1-1 ("株式会社設立登記申請書(取締役会を設置する株式会社の発起設立)", "Stock company with a board of directors, incorporation by promoters") of the same index page (https://houmukyoku.moj.go.jp/homu/COMMERCE_11-1.html, section "1 設立") the already-published no-board sibling document is sourced from (item 1-3). 20 pages, zero AcroForm/Widget annotations on every page (confirmed via pdfjs-dist's getAnnotations()), a full genuine Japanese text layer.
  • Companion worked example (fetched live, HTTP 200, 756356 bytes, with a browser User-Agent): https://houmukyoku.moj.go.jp/homu/content/001331097.pdf — the Bureau's own filled-in specimen ("記載例") of the identical row 1-1 variant, titled on its own first line "(取締役会を設置する株式会社の発起設立)". 20 pages, zero AcroForm/Widget annotations, same placeholder company name "○○商事株式会社" throughout as every other Japan document in this registry sourced from this same index page.
  • The index page itself (fetched live, HTTP 200, 143773 bytes): https://houmukyoku.moj.go.jp/homu/COMMERCE_11-1.html — re-confirmed row 1-1's two linked files (001249314.pdf blank template, 001331097.pdf worked example, plus a .docx edition not opened) and the full four-variant table already recorded in the no-board sibling's own VERIFICATION.md: | Row | Variant | Worked example | Blank template | |---|---|---|---| | 1-1 | Board of directors installed, incorporation by promoters (発起設立) | 001331097.pdf (this document's worked example) | 001249314.pdf (this document's source) | | 1-2 | Board of directors installed, public subscription (募集設立) | 001252642.pdf | 001249316.pdf | | 1-3 | No board of directors, incorporation by promoters (発起設立) | 001331002.pdf | 001249317.pdf (already published, jp/houmukyoku/stock-company-establishment-registration-application) | | 1-4 | No board of directors, public subscription (募集設立) | 001331010.pdf | 001249318.pdf |
  • Cross-check source: the already-published no-board sibling's own two source PDFs, re-fetched fresh this cycle (001249317.pdf blank template, 574954 bytes; the sibling's worked example was not re-fetched since its own VERIFICATION.md already records the full extraction) — used only to isolate, line-by-line, exactly what differs between the two variants, not re-verified independently as its own claim (that document's own review gate already covered that).
  • Retrieved / reviewed: 2026-07-10.
  • Reviewer: GovSchema Engineering (Standards Engineer — initial authoring source review).
Bot-mitigation note

Re-confirms the finding recorded by every prior Japan cycle since GOV-2005: houmukyoku.moj.go.jp returns HTTP 403 to a plain default-curl request but HTTP 200 to a request carrying an ordinary desktop-browser User-Agent string (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0 Safari/537.36) — narrow bot mitigation keyed on the default-curl signature, not an IP-level block. All three files (blank template, worked example, index page) were fetched successfully with that browser User-Agent on the first attempt. node tools/verify-sources.mjs registry/jp/houmukyoku/stock-company-establishment-registration-application-board-of-directors/1.0.0 reports "1 directory, 4 URLs checked, 0 warning(s), 0 allowlisted, all clear" — confirmed directly, immediately before opening this PR.

Extraction method

Both PDFs were extracted with pdfjs-dist (pinned 3.11.174, installed into a throwaway /tmp scratch directory, not added to this repo's tracked package.json) via getTextContent(), sorting each page's text items by descending y (row, top to bottom) then ascending x (column, left to right) before concatenation — the same x/y-coordinate row-grouping technique used for every other Japan document in this registry sourced from a non-AcroForm PDF with mixed prose/label-value layout. Zero AcroForm/Widget annotations were confirmed on every page of both PDFs via getAnnotations().

The critical extraction finding, driving this document's field/scope decisions, came from diffing this variant's own blank template and worked example against each other and against the already-published no-board sibling's own two source PDFs:

  1. The blank template defers its entire 登記すべき事項 (matters to be registered) body to a separate annex page ("別紙のとおり(※別紙は4 ページ参照。)", page 1) — unlike the no-board sibling's own blank template, which embeds that body directly and fully on page 1 itself. The annex page (page 4 of the blank template) nonetheless still carries the identical ○○商事株式会社 placeholder content seen in the worked example's own annex (page 5), the same underlying reality already documented in the no-board sibling's own VERIFICATION.md (登記すべき事項 is a passage the applicant drafts and submits separately, not literal boxes printed on the page) — this document's structural presentation differs from its sibling, but the substance does not.
  2. The attachment list's own wording for the officer's-acceptance and investigation-report items changes from parenthetical/optional auditor phrasing to unconditional auditor phrasing. The no-board sibling's blank template prints "設立時取締役(及び設立時監査役)の就任承諾書" and "設立時 取締役(及び設立時監査役)の調査報告書及びその附属書類" — the auditor bracketed as an "if any" case. This variant's blank template instead prints "設立時取締役、設立時代表取締役及び設立時監査役の就任承諾書" and "設立時 取締役及び設立時監査役の調査報告書及びその附属書類" — no brackets, and the representative director named as a third, distinct party alongside ordinary directors and the auditor. This is independent, source-printed corroboration (not outside legal knowledge) that a board-installed company's auditor is not merely optional the way it is for the no-board sibling.
  3. The worked example's own officer block (登記すべき事項, annex page 5) additionally shows a 監査役 (auditor) entry, an auditor audit-scope registered-matter pair, and a 「監査役設置会社に関する事項」 line — none of which appear anywhere in the no-board sibling's own worked example (which the sibling's own VERIFICATION.md explicitly records as having "no auditor"). Combined with finding 2 above, this document treats the auditor as required rather than optionally gated — see "What the application maps to" below for the full disclosed reasoning, including the Companies Act art. 327(2) statutory backdrop and its narrow, out-of-scope exceptions.
  4. The representative director is selected by the incorporation-time directors' own board resolution, not designated directly by the promoters/shareholders as in the no-board sibling. The worked example's own specimen packet (pages 12-13) shows a two-step process: first a "設立時取締役、設立時監査役選任及び本店所在場所決議書" (a promoters' resolution appointing the incorporation-time directors and auditor), then a separate "設立時代表取締役選定決議書" (a resolution of those already-appointed directors electing one of themselves as representative director) — the same two-document structure the no-board sibling's own attachment list already names (representativeDirectorSelectionDocumentFile), but there that document is only conditionally required ("more than one director is appointed and one of them is separately selected"), whereas here it is unconditionally printed on the attachment list and therefore modelled as always required.

What the application maps to

  • フリガナ / 商号 / 本店 / 登記の事由companyNameFurigana, companyName, headOfficeAddress, incorporationProcedureCompletionDate — identical source rows and treatment to the no-board sibling document.
  • 「公告をする方法」/「目的」/「発行可能株式総数」/「発行済株式の総数並び に種類及び数」/「資本金の額」methodOfPublicNotice, businessPurposes, totalAuthorizedShares, totalIssuedShares, capitalAmount — unchanged from the no-board sibling document; the board-of-directors distinction has no effect on any of these registered matters, confirmed by both variants' worked examples printing the identical illustrative values (800 authorized shares, 200 issued shares, ¥10,000,000 capital).
  • 「株式の譲渡制限に関する規定」hasShareTransferRestriction + shareTransferRestrictionClause. Both variants' worked examples print the identical standard clause text, but the default approving body differs by operation of law even though neither source PDF prints it explicitly: Companies Act art. 139(1) makes the board of directors the default approver for a board-installed company (this document), versus the shareholders' meeting for a no-board company (the sibling) — disclosed in the field's own description rather than modelled as a separate field, since it is not itself a data point either source document asks the applicant to supply.
  • 「役員に関する事項」(取締役)directorNames, unchanged in kind from the no-board sibling, though this variant's own worked example lists three directors rather than two.
  • 「役員に関する事項」(代表取締役)representativeDirectorName / representativeDirectorAddress, unchanged in kind, but their description fields are updated to disclose the board-election mechanism (see extraction finding 4 above) in place of the no-board sibling's direct-designation mechanism.
  • 「役員に関する事項」(監査役)hasAuditor (now required: true, changed from the no-board sibling's required: false) + auditorNames (now unconditionally required: true rather than requiredWhen-gated). Grounded in extraction findings 2 and 3 above: Companies Act art. 327(2) requires a board-installed company to appoint an auditor unless it instead adopts a committee-based governance structure (指名委員会等設置会社/監査 等委員会設置会社) or is a non-public company with an accounting advisor (会計参与) installed — neither alternative structure is modelled by this document (see "What is NOT modelled" below), so within this document's own scope the auditor is not optionally gated. This is a deliberate, disclosed departure from the no-board sibling's own field shape, not an oversight — the two documents' hasAuditor fields are intentionally different (optional vs. required) because the underlying legal requirement itself differs by company structure.
  • 「役員に関する事項」(監査役の監査の範囲に関する事項) → new field auditorScopeLimitedToAccounting (boolean, optional), with no counterpart on the no-board sibling document (whose own worked example has no auditor at all to have a scope-of-audit registered matter for). Sourced from the worked example's own annex line "監査役の監査の範囲を会計に関するものに 限定する旨の定款の定めがある".
  • The filing block (page 2 of the blank template) → applicationDate, legalAffairsBureauOffice, contactPhoneNumber, filedByAgent / agentName / agentAddress — unchanged in kind and treatment from the no-board sibling document.
  • The attachment list (「添付書類」) → documents[], the same ten attachment requirements as the no-board sibling document, by the same ids (deliberate reuse, not re-specification, per this registry's composability/reuse convention), but with two required/description changes disclosed above: representativeDirectorSelectionDocumentFile changes from conditionally required to unconditionally required (extraction finding 4), and acceptanceOfAppointmentLettersFile / investigationReportAndAttachmentsFile have their label/sourceRef updated to the unconditional (non- parenthetical) auditor wording this variant's own source PDFs print (extraction finding 2).

What is NOT modelled (out of scope), and why

  • The two remaining sibling variants (board installed + public subscription, no board + public subscription — rows 1-2 and 1-4 of the same index-page section) — each its own distinct template, left as candidates for a future companion-schedule cycle, per the "Why this candidate, this cycle" reasoning above.
  • Committee-based governance structures (指名委員会等設置会社, nomination-committee company; 監査等委員会設置会社, audit-and-supervisory- committee company) and the non-public-company-with-accounting-advisor exception to Companies Act art. 327(2) — each a distinct, rarer governance structure under which a board-installed company's auditor requirement is replaced or waived. Neither source PDF examined this cycle documents either alternative structure; this document models only the plain board-of-directors-plus-company-auditor case its own worked example actually shows.
  • The internal content of every attached supporting document (the articles of incorporation's own model articles; the promoters' consent/resolution letters; the investigation report; the capital-payment proof; the capital-amount certificate; the power of attorney) — each modelled only as a documents[] attachment requirement, not decomposed field-by-field, mirroring the no-board sibling document's own scope decision.
  • The registration-fee/tax computation (「課税標準金額」and「登録免許税」) — both source documents show the identical formula already documented in the no-board sibling's own VERIFICATION.md (0.7% of capitalAmount, ¥150,000 statutory floor, rounded down to the nearest ¥100) — a pure arithmetic derivation of capitalAmount with no independent input, excluded per this registry's established excludable-arithmetic-vs-input test.
  • 「登記記録に関する事項」「設立」 and, when hasAuditor is true, 「監査役設置会社に関する事項」「監査役設置会社」 — both fixed, non-variable constants that follow automatically from this document's own premise (this is the board-installed variant; a true hasAuditor implies the company is, by definition, an auditor-installed company) rather than independent data points the applicant supplies. Likewise「取締役会設置会社 に関する事項」「取締役会設置会社」is a fixed constant of this specific document (every filing against this template installs a board of directors, unlike the no-board sibling, where the equivalent statement is simply absent).
  • The "other possible attachments" examples the worked example's own page 2 lists beyond the ten core attachment types (a share-registrar-agent contract, when one is appointed; a court-appointed inspector's investigation report and related professional certificates, for larger in-kind contributions requiring court inspection under Companies Act art. 33) — both narrower, rarer edge cases the source itself frames as supplementary examples ("それ以外の添付書類の例"), not part of the ten-item core attachment list either variant's blank template prints; left unmodelled, consistent with investigationReportAndAttachmentsFile's own existing scope boundary (ordinary directors'/auditor's investigation report, not a court-appointed inspector's).
  • The Word (.docx) edition of the blank template, linked alongside the PDF at the same index-page row — not opened or cross-checked this cycle.

Mock-data test run

Per this registry's established practice, a one-off Node.js script (not committed to the repo) checking every type/required/requiredWhen/ validation constraint in schema.json was run against two realistic scenarios plus five negative controls:

``` PASS [OK] Scenario 1: worked-example values, board-installed, filed by representative director personally PASS [OK] Scenario 2: sole-promoter incorporation with agent filing PASS [FAIL] Negative control 1: missing hasAuditor/auditorNames (required in this board-installed variant) - MISSING required field: hasAuditor - MISSING required field: auditorNames PASS [FAIL] Negative control 2: missing shareTransferRestrictionClause when required - MISSING required field: shareTransferRestrictionClause PASS [FAIL] Negative control 3: missing agentName/agentAddress when filedByAgent=true - MISSING required field: agentName - MISSING required field: agentAddress PASS [FAIL] Negative control 4: capitalAmount below minimum (0) - INVALID minimum for capitalAmount: 0 < 1 PASS [FAIL] Negative control 5: missing representativeDirectorSelectionDocumentFile (always required in this variant) - MISSING required document: representativeDirectorSelectionDocumentFile

ALL SCENARIOS BEHAVED AS EXPECTED ```

Scenario 1 reproduces the worked example's own illustrative values (three directors, one also representative director, one auditor with scope limited to accounting, filed by the representative director personally — filedByAgent: false). Scenario 2 is an independently-constructed fictional scenario (a two-director incorporation, "藤崎コンサルティング株式会社", filed through a judicial-scrivener agent — exercising filedByAgent/agentName/ agentAddress together, with a different auditor-scope choice). The five negative controls confirm the check script actually enforces required/requiredWhen (for hasAuditor/auditorNames, unconditionally required in this variant unlike the no-board sibling; shareTransferRestrictionClause; the filedByAgent-gated agent fields; and representativeDirectorSelectionDocumentFile, unconditionally required in this variant) and validation.minimum (rejecting a zero-yen capitalAmount) rather than trivially passing everything. No defects were found in the schema itself.

Both registry validators were run against the schema document and pass:

``` $ node tools/validate.mjs registry/jp/houmukyoku/stock-company-establishment-registration-application-board-of-directors/1.0.0/schema.json ok registry/jp/houmukyoku/stock-company-establishment-registration-application-board-of-directors/1.0.0/schema.json 1/1 document(s) passed.

$ node tools/validate-ajv.mjs registry/jp/houmukyoku/stock-company-establishment-registration-application-board-of-directors/1.0.0/schema.json ok registry/jp/houmukyoku/stock-company-establishment-registration-application-board-of-directors/1.0.0/schema.json [v0.3] 1/1 document(s) validated against the meta-schema (ajv 2020-12). ```

Full-registry validation (this document plus every prior document) and node tools/verify-sources.mjs registry/jp/houmukyoku/stock-company-establishment-registration-application-board-of-directors/1.0.0 ("1 directory, 4 URLs checked, 0 warning(s), 0 allowlisted, all clear") were both re-run clean immediately before opening this PR.

Scope and jurisdiction notes

  • This is Japan's seventh document in the registry (after jp/isa/certificate-of-eligibility-application, jp/j-lis/individual-number-card-issuing-application, jp/houmukyoku/stock-company-establishment-registration-application, jp/houmukyoku/limited-liability-company-establishment-registration-application, jp/houmukyoku/seal-registration-notification, and jp/nta/individual-income-tax-final-return) and its second in the Business Formation vertical alongside a company-type variant — Japan remains at 4 of its 6 verticals (Visa, National ID, Business Formation, Taxes); this document deepens rather than widens Business Formation coverage. DMV and Passport remain confirmed dead ends (GOV-2005).
  • id/process slug stock-company-establishment-registration-application-board-of-directors reuses the already-published sibling's own base slug with a -board-of- directors suffix, following this registry's established suffix convention for a same-authority, same-underlying-process variant (e.g. ZA SARS's ITR14 Annexure family: -dormant, -micro-business, -body-corporate, -small-business, -medium-large-business).
  • version set to 1.0.0: this document models one complete, self-contained procedural variant in full (every page of its own application template), the same basis this registry has used for every other Japan document's initial release.
  • Conditional requiredness uses requiredWhen (GSP-0013), consistent with every other recent document in this registry.

Re-verification

Per the practice's cadence, nextReviewBy is set to 2027-01-10 (6 months). A future review should prioritize the two remaining sibling incorporation variants (board installed + public subscription; no board + public subscription) as companion documents, both flagged above as the registry's remaining open Japan companion-schedule candidates on the same houmukyoku.moj.go.jp index page.

View the raw record (VERIFICATION.md)

Version history

  • 1.0.0 draft latest this page has verification record schema.json

Independent and non-affiliated

GovSchema is an independent, open-source project. This reference is not produced, reviewed, or endorsed by Legal Affairs Bureau (法務局), Ministry of Justice or any government. The authoritative source is always the live government form and its official instructions.