Japanese Invoice Localization:
Why the Qualified Invoice System (インボイス制度) Breaks Foreign SaaS Billing

TL;DR

Key Takeaways

• The registration number is non-negotiable — without a 登録番号 ("T" + 13 digits) on the invoice, the buyer cannot claim the consumption tax credit, which raises their real cost and stops payment.
• Tax must be broken out by rate — a qualified invoice shows the taxable amount and consumption tax separately for the 10% standard rate and the 8% reduced rate, not a single bundled total.
• 領収書, 請求書, and 適格請求書 are three different documents — English "invoice" or "receipt" collapses distinctions that Japanese finance treats as legally meaningful.
• The PDF and its email must be localized, not translated — field labels, issuer name, recipient company name, and amount formatting all follow Japanese conventions, not a word-for-word rendering of the English template.
• Payment expects 振込 details and clear 締め日 / 支払サイト — Japanese B2B buyers settle by bank transfer and plan around a closing date and payment cycle, which the invoice should state explicitly.
• A non-compliant invoice is a trust signal — to a Japanese 経理 team, a missing registration number reads as a vendor that does not understand the market, eroding B2B confidence beyond the single transaction.

The Qualified Invoice System: What Changed in 2023

The single most important fact for any foreign company billing Japanese businesses is this: on October 1, 2023, Japan introduced the Qualified Invoice System — formally the 適格請求書等保存方式, almost always called インボイス制度 in conversation. It changed the rules of what an invoice has to contain in order to be useful to the company receiving it.

Under the consumption tax (消費税) system, a business buyer normally subtracts the tax it paid on its purchases from the tax it owes on its sales. This is the input tax credit, called 仕入税額控除 in Japanese. The Qualified Invoice System added a condition: from October 2023, a buyer can only claim that credit if it holds a qualified invoice (適格請求書) issued by a registered issuer. An ordinary invoice that lacks the required fields no longer supports the credit.

For a Japanese company, the consequence is concrete and financial. If a vendor's invoice does not qualify, the buyer loses the ability to deduct the consumption tax on that purchase, which makes the service effectively more expensive. This is why a foreign SaaS invoice that looks perfectly normal by international standards gets returned by the customer's accounting team. The team is not nitpicking formatting — they are protecting their own company's tax position. A non-compliant invoice is, for them, a cost.

Foreign vendors often discover this only after the fact: the subscription is live, the service is being used, and then the first invoice gets bounced with a request for a「適格請求書」and a「登録番号」that the billing system has never heard of. By then the relationship is already strained. Getting the invoice right before the first billing cycle is far cheaper than fixing it under pressure afterward.

The Required Fields on a 適格請求書

A qualified invoice is defined by the specific information it carries. Translation alone never produces these fields because they do not exist on a typical English invoice — they have to be added. The qualified invoice must include the issuer's name and registration number, the transaction date, a description of what was supplied, the amount split by tax rate with the tax shown separately, and the name of the recipient.

The registration number (登録番号) is the field foreign systems most often miss entirely. It is issued to a business that registers as a qualified invoice issuer (適格請求書発行事業者) with the National Tax Agency, and it always takes the form of the letter "T" followed by a 13-digit number. There is no way to fabricate or approximate it; the buyer's finance team can and does check that it is present and well-formed. If your company has registered, the number must print on every invoice. If it has not registered, you cannot issue a qualified invoice at all — a position that an increasing number of Japanese B2B buyers treat as a reason not to purchase.

The second field foreign templates routinely get wrong is the tax breakdown. A qualified invoice must show, for each applicable tax rate, the total taxable amount at that rate and the consumption tax charged on it. A single line reading "Tax: ¥X" is not sufficient. Even if a SaaS subscription is entirely taxed at the 10% standard rate, the invoice must state that the items are 10%-rate items and show the tax for that rate as its own figure. The 8% reduced rate applies to a narrower set of items, but the document still has to be structured so that, if both rates ever appeared, each would be shown separately.

The recipient's name also matters more than on an English invoice. A qualified invoice should carry the buyer's registered company name (the 宛名), not just an email address or a personal first name pulled from the signup form. Japanese finance teams file invoices against the legal entity, and an invoice addressed to "john@" rather than to the company name creates an internal matching problem before anyone even looks at the tax fields.

領収書 vs 請求書 vs 適格請求書

English uses "invoice" and "receipt" loosely, and many billing systems use them almost interchangeably. Japanese does not. There are three distinct documents, and using the wrong word — or sending the wrong document — signals to a Japanese finance team that the vendor does not understand how their process works.

A 請求書 (seikyūsho) is a bill: a request for payment, issued before money changes hands. A 領収書 (ryōshūsho) is a receipt: confirmation that payment was received, issued after money changes hands. These map to two different moments in the transaction, and a Japanese accounting workflow treats them as separate records. Sending a document labeled "Receipt" when the customer needs a 請求書 to initiate payment — or vice versa — interrupts the workflow.

The 適格請求書 (tekikaku seikyūsho), the qualified invoice, is not a fourth document type sitting alongside the others. It is a property a 請求書 or a 領収書 can have: the document additionally meets the field requirements of the Qualified Invoice System. So a single PDF can be both a 請求書 and a 適格請求書 if it requests payment and carries the registration number and per-rate tax breakdown. The critical point for foreign vendors is that being a valid 請求書 does not make a document a 適格請求書. The qualifying fields are an additional layer, and it is that layer the customer's finance team is checking for.

How to Present the Consumption Tax Breakdown

The tax section is where compliant Japanese invoices look most different from English ones, and it is worth getting the layout right rather than approximating it. The consumption tax standard rate in Japan is 10%, with a reduced rate of 8% applied to a defined set of items. A qualified invoice has to make the rate-by-rate math visible, not hidden in a single total.

In practice this means the invoice groups line items by tax rate, then for each rate shows the subtotal of taxable items and the consumption tax on that subtotal. The customer's finance team reads this structure to confirm that the tax was calculated correctly per rate — which is exactly what they need in order to claim the input tax credit. A foreign template that lists items and then drops a single combined tax figure at the bottom forces them to reverse-engineer the rate split, and many will simply reject the invoice rather than do that work.

Two formatting conventions accompany the tax section. Amounts are conventionally written with the yen marker as a suffix — 55,000円 — rather than a leading "¥" alone, and the document typically labels the taxable category as 「10%対象」 (subject to 10%). Getting these surface conventions right is low-effort and signals to the reader that the document was prepared for Japan, not merely converted to it.

Localizing the Invoice PDF and Its Email — Not Just Translating

The distinction between translating an invoice and localizing one is the heart of this topic. A translated invoice keeps the structure of an English document and swaps the words. A localized invoice is rebuilt around what a Japanese finance team needs to find, where they expect to find it, in the labels they recognize.

The field labels are the most visible layer. "Bill to" becomes 宛名 or 請求先; "Issued by" becomes 発行者; "Invoice date" becomes 発行日; "Due date" becomes お支払期限. These are not arbitrary translations — they are the standard labels Japanese invoices use, and a reader scans for them by shape. An invoice that invents its own translated labels makes the finance team hunt for each field.

The accompanying email matters just as much as the PDF. A billing email that opens with "Hi John, please find your invoice attached" lands wrong in a B2B context where the recipient is a finance staffer, not the person who signed up. The Japanese billing email should address the company politely, state clearly that the attached document is the 請求書 (and that it is a 適格請求書), name the payment due date and method, and close in the register Japanese business correspondence expects. The email is the first thing the 経理 team reads; if it is casual or clearly auto-translated, the invoice attached to it inherits that impression before it is even opened.

Payment Terms: 締め日 and 支払サイト

Japanese B2B payment runs on a rhythm that foreign vendors frequently misread. Rather than paying each invoice on its own due date, many Japanese companies aggregate invoices to a monthly closing date (締め日) and then pay them together after a fixed interval — the payment cycle (支払サイト). A common pattern is「末締め翌月末払い」: invoices are closed at the end of the month and paid at the end of the following month.

The practical implication is that a foreign vendor's expectation of "Net 14" or "due on receipt" often does not match how the customer's payables process actually works. The customer is not refusing to pay — their internal cycle simply does not have a slot for an off-schedule due date. An invoice that states its terms in a way the customer can map onto their 締め日 and 支払サイト avoids a round of back-and-forth. Where possible, aligning the billing date with a typical closing date, and stating the due date as a clear calendar date rather than a relative "Net N," makes the invoice fit the customer's process instead of fighting it.

This is also why the due-date field should be an explicit date (お支払期限: 2026年7月31日) rather than a relative term. A Japanese finance team plans payment runs around dates, not around "14 days from issue," and a relative term forces them to do a calculation that an explicit date removes.

Bank Transfer (振込) Details

The default settlement method for Japanese B2B is the bank transfer, called 振込 (furikomi). Credit-card-only billing, common for international SaaS, is frequently a blocker for Japanese business customers whose accounting processes are built around transfers. An invoice that expects payment should therefore present complete and correctly labeled bank account (口座) details.

A Japanese bank transfer requires a specific set of fields, and finance staff look for each by its standard label: the bank name (銀行名), the branch name (支店名), the account type (口座種別 — 普通 for ordinary or 当座 for current), the account number (口座番号), and the account holder name (口座名義). The account holder name in particular needs to be presented in the form the bank will match against, often in katakana for a transfer, and a mismatch here causes the transfer to fail at the customer's bank rather than at the invoice stage.

One detail worth noting: in a Japanese 振込, the customer usually pays the transfer fee, but who bears that fee (振込手数料) is sometimes specified on the invoice. Stating it removes a small but recurring source of payment friction.

Japanese Invoice Localization Checklist

Before/After Invoice Examples

Example 1: Registration Number

Example 2: Tax Line

Example 3: Recipient Field

Example 4: Document Label

Example 5: Bank Transfer Block

Frequently Asked Questions