The current billing behavior for Agency SaaS subscriptions halts all subsequent invoicing and payment attempts immediately following a single failed or missed monthly payment.

When a client resolves the single outstanding missed invoice (e.g., paying November's invoice on December 9th), the system recognizes the account as "current" but fails to generate or process invoices for any intervening missed months (e.g., December's payment, which was already due).

* November 1: Payment failed (Card expired).

* December 1: The system DID NOT generate an invoice or attempt payment for the December subscription fee.

* December 9: The user paid the outstanding November invoice.

* Result: The system marks November as paid, but December's invoice is permanently skipped. The system then reverts to the original schedule, sending the next invoice on January 1st.

This behavior results in immediate revenue loss for the Agency and requires manual reconciliation and invoicing for every missed month, undermining the core function of automated SaaS billing.

The system must operate with a cumulative billing logic standard for all subscription platforms:

Maintain Schedule: All future scheduled subscription invoices must continue to be generated and added to the client's ledger, regardless of the status of previous invoices.

Cumulative Payment Attempts: Once the client resolves any single past-due invoice, the system should immediately generate and/or process all subsequently due, but unpaid, monthly invoices.

Correct Status: If a client is one month behind, the system should show two invoices due: the immediate past month (e.g., November) and the current month (e.g., December).