Check the meaning.
Then compare.

1. Use comparable exports. Align the reporting date, account scope and status definitions. A canceled subscription can still have legitimate access until the end of its term.
2. Choose a stable shared ID. Prefer an existing customer or account ID. Display names and email addresses may change or be shared. Duplicate IDs are reported and will not be paired automatically.
3. Align column names. The current evaluator compares shared column names. Choose only fields with the same meaning in both systems.
4. Set explicit types. Amount fields use exact decimal comparisons with your absolute tolerance. Date fields require YYYY-MM-DD. Text retains case and internal spaces after trimming edges.
5. Investigate exceptions. Check trials, free plans, manual exceptions, grace periods and delayed exports. Missing records alone do not establish a debt, security incident or loss.
6. Keep the report under your control. Download JSON or spreadsheet-safe CSV. Files stay in the tab during comparison; exported reports should follow your organization’s data rules.

For automation builders

The current hosted pilot is a browser evaluation tool. There is no hosted paid API. Read the machine-readable service description for its actual capabilities. Payment protocols and search listings do not by themselves establish demand.

Try three worked examples

Compare synthetic billing and access records, duplicate IDs, and decimal/date differences. Download the CSV pairs, inspect the rules and run each example locally to see the expected findings.

Evaluate the workflow

Use a synthetic example first. Then record how long setup and review take, which findings are useful, and which are explained by legitimate exceptions. Repeat with a later comparable export before deciding whether automation is worth paying for.