Skip to main content

Back to e-DRS Back to Home

Submission Guide V2.1

Part 1. Application to change register

Steps

    1. Provide general details, Title numbers, postcode/local authority/references etc.
    2. Identify which applications are being submitted. E.g. discharge, transfer, charge.
    3. Specify against each application if you are going to be submitting a document. (The only types that will allow no document are DIS (Discharge) and COA (Change of Address))
    4. Provide details of any supporting documents to be sent alongside the application.
    5. Provide details of any representatives.
      • Lodging conveyancer must be provided. Key number details will be picked up automatically from the details of the user making the submission.
      • It is probably easiest here to always provide lodging, certified and identity with ids of 1, 2, and 3. Then provide incremented ids for any representing conveyancers.
    6. Provide details of which parties are involved in the application.
      1. For each party specify which roles they have for which applications, e.g. lender/borrower for a charge, transferor/transferee for a TR1 (Transfer).
      2. For each party provide details of who’s representing them. There are 5 possibilities here:
        1. Representation not provided: don’t fill in the representativeId at all.
        2. Represented by lodging conveyancer: provide the id from LodgingConveyancer in step 5.
        3. Represented by another conveyancer: provide the id from relevant Representing Conveyancer in Step 5.
        4. Not represented, Identity already checked: provide the id from Certified in Step 5.
        5. Not represented, Identity evidence attached: provide the id from IdentityEvidence in Step 5. For each party linked to this, you must have an ‘Identity Form’ in the Supporting Documents list in Step 3.
      3. Provide party address for services. There are 3 options here:
        1. Existing property address: provide AddressForServiceTypeContent.A1
        2. For existing proprietors you can use their existing address: AddressForServiceTypeContent.B1
        3. Otherwise you need to specify the actual address, there must be a postal address. Then you can have 2 additional addresses which can be postal/dx/email.

Part 2. Attachments

For each application (which has a document) submit the attachment to the attachment service.

  • When filling in the details use the application priority or supporting document id as the attachment id.
  • The application service is the service id for the application to the change register service (currently 104).

Part 3. Collect attachment results

When you submit attachments, we perform some asynchronous processing on them, including virus scanning. Once this processing is complete we produce a result indicating if we’ve accepted the attachment.

To collect your results:

  • Submit a request to the outstanding requests service.
  • For each result with a service of 105.
  • If NewResponse is true (if you set ShowOnlyNewResponses to true in your request, you can ignore this check).
  • Submit the message id to the attachment poll service.
  • A response of type 30 means it was accepted.
  • A response of type 20 means it was rejected.

Part 4. Requisition monitoring

If a requisition is raised by our caseworkers, this is made available to you via business gateway. This will come up in the outstanding requests service under service 107. Using the same logic as part 3 to find any requisitions, submit the messageIds from the outstanding request response to the correspondence poll service.

  • These messageIds are not messageIds you provide, they are generated by us, so the only way to collect requisitions is to use outstanding requests.
  • The response from the poll service will contain the messageId and external reference from the application it relates to.

Part 5. Responding to requisitions

Responses to requisitions must be sent via business gateway.

  • These are handled using the attachment service detailed in part 2 except you now have some extra options.
  • If you need to provide a new copy of a document you’ve already told us about, simply provide the attachment id again.
  • If it’s a completely new document, you can specify the ApplicationType or DocumentName to say what it is.
  • We return the attachment id we generated for that document in the final response (which is collected in part 3).
  • Repeat part 3 accordingly (this is intended to be a scheduled task, so shouldn’t need anything new here).

Part 6. Collect results

When the application is completed the results are made available in business gateway. The best way to pick these up is to use the outstanding requests service already detailed above.

  • These results are under service 104. The type 30 response indicates the application has been processed. With the relevant response fields completed to indicate whether it was processed, early completed, cancelled etc.

Part 7. Early completion

If your application is completed subject to early completion you will have been notified in the result collected in part 6. When the discharge finally arrives, we create a new response and make it available to you via business gateway. This works the same as part 4 in that we generate the message id to assign to the new message.

  • These will appear under service 108.