How do I reconcile numbers that disagree between two systems?

iDBQuery reconciles numbers that disagree between two systems by querying both as one model and comparing them row by row. Connect each source, ask iDBQuery to match the figures, and it surfaces the exact records that differ — with citations to both sides — so you find the cause of the discrepancy instead of guessing.

When the same number reads differently in two systems — sales in your database vs the finance ledger, inventory vs the warehouse export — reconciliation usually means dumping both to spreadsheets and eyeballing them. iDBQuery makes it a query.

  • Compare in place — connect both systems and ask "where do these totals disagree?" iDBQuery joins them on the right keys and returns the gaps.
  • Drill to the rows — it doesn't just say the totals differ by an amount; it shows the specific records present in one and missing or different in the other, cited on both sides.
  • Explain the cause — hand it to the Analyst agent and it investigates: timing differences, duplicate entries, a mismatched currency or status, a dropped record.
  • No data movement — both sources are queried live, so you reconcile against current data, not last week's export.

The value is in the trail. Because every figure cites its source row in whichever system it came from, you can prove which side is wrong and why — a refund booked twice, an order counted before it shipped, a rounding rule applied inconsistently. iDBQuery turns a multi-hour, error-prone manual cross-check into a question you can ask and re-ask as the data changes.

Updated 2026-06-22