Table of contents
Outsourced mortgage support is easiest to manage when the invoice matches the work. Too often, the bill arrives as a single line for hours, and the operations lead has no practical way to confirm what was done. The team may be satisfied with the service and still overpay for rework, idle time, or tasks outside the agreed scope. A vendor invoice check closes that gap.
The check is not an accusation. It is a shared control that protects both sides. It gives the vendor a clear record of approved work and gives the buyer a defensible basis for payment. It also creates a feedback loop for scope changes. This guide explains the fields and the monthly routine.
Agree on the unit of work
Start with the unit the contract actually prices. A vendor may charge by hour, by file, by completed task, or by a monthly capacity block. The invoice check should use the same unit. Comparing hours against a file-based contract creates confusion and weakens the review.
If the contract prices by hour, define what counts as billable. Travel, training, internal meetings, and rework may be included or excluded. Write the rule in the statement of work and repeat it on the invoice template. A clear rule prevents a monthly debate about a handful of hours.
If the contract prices by file or task, define completion. A file is complete when the agreed checklist is done and the evidence is in the system, not when the work is started. A task is complete when the output is accepted by the named reviewer. The completion rule should be testable.
Tie the invoice to a work log
Ask the vendor for a work log that lists the date, the file or task, the activity, the person, and the time or quantity. The log should be exportable, not a PDF summary. A structured export lets the buyer sample and reconcile without retyping. It also makes trends visible across months.
Do not require a narrative for every line. A short activity code and a file reference are enough for routine work. Reserve narrative notes for exceptions, escalations, and work outside the agreed scope. A log that is too detailed becomes a burden and is often completed after the fact.
Compare the log total with the invoice total before reviewing quality. A mismatch is a finding, even when the difference is small. The vendor should explain the difference and correct the invoice or the log. A recurring mismatch points to a process problem that will not fix itself.
Sample the completed work
Pick a sample of files or tasks from the invoice and confirm that the work was done and accepted. Use the same sample method each month so the result is comparable. Check the evidence in the system, not only the vendor's note. A completed task should leave a document, a status change, or a reviewer sign-off.
Record the sample size and the pass rate. A small sample can still reveal a pattern if the same issue appears more than once. If a task is marked complete but the evidence is missing, treat it as incomplete until the vendor supplies the record. The buyer should not pay for work that cannot be verified.
Share the sample result with the vendor in a short review call. Name the files that passed and the files that need correction. Give the vendor a chance to explain before applying a credit. A factual conversation is more useful than a surprise deduction.
Check service levels separately from volume
Volume and quality are different questions. A vendor can complete every file and still miss the response-time or accuracy standard. Review the service-level report alongside the invoice. The report should use the same definitions as the contract, including business hours and excluded downtime.
If a service level was missed, apply the remedy in the contract rather than inventing a new penalty. The remedy might be a credit, a corrective action plan, or a review meeting. Record the remedy and the follow-up date. A remedy that is never tracked is a discount with no learning.
Do not let a service-level credit hide a quality problem. A vendor that misses response times may also be rushing reviews. Look at the rework and exception data before concluding that the volume is healthy. The mortgage operations support lead can connect the service report to the file outcomes.
Review scope changes before they appear on the invoice
Scope changes are a common source of invoice disputes. A new lender portal, a new document type, or an added reporting requirement may be outside the original statement of work. The buyer and vendor should agree on the change before the work begins. A short change note should record the scope, the price, and the start date.
Review the change log during the monthly invoice check. Confirm that each billed change has an approved note. A change that was requested verbally and never documented should be discussed before payment. The conversation should focus on the work and the rate, not on blame.
Keep the rate card current. If the contract includes annual adjustments, confirm that the invoice uses the correct rate for the period. A rate error is easy to miss when the invoice looks familiar. Check a sample of lines against the rate card each month.
Report the result in one page
The monthly report should show the invoice total, the approved total, the sampled files, the service-level result, and any open corrections. Keep it to one page with a short narrative. The operations lead should be able to understand the position without opening the work log. Add a link to the detailed log for anyone who needs to check a line.
Include a section for next month's actions. One action might be a vendor process fix, and another might be an internal change such as a clearer task description. Assign an owner and a date. A report without actions becomes a recurring formality.
Share the report with finance and the vendor on the same schedule. A consistent cadence reduces surprises and makes the annual contract review easier. It also gives the vendor a fair chance to correct a problem before it affects the relationship. Keep the distribution list short so the report does not become a public scorecard.
Protect the relationship while enforcing the control
A vendor invoice check should be firm and predictable, not adversarial. The vendor should know the sample method, the evidence standard, and the correction process in advance. Predictability builds trust and reduces the time spent defending invoices. It also makes a genuine disagreement easier to resolve.
Recognize good work when the data supports it. A vendor that meets the service level and reduces rework deserves a note in the review. Recognition is part of vendor management, not a soft extra. It helps retain the people who know the files.
The Office of the Comptroller of the Currency's third-party risk guidance describes the value of ongoing monitoring. A monthly invoice check is a practical part of that monitoring. It gives the buyer evidence and the vendor a clear standard. Review the check whenever the contract, the rate card, or the scope changes, because an old control can miss a new billing model.