—
Needs action
a step is yours to take
Work these
iNeeds action
Rows with a step you can take now.
Rows with a step you can take now.
—
Set aside
by you · bring back when ready
Yours to bring back
iSet aside
Rows you chose to defer. They never go overdue. Use Bring back when ready.
Rows you chose to defer. They never go overdue. Use Bring back when ready.
—
Waiting
blocked elsewhere · no step until it arrives
No step yet
iWaiting
Blocked until something arrives: FX JE approval, a journal another team posts, an AP reply, or something you marked as waiting for.
Blocked until something arrives: FX JE approval, a journal another team posts, an AP reply, or something you marked as waiting for.
—
Returned Payments
High Priority
iAutomation Gap impact (Build Alpha 4b)✗ Not eliminated. Reconciliation pairs the bank-side payment + return; no system-side row is created (AP keeps the original `negotiable` open to reissue). Requires AP follow-up — Automation Gap cannot trigger AP's re-initiation workflow.
—
Duplicate partial refund
High Priority
iAutomation Gap impact (Build Alpha 4b)✗ Not eliminated. Detection approach not yet defined. Identifying which bank line is the original payment vs. the reissue requires investigation; the partial-refund math (credit applied to future invoice + remainder refunded) doesn't share a payment reference. Cannot be automated until detection logic is designed.
—
FX Pending JE
Medium Priority
iAutomation Gap impact (Build Alpha 4b)◑ Partial. Cannot auto-reconcile until cash management creates a manual journal entry in Fusion for the FX delta. Once the JE flows through to the system side, Automation Gap auto-matches. The JE creation itself stays manual.
—
DD Pending
Needs Review
iAutomation Gap impact (Build Alpha 4b)? Unconfirmed. DD matching rules vary by sub-type and are mostly bank-specific (per Joanne, mostly JPM). Awaiting confirmation from Allison and Johanne on whether any DD sub-types can be auto-matched. May require manual handling indefinitely.
—
Other Unmatched
Needs Review
iAutomation Gap impact (Build Alpha 4b)✓ Mostly eliminated. Catch-all for items that don't fit a specific reason. Items our engine can match via reference normalization never reach this queue — they reconcile automatically. Only genuine mismatches remain here: GL entry truly missing, reference keyed wrong, no comparable pair exists.
—
Awaiting JE Approval
you loaded it · approval pending
—
Awaiting JE
posted by another team
—
Awaiting AP reply
sent to AP · no answer yet
—
Waiting on…
your note says what
—
Matched without a reference
amount + source + date window
Spot-check these
iMatched without a reference — why you're seeing this
The reference field was empty, so these matched on amount, source type and a date window. FX variances don't recur (the rate moves, so each amount is effectively unique), which is what makes the fallback safe here. Worth spot-checking during pilot.
The reference field was empty, so these matched on amount, source type and a date window. FX variances don't recur (the rate moves, so each amount is effectively unique), which is what makes the fallback safe here. Worth spot-checking during pilot.
—
Matched with a reference
reference present · amounts net to zero
Optional
iWhy spot-checking is optional here
A unique reference plus date and amount cannot coincidentally agree. These are certain, not confident — no score is involved. Open any row if you want to check one; we don't expect these to be wrong.
A unique reference plus date and amount cannot coincidentally agree. These are certain, not confident — no score is involved. Open any row if you want to check one; we don't expect these to be wrong.
Status:
Unmatched:
Reconciled:
Workflow:
Filter:
0 selected
Unreconciled
Reconciliation Workbench · Bank Statement vs. General Ledger
—
| Date | Bank Ref | Vendor / Payee | Bank | CCY | Amount | Type | Amount Variance | Match Status |
|---|