Repeat-client billing · manual calendar review

Which supplied payment run could include this invoice?

Compare the approval time against a customer's supplied cutoffs, then separate that result from the original invoice due date. A missing run is left unresolved; this page never invents a customer's payment policy.

Use internal codes only. No customer names, bank details or private invoice text are needed. Check the fictional example against your confirmed records before using a result.

Try the existing invoice tool ↗

The invoice tool is separate. Free output has branding and usage limits. This review adds no automatic invoicing, payment tracking, reminders, account access or membership feature.

Start from a filled fictional calendar

Confirmed eligibility basis What does approval exactly at cutoff mean? Run code | Run YYYY-MM-DD | Approval cutoff with UTC offset

One record per line, pipe-separated, without a header. Use explicit UTC offsets, for example +11:00. Use unknown only when actual approval time is not confirmed.

Invoice code | Original due date | Actual approval timestamp or unknown | Confirmed earliest date I checked these calendar dates and eligibility rules with the buyer. The example is fictional.

No live result yet. Changing any input clears the previous result.

Fictional worked result

INV-A was approved one hour after RUN-A's cutoff. Of the two supplied runs, RUN-B is the first match, seven calendar days after the original due date. INV-B meets RUN-A's cutoff and matches 22 October. INV-C remains unresolved because its approval time is unknown.

A payment-run match is not confirmation that money will arrive on that date. Keep the original due date, customer approval evidence, forecast run and actual receipt as separate records. Do not change an issued invoice just to match an internal run.

How this review works

Confirm one buyer and one calendar scope. Enter that buyer's supplied run dates and approval cutoffs.
Choose the confirmed eligibility rule. “Earliest date” can differ from the invoice due date; neither is inferred from a website example.
For each invoice, exclude runs earlier than its eligibility date. Compare actual approval time with each remaining cutoff, using the chosen equality rule.
Return the first matching supplied run. Show the calendar-day difference from the unchanged due date. If no supplied run matches, request the next calendar instead of guessing.

Boundaries and next step

Use one fixed UTC offset per review. Split records spanning daylight-saving changes into separate reviews with confirmed local times. Invalid dates, duplicate codes, mixed offsets and multiple runs on one date stop the review. Up to 100 invoice rows and 100 run rows are supported. This does not calculate bank clearing time, public holidays, interest, GST or contractual rights.

Entries are processed by this page's code without uploads, account storage or changes to invoice drafts. A browser may restore typed form values. Downloaded JSON is a working paper, not an invoice, bank record or proof of payment.

After resolving a flagged record, use the existing Australian invoice template or ABN invoice field guide if a new invoice is appropriate. For the original workflow, see month-end AP cutoff and payment-run reminders.

Source and independent method

Western Sydney University documents its own approval cutoff, payment run and due-for-payment conditions. That is a specific buyer's process, not a rule for all Australian customers. This independent review accepts the calendar you confirm; it does not assume the university's rules apply to your invoice. business.gov.au explains invoice and payment information.

Sources read 19 October 2026. Fictional example and calculation method prepared independently by ABN Invoice. Source organisations do not endorse this candidate.