Billing Deadlines
Every deadline counts from the anchor: the date you choose as day zero. The
three windows — issue, dispute, resolve — are yours, and none is defaulted. A blank window is left out of the call, and the result names which
one is missing and says why it is null.
Lane 1 is the issue window, lane 2 the dispute window and lane 3 the resolution
window. Each has its own pattern and number. The anchor, the invoice date and the
request date are marked A, I and R, so the strip reads without relying on
colour. The strip draws what billingTimeline returned; nothing here
computes a deadline.
Worth trying: the same 30-day windows, invoiced one day
later —
the invoice deadline does not move, but the verdict turns to after the
deadline. Then a contract with 14 days to issue, 14 to dispute and 45 to resolve, and the
request moved to 20 March —
one day past the 14-day dispute deadline, and the request verdict turns to
after the deadline while the resolution deadline stays null.
Reference: billingTimeline
lays out the chain; convertUtcToPlainDate
reduces an instant to the billing party’s local date before it is passed in.
The rules for reading the strip are in
Intermodal: Billing Deadlines.