HOW LOANRECON WORKS
Follow every payment from processing to settlement.
Loan payments create records across multiple systems. A payment may be processed successfully, posted to the borrower’s loan, and settle into the bank account at different times and with different identifiers.
LoanRecon brings those events together at the individual loan and payment level to automatically verify that what was processed, posted, and settled actually matches.
Bring payment activity together
LoanRecon is designed to ingest payment activity from the systems and data sources already involved in your workflow.
The data does not need to come from the same system, use the same format, or arrive the same way. LoanRecon normalizes incoming records into a common payment model that can be reconciled across the payment lifecycle.
SFTP files
NACHA files, processor reports, settlement files, posting files, return files, CSVs, and scheduled exports.
Email and attachments
Reports and files delivered to shared reconciliation, accounting, or operations inboxes.
APIs
Payment processors, servicing systems, banking systems, or other platforms that expose transaction data programmatically.
Webhooks
Real-time events such as payment success, failure, return, or status changes.
Database and data warehouse feeds
Payment and servicing activity stored in operational databases or a data warehouse.
Scheduled or manual file ingestion
Files from systems where direct automation is not available or necessary.
LOANRECON
The source doesn’t have to look the same. LoanRecon turns different records into a common payment lifecycle.
Connect the records that belong together
Once payment data is normalized, LoanRecon matches related events across systems to determine which processor transaction, loan posting, bank settlement, return, and other payment events belong together.
Records may not share one universal identifier. LoanRecon can use the identifiers and payment attributes available in the underlying data to connect related activity.
Loan / account identifier
Transaction identifier
ACH trace identifier
Payment amount
Processing or effective date
Settlement timing
Different source records ↓ one identified payment
Payment #07241
Loan #483921
Reconcile down to the individual loan
LoanRecon is designed to reconcile the underlying payment activity at the loan level, not just compare aggregate processor, servicing, and bank totals. Each matched payment is associated with the underlying loan so teams can trace how money moved for a specific borrower account.
LOAN #483921
Payment #07241 — $1,842.16
Processed — Verified
Posted — Verified
Settled — Verified
Status: Reconciled
Payment #08432 — $1,250.00
Processed — Verified
Posted — Verified
Settlement — Not found
Status: Settlement break
Batch reconciliation tells you that something is wrong. Loan-level reconciliation helps show which loan and payment caused it.
Build a timeline for every payment
LoanRecon brings related events together chronologically so an operator can understand the complete lifecycle of a payment without reconstructing it manually across different systems.
Payment #07241
Loan #483921
10:03 AM · Processed
Processor · $1,842.16 · Verified
↓
10:05 AM · Posted
Loan system · $1,842.16 · Verified
↓
Next business day · Settled
Bank · $1,842.16 · Verified
RECONCILED
Instead of checking each system independently, the payment can be viewed as one lifecycle from initiation through settlement.
Query the payment history for any loan
LoanRecon gives operations teams a loan-level view of payment activity across connected systems. Search for a loan and see related processor events, servicing postings, settlement activity, returns, exceptions, and reconciliation status together.
Search: Loan #483921
LOAN #483921
AUGUST 12
Processor transaction — $1,842.16
Posted to loan — $1,842.16
Bank settlement — $1,842.16
Status: Reconciled
AUGUST 28
Processor transaction — $1,250.00
Posted to loan — $1,250.00
Bank settlement — Not found
Status: Settlement break
Instead of reconstructing a payment timeline by searching across multiple systems, teams can query the loan directly and see the relevant payment activity together.
Surface the payments that don’t reconcile
Payment #08432
Loan #483921
Processed — Verified
Posted — Verified
Settlement — Not found
SETTLEMENT BREAK DETECTED
LoanRecon continuously checks the expected payment lifecycle and surfaces payments where an expected event is missing, inconsistent, duplicated, returned, or otherwise does not reconcile. It identifies the payment and the point in its lifecycle that requires investigation; it does not assume every exception can be resolved automatically.
Start with the payment, not the variance
Loan system postings $124,800
Bank settlements $123,550
Variance $1,250
Traditional reconciliation may tell the team that two totals do not match. The investigation still requires determining which payment caused the difference and tracing that payment across systems. LoanRecon reconciles the underlying activity down to the individual loan.
$1,250 batch variance
↓
LoanRecon
↓
Loan #483921
Payment #08432
$1,250.00
Settlement missing
Think this could help your payment reconciliation process?
We’re talking with loan servicing and operations teams about how reconciliation works today and where the hardest investigations happen.
Let’s Talk Payment Recon