Payment operations
Post lockbox, ACH, card and branch payments, clear exceptions and reconcile the day's postings against the bank account.
Financial Services / Loan Servicing
Loan servicing software for everything after the loan funds
Origination gets the attention, but most of a loan's life is servicing: payments to apply, statements to send, late accounts to work and payoffs to quote. Agnotic Technologies builds loan servicing software for banks, credit unions and lenders that applies every payment the same way and keeps a record of each rule it followed.
Waterfall
Payment rules held as configuration
Statements
Built from the loan ledger
Delinquency
Day-count triggers with owners
Trusted by global innovators
Industry Overview
What is loan servicing software?
Loan servicing software is the lending system that runs a loan from funding to payoff: it applies payments, sends periodic statements, works delinquent accounts and hardship plans, reports to credit bureaus and quotes payoff amounts. Agnotic Technologies builds it for lenders as a custom system or as a servicing layer beside an existing core.
Who it is for
Who uses loan servicing software?
Servicing touches more teams than origination does. Each one needs its own queue and its own view of the same loan.
Collections and loss mitigation
Work late accounts by days past due, record promises to pay and review hardship applications against the lender's programs.
Customer service
Answer balance, escrow and payoff questions from one screen, and log disputes and error notices with a due date.
Finance and investor reporting
Need interest accruals, charge-offs and remittances that tie to the general ledger, plus reports for loan owners when you service for others.
Industry Challenges
Where does loan servicing go wrong?
Servicing errors are quiet. They surface months later as a complaint, a bureau dispute or an audit finding. These are the ones we look for first.
Partial payments sit in suspense with no rule for when they are applied, so the borrower looks late while enough money waits unapplied.
The payment waterfall is coded into the posting job, so changing the order of fees, interest and principal needs a release and nobody can show which order applied last year.
Statements come from a reporting copy instead of the loan ledger, so the amount due on paper differs from the amount the system expects.
Delinquency day counts restart from the wrong date after a due date change, so outreach and late fees fire on the wrong day.
Bureau files are built from a spreadsheet export, so a corrected account keeps reporting late until someone fixes it by hand.
Payoff quotes are worked out manually when escrow or fees are outstanding, and two agents give the borrower two different figures.
Servicing events
What should the system do at each servicing event?
This is the event table we build servicing rules from. Each event has a system action, a record it must write and a rule that shapes it. Mortgage rules are cited where they apply; other consumer and commercial loans follow your loan agreement and the law your counsel confirms.
| Event | System action | Record it must write | Rule that applies |
|---|---|---|---|
| Full payment received | Apply through the waterfall as of the date of receipt | Payment with receipt date, effective date and the split by bucket | Crediting on receipt for mortgages, 12 CFR 1026.36(c)(1) |
| Partial payment | Hold in suspense until the total covers a periodic payment, then apply it | Suspense balance with the date each amount arrived | Your partial payment policy; suspense handling in 1026.36(c)(1)(ii) for mortgages |
| Missed payment | Start the delinquency clock from the oldest unpaid due date and open a collections item | Days past due, any late fee assessed and each contact attempt | Live contact by day 36 and written notice by day 45 for mortgages, 12 CFR 1024.39 |
| Hardship request | Open a loss mitigation case, collect documents and run program eligibility | Application date, documents received, decision and reason | Your hardship programs; Regulation X loss mitigation procedures for mortgages |
| Payoff request | Calculate principal, interest to the payoff date, fees and escrow, and issue a dated quote | Quote amount, good-through date and daily interest | Within seven business days of a written request for dwelling-secured loans, 12 CFR 1026.36(c)(3) |
| Charge-off | Move the balance off the active book, apply your accrual policy and keep recovery collection open | Charge-off date and amount, then every recovery posting | Your accounting policy and the bureau status codes you furnish |
| Monthly cycle close | Accrue interest, assess fees, produce the statement and build the bureau file | Statement image, cycle balances and the data furnished | Periodic statements for mortgages, 12 CFR 1026.41; furnisher accuracy, 12 CFR 1022.42 |
Our Approach
How should a lender approach servicing software?
Three principles keep a servicing build auditable as volume grows.
Rules as versioned configuration
The payment waterfall, late fees, grace periods and day-count conventions live in configuration with an effective date, so the system can show which version applied to any past payment.
One loan ledger feeds everything
Statements, payoff quotes, bureau files and general ledger entries are all built from the same transaction ledger, never from separate copies.
Every clock is a scheduled event
Due dates, delinquency days and hardship deadlines are events with owners, so a missed step raises an alert instead of surfacing in the next audit.
Capabilities
What do we build into loan servicing software?
How to build lending software for the servicing stage: modules that follow the loan after funding, configured for your products and connected to your core.
Payment intake and posting
ACH, debit card, lockbox, branch and wire payments posted with receipt and effective dates, including returned payment handling.
Payment application engine
A configurable waterfall for fees, interest, principal and escrow, with suspense handling and reversal when a payment is returned.
Interest and fee accrual
Daily or monthly accrual by product, scheduled rate changes, and late fees assessed on your grace period rules.
Periodic statements
Statements produced from the ledger each cycle, with the account history and delinquency details your products require.
Collections workspace
Queues by days past due, promise-to-pay tracking, contact attempt logs and call scheduling that respects your contact rules.
Hardship and loss mitigation
Application intake, document checklists, program eligibility rules, decisions with reasons and modified payment schedules.
Credit bureau furnishing
Monthly Metro 2 files built from the loan ledger, with dispute tracking and corrections sent in the next cycle.
Payoff and lien release
Dated payoff quotes with daily interest, payoff posting, and a lien release task when the balance reaches zero.
How It Works
How does one payment move through the servicing system?
The path a borrower payment takes from receipt to the general ledger. Every step writes a record the next step can be checked against.
Receive
The payment arrives by ACH, card, lockbox or branch and is stamped with its receipt date and source before anything else happens.
01
1
Match
The payment is matched to a loan by account number or reference. Unmatched items go to an exception queue with the raw remittance data.
02
2
Apply
The waterfall version in force on the receipt date splits the payment across fees, interest, principal and escrow, or holds it in suspense.
03
3
Update status
Days past due, next due date and delinquency status are recalculated, which can close a collections item or cancel a scheduled late fee.
04
4
Post and reconcile
Journal entries go to the general ledger, and the day's postings are reconciled against deposits in the bank account.
05
5
Report
The payment flows into the next statement and the monthly bureau file, so the borrower and the bureaus see the same history.
06
6
Engineering Stack
Systems and standards behind loan servicing
Chosen to fit your loan products, your core and your payment rails.
Payments
ACH origination and returnsDebit card processingLockbox filesReal-time payment rails where your bank offers them
Ledger
Double-entry loan ledgerPostgreSQLEvent log of every postingGeneral ledger interface
Reporting
Metro 2 credit reporting formatStatement generation with print and e-deliveryInvestor remittance reports
Platform
Role-based access and SSOEncryption in transit and at restAudit logsScheduled jobs with alerting
Sizing
What sizes a loan servicing build?
A loan servicing build is sized by the loan products and payment schedules, the payment channels, escrow analysis, investor or participation reporting, credit bureau furnishing, the active loans to migrate with their history, and the core and general ledger integration. Agnotic Technologies answers each with your servicing and finance leads before it estimates the work.
| Driver | Question to answer before scoping | What it changes in the build |
|---|---|---|
| Loan products and payment schedules | Which products are serviced: installment, revolving, interest-only, balloon or variable rate, and how are their schedules set? | Each product needs its own accrual method, waterfall version, statement layout and test cases. |
| Payment channels | Which channels must post on day one: ACH, debit card, lockbox, branch, wire or real-time payments? | Each channel adds an intake file or API, return handling and a daily reconciliation report. |
| Escrow analysis | Do any loans carry escrow for taxes and insurance that needs annual analysis and disbursement? | Escrow adds analysis runs, shortage and surplus handling, disbursement tracking and borrower notices. |
| Investor or participation reporting | Are loans sold, participated or held for investors who expect remittance and loan-level reports? | Adds ownership splits, investor remittance calculations and reports in each investor's layout. |
| Credit bureau furnishing | Will you report to the credit bureaus, and how are disputes from borrowers and bureaus handled today? | Adds monthly Metro 2 file builds, dispute queues and correction rules tied to the loan ledger. |
| Active loans and history to migrate | How many active loans move, and must their payment, delinquency and modification history move with them? | Migration needs mapping, a balance reconciliation for every loan and a parallel run before cutover. |
| Core and general ledger integration | Does the servicing system post to a core banking platform, a general ledger or both, and how often? | Sets the posting interface, the daily balancing jobs and who owns the account mapping. |
Measured Impact
What should a servicing team measure?
Measures we build into servicing dashboards for operations and finance.
Unapplied cash
Suspense and exceptions
Money received but not yet applied, by age and reason.
Posting errors
Reversals and returns
Returned payments, unmatched items and reversals in each cycle.
Hardship pipeline
Open cases
Applications waiting for documents or a decision, by age.
Disputes
Bureau and borrower
Open disputes and error notices against their due dates.
Use Cases
Which lenders need custom servicing software?
Typical first projects for servicing teams.
01
Consumer installment lenders
Servicing for personal and auto loans held on the lender's own book.
02
Credit unions
A servicing layer for member loans beside a core that handles deposits.
03
Mortgage subservicing
Escrow, statements and loss mitigation workflows for residential loans.
04
Small business lenders
Term loans and lines with flexible schedules and covenant tracking.
05
Lending for startups
A first servicing system for a new lending product, built to grow from one loan type to several.
06
Servicing migration
Moving loans off a legacy system with balance and history reconciliation before cutover.
Integrations
Which systems does servicing software connect to?
The systems a servicing platform reads from or writes to.
Deposits and general ledger
Core banking system
Loan boarding
Loan origination system
Payments
Payment processor and ACHLockbox provider
Furnishing
Credit bureaus
Statements and notices
Document and e-delivery
Self-service
Borrower app or portal
Collections calls
Contact center
Compliance-First Development Services Backed by Global Standards
We build secure, scalable products designed for privacy, interoperability, and regulatory readiness from day one across every sector we serve.
Service Organization Control 2
Verified controls for security, availability, and confidentiality of enterprise data systems.
Information Security Management
Adhering to the international gold standard for managing information security risks.
Payment Card Industry (PCI DSS)
Securing payment transactions and protecting cardholder data with industry-best practices.
Our Edge
Why Global Leaders Choose Us
We combine deep technical expertise with industry-specific knowledge to deliver solutions that aren't just functional, but transformational.
Enterprise-Grade Security
We implement rigorous security protocols and compliance standards (HIPAA, GDPR, SOC2) across all industrial solutions to protect sensitive data.
High-Performance Scaling
Our architectures are built to handle massive data loads and user bases, keeping performance steady whether you're serving ten or ten million.
Accelerated Time-to-Market
Using our suite of internal tools and proven frameworks, we cut setup work so your first release reaches users sooner.
Embedded AI Integration
Beyond simple wrappers, we build deep-learning integrations and predictive analytics directly into the core of your industry-specific workflows.
Engagement Model
How does a servicing engagement work?
We start with one loan product. Timing depends on scope; we agree a fixed first release on the scoping call.
01
Scoping call
We review your loan products, payment channels, current servicing system and the rules your counsel says apply.
02
Rules workshop
The waterfall, fees, grace periods, delinquency triggers and hardship programs are written down as configuration with your compliance team.
03
Fixed-scope first release
One product's payment posting, statements and payoff quotes, reconciled against your current system in a parallel run.
04
Migration and rollout
Loan boarding, history migration, collections and bureau furnishing for the remaining products.
05
Support
Rule changes, rate updates and regulatory changes under change control, with posting monitoring.
Facts and sources
Servicing rules we design around
Most of these apply to mortgage loans; we use them as the baseline for servicing design. Each is linked to its primary source.
For a closed-end consumer credit transaction secured by a principal dwelling, a servicer must credit a periodic payment to the loan account as of the date of receipt, unless a delay causes no charge to the consumer and no negative credit reporting.
Source: 12 CFR 1026.36(c)(1)(i) (eCFR)For a consumer credit transaction secured by a dwelling, the creditor, assignee or servicer must send an accurate payoff statement within a reasonable time and in no case more than seven business days after a written request, with limited exceptions such as bankruptcy or foreclosure.
Source: 12 CFR 1026.36(c)(3) (eCFR)A residential mortgage servicer must provide a periodic statement for each billing cycle, and when the consumer is more than 45 days delinquent the statement must add delinquency information, including an account history for up to the previous six months.
Source: 12 CFR 1026.41 (eCFR)A mortgage servicer must make good faith efforts to establish live contact with a delinquent borrower no later than the 36th day of delinquency, and send a written early intervention notice no later than the 45th day.
Source: 12 CFR 1024.39 (eCFR)Every furnisher must establish and implement reasonable written policies and procedures for the accuracy and integrity of the consumer information it furnishes to a consumer reporting agency.
Source: 12 CFR 1022.42(a) (eCFR)
Voice of success
We don't just build products; we forge lasting partnerships. See how we've helped industry leaders transform their vision into technical reality.
“I can clearly see how Agnotic has a unique way of handling end-to-end development. They are always active on quick chat and provide support quickly.”
Aaron Phelan
Founder, Benchmark
“Agnotic combines deep technical expertise with strong domain knowledge. They understand the business context, anticipate challenges, and make collaboration smooth and effective.”
John Pasmore
Founder, Latimer
“Agnotic is the best technical team we evaluated. Their engineering excellence made our work dramatically easier and allowed us to stay focused on what matters most for maternal care outcomes. They took full ownership of the technical execution, and we are always happy to continue working together.”
Kim Smith
Founder, My Lauren
Related pages
Before and around loan servicing
This page starts when the loan funds. These pages cover what comes before it and the systems beside it.
Loan origination software
Application, underwriting and disbursement: everything before servicing starts.
Credit risk scoring software
The scoring models that servicing performance data later tests.
Core banking software development
The ledger and product engine a servicing layer posts to.
BFSI analytics dashboard software
Executive dashboards that sit on servicing and portfolio data.
KYC compliance software
Identity checks when a co-borrower or successor in interest is added to a loan.
Debt collection software
Account placement, validation notices and Regulation F contact limits once a loan goes to collections.
Buy now pay later (BNPL) software
Installment plans, point of sale decisions, merchant checkout and refunds that adjust the schedule.
More in Financial Services
More Financial Services Solutions
Explore other production-grade engineering platforms we deliver across financial services.
Frequently Asked Questions
Lending cost for a servicing build follows the seven drivers in the sizing table on this page, and loan migration usually weighs most. We size them on the scoping call, which a loan servicing calculator cannot do.
That depends on the products and the migration. On the scoping call we agree a fixed first release, usually one loan product running in parallel with your current system, and plan the rest from there.
Yes. We migrate balances, payment history, escrow and collections notes, then run both systems side by side until every loan's balance and next due date match before cutover.
Yes. Hardship applications, document checklists, program eligibility, trial payment plans and permanent modifications run as a loss mitigation case with a decision, a reason and a new payment schedule written back to the loan.
The Metro 2 file is built from the same ledger as statements, every dispute is tracked to a resolution, and corrections flow into the next file automatically. That gives you the evidence behind the written accuracy policies a furnisher must keep.
Often, when the product has payment rules that packaged servicing systems handle poorly, such as income-based schedules or embedded lending. Lending for startups usually begins with one product's posting, statements and payoff, built so new products are configuration rather than new code.
No. Agnotic Technologies is a software development services company. We build and support the servicing software; your team or your subservicer services the loans and talks to borrowers.
Industries