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.

When mapping of Ingram Resources to Contract Services

• Be attentive to the Ingram license count and the Autotask license count prior to mapping

  • If the counts are not equal then IDSync will post an adjustment to the Contract to make them equal

    • Adjustments that are increases are posted with the current date as the effective date and may result in a prorated invoice

    • Adjustments that are decreases are posted to the first day of the next billing period to prevent prorated credits

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

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

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

• IDSync relies solely on the internal counter to determine ongoing adjustments as changes occur in the Ingram Marketplace. IDSync does not interrogate Autotask 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 Autotask license count once the link from mapping is in effect.

There are two options for the processing of license reductions.

By default, license reductions made in the Ingram Marketplace are posted to Autotask with an effective date that is the first day of the next billing period.

This is done at the request of resellers as Ingram in the past only prorated increases on their invoice to the reseller and not reductions. A reseller was charged for the full period for reductions. Because Autotask always prorates, they recommended IDSync to post reductions to the first day of the next billing period avoiding a prorate condition and a credit to the reseller customer.

Also, in Autotask the default data show for the Contract Services screen is based on the current date. So to see an adjustment posted to a future date, it is necessary to change the “Show data” date in the top right corner of the Services screen.

You can also confirm adjustments in IDSync by view the Adjustments Log report.

If you prefer to have reductions posted with the current date as the effective date, you can request that by sending an email to support@idsync.io and requesting that reductions be processed like increases. IDSync will make the configuration setting change at your request and then both reduction and increase license adjustments will be posted using the current date. Autotask will then prorate charges accordingly which could result in a credit on the invoice for the reduction. A couple key items for this configuration change are:

• it is a global change, affecting all your accounts

• it only affects reductions after the change is made, any pre-existing reductions that have already posted are not changed in any way.

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 contract start date has some adequate buffer between the invoice date and the contract 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.