A tax payment certificate was requested through Japan’s e-Tax system.
The response was essentially:
“Could not be issued. Please contact the office you applied to for details.”
Fine. Then put the contact information on the screen.
The page had room for the user ID, receipt number, submission time and the name of the tax office. The two pieces of information that actually mattered next—why it failed and how to call the office—were missing.
So the system had enough context to identify the case, but delegated the final debugging step to the taxpayer.
A phone call produced the punch line: in this case, the application itself was not the problem. The tax office said the processing had failed because of a system-side error.
1. What was being requested?
The document was a Type 3-2 tax payment certificate for an individual.
It certifies that there are no unpaid amounts for income tax and special income tax for reconstruction, and for consumption tax and local consumption tax.
This was not a request to recalculate a complicated tax return. It was basically a request for official confirmation that the relevant taxes were not outstanding.
Yet the online result was simply “could not be issued.”
Without an explanation, a normal user has to guess:
Was the form wrong? Is there an unpaid tax balance? Was an attachment missing? Was the applicant ineligible? Did I break something?
In this case, no. The office explained by phone that a system error had prevented processing and generated the failure notice.
The human starts debugging themselves because the software refuses to say that the software fell over.
2. The timing matters: this happened immediately after a major national tax-system migration
This is where the story becomes more than a single annoying screen.
Japan’s National Tax Agency says it replaced its national tax system on September 24, 2026.
An official notice issued that day said there were problems with systems required for tax-office counter operations. It specifically listed delays in issuing tax payment certificates and said that certificates could not be issued immediately even when requested through e-Tax. Electronic tax payment certificates were temporarily not being issued.
On September 25, the agency reported that some e-Tax functions had become unavailable. On September 28, it separately announced a defect affecting recognition of an e-Tax software update released on September 24.
That does not prove that every one of these incidents had the same technical root cause as this particular failed certificate request.
But it does establish the surrounding context: the request occurred immediately after a major system migration during a period when the agency itself was publicly reporting multiple operational problems.
As of the fact check on September 29, the e-Tax front page was still displaying the tax-office counter delay notice as an emergency announcement.
The computers were having a rough week. Ironically, the physical counter was reportedly not especially crowded at the time of the phone call.
3. The fastest fallback became: come to the tax office
After the cause was checked by phone, the practical answer was simple: if the certificate was still needed, visit the competent tax office.
For this specific case, the staff member advised bringing:
- a driver’s license for identification;
- a ¥400 revenue stamp for one copy.
The caller was also told that buying the ¥400 revenue stamp in advance at a post office would make the visit smoother.
So an online process designed to avoid a trip ended with a very reliable disaster-recovery strategy: paper, identification and a physical counter.
Sometimes the strongest failover architecture is a building with humans in it.
3.1. Then the actual visit produced another twist: first in line
On arrival at the tax office, there was nobody ahead at the counter. The visit started with a zero-person queue.
Given the official warnings about counter delays immediately after the large system migration, some waiting had seemed reasonable. Instead, at least at that moment, there was no line at all and the process looked likely to finish much faster than expected.
The online route had required a failure notice, a search for contact information and a phone call. The physical fallback, meanwhile, went straight to the counter. For once, the human queue was shorter than the digital one.
The purpose of the certificate in this case was Meta business verification. For the purpose field, the practical approach was simply to state the concrete use: verification of the business or operator for submission to Meta.
4. Do not generalize “driver’s license plus ¥400” into a nationwide rule
This distinction matters.
The driver’s-license-and-stamp instruction was case-specific advice from the tax office.
For a general paper request submitted at a tax-office counter, the National Tax Agency lists the following items:
- a completed application for a tax payment certificate;
- the applicable fee, paid in cash or with a revenue stamp;
- a My Number Card; or, if the person does not have one, identity verification documents plus a document confirming the My Number;
- a power of attorney when a representative applies.
So “just bring a driver’s license” should not be treated as universal guidance.
The office may have been able to simplify the individual instructions because it already had the e-Tax request and case information in front of it.
Before visiting, confirm the required documents with the tax office that will actually issue the certificate.
5. The ¥400 versus ¥370 trap
There is another easy source of confusion: both prices are correct.
Under the current official guidance for Type 3 and Type 4 certificates, including Type 3-2 and Type 3-3:
- an e-Tax request costs ¥370 per paper copy;
- a fresh paper request made at a tax-office counter costs ¥400 per copy.
So memorizing only “Type 3-2 costs ¥400” is wrong, and memorizing only “it costs ¥370” is also wrong.
The fee depends on the application route.
In a situation like this, where the online route has failed and the applicant switches to a fresh paper counter request, the relevant fee is ¥400 per copy.
If a revenue stamp is used, do not cancel or mark it yourself. The National Tax Agency explicitly says that a cancelled stamp is invalid.
A tiny piece of paper worth ¥400 becomes worth nothing if you helpfully stamp it yourself. Leave it alone.
6. The worst part was not the outage. It was the error message
Systems fail. Large migrations fail. Zero incidents is not a realistic standard.
The real design question is what the system tells the user after failure.
At minimum, this screen should have provided four things:
- A cause category: user-input problem or system-processing problem.
- A next action: retry, wait, call the office, or use a counter fallback.
- Contact information: if the system can display the responsible tax office, it can also display a phone number or a direct contact link.
- A link to current incident information: especially during a known migration-related disruption.
Instead, the message effectively said:
“It failed. We are not telling you why. Please investigate by telephone.”
That converts a backend incident into unpaid frontend labor for the user.
7. What to do if you see the same message
Do not immediately assume you made an error.
Call the tax office shown as the destination of the request and keep the receipt information displayed in e-Tax available so the staff can identify the case.
If the office confirms a system-side error, repeatedly submitting the same request may be less useful than switching to a counter request.
Before visiting, confirm exactly what to bring. The general official rule for a paper counter request includes the application form, the fee, and My Number/identity documentation. Case-specific instructions may differ depending on what the office can already verify.
For Type 3-series certificates, a fresh paper counter request is ¥400 per copy. If the office suggests preparing a revenue stamp in advance, buy it and bring it unused.
During periods of major maintenance or migration, check current National Tax Agency incident notices before leaving home.
8. Conclusion: failures happen. “Contact us” without contact information is optional suffering
The sequence was:
online request; failure notice; no cause; manual search for the office; phone call; “it was a system error”; counter fallback; identification and fee; physical visit.
The actual fix was not re-entering the application. It was one phone call.
And in this case, that call took place against a documented background of a major national tax-system migration and publicly acknowledged problems with tax-certificate issuance.
The lesson is not “never use e-Tax.” Online requests are usually the more convenient and cheaper route.
The lesson is much simpler:
If your system already knows which office owns the request, show the user how to contact that office. If the failure is on the system side, say so.
If you can display a long receipt number, you can fit a phone number on the same screen.
Official source notes
- National Tax Agency: procedures for requesting tax payment certificates
https://www.nta.go.jp/taxes/nozei/nozei-shomei/01.htm - e-Tax: requesting tax payment certificates
https://www.e-tax.nta.go.jp/tetsuzuki/shomei_index.htm - National Tax Agency: delays in tax-office counter procedures
https://www.nta.go.jp/files/000041014.pdf - e-Tax: temporary unavailability of some e-Tax functions
https://www.e-tax.nta.go.jp/topics/2026/topics_20260925_mentenansu.htm - e-Tax: software defect and corrective update
https://www.e-tax.nta.go.jp/topics/2026/topics_20260928_e-taxsoft.htm - National Tax Agency: national tax-system replacement
https://www.nta.go.jp/taxes/shiraberu/sodan/system.htm
Personal identifiers, receipt numbers, the specific tax office, address, telephone number and name have been removed. The statement that this case was a system error comes from the taxpayer’s direct phone confirmation with the tax office. The article does not claim that the specific failure had the same technical root cause as the separately published national incidents. Case-specific instructions and the agency’s general document requirements are kept distinct.
