Funnel reconciliation
Decision Cloud decisions vs LoanMeld originations - count parity by declared timezone
America/New_York (EDT)Counting by: created date2026-06-16 → 2026-07-15
Decision Cloud side counts by: linked loans.created_at; lead submitted_at while no loan exists
LoanMeld side counts by: loans.created_at
Both sides are aligned to America/New_York (EDT) before any date filter applies — cross-system counts compared under different zones or date fields are not parity evidence.
DC accepted leads
0
accepted / redirected, in declared range
LoanMeld loans
0
0 VIP-tagged
Matched pairs
0
joined on stored DC lead id
Diff rows
0
0 DC-only - 0 LM-only (0 unexplained)
Declared range and facets
both systems align to the declared timezone and date field before any count is compared
Loans Count:…live preview
Origination-source segments
each segment reconciles independently — a facet, not tribal memory
| Segment | Loans | Matched to DC | Missing decision record |
|---|
Accepted leads with no loan (0)
Decision Cloud accepted and redirected these leads; LoanMeld never booked a loan — the funnel-drop direction of the diff
No accepted leads are missing a loan in the declared range.
Loans with no decision record (0)
loans in the declared range with no stored Decision Cloud lead — lead-channel rows here are the measurable #271 hole
Every loan in the declared range carries a stored decision record.