1. Loan Management System
  2. Features
  3. Servicing and reconciliation
Feature · Servicing and reconciliation

Servicing and reconciliation

Review loan adjustments and verify recorded operation effects.

OverviewServicing approval inbox
Loan Management System · Servicing and reconciliation

Servicing approval inbox

Approval conditions

New
ParentOrganizationStatusRevisionOutstanding principal USDReviewed at
LA-94975ORG-2538Submitted19037024 Oct
LA-66410ORG-2640Submitted40072004 Oct
LA-25272ORG-2757Submitted16080011 Oct
LA-48641ORG-6096Submitted10095024 Oct
LA-19683ORG-7245Submitted43031012 Oct
6 of 6 records
LA-94975Servicing reviews · SR-20117
Submitted
OrganizationORG-2538
Revision190
Outstanding principal USD370
Reviewed at24 Oct
Example screen with sample data

What you can do

Resolve a servicing change

A servicing review belongs to a loan application and an organization. It carries a revision, status and optional loan reference, reviewed date, outstanding principal, provider application ID and decision date. The Credit Officer prepares the adjustment and supporting evidence. A submitted revision goes to an Independent Credit Approver, who records a decision against that revision and the same parent application. The servicing status changes only after the decision exists. Completed should mean the required authority and effect have actually been recorded, not simply that someone finished reading a form.

The application and servicing review share an evidence trail. Attachments and application evidence remain on the parent case, and the decision row identifies reviewer, reason and source revision. Operation receipts record the action key and expected revision for an attempted change. If the actual effects do not match the receipt’s claim, the result state gives the team a way to mark review needed with a concrete failure reason. A duplicate request should resolve to the same operation result rather than creating another adjustment.

How the work is organized

  • Submitted revision. The review keeps the version and parent case that the approver must assess.
  • Independent decision. The approver’s outcome and reason are recorded before the servicing status changes.
  • Effect verification. Receipts are checked against persisted records before completion is accepted.

What to agree during setup

Agree what counts as sufficient support for changing a servicing position, including how the outstanding principal is sourced. Decide who can submit a review and who can independently decide it. Define the provider response that establishes a completed adjustment and how a delayed response will be investigated. The organization scope must match across the servicing review, parent application and actor. Establish how operation keys are generated for retries so a repeated click cannot create duplicate work.

Use a pilot review on a confirmed application. The Credit Officer enters the loan reference and outstanding principal and attaches support to the parent case. A different person approves the submitted revision and inspects the resulting decision row. Try an old revision and a self-approval; neither should complete the review. Then leave an operation receipt pending and ask the team to verify its claimed effects. A missing effect should move the receipt to review needed with a precise reason, without resending the provider action.

Check the handoff on an actual case

A provider reports a servicing adjustment for a borrower’s loan account. The Credit Officer records a review against the relevant application and supplies the provider reference. The Independent Credit Approver checks the parent case, current revision and supporting evidence before deciding. The team then compares the operation receipt’s effect references with the actual decision and servicing state. If the provider reference is present but the local decision row is absent, the receipt is an exception. If the decision exists and the effect is verified, the review can reach completed status through the authorized path.

Correction and cancellation need the same care. A confirmed application with an uncertain provider effect cannot be quietly relabeled to imply reversal. Preserve verified evidence and earlier decisions; add a correction to explain what changed. This leaves the Auditor a trail of what the team knew at each step.

What your team sees

  • Servicing approval inbox — Submitted adjustments needing a separate decision.
  • Servicing status board — Reviews grouped by current status.
  • Open operation exceptions — Attempts with failed or review-needed effects.

Follow the work through

See servicing review and implementation for the rehearsal and release sequence.

What it keeps track of

Data model
Servicing reviews
Servicing adjustments reviewed against a loan application.
Loan applications
Loan applications moving through underwriting, approval, disbursement and repayment.
Review decisions
Independent approver decisions recorded against a frozen application revision.
Operation receipts
Idempotent operation receipts with stable operation keys and actual effect references.
Application evidence
Statements, confirmations, settlement notices and corrections supporting a loan application.
Record attachments
Supporting documents attached to a loan application.

Who uses it

Permissions
Credit Officer
Prepares the servicing change.
Independent Credit Approver
Decides the submitted revision.
Auditor
Inspects authorized evidence.
App Administrator
Maintains membership without exercising approval authority.

Set up Loan Management System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started