Names Across Borders: Romanization and Identity Matching in Japanese Document Packages

“Please make sure the name matches the passport.”

The instruction sounds simple. It leaves three things open: which name, in which script, matched against what.

A single person may be represented by characters in a family register, by a reading recorded in kana, by a Roman-letter spelling fixed in a passport, by a rendering chosen for a translation, and by a name already sitting in a foreign case file. Those representations usually agree. When they do not, the package fails quietly.

For overseas counsel, immigration professionals, global mobility teams, and other professionals coordinating Japanese documents, this article separates those layers, summarizes what Japan’s current rules actually fix, and sets out how to keep a document package consistent before it is filed.

1. One Person, Several Name Layers

Cross-border name questions become tractable once the layers are named:

• The Japanese source name. The surname and given name as recorded in the Japanese record — characters first, in distinct fields.
• The recorded reading, where available. The furigana now recorded in the family register: a reading of the name in kana.
• An existing Roman-letter identity reference. Most often a passport, in which a spelling has already been fixed under Japan’s passport rules.
• The translation’s rendering. The Roman-letter form used in a Certified Translation of the Japanese record.
• The receiving-side filing name. The spelling already used in the particular application, proceeding, or file abroad.

These layers are connected, and Japan’s current rules connect some of them tightly. They are still not one thing, and no single layer answers for all the others.

The starting question is therefore not “how is this name romanized?”

It is: which representation of the name does this filing need to match?

2. The Japanese Record: Characters First, Fields Before Order

The source name is the one in the Japanese record — character by character. Which record that should be is a prior question, addressed in our earlier Insight, Choosing the Right Japanese Record Before Authentication: A Framework for Overseas Counsel.

Within the record, the surname and the given name are distinct elements, and Japanese law treats them as such — the current rules on readings, for example, define the reading of the surname and the reading of the given name separately.

Layout adds a trap. In a family-register certificate, the surname may appear at the level of the register while each person’s entry carries the given name; the two are not printed side by side the way a foreign form expects them.

Reading a name off the page by position, rather than by field, is how a surname ends up in a given-name box — an error no later spelling choice can repair.

Identity matching begins with correct field mapping, not with romanization.

Until the surname and given-name fields are fixed against the source, nothing should be converted into Roman letters and nothing should be reordered.

3. The Recorded Reading: What Koseki Furigana Now Adds

Japanese records have long fixed the characters of a name. The reading was, until recently, a different matter.

That changed with an amendment effective May 26, 2025: the reading of names — furigana — became a recorded matter in the family register itself. A one-year notification period ended on May 25, 2026, and where no notification was made, the law provides for the municipal mayor to record the reading.

Two limits keep this development in proportion.

First, the scope of what is recorded. Where furigana has been recorded in the family register, it provides an officially recorded reading of the name in kana. It is not itself the person’s Roman-letter spelling.

Furigana recorded in the family register records the name’s reading in kana; it is not itself an official Roman-letter spelling.

Second, coverage on paper. Whether and how a particular certificate presents a recorded reading — a current certificate, a removed register, an older issuance — should be confirmed on the document itself rather than assumed.

The recorded reading matters for the next layer, because Japan’s passport rules now sound the name by it. A reading in kana and a spelling in Roman letters nonetheless remain different things, produced by different rules.

4. Passport Romanization: Hepburn as the Default, with Real Exceptions

For many Japanese nationals, a passport is a central official Roman-letter identity reference, and the current passport rules connect it to the family-register name in two distinct steps.

First, the sounding. Under the current Passport Act Enforcement Regulations, at the time of writing, the name on a passport is the name in the family register, sounded by the reading recorded there; where no reading is recorded, established readings of the characters apply.

Second, the writing. That sounding is then written on the passport in Hepburn romanization by default.

Two steps, two layers: the recorded reading identifies how the name is sounded; Hepburn provides the default Roman-letter rendering. Neither step alone is “the name.”

Passport Hepburn also has conventions of its own. Long vowels are generally not spelled out — a name read Yoko is written YOKO, a name read Ito is written ITO — while accepted alternatives such as ITOH or OHNO exist where a long-vowel spelling has been authorized. Non-Hepburn spellings can also be accepted where official documents show the spelling is actually in use — a foreign-style name, for example — and the authorities consider the spelling appropriate and specially necessary.

The consequence for document work is direct: a mechanical transliteration of the kana reading may not reproduce the spelling in an existing passport. The passport must be looked at, not predicted.

One more feature makes the passport layer durable. Under the current regulations, a Roman-letter spelling, once recorded in a passport, can in principle no longer be changed; exceptions require a finding of special necessity. And for those whose register does not yet record a reading, current guidance keeps the spelling of an existing or previous passport in place.

5. Alternate Names on a Japanese Passport

The passport layer has one more compartment: names that are not the register name.

Under the current rules, a name other than the family-register name — a former surname, or a foreign spouse’s surname in use, for example — can in some cases be added to the passport face in parentheses after the register name. The addition requires official documents showing the name is in social use, and a finding that the notation is specially necessary for the person’s travel.

The design of the measure matters as much as its existence. It is described as an exceptional, convenience-based notation; the alternate name is not recorded in the passport’s IC chip or MRZ (Machine Readable Zone), and a former surname may carry an explanatory label identifying it as such.

For package planning, the point is structural: a parenthetical alternate name appears on the passport face but is not recorded in the IC chip or MRZ.

Whether a particular person can obtain such a notation, and whether a particular alias qualifies, is decided in the application process for the particular case — not by rule of thumb, and not by this article.

6. Translation Rendering: Follow an Identity Reference Where One Exists

A Certified Translation of a Japanese record must present the name in Roman letters. The question is on what basis.

Where an established identity reference exists — a passport, or another Roman-letter spelling already fixed in official use — the rendering should be checked against it, supported by reliable records supplied for the matter.

Where no established Roman-letter identity reference exists, the basis for the rendering must first be identified. That may include a recorded reading, where available, together with a stated romanization convention — made explicit rather than silently treated as if a legal naming decision had been made. And if the reading itself is not established, it should be confirmed rather than inferred from the characters alone.

A translation may render a name in Roman letters; it does not create a new legal identity record.

The same limit applies in the other direction. Where two existing official records already spell a name differently, a translation does not resolve that discrepancy; which reference the submission should follow is an identity question for the matter, not a wording choice within the translation.

Our office applies this rule to its own work: romanized names are supported by reliable records where available, and we do not independently determine a person’s legal name.

7. The Receiving Side: Which Spelling Does the Matter Already Use?

Submissions rarely land in empty files.

The matter abroad may already carry a spelling — in an application form, a court record, a client or matter file — and the receiving side may expect new documents to match the reference it already holds. What it expects should be confirmed in writing for the particular matter.

The passport is often that reference. It is not automatically so: which spelling a filing must match is a fact about the matter, not a rule about passports.

Where package components will differ deliberately — a maiden name in the Japanese record, a married name in the file abroad — the difference should be identified before filing. Whether an explanation or supporting evidence is needed is the receiving side’s call, made under its own requirements.

8. Name Order: Keep the Fields, Whatever the Display

Japanese records present the surname first. Foreign forms vary, and translations carry their own field labels.

This article does not propose a universal display order, because none governs every context.

The workable principle is narrower:

Keep surname and given-name fields clear even when display order changes.

A reordered name with clear field identity is a display choice. A misassigned field is an identity error — and it survives every later conversion, translation, and certification applied on top of it.

9. A Name-Consistency Decision Table

The questions below make the name layers explicit before a package is finalized.

The table does not produce a spelling.

It produces the reference against which every spelling in the package can be checked.

10. A Pre-Instruction Name Checklist

1. Receiving authority — Who will act on the documents, and in what proceeding?
2. Japanese source record — Which record carries the name being evidenced?
3. Exact source characters — What are the characters, confirmed against the record itself?
4. Surname and given-name fields — Is each element assigned to the correct field?
5. Recorded furigana / reading in kana, if available — What reading, if any, does the register record?
6. Passport or existing Roman-letter reference — What spelling is already fixed, and in which document?
7. Non-Hepburn, alternate, or former-name issue — Does any name in the matter sit outside the default pattern?
8. Translation rendering — Does the rendering follow the confirmed reference, or is its basis stated?
9. Filing or application spelling — What does the receiving-side matter already use?
10. Final cross-document consistency review — Do all package components agree, with any intentional difference identified?

If item 6 is answered “none exists,” item 8 cannot be answered by matching — the rendering basis must be stated instead.

11. The Japan-Side Representative’s Role

The receiving side determines which name reference its procedure requires. Overseas counsel or another instructing professional confirms that requirement for the matter.

A Japan-side representative can then align the package. Depending on the agreed scope, that may include:

• confirming the source characters and the surname and given-name fields in the Japanese record;
• checking whether the document presents a recorded reading, where one is available;
• collecting the existing Roman-letter references the person already holds, where available;
• checking the translation’s rendering against the confirmed reference — or recording the rendering basis where none exists;
• keeping alternate and former names in their proper layer of the package;
• running the final cross-document consistency review before dispatch.

The representative aligns the package with the confirmed references. It does not determine a person’s legal name, resolve conflicts between existing official records, or decide which spelling a foreign authority will act on.

Match the package to the confirmed identity reference, not to habit.

12. Conclusion

A name that is one name in Japanese can surface abroad in more than one Roman-letter form, each with a rule or a history behind it.

The practical sequence is:

Japanese source name — characters and fields
→ Recorded reading in kana, where available
→ Existing Roman-letter identity reference, where one exists
→ Translation rendering
→ Receiving-side filing name
→ Final consistency check

This leads to the operational rule of this article:

Confirm the identity reference before fixing the romanized spelling.

And to its corollary:

Before treating a spelling difference as a translation choice, identify the underlying identity reference.

Whether a particular spelling satisfies a particular foreign filing remains, as always, the receiving side’s decision.

Scope Note

Apostille Japan is a Tokyo-based Gyoseishoshi office handling agreed Japan-side steps for eligible documents issued or prepared in Japan, including document review and procurement where legally and practically permissible, notary coordination where required, Ministry of Foreign Affairs apostille applications, Certified Translation, final document checks, and international delivery for submissions to the United States, the United Kingdom, Singapore, New Zealand, and the Philippines.

The required evidence, name rendering, document form, authentication route, translation requirement, and final submission structure depend on the receiving authority, document type, issuing authority, and purpose of use. Apostille Japan does not determine foreign-law requirements or guarantee acceptance by a receiving authority.