SaaS Mode

Compliance Center and Compliance Manager
All sub‑accounts need to get direct access to essential legal documents. For example make a menu item Compliance Center Center in each sub account. In that menu you will find the following: Contracts (or singed contracts) Terms and Conditions Privacy Policy GDPR Information HIPPA Other relevant compliance documents This ensures transparency and makes it easy for sub-accounts to review and manage all legal information in one centralized location what they agreed on with you. If you have like 200 subs accounts and different contract you can find them really easy back in each sub account. Ideally, you could make a centralized Compliance Manager in the Agency View. There you can manage all these documents. It would be especially useful if agencies could create and manage different sets of terms, privacy policies, contracts, and compliance documents and have them automatically appear in the corresponding sub-accounts. Either applied to all sub-accounts or customized per sub-account. Additionally, having the option to upload and display signed agreements and contracts would ensure that customers can always access and review their specific documents easily. This feature would improve transparency, streamline compliance, and enhance the customer experience. Access is role‑based to ensure that only authorized users have the rights to view these documents. This guarantees transparency while protecting sensitive information, giving the right users the ability to read content securely.
0
·
New Feature
SaaS Subscription Billing Should Continue Invoicing/Attempting Payment for All Future Cycles After a Single Failed/Missed Payment
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). Example: * 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. Intended Behavior: 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).
0
·
Bug
Load More