Invoices and dunning

Invoices are produced from policy transactions. Each record keeps premium, taxes, fees, commission where applicable, and the remaining balance. The PDF shows named tax lines when its tax total matches a quote snapshot that contains itemized taxes; otherwise it combines them as Taxes and surcharges.

​

Aging

Open balances move through Current, 1-30, 31-60, 61-90, and 90+ buckets. The 90+ bucket begins after day 90. Manual and automated delivery share one ledger, so Underflow knows what the payer has already received.

​

Dunning

The hourly scheduler runs one dunning pass during the workspace’s local eight o’clock hour. In a fractional-offset time zone, that can be 8:15, 8:30, or 8:45. It sends or proposes at most one notice per invoice per pass:

1. The initial invoice, if no non-failed attempt is on file.
2. One reminder when the balance crosses each aging bucket.
3. A final notice when the balance is more than 90 days past due.

Each aging bucket sends its reminder once. A manual Send or Resend records an invoice delivery and satisfies the initial-delivery step, but it does not mark an age-specific reminder as sent. Signed provider events mark every attempt Pending, Accepted, Delivered, Deferred, Bounced, Complained, or Failed. Severity catches up one step per pass, normally one step each day. For example, an invoice first processed 40 days late receives its initial delivery on one pass and the appropriate aging reminder on the next.

​

Escalation to cancellation

When a balance remains more than 90 days past due after confirmed delivery of the final notice, Aurora proposes a nonpayment cancellation. Provider acceptance alone is not delivery. The proposal always requires a person’s approval. Approval requires a verified home-state notice rule and creates the cancellation notice; confirmed delivery starts that rule’s notice period. The due-date sweep checks both the balance and confirmed notice delivery before changing coverage. If the balance is clear, it rescinds the schedule and creates a corrective notice; until then the scheduled cancellation remains visible unless a member rescinds it manually. See Cancellations and reinstatement.

​

Delivery failures

A notice that did not go out is still owed. A missing billing email fails before a delivery attempt is created; a send the mail provider refuses stays on file as Failed. Neither counts toward the cadence, so once the address or provider problem is corrected the next pass sends the same notice again. Accepted, Pending, Deferred, Bounced, and Complained attempts did go out and are not repeated automatically; review those provider states before sending again manually. Delivery history belongs to the invoice. The Receivables register shows the latest attempt’s provider status, time, and total attempt count; it does not currently open a full delivery-history view.