Separate the service period, invoice date and buyer cutoff
Record the work period, actual invoice issue date, buyer submission cutoff and agreed payment trigger without changing one date to stand in for another.
What happened
You finish November’s work for a Japanese customer and issue the invoice in December. The buyer asks for a November date so it can process the charge in its current cycle. Before changing the document, find out whether that request concerns the service period, the invoice issue date or an internal accounting field.
Consider a fictional overseas service provider billing work performed from 1 through 30 November 2026. The invoice is actually issued on 2 December, and accounts payable (AP), the buyer’s invoice-processing team, confirms a submission cutoff of 3 December 2026 at 15:00 Japan Standard Time (JST). These dates are invented for this exercise, not a Japanese billing calendar or a statutory deadline.
Your useful output is a dated record that keeps four meanings apart: work covered, document issued, processing cutoff and agreed payment trigger. The actual receipt timestamp belongs beside them as evidence. This guide does not decide whether a past-dated document is lawful or determine your payment due date.
What’s going on on the Japanese side
Record the work period without substituting a month-end date for every event
Check what this charge covers: a monthly service, recorded hours or a delivered result. A period describes work across dates; a delivery date describes an event. Neither establishes that every item was accepted or that unfinished work is billable.
In the fictional monthly-service example, retain both endpoints, 1–30 November 2026. If some work continues into December, identify which portion belongs to this charge and return to the agreement before treating the entire project as completed. The milestone billing record helps separate newly billable work from earlier invoices.
GOV.UK’s invoice guidance lists the supply date and invoice date separately. That is UK guidance, not a list of requirements imposed on every overseas supplier selling to Japan. It supports keeping the concepts distinct; it does not decide how your service period maps to a legally required supply date. Source
Keep the actual issue date separate from a requested processing date
For the example, the document was issued on 2 December. Writing 30 November in a service-period field communicates something different from replacing its issue date. Ask what the buyer’s requested date is intended to represent and where that field will appear.
Do not treat a request from AP as sufficient advice about your own accounting or tax obligations. Preserve the original invoice and the request while your accounting adviser checks any proposed issue-date correction. If the document needs correction, follow the applicable correction process and the buyer’s intake instructions instead of silently overwriting an already submitted file.
| Fictional record | Supported entry | What it does not establish |
|---|---|---|
| Work covered | 1–30 November 2026 | Every project deliverable was accepted on 30 November |
| Actual invoice issue date | 2 December 2026 | AP received the invoice on that date |
| Buyer submission cutoff | 3 December 2026, 15:00 JST, from AP’s reply | A payment due date or promised bank credit |
| Payment trigger | Not yet clarified | Receipt, approval or month-end can be selected by guesswork |
Astellas describes payment terms agreed in the contract or based on the country-specific standard of the affiliate processing the invoice. Its page also describes submission routes that vary by location. This is one company’s procedure, not evidence that Japanese businesses share a cutoff or payment cycle. Source
What to do next
Convert the confirmed cutoff into your local calendar date
-
Ask for the full deadline and its meaning. Confirm the date, time, timezone, relevant holiday treatment and whether AP means successful portal submission, arrival in its mailbox or another recorded event. Ask which acknowledgment demonstrates that event. A message sent before the cutoff may still leave receipt unresolved.
-
Save both the buyer’s timestamp and your local conversion. Use the timezone for your actual location and the specific date, including its seasonal offset. Retain the original reply and the conversion method so the local reminder can be checked later.
The following conversions are calculated for the fictional deadline, using the named timezone rules for that date. They are examples of the same instant, not three submission options.
| Location / timezone | Same fictional cutoff | Check |
|---|---|---|
| Japan / Asia/Tokyo | 3 December 2026, 15:00 JST (UTC+09:00) | Buyer-stated timestamp |
| UTC / Europe/London on this date | 3 December 2026, 06:00 UTC (London GMT) | 15:00 minus nine hours |
| Los Angeles / America/Los_Angeles | 2 December 2026, 22:00 PST (UTC−08:00) | 06:00 UTC minus eight hours crosses to the previous date |
A Los Angeles provider who puts “3 December” in a date-only reminder can miss the local evening deadline. Keep the year, calendar date, time and zone together. Choose your own preparation buffer rather than treating the exact cutoff as a safe moment to begin uploading; the buffer is your plan, not a new buyer requirement.
Identify the agreed payment trigger before calculating a due date
- Copy the relevant terms into your private billing record. Record the document version, exact wording and any accepted changes. If the wording refers to invoice receipt, acceptance, month-end or another event, identify the evidence for that event rather than selecting the most convenient date.
If a reply says “next payment cycle,” ask for the scheduled execution date and whether that changes any agreed term. Do not calculate a due date from the cutoff alone. For this fictional case, the payment trigger and payment date remain unconfirmed; the table deliberately contains no calculated due date.
Contract wording or an internal cutoff does not establish that an applicable mandatory payment deadline can be extended. Do not treat late administrative receipt or pending internal approval as an automatic extension. Where governing law, the transaction’s scope or competing terms are uncertain, preserve the facts and ask an appropriate professional to assess them.
Explain a missed cutoff without rewriting the underlying facts
- Choose the next question from the actual status. The actions below are proposed recordkeeping steps, not rules requiring a buyer to accept a late invoice or change its payment terms.
| Current status | Ask next | Preserve |
|---|---|---|
| Not submitted; confirmed cutoff still ahead | Which route and acknowledgment count as receipt? | Correct destination and complete cutoff |
| Submitted; receipt unknown | Has this same invoice entered the designated process? | Sent record, invoice number and response |
| Cutoff passed or processing rejected | Can it enter the current cycle, or what execution date is now proposed? | Actual dates, stated reason and named responder |
| Buyer asks for an earlier issue date | Which field and purpose does the request concern? | Original invoice and adviser-reviewed correction decision |
| Terms or due date disputed | Which wording or event is disputed? | Agreement, receipt evidence and separate party positions |
Use the receipt-evidence guide if acceptance into AP’s process is the missing fact. Mark any resend as a copy of the same invoice. For an actual correction, use the returned-invoice workflow so the original and replacement do not become two payable entries.
Keep the four meanings visible and add evidence as it arrives
- Maintain one billing note beside the invoice. This is an editorial checklist, not a complete invoice or accounting record. An unanswered field should say “unconfirmed,” with an owner and next question, rather than contain a plausible date.
| Record field | Fictional starting entry / evidence needed |
|---|---|
| Service period and charge basis | 1–30 November 2026; agreed monthly service |
| Actual issue date / invoice ID | 2 December 2026; copy the real identifier in use |
| Formal receipt timestamp | Unconfirmed; retain AP or portal acknowledgment when obtained |
| Submission cutoff / source | 3 December 2026, 15:00 JST; retain AP’s dated reply |
| Agreed payment trigger / source | Unconfirmed; locate terms and ask about ambiguous wording |
| Responding owner / next update | Record the established AP contact and agreed response date |
| Due date / scheduled transfer | Keep separate; neither is established in this starting example |
After a reply, record what changed and what remains unresolved. A proposed payment run is not evidence of bank credit. If a supported due date later passes without matched payment, move to the overdue-invoice follow-up with this factual timeline.
Template
Ask about the processing cycle while preserving the actual dates
Replace the fictional dates and add your existing invoice reference. Send only the information needed through the buyer’s established channel; confidential agreement extracts can be shared separately with the appropriate recipient.
Subject: Service period, issue date and processing cutoff — [invoice ID]
The services cover 1–30 November 2026, and the invoice was issued
on 2 December 2026. We have recorded your submission cutoff as
3 December 2026 at 15:00 JST.
Can this invoice enter the current processing cycle before that
confirmed cutoff, or should we expect a different scheduled
payment date? Please confirm which receipt event counts for the
cutoff and the payment trigger under our agreed terms.
If your request for a November date concerns the service-period
field, please confirm that meaning. We have kept the service
period and actual issue date separate while clarifying the request.
件名:役務対象期間・発行日・処理締切の確認 — [請求書番号]
役務対象期間は2026年11月1~30日で、請求書は2026年12月2日に
発行しました。提出締切は2026年12月3日15時(日本標準時)と
記録しています。
この確認済み締切までに今回の処理に含められるでしょうか。
それとも別の支払予定日を見込む必要がありますか。締切の判定に
用いる受付時点と、合意済み支払条件の起算点をご確認ください。
11月の日付をご希望の理由が役務対象期間の欄であれば、その旨を
ご確認ください。ご依頼の意味を確認する間、役務対象期間と
実際の発行日は分けて記録しています。
When to bring in a professional
Refer date corrections and disputed payment timing to the appropriate adviser
Ask your accounting or tax adviser how required supply-date fields, issue-date corrections and reporting periods apply to your business. Use legal advice for disputed obligations, governing law or mandatory payment deadlines. AP can clarify its processing channel and cutoff, but that answer does not settle those separate questions.
Kit
Start with one invoice and an existing document or spreadsheet
Copy the service period, actual issue date and buyer’s cutoff into the record above, then identify the missing payment-trigger evidence. No purchase, registration or new billing tool is needed. The overall selling workflow places this record alongside the agreement and invoice-submission stages.
This guide goes stale when
- GOV.UK changes its invoice-date and supply-date guidance.
- Astellas changes its published payment-term or invoice-submission guidance.
- The buyer's cutoff, submission route, agreed terms or relevant timezone rules change.
Sources
| Publisher | Document | Checked |
|---|---|---|
| other | GOV.UK — Invoices: what they must include | November 2, 2026 |
| other | Astellas — Purchase to Payment | November 2, 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.