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.
AP payment queue
What is ready for the run, what is held and why, and how a paid item is cleared by the bank.
9 approved1 suggested
Configuration
Derivation · reads 4 connections
Reconciles into
AP Payment QueueAP_PAYMENT_QUEUE
4 canonical values · 10 treatments
Time basis
Next payment run (Thursday)
The date every input aligns on.
Formula
PAYABLES WHERE stage = 'approval' AND payment_reference IS NULL AND VENDORS.payment_profile_approved AND due_date <= next payment run
Canonical values
4 targets. Every approved treatment resolves to one of these.
- Ready to payREADYApproved, open, vendor cleared
2 values
- HeldHELDVendor, hold, or due date blocks it
3 values
- Paid, awaiting clearingPAIDLeft Sage, not yet at the bank
2 values
- ClearedCLEAREDBank debit matched
1 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.