Mappings
Every data point across projects
The dimensions, objects, and derivations the organization consolidates from every connection, how source values reconcile into them, and where each one comes from.
Completed, not invoiced
What counts as completed work, what closes it, and which work never invoices and should not be chased.
5 approved1 need review1 suggested
Configuration
Derivation · reads 2 connections
Reconciles into
Completed, Not InvoicedCOMPLETED_NOT_INVOICED
3 canonical values · 7 treatments
Time basis
Business days since completion
The date every input aligns on.
Formula
CAR_CYCLE_EVENTS WHERE event_type IN ('completed', 'released') AND NOT EXISTS (GROSS_REVENUE.work_order_id = cycle.work_order_id) AND business_days_since(completed_at) >= 2
Canonical values
3 targets. Every approved treatment resolves to one of these.
- Awaiting invoiceOPENCompleted, no invoice after two business days
3 values - InvoicedINVOICEDA Sage invoice names the work order2 values
- Never invoicesNEVERListed and flagged, not chased1 values
Tell Eagle how to reconcile
Plain English. Eagle re-treats the matching rows and says what it did.
Instructions in effect
Nothing yet. Anything you say is applied to the table and kept for new source values.
Select rows to preview how they combine into a canonical value. Click a source value to inspect or edit its treatment. Hover a confidence to see why.