Purpose
This Provider Implementation Guide provides the information required for a successful implementation of Title API Integration for receiving and returningsynchronousTitle and Closing order events and order statuses from Direct2Title.
This document is created, maintained, and distributed by Avanze Tech Labs Inc. to communicate theimplementation requirements to its customers. Avanze supports the contents included in the Provider Implementation Guide when the order originates from Client.
Products
The Client will be ordering the following products using the Direct2Title platform. The Client should verify that their interface supports these products and represents the correct geographic coverage to meet the Client’s needs. This product listing contains all possible Title and Closing products that the Client will be ordering on the Direct2Title portal.
| PRODUCT | CODE | PRODUCT NAME | PRODUCT DESCRIPTION |
|---|---|---|---|
| Title | TC | Commitment/Prelim Report | Preliminary report issued before the actual policy which lists the condition of the title and steps necessary to complete the final issuance of title insurance. |
| Title | PR | Property Report Plus | Name of grantors and grantees, including the status of the parties and estate by which title is held, consideration, date of execution, date of recording, deed reference, legal description, created interests or conditions of title as set forth in the deed, and parcel identification number, involuntary liens and judgements inclusive of municipal, mechanics/materials, tax liens, small claims awards affecting real estate and special assessments. No insurance is provided. |
| Title | LS | UCC Lien Search | Provides name of Co-op corporation and names of owners of shares of stock associated with a specific unit within that Co-op. Includes lien search against building, unit, and owner and offers guarantee of certain liabilities. |
| Title | LV | Legal and Vesting | Provide legal description and vesting information on subject property from legal and vesting data sources. |
| Closing | CS | Closing and Escrow Services | The closing agent handles title compliance, payoffs, and disbursements along with proper ID and execution of the documents at closing. |
Events Description
We have many events to process order
Place Order
| Code | PlaceOrder |
| Description | New Order Request |
| Type | Inbound |
| EVENT DEFINITION | Abstractor receives this event, from Client, as the new order request. |
Add Attachment
| Code | AddAttachment |
| Description | Document Upload |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | To transfer document between the Client’s and the Abstractor’s systems. |
Add Note
| Code | AddNote |
| Description | Comment |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Abstractor and/or Client sends this event to provide a comment on an order request. Based on the information provided in the comment If anyaction is required it can be flagged in the Event. |
Add Note Ack
| Code | AddNoteAck |
| Description | Comment Acknowledgment Required |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Abstractor and/or Client sends this event to provide a comment, simultaneously indicating action is required as a result of the information provided in the comment. |
Update Order Info
| Code | UpdateOrderInfo |
| Description | Order Information Update |
| Type | Inbound |
| EVENT DEFINITION | Client sends this event to notify the Abstractor of the change in Loan information. The information may include Loan Amount, Borrower information etc. |
Update Status
| Code | UpdateStatus |
| Description | Status Update |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Generic event used to update different statuses of an order. |
Deliver Product
| Code | DeliverProduct |
| Description | Product Delivered by the Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client with the final title product. Inthis event Document / Dataor Both can be sent based on the Customer Setupre. |
Accept Order
| Code | AcceptOrder |
| Description | Service Confirmed by Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client to inform that the order has been accepted by the Abstractor. The Abstractor may provide their order number in this. |
Deny Order
| Code | DenyOrder |
| Description | Order Denied by the Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client that the Abstractor has denied the order request. |
Cancel Order
| Code | CancelOrder |
| Description | Order Cancelled |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Client and/or Abstractor sends this event to cancel the order request. |
Complete Order
| Code | CompleteOrder |
| Description | Order Completed |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client to notify that the order request is complete. |
Curative Pending
| Code | CurativePending |
| Description | Curative Pending |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to notate pending Curative items and responsible parties. Event may be associated with action required. |
Cleared Title
| Code | ClearedTitle |
| Description | Curative Cleared |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client to notify that the curative process is complete and the title is clear. |
Clear To Close
| Code | ClearToClose |
| Description | File Considered Ready For Closing |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends CTC documentation once file is deemed ready to close. |
Deliver Policy
| Code | DeliverPolicy |
| Description | File Considered Ready For Closing |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends CTC documentation once file is deemed ready to close. |
Hold Order
| Code | HoldOrder |
| Description | Service On Hold |
| Type | Inbound |
| EVENT DEFINITION | Client sends the event to the Abstractor to notify the order has been put on hold due to incompleteness. This event will stop the SLA clock. |
Request Revision
| Code | RequestRevision |
| Description | Title Product Revision Required |
| Type | Inbound |
| EVENT DEFINITION | Client sends the event to the Abstractor to notify revisions are required based on delivered title product. |
Resume Order
| Code | ResumeOrder |
| Description | Service Resume |
| Type | Inbound |
| EVENT DEFINITION | Client sends the event to the Abstractor to notify the order has resumed, and the SLA clock can continue. |
Revised Title Commitment
| Code | RevisedTitleCommitment |
| Description | Provides Revised Title Commitment Post Curative |
| Type | Outbound |
| EVENT DEFINITION | Specific to files which required curative, event identifies revised title commitment post clearing of relevant curative items. |
Revision Accepted
| Code | RevisionAccepted |
| Description | Abstractor Agrees To Complete Requested Revisions |
| Type | Outbound |
| EVENT DEFINITION | Client identified revisions are agreed with by Abstractor for completion of revision request. |
Revision Not Accepted
| Code | RevisionNotAccepted |
| Description | Abstractor Disagrees With Requested Revisions |
| Type | Outbound |
| EVENT DEFINITION | Abstractor, due to title-specific requirements, may not facilitate some or all revisions requested by Client. Identified with mandatory ReasonCode. |
Updated Clear To Close
| Code | UpdatedClearToClose |
| Description | Abstractor Provides Updated Clear To Close Certificate |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends relevant documentation validating CTC when ClearToClose has already sent and revisions identified after require an updated certificate. |
Place Order
| Code | PlaceOrder |
| Description | New Order Request |
| Type | Inbound |
| EVENT DEFINITION | Abstractor receives this event, from Client, as the new order request. |
Add Attachment
| Code | AddAttachment |
| Description | Document Upload |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | To transfer document between the Client’s and the Abstractor’s systems. |
Add Note
| Code | AddNote |
| Description | Comment |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Abstractor and/or Client sends this event to provide a comment on an order request. Based on the information provided in the comment If anyaction is required it can be flagged in the Event. |
Add Note Ack
| Code | AddNoteAck |
| Description | Comment Acknowledgment Required |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Abstractor and/or Client sends this event to provide a comment, simultaneously indicating action is required as a result of the information provided in the comment. |
Update Order Info
| Code | UpdateOrderInfo |
| Description | Order Information Update |
| Type | Inbound |
| EVENT DEFINITION | Client sends this event to notify the Abstractor of the change in Loan information. The information may include Loan Amount, Borrower information etc. |
Update Status
| Code | UpdateStatus |
| Description | Status Update |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Generic event used to update different statuses of an order. |
Document Ship Info
| Code | DocShipInfo |
| Description | Documents Shipped Information |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to provide document shipping and tracking information. Event allows distinction of recipient (Client, Abstractor, Borrower, Seller, Other) |
Sent To Record
| Code | SentToRecord |
| Description | Recording submitted by Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to the Client to notify Client the mortgage has been transmitted for recordation. |
Completed Recording
| Code | CompletedRecording |
| Description | Recording submitted by Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to the Client to notify Client the mortgage has been transmitted for recordation. |
Request Payoff
| Code | RequestPayoff |
| Description | Client Sending |
| Type | Inbound |
| EVENT DEFINITION | Client sends this event to Abstractor to request a payoff |
Recorded Docs
| Code | RecordedDocs |
| Description | Recorded Mortgage/Deed of Trust |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to provide Client with copy of recorded mortgage/deed of trust. This event requires a document to be sent. |
Ordered Payoff
| Code | OrderedPayoff |
| Description | Payoff Ordered |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to notify the other party the payoff has been ordered. |
Completed Payoff
| Code | CompletedPayoff |
| Description | Payoff Delivered |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to notify the payoff ordered has been delivered. A Document may be sent with this event. |
Scheduled Signing
| Code | ScheduledSigning |
| Description | Signing Scheduled |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to notify that signing has been scheduled. The event requires scheduling date, time, location, and notary name, phone, and email. |
Rescheduled Signing
| Code | RescheduledSigning |
| Description | Singing Rescheduled |
| Type | Inbound/Outbound |
| EVENT DEFINITION | Client/Abstractor sends this event to notify that signing has been rescheduled. The event requires date(s), time(s), and location at which borrower is available to schedule the closing. |
Ready To Schedule
| Code | ReadyToSchedule |
| Description | Ready to Schedule |
| Type | Inbound/Outbound |
| EVENT DEFINITION | Client sends the event to the Abstractor to schedule signing. The event requires date(s), time(s), and location(s) at which borrower is available to schedule the closing. And Abstractors also sends the event to Client based on SOW notifying Client of scheduled date(s), time(s), and location(s) borrower has requested for scheduling. |
Accept Order
| Code | AcceptOrder |
| Description | Service Confirmed by Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client to inform that the order has been accepted by the Abstractor. The Abstractor may provide their order number in this. |
Add Critical Docs
| Code | AddCriticalDocs |
| Description | Critical Post-Closing Documents Uploaded |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client to provide critical documents prior to receipt of full closing package for review. This event requires a document to be sent. |
Deny Order
| Code | DenyOrder |
| Description | Order Denied by the Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client that the Abstractor has denied the order request. |
Cancel Order
| Code | CancelOrder |
| Description | Order Cancelled |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Client and/or Abstractor sends this event to cancel the order request. |
Complete Order
| Code | CompleteOrder |
| Description | Order Completed |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to Client to notify that the order request is complete. |
Deliver Abstractor SS
| Code | DeliverAbstractorSS |
| Description | Closing Statement Delivered |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to the Client to deliver the Preliminary HUD/CD. This event requires a document to be sent. |
Disbursement Ledger
| Code | DisbursementLedger |
| Description | Disbursement Ledger Post Funding |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to provide Client with disbursement ledger. This event requires a document to be sent. |
Deliver Client SS
| Code | DeliverClientSS |
| Description | Closing Instructions |
| Type | Inbound |
| EVENT DEFINITION | Client sends this event to the Abstractor to deliver the closing instructions/CD. This event requires a UCD XML document to be sent. |
Request SS Revision
| Code | RequestSSRevision |
| Description | Closing Statement Modifications Requested |
| Type | Inbound |
| EVENT DEFINITION | Client sends this event to the Abstractor to make changes to the Closing Statement. |
Complete SS Revision
| Code | CompleteSSRevision |
| Description | Closing Statement Modifications Complete |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to notify Client the requested Closing Statement modifications have been completed. This event requires a document to be sent. |
Approve SS
| Code | ApproveSS |
| Description | Closing Statement Approved by Client |
| Type | Outbound |
| EVENT DEFINITION | Client sends this event to the Abstractor to notify they are ready to receive the Final HUD. |
Deliver Final SS
| Code | DeliverFinalSS |
| Description | Closing Statement Distributed |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Client or Abstractor can exchange this event having Final data and/or Attachment. |
Funds Sent By Client
| Code | FundsSentByClient |
| Description | Loan Funds Delivered |
| Type | Inbound |
| EVENT DEFINITION | Client sends this event to the Abstractor to notify the loan. |
Clear to Fund
| Code | ClearToFund |
| Description | Clear to Fund |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Client or Abstractor sends this event to notify the funds have been approved to be disbursed. |
Not Clear to Fund
| Code | NotClearToFund |
| Description | Not Clear to Fund |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Client or Abstractor sends this event to notify the loan is not clear to fund. |
Funded Loan By Abstractor
| Code | FundedLoanByAbstractor |
| Description | The Abstractor Disbursed Funds |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to the Client to advise that the Abstractor has disbursed the funds, and provided disbursement information. |
Funds Received
| Code | FundsReceived |
| Description | Funds Received by Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to the Client to notify the funds have been received. |
Deliver Closing Package
| Code | DeliverClosingPackage |
| Description | Document Package Delivered by Client |
| Type | Outbound |
| EVENT DEFINITION | Client sends this event to the Abstractor to notify the document package has been delivered. This event requires a document to be sent. |
Receive Closing Package
| Code | ReceiveClosingPackage |
| Description | Document Package Received by Abstractor |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to notify the closing package has been received. |
Completed Signing
| Code | CompletedSigning |
| Description | Closing Documents Executed |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to notify the Client that the Closing Documents were executed by the applicable parties. |
Failed Signing
| Code | FailedSigning |
| Description | Closing Documents Not Executed |
| Type | Outbound |
| EVENT DEFINITION | Client or Abstractor sends this event to notify the other party that the closing documents were not executed. |
Add Executed Docs
| Code | AddExecutedDocs |
| Description | Critical docs uploaded |
| Type | Outbound |
| EVENT DEFINITION | Abstractor sends this event to the Client to deliver the executed closing package. This event requires a document to be sent. |
Hold Closing Order
| Code | HoldOrder |
| Description | Service On Hold |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Client and/or Abstractor send the event to notify the order has been put on hold due to incompleteness. This event will stop the SLA clock based on SOW. |
Resume Closing Order
| Code | ResumeOrder |
| Description | Service On Resume |
| Type | Inbound/ Outbound |
| EVENT DEFINITION | Client and/or Abstractor send the event to notify the order has been put on Resume due to incompleteness. This event will stop the SLA clock based on SOW. |