Desired Outcome
Introduce a company-level control mechanism that ensures financial risk is properly managed.

Currently, blocklisting in Mews is applied at the customer profile level, which aligns with where reservations are created and managed.
However, in Account Receivables workflows, companies (profiles with billing responsibility) are financially accountable — not the individual customers attached to reservations.

Option A: Company-Level Blocking

Add a “Block company” flag
Prevent:
-Creation of new reservations linked to that company
-Assignment of that company as billing profile
-Applies across all related customer profiles

Option B: Automated Financial Enforcement (Credit-Based)
Enhance the credit limit system:

Automatically evaluate:
-Outstanding balance
-Credit limit thresholds

Trigger:
-Reservation warnings or hard stops
-Visual alerts across profiles

Option for configurable enforcement (warning vs block)

Option C: Cascading Risk Flagging

• Introduce a “financial risk status” at company level
• Automatically: >Flag all associated customer profiles >Surface warnings during reservation creation

Could integrate with automations / API triggers

Business Impact
-Reduces financial risk exposure
-Improves AR control and accountability
-Eliminates reliance on manual processes
-Aligns system logic with real-world financial responsibility