Difference between revisions of "Why MOR does not allow to delete users"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 1: | Line 1: | ||
MOR/M4 does not allow the deletion of users who have made at least one call or payment in the past to prevent issues with billing integrity. | |||
'''Let’s Break It Down: Why Deleting Users Can Mess Up Billing''' | |||
Imagine | Imagine this setup: | ||
* You have 2 users: U1 and U2. | |||
* You have 1 provider: P1. | |||
'''Here’s what happens during the month:''' | |||
* U1 makes 20,000 calls (at 1 EUR per call) = 20,000 EUR. | |||
* U2 makes 10,000 calls (at 1 EUR per call) = 10,000 EUR. | |||
So, in total: | |||
* Users owe you 30,000 EUR. | |||
* Since you sell at a 100% margin, you pay your provider P1 15,000 EUR for the calls. | |||
* Your profit = 15,000 EUR. | |||
BUT | '''What happens if you delete U1 and their calls?''' | ||
Now the system only shows U2 with 10,000 calls, meaning: | |||
* You see that you owe P1 50% of 10,000 EUR = 5,000 EUR. | |||
* BUT P1’s records still show they sent 30,000 EUR worth of calls, meaning you owe them 15,000 EUR. | |||
'''The Result:'''You think you owe 5,000 EUR, but P1 demands 15,000 EUR. This mismatch leaves you with a -10,000 EUR loss for the month! | |||
'''The Lesson:''' Never delete users with historical call data, as it disrupts billing and creates financial discrepancies! | |||
<br><br> | <br><br> | ||
= | = Solution = | ||
* Kolmisoft engineers can delete Users after removing old CDRs and Payments associated with those Users. MySQL root password is needed. This task can be done by [[Support#Rates_of_technical_services | an hourly rate]]. | * Kolmisoft engineers can delete Users after removing old CDRs and Payments associated with those Users. MySQL root password is needed. This task can be done by [[Support#Rates_of_technical_services | an hourly rate]]. |
Revision as of 08:11, 14 January 2025
MOR/M4 does not allow the deletion of users who have made at least one call or payment in the past to prevent issues with billing integrity.
Let’s Break It Down: Why Deleting Users Can Mess Up Billing
Imagine this setup:
- You have 2 users: U1 and U2.
- You have 1 provider: P1.
Here’s what happens during the month:
- U1 makes 20,000 calls (at 1 EUR per call) = 20,000 EUR.
- U2 makes 10,000 calls (at 1 EUR per call) = 10,000 EUR.
So, in total:
- Users owe you 30,000 EUR.
- Since you sell at a 100% margin, you pay your provider P1 15,000 EUR for the calls.
- Your profit = 15,000 EUR.
What happens if you delete U1 and their calls? Now the system only shows U2 with 10,000 calls, meaning:
- You see that you owe P1 50% of 10,000 EUR = 5,000 EUR.
- BUT P1’s records still show they sent 30,000 EUR worth of calls, meaning you owe them 15,000 EUR.
The Result:You think you owe 5,000 EUR, but P1 demands 15,000 EUR. This mismatch leaves you with a -10,000 EUR loss for the month!
The Lesson: Never delete users with historical call data, as it disrupts billing and creates financial discrepancies!
Solution
- Kolmisoft engineers can delete Users after removing old CDRs and Payments associated with those Users. MySQL root password is needed. This task can be done by an hourly rate.
- Hide users if you don't want to see them in your system. In the latest MOR version, hidden users are not visible in search filters.