Reverse mortgage vendor orders: reconcile each request

Reverse mortgage vendor orders need a clear chain from request to acknowledgment, delivery, review, and billing. A sent request does not prove that a vendor accepted the work. A delivered report does not prove that your reviewer accepted it.

Use the operating approach below to reconcile those separate events without losing the original order history. It is a suggested internal workflow, not a regulatory checklist or a description of specific ReversePilot features.

What belongs in a reverse mortgage vendor orders record?

Start with one record for each service request. Link it to the correct loan file, service type, and authorized vendor. Give your team enough context to distinguish a new order from a correction or a follow-up on existing work.

The Consumer Financial Protection Bureau explains that reverse mortgage closing costs can include third-party services such as appraisals, title searches, and credit checks. That does not mean every listed service applies to every file. Use your approved procedures to determine the appropriate order.

• Internal file reference and requested service.
• Vendor name and vendor order reference, when available.
• Request time, requester, and internal follow-up owner.
• Scope, approved delivery channel, and expected response.
• Current evidence, unresolved question, and next action.

Keep sensitive source documents in the approved file location. Link to them through your authorized workflow rather than copying personal information into a general tracking sheet. Your record should help colleagues locate evidence without creating unnecessary extra copies.

Separate sending from vendor acknowledgment

Record what you can actually verify after submitting a request. A local success message may show that your team sent something, while a vendor reference confirms a different event. Preserve both when they are available, and label an uncertain result as unresolved.

1. Check the original request record and any returned acknowledgment.
2. Look for an existing vendor reference before sending another order.
3. Ask the vendor to confirm receipt through the approved contact channel if the result remains unclear.
4. Record the confirmed outcome and the person responsible for the next step.

For example, suppose a submission screen stops responding after your processor sends a request. That alone does not establish failure. A second submission could create another order, so reconcile the first attempt before deciding whether to resend.

A promised delivery date also differs from an internal follow-up date. Record whose commitment each date represents. Connect overdue follow-up work to your pipeline aging review without treating an estimated delivery date as a confirmed result.

Track delivery and review as separate events

When a report arrives, match it to the file and order before moving it forward. Record the delivery time and the reviewer responsible for assessing it. Leave the review outcome open until that person records a decision.

If a report needs correction, preserve its connection to the original order. State what needs clarification and who will review the response. Avoid describing a correction as a new purchase unless that is the actual agreed scope.

The document version control approach helps keep original and corrected reports distinguishable. For appraisal-specific coordination, use the separate appraisal handoff explainer. Neither a file upload nor a vendor completion flag substitutes for your review decision.

Reconcile invoices and unresolved orders

Compare an invoice with the order reference, agreed service, and available delivery evidence. If the scope or amount differs, route the discrepancy to the person authorized to resolve it. Do not infer that an invoice proves delivery or that delivery proves payment approval.

A cancellation request needs its own outcome, too. Keep the request and vendor response linked until the status is confirmed. Do not assume a cancellation removes charges; record what the vendor confirms and route any disputed amount through your approved process.

• Unacknowledged request: confirm whether an order exists.
• Delivered but unreviewed report: assign or follow up with the reviewer.
• Possible duplicate: reconcile references before requesting more work.
• Invoice discrepancy: document the question and authorized decision owner.

Review exceptions as specific actions rather than a list of vaguely pending files. A useful entry says what is missing, who is checking it, and when they will follow up. Close it only when you can point to the resolving evidence.

Key takeaways

• Keep the request, acknowledgment, delivery, review, and billing outcomes distinct.
• Check uncertain submissions before creating another order.
• Link corrections and cancellation responses to the original request.
• Give every unresolved discrepancy an owner and a specific next action.

Use the coverage handoff explainer to keep open vendor questions moving when the usual owner is away.