Document an owner-statement correction after publication

When an owner statement needs correction after publication, preserve the exact version the owner received and build a bridge to the corrected records. The bridge should identify what changed, why it changed, who approved the correction, how the statement total changed, and whether a distribution or other settlement amount is still open.

Do not replace the issued file with a revised file that uses the same name and date. The original statement, correction evidence, and revised output answer different questions.

Give each statement version a stable identity

Record the owner, included properties, statement period, accounting basis, report filters, original publication date, and packet or report ID. Save the issued file before changing the source records.

AppFolio’s owner portal help explains that owners can view or download published statement packets.¹ If a portal or another delivery method is used, record which packet was published and when. Portal availability does not prove the underlying bookkeeping is correct.

Build a five-part correction bridge

Use one correction ID and connect these records:

1. Issued statement. Identify the original file, publication date, and reported net amount.
2. Correction source. Retain the invoice, receipt, bank item, system record, or other evidence that established the error.
3. Bookkeeping change. Record the affected property, transaction reference, old value, corrected value, approval, and posting date.
4. Revised statement. Generate a new version or clearly labeled later-period adjustment under the firm’s approved process.
5. Settlement effect. Compare what was previously distributed or collected with the corrected amount and keep any difference open until supported.

The responsible property manager and accountant decide how the correction appears in the records and owner reporting. State requirements and management agreements may also apply. This workflow documents the evidence; it does not interpret those requirements.

Worked example: one duplicated repair

Illustrative example. A published statement for Property P-204 reports $8,400 of receipts, $3,180 of expenses, and a $5,220 net amount. The team later confirms that a $480 plumbing invoice was entered twice under two different references.

The bookkeeping change should reference the original transaction and the duplicate record. The revised statement should show its own version and publication date. The $480 difference remains open until the firm’s approved process and supporting payment evidence establish its resolution; the bookkeeper should not infer that outcome from the corrected report alone.

Check both systems when QuickBooks is also used

If property software produces the owner statement while QuickBooks holds a related summary or management-company record, inspect the agreed system-role map before making a second correction. The error may affect only the property records, or it may also affect a summarized entry, transfer, or clearing balance in QuickBooks.

Record the source-system ID and the related QuickBooks reference where one exists. Do not copy the full correction into both systems merely to make their screens look alike. Reconcile the approved accounting effect under the documented design.

Close the correction only when the trail is reproducible

Before closing the item, confirm that:

• the issued and revised statement files both remain available;
• the source evidence supports the reason and amount;
• the affected property and owner are identified;
• the bookkeeping references show the approved change;
• the settlement difference is resolved or remains visibly open; and
• the next reviewer can reproduce the corrected total.

The IRS lists invoices, paid bills, receipts, deposit slips, and payment records as supporting business documents.² Keep the relevant source records with the correction bridge instead of retaining only a narrative note.

Use the system-role guide to decide which records need correction in each system. Carry any unresolved amount into the reconciliation exception log with an owner and review date.