Skip to main content

Back to e-DRS Back to Home

Electronic Document Registration Service vendor test data

Note: all tests require the basic minimum data items as per the schemas.

This will actually be ignored by the system but is needed to pass XML validation.

Items highlighted in the test documentation are needed for the test to return the correct response.

1. Electronic Document Registration Service

  • Test: Electronic Document Registration Service 01
  • Test purpose: Lodge an application against closed title
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.title.closed.specific
  • Description: “Title number CL123456 is closed.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.title.closed.specific
  • Description: “Title number CL123456 is closed.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.title.closed.specific
  • Description: “Title number CL123456 is closed.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.title.closed.specific
  • Description: “Title number CL123456 is closed.”
Login details Message ID any
  • TypeCode: ‘20’
  • Code: bg.title.closed.specific
  • Description: “Title number CL123456 is closed.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.title.closed.specific
  • Description: “Title number CL123456 is closed.”
ProductType TitleNumber or LesseeTitle (when LeaseExtension ServiceTitleType) CL123456
  • TypeCode: ‘20’
  • Code: bg.title.closed.specific
  • Description: “Title number CL123456 is closed.”
  • Test: Electronic Document Registration Service 02
  • Test purpose: Lodge an application against invalid title
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.title.invalid.specific
  • Description: “Title number IV123456 is invalid.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.title.invalid.specific
  • Description: “Title number IV123456 is invalid.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.title.invalid.specific
  • Description: “Title number IV123456 is invalid.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.title.invalid.specific
  • Description: “Title number IV123456 is invalid.”
Login details Message ID any
  • TypeCode: ‘20’
  • Code: bg.title.invalid.specific
  • Description: “Title number IV123456 is invalid.”
  • ProductType
  • Note: To test multiple titles send in extra titles that are valid and not CL123456 or IV123456.
 All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.title.invalid.specific
  • Description: “Title number IV123456 is invalid.”
  • ProductType
  • Note: To test multiple titles send in extra titles that are valid and not CL123456 or IV123456.
 TitleNumber or LesseeTitle (when LeaseExtension ServiceTitleType) IV123456
  • TypeCode: ‘20’
  • Code: bg.title.invalid.specific
  • Description: “Title number IV123456 is invalid.”
  • Test: Electronic Document Registration Service 03
  • Test purpose: Lodge an application out of hours
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘10’
  • MessageDescription: “Service is not currently available. System has queued your request, please poll at specified time.”
  • ExpectedResponseDateTime: will be the next working day.
Login details Password landreg001
  • TypeCode: ‘10’
  • MessageDescription: “Service is not currently available. System has queued your request, please poll at specified time.”
  • ExpectedResponseDateTime: will be the next working day.
Login details User locale En
  • TypeCode: ‘10’
  • MessageDescription: “Service is not currently available. System has queued your request, please poll at specified time.”
  • ExpectedResponseDateTime: will be the next working day.
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘10’
  • MessageDescription: “Service is not currently available. System has queued your request, please poll at specified time.”
  • ExpectedResponseDateTime: will be the next working day.
Login details Message ID testoutofhours
  • TypeCode: ‘10’
  • MessageDescription: “Service is not currently available. System has queued your request, please poll at specified time.”
  • ExpectedResponseDateTime: will be the next working day.
ProductType All All eligible data
  • TypeCode: ‘10’
  • MessageDescription: “Service is not currently available. System has queued your request, please poll at specified time.”
  • ExpectedResponseDateTime: will be the next working day.
  • Test: Electronic Document Registration Service 04
  • Test purpose: Lodge an application correctly (default test)
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘10’
  • MessageDescription: “Your application has been accepted.”
  • PriorityDateTime: now
  • ABR (Application Barcode Reference): A123BCD
Login details Password landreg001
  • TypeCode: ‘10’
  • MessageDescription: “Your application has been accepted.”
  • PriorityDateTime: now
  • ABR: A123BCD
Login details User locale En
  • TypeCode: ‘10’
  • MessageDescription: “Your application has been accepted.”
  • PriorityDateTime: now
  • ABR: A123BCD
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘10’
  • MessageDescription: “Your application has been accepted.”
  • PriorityDateTime: now
  • ABR: A123BCD
Login details Message ID any
  • TypeCode: ‘10’
  • MessageDescription: “Your application has been accepted.”
  • PriorityDateTime: now
  • ABR: A123BCD
  • ProductType
  • Note: Do not use any red data from the above tests as this may trigger that test to run instead of this one.
 All All eligible data
  • TypeCode: ‘10’
  • MessageDescription: “Your application has been accepted.”
  • PriorityDateTime: now
  • ABR: A123BCD
  • Test: Electronic Document Registration Service 05
  • Test purpose: Lodge an application with an incorrect first priority
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.priority.startvalue
  • Description: “Application priority must begin with 1.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.priority.startvalue
  • Description: “Application priority must begin with 1.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.priority.startvalue
  • Description: “Application priority must begin with 1.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.priority.startvalue
  • Description: “Application priority must begin with 1.”
Login details Message ID any
  • TypeCode: ‘20’
  • Code: bg.drs.priority.startvalue
  • Description: “Application priority must begin with 1.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.priority.startvalue
  • Description: “Application priority must begin with 1.”
ProductType Priority First priority > 1
  • TypeCode: ‘20’
  • Code: bg.drs.priority.startvalue
  • Description: “Application priority must begin with 1.”
  • Test: Electronic Document Registration Service 07
  • Test purpose: Lodge an application with missing mandatory roles
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.application.roletype
  • Description: Role type of <Role Type> must be present for <Application Type> <Application Priority>
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.application.roletype
  • Description: Role type of <Role Type> must be present for <Application Type> <Application Priority>
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.application.roletype
  • Description: Role type of <Role Type> must be present for <Application Type> <Application Priority>
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.application.roletype
  • Description: Role type of <Role Type> must be present for <Application Type> <Application Priority>
Login details Message ID any
  • TypeCode: ‘20’
  • Code: bg.drs.application.roletype
  • Description: Role type of <Role Type> must be present for <Application Type> <Application Priority>
ProductType The table below sets out the application types and roles required. To run this test, create the required application and miss off the required role. To pass schema validation all parties must have at least one role. So in effect at least two applications will be needed with one (from the list here) containing no linked parties or roles. The error message will contain the application details with the missing role type. All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.application.roletype
  • Description: Role type of <Role Type> must be present for <Application Type> <Application Priority>
Application Role Required
Charge Borrower
Note Agreed Maximum Amount of Security (CH3) Borrower
Transfer
  • Transferee
  • Transferor
Transfer by Law of Operation
  • Transferee
  • Transferor
Transfer not for value
  • Transferee
  • Transferor
Transfer of Charge
  • Transferee
  • Transferor
Transfer Subject to a Charge
  • Transferee
  • Transferor
Entry of Restrictive Covenent Transferor
Lease
  • Lessor
  • Lessee
  • Test: Electronic Document Registration Service 08
  • Test purpose: Lodge an application with incorrect mandatory representation
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.party.representation
  • Description: “Representation for <party name> must be provided.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.party.representation
  • Description: “Representation for <party name> must be provided.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.party.representation
  • Description: “Representation for <party name> must be provided.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.party.representation
  • Description: “Representation for <party name> must be provided.”
Login details Message ID any
  • TypeCode: ‘20’
  • Code: bg.drs.party.representation
  • Description: “Representation for <party name> must be provided.”
  • ProductType
  • The table below sets out the roles, for certain application types, that require mandatory representation. To invoke the test submit a party that has the required roleType and application type but is missing representation.
All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.party.representation
  • Description: “Representation for <party name> must be provided.”
Application type Representation for roles
Charge Lender
Any other application type (other than a charge)
  • Transferee
  • Transferor
  • Borrower
  • Lessor
  • Lessee
  • Test: Electronic Document Registration Service 09
  • Test purpose: Lodge an application with no lodging conveyancer representation
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.lodging.representation
  • Description: “Representation by the Lodging Conveyancer must be provided for one of the parties to the application.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.lodging.representation
  • Description: “Representation by the Lodging Conveyancer must be provided for one of the parties to the application.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.lodging.representation
  • Description: “Representation by the Lodging Conveyancer must be provided for one of the parties to the application.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.lodging.representation
  • Description: “Representation by the Lodging Conveyancer must be provided for one of the parties to the application.”
Login details Message ID any
  • TypeCode: ‘20’
  • Code: bg.drs.lodging.representation
  • Description: “Representation by the Lodging Conveyancer must be provided for one of the parties to the application.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.lodging.representation
  • Description: “Representation by the Lodging Conveyancer must be provided for one of the parties to the application.”
ProductType Submit the request with no parties containing representation by the Lodging Conveyancer. Submit the request with no parties containing representation by the Lodging Conveyancer.
  • TypeCode: ‘20’
  • Code: bg.drs.lodging.representation
  • Description: “Representation by the Lodging Conveyancer must be provided for one of the parties to the application.”
  • Test: Electronic Document Registration Service 10
  • Test purpose: Lodge an application with a missing identity form
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
Login details Message ID any
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
ProductType IdentityEvidence Any XML valid input
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
ProductType Party Uses above representation provided in IdentityEvidence
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
ProductType SupportingDocument Missing identity form
  • TypeCode: ‘20’
  • Code: bg.drs.identityform
  • Description: “An Identity Form must be provided.”
  • Test: Electronic Document Registration Service 11
  • Test purpose: Lodge an application without confirming AP1 (Alteration of Register) warning is understood
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.ap1warning
  • Description: “Certification is required that the AP1 warning has been read and understood.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.ap1warning
  • Description: “Certification is required that the AP1 warning has been read and understood.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.ap1warning
  • Description: “Certification is required that the AP1 warning has been read and understood.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.ap1warning
  • Description: “Certification is required that the AP1 warning has been read and understood.”
Login details Message ID any
  • TypeCode: ‘20’
  • Code: bg.drs.ap1warning
  • Description: “Certification is required that the AP1 warning has been read and understood.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.ap1warning
  • Description: “Certification is required that the AP1 warning has been read and understood.”
ProductType AP1WarningUnderstood False
  • TypeCode: ‘20’
  • Code: bg.drs.ap1warning
  • Description: “Certification is required that the AP1 warning has been read and understood.”
  • Test: Electronic Document Registration Service 12
  • Test purpose: Lodge an application with an incorrect priority order
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.priority.nonconsecutive
  • Description: “Application priority must be in consecutive numerical order.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.priority.nonconsecutive
  • Description: “Application priority must be in consecutive numerical order.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.priority.nonconsecutive
  • Description: “Application priority must be in consecutive numerical order.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.priority.nonconsecutive
  • Description: “Application priority must be in consecutive numerical order.”
Login details Message ID Any schema valid entry
  • TypeCode: ‘20’
  • Code: bg.drs.priority.nonconsecutive
  • Description: “Application priority must be in consecutive numerical order.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.priority.nonconsecutive
  • Description: “Application priority must be in consecutive numerical order.”
ProductType Priority Ensure 2 or more applications have non consecutive priority numbers
  • TypeCode: ‘20’
  • Code: bg.drs.priority.nonconsecutive
  • Description: “Application priority must be in consecutive numerical order.”
  • Test: Electronic Document Registration Service 13
  • Test purpose: Lodge an application with missing mandatory documentation
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.application.document
  • Description: Application <application name> must be supported by a document
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.application.document
  • Description: Application <application name> must be supported by a document
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.application.document
  • Description: Application <application name> must be supported by a document
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.application.document
  • Description: Application <application name> must be supported by a document
Login details Message ID Any schema valid entry
  • TypeCode: ‘20’
  • Code: bg.drs.application.document
  • Description: Application <application name> must be supported by a document
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.application.document
  • Description: Application <application name> must be supported by a document
ProductType Application Only a discharge or change of address do not require any mandatory documents. Submit any other application without documents (neither application document nor supporting document)
  • TypeCode: ‘20’
  • Code: bg.drs.application.document
  • Description: Application <application name> must be supported by a document
  • Test: Electronic Document Registration Service 14
  • Test purpose: Lodge an application against a scheme title
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: schema.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: schema.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: schema.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: schema.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
Login details Message ID Any
  • TypeCode: ‘20’
  • Code: schema.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: schema.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
ProductType TitleNumber or LesseeTitle (when LeaseExtension ServiceTitleType) SC123456
  • TypeCode: ‘20’
  • Code: schema.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”

Scheme titles (originally known as “improvement scheme titles”) were introduced to facilitate the registration of areas of land acquired piecemeal. This is for slum clearance and redevelopment, normally by public authorities such as local councils and new town development corporations.

  • Test: Electronic Document Registration Service 15
  • Test purpose: Lodge an application against caution title
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
Login details Message ID Any
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”
ProductType TitleNumber or LesseeTitle (when LeaseExtension ServiceTitleType) CT123456
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Applications for a dealing against scheme titles or caution titles are not supported.”

A caution against first registration is a means of protecting an interest in an unregistered estate in land. When registered, a caution is given its own caution title number.

  • Test: Electronic Document Registration Service 16
  • Test purpose: Lodge an application with lodging conveyancer as representing transferee with no address for service
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: bg.drs.transferee.afs
  • Description: “As you are representing the transferee the address for service is required.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: bg.drs.transferee.afs
  • Description: “As you are representing the transferee the address for service is required.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: bg.drs.transferee.afs
  • Description: “As you are representing the transferee the address for service is required.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.transferee.afs
  • Description: “As you are representing the transferee the address for service is required.”
Login details Message ID Any
  • TypeCode: ‘20’
  • Code: bg.drs.transferee.afs
  • Description: “As you are representing the transferee the address for service is required.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.drs.transferee.afs
  • Description: “As you are representing the transferee the address for service is required.”
ProductType Submit the request with a transferee party containing representation by the Lodging Conveyancer but with no address for service. Submit the request with a transferee party containing representation by the Lodging Conveyancer but with no address for service.
  • TypeCode: ‘20’
  • Code: bg.drs.transferee.afs
  • Description: “As you are representing the transferee the address for service is required.”
  • Test: Electronic Document Registration Service 17
  • Test purpose: Lodge an application against a franchise title
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: franchise.title
  • Description: “Applications for a New Lease, Lease Extension or a Transfer of Part against an affecting franchise or relating franchise are not supported.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: franchise.title
  • Description: “Applications for a New Lease, Lease Extension or a Transfer of Part against an affecting franchise or relating franchise are not supported.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: franchise.title
  • Description: “Applications for a New Lease, Lease Extension or a Transfer of Part against an affecting franchise or relating franchise are not supported.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: franchise.title
  • Description: “Applications for a New Lease, Lease Extension or a Transfer of Part against an affecting franchise or relating franchise are not supported.”
Login details Message ID Any
  • TypeCode: ‘20’
  • Code: franchise.title
  • Description: “Applications for a New Lease, Lease Extension or a Transfer of Part against an affecting franchise or relating franchise are not supported.”
    ProductType <TitleNumber> can be entered under:
    • <LessorTitle>
    • <TransferorTitle>
    • <AdditionalTitle>
All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: franchise.title
  • Description: “Applications for a New Lease, Lease Extension or a Transfer of Part against an affecting franchise or relating franchise are not supported.”
    ProductType <TitleNumber> can be entered under:
    • <LessorTitle>
    • <TransferorTitle>
    • <AdditionalTitle>
TitleNumber or LesseeTitle (when LeaseExtension ServiceTitleType) FT123456
  • TypeCode: ‘20’
  • Code: franchise.title
  • Description: “Applications for a New Lease, Lease Extension or a Transfer of Part against an affecting franchise or relating franchise are not supported.”

Under section 3, Land Registration Act 2002, a franchise may be the subject of an application for voluntary first registration. The most common franchise is the right to hold a market or fair.

  • Test: Electronic Document Registration Service 18
  • Test purpose: Lodge an application against a pending new title
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: pending.title
  • Description: “The title number provided PT123456 is a pending new title. Applications for a New Lease, Lease Extension or a Transfer of Part will not be permitted against a pending new title.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: pending.title
  • Description: “The title number provided PT123456 is a pending new title. Applications for a New Lease, Lease Extension or a Transfer of Part will not be permitted against a pending new title.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: pending.title
  • Description: “The title number provided PT123456 is a pending new title. Applications for a New Lease, Lease Extension or a Transfer of Part will not be permitted against a pending new title.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: pending.title
  • Description: “The title number provided PT123456 is a pending new title. Applications for a New Lease, Lease Extension or a Transfer of Part will not be permitted against a pending new title.”
Login details Message ID Any
  • TypeCode: ‘20’
  • Code: pending.title
  • Description: “The title number provided PT123456 is a pending new title. Applications for a New Lease, Lease Extension or a Transfer of Part will not be permitted against a pending new title.”
ProductType <TitleNumber> can be entered under:
  • <LessorTitle>
  • <TransferorTitle>
  • <AdditionalTitle>
 		All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: pending.title
  • Description: “The title number provided PT123456 is a pending new title. Applications for a New Lease, Lease Extension or a Transfer of Part will not be permitted against a pending new title.”
ProductType <TitleNumber> can be entered under:
  • <LessorTitle>
  • <TransferorTitle>
  • <AdditionalTitle>
 		TitleNumber or LesseeTitle (when LeaseExtension ServiceTitleType) PT123456
  • TypeCode: ‘20’
  • Code: pending.title
  • Description: “The title number provided PT123456 is a pending new title. Applications for a New Lease, Lease Extension or a Transfer of Part will not be permitted against a pending new title.”
  • Test: Electronic Document Registration Service 19
  • Test purpose: Lodge an application against a lessee title that is not leasehold
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Lessees title number provided LT123456 does not match a leasehold title held by Land Registry.”
Login details Password landreg001
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Lessees title number provided LT123456 does not match a leasehold title held by Land Registry.”
Login details User locale En
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Lessees title number provided LT123456 does not match a leasehold title held by Land Registry.”
Login details AdditionalProviderFilter Any eligible data
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Lessees title number provided LT123456 does not match a leasehold title held by Land Registry.”
Login details Message ID Any
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Lessees title number provided LT123456 does not match a leasehold title held by Land Registry.”
ProductType All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Lessees title number provided LT123456 does not match a leasehold title held by Land Registry.”
ProductType LesseeTitle LT123456
  • TypeCode: ‘20’
  • Code: caution.title
  • Description: “Lessees title number provided LT123456 does not match a leasehold title held by Land Registry.”
  • Test: Electronic Document Registration Service 20
  • Test purpose: Lodge a charge application
Field group Field name Input Expected output
Login details User ID BGUser001
Login details Password landreg001
Login details User locale En
Login details AdditionalProviderFilter Any eligible data
Login details Message ID Any
ProductType <ChargeDate> can be entered under: <ChargeApplicationType> All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.chargedate.invalid
  • Description: “Application Charge <X> Charge Date must not be in the future.”
    ProductType <ChargeDate> can be entered under:
  • <ChargeApplicationType>
    •
ChargeDate 01/01/5000 (Any future date)
  • TypeCode: ‘20’
  • Code: bg.chargedate.invalid
  • Description: “Application Charge <X> Charge Date must not be in the future.”
<MDRef> can be entered under: <ChargeApplicationType> MDRef A
  • TypeCode: ‘20’
  • Code: bg.mdref.invalid
  • Description: “Application Charge <X> MDRef A is invalid.“
<MDRef> can be entered under: <ChargeApplicationType> MDRef MD999Z
  • TypeCode: ‘20’
  • Code: bg.mdref.validation
  • Description: “Application Charge <X> MDRef MD999Z validation failed.”
  • Test: Electronic Document Registration Service 21
  • Test purpose: Lodge a single charge application
Field group Field name Input Expected output
Login details User ID BGUser001
Login details Password landreg001
Login details User locale En
Login details AdditionalProviderFilter Any eligible data
Login details Message ID Any
ProductType <FeeInPence> can be entered under: <ChargeApplicationType> All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.feeinpence.invalid
  • Description: “Application Charge <X> FeeinPence must not be below 2000.”
ProductType <FeeInPence> can be entered under: <ChargeApplicationType> FeeInPence 12
  • TypeCode: ‘20’
  • Code: bg.feeinpence.invalid
  • Description: “Application Charge <X> FeeinPence must not be below 2000.”
  • Test: Electronic Document Registration Service 22
  • Test purpose: Lodge a single application
Field group Field name Input Expected output
Login details User ID BGUser001
Login details Password landreg001
Login details User locale En
Login details AdditionalProviderFilter Any eligible data
Login details Message ID Any
ProductType <FeeInPence> can be entered under: <ChargeApplicationType> All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.feeinpence.invalid
  • Description: “Application Charge <X> FeeinPence must not be below 2000.”
ProductType <FeeInPence> can be entered under: <ChargeApplicationType> FeeInPence 12
  • TypeCode: ‘20’
  • Code: bg.feeinpence.invalid
  • Description: “Application Charge <X> FeeinPence must not be below 2000.”
  • Test: Electronic Document Registration Service 23
  • Test purpose: Lodge a single discharge application
Field group Field name Input Expected output
Login details User ID BGUser001
Login details Password landreg001
Login details User locale En
Login details AdditionalProviderFilter Any eligible data
Login details Message ID Any
ProductType <FeeInPence> can be entered under: <OtherApplicationType> All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.feeinpence.discharge.invalid
  • Description: “Application Charge <X> FeeinPence must be 0.”
ProductType <FeeInPence> can be entered under: <OtherApplicationType> FeeInPence 1000
  • TypeCode: ‘20’
  • Code: bg.feeinpence.discharge.invalid
  • Description: “Application Charge <X> FeeinPence must be 0.”
  • Test: Electronic Document Registration Service 24
  • Test purpose: Lodge an application with charge and discharge
Field group Field name Input Expected output
Login details User ID BGUser001
Login details Password landreg001
Login details User locale En
Login details AdditionalProviderFilter Any eligible data
Login details Message ID Any
ProductType <FeeInPence> can be entered under: <OtherApplicationType> <ChargeApplicationType> All not mentioned below All eligible data
  • TypeCode: ‘20’
  • Code: bg.feemismatch.charge.invalid
  • Description: “FeeInPence of charge must match TotalFeeInPence.”
ProductType <FeeInPence> can be entered under: <OtherApplicationType> FeeInPence (of charge) 3000
  • TypeCode: ‘20’
  • Code: bg.feemismatch.charge.invalid
  • Description: “FeeInPence of charge must match TotalFeeInPence.”
ProductType <FeeInPence> can be entered under: <OtherApplicationType> FeeInPence (of discharge) 0
  • TypeCode: ‘20’
  • Code: bg.feemismatch.charge.invalid
  • Description: “FeeInPence of charge must match TotalFeeInPence.”
ProductType <FeeInPence> can be entered under: <OtherApplicationType> TotalFeeInPence 0
  • TypeCode: ‘20’
  • Code: bg.feemismatch.charge.invalid
  • Description: “FeeInPence of charge must match TotalFeeInPence.”

2. Electronic Document Registration Service Polling Service

  • Test: Electronic Document Registration Service Poll 01
  • Test purpose: Lodge an application correctly
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘30’
  • MessageDetails: “Your application has been processed.”
  • ResultTypeCode: ‘10’
  • DespatchDocument:
  • filename: Land Registry Documents.zip
  • XmlRegisters:
Login details Password landreg001
  • TypeCode: ‘30’
  • MessageDetails: “Your application has been processed”
  • ResultTypeCode: ‘10’
  • DespatchDocument:
  • filename: Land Registry Documents.zip
  • XmlRegisters:
Login details User locale En
  • TypeCode: ‘30’
  • MessageDetails: “Your application has been processed”
  • ResultTypeCode: ‘10’
  • DespatchDocument:
  • filename: Land Registry Documents.zip
  • XmlRegisters:
Login details Message ID returnType1
  • TypeCode: ‘30’
  • MessageDetails: “Your application has been processed”
  • ResultTypeCode: ‘10’
  • DespatchDocument:
  • filename: Land Registry Documents.zip
  • XmlRegisters:
  • Test: Electronic Document Registration Service Poll 02
  • Test purpose: Lodge an application correctly with an incorrect total Fee
Field group Field name Input Expected output
Login details User ID BGUser001
  • TypeCode: ‘30’
  • MessageDetails: “Your application has been processed”
  • ResultTypeCode: ‘10’
  • ActualFee: 50000
  • FeeAdjusted: true
  • DespatchDocument:
  • filename: Land Registry Documents.zip
  • XmlRegisters:
Login details Password landreg001
  • TypeCode: ‘30’
  • MessageDetails: “Your application has been processed”
  • ResultTypeCode: ‘10’
  • ActualFee: 50000
  • FeeAdjusted: true
  • DespatchDocument:
  • filename: Land Registry Documents.zip
  • XmlRegisters:
Login details User locale En
  • TypeCode: ‘30’
  • MessageDetails: “Your application has been processed”
  • ResultTypeCode: ‘10’
  • ActualFee: 50000
  • FeeAdjusted: true
  • DespatchDocument:
  • filename: Land Registry Documents.zip
  • XmlRegisters:
Login details Message ID returnType2
  • TypeCode: ‘30’
  • MessageDetails: “Your application has been processed”
  • ResultTypeCode: ‘10’
  • ActualFee: 50000
  • FeeAdjusted: true
  • DespatchDocument:
  • filename: Land Registry Documents.zip
  • XmlRegisters: