Why does my Yardi GL export total not match my financial statements?

The five most common causes are: (1) the export date range doesn't match the financial statement period — Yardi uses the posting date, not the transaction date; (2) some GL accounts are excluded from the export filter; (3) the export is set to cash basis while financials are on accrual; (4) intercompany/elimination entries appear in consolidated statements but not in individual entity exports; (5) closed-period adjustments were made after the original export was pulled.

How do I find which GL accounts are missing from my Yardi export?

Run a Chart of Accounts report for the entity in Yardi, then compare account numbers against those present in your GL export. Any account with a balance during the period but absent from the export has been excluded by your export filter. Check the account range settings in your GL export configuration under Reports > General Ledger > GL Detail.

What is the difference between posting date and transaction date in Yardi GL exports?

The transaction date is when an expense was incurred. The posting date is when it was entered in Yardi. These often differ — especially for year-end accruals posted in January that relate to the prior December. When your export filters by posting date, December accruals entered in January are excluded from the December export. Filter by transaction date when you need expenses to match the period they relate to.

Yardi GL Export Not Balancing: 5 Causes and How to Fix Each

By Angel Campa·Founder, CapVeriUpdated March 19, 20265 min read

A Yardi GL export that doesn't balance to your financial statements creates a cascade of problems: CAM reconciliation totals are wrong, tenant billings are off, and tracing the discrepancy back to its source takes hours. The good news is that the mismatch is almost always caused by one of five configuration issues — and each has a specific fix.

Cause 1: Wrong Date Range (Accrual Cutoff vs. Fiscal Year End)

This is the most common cause of GL export imbalances, and the most misunderstood.

Yardi's GL export lets you filter by either posting date or transaction date. Your financial statements are produced using transaction dates — expenses are recognized in the period they relate to, not the period they were entered. When your GL export filters by posting date, any entry that was posted after your fiscal year end — even if it relates to the prior year — gets excluded.

The specific scenario: Your fiscal year ends December 31. Your finance team posts December accruals during the first two weeks of January (normal close process). You run your Yardi GL export on January 15 filtered to December 31 — using posting date. Those January-posted accruals don't appear. Your statements include them. Gap.

How to fix it: In the GL export configuration, change the date filter from Posting Date to Transaction Date. Set the date range to match your fiscal year exactly. Re-export and reconcile.

Secondary date issue: Some organizations run a 13-period fiscal year or have a fiscal year that doesn't align with the calendar year. If your export date range is calendar-year and your statements are fiscal-year, they'll never balance.

Cause 2: Excluded Account Ranges

Every Yardi GL export has an account filter — a range of GL account numbers included in the export. If your chart of accounts has changed since the export filter was originally configured, new accounts may fall outside the filter range.

Common scenarios where accounts get excluded:

A new vendor category was added mid-year and assigned an account number outside the existing range
An account was reclassified and moved to a different number range
Capital expenditure accounts were intentionally excluded from the filter, but some OpEx expenses were posted to those accounts by mistake
Intercompany payable/receivable accounts were excluded from the operating export

How to find excluded accounts:

Run a full Chart of Accounts report for the entity (Reports > Setup > Chart of Accounts)
For each account with a non-zero balance during the period, note the account number
Cross-reference against your GL export — any account present in the Chart of Accounts report but absent from the export has been filtered out
Check the GL export account range filter in your report configuration

How to fix it: Update the account range filter in your GL export configuration to include all operating accounts. If you need to continue excluding capital accounts, define the exclusion specifically by account number rather than by range.

Cause 3: Accrual vs. Cash Mismatch

Yardi supports both accrual and cash basis reporting. If your GL export is configured on cash basis while your financial statements are on accrual (or vice versa), the totals will not match for any period where outstanding payables or receivables exist.

What accrual vs. cash means in practice:

Accrual: Expenses are recognized when incurred, regardless of when payment is made. A December utility bill paid in January appears in December on accrual basis.
Cash: Expenses are recognized when cash changes hands. That December utility bill paid in January appears in January on cash basis.

How to identify this problem: Look at the size of the discrepancy. If it equals roughly the sum of your year-end accruals (items in "Accounts Payable" that relate to the year being reconciled), you have a basis mismatch.

How to fix it: In the GL export report settings, locate the Basis field. Change to match your financial statements — almost always Accrual for commercial real estate. For CAM reconciliation purposes, accrual basis is generally required to match lease year expenses.

Cause 4: Intercompany and Elimination Entries

When your financial statements are consolidated across multiple entities, they include elimination entries that remove intercompany transactions. A Yardi GL export at the entity level does not include eliminations — nor should it. But this creates a permanent reconciling difference between entity-level exports and consolidated statements.

Example: Entity A owns a building. Entity B is a management company that charges management fees to Entity A. At the entity level, Entity A shows $50,000 in management fee expense. The consolidated statements eliminate this intercompany transaction. Your entity-level export shows $50,000. Consolidated statements show $0. The export doesn't balance to the consolidated statement by exactly $50,000.

This is not a bug. It is correct accounting. But it's frequently misidentified as an export error.

How to handle it: For CAM reconciliation purposes, you need entity-level (not consolidated) financial data. Management fees are typically recoverable from tenants as a CAM expense. Using the entity-level export — which includes the management fee — is correct for CAM purposes. Document the reconciling difference as "intercompany eliminations" in your audit trail.

Cause 5: Closed-Period Adjustments Not Captured

After a period is closed in Yardi, some adjustments can still be posted depending on your close settings. If you pull a GL export, then a subsequent period adjustment affects a closed period, your original export is stale.

Common closed-period adjustment scenarios:

Audit adjustments posted after year-end close
Property tax true-ups posted to the prior year after tax bills arrive
Insurance adjustments when actual premium differs from the estimate
Utility reconciliation adjustments for the prior year

How to identify this problem: Compare the export date to the last-modified date on your financial statements. If statements were updated after the export was pulled, the export is likely missing adjustments.

How to fix it: Always pull your final GL export after the close is complete and all adjustments have been posted. If you need to run preliminary reconciliations before close, document that the export is preliminary and re-run after final close.

Systematic Validation Before Reconciliation

Before beginning CAM reconciliation, perform this five-point export validation:

Confirm export date range matches reconciliation period (transaction date, not posting date)
Confirm export basis is accrual
Confirm all operating accounts are included in the export filter
Pull the export only after final close, not before
For entity-level exports, document intercompany items as reconciling items

CapVeri's recovery gap analyzer runs this validation automatically when you upload your GL export — flagging date range issues, missing account ranges, and basis mismatches before they propagate into tenant reconciliation statements.