Cookie settings
Portfolio Review Journal

RECORDS / CONTEXT / REVIEW · U.S. English

Report context

The five details every report comparison needs

Check scope, period, basis, filters and version before comparing Buildium reports or explaining a number to a property owner.

Editorial analysis. This publication cannot access accounts or provide property management or official product support. Official-source links lead away from this site.

In this article

Two reports can disagree without either being wrong. Before investigating the numbers, establish whether both reports were designed to describe the same thing.

A comparison begins with a small context card. Keep it beside the source files or in the approved review record. The card does not alter the reports; it records the assumptions under which someone is comparing them.

1. Which entities are included?

Write down the property or portfolio selection exactly enough to reproduce it. A familiar folder name is not evidence of the selected scope. A report for one building and a report for an owner’s entire portfolio should not be treated as matching totals merely because that owner is associated with both.

Also distinguish the management business from the properties it manages. Buildium’s Company Financials page describes reporting for the management company as well as managed properties. A business expense and a property expense may belong to different questions. Ask the preparer which entity the report describes before attributing a difference to missing transactions.

2. Is the date a period or a point in time?

Read the report heading and parameter summary. A report describing activity across a range is not the same object as a snapshot at a particular date. Preserve the actual start and end dates; do not shorten a custom period to “October” if it begins or ends midmonth.

If two reviewers are in different offices, agree on the intended cutoff and where it is documented. Do not invent a universal midnight rule for every report. The relevant setting and organization’s process should answer that question. An export timestamp tells you when the file was created, not necessarily the last transaction date included.

3. What accounting basis or status filter was used?

When a report exposes a basis or status setting, record it. If the setting is not visible, ask rather than assuming. A paid-only listing and a list including outstanding items answer different questions. The review note should name the filter in ordinary language, without trying to redefine accounting rules.

Fictional comparison

A maintenance summary includes an invoice received in October. A separate cash-oriented report does not show the payment because it occurred later. The first task is to confirm the report settings and transaction trail. The missing line alone does not prove a lost invoice or an incorrect payment.

4. Which columns and grouping matter?

Keep the column headings with an exported number. A screenshot of a total without the heading or filter area may be impossible to interpret. If a report groups several properties or categories, confirm whether the subtotal being quoted is the intended comparison point.

Use a controlled copy for annotations. Do not overwrite source cells merely to make the totals agree. A change to an exported spreadsheet is not a correction to the underlying record. If a source needs correction, refer it to the authorized record owner and preserve the reason for the change.

5. Which version is the shared reference?

Give files a readable version label and preserve the original downloaded copy. If a later report replaces an earlier one, note what changed and whether the earlier conclusions still apply. Repeatedly attaching a file called “final” makes the review harder, especially when new information arrives.

A compact comparison note might read: “Same two properties, same period, settings confirmed, export generated after the correction; prior packet replaced.” If those facts are not known, list them as questions. Continue with owner-statement questions when the remaining issue concerns a particular statement, or use an exception entry to track an unresolved scope mismatch.

Sources and scope

Public sources checked October 21, 2026. The review method and fictional examples are original editorial guidance, not Buildium instructions or accounting, legal or tax advice. No private account was inspected.

  1. Buildium: Company Financials

    The product offers distinct financial reports, including balance sheets, income statements and transaction reports. Access: direct public page.

Have a public source that changes this analysis? Suggest a correction. Please don’t send private resident, owner or financial records, identity documents or account credentials.