Practical guide

A safer workflow for Yardi Breeze report exports and Excel

Exporting a report is easy. Keeping its meaning intact while filtering, cleaning, joining, and summarizing it is where month-end spreadsheets become fragile. This workflow keeps a trail from source rows to final artifact.

Choose the report for the question

Start by writing down the artifact you need and the fields it requires. Owner statements generally need detailed dates, property codes, account information, descriptions, and amounts. Bank reconciliation needs book transaction activity that can be compared with bank rows. A summary report may look convenient but omit the detail needed to explain a variance or match a deposit.

Set scope before export

Confirm the property selection, account range, and date window in Yardi Breeze®. If you need year-to-date totals and prior-month comparisons, export enough history to support them. Record the chosen filters in a small control sheet or filename. Avoid relying on memory after several similar files have accumulated in Downloads.

Preserve an untouched source copy

Save the downloaded file immediately with a predictable name containing report type, period, and export date. Never clean the only copy. Duplicate it for working use. An untouched file is the evidence that lets you distinguish a source-system value from a formula, manual correction, or formatting change introduced later.

Inspect the shape before formatting

Look for report titles above the header, merged cells, repeated header rows, subtotals, blank lines, and notes below the table. Check whether each row is a transaction, a summary, or a visual separator. Excel’s filters and tables are powerful only after the data is a consistent rectangle. Remove presentation-only rows from the working copy while documenting what you removed.

Standardize headers explicitly

Trim spaces and normalize obvious punctuation, but maintain a mapping from original headings to your working names. Do not silently guess when a required field is missing or renamed. Put unknown headers into a review list. A robust workflow stops and asks for the header row rather than calculating with the wrong property or amount column.

Normalize dates and amounts

Dates may arrive as Excel serials, US-formatted text, or ISO strings. Convert them to one real date type and verify several examples, especially ambiguous values such as 03/04/26. Amounts may contain currency signs, commas, parentheses, separate debits and credits, or text. Convert on a new column and compare totals before replacing anything. Decide and document a single sign convention.

Keep identifiers as text

Property, unit, account, check, and reference codes may have leading zeros or characters that look numeric. Import these as text. Automatic numeric conversion can turn a stable code into a different value, break a join, or display long references in scientific notation. Codes identify; amounts calculate.

Use tables and controlled joins

Convert the clean range to an Excel Table so formulas and filters expand predictably. Keep owner-to-property mapping in a separate controlled table. Use XLOOKUP or Power Query to add the owner, then count unmapped property codes. Never filter unmapped rows away. Give them a visible “UNASSIGNED” status and resolve them before final output.

Build control totals

At minimum, record source row count, clean row count, source amount total, clean amount total, and number of unmapped rows. When debit and credit columns exist, total them separately before deriving a signed amount. Add controls for the selected period and property list. These checks turn invisible spreadsheet damage into a visible exception.

Separate data, calculation, and presentation

Use distinct sheets or queries for raw source, cleaned rows, mappings, calculations, controls, and the final presentation. Avoid manually typing totals into the report sheet. A number should trace through a formula or query to the clean table and then to an original row. Keep branding and layout changes away from source data.

Watch for common failure modes

Typical problems include subtotals counted as transactions, filtered rows omitted from a copy, formulas not extended to new rows, dates stored as text, signs reversed, duplicate imports, mapping joins that multiply rows, and old opening balances carried forward without approval. Put checks for these into the workbook rather than depending on visual inspection alone.

Protect sensitive exports

Store working files in an approved location, restrict access, and delete temporary copies according to policy. Do not email unencrypted ledgers casually or upload them to unknown converters. A tool that works with exports should explain retention clearly and should never require a Yardi login to fetch a report the authorized user can download themselves.

Finish with a reproducible review

Refresh calculations, recheck controls, spot-check rows against the untouched export, lock the period, and record who reviewed the result. If a header changes next month, update the mapping and re-run controls rather than patching totals. Repeatability is the difference between a one-off spreadsheet and a dependable close process.