E-Bookkeeping Law Compliance: A Practical Guide for SMEs

Japan's Electronic Bookkeeping Law (denchoho) sets out how businesses must retain records required for tax purposes. Since the 2022 revision, the most consequential change for SMEs has been the mandatory electronic retention of electronic-transaction data — a requirement that owners and non-IT staff alike need to understand, not just the accounting team. This article sorts out what is actually mandatory versus optional, then walks through practical approaches, rough cost ranges, common mistakes, and a pre-implementation checklist. Because the fine print of this law changes from year to year, always verify the current details in the National Tax Agency's latest FAQ and guidance before acting.

The law covers three broad retention methods: electronic-transaction data storage, scanner-based storage, and electronic storage of self-prepared ledgers. Of these, SMEs are only required to comply with electronic-transaction data storage. Scanner storage (digitizing paper invoices and receipts) and electronic ledger storage (keeping accounting-software ledgers as data rather than printing them) are both optional — a business can keep using paper for those without issue. In short, the one hard requirement is that data received as an electronic transaction must be kept as electronic data; there is no need to digitize everything else just because the law exists.

An electronic transaction is any transaction where the underlying information is exchanged as electronic data. Common examples include PDF invoices attached to email, receipts issued for download from a website, order and shipment data exchanged through EDI systems, and data issued or received through cloud invoicing or cloud expense-management services. By contrast, a paper invoice that is filed as-is, or a document printed out from a fax, is not considered an electronic transaction. Where the line falls can be unclear in some cases; a useful test is whether the exchange with the counterparty began and ended entirely as electronic data.

Retained electronic-transaction data is generally understood to need two things. The first is authenticity — assurance that the data has not been altered after the fact. Accepted approaches include attaching a timestamp, using a system that records a history of any correction or deletion, or, where no such system is used, establishing and following in-house rules for preventing unauthorized correction or deletion of electronic-transaction data. Many SMEs choose the last option, since it requires no software spend — just a written policy. The National Tax Agency publishes a template for this policy, which is a practical starting point to adapt for your own operations.

The second requirement is visibility — the ability to promptly locate and display stored data if a tax audit occurs. This generally breaks down into three elements: keeping a computer, display, and printer available at the storage location so records can be shown on screen or printed in a readable format; keeping a system-overview document on hand if the storage system was built in-house; and being able to search records by transaction date, transaction amount, and counterparty. Search requirements may be relaxed or waived where a business can respond to a tax official's request to download the data, or where its revenue for the relevant period falls under a certain threshold. Because these thresholds and conditions can change, confirm whether your business qualifies against the latest official guidance.

SMEs generally take one of three approaches.

- Approach 1 — file-naming rules plus an internal policy: standardize PDF file names (for example, date, counterparty, amount) and organize them into folders. System cost is close to zero, but naming and filing is done manually, so the workload grows as transaction volume increases.
- Approach 2 — turn on e-bookkeeping features already built into your accounting or invoicing system: many cloud accounting and invoicing services now include search and timestamp functionality that can simply be enabled. Rough monthly cost: on the order of a few thousand yen to about 20,000 yen.
- Approach 3 — adopt a dedicated document-management or e-bookkeeping compliance service: worth considering when transaction volume is high, multiple staff are involved, or you also want to move toward scanner storage or electronic ledgers later. Rough cost: an initial fee on the order of 100,000 to 300,000 yen, plus a monthly fee on the order of 10,000 to 50,000 yen.

Which approach fits best depends on transaction volume, staffing, and how well existing systems already support the requirements. A practical, staged path is to start with Approach 1, watch how transaction volume evolves, and move to Approach 2 or 3 once the manual workload becomes a real burden.

Over the years, the law has included various leniency and grace-period measures for businesses that struggle to comply, and there has also been discussion around penalties or risks such as the revocation of blue-return tax status for records that consistently fail to meet requirements. However, the details of these measures are revised regularly through annual tax reforms, so information current at the time of writing should not be treated as a fixed fact. Whether a grace period applies to your business, and what actually happens if requirements are not met, should be confirmed against the National Tax Agency's latest FAQ and guidance, or with your tax accountant.

- Assuming printing and filing on paper satisfies the requirement: printing out electronic-transaction data and storing the paper copy is generally understood not to meet the requirement — the data itself must be retained electronically.
- Folder structures that don't actually meet the search requirement: inconsistent file names and scattered storage locations that can't be searched by transaction date, amount, and counterparty.
- Compliance knowledge locked in one person's head: internal policies and operating rules are never written down, so operations stall when that staff member is transferred or leaves.
- No backup in place: no plan for what happens if the PC or cloud service holding the data is damaged or its subscription is cancelled, risking permanent data loss.

The starting point for compliance is a simple inventory: identify every electronic transaction your business handles, and understand clearly that the only hard requirement is retaining that data electronically. From there, choose an approach — 1, 2, or 3 — that fits your scale and transaction volume while meeting the authenticity and visibility requirements. Because the details of this law change over time, always confirm the latest information from the National Tax Agency and consult your tax accountant on anything unclear. For related reading, see The hidden gaps in invoice-system compliance on overlooked compliance risks, Practical AI use cases in accounting work on streamlining day-to-day accounting, and Cloud backup and disaster recovery on protecting against data loss.