FNB Williamson · Operations
Bridge Monitor
Every file and API bridge LEDGERLINK runs for this bank. 6 of 7 healthy. This screen is the honest answer to “what happens when a file fails?”
90-day window
Bridges
Armored Deposit File
Brinks → LEDGERLINK Cash Logistics · SFTP · Daily 7:30 PM ET
Healthy1,120 records / 90d
99.90% uptime
Last run 1d ago — 3 locations, all credited
Core Balance API
FNB Core → LEDGERLINK Aggregation · API · 4-minute poll
Healthy812,400 records / 90d
99.99% uptime
Last run 4h ago
FX Desk Position API
FNBW International → LEDGERLINK Aggregation · API · 15-minute poll
Healthy86,200 records / 90d
99.95% uptime
Last run 4h ago
Lockbox Remittance (SFTP)
Fifth Third Remittance → LEDGERLINK Lockbox · SFTP · Daily 6:00 AM ET
Healthy2,988 records / 90d
99.93% uptime
Last run 13h ago — 34 payments, $61,230.75
Presentment Feed (In-clearing)
FNB Core → LEDGERLINK Match Engine · API · Hourly + teller real-time
Partial41,230 records / 90d
99.88% uptime
Last run 5h ago — 2 of 49 rows failed validation: missing check number
QuickBooks → Issue File
QuickBooks Online → LEDGERLINK Positive Pay · API · Daily 6:00 AM ET
Healthy3,912 records / 90d
99.97% uptime
Last run 13h ago — 47 checks loaded, 0 errors
Return File (End-of-day)
LEDGERLINK Positive Pay → FNB Core · SFTP · Daily 4:30 PM ET
Healthy214 records / 90d
100.00% uptime
Last run 1d ago — 1 return item transmitted
Design principle
A failed row never disappears. It is quarantined, shown here with the exact field and reason, and a ticket is cut. The customer's register is never silently wrong.