Applies To: Work 365 (Provider Invoices – Partner Center)
Audience: Billing & Finance, System Administrators

Overview

To keep billing runs on schedule, Work 365 lets you tolerate tiny deltas between a provider invoice and your calculated totals. If the variance is at or below a configured Usage Mismatch Tolerance, the import and reconciliation proceed so downstream steps (PDF, post, email, ERP sync) aren’t blocked. This is for rounding/precision noise—not to hide real data issues.

Key Concepts

• Usage Mismatch Tolerance – A small currency threshold on the Partner Center integration that allows invoice import to continue when totals differ by a tiny amount.

• Checksum Validation – Compares provider header totals vs. Work 365’s computed totals. If the difference exceeds tolerance, the import stops with an error.

• Scope – Applies only during Provider Invoice import/reconciliation. It does not change provider data, line math, pricing, taxes, or posted amounts.

How It Works

1. Work 365 downloads the provider invoice and computes totals from detail lines.

2. It compares the provider’s totals to Work 365’s calculated totals.

3. If difference ≤ Usage Mismatch Tolerance: import continues.

4. If difference > Usage Mismatch Tolerance: import stops with a checksum error so you can investigate.

The tolerance never adjusts numbers; it only decides whether the pipeline proceeds on very small variances.

When to Use It

• Cents-level rounding differences across currencies or tax rounding.

• Minor timing nuances where the provider made a tiny post-publication correction.

• FX conversions that introduce cents-level drift.

Steps — Modify the Usage Mismatch Tolerance

1. Go to Administration → Admin Hub.

2. Integrations → select your Partner Center integration.

3. Settings → Edit.

4. Locate Usage Mismatch Tolerance and enter a small amount (base currency).

5. Save. The new tolerance applies to future provider invoice imports.

Recommended Guidance

• Keep it minimal. Use the lowest value that clears routine rounding—typically a few cents.

• Investigate patterns. If you routinely hit the threshold, review product/offer mapping, segments/markets, and tax/FX sources.

• Audit the change. Note who changed it, when, and why. Validate the very next import.

Validating the Change

• Re-attempt the Provider Invoice import.

• Confirm it passes reconciliation and totals match the provider file.

• Check Exceptions / Jobs dashboards to ensure no lingering errors.

Troubleshooting

The invoice still won’t import

• The variance likely exceeds the tolerance or configuration issues exist (unresolved references, missing mappings, unsupported SKUs). Open the Provider Invoice and review the error.

Imported, but lines look off

• Tolerance only bypasses the total-difference stop; it doesn’t fix mapping. Review Provider Part Numbers, product/price list mapping, tax settings, and currency precision.

Concerned about accuracy

• Tolerance doesn’t mutate data; it just avoids blocking on tiny deltas. Continue reconciling totals against the provider’s statement.

FAQ

What amount should we use?
Start as low as possible (e.g., a few cents in your base currency). Raise only if you routinely see harmless rounding noise.

Does this change line amounts or taxes?
No. It only decides whether the import proceeds. All values remain as reported/calculated.

Is this the same as “Override Tolerance” during import?
Not exactly. Usage Mismatch Tolerance is the default/global threshold on the Partner Center integration. Override Tolerance is a one-off allowance entered at import time (handy for known credits or temporarily missing marketplace items).

Can I revert later?
Yes. Edit the setting and lower it—or set to 0—anytime.

Quick Compare

Best Practices

• Keep Azure billing in arrears and run it mid-month (~15th) to use finalized usage files.

• Use the smallest tolerance that avoids noise—don’t use it to paper over real mismatches.

• Pair with routine reconciliation and the Exceptions Dashboard to catch genuine issues early.

• Document tolerance values per environment (Dev/Test/Prod) in your ops runbook.

Summary

Usage Mismatch Tolerance keeps invoice processing moving when you hit tiny, expected variances. Set it sparingly, monitor the next run, and investigate any recurring or larger differences to protect data integrity.