Short answer: A GL detail report lists every transaction behind an account balance, with posting date, source type, reference and memo. To trace a property number back: (1) confirm the GL detail total matches the number you're questioning, (2) filter by the right property, entity, account and period, (3) read each line's source type and dates, (4) group the lines into the usual causes, such as late or duplicate bills, accruals and reversals, reclasses, allocations or miscoding, (5) open the source document behind each line that matters, and (6) explain the number or correct it. Most "the numbers don't match" problems turn out to be filter or period problems, not missing transactions.
Every property number eventually gets questioned. An owner asks why water doubled. A lender asks why repairs on the T-12 don't match last quarter. An auditor picks a balance and asks for support. The answer almost always starts in the same place: the general ledger detail report.
The summary report says what the number is. The GL detail says why.
Must Read: The Owner Statement: Answering the Question Before the Owner Asks
Table of Contents
-
What the GL Detail Report Shows
-
Where Tracing Comes Up
-
Tracing vs Vouching
-
Step 1: Start From the Right Total
-
Step 2: Filter for the Property
-
Step 3: Read Each Line
-
Step 4: Group the Lines Into Causes
-
Step 5: Open the Source Document
-
Step 6: Explain or Correct
-
Worked Example: The $8,400 Water Bill
-
Making Tracing Faster
-
Checklist
-
Common Mistakes
-
FAQs
-
Conclusion
What the GL Detail Report Shows
Column names vary by system, but most GL detail reports carry:
|
Column |
What it tells you |
|---|---|
|
Account |
The GL account the line hit |
|
Posting date / period |
The accounting period the line counts in |
|
Transaction date |
When the underlying event happened (bill date, service date, entry date) |
|
Source type |
Bill, payment, journal entry, accrual, reversal, allocation, receipt, invoice |
|
Reference / document number |
The link back to the source record |
|
Name |
Vendor, tenant or owner |
|
Memo / description |
What the preparer wrote, often the most useful clue |
|
Property / entity dimensions |
Property, location, class, department or subsidiary, depending on the system |
|
Debit / credit / amount |
The value, and its direction |
|
Running balance |
How the account built up over the period |
In property accounting, the property and entity dimensions matter most. One GL account, such as Water & Sewer, usually spans many properties and owners. A GL detail without the right property filter answers a different question.
Where Tracing Comes Up
-
Owner questions about a statement line.
-
Budget variance notes at month-end.
-
Lender reporting, where T-12 lines need to tie to the closed GL. See the quarterly lender reporting package.
-
CAM reconciliations, where recoverable expense pools get challenged by tenants.
-
Audits and reviews, where an auditor selects balances or entries for support.
-
Management transitions, where the new manager needs to understand opening balances.
Tracing vs Vouching
Audit terminology commonly separates two directions:
|
Direction |
Common term |
Question it answers |
|---|---|---|
|
Ledger → source document |
Vouching |
Is everything recorded real and supported? |
|
Source document → ledger |
Tracing |
Is everything that happened recorded? |
"Tracing a number back," as property teams use the phrase, is mostly vouching: starting from a balance and checking the support. Both directions are worth knowing. A missing utility bill won't appear in the GL detail at all, so a spike or a gap may need checking from the source side too. Auditing standards such as PCAOB AS 1105 describe inspecting records and documents as one source of audit evidence.
Step 1: Start From the Right Total
Before reading a single line, confirm that the GL detail total equals the number in question. That number might be the owner statement line, the T-12 figure or the trial balance.
If the totals don't match, stop. The difference is almost always one of these:
-
Period: the statement uses a cutoff or posting period different from the report's date range.
-
Basis: a cash-basis owner statement against an accrual-basis GL.
-
Filter: a property, entity or subsidiary is missing or extra.
-
Account mapping: the statement line combines several GL accounts.
-
Timing: entries posted after the statement was run.
The owner ledger has the same discipline, agreeing a subledger to the GL. See the owner ledger.
Step 2: Filter for the Property
Filter by:
-
Account: every account that feeds the line in question, not just one.
-
Property: the property dimension, whatever your system calls it.
-
Entity / owner: the legal entity or subsidiary.
-
Period: by posting period, not transaction date, if you're matching a closed period.
Then compare against the same filters for prior months. A spike is easier to read next to a normal month.
Step 3: Read Each Line
For each line, note:
-
Source type: a bill and a journal entry need different follow-up.
-
Posting date vs transaction or service date: a gap often means a late bill or a prior-period item.
-
Memo: "reclass," "accrual," "reverse," "alloc," "true-up" and "per owner" all point to manual entries.
-
Who entered it, where the system records it: unusual preparers or approvers are worth a look.
-
Direction: credits in an expense account usually mean reversals, refunds or reclasses out.
Step 4: Group the Lines Into Causes
Most unexpected property numbers come from a short list of causes:
|
What you see in the GL detail |
What it usually means |
What to check |
|---|---|---|
|
Two bills from the same vendor in one month |
Late prior-month bill, or a duplicate |
Service dates on each invoice |
|
Accrual with no matching reversal, or the reverse |
Accrual set up in one period and reversed in another |
Accrual schedule and reversal dates |
|
Journal entry with "reclass" memo |
Cost moved between accounts or properties |
Support for the reclass and who approved it |
|
Allocation entry |
Share of a shared cost (master meter, shared staff, portfolio contract) |
Allocation basis and whether it changed |
|
Bill coded to this property for a vendor account you don't recognise |
Miscoding from another property |
Account number or service address on the invoice |
|
Credit in an expense account |
Refund, reversal or reclass out |
Source document for the credit |
|
Round-number journal entry with no reference |
Estimate or manual adjustment |
Supporting schedule; may need follow-up |
|
Intercompany entry |
Cost charged between related entities |
Matching entry on the other entity's books |
Step 5: Open the Source Document
For each line that drives the variance, open what's behind it:
-
Bills: the vendor invoice, plus the PO or work order where relevant.
-
Journal entries: the supporting schedule or calculation, and its approval.
-
Allocations: the allocation schedule and basis.
-
Receipts and charges: the lease charge, tenant ledger or deposit record.
Supporting documents such as invoices, paid bills and account statements are what back up the entries in the books, as the IRS explains in its guidance on what records to keep. A line with no document attached is a finding in itself.
Step 6: Explain or Correct
Each line ends in one of three outcomes:
-
Correct and explained: write the variance note. For example: "Includes July water bill of $2,980 received late."
-
Wrong, correct it: reclass, reverse or recover. If the period is already closed and statements have gone out, follow your policy for prior-period corrections. Many teams correct in the current period with a clear note rather than reopening. See the owner statement cutoff.
-
Unsupported: get the document, or escalate.
Record what you found, even when nothing was wrong. The next person asking the same question gets the answer in minutes.
Worked Example: The $8,400 Water Bill
Question: Maple Court's September owner statement shows Water & Sewer at $8,400. The usual monthly figure is about $3,000.
GL detail: Water & Sewer, Maple Court, September (illustrative)
|
Date |
Source |
Name / memo |
Amount |
|---|---|---|---|
|
Sep 1 |
Journal entry (reversal) |
Reverse August water accrual |
($3,000) |
|
Sep 5 |
Bill |
City Water: August service |
$3,050 |
|
Sep 6 |
Bill |
City Water: July service (received late) |
$2,980 |
|
Sep 18 |
Bill |
City Water: account ending 4471 |
$2,370 |
|
Sep 30 |
Journal entry (accrual) |
Accrue September water estimate |
$3,000 |
|
Total |
$8,400 |
Findings:
|
Line |
What it is |
Outcome |
|---|---|---|
|
Aug reversal + Aug bill |
Normal: the accrual is replaced by the actual bill (net $50) |
Correct |
|
July bill |
Real Maple Court cost, but July wasn't accrued, so it lands in September |
Correct, add a variance note |
|
Account ending 4471 |
Service address on the invoice is Elm Plaza |
Wrong property: reclass $2,370 to Elm Plaza |
|
September accrual |
Normal estimate |
Correct |
After the reclass, September is $6,030, of which $2,980 is the late July bill. The variance note practically writes itself, and Elm Plaza's owner now carries their own water cost.
Making Tracing Faster
Tracing is slow when the GL, the documents and the property dimensions live in separate places. It's fast when you can drill from a statement line into the GL detail, and from a GL line into the attached invoice, without leaving the system.
A few habits help in any system:
-
Attach source documents to transactions at entry, not at audit time.
-
Require a memo and a reference on every manual journal entry.
-
Use consistent memo words for accruals, reversals, reclasses and allocations.
-
Keep the property and entity dimensions mandatory on every expense line.
For example, property reports that drill down from summary to transaction can shorten an owner question from an afternoon of exports to a few clicks.
Checklist
-
GL detail total agrees to the number being questioned
-
Differences in period, basis, filter or account mapping explained before going further
-
Filtered by every feeding account, property, entity and period
-
Compared to at least one normal prior month
-
Each line's source type, dates and memo read
-
Lines grouped into causes
-
Source document opened for every line driving the variance
-
Miscoded lines reclassed, with support
-
Unsupported entries followed up
-
Variance note or correction recorded
-
Prior-period corrections handled per policy
Common Mistakes
-
Reading lines before agreeing the total. You end up explaining a different number.
-
Filtering by transaction date for a closed period. The posting period decides what's in the statement.
-
Checking one account when the line combines several. Part of the answer sits in another account.
-
Stopping at the memo. Memos explain intent, not support. Open the document.
-
Treating every journal entry as suspicious, or none. Accruals and reversals are routine; unsupported round-number entries aren't.
-
Fixing it without a note. The same question comes back next quarter.
-
Only tracing from the ledger. A bill that was never entered won't show up in the GL detail at all.
Frequently Asked Questions
1. What is a GL detail report?
A report listing every transaction posted to one or more general ledger accounts over a period, with dates, source type, reference, memo and amount, so you can see what makes up a balance.
2. How is a GL detail report different from a trial balance?
A trial balance shows each account's balance. The GL detail shows the individual transactions that produced those balances.
3. How do you trace a number back to its source document?
Agree the GL detail total to the number, filter by property, entity, account and period, read each line, group the lines into causes, and open the invoice, schedule or record behind each significant line.
4. What is the difference between vouching and tracing?
In common audit usage, vouching runs from the ledger to the source document, and tracing runs from the source document to the ledger.
5. Why doesn't the GL detail match the owner statement?
Usually because of period or cutoff, cash vs accrual basis, a missing or extra property or entity filter, account mapping, or entries posted after the statement was run.
6. What causes a sudden spike in a property expense?
Common causes include a late prior-month bill, an accrual and its reversal sitting in different periods, a reclass, an allocation change, a duplicate bill or a cost coded to the wrong property.
7. Should a miscoded expense be corrected in a closed period?
That depends on your close policy and whether statements have gone out. Many teams correct it in the current period with a clear note rather than reopening a closed period.
8. How can tracing be made faster?
Attach documents at entry, require memos and references on manual journal entries, keep property and entity dimensions mandatory, and use reports that drill down from summary to transaction.
Conclusion
A property number is only as defensible as the trail behind it. Agree the total, filter for the property, read the lines, group them into causes and open the documents. Most questions answer themselves by the fourth step. Do it the same way every time and record what you find, and the GL detail report becomes the fastest way to settle a question about any number.
Note: This article is for general information only and isn't legal, tax, audit or accounting advice. Reporting, correction and documentation requirements vary by entity, agreement and jurisdiction. Confirm your approach with a qualified professional.