Wire Transfer
Transaction codes: 495 (USD) · 514 (FX / foreign currency)
End-to-End ID
bank side
Payment Reference Number
GL side
confirmed

String comparison. Both fields must match exactly, including leading zeros.

Amounts match exactly. Should reconcile automatically once reference formats align. If unmatched: the GL candidate with the matching Payment Reference Number is shown — verify and confirm.
Bank amount is in foreign currency; GL amount is the USD equivalent. Amounts will not match. A manual journal entry is required at month end to record the FX conversion before reconciliation can be completed.
Failed Payment Duplicate Amount Variance

Amount Variance applies to FX wires only — expected due to currency conversion.

#
Check
Standard checks and Matthew Bender checks (handling may differ — see open question)
Check Number
bank side
Reference / Transaction Number (same value)
GL side
confirmed

Direct 1-to-1 lookup. Check number is a string — leading zeros must be preserved in both fields for the match to work.

Check clears the bank. System matches check number on bank side to Transaction Number in GL. If Fusion auto-reconciles: no action needed. If unmatched: one GL candidate is shown with the matching Transaction Number — verify and confirm.
Failed Payment Duplicate

Amount Variance on checks is not a confirmed scenario — a check amount is fixed at issuance. Flagged for cash management team confirmation.

Matthew Bender checks are processed differently and may not follow the standard check number matching model. Confirm with cash management team before reconciling these.
EFT (Electronic Funds Transfer)
ACH-based payments; matching field pending confirmation
End-to-End ID
bank side
Payment Reference Number
GL side (assumed)
unconfirmed

Assumed same as wire. Waiting on confirmation from cash management team's Philippines contact.

Once the matching field is confirmed, expected to follow the same pattern as USD wires — string comparison on the reference field, 1-to-1 match, should reconcile automatically when reference formats align.
Failed Payment Duplicate
Matching field not confirmed. Question to ask: "Can you confirm whether Payment Reference Number is the matching field for EFTs, the same way it is for wires?"
Direct Debit
Citibank Credit Card · PA Supreme Court · RELX CENTRE CTA US (tx code 455)
End-to-End ID
bank side (identifying label only)
? — matching field unconfirmed
GL side
unconfirmed

Vendor (Counterparty) used as the identifying label. The specific field used to match bank side to GL side has not been confirmed — no transcript basis for any particular field.

Direct debits do not go through AP — they are posted as manual journal entries in the GL. The user identifies the debit on the bank side, locates the corresponding journal entry, and reconciles manually. End-to-End ID is long (16+ digits) and unique per transaction.
Failed Payment Duplicate
Matching field not confirmed. Question to ask: "When you reconcile a direct debit, what field on the bank side and what field on the system side are you matching on?"
Sweep (ZBA)
Transaction codes: 275 (standard sweep) · 575 (negative / return — handling unconfirmed)
Many-to-many batch reconciliation. Multiple bank statement lines are matched against multiple journal entries. The two sides must sum to the same total — reconciliation completes when the difference is $0.00.

No single identifier links bank to GL — balance is the confirmation.

ZBA sweep moves money between LexisNexis accounts daily. The user selects the relevant bank entries and journal entries, verifies both sides balance to zero, then reconciles as a batch. Code 575 entries (negative amounts) are excluded from the default selection and handled separately.
Amount Variance

If batch totals do not balance to $0.00, there is a variance that must be resolved before reconciliation can complete.

Transaction code 575 meaning unconfirmed. Question to ask: "What does code 575 mean and how do you handle those entries — do they get reconciled separately?"