5 Seikyusho (請求書) Entry
Errors That Trigger Consumption Tax Discrepancies

What follows are five seikyusho-specific data entry errors — errors that exist because a Japanese invoice carries fields that have no equivalent in a Western invoice, and because the manual step between the PDF and the spreadsheet creates a gap where none of these errors are visible until a payment fails, a tax return is questioned, or a monthly reconciliation refuses to balance.

Error 1: Wrong Consumption Tax Rate — When an 8% Item Lands in the 10% Column

What it looks like. You are processing a supplier invoice with mixed-rate line items — office supplies at 10% and packaged beverages for the break room at 8%. The AP clerk transcribing the invoice into the accounting system sees the total amount column and types it. The consumption tax breakdown — two separate subtotals, each with its own rate, each with its own tax amount — is entered as one aggregate number or, worse, everything goes into the 10% column because the person entering it does not recognise which items qualify for the reduced rate. The consumption tax return (消費税申告) is filed. Three months later, the reconciliation shows a discrepancy: the claimed input tax credit is higher than it should be, because 8% items were credited at 10%.

What actually happened. Japan's consumption tax system runs on two rates — 10% standard (7.8% national consumption tax plus 2.2% local consumption tax) and 8% reduced (6.24% national plus 1.76% local) — and they apply to different categories of goods. Under the reduced tax rate system (軽減税率制度, keigen zeiritsu seido) introduced in October 2019 alongside the rate increase from 8% to 10%, food and non-alcoholic beverages (excluding dining out and alcohol) and subscription newspapers issued at least twice weekly qualify for the 8% reduced rate. A standard office-supply invoice that happens to include packaged tea or coffee is a mixed-rate invoice — and the Qualified Invoice System (インボイス制度) requires that the taxable base and tax amount be stated separately for each rate category.

When an AP clerk manually entering a seikyusho classifies a reduced-rate item at the standard rate — or, more commonly, when the invoice has twenty line items and only two are reduced-rate, and the clerk consolidates everything into one tax column — two things happen. The input tax credit claimed on the consumption tax return is overstated by the difference between 10% and 8% on each misclassified item. On a single line item of ¥20,000, the overstatement is ¥400 (¥2,000 claimed at 10% instead of ¥1,600 at 8%). Across sixty invoices with an average of two misclassified reduced-rate items each, the annual overstatement can reach ¥576,000 — a number that the National Tax Agency's data-matching system treats as an underpayment, not a clerical error. The taxpayer owes the difference plus an understatement penalty (過少申告加算税, kashō shinkoku kasanzei) of 10% to 15% under the General Law of National Taxes (国税通則法).

The error also flows in the other direction. A food-service invoice where a 10% item — a catering service with on-site consumption — is mistakenly entered at 8% underclaims the input tax credit. The buyer pays more tax than required, which the NTA will happily accept, but the company's financial statements now carry an overstated tax expense and an understated net income. The error compounds because consumption tax accounting in Japan accrues the tax at the point of purchase, not the point of payment, so a misclassification in month one propagates into every subsequent month's beginning balance until corrected.

Error 2: インボイス登録番号 Missing or Invalid — When the T-Number Check Is Skipped

What it looks like. The supplier's invoice arrives with a T+13-digit registration number printed in the header. The AP clerk types it into the accounting system — T1234567890123. The purchase journal is posted. The consumption tax return is filed. Eighteen months later, during a tax audit, the auditor flags the transaction: the supplier's registration had been cancelled three months before the invoice date, the T-number is no longer valid, and the input tax credit of ¥150,000 claimed on that ¥1,500,000 invoice is disallowed. The company owes the ¥150,000 in back tax plus a 10% understatement penalty — ¥165,000 in total — because the T-number was transcribed correctly but never verified against the NTA registry.

What actually happened. The Qualified Invoice System (インボイス制度, officially 適格請求書等保存方式), effective since October 2023 under Article 57-2 of the Consumption Tax Act, requires that a buyer claiming input tax credit hold a qualified invoice (適格請求書, tekikaku seikyūsho) bearing a valid registration number. The NTA maintains a public registry of qualified invoice issuers (適格請求書発行事業者公表サイト) where anyone can search by registration number or business name to verify active status. A supplier's registration can be voluntarily cancelled, automatically revoked upon business closure, or expired without the buyer's knowledge. The Tokyo Chamber of Commerce and Industry (東京商工会議所) advises buyers to verify registration status at each transaction — not once at onboarding, but every time an invoice is received.

The manual entry workflow treats the T-number as a field to transcribe, not a field to verify. The clerk types it into the spreadsheet. The system accepts it. The audit trail shows the number was captured, but it does not show that the number was checked — and when the audit reveals that the number was invalid at the transaction date, "we typed it correctly" is not a defence. Under the transitional schedule, invoices from unregistered suppliers carry a reduced input tax credit: 80% deductible through September 2026, 50% through September 2029, then zero. If the AP team does not know which suppliers are registered and which are not — because no one is checking the registry — every invoice from a non-registered supplier is overstating the input tax credit by the gap between the transitional percentage and 100%.

The cost of not verifying compounds with supplier count. A company with 200 active suppliers where five registrations lapse in a year without the AP team noticing faces five years of disallowed credits on five suppliers' worth of invoices — and because consumption tax filings can be corrected retroactively for up to five years under the statute of limitations, the liability accumulates backward as well as forward.

Error 3: 振込先 Bank Details Typo — When One Wrong Digit Costs ¥880 to Undo

What it looks like. The furikomi block (振込先, furikomisaki) on the seikyusho reads: 三菱UFJ銀行, 新宿支店, 普通, 1234567, カ)ヤマダショウジ. The AP clerk types the branch code as 001 instead of 002 — a single-digit swap. The internet banking system accepts the transfer. ¥320,000 leaves the company's account. Ten days later, the supplier calls: the payment never arrived. The AP team traces the transfer, identifies the branch code error, and discovers the funds landed in an active account at a different branch — not a closed account that would have automatically rejected the transfer. The bank charges ¥880 for the kumimodoshi (組戻し) procedure. The supplier, now a month past their expected payment date, shortens the credit terms on the next purchase order from 翌月末払い to 翌月10日払い — a twenty-day reduction in the payment window that the procurement team did not negotiate and whose cost is not itemised on any invoice but appears as reduced working capital flexibility.

What actually happened. A Japanese invoice carries a payment instruction block that has no equivalent in Western invoice formats: four to five separate bank fields — bank name (銀行名), branch name (支店名), account type (口座種別 — 普通/ordinary or 当座/current), account number (口座番号), and account holder name (口座名義) — that the payer must transcribe into the internet banking screen character by character. These are the same four fields that already exist in the accounting software's supplier master, but the two systems — the invoice PDF and the banking portal — do not share a data pipe. The AP clerk retypes them for every invoice. A 1% character-level error rate — one mistyped digit or katakana character per hundred fields — produces approximately one incorrect transfer per thirty-three invoices, because each invoice carries roughly three bank detail fields (branch, account type, account number) plus the name field.

The kumimodoshi procedure is a bank-mediated fund recall that depends on the receiving account holder's consent. Mizuho Bank charges ¥880 (tax-inclusive) per request, and the fee is non-refundable even if the recipient refuses. SBI Shinsei Bank's published timeline warns the procedure may take two weeks to several months. The receiving bank contacts the unintended recipient, who must agree to return the funds — a consent that is not guaranteed. If the funds landed in a closed or dormant account, the transfer is automatically rejected and the money returns without a kumimodoshi fee. If the account is active, the procedure is manual, slow, and uncertain. Beyond the ¥880 fee, the staff time cost of tracing the transfer, contacting the bank, documenting the error, and processing a corrective payment is roughly one hour — approximately ¥3,000 in labour at a mid-range AP clerk rate in a Japanese city, making the total cost per furikomi error roughly ¥3,880.

Across 300 invoices per month at a 1% furikomi field error rate, the annual cost is approximately ¥139,680 in direct fees and labour — and that excludes the supplier relationship damage from repeated late payments, which tends to surface not as a line item but as tighter payment terms and higher prices in the next contract negotiation. The cost analysis of manual seikyūsho processing breaks down the four-layer cost structure — direct labour, furikomi errors, gensen choshu exposure, and invoice compliance — and quantifies why the furikomi error layer alone exceeds the annual cost of most accounting software subscriptions.

Error 4: 源泉徴収漏れ — When the Withholding That Should Have Been Deducted Becomes the Company's Tax Liability

What it looks like. A seikyusho arrives from a web design sole proprietor (個人事業主, kojin jigyōnushi) for ¥480,000. The invoice carries a line noting 源泉徴収あり — withholding applies. The AP clerk, processing forty other invoices in the same afternoon, categorises the payment as a standard service purchase rather than a withholding-eligible professional fee. The full ¥480,000 is paid to the designer. The 10.21% — ¥48,998 — that should have been withheld and remitted to the tax office is neither withheld nor remitted. Six months later, during the tax accountant's quarterly review, the missed withholding is discovered. The company now owes ¥48,998 in principal tax, plus a non-payment penalty (不納付加算税, funōfu kasanzei) of 10% (¥4,900), plus late payment interest (延滞税, entai zei) accruing daily from the original due date at the statutory rate — roughly ¥735 for six months at the current 3% annual rate under Article 404 of the Civil Code. Total exposure on a single missed withholding: ¥54,633. The supplier, who received the full amount, has no incentive to return the overpaid portion. The company now carries a tax liability for money it already paid to someone else.

What actually happened. Japan's withholding tax system (源泉徴収制度, gensen chōshū seido) under Article 204 of the Income Tax Act (所得税法) places a deduction obligation on the payer — not the payee — when the payment is for certain categories of professional service. The qualifying categories include lawyers (弁護士), certified public tax accountants (税理士), certified public accountants (公認会計士), judicial scriveners (司法書士), social insurance labour consultants (社会保険労務士), designers (デザイナー), writers (著作家), and several other professions defined in the NTA's withholding tax guide (源泉徴収のあらまし). The withholding rate is 10.21% (10% income tax plus a 2.1% reconstruction special surtax) on amounts up to ¥1,000,000 and 20.42% on the portion exceeding ¥1,000,000. The withheld amount must be remitted to the tax office by the 10th of the month following the payment.

Under the National Tax Collection Act (国税通則法), the withholding agent — the company making the payment — is jointly liable for the unremitted tax. The tax office does not pursue the supplier for the missing withholding. It pursues the payer who failed to deduct it. This creates an asymmetry: the AP clerk who missed the withholding has no personal liability, but the company they work for now owes the tax office ¥48,998 plus penalties for a payment it already made in full to the supplier — a 110% payment on a single invoice.

The error is structural. A manual AP process places the withholding decision — is this payment subject to 源泉徴収? — on a person reading the invoice description and matching it against their memory of which suppliers are withholding-eligible. The invoice itself may or may not clearly label the withholding status. Some designers include a separate 源泉徴収額 line; others note it in small text near the total; some do not mark it at all, and the obligation still applies. A 2% misclassification rate across 300 invoices per month means six missed withholds — and at an average withheld amount of ¥50,000 per qualifying invoice, the annual exposure including penalties reaches approximately ¥196,000. This cost is entirely invisible in the accounting software subscription because the software processes the payment the AP clerk enters — it does not flag that the clerk should have entered a different amount.

Error 5: 締日 Miscalculation — When the Settlement Day Lands the Expense in the Wrong Fiscal Period

What it looks like. An invoice dated March 22 arrives from a supplier whose payment terms read 20日締翌月末払い. The AP clerk, using the invoice date as the transaction date, books the expense to March — the current fiscal year, which closes on March 31. The supplier's year-end audit flags the discrepancy: under 20日締 terms, a March 22 invoice falls into the April billing period because the March billing cycle closed on March 20. The expense belongs to the next fiscal year. The company's March financial statements overstated expenses and understated net income. The quarterly consumption tax return attributed the input tax credit to the wrong reporting period. The auditor requests a correction to both sets of books — a multi-entry adjustment that cascades from the purchase journal through the consumption tax return to the financial statements.

What actually happened. The shimebi (締日, shimebi) system that governs Japanese payment terms is not a date-counting system like Net 30 — it is a calendar convention where each supplier defines a monthly closing day, and every transaction before that day belongs to the current billing cycle while every transaction after it belongs to the next. The payment terms string on the invoice — "20日締翌月末払い" — means the billing period closes on the 20th, and payment is due by the end of the following month. The invoice date of March 22 is two days after the March cycle closed. The transaction belongs to the April cycle, with payment due at the end of May. The AP clerk who used the invoice date as the posting date without checking the settlement day shifted the expense by one full fiscal period.

The settlement day determines more than the payment due date. It determines the fiscal-year classification of the expense — and that classification cascades into three separate reporting systems. The purchase journal records the expense in the wrong month. The consumption tax return (消費税申告) attributes the input tax credit to the wrong reporting period — and under Japan's consumption tax filing rules, the return is due within two months of the fiscal year-end, with no extension. A corrected return filed after the deadline carries a late filing penalty (無申告加算税, mushinkoku kasanzei) of 15% to 20% of the additional tax due. The financial statements presented to the bank or shareholders carry an expense that belongs in a different reporting period, which, for a March fiscal-year-end company, means the auditor must identify and correct the misclassification before signing off.

The shimebi miscalculation is the hardest of the five errors to catch because the invoice date and the settlement day are often close — a March 18 invoice under 20日締 terms belongs to March; a March 22 invoice under the same terms belongs to April. Looking at the calendar, both dates feel like March. Only the payment terms string — 20日締 — distinguishes one from the other, and the payment terms string is the field most likely to be overlooked during manual entry because it is not a number the AP clerk needs to type for the payment. It is a text annotation, read once and mentally parsed, and the result of that parsing — "belongs to April" — is never recorded anywhere except as the implicit consequence of the posting date chosen.

This is not a Japanese quirk — it is a direct consequence of a billing system where payment terms encode two computable values (settlement day and payment lag) inside a compound text string, and the manual entry workflow extracts neither of them as structured data. The shimebi payment deadline analysis covers the full operational impact: thirty suppliers with different settlement-day conventions create a cash-flow forecasting problem that a payment calendar cannot solve without structured settlement-day data from the invoice. The same gap between the payment terms on the PDF and the posting date in the ERP drives the PO-to-delivery-to-invoice matching bottleneck on the procurement side: a three-way match needs the three documents to agree on fiscal period, and the period is determined by the settlement day embedded in the payment terms string.

How to Catch These Five Errors Before They Compound — Three Measures That Work on Every Invoice

These five errors share a common architecture. Each one originates in the gap between a seikyusho PDF and the spreadsheet or accounting screen where its data is entered — and each one is invisible at the point of entry. The wrong consumption tax rate looks like a number in a column. The unverified T-number looks like a correctly transcribed string. The mistyped furikomi branch code looks like a valid code — the bank does not reject it, it sends the money somewhere else. The missed gensen choshu withholding produces a payment amount that looks correct because the full amount was transferred. The wrong settlement day produces a posting date that looks plausible because March 22 is close to March 20. None of these errors trigger an immediate error message. They surface downstream — in a bank reconciliation, a tax return review, or an audit — by which point the data that would diagnose them has already been buried under the next month's batch of invoices.

Three measures prevent all five errors — not by making the manual entry process more careful, but by moving the data capture upstream of the keyboard.

For anyone processing seikyusho at scale — thirty to three hundred invoices per monthly settlement cycle, from suppliers who each use a different billing system with a different invoice layout — these three measures shift the AP team's role from data creation to data verification. The spreadsheet arrives populated. The AP clerk scans for flagged items — a T-number that the registry did not recognise, a tax rate classification that looks questionable, a payment term that was parsed incorrectly because the supplier used an unusual syntax. Verification takes minutes per batch. Manual entry — opening each of sixty invoice PDFs, reading the furikomi block, classifying the consumption tax rates, checking the withholding status, parsing the payment terms, and typing everything into a different screen — takes hours and produces the five errors above at a rate proportional to invoice volume and time pressure. The same approach applies to related document types that share extraction logic with seikyusho: the common Japanese passbook (通帳) data entry mistakes share the same architecture — errors that are invisible at the point of manual entry and compound across rows until a reconciliation refuses to balance.

FAQ: Seikyusho Data Entry Errors and Consumption Tax

How do I know whether a line item qualifies for the 8% reduced consumption tax rate?

The reduced rate applies to food and non-alcoholic beverages (beverages with less than 1% alcohol) sold for home consumption — not dining out — and to subscription newspapers published at least twice weekly. The key distinction is between take-home food (8%) and on-site consumption (10%). A supermarket bento purchased for home is 8%; the same bento eaten at the store's eat-in corner is 10% because it qualifies as dining out. Alcoholic beverages (1% alcohol or above) are always 10% regardless of where they are consumed. Seasonings like mirin and cooking sake — items with less than 1% alcohol or rendered non-potable — qualify for 8%. If the line item description is ambiguous, the supplier's invoice should separately state the reduced-rate items and their totals. If it does not, and the supplier is a qualified invoice issuer, the invoice is technically non-compliant under the Qualified Invoice System — the buyer should request a corrected invoice or accept the transitional input tax credit reduction.

How often should I verify supplier registration numbers against the NTA registry?

The Tokyo Chamber of Commerce and Industry recommends verification at each transaction — meaning every time an invoice is received, not just once during supplier onboarding. In practice, for a company with 200 active suppliers processing monthly invoices, a monthly batch verification against the NTA registry (ten numbers per query, approximately forty minutes per session) is the minimum prudential standard. A supplier's registration can be cancelled at any time — voluntarily upon business closure, or automatically when tax status changes — and the buyer receives no automatic notification. The NTA public registry at invoice-kohyo.nta.go.jp is the authoritative source. If a number returns no result or a mismatched business name, the invoice cannot support a full input tax credit claim.

Can a furikomi sent to the wrong account always be recovered?

No. The kumimodoshi (組戻し) procedure requires the receiving bank to contact the unintended recipient and obtain their consent to return the funds. If the recipient refuses — or if the contact attempt fails because the account holder cannot be reached — the funds are not returned, and the ¥880 request fee is still charged. The only guaranteed recovery scenario is when the receiving account number does not exist or has been closed, in which case the transfer is automatically rejected and the funds return without a kumimodoshi procedure. For active accounts, recovery depends entirely on the recipient's cooperation. This is why the furikomi error is not a clerical inconvenience — it is a funds-at-risk event. The best prevention is eliminating the typing step: extracting the bank details from the invoice image means the digits come from the document, not from a person reading and retyping.

How do I determine whether a supplier's invoice is subject to gensen choshu withholding?

The withholding obligation is determined by the nature of the payment, not by a field on the invoice. If the payment is for professional services rendered by a qualifying category — lawyers (弁護士), certified public tax accountants (税理士), certified public accountants (公認会計士), judicial scriveners (司法書士), social insurance labour consultants (社会保険労務士), designers (デザイナー), writers (著作家), and certain other categories listed in the NTA's withholding tax guide — and the payee is an individual or sole proprietor (not a corporation), the payer must withhold 10.21% and remit it to the tax office. The invoice may or may not indicate the withholding status. Some suppliers include a separate 源泉徴収額 line; others note it in small text; some do not mark it at all. The obligation exists regardless of whether the invoice labels it. For a detailed treatment of how withholding interacts with the payment calculation and the tax deposit schedule, see the complete guide to Japanese invoice extraction, which covers the full gensen choshu workflow from invoice classification through payment batch adjustment to tax deposit booking.

What happens when thirty suppliers each use a different shimebi day?

The AP team is managing thirty different fiscal-period classification rules simultaneously — one per supplier — and the rules must be applied to every invoice individually because the settlement day is embedded in the payment terms text string, not in a database field that the accounting system can query. An invoice dated the 18th under 15日締 terms belongs to the following month. The same invoice date under 20日締 terms belongs to the current month. The same date, the same amount, two different fiscal periods — and the AP clerk must know which supplier uses which settlement day to post the expense to the correct period. The shimebi payment deadline problem analysis covers the full cascade: how thirty different settlement days create thirty different payment calendars, why the spreadsheet cannot solve the problem because it cannot read the payment terms off the invoice, and how parsing the settlement day into structured data during extraction turns thirty manual calendar calculations into one formula.

Can Japanese accounting software catch these errors automatically?

No — and this is the structural limitation that makes these errors persistent. Accounting software — 弥生会計 (Yayoi), freee, マネーフォワード クラウド会計 (MoneyForward Cloud), 勘定奉行 (Kanjo Bugyo) — automates journal entries for transactions it can match to a bank feed. It checks arithmetic: does the debit equal the credit? It does not check whether the consumption tax rate on line item 14 should have been 8% instead of 10%, because the software processed the number the AP clerk entered — it has no access to the original invoice to compare against. It does not verify that the supplier's T-number is still active on the NTA registry, because the registry check is an external lookup the software does not perform automatically. It does not flag a missed gensen choshu withholding, because the withholding decision is based on the nature of the payment — information that lives on the invoice, not in the accounting software's chart of accounts. The software processes the data it receives. If the data entering the software carries the five errors above, the software faithfully propagates them into the purchase journal, the consumption tax return, and the financial statements. The fix is upstream of the software — at the point where data moves from the invoice PDF into structured form. For the complete workflow from extraction through accounting software import, the how-to guide for extracting Japanese invoice data to Excel covers the pipeline: defined columns → batch extraction → structured spreadsheet → import into Yayoi, freee, or MoneyForward Cloud.

The Error You Cannot See Until the Reconciliation Refuses to Balance

The five errors on this page share one property that makes them harder to catch than a simple typo: they are invisible at the point of entry. A mistyped furikomi branch code does not trigger a validation error — the bank accepts the transfer and sends the money. A misclassified consumption tax rate does not produce a mismatch at the point of entry — the number in the cell looks like a number, and the mismatch surfaces only when the consumption tax return's rate-grouped totals disagree with the supplier's stated breakdown. A skipped gensen choshu withholding produces a payment amount that looks correct — the full invoice total was paid — and the error is discovered only when the tax office asks why the withholding was not remitted. A wrong settlement day produces a posting date that is close enough to the correct date that the discrepancy is not obvious until the fiscal-year financial statements are being reviewed.

The manual entry workflow depends on a person noticing all five of these potential errors across sixty invoices in an afternoon — and the errors that go unnoticed are the ones that compound. The extraction workflow makes them visible by producing structured data from the document at the point of capture and applying Computed Columns that enforce the rules — the tax rate classification, the withholding flag, the settlement day parsing, the registry verification — that manual entry skips under time pressure. The AP team's job shifts from creating data and hoping it is correct to verifying data and correcting the outliers. The gap between "hoping" and "verifying" is the difference between finding a ¥48,998 gensen choshu error six months later during a tax review and catching it the moment the column flags "Withholding Required: Yes" on a supplier the clerk almost categorised as a standard purchase. For the complete field-by-field breakdown of every column that a Japanese invoice extraction workflow should capture — and how Computed and Inferred Columns handle the five errors above automatically — the complete guide to Japanese invoice data extraction covers the full schema in detail.