Reasons for the Checksum Error on the Provider Invoice

Audience: Billing Teams, System Administrators

Overview

When Work 365 imports a Provider Invoice (e.g., from Microsoft Partner Center), it validates that the invoice header total equals the sum of all line items (usage + license summary).
If the totals don’t align, Work 365 blocks the import and throws a Checksum Error to prevent incomplete or inconsistent financial data from entering your environment.

This article explains why checksum mismatches occur and how to resolve them effectively.

How the Checksum Validation Works (at a glance)

• Header Total (from provider) is compared to the computed Detail Total in Work 365.

• Detail Total = Sum of License Summary lines + Usage/Consumption lines ± Credits/Adjustments (if present).

• Any non-zero difference outside the allowed tolerance triggers Checksum Error and the invoice is not activated.

Common Causes & Resolutions

Cause: Additional Tax Applied

Symptom: Provider header includes tax/levies not accounted for in Work 365.
Resolution:

1. Open the Provider record in Work 365.

2. Add or adjust the tax configuration so the extra tax is recognized during validation.

3. Re-import the provider invoice.

Cause: Credit Back from Microsoft

Symptom: Partner Center shows a credit note/adjustment; daily/summary lines don’t include that amount.
Resolution (one-time):

1. During manual import, enable Override Tolerance.

2. Enter the credit amount (rounded up to the nearest whole number).

3. Re-import the provider invoice.

Cause: G-Series / Marketplace / Reserved Instance Items Missing

Symptom: Certain categories (e.g., Marketplace SKUs, Reserved Instances) appear in Partner Center summaries but are absent from the detailed file you imported.
Resolution:

1. Download the summary file from Partner Center.

2. Identify the missing item(s) and total their charges.

3. If the missing total equals the checksum difference, use Override Tolerance to reconcile and sync.

Other Frequently-Seen Root Causes (Checklist)

• Rounding/Precision drift (e.g., fractional unit prices with many decimals).

  • Fix: Use Override Tolerance for minor cents-level differences; review decimal precision on currency fields if drift is frequent.

• Currency mismatch (provider invoice in a currency not active/mapped in Dataverse).

  • Fix: Activate the currency in Dynamics 365 and ensure price list/provider currency mapping is correct.

• Partial-period consumption still syncing (late-arriving lines).

  • Fix: Re-run import after the next sync window or re-import with Override Tolerance if difference is confirmed and documented.

• Split charges across multiple provider invoices for the same billing period.

  • Fix: Ensure you’re importing all related invoices for that cycle; avoid mixing partials across months.

How to Use Override Tolerance

Use Override Tolerance only when the difference is understood and acceptable (e.g., known credit, known missing Marketplace block).

Steps:

1. While importing the provider invoice, check Override Tolerance.

2. Enter a positive value equal to the missing/credited amount (rounded up).

   • Example: If the difference is –1,329.7525, enter 1,330.

3. Click Submit to re-import.

4. The invoice should now sync successfully without triggering checksum validation.

Important: Always document the reason (invoice number, amount, explanation) in the Notes on the Provider Invoice for audit purposes.

Adjusting the Default Tolerance

If small mismatches occur frequently (e.g., rounding), you can adjust the default tolerance.

Steps:

1. Navigate to Work 365 → Administration → Admin Hub.

2. Under Integrations, open the Partner Center configuration and click Edit.

3. Locate Usage Mismatch Tolerance.

4. Update the value (e.g., from 1 to 5).

5. Click Save.

Caution: Setting tolerance too high can mask legitimate discrepancies. Investigate the cause first, then set the minimum tolerance needed.

Troubleshooting — Isolate & Reconcile the Difference

Use this quick workflow to determine the root cause before overriding:

1. Confirm invoice scope & dates

   • Verify the billing period on the Provider Invoice matches your expectation for this import.

2. Export provider files

   • From Partner Center, download:

     • Invoice Summary (header-level)

     • Daily Rated Usage/License files (detail-level)

3. Compare totals

   • Sum usage + license in the detail files; compare to the invoice header total.

   • Identify the delta and the category causing it (tax, credit, marketplace, reserved instance).

4. Check currency & precision

   • Ensure the invoice currency exists and is active in Dynamics 365.

   • Look for fractional amounts beyond typical precision.

5. Re-import strategy

   • If the delta is explained: use Override Tolerance (document the reason).

   • If unexplained: review provider config, tax settings, product mappings; wait for the next sync if late items are suspected.

Best Practices

• Investigate before overriding: Confirm whether the difference stems from credits, tax adjustments, or missing usage.

• Align configurations: Keep Provider settings, tax configuration, and integration mappings in sync with Partner Center.

• Document overrides: Record invoice number, amount, and reason for each override to support audit/reconciliation.

• Review regularly: Periodically review recent Provider Invoices and override entries to ensure all differences are legitimate and accounted for.

• Minimize global tolerance: Prefer case-by-case Override Tolerance over raising the global Usage Mismatch Tolerance unless justified.