Common Error Messages in ResWare

Audience: Title Agents

The short answer: This article covers common error messages you may see in ResWare when sending orders, signings, or documents to Proof, and how to resolve each one. Error and success messages appear in the XML tab on the file in ResWare.

Send Order / Send Signings / Send Documents Errors

These errors may appear when making Send Order, Send Signings, or Send Documents calls from ResWare to Proof.

Error: "Invalid credentials"

The URL in the ResWare-to-ResWare Mappings for this call may be incorrect or incomplete — including a missing URL parameter for Send Documents or Send Signings calls.

+ Troubleshooting Steps
  1. Open the ResWare-to-ResWare Mappings for the affected call.
  2. Compare the URL against the Job Aid to confirm it matches the expected format exactly.
  3. If the error is on a Send Documents or Send Signings call, check that the RemotePrimaryContactEmployeeID is included as a URL parameter. For example, if the RemotePrimaryContactEmployeeID is 20, that section of the URL should read om=20.
  4. Correct any discrepancies and retry the call.

Error: "It looks like you have a signing party on the Signing 0 that does not match the transaction type. Please refer to the job aid to get help sending Signings."

The Signing Type and Signing Party in the Signings tab don't match — Signing Types map to Transaction Types in Proof, and each Transaction Type is specific to either a Buyer or Seller transaction.

+ Troubleshooting Steps
  1. Open the Signings tab and note the Signing Type and Signing Party for the affected signing.
  2. Check the Job Aid to identify which Transaction Type in Proof your Signing Type maps to.
  3. Confirm the Signing Party (Buyer or Seller) matches the Transaction Type. For example, if the Signing Type maps to "Purchase buyer cash," the Signing Party should be the Buyer — not the Seller.
  4. Update the Signing Type to one that maps to the correct Transaction Type for the Signing Party on file.
  5. Reference the Job Aid for the complete Signing Type-to-Transaction Type mapping guide.

Error: "Error Signer [Name] (signer) is missing from File..."

A signer was added to the file in ResWare after the most recent Send Order call, so that party's record hasn't been synced to Proof yet.

+ Troubleshooting Steps
  1. Run Send Order again to sync the updated signer information to Proof.
  2. Once Send Order completes successfully, proceed with Send Signing.

Error: "Organization missing Notarize user for Escrow Officer with..."

The Escrow Officer listed on the file in ResWare doesn't have a matching email address in your Proof organization, so Proof can't assign the transaction to that user.

+ Troubleshooting Steps
  1. Note the Escrow Officer's email address as it appears in ResWare.
  2. In Proof, create an organization member using that exact email address.
  3. Once the organization member is created, retry the order.

Error: "The Signing #0 is not eligible on Notarize for a _______ transaction for that property address and underwriter. Please check your notes to view eligible transaction types and underwriters."

Proof's eligibility check returned a failure for the selected transaction type, property address, or underwriter combination. An incorrect or unsupported county is the most common cause once state and underwriter configuration is confirmed.

+ Troubleshooting Steps
  1. Confirm your Title Agency is configured in Proof to operate in the state and with the underwriter for this transaction type.
  2. If the state and underwriter configuration looks correct, review the County selected on the file — an unsupported or incorrect county is the most common cause of this error.
  3. If the issue persists after verifying both, contact your Proof Solutions Engineer or submit a support request.

Common Entity Support Errors

These errors appear in the XML tab during the Send Signings call when there are issues with entity signer information.

Error: "The signing #{signing number} has no signatories for {Entity Buyer/Seller Name}"

The Custom Fields for entity signatory information haven't been added or completed for an entity buyer or seller who needs to sign documents on the file.

+ Troubleshooting Steps
  1. Navigate to the Custom Fields for the entity buyer or seller named in the error.
  2. Add and complete all required entity signatory fields.
  3. Retry the Send Signings call.

Error: "Invalid Buyer/Seller: the {field name} field is missing for {buyer/seller name}"

One or more entity signatory fields have been partially completed — once any field for an entity signatory is entered, all fields for that signatory become required.

+ Troubleshooting Steps
  1. Review the entity signatory fields for the buyer or seller named in the error.
  2. Complete all required fields for that signatory, including: email, first name, last name, and title.
  3. Retry the Send Signings call.

Still Unsure?

Our support team is happy to help. Submit a support request or chat with us from any page in the app.

Updated

Was this article helpful?

0 out of 10 found this helpful