Group monthly charges without hiding separate orders
Check whether your buyer accepts monthly consolidation, keep each project and order traceable, and exclude charges already invoiced.
What happened
You complete several small projects for a Japanese client and want to send one invoice at month end. The same contact commissioned them, but the order references differ. A neat total on your side is not enough to show which buying entity owes which charge or whether its invoice process accepts the combination.
This guide uses a fictional monthly register: project A costs USD 300, B costs USD 450 and C costs USD 250. They belong to the same purchasing entity and add to USD 1,000. Project D costs USD 200 but belongs to another entity, so it stays outside that proposed invoice even if the contact person is the same.
The useful output is the register, whether or not consolidation is allowed. It can produce one approved invoice or several separate invoices without losing the original lines. A document, spreadsheet or your existing invoice software can hold it; a new service is not required.
What’s going on on the Japanese side
Confirm that the buyer accepts one consolidated invoice
Ask accounts payable (AP), the team processing the buyer’s invoices, whether it accepts the proposed combination. Specify the purchasing entity, supplier identity, service period, currency and each PO, meaning purchase order, with its line reference. Ask whether one invoice can contain several orders or whether each PO requires a separate document.
Astellas’s published instructions ask suppliers to reference its PO number and the matching PO lines being invoiced. It says mismatches can delay processing and approval. This is one company’s matching requirement, not permission to put several POs on one invoice or a rule for every Japanese buyer. (Source)
Separate the confirmation of format from the underlying payment terms. A monthly submission arrangement does not by itself settle when payment is due. Record any proposed change to the timing and resolve conflicting terms or applicable legal requirements instead of treating AP’s cutoff as a new contractual deadline.
Group only charges with compatible billing identities and currency
Use the purchasing legal entity, issuing supplier, currency and compatible billing terms as screening fields. Confirm the buyer identity from the accepted order or contract, rather than an email signature or brand name. A shared contact, company group or office address does not establish that the charges belong on the same invoice.
Even matching fields do not prove consolidation is allowed. Different tax treatment, payment terms, submission channels or cutoff dates may need separate handling; ask the appropriate accounting contact about the actual documents. Keep different currencies in separate subtotals until an explicit, agreed conversion basis has been established.
What to do next
Preserve a traceable line for each project and order
- Create a register before preparing the invoice. The following November 2026 example assumes the same issuing supplier, USD amounts on a common basis, and no tax, expense or exchange adjustments. Buyer Entity One and Buyer Entity Two are fictional labels. None of the amounts or order numbers represents a real transaction.
| Project / service period | Purchasing entity | PO and line | Previously invoiced for this charge | Candidate amount |
|---|---|---|---|---|
| A / 2–6 November | Entity One | PO-A, line 1 | None found; verify register | USD 300 |
| B / 9–13 November | Entity One | PO-B, line 2 | None found; verify register | USD 450 |
| C / 16–20 November | Entity One | PO-C, line 1 | None found; verify register | USD 250 |
| D / 9–13 November | Entity Two | PO-D, line 1 | None found; verify register | USD 200, excluded from Entity One |
- Verify each candidate’s billing evidence. Keep the agreed description, service period, quantity or unit basis where relevant, amount and supporting delivery or approval reference. Check what the terms require before billing; completion and approval are not interchangeable. Use the PO reference guide to match each line to the buyer’s order.
For this first scenario, assume A, B and C pass those checks and AP confirms they may share an invoice. USD 300 + USD 450 + USD 250 = USD 1,000. Entity Two’s USD 200 stays in its own group; it is not an adjustment or discount against the USD 1,000.
Remove charges already billed during the same month
- Search by work and reference, not payment status. Check earlier invoice numbers, their line descriptions and the service periods they cover. A charge on an issued invoice remains previously billed even if no cash has arrived. A draft that was not issued is a different state; check your system’s history and submission evidence rather than guessing from its filename.
Consider a separate variation: B was invoiced mid-month as INV-B-11 for USD 450 and remains unpaid. The new month-end charges for A and C total USD 550, not USD 1,000. B remains in the register with its existing invoice reference, but contributes USD 0 to the new invoice; a separate balance summary can identify its unpaid USD 450.
- Retain correction and cancellation history. If an earlier invoice was canceled or reduced, record the original number, amount, correction reference and confirmation before deciding what remains eligible to bill. An unsent cancellation request is not completed cancellation. If the records disagree, hold the affected line for investigation rather than silently reissuing it under the monthly invoice number.
Send a summary that identifies every included charge
- Ask permission using a proposal, not another payable document. Send only the recipient purchasing entity’s relevant lines, with the message below marked “Proposal for grouping confirmation — not an invoice.” It should identify the period, entity, currency and PO lines, and state that no invoice is being issued by that message. Do not upload the proposal into a payable-invoice channel unless AP specifically directs how to submit it as non-payable material.
Return to the original scenario where none of A, B or C has been invoiced. If AP allows one invoice, carry those confirmed lines into a USD 1,000 invoice. If it requires separate invoices, create A, B and C documents for USD 300, USD 450 and USD 250; the eligible total remains USD 1,000.
In the already-invoiced-B variation, only A and C generate new charges totaling USD 550, whether combined or issued separately. B keeps its existing INV-B-11 for USD 450 and is not invoiced again. Keep excluded-row detail in your internal register; send each buyer only its relevant subset, without another entity’s project details.
If only one PO must be separate, record exactly which lines may be grouped. If AP has not answered, leave permission pending and ask for the owner and next check time; do not interpret silence as acceptance. If a cutoff approaches, ask how to submit the eligible charges while preserving the agreed payment terms.
Close the monthly register without erasing excluded items
- Assign an outcome to every line. Keep the register in your existing document or spreadsheet, with one row per charge. The following fields make exclusion reasons visible without placing them on the buyer’s payable invoice.
| Field | What to record |
|---|---|
| Month and service period | Billing batch plus actual dates covered by the charge |
| Buyer / supplier / currency | Confirmed legal identities and amount currency |
| PO / project / line | Buyer reference and your work identifier; alternative reference if no PO is used |
| Previous invoice | Number, line, amount and issue status; cancellation or credit reference if relevant |
| Current invoice | Number and this line’s new charge, or pending if not issued |
| Held / excluded | Amount, reason and evidence; retain the line rather than deleting it |
| Confirmation / next owner | AP response, date, unresolved question, responsible person and follow-up |
| Submission / receipt | Route, timestamp and acknowledgment for the issued document |
For the first scenario, A/B/C move from eligible to issued only when the actual invoice is issued; record its number once. D remains excluded from that group with “different purchasing entity,” and its own billing decision is tracked separately. A line awaiting approval stays held, with the missing evidence named.
- Reconcile the register before closing the batch. Confirm that each eligible amount appears once in the issued invoice lines and that previously billed, held and excluded rows contribute nothing to the new total. Keep payment allocations in a separate field or linked record; money received does not rewrite which work was invoiced. Use receipt evidence to distinguish sending from confirmed intake.
Use your current tools if they preserve this history and produce the buyer’s accepted format. Compare software only when repeated duplicate checking, numbering, line tracking or payment matching creates a specific burden the current setup cannot handle. Check currencies, local invoice requirements, history retention, buyer-format exports and ongoing cost before choosing anything; software cannot grant consolidation permission or replace a mandatory buyer portal.
Template
Use this with the first fictional scenario only after checking that A, B and C have not been invoiced. Replace the identifiers and dates; the Japanese version requests the same decision.
Subject: Proposed November grouping — not an invoice
This proposed monthly invoice groups projects A, B and C for the
same purchasing entity, totaling USD 1,000. Does your AP process
allow these order references on one invoice?
A: USD 300 — PO-A / line 1 — 2–6 November 2026
B: USD 450 — PO-B / line 2 — 9–13 November 2026
C: USD 250 — PO-C / line 1 — 16–20 November 2026
Purchasing entity: [confirmed legal name]
Please confirm whether separate invoices are required for any line,
the submission route and cutoff, and any unresolved billing condition.
This message requests grouping confirmation; it is not an invoice.
件名:11月分の合算案について(請求書ではありません)
同一購入法人の案件A・B・C、合計1,000米ドルを月次でまとめる案です。
下記の注文参照を一つの請求書に記載できるかご確認ください。
A:300米ドル/PO-A・明細1/2026年11月2〜6日
B:450米ドル/PO-B・明細2/2026年11月9〜13日
C:250米ドル/PO-C・明細1/2026年11月16〜20日
購入法人:[確認済みの正式名称]
別請求が必要な明細、提出経路・締切、未確認の請求条件があれば
お知らせください。
本メールは合算可否の確認依頼であり、請求書ではありません。
When to bring in a professional
AP can confirm document routing and its accepted grouping. Ask an accountant about mixed tax treatment, invoice-form requirements, cancellations or credits that change the amount basis. Provide the source documents and register, not only the proposed total.
Seek legal advice when the purchasing entity, entitlement to payment or conflicting payment terms are disputed. This register is an editorial control against missing or duplicated charges; it does not determine tax treatment or whether a buyer may legally delay payment.
Kit
Copy the register and message above at no charge; no kit or registration is needed. For stages of one project, use milestone invoice reconciliation. For differences after a payment, use short-payment reconciliation. The selling-to-Japanese-companies guide connects the broader workflow.
This guide goes stale when
- Astellas changes its PO and invoice-line matching instructions.
- Your buyer changes its consolidation permission, purchasing entity, submission route or cutoff.
- Your invoice format, currency or applicable accounting requirements change.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | Purchase to Payment | October 27, 2026 |
Was this useful?
More on Invoicing & tax paperwork
-
Make a bilingual invoice without creating two different bills
Keep one invoice identity across English and Japanese, reconcile dates and amounts, and tell the buyer how the translated document relates to the original.
-
Your Japanese client says they paid: trace the transfer before sending a reminder
Separate payment advice, execution, tracking and bank credit, then assemble a safe trace packet for the same invoice and transfer.
-
Allocate one combined payment across several invoices without guessing
Keep a bank credit separate from proposed invoice allocations, request a remittance breakdown and preserve unexplained balances without double-counting.
Get the next guide by email
Two emails a month: new guides, and what changed on the Japanese side. Unsubscribe in one click.