Interface: DraftSendDetail
Defined in: src/server/services/invoice/weeklyRun.ts:743
Pre-send confirmation row for one draft invoice in the Review & send dialog: who it will be
addressed to, when it is due, and an advisory amount-anomaly signal. baselineCents is integer
cents (or null when there isn't enough issued history); anomaly is purely advisory and never
blocks a send.
Properties
anomaly
anomaly:
boolean
Defined in: src/server/services/invoice/weeklyRun.ts:751
This draft's amount is unusually far from the baseline — an advisory "double-check" flag.
baselineCents
baselineCents:
number|null
Defined in: src/server/services/invoice/weeklyRun.ts:749
Mean of the facility's recent ISSUED invoice totals (null when there isn't enough history).
dueDate
dueDate:
string|null
Defined in: src/server/services/invoice/weeklyRun.ts:747
invoiceId
invoiceId:
string
Defined in: src/server/services/invoice/weeklyRun.ts:744
toEmails
toEmails:
string[]
Defined in: src/server/services/invoice/weeklyRun.ts:746
The billing-contact email(s) the invoice will actually be sent to — shown before confirming.
unapprovedHours
unapprovedHours:
number|null
Defined in: src/server/services/invoice/weeklyRun.ts:759
Hours the send RPC's soft gate will hold this draft on — SAME predicate as send_invoices
(0113): submitted/pending_approval entries in the draft's period, on its line assignments,
unattributed or attributed to this draft. Server-computed so the dialog's acknowledge flow
never depends on a client-supplied figure. null = the precheck read failed — the dialog
must say so, never imply zero (the RPC still holds unacknowledged sends either way).