Skip to content

Reconcile an invoice discrepancy report

As a member of Accounting Functions, I want to understand why a payment amount doesn't match an invoice amount on a discrepancy or reconciliation report, so that I can tell a real problem apart from expected behavior before escalating it.

Screens: Reports > Accounting (Paid Invoice Discrepancy report), Accounting > Process Remittances (Checkoff popup), Reports > Accounting (Journal Entry by GL Code)

The core mental model: allocated vs. overage

This is the single most valuable concept in this chapter for a new hire. The Paid Invoice Discrepancy report only compares the invoiced amount to the Dues-allocated portion of a payment — any overage from a payment (money received beyond what was strictly allocated to Dues) is expected to not show on that report until it's reallocated.

\"Disappearing\" money is usually a display gap, not a ledger error

A real historical bug had the Checkoff popup, Cash Receipt, and this Discrepancy report all under-reporting overage on the same payment — the member and jobsite ledger records were correct the entire time; three display surfaces just weren't showing the full picture. (IUOE-2745, IUOE-2491) Before escalating a "missing money" claim from one of these reports, check the member/jobsite ledger directly — if the ledger is right, you're looking at a reporting-surface gap, not a financial one.

Steps

  1. Run the Paid Invoice Discrepancy report for the employer/period in question.
  2. If a discrepancy shows, open the Checkoff popup on the specific payment and compare Amount Paid vs. Amount Applied/Allocated directly — don't trust the summary report alone for a borderline case.
  3. Cross-check against Journal Entry by GL Code (see Post a payment and complete the deposit for the posted/deposit-completed prerequisite that report needs) — its bottom "Checkoff batch entries / CheckoffTotal / Grand Total" box should match the body's own Report Totals.

The GL Code report's own totals can diverge from its body

This happened for real (root cause of IUOE-2798) and is worth checking every time, not just when something already looks wrong — a divergence between the summary box and the report body is itself a signal, independent of whatever discrepancy you started investigating.

Things to watch out for

Bucket payment allocation math is only confirmed for one scenario

Bucket payment allocation (amount paid vs. amount applied) is confirmed working only for a full walk-in payment against an adjusted bucket. Phone payment, employer payment, and unadjusted-bucket scenarios have shown apparent mismatches in testing and are not confirmed reliable — don't generalize a bucket-payment fix from one payer/channel combination to all of them. (IUOE-2705)

Fair Share members have a different invoice-inclusion gate

If a Fair Share member is missing from an invoice/remittance where you expect them, check their card signed date first — Fair Share inclusion is gated on that field specifically, a different rule than regular dues members use. (IUOE-2703)

Invoice member sort order is a per-employer config field, not a bug

If invoice ordering looks wrong, check the Employer Plus "Invoice sort order" field before filing a new ticket — it's commonly set to jobsite-then-member instead of Member Alpha, and that's a config correction, not a defect. (IUOE-2447)

A \"random\" load failure is often concurrent-user timing

Invoices that "don't load consistently" in Process Remittances have traced back to a race condition — another user finalizing the same invoice mid-session stales out your screen's reference to it. Before filing a new bug, note who else was active in the system at the time. (IUOE-2136)