FAQ and Key Integration Concepts

Not all Ingram software licenses are supported for syncing to Autotask. Primarily, IDSync supports user based licenses. Most often these are identifiable on the Billing screen as UNIT: USER

You may also see licenses appearing as UNIT: UNIT and UNIT: LICENSE If they are usage based licenses (like G Suite Business), then IDSync does not support them by default and they should not be mapped and must be manually invoiced. There are some UNIT and LICENSE types that behave as user based licenses, such as Dropbox. These are supported. When in doubt contact IDSYNC.

Usage Based Licenses

These require special coding to support their special requirements and each have to be supported explicitly.

Currently, the only usage based license support is for Azure CSP. It is projected that sometime in 2021, Azure NCE will also be supported.

After mapping of Ingram Resources to Connectwise Agreements has been performed, there is an established link between the mapped products.

• IDSync keeps an internal counter of the license count obtained from Connectwise at the time of mapping.

• The internal counter is updated for any adjustments sent to Connectwise

• IDSync relies solely on the internal counter to determine ongoing adjustments as changes occur in the Ingram Marketplace. IDSync does not interrogate Connectwise for its license count after the map is established. So any change to the count other than by IDSync will not be known by IDSync for reconciliation processing. It is expected that no manual adjustments are made to the Connectwise license count once the link from mapping is in effect.

When mapping Ingram with Connectwise, you have the option of 3 prices sources: Catalog, Agreement, Custom.

Agreement uses the price from the top Addition record on the agreement and if it is not present it will revert to Catalog as the source.

When you select Agreement price it interrogates Connectwise via the API to retrieve the price and populate the IDSync screen. It only does this during mapping. When you subsequently open the Billing screen and view mappings set to Agreement, it will reflect a price of 0. This does not mean IDSync has changed any pricing. It is simply avoiding the API overhead and not retrieving the latest price. There is a circular arrows icon next to the price display, you can click and IDSync will retrieve the latest pricing.

Azure is a consumption based subscription and only updates with a new adjustment when the Ingram monthly invoice is issued. To prevent proration for a monthly adjustment, IDSync posts the adjustment to the first day of the next billing period. It is recommended that the agreement start date has some adequate buffer between the invoice date and the agreement start date to allow for small variances in the invoice date or its issuance. That way the effective date posts to the nearest next billing period. We would recommend a 4-5 day buffer. If the buffer is too small, the posting could post to the next billing period rather than the nearest.

Project invoice dates for an Azure subscription can be found by looking at the Invoices Report.

Prior to invoicing it is recommended to review the Adjustments

• Log shows all the successful license adjustments made by IDSync and should be reviewed for any unexpected adjustments

• Failure Log shows any adjustments that Connectwise rejected and includes the error message of why it was rejected. Review these failures so that corrective action may be taken prior to invoicing so the adjustment is applied