Property rental
Prepare tenant records and lease details with less repeated data entry.
IdScanly extracts structured information from supported identity documents for your property-management software. Use document data to prepare applicant records, populate the identity section of a draft lease and keep co-tenants clearly separated throughout the rental process.
Synthetic data. A possible integration, not a ready-made connector or a live product screen.
DEMO-0001DEMO-0001Property teams often move the same tenant details between application forms, internal records and lease templates. A name entered during an enquiry may need to be checked again at contract preparation, and a shared tenancy adds several people to the file.
A tenant ID OCR API helps with the document-reading and transcription work. Your application receives structured values from an image and uses the necessary fields to prepare a draft record for review.
This is useful for property-management platforms, letting agencies and operators handling rental administration across several properties. You choose when the document step belongs in the process and how the reviewed information is used.
An initial property enquiry may need only contact information. Introduce document capture when it is justified for the rental process, and explain the purpose in your application.
For example, a property manager preparing a lease can request the relevant identity evidence, extract the supported fields and check the names against the contract draft. This keeps identity administration connected to a defined task.
Your software can apply different access and retention rules to enquiries, incomplete applications and signed tenancies. OCR integration should support those distinctions rather than create a permanent document collection by default.
Use a supported passport, identity card or other required identity document to prepare the tenant’s identity fields. Staff review the extracted values before the approved details move into the lease and property-management record.
Create an individual record for each co-tenant and link those records to the shared tenancy. Separate document sessions make it easier to keep names, document references and signature roles associated with the correct person.
Where an updated identity document is required, prepare the changed fields for review without immediately replacing the approved record. Your application controls which administrative records need an update after confirmation.
The fields your workflow needs may include:
| Information | Potential use in your rental software |
|---|---|
| Name and available name components | Prepare the tenant’s identity section in a draft lease |
| Document type and number | Record a document reference where needed for the process |
| Issuing details | Provide context for document review |
| Validity dates | Support the administrative checks you define |
| Printed address, where present and supported | Supply a value for review when that document contains an address |
A document-derived address should remain identifiable as such. It may differ from a contact address, current residence or the property being rented. Your software should request and label those values separately when necessary.
Keep people separate from properties and agreements in your data model. One tenancy can involve several people, and each person may have more than one supporting document.
Supported capture feedback can guide an applicant when a document photo is blurred, affected by glare or missing an edge. Your interface can explain the correction and accept another image of the same document within the existing scan session.
Confidence values and available partial results also give your application information for the review experience. Missing fields should remain unresolved until a suitable correction or review supplies the necessary information.
IdScanly provides a backend REST API. Your team implements the applicant interface, staff review screen, property-management connection and lease-template mapping.
Test the document types common among your prospective tenants and the fields your agreements require. Available data varies by document, country, version and image quality.
Document OCR helps prepare identity information. Credit assessment, references, income checks and tenant-selection decisions belong to separate processes.
Read the API documentationNo. It extracts information from supported identity documents. It does not assess credit, affordability, income or suitability for a tenancy.
Your integration can map reviewed document fields into the identity section of your lease template. Contract generation and signing remain in your property software.
Create a separate person record and document sessions for each co-tenant, then link them to the same tenancy and the correct contract role.
No. An address can only be returned where it is present and supported. Collect other necessary address information through a separate, clearly labelled step.
Document extraction can also support guest registration. For pre-arrival and reception check-in workflows, see the dedicated hospitality page.
Define which fields your process requires, who can access them and how long you need them. Review IdScanly’s processing terms and your own rental-data obligations before production use.
Try your expected tenant documents and review the fields needed for your agreements. Share your application flow, property software and document requirements to discuss API integration.
Related: Hotel and short-stay guest registration · Customer onboarding OCR