1. New service - Starts on the first day of a month
    Create new service in Connectwise with the given quantity as units and start date as the effective date



  2. New service - Starts on during a month
    Create a new service in Connectwise with the given quantity as units. the effective date will be either the start date or the first day of the month(base on "change start date to the first day of the month" setting)



  3. Existing service - Starts on the first day of a month
    Get status of service from Connectwise base on the start date and quantity, it will be marked as completed(will be green) due to it already exists with the same units. 



  4. Existing service - Quantity changed for the entire of month
    Just sending unit adjustment to Connectwise base on the new amount



  5. New service - With quantity change during a month
    there will be 2 rows, one row for the creation of service and another row for quantity change. each will have separated actions. for first one we will create new service in Connectwise like scenario no 1. and for the other, we will send unit adjustment for that service.
    note: because these actions should run in exact order, therefore we do not permit the user to execute change action first.



  6. Existing service - With quantity change during a month
    Just sending unit adjustment to Connectwise base on the new amount and date of the change



  7. New charge(Usage/one-off)
    Creating new charge in Connectwise with given "unit cost", "unit price", "material code", "effective date" and "is billable".
    note: user can change "unit price", "effective date", "is billable" before sending to Connectwise 



  8. Existing charge(Usage/one-off)
    Get status of charge from Connectwise base on the effective date and unit cost, it will be marked as completed(will be green) due to it already exists with the same unit cost. 



  9. New multiple charges for the same source contract
    Creating every charge individually, same as scenario no 7.



  10. Two Services from different source contracts which are mapped to the same contract-service in Connectwise
    In this case, we set the row as "invalid scenario" and prevent user to post the adjustments.


  11. New service - With more than 1 quantity change during a month
    It will be the same as scenario no 5. still, all actions should be run in exact order(base on start date). and if the user wants to run action in other orders, it will be prevented.



  12. Existing service - With more than 1 quantity change during a month
    It will be a combination of scenario no 6 and no 11. we need to send unit adjustment to Connectwise in exact order(base on start date). main service row will be completed(green) due to existing of service with the same units.



  13. Existing service - Ends during a month
    this means service is terminated at the given date. so we send decreasing unit adjustment to Connectwise with the given quantity to terminate that service. the effective date will be either the end date or the last day of the month(base on "change end date to the last day of the month" setting)



  14. New service - Ends during a month
    This mean service is created in a month and also terminated during the same month. so we need to do 2 actions, first, we create that service like scenario no 1, and second, we terminate that service by sending decreasing adjustment to Connectwise like scenario no 13



  15. Existing service - With quantity change at the start of the month + ends during a month
    We need to do 2 actions, first, we post unit adjustment for that service to Connectwise like scenario no 4, and second, we terminate that service by sending decreasing adjustment to Connectwise like scenario no 13



  16. New service - Ends on the last day of a month (and starts on the first day of the month)
    In this case, we need to get data from "Accounts Modified" report from ALSO/Westcoast API to determine whether this service is terminated. the rest will be the same as scenario number 14.

  17. Existing service - Ends on the last day of a month
    In this case, we need to get data from "Accounts Modified" report from ALSO/Westcoast API to determine whether this service is terminated. the rest will be the same as scenario number 13.



    The Mock File: