Reconciling and Validating Sync Operation

Just like any accounting based system, like a checkbook, credit card statement, or invoicing, there needs to be some level of oversight and validation performed on a regular basis to ensure proper operation and data accuracy.

A set of simple steps can be followed to essentially reconcile / check consistency between both sides. In this case between Ingram and Autotask.

Tools

Autotask Data

• Create a custom report that will show the current state of all contract service items

Ingram Data

• IDSync Subscription Report

IDSync Adjustment Audit History

• IDSync Adjustments Log Report

• IDSync Adjustments Failure Log Report

Process

• Check and handle any exceptions

  • View the IDSync Adjustments Failure Log Report for any current exceptions that are adjustments rejected by Autotask.

    • If Autotask is rejecting adjustments, then it is likely the two sides are not in proper sync

    • Correcting any exceptions will allow those adjustments to be retried and post to Autotask

  • View the IDSync Adjustments Log Report

    • These are successful adjustments, but is still a good idea to view the successful adjustments to see if there is anything might require further attention. Most likely not since these were successful, but still a good idea to revisit the period’s activity.

      • Review the key elements to verify proper mapping was done

        • What are the Ingram accounts, subscriptions, and resources source of adjustment

        • What are the Autotask accounts, contracts, and services that are targets of adjustment

        • What was the amount of the adjustment

        • What date was the adjustment made

        • What was the effective date the adjustment is being applied as

• After any exceptions have been addressed and postings processed

  • Run the Autotask custom report and export to Excel

  • Export the IDSync Subscription Report to csv and load into Excel

  • Compare the Autotask report with the IDSync Subscription report

    • Primarily this involves comparing the license counts to see that they are equal

      • Possible reasons license counts may not be equal

        • Some adjustments are posted to the beginning of the next billing period and may not be reflected in the Autotask report. Just like checks that haven’t cleared the bank need to be identified to reconcile a checkbook, so do adjustments that are posted to the future

          • Azure CSP adjustments post to the start of the next billing period

          • License reductions by default are posted to the beginning of the next billing period. There is a config option to change this so reductions post using the current date as the effective date. Send an email to support@idsync.com to have this changed.

    • Compare Unit Cost and Unit Price (MSRP)

      • IDSync does not update these in Autotask, but if there is a variance you may chose to manually modify the Autotask records.

If there are Autotask contracts that don’t reconcile with the Ingram data points that you are unable to answer, contact IDSync by sending an email to support@idsync.com