UK payment visibility. Settlement confirmation. Reconciliation-ready data.
A Open Banking PIS and AIS for finance teams that need more than a status page.
The customer pays. You get confirmation. Then you wait for the money to show up.
That is not a startup founder describing a problem. That is the daily experience of UK finance operations teams. The payment tracker shows “sent.” The bank knows what happened next. Nobody else does.
Most payment tracker tools were built to answer one question: did the payment instruction leave? Finance teams running at volume need three more. Did it arrive? Was the reference intact when it did? Is the data structured enough to close the reconciliation without a manual step?
Those three questions are where most payment trackers break down.
Research published in March 2026 found that 85% of UK firms still rely on fully or mostly manual reconciliation. Not because they haven’t invested in technology. Because the payment tracker is showing them initiation status, and the reconciliation needs settlement data.
“The payment tracker problem isn’t usually the tool. It’s what the tool has access to. A tracker connected only to initiation events can tell you the payment left. It can’t tell you it arrived. That gap is where the finance team spends Friday afternoon.” – Ravi, Finexer
TL;DR
A payment tracker monitors payment status from initiation through to settlement. Most UK payment tracker implementations stop at initiation – they show that a payment went out, not that it arrived, whether the reference survived transit, or whether the data connects to the reconciliation layer. Industry research from March 2026 found 85% of UK firms still reconcile manually. The fix is not a better tracker. It is connecting the tracker to bank-confirmed settlement data via Open Banking AIS – delivering per-payment webhook confirmation and structured transaction data at the point of settlement, not in the following morning’s batch file.
Key Takeaways
What is a payment tracker?
A payment tracker monitors payment status from initiation through settlement, surfacing reference data and timestamps at each stage. Its usefulness depends on what data it receives. A tracker connected to initiation only shows a payment left. One connected to bank settlement data shows it arrived.
Why does international payment tracking break down?
Three problems compound: references are stripped by correspondent banks, settlement timelines vary by corridor with no fixed window, and status updates arrive in T+1 batch files rather than at settlement. The result is a payment tracker showing “processing” for 24-48 hours with nothing actionable.
What does a connected payment tracker actually require?
Per-payment webhook at settlement – not batch updates. References embedded at initiation and returned confirmed at bank settlement. When PIS embeds a reference and AIS returns it confirmed, the tracker closes the loop between the payment that left and the credit that arrived.
Why Do UK Payment Trackers Still Fail Finance Teams?
What Is the Real Scale of the Payment Visibility Problem in the UK?
The payment visibility problem has a number attached to it.
SWIFT reported in April 2025 that the financial industry spends an estimated $1.6 billion annually investigating delayed and missing payments – each investigation typically taking five to ten working days to resolve. That cost sits almost entirely in manual investigation time.
In the UK specifically, 85% of firms still rely on fully or mostly manual reconciliation. The same research found that 39% of UK firms only see their FX costs after settlement – nearly four in ten businesses lack real-time visibility over one of their biggest cross-border cost drivers.
The payment tracker market has grown. The manual work has not shrunk.
Three structural reasons explain why:
The tracker connects to the platform, not the bank. Most payment tracker tools surface data from the payment platform – the instructions that went out. The bank settlement event is a different system. When the bank rejects a payment or settles it with a modified reference, the payment tracker has no event to update on. It shows “processing” until the next batch file arrives.
The finance team sees “sent.” The bank statement the following morning shows the credit. The 16-hour gap in between is invisible to the tracker.
International payment tracking breaks at correspondent banks. SWIFT’s own research identified lack of visibility over funds once sent as a core problem in international payments – tracking visibility is lost as payments pass through intermediary banks. A reference embedded at initiation – “INV-2024-089” – regularly arrives at the destination as “089” or nothing at all. The international payment tracking layer receives a settled credit with no usable identifier.
A human investigates. At 10 international payments a week, this is inconvenient. At 200, it is a role.
Reconciliation data arrives too late. The payment tracker and the accounting system are separate tools. The tracker shows “settled.” The ledger shows the invoice as open. Someone manually connects them. This step exists because the payment tracker was not built to push settlement data into the reconciliation workflow.
For finance operations teams evaluating how payment infrastructure changes the data available to a payment tracker, the real-time transaction monitoring guide covers how webhook-based settlement events differ from batch-based status updates in production environments.
What Does Effective International Payment Tracking Actually Require?
How Should a Connected Payment Tracker Work Across Domestic and International Flows?
| Tracking Requirement | Standard Payment Tracker | Connected Payment Tracker |
|---|---|---|
| Settlement confirmation | Not available – tracker shows “processing” until next batch update | Per-payment webhook at bank settlement – status confirmed near settlement |
| Reference continuity | Initiation reference only – no visibility into whether it survived transit | Reference embedded at initiation, confirmed at bank settlement via AIS |
| International payment tracking | Status unclear for 24-48 hours – no per-stage updates through correspondent chain | Per-payment status at each stage – initiated, in progress, confirmed |
| Failed payment detection | Discovered in next-day statement or via recipient complaint | Webhook failure notification near-immediately with reason code |
| Reconciliation connection | Manual step – tracker data does not connect to accounting system | Structured transaction data with reference connects to reconciliation layer |
| Scale | Manual overhead grows linearly with payment volume | Structured data layer reduces manual overhead relative to volume |
The gap between columns is not a software feature gap. It is a data layer gap.
Fluxa founder Paul Jones launched a UK payment visibility startup in 2026 specifically because of this problem. His description: “The customer pays, you get a confirmation, and then you just wait for the money to show up. Nobody tells you where it is in between or why it’s taking however long it takes.”
That is the standard payment tracker experience for UK SMEs and finance teams alike. For international payment tracking, the visibility gap is larger and the investigation overhead is higher.
For platforms evaluating the API infrastructure that feeds payment tracker tools, the payment integration via API guide covers how PIS and AIS connect at the infrastructure level to provide per-payment status and reconciliation data.
How Does Finexer Support Payment Tracker Workflows?
What Data Does Finexer Provide to Improve Payment Visibility?
Finexer is not a payment tracker dashboard. It doesn’t build finance reporting tools, manage ledgers, or replace ERP systems.
Finexer provides FCA-authorised Open Banking PIS and AIS – the UK payment initiation and bank transaction data layer that payment tracker tools and finance operations platforms use to surface accurate, timely payment status.
The payment visibility problem has two parts: the payment that left, and the bank data confirming it arrived. PIS handles the first. AIS handles the second. Together they close the loop the tracker needs.
PIS – the payment that leaves with a reference:
- Pay by Bank via Faster Payments – reference embedded at initiation, webhook at each lifecycle stage
- Bulk Payout – per-recipient references and status in a single API call
- Per-payment webhook: initiated, in progress, confirmed, or failed – reason code near-immediately on failure
AIS – Transaction and Invoice Tracker – the bank confirmation that closes the loop:
- Per-payment bank transaction data near settlement – not T+1 batch
- Payment reference from PIS initiation returned confirmed at bank settlement
- Consistent JSON across almost all major UK banks
- Up to 7 years of transaction history for exception resolution
For international payments: GBP to support EU and global recipients via Open Banking payment initiation. Settlement timelines depend on recipient location, payout network, and banking partner routing.
- Usage-based pricing, no setup fees, deployment measured in weeks
- FCA-authorised (FRN 925695)
For platforms managing high-volume payout operations where per-payment tracking matters at bulk scale, the Finexer bulk payment services guide covers how per-recipient references and webhook status work across bulk disbursements.
“The payment tracker failures I see in UK finance teams aren’t separate problems. They’re the same problem repeated: the data layer doesn’t reach the bank. Fix that and most of the manual work disappears.” – Ravi, Finexer
What I Feel
Industry research from March 2026 found that despite significant investment in AI and automation, 85% of UK firms still rely on fully or mostly manual reconciliation.
That is not a failure of effort. Finance teams have invested in tracking tools, accounting software, and process improvements. The issue is structural: the tracker is connected to the payment platform. The platform is not connected to the bank. The reconciliation needs bank data. Someone bridges the gap manually. Every time.
The fix is not a better dashboard. It is connecting the tracker to bank-confirmed settlement data – arriving at the point of settlement, not the following morning.
Common Use Cases
Finance Operations Teams
Finance teams managing high-volume payment runs need per-payment webhook confirmation at settlement. A payment sent at 2pm should show confirmed by 2pm – not in tomorrow morning’s statement. Exceptions surface immediately, not at month-end when the trail is cold.
ERP and Accounting Platforms
ERP platforms need structured transaction data that connects to open payables. When AIS delivers bank-confirmed settlement data with the same reference used at PIS initiation, the ledger updates from the payment flow – not from a manual reconciliation step.
Platforms Handling International Payouts
Platforms disbursing to supported EU and global recipients need international payment tracking that surfaces per-stage status updates. Settlement timelines vary by recipient location and network routing. Per-payment updates reduce the support overhead from recipients asking where their payment is.
Billing and Invoicing Platforms
When a customer pays via Pay by Bank and the payment tracker receives bank-confirmed settlement with the pre-filled invoice reference intact, the invoice closes automatically. The reference that created the payment closes it.
How do UK businesses track international payments effectively?
Most UK businesses currently track international payments via bank portals or end-of-day statements – T+1 visibility at best. Effective international payment tracking requires per-stage webhook updates from initiation through settlement, with payment references that survive the correspondent bank chain intact. Settlement timelines vary by recipient location, payout network, and banking partner routing – there is no fixed international settlement window.
What is UETR and how does it help payment tracking?
UETR stands for Unique End-to-End Transaction Reference – a 36-character identifier for SWIFT payments under ISO 20022. For UK Open Banking Faster Payments, the equivalent is the reference embedded at initiation by the PISP. Unlike UETR, which depends on correspondent bank handling, an Open Banking reference is within the platform’s control to preserve through bank confirmation.
Why do payment trackers fail at scale?
At low volumes, manual tracker checks are manageable. As volume grows, a tracker requiring manual checks becomes a workflow itself. Most payment trackers receive batch data rather than event-driven webhooks. A tracker fed by per-payment webhook events scales because data pushes automatically – the data layer changes, not the software.
Fix your payment tracker data layer with Finexer Open Banking PIS and AIS.
About the Author
Ravi Ranjan
Ravi Ranjan is Co founder & CEO of Finexer