The Tokyo Café Owner Who Runs Her Business in Japanese But Invoices Tourists in English

By the InvoiceFlow team — published 26 May 2026 — 10 minute read

The first time we visited Yuki Tanaka's café in Shimokitazawa, the menu was in three scripts: kanji, hiragana, and small italic English subtitles. The chalk board out front was Japanese only. The Instagram feed alternated. The receipt printer behind the counter produced thermal slips in Japanese for locals and slightly different ones in English for tourists. It was the most carefully bilingual small business we had ever seen.

Yuki opened the café — a 14-seat third-wave coffee shop with a tiny menu of single-origin pour-overs and one obsessively researched cheesecake — three years ago. She runs it alone, with one part-time barista on weekends. Her clientele is roughly 60% locals, 30% Japanese tourists from outside Tokyo, and 10% international visitors who found her on a coffee-focused travel blog.

That last 10% is the reason this story exists.

Why a café needs invoicing software

If your only customers walk in, pay with a card, and walk out, you don't need invoicing. You need a point-of-sale system. Yuki had one of those — a small tablet-based register — and it handled day-to-day transactions fine.

But she also did three other things:

All three required actual invoices. PDF, line items, tax breakdowns, payment terms. And depending on who was receiving the invoice, the language had to be different.

The translation tax

Before switching to InvoiceFlow, Yuki's bilingual invoicing setup looked like this: she maintained two parallel invoice templates in a word processor. One in Japanese. One in English. Every time she created an invoice for an international client, she had to remember which template to start from, then manually translate any custom line items. Her English was good but not native; she lost about 20-30 minutes per invoice second-guessing word choices.

"I would write 'cheesecake' and then panic about whether I should say 'cake' or 'dessert' or what the wholesale word was," she told us. "Every invoice took longer than the actual work."

The bigger problem was consistency. The two templates drifted apart. Her Japanese template had her bank details in the bottom right; her English template had them in the bottom left. Her Japanese invoices used the 元号 (Reiwa era) date format; her English ones used Western. Numbers were styled differently. Addresses were ordered differently — Japanese addresses start with the largest unit (prefecture) and end with the building, while English addresses go the opposite way. By the time she'd been running parallel templates for two years, they looked like documents from two different businesses.

The locale-aware invoicing setup

The single feature that mattered most for Yuki was per-invoice locale selection independent of the app's UI language. This is one of those features that sounds technical and is actually about saving 20 minutes a day.

How it works

The app's interface is in Japanese — every menu, button, and tooltip Yuki interacts with is in her native language. She doesn't have to read English to use the software. But when she creates a new invoice, she can set the invoice's locale separately. For a local client, she picks Japanese. The resulting PDF has Japanese labels (請求書, 合計, 振込先), Japanese date format, Japanese number formatting, and the Japanese-conventional address order. For an international client, she picks English. The PDF has English labels (Invoice, Total, Bank details), ISO date format, comma-separated numbers, and Western-ordered addresses.

She doesn't switch the app's language. She doesn't maintain two templates. She picks once per invoice. Everything else is automatic.

Product names that translate themselves

For the wholesale bean business, she stored each product with both a Japanese name and an English name. When she invoices a local restaurant, the line item reads "エチオピア イルガチェフェ ナチュラル 250g". When she invoices the wholesaler in Singapore, the same product reads "Ethiopia Yirgacheffe Natural 250g". Same SKU, same price, two display names. No manual translation per invoice.

Mixed-script addresses

The trickier feature is what the app does with addresses. Japan has 47 prefectures and a unique address-numbering system that doesn't map cleanly to Western conventions. When Yuki's English-locale invoice prints her business address, the app uses a romanized version: "1-2-3 Kitazawa, Setagaya-ku, Tokyo 155-0031, Japan". When her Japanese-locale invoice prints the same address, it shows "〒155-0031 東京都世田谷区北沢1-2-3". Both are correct. Both come from the same stored record. She didn't have to type the address twice.

This works because the country-picker stores both the script-appropriate and the Latin-script version of the country and city, and the address-hints library knows the conventional ordering for each. The PDF renderer picks the right script based on the invoice's locale.

The tax-rate question

Japan has a 10% consumption tax (消費税) with a reduced 8% rate for certain food items. Yuki's bean sales — when consumed off-premises — qualify for the 8% rate; her catering — when consumed on site — is taxed at 10%. Her invoicing app needs to handle both, label them correctly in both languages, and produce the breakdown her tax accountant requires.

Per-line-item tax rates handle the math. The locale handles the labeling. On a Japanese invoice, the tax line reads "消費税 (8%)" or "消費税 (10%)" with the appropriate Japanese formatting. On an English invoice, the same line reads "Consumption tax (8%)" or "Consumption tax (10%)". Identical data, language-appropriate labels.

What changed for Yuki's business

The headline change was time. She estimates she now spends 6-8 minutes on an invoice that used to take 25-35. With roughly 18 invoices per month between wholesale and catering, that is about 5 hours of recovered time monthly — time she now spends on actual coffee work or, occasionally, doing nothing, which she correctly identifies as the most underrated form of business growth.

Fewer mistakes

The translation-anxiety errors stopped. She doesn't second-guess vocabulary because the stored product names are pre-translated and consistent. Her wholesale clients in Singapore and Germany have started commenting positively on how professional her invoices look — which is partly the templates and partly the absence of weird literal translations like "cake from cheese" that used to slip through.

Faster payment from international clients

One of the unexpected effects: her German wholesale client used to take 35-45 days to pay because invoices would get questioned by their accounts payable department over formatting issues. Now they pay in 18-22 days. The accounts payable team simply processes them faster because they look like invoices accounts payable teams expect to see.

The broader lesson for international-facing local businesses

If you run a business in a non-English-speaking country and any meaningful portion of your customers are foreign, you face this problem. Your books are in your local language. Your local invoices need to be in your local language for tax purposes. Some of your customer-facing documents need to be in English (or another second language) for the recipients to actually use them.

The wrong solution is to switch your entire workflow to English. You lose speed, lose accuracy, and create a confused setup where your accountant doesn't understand half your records.

The right solution is to separate the language you work in from the language any given output document uses. Your app interface stays in your language. Your records stay in your language. Individual invoices, quotes, or contracts can be flipped to a different output locale on demand.

What to look for

One last detail

Yuki's most-loved feature is so small it's almost embarrassing. The invoice file naming. When she emails a Japanese invoice, the file is named with the Japanese client name and the Japanese date format. When she emails an English invoice, the file is named with the romanized client name and the ISO date. Her German wholesale client's filing system can sort her invoices chronologically. Her Japanese restaurant client's filing system can sort hers. Both happen automatically.

"It's the kind of thing nobody notices when it's right," she said. "And everyone notices when it's wrong."

This is, arguably, the entire principle of good invoicing software in one sentence.