FA-59789 / Subscription proration billing / Member archive

Proration behavior modes and pending items: none keeps pending · case 04

Changes made without prorations erase previously pending items.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

Input {behavior create_prorations|none|always_invoice, amount (net new proration), pending (existing pending items)}. none: nothing is created and pending is untouched. create_prorations: amount joins pending for the next renewal invoice. always_invoice: pending plus amount are invoiced now; a negative total becomes a credit. Return [invoiced_now, pending_after, credited].

Why this case matters

Whether prorations are invoiced now, deferred, or skipped decides when the customer pays and what stays pending.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
regression 0	`[0, 0, 0]`	`[0, -1049, 0]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.