Payment Reconciliation:
An Exception Queue for
Provider Disagreements
A six-field investigation worksheet
Dmytro Nasyrov PhD
The six fields in the queue
Field
Investigation job
Internal payment reference
Identify the candidate internal record.
Provider event reference
Identify the provider and its source record.
Status vocabulary
Preserve the raw label and vocabulary revision.
Amount and currency
Retain the reported value and its currency.
Evidence pointer
Locate the source record or name the missing evidence.
Exception owner
Name the role responsible for the next check.
Two synthetic provider records
Fictional records and labels. No real payment or executed test.
Field
Record A
Record B
Internal reference
P-731 / candidate
P-731 / candidate
Provider event
Provider A / A-17
Provider B / B-09
Raw status / vocabulary
completed / A-v1
approved / B-v1
Amount and currency
100.00 EUR
100.00 EUR
Evidence pointer
E-A-17 / sample record
Missing source record
Exception owner
Payments analyst
Provider liaison
The unresolved identity check
Both rows carry the candidate reference P-731 and 100.00 EUR. The supplied example contains no evidence that A-17 and B-09 describe the same external transaction.
Keep both rows in the queue. Ask the provider liaison for the source record and the reference binding needed to investigate B-09.
Matching amounts alone leave the identity question open.
The status-vocabulary mapping
Source label
Interpretation in this example
completed / A-v1
Meaning awaits the A-v1 definition.
approved / B-v1
Meaning awaits the B-v1 definition.
Retain each raw label. Attach the approved mapping revision before assigning a shared internal status.
The example establishes no equivalence between these fictional labels.
The evidence handoff
Handoff entry
Record for B-09
Owner
Provider liaison
Missing evidence
Source record and transaction-reference binding
Next check
Locate the permitted record and document the binding
Current disposition
Waiting for evidence
Use approved access to payment records. The worksheet contains no account credentials or customer data.
Provider formats retain their own meaning
Stripe distinguishes Dashboard payment status from PaymentIntent status. Record the object and field alongside the label.
Source: Stripe payment status updates
Adyen Standard webhooks include eventCode and success. The success field reports the outcome of that event.
The review closure conditions
Condition
Evidence the reviewer needs
Identity
A documented link between the source and internal record.
Vocabulary
The applicable source definition and mapping revision.
Evidence
A permitted, retrievable source record for the conclusion.
Ownership
A named reviewer and the recorded basis for closure.
B-09 remains open: its source record and reference binding are missing. Queue closure alone establishes no settlement result.
Payment integration and reconciliation scope
When provider records disagree, Pharos Production offers payment solutions development covering provider integrations and reconciliation tests. Agree source matching, status mapping and exception ownership within the implementation scope.
This proposed queue gives a reviewer a place to record unresolved differences. Reconciliation conclusions require the evidence and controls agreed for the payment flow.
About the author
Written by Dmytro Nasyrov PhD, software architect with 24 years of production experience. Dmytro is the founder and CTO of Pharos Production. He works on production software architecture for FinTech, AI, Web3 and blockchain systems.
Dmytro Nasyrov. Photo supplied by the author.