A witnessed record is not just a log entry. It is an event that a human has confirmed, a receipt that has been generated, and a permanent addition to someone’s Trust Graph that cannot be undone. When an agent confirms a payment in Leja Professional, three things happen at once: the payment is recorded against the tenant’s RIN, a state-compliant PDF receipt is generated, and a witnessed event is added to the ledger. None of these steps is optional — all three must occur for the record to count. This is the core of how Leja works. The operational tool (the receipt, the agreement, the maintenance completion) is the instrument. The witnessed event it leaves behind is the product.Documentation Index
Fetch the complete documentation index at: https://relvor.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
What makes a record “witnessed”
Four properties distinguish a Leja witnessed record from an ordinary document or database entry: Human confirmation is required. No event enters the ledger without a person confirming it. Leja’s AI assists — it extracts payment details from bank alerts, flags anomalies, and detects potential fraud — but it never writes to the ledger on its own. The AI narrows down what needs human attention. A human makes the final call. Records are immutable once created. Once a witnessed event is written to the ledger, its contents cannot be changed. Incorrect records can be disputed and annotated — a correction note is added alongside the original — but the original event remains permanently. This is what makes the records trustworthy: their permanence creates accountability for everyone who confirms them. State compliance is automatic. Every receipt and tenancy agreement auto-applies the tenancy law of the state where the property is located — not where the agent is based, not where Leja’s offices are. The property’s state drives compliance. More on this below. A PDF receipt is always generated. Every confirmed payment produces a timestamped, state-compliant receipt in the formatLJA-YYYYMM-XXXX — for example, LJA-202604-0031. This number is unique per organisation. The receipt identifies the parties, the property, the amount, the period covered, and the stamp required by the relevant state law.
Witnessed records cannot be deleted. If a record contains an error — a wrong amount, a misidentified property, an incorrectly attributed payment — you can raise a dispute through Leja. The outcome of the dispute, including any correction, is added as an annotation alongside the original record. Both the original event and the correction remain permanently in the ledger. Neither party can remove either.
State compliance: automatic, not manual
Nigerian tenancy law varies by state. A receipt issued in Lagos must comply with the Lagos Tenancy Law 2011. An agreement signed in Ibadan must comply with the Oyo State Tenancy Law 2006. An eviction in Abuja must follow the FCT Tenancy Act 2008. Getting this wrong exposes agents and landlords to legal liability — and most agents today manage it manually, if at all. Leja reads the state from the property record and applies the correct legal framework automatically. You do not select a template. You do not check a box. The system knows which state the property is in and generates the right document.| State | Governing law | Active |
|---|---|---|
| Lagos | Lagos Tenancy Law 2011 | Yes |
| Oyo | Oyo State Tenancy Law 2006 | Yes |
| FCT / Abuja | FCT Tenancy Act 2008 | Milestone Wave 2 |
| Rivers | Rivers State Rental Accommodation Law | Milestone Wave 2 |
| All other states | State enum complete from day one — templates added progressively | Roadmap |
Event types that create witnessed records
Not every action in Leja creates a witnessed record — only actions that close a transaction loop and produce durable evidence. Payment confirmations When an agent confirms a rent payment, a witnessed payment event is added to the tenant’s Trust Graph and aLJA-YYYYMM-XXXX receipt is generated. This is the most frequent source of witnessed records in the system.
Lease signings and changes
When a tenancy agreement is signed and witnessed, when a lease is renewed, when a clean exit is confirmed, or when an eviction is resolved — all of these create a permanent lease event tied to both the tenant’s RIN and the property’s record.
Maintenance completions
When a maintenance job is confirmed as complete by both the requester and the service provider, a maintenance completion event is added to the property’s history and to the relevant RIN records. Disputed completions are also recorded with their outcome.
Disputes and resolutions
When a dispute is raised — by a tenant, a landlord, or an agent — the dispute itself is witnessed and logged. When it is resolved, whether amicably or through escalation, the resolution outcome becomes part of the permanent record. Disputes do not disappear from the ledger; they show how they were handled.