When an invoice is edited after the dated QuickBooks export used for a collections forecast, keep the original snapshot intact and process the edit as a new evidence event. Do not silently replace the old amount, due date, customer, or status inside the prior forecast.
Why the edit matters
A four-week forecast is only reviewable when its inputs have an effective date. An invoice edit can change the balance that remains open, the date used for aging, the customer assignment, or the evidence behind an expected collection week. Even when the edit is correct, overwriting the earlier row makes it difficult to explain why a forecast changed.
QuickBooks provides an audit history for transaction activity. Use that history and a fresh invoice-level report to establish what changed and when. The weekly AR snapshot change log provides the companion structure for comparing dated exports.
Build an invoice change bridge
Record the invoice identifier, prior export date, changed-at date, person or system associated with the change, affected fields, prior values, current values, and supporting note. Classify the change before updating cash timing:
- A balance change requires a bridge from the prior open amount to the current open amount.
- A due-date or terms change requires evidence that the revised date is the operative customer-facing date.
- A customer or invoice-number change requires identity reconciliation so two rows do not become two expected receipts.
- A status change requires a fresh check of payment, credit, void, or deletion evidence.
The QuickBooks AR aging report-date checklist helps keep the source cutoff explicit.
Update the forecast without rewriting history
Lock the prior forecast as the baseline. Add the edit as a dated variance, then update only the current forecast version. If the change reduces the open balance, remove only the unsupported expected cash. If it changes timing but not balance, preserve the original amount and update the collection week with a reason and next review date.
If the edited invoice no longer appears in the same report population, reconcile it through the Open Invoices versus AR Aging Detail guide before assigning an action.
Minimum review fields
The review record should include snapshot date, transaction ID, invoice number, customer, prior and current balance, prior and current due date, change type, evidence link, owner, forecast effect, and review date. A material or unclear edit should remain an exception rather than receiving a precise new payment assumption.
Decision rule
Treat an edited invoice as a versioned source event. Preserve the old snapshot, reconcile the new row, and make the forecast change explainable. Finance teams can view the AR Pulse example to see the intended invoice-level evidence boundary.