A tenant ledger is the transaction-by-transaction history of what a tenant was charged and what it paid, and in a diligence file it is the proof behind every number on the rent roll. Upload the ledger export or printout and get the charges, payments and credits, the running balance, the late fees, the prepaid and deposit amounts, and the aging pulled into clean structured fields, each citing its source row.
Upload a document to extract
Drop files here or click to upload
Up to 50 files, 50MB each
Uploading...
A rent roll tells you what a tenant is supposed to pay; the tenant ledger tells you what actually happened, charge by charge and payment by payment. In diligence and audit the ledger is the evidence, and reading it means separating the recurring charges from the one-time ones, the payments from the credits, and the current balance from months-old arrears. Each row names a ledger element, says what it records, and states what an abstractor is checking for.
| Ledger element | What it records | What you are checking for |
|---|---|---|
| Charges by code | Every amount billed to the tenant, base rent, CAM, taxes, insurance, and one-time charges, usually tagged by a charge code | Whether the recurring charges match the lease and the rent roll, and whether any charge looks out of place or duplicated |
| Payments and credits | Every payment received and every credit or concession applied against the charges | Whether the tenant pays on time and in full, and whether concessions are eroding the collected rent the roll implies |
| Running balance | The cumulative amount owed after each transaction, the balance carried forward line by line | The current balance and whether it is zero, prepaid, or in arrears, which is the number diligence actually cares about |
| Late fees and interest | Charges assessed for late or missed payments, and any interest on an overdue balance | A pattern of late fees signals a shaky tenant even when the balance is eventually paid, a credit-quality flag a rent roll hides |
| Prepaid rent and deposits | Amounts the tenant paid ahead and the security deposit held, shown as credits on the ledger | Whether prepaid rent inflates a single month's collections and whether the deposit on the ledger matches the lease |
| Aging buckets | The balance split into current, 30, 60, 90, and 90-plus days past due | How old the arrears are, since a balance 90 days out is a very different risk than one that is 15 days late |
| Period covered | The date range of the ledger, from the first transaction shown to the last | Whether the ledger covers enough history to judge payment behavior, not just a clean recent month |
The job is to turn a raw, transaction-level ledger, however it was exported, into clean fields that reconcile to a balance and surface the payment behavior behind it.
Every billed amount tagged by charge type, so recurring rent and CAM are separated from one-time charges and can be checked against the lease and the rent roll.
Every payment and every credit or concession applied, so what the tenant actually paid is clear rather than buried in a running column.
The cumulative balance carried line by line to a current figure, so the number that matters, what is owed today, is confirmed rather than assumed.
The late fees and interest assessed over the period, so a tenant that pays but always pays late is flagged as the credit risk it is.
Prepaid rent and the security deposit shown on the ledger, so a single inflated month is understood and the deposit is checked against the lease.
The balance split into current, 30, 60, 90, and 90-plus buckets, so the age of any arrears, and the real collection risk, is visible at a glance.
From a raw ledger export or printout to one reconciled record that shows what was charged, what was paid, what is owed, and how old the arrears are, with a source citation per field.
Export it from Yardi, MRI, AppFolio, RealPage, or QuickBooks, or upload a PDF or scanned printout. Any format works.
The model returns the charges by code, the payments and credits, the running balance, the late fees, the prepaid and deposit amounts, and the aging as structured fields.
Each field links to its source row. The output surfaces the current balance and the aging split so delinquency is obvious without reading the whole ledger.
Push the reconciled charges, payments, balance, and aging to Excel, CSV, JSON, or the API so every tenant's history is on one comparable schedule.
Last updated July 2026. What a tenant ledger is, how it differs from a rent roll, and why the running balance and aging are the numbers diligence and audit actually rely on.
A tenant ledger is the transaction-by-transaction record of everything a tenant has been charged and everything it has paid, kept by the landlord or property manager for each tenant. Every line is a charge, base rent, CAM, taxes, a late fee, or a payment or credit, and each line updates a running balance that shows what the tenant owes at that moment. It is the source document behind the rent roll: where the roll summarizes the current rent and balance, the ledger proves how that balance was reached. Abstracting it turns a raw, often messy, transaction list into clean fields that reconcile to a current balance and reveal the payment behavior behind it. The reconciled figures line up with the summary produced by rent roll abstraction and slot into the same diligence file as the leases on the commercial lease abstract template.
A rent roll is a point-in-time summary of every tenant, the current rent, term, and outstanding balance, while a tenant ledger is the full transaction history for a single tenant that shows how that balance was built charge by charge. The roll answers what everyone pays right now; the ledger answers what one tenant actually paid, when, and whether it was ever late. In diligence the roll is the overview and the ledger is the evidence: a buyer trusts a rent roll only after spot-checking the ledgers behind the numbers. That is why both get abstracted, and reading a roll well is its own skill covered in the guide to how to read a rent roll.
Read a tenant ledger by separating the three kinds of lines, charges, payments, and the resulting balance, and then following the running balance to the bottom to see what is owed today. Start with the recurring charges and confirm they match the lease and the rent roll; scan the payment column for gaps or partial payments; watch for late fees, which flag a tenant that struggles even if it eventually pays; and finish on the current balance and how old any arrears are. A ledger that ends at zero every month is a strong tenant; one that carries a growing 60- or 90-day balance is a risk the rent roll alone will not show you. The point of abstraction is to surface those signals without reading every line by hand.
The running balance is the cumulative amount the tenant owes after each transaction, carried forward line by line, so a charge increases it and a payment reduces it. A zero balance means the tenant is current; a positive balance means it is behind; a negative balance means it has prepaid or holds a credit. The final running balance is the single number most of diligence cares about, because it states, as of the ledger date, whether the tenant owes money and how much. Confirming that figure and tying it to the aging is the core of what a ledger abstract delivers.
Because the rent roll can be optimistic and the ledger cannot: it is the actual record of collections, and it exposes tenants that pay late, carry stale balances, or lean on concessions the roll does not show. A buyer underwriting a property, or an auditor testing reported income, uses the ledgers to verify that the rent the seller claims was actually collected and to age the receivables that are not. A stack of ledgers that all reconcile cleanly supports the valuation; a few that show mounting arrears change the price. Pulling those balances and aging into one comparable schedule is what makes the check fast, and the resulting income feeds the review that runs through purchase and sale agreement abstraction.
Yes, and a portfolio of ledgers exported from different systems in different formats is exactly where manual reconciliation breaks down. The model reads each ledger, whether it came out of Yardi, MRI, AppFolio, RealPage, or QuickBooks or as a scanned printout, and returns the charges by code, the payments and credits, the running balance, the late fees, the prepaid and deposit amounts, and the aging as structured fields. Accuracy depends on export quality, and every published accuracy figure in this category is self-reported, so test on your own messiest ledger first. The general tool is on lease abstraction software.
The transaction-by-transaction record of everything a tenant was charged and paid, with a running balance updated line by line. It is the source document behind the rent roll, proving how a tenant's current balance was reached.
A rent roll is a point-in-time summary of every tenant; a tenant ledger is the full transaction history for one tenant showing how its balance was built. The roll is the overview, the ledger is the evidence diligence checks it against.
Separate the charges, payments, and running balance; confirm recurring charges match the lease and rent roll; watch for late fees and partial payments; and finish on the current balance and how old any arrears are.
The cumulative amount owed after each transaction, carried forward line by line. Zero means current, positive means behind, negative means prepaid or credited. The final balance is the number diligence cares most about.
Because the rent roll can be optimistic and the ledger cannot. It is the actual record of collections and exposes late payers, stale balances, and concessions the roll hides, verifying that claimed rent was really collected.
Yes. The model reads each ledger from any system, Yardi, MRI, AppFolio, RealPage, or QuickBooks, and returns the charges, payments, running balance, late fees, prepaid amounts, and aging as structured fields, source-linked per row.
The summary the ledger balances reconcile to.
Learn moreThe expense side of the same diligence file.
Learn moreThe transaction the verified income supports.
Learn moreThe lease terms the charges are checked against.
Learn moreManage charges and balances across the portfolio.
Learn moreThe full overview of our AI lease abstraction tool.
Learn moreFor individuals and small teams beginning to automate document data capture.
USD / mo
$288 charged today
Choose extraction speed vs. model accuracy per job.
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
For growing teams that need bulk extraction, custom templates and spend analytics.
USD / mo
$888 charged today
Choose extraction speed vs. model accuracy per job.
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
High-volume extraction with API access, priority processing, and adjustable page tiers.
USD / mo
$ charged today
Scales with your selected tier.
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
Everything you need to know before you subscribe, or talk to our team if you need something specific.
Ask a questionEach plan includes a monthly allowance of pages, and the number you get depends on which AI model you choose at extraction time. Base AI processes pages faster; Pro AI delivers the highest field-level accuracy. Your allowance resets on your billing anniversary each month, unused pages do not roll over. A typical commercial lease runs 20 to 60 pages including amendments, so the Starter plan's 2,500 Base AI pages cover roughly 40 to 120 leases a month.
Once your included pages are used up, extraction pauses until the next billing cycle. You can upgrade your plan at any time mid-month, the higher allowance kicks in immediately and you are only charged the prorated difference for the remainder of the period.
Yes. You can switch from monthly to yearly billing at any renewal date to lock in the 50% discount. If you switch mid-cycle, the new rate takes effect at the start of your next billing period. Annual plans are non-refundable after the 14-day cancellation window.
All plans export to Excel XLSX and CSV. Plus adds QuickBooks (QBO) export and financial reports. Pro and Enterprise unlock JSON output via REST API and webhooks so you can push structured data directly into any ERP, RPA platform or internal system.
We do not use your documents to train or improve our own models, and files are encrypted in transit (TLS 1.2+) and at rest (AES-256). Extraction runs through a third-party model provider, so review their terms if your policy requires a contractual no-training commitment. You control retention: documents can be deleted from the workspace at any time, and we will remove everything on request.
Enterprise plans are tailored to your organisation's document volume, compliance requirements and integration needs. Pricing is based on committed monthly page volume with volume discounts at scale. Contracts include a Data Processing Agreement (DPA), custom security review support where required, and dedicated infrastructure options. Contact our sales team to get a custom quote.
Get a custom quote with volume pricing, a dedicated account manager, on-premise deployment options, and a GDPR DPA.