How to Convert Japanese Delivery Notes to Excel

If you need to convert Japanese delivery notes to Excel, the first thing to get right is the document's role. A Japanese delivery note, or 納品書, is a receiving document rather than the invoice itself, so teams often extract it before AP processing starts. The spreadsheet usually needs item lines, quantities, delivery dates, supplier details, PO references, and optional price fields because some Japanese delivery notes include pricing and others do not.

The distinction matters in day-to-day work. The 納品書 confirms what was delivered, when it arrived, and which items or quantities need to be checked. The later invoice, or 請求書, is the billing document used for payment approval, coding, and settlement. If those two documents are treated as interchangeable, receiving logs become messy, discrepancy review slows down, and invoice matching starts from bad source data.

For most teams, the immediate goal is not "read the Japanese PDF." It is to turn a delivery document into usable rows that operations, receiving, or finance staff can sort, filter, and reconcile. That is why separate extraction makes sense before invoice matching or month-end summary billing enters the picture. The useful output is a spreadsheet that preserves the delivery note number, supplier, line items, quantities, dates, and any price data that happens to be present.

A common Japanese workflow makes the value easier to see: goods arrive with a 納品書, the receiving or AP team extracts the note into spreadsheet rows, discrepancies are checked against what was ordered and delivered, and only later is the 請求書 or a consolidated billing document matched back to those rows. That sequence is why delivery-note extraction deserves its own workflow instead of being folded into invoice entry.

A prompt-based document-to-spreadsheet workflow fits this job well because the operator can describe the exact fields and row structure needed without building templates or rules first. It creates a usable bridge between Japanese delivery paperwork and the controlled downstream review that AP teams actually need.

Build an Excel schema that works for priced and non-priced 納品書

The spreadsheet has to reflect how Japanese delivery notes are actually used, not just what text happens to appear on the page. In practice, the core columns are usually:

• Delivery note number
• Supplier name
• Delivery date
• PO or order reference
• Item name
• Quantity
• Unit
• Spec, size, or pack detail
• Unit price, if present
• Total amount, if present
• Notes or discrepancy flag
• Source file and page

OIST's supplier guidance for business partners in Japan lists delivery slip fields including date of issue, total amount, items, quantities, delivery date if different, unit price, contact information, and a breakdown. That is a useful reminder that a delivery note can carry both document-level and line-level information, and that the price fields are real fields when present rather than invoice-only concepts.

The important design choice is to treat price columns as optional, not mandatory. Some 納品書 are priced and can support early valuation or discrepancy checks. Others are pure delivery records that confirm what arrived but leave commercial values to the invoice stage. If the spreadsheet forces a value into every price column, reviewers end up guessing, overriding, or mixing delivery data with later billing data.

For that reason, line-item output is often more useful than one row per document. One line per item lets the spreadsheet preserve quantities, pack sizes, and product descriptions in a way that receiving teams can review directly. Document-level fields such as supplier name, delivery note number, and delivery date can simply repeat on each row. The result is easier to filter, audit, and match later.

The final columns, source file and page, do more than help with cleanup. They make the sheet trustworthy. When a quantity looks wrong or an item description seems truncated, AP or receiving staff can jump back to the exact page instead of searching through a stack of Japanese PDFs by hand.

The Japanese document details that trip up generic OCR

Japanese delivery notes are not hard only because they are in Japanese. They are hard because the language, layout, and document conventions all affect structure at the same time. A generic OCR pass might read the page, but that does not guarantee the output lands in clean spreadsheet columns.

Headers may appear in kanji, mixed scripts, or full-width characters. Supplier names can switch between legal entities, abbreviations, and branch labels. Stamps and seals may overlap nearby fields. Handwritten receiving marks can sit beside typed quantities. The same business fact, such as a delivery date or order reference, can appear in different parts of the page depending on the supplier's format.

For spreadsheet work, the real problem is field mapping rather than text capture. If a product spec slides into the item-name column, or a PO reference is mistaken for the delivery note number, the row may look complete while still being wrong enough to break receiving checks. The cleanup work then shifts from typing to detective work.

Layout variation is another common failure point. Some suppliers present tidy line tables, while others compress quantities, units, and remarks into narrow cells or uneven multi-line blocks. Full-width numerals and punctuation add another layer of inconsistency when the downstream spreadsheet needs standard dates, numeric quantities, and searchable references.

That is why "Japanese delivery note OCR" is only part of the job. The harder part is normalizing Japanese delivery-note fields into a stable schema that operations and finance teams can trust without manually re-reading every page.

Prompt the extraction around rows, dates, and page traceability

Once the schema is clear, the prompt should describe the spreadsheet you want, not just ask for text extraction. For Japanese delivery notes, that usually means telling the system to create one row per line item, repeat the delivery note number and supplier on each row, format dates consistently, and keep PO references, item descriptions, and quantity fields separate.

A useful prompt also explains how to treat optional fields. If unit price or total amount appears, extract it. If the delivery note has no pricing, leave those columns blank rather than forcing a zero or borrowing data from somewhere else on the page. That simple instruction protects the spreadsheet from mixing receiving data with later invoice data.

For example, a practical prompt might say: create one row per line item, repeat the delivery note number, supplier name, and delivery date on each row, format dates as YYYY-MM-DD, extract unit price and total only when they appear, and include the source file and page number for every row. The resulting sheet might have repeated document fields beside item-level columns, with blank price cells on non-priced 納品書 instead of guessed values.

Page traceability should be explicit as well. Ask for the source file and page number on every row so reviewers can verify ambiguous items quickly. If certain marks are not operationally useful, such as stamps, handwritten checks, or cover pages, say so in the prompt. If dates need to be normalized to YYYY-MM-DD, say that too. The more the prompt reflects the actual review workflow, the less cleanup the spreadsheet needs afterward.

A prompt-based tool such as Invoice Data Extraction becomes practical here because the operator can describe the row structure directly instead of setting up templates. The platform is built around a single prompt field and file upload area, its prompt controls support row-level instructions, column naming, page handling, and date formatting, and every output row can include the source file and page number for verification. That matters when Japanese layouts vary by supplier but the downstream Excel sheet still has to stay consistent.

Use the spreadsheet for receiving checks, discrepancy review, and invoice matching

Once the data is in Excel, the delivery note stops being a static attachment and becomes a working control record. Receiving teams can confirm whether the delivered quantities match what was expected, flag shortages or over-deliveries, and keep a clean record of which supplier document supports each receipt.

That separation becomes even more useful when the 納品書 does not include prices. In that case, the sheet still gives AP and operations a usable record of item lines, quantities, dates, and PO references while the commercial values arrive later on the invoice or month-end billing document. The delivery note is still doing a separate job, and the spreadsheet preserves that distinction.

From there, the rows can support discrepancy review and later reconciliation. If a supplier invoice shows a different quantity, product description, or reference number, the team can match delivery notes against supplier invoices without rebuilding the receiving history from scratch. When the billing stage begins, it also helps to read Japanese invoices and map the key fields against the delivery data that already exists.

In practice, this is where the broader value of invoice and financial document extraction becomes clear. Delivery notes, invoices, and related supplier documents are easier to control when each document type is extracted into structured data at the stage where it is actually used, rather than being treated as one undifferentiated stack of PDFs.

When a workflow-built extractor beats manual copy-paste or basic OCR

Manual entry can work for a small trickle of documents when the layouts are stable and the review stakes are low. A raw OCR pass can also be enough if the only goal is to make the page searchable. Neither approach is ideal when Japanese delivery notes vary by supplier, pricing may be absent, and the spreadsheet has to support receiving checks before invoice processing starts.

What teams usually need is not readable text but consistent structured output. If the same supplier uses multiple layouts, if line items need to stay intact, or if the team has to preserve source-page traceability for every row, then a workflow-built extractor starts to justify itself. At that point the job looks less like office admin and more like controlled data preparation for AP.

If your workflow is broader than Japan-specific documents, it also helps to understand how teams convert generic delivery note PDFs to Excel. The difference here is that Japanese document conventions add enough field-mapping and normalization work that the generic playbook often needs tighter instructions and more review discipline.

Invoice Data Extraction is a practical example when those workflow demands are already present. It converts financial documents into Excel, CSV, or JSON from a natural-language prompt, supports mixed batches of up to 6,000 files, can process single PDFs up to 5,000 pages, and supports major languages and scripts, including East Asian scripts. For teams handling mixed Japanese supplier layouts, optional pricing, line-item extraction, and later invoice matching, that kind of controlled output is usually the point where a workflow-built extractor becomes worth it.