Japan Delivery Note vs Invoice: When You Need Both

In Japan, a delivery note usually does not replace an invoice. The delivery note, often called a noshinsho, confirms what was delivered and received; the invoice requests payment. When a supplier makes several deliveries and bills at the end of the month, finance teams often keep both so billed amounts can be matched back to actual deliveries and supporting tax records.

Delivery notes and invoices often share supplier names, item descriptions, quantities, and dates, but they support different events: receipt or acceptance on one side, billing and payment review on the other. The distinction matters most when a Japanese supplier sends several delivery notes during the month and one summarized invoice later; AP should review the documents together instead of treating either one as complete in isolation.

What Each Document Does in the Japanese Receiving-to-Payment Flow

The delivery note belongs to the receiving side of the workflow. It travels with the goods or appears when the goods arrive, and it helps the buyer confirm what was sent, what was received, and what was accepted. If you need a refresher on what a delivery note does in receiving, that receiving function is the key reason the document continues to matter even when an invoice will follow later.

The invoice belongs to the billing side of the workflow. It states what amount the supplier is claiming, which billing period or transaction the claim relates to, and what the buyer needs to review before payment is approved. In other words, the invoice is not just another copy of delivery information. It is the payment request and accounting record that AP uses to post, approve, dispute, or pay the charge.

Because both documents can show item names, quantities, and dates, teams sometimes treat them as substitutes when they are not. That overlap is useful for matching, but AP still needs receiving evidence while finance needs the payment request.

The delivery note proves the delivery event; the invoice proves the billing event. For field-level details, use how to read Japanese invoices.

Why Japanese Suppliers May Bill Monthly After Multiple Deliveries

The easiest way to understand the Japanese delivery slip invoice system is to separate two common patterns.

• One delivery, one invoice: goods arrive, the buyer checks them, and the supplier issues an invoice tied to that single delivery.
• Multiple deliveries, one summarized invoice: goods arrive across several dates, each delivery has its own delivery note, and the supplier sends one invoice at the end of the billing period, often monthly.

The second pattern is where most of the confusion starts. In ongoing supplier relationships, shipments may move throughout the month while settlement happens on a periodic billing cycle. From the buyer's side, that means the invoice may represent a collection of deliveries rather than one handoff of goods. The later invoice is still the payment document, but it is no longer the only document that explains what happened during the period.

This pattern matters especially for foreign buyers who receive Japanese supplier paperwork in batches. A delivery note may show up first, with no immediate invoice attached. Weeks later, the invoice arrives and summarizes several earlier deliveries. Read in isolation, either document can look incomplete. Read together, they describe a normal commercial chain: delivery, acceptance, then billing. Japanese-speaking accounting teams handling this volume directly — supermarket and food-wholesale 経理 in particular — often need to consolidate stacks of paper, PDF, and EDI delivery notes into Excel at month-end; see 納品書・納品明細書のExcel一括取り込みと月締め経理の実務 for that workflow in Japanese.

When Keeping Both Documents Strengthens QIS-Era Tax Support

Under Japan's Qualified Invoice System, the practical question is not whether a delivery note turns into an invoice. The question is whether the invoice on its own carries enough detail to support review, matching, and tax treatment. In some cases it does. In others, the invoice points back to delivery records rather than fully repeating the underlying detail. A common version of that problem is a summarized invoice that refers back to delivery note numbers instead of restating each delivery's full item detail.

According to JP PINT's current summarized invoicing guidance, Japan's summarized invoicing process uses a delivery note with each delivery and a period-end invoice. When a summarized invoice refers to delivery-note details rather than carrying every required item itself, the buyer may need to retain both the invoice and the delivery notes to support input tax credit. That is the practical reason to keep the documents together instead of treating delivery notes as disposable after billing.

This is not a blanket rule that every Japanese transaction needs the same document set in the same form. It is a record-retention logic: when the invoice is summarized, abbreviated, or dependent on delivery references, AP may need the related delivery notes to show what goods were delivered, on which dates, in what quantities, and across which billing period.

For the wider rule set, review the guide to Japan Qualified Invoice System requirements. The narrower point here is that QIS-era support often depends on whether the invoice can stand on its own.

A Practical Check for Foreign Buyers and AP Teams

For day-to-day controls, the simplest rule is this: when one delivery has one fully detailed invoice, the delivery note mainly supports receiving and acceptance. When several deliveries are rolled into one summarized invoice, or when the invoice only points back to delivery references, retain and match the related delivery notes with the invoice.

That review should be concrete. Check the supplier identity, delivery dates, item or quantity references, signs of receiving or acceptance, the billing period on the invoice, and whether the invoiced amount can be tied back to the underlying deliveries.

• If the invoice stands on its own, the delivery note is still useful receiving evidence, but payment support is largely carried by the invoice.
• If the invoice summarizes several deliveries, the delivery notes help explain what is sitting inside that total.
• If the invoice refers back to delivery documents instead of restating detail, retaining both records is the safer documentation posture.

This sits inside broader invoice processing workflows. Receiving evidence, invoice review, payment approval, and retention should line up so the buyer is not approving a bill that cannot be traced back to actual deliveries.