Build a weekly cost snapshot for an active flip

A flip can be moving on schedule while its bookkeeping falls a week or two behind. The investor sees crews, deliveries and draws in real time, but the property report may contain only what has reached the bank or accounting file.

A weekly cost snapshot closes that information gap without pretending every open item is already an accounting entry. It brings the current property facts into four lanes: acquisition, rehab, holding and exit preparation. Each amount carries a source, status and next action.

Start with one property and one cutoff

Use a stable property ID rather than a shortened street name. At the top of the snapshot, record:

• Property ID and legal ownership record.
• Week-ending date and time.
• Bank and card accounts reviewed.
• Project report name and filters.
• Last document received from the project lead.
• Person responsible for each unresolved item.

QuickBooks Projects can group income and costs by project, depending on the subscription and setup. Another approved structure can work, but the property identity and cutoff need to remain consistent.

Use four lanes with clear boundaries

The snapshot should answer four different operational questions.

Acquisition

List the closing statement, earnest-money trail, lender or capital funding records and acquisition-related invoices held in the project file. Do not decide the tax or accounting treatment in the snapshot. Record where each supported amount appears and route classification decisions to the responsible accountant.

Rehab

Show approved scope, invoices received, credits, cleared payments and open documentation by vendor. Keep approved but uninvoiced work separate from costs already supported by invoices. A proposal, invoice and payment can refer to the same work without being three separate costs.

Holding

Capture the property-linked period and source for recurring items such as utilities, insurance, financing statements and local services. The holding-cost schedule provides a detailed monthly control; the weekly snapshot carries only its current total and exceptions.

Exit preparation

Before a property is listed or sold, show open vendor items, expected credits and documents that the closing file will need. These are readiness facts, not a forecast of proceeds or profit.

Add a status to every amount

Use a small controlled list:

• Recorded and cleared: present in the project books and cleared in the financial account.
• Recorded, not cleared: present in the books but not yet cleared.
• Supported, not recorded: source document received but not yet represented in the project report.
• Expected, support missing: the team expects an item, but the required document has not arrived.
• Question: property, vendor, amount or approval is unresolved.

The IRS recordkeeping guidance says supporting documents should show the payee, amount, proof of payment, date and what was purchased or received. That is why a bank line alone is not enough evidence for the property snapshot.

Worked example: one active renovation

Illustrative example. Property FL-318 has this week-ending snapshot:

The $286,400 supported total is not presented as final project cost or taxable basis. It is the sum of items currently supported in this illustrative control. The $5,620 open amount consists of a $3,500 supported invoice and a $2,120 expected invoice. Those two items require different next actions.

Apply an evidence-freshness test

For each lane, note the newest source date. A current bank feed does not make the snapshot current if the latest contractor invoice is two weeks old. Likewise, a fresh scope update does not prove the card transactions were reviewed.

Mark a lane stale when its required source has not arrived by the agreed weekly cutoff. Record the missing document, responsible person and next review date. Avoid replacing the last verified amount with an estimate merely to make the table look complete.

Intuit’s project profitability reporting guidance explains how project reports summarize income, costs and profitability from recorded activity. The weekly snapshot should reconcile to that recorded population while keeping supported open items visibly outside it.

End the review with three actions

A useful weekly review produces a short queue:

1. Documents to collect.
2. Records to match or enter under the approved workflow.
3. Questions that require investor, project lead or accountant decisions.

The bank-feed project context guide explains how to restore property evidence to cleared transactions. The contractor-deposit guide shows how one payment remains connected to later invoices.

Project-aware bookkeeping gives a real estate flipper a defensible weekly view of what the records support, what the books contain and what still needs attention. That is more useful than a single bank balance and more honest than a report filled with unsupported estimates.