Integration
InventoryBase
Link completed inventories, check-in and check-out reports to the tenancy record, so the evidence sits with the rest of the file.
Every connection runs against your own account, with access granted by your own administrator.
Current status
Available
Category
Maintenance and inspections
Prerequisites
API access on your own InventoryBase account.
Verified read scope
Completed reports, photographs and condition findings
Verified write scope
Report references and follow-up actions recorded against the tenancy
Limitations
Report content is produced in InventoryBase. LETO records the findings and raises the follow-up.
Provider names describe compatibility. Their use does not imply endorsement or partnership.
How the connection works
InventoryBase produces inventories, check-in and check-out reports and periodic inspections. These documents drive a lot of downstream work, which is where LETO is useful.
How access is granted
Your administrator grants LETO access from inside your own InventoryBase account with the permissions listed above. Reports remain stored in InventoryBase; LETO reads them rather than copying them into a second library.
What changes day to day
When an inspection raises an action, LETO turns it into a tracked item against the tenancy and follows it up. Overdue inspections are chased with the inspector or the tenant, and the completed report is referenced in the tenancy history.
What stays with your team
Condition judgements, deposit deductions and any dispute response stay with your staff. LETO assembles the evidence; a person decides what it means.
Talk to us about InventoryBase
Tell us how your account is configured and we will set out exactly what can be connected, what access it needs and what the automation would write back.
We will set out exactly what connects to your account.