Bill by configuration
ConnectActive can bill an agreement addition by the company’s ConnectWise Manage configurations instead of its users: one unit for each active configuration of a type, such as Managed Workstation or Server. There are two steps, on two pages. Ticking a type on the company’s Settings makes it a group. You then map that group to an addition on the company’s Agreements page, the same way as any other group.
1. Choose the configuration types
Section titled “1. Choose the configuration types”- Open the company’s Settings page.
- Open the Bill by Configuration card. It lists your ConnectWise Manage configuration types.
- Tick each type you bill for. Each choice is saved as you make it.
- Click Perform Sync. Each ticked type becomes a group named Configuration - type, for example Configuration - Managed Workstation. The group lists show a newly ticked type only after a sync has run.
A configuration is a member of its type’s group when it belongs to the company and its status is not Inactive, Retired or Automate Inactive. Each configuration counts once, whatever its contact or name.
2. Map the group to an addition
Section titled “2. Map the group to an addition”- Click Agreements.
- On Overview, click SELECT under Group Mapping (or open the Group Mappings tab).
- Under Map Group to Agreement Addition, choose Configuration - type and click Add Group Mapping.
- Choose the addition in Select Agreement Addition, or create it with Create a New Agreement Addition.
- Set the options you need (Mapping options). The options that only apply to users aren’t shown for a configuration mapping.
- Click Perform Sync, check the count under Agreement Additions on the Review Form, and click COMMIT.
The addition’s count is the number of active configurations in the group. With Include Users on Invoice, the invoice lists each configuration by its name.
Bill several types on one addition
Section titled “Bill several types on one addition”To bill, for example, workstations and laptops as one Managed Devices addition:
- Tick both types on the Bill by Configuration card, and click Perform Sync.
- Map one of them, such as Configuration - Managed Workstation, to the addition as above.
- On that mapping’s header, click the merge button (Map 2 or more Licenses to a single Agreement Addition).
- Choose Configuration - Laptop, choose Union, click CLOSE, then perform and commit a sync.
Difference subtracts one type from another, and Intersection works as it does for any group (Combine groups or licenses). The merge list offers only configuration groups for a configuration mapping. Configurations and users can’t be counted on the same addition.
How the addition changes
Section titled “How the addition changes”- Each sync. A configuration added, retired or moved to another company in ConnectWise Manage changes the count at the company’s next sync.
- Like users. Configurations added and removed are recorded on the addition’s audit. Prorating, Hold Contact Drops until After Invoicing, tiered pricing and Do Not Update Count work as they do for users.
- Renamed configurations. A configuration that is renamed stays on the addition under its new name, and isn’t recorded as removed and added. A renamed configuration type keeps its mappings.
- Contacts are not affected. Configurations are never matched to contacts, never create or change a ConnectWise contact, and don’t count as synced users.
Unticking a type
Section titled “Unticking a type”If you untick a type that a mapping uses, the card names the additions that bill it and asks you to confirm. The mappings and their settings are kept, but syncs stop updating those additions until you tick the type again. The sync log says the group was not found. A ticked type that has been deleted in ConnectWise Manage is marked Unavailable, and nothing is billed for it.
If configurations can’t be read
Section titled “If configurations can’t be read”The API member needs to read configurations (Permissions). If a sync can’t read the company’s configurations, it leaves every addition that bills configurations unchanged and names those mappings in the sync log. The company’s other additions are synced as usual.
