Reconcile
0d ago
Pipeline sync
Oct 5, 2026, 11:39 AM ET (pipeline_incremental) 0d ago
Sage GL delivery
Oct 5, 2026, 1:23 AM ET — window through Sep 30, 2026 — misses the current month 0
Unassigned slate batches
all batches route 0
Unmapped in-use codes
every in-use code maps
Pipeline sync
Oct 5, 2026, 11:39 AM ET (pipeline_incremental) 0d ago
Sage GL delivery
Oct 5, 2026, 1:23 AM ET — window through Sep 30, 2026 — misses the current month 0
Unassigned slate batches
all batches route 0
Unmapped in-use codes
every in-use code maps
All entities
| Month / Entity | Sage Net Revenue | NGP Contributions | Difference | Status | Run |
|---|---|---|---|---|---|
| ▶ Oct 2026 (1 entity) | $0.00 | $16,000.00 | -$16,000.00 | ✗ Mismatch | Build JEs → |
| 314 Action (101) | $0.00 |
$16,000.00
1 contribution |
-$16,000.00 | ✗ |
Note: reconciliation is penny-exact — any non-zero gap is a Mismatch. Reconciling items that legitimately have no NGP counterpart (interest, list rental, non-NGP transfers, exclusions, unassigned slate) are carved into their own rows and removed from the compared totals, so what remains should net to zero. A known gap you can't clear yet (e.g. a Sage-side reclass still pending) can be Acknowledged so it stops blocking the close; if that gap later changes, the acknowledgement goes stale and the row re-surfaces. The 401 + 403 row is compared combined because the NGP export can't split Impact Slate HD from JF.