# Late-Arriving Business Data: Revise a Report Without Erasing Its Earlier Version

<a id="main-content"></a>

Operations &amp; Systems

October 28, 2026  ·  7 min read  ·  Victor Valentine Romo

On this page

1. [Freeze the Original Reporting Contract](<#freeze-the-original-reporting-contract>)
2. [Establish Why a Record Is Late](<#establish-why-a-record-is-late>)
3. [Separate New Observations, Corrections, and Duplicates](<#separate-new-observations-corrections-and-duplicates>)
4. [Reconcile a Fictional Four-Service Report](<#reconcile-a-fictional-four-service-report>)
5. [Build the Difference Before Replacing the Number](<#build-the-difference-before-replacing-the-number>)
6. [Treat a Watermark as a Technical Completeness Estimate](<#treat-a-watermark-as-a-technical-completeness-estimate>)
7. [Copy a Revision Log Readers Can Follow](<#copy-a-revision-log-readers-can-follow>)
8. [Notify the People Whose Decisions Used the Earlier Version](<#notify-the-people-whose-decisions-used-the-earlier-version>)
9. [Sources](<#sources>)

The monthly report goes out. Two valid completion records arrive after its cutoff. Someone replaces the total in the shared [workbook](</articles/excel-date-systems-business-handoffs/>).

The new number has lost the explanation for the old one.

Preserve the issued report before preparing a revision. Show which records changed membership, why they changed, and who accepted the replacement. Give readers enough evidence to follow the difference.

The method below is an editorial proposal for [operational reporting](</articles/reporting-automation-b2b-services/>). Every service record, role, and date is fictional. It does not define accounting restatement requirements or a platform configuration.

<a id="freeze-the-original-reporting-contract"></a>

## Freeze the Original Reporting Contract

Start with the report that readers received. Retain its value, definition version, input snapshot, and issue [timestamp](</articles/event-time-processing-time-business-reports/>). A current dashboard view cannot substitute for the earlier artifact.

Write four time definitions beside that artifact. They answer different questions.

| Time definition | Meaning in this method | Original synthetic report |
| --- | --- | --- |
| Reporting period | Interval that occurrence time must enter | 2026.09.01 00:00 through, but excluding, 2026.10.01 00:00 UTC |
| Availability cutoff | Latest permitted receipt boundary | Receipts before 2026.10.01 09:00 UTC |
| Extraction timestamp | When the retained input snapshot was extracted | 2026.10.01 09:05 UTC |
| Issue timestamp | When readers received this version | 2026.10.01 10:00 UTC |

The fictional report [counts distinct completed services](</articles/throughput-busy-time-service-team-reports/>). One service contributes one count. Its occurrence time selects the month. Its receipt time determines availability at the cutoff.

The extraction runs after the cutoff, but its selection still excludes later receipts. Record that rule explicitly. Extraction time alone does not describe the available population.

Keep the definition in a [business metric dictionary](</articles/business-metric-dictionary-template/>). A revision must identify whether the definition stayed fixed or changed. This example keeps the counting rule fixed.

<a id="establish-why-a-record-is-late"></a>

## Establish Why a Record Is Late

For this report, a late observation has a September completion time and a receipt at or after the original availability cutoff. Preserve both timestamps.

An October receipt is not enough to establish lateness here. A receipt at 2026.10.01 08:00 UTC would meet the original cutoff. Compare exact boundaries before assigning a reason.

Retain evidence that the original snapshot lacked the record. Compare stable service identifiers against the preserved input. A changed displayed total does not prove when any particular observation arrived.

Also retain the receiving boundary. The example uses reporting-intake receipt. An [upstream](</articles/data-lineage-small-business-reports/>) application's creation timestamp would describe a different point in the route.

If the original intake timestamp is unavailable, record that limitation. A record's first appearance in a later extract establishes availability in that extract. It does not establish the exact arrival instant.

[Keep missing evidence visible](</articles/null-blank-zero-business-data/>). Label a candidate's arrival time unknown until the reviewer can support it. Do not manufacture a precise cutoff comparison from a filename or a person's recollection.

<a id="separate-new-observations-corrections-and-duplicates"></a>

## Separate New Observations, Corrections, and Duplicates

Use one classification per proposed change before calculating the revised total.

A new observation introduces a service the original input did not contain. A correction changes evidence about a service already represented. A duplicate represents the same counted event again.

Those definitions belong to this review method. Match identity using the report's counting unit and supporting source evidence. Similar text alone does not prove two rows describe one service.

A correction can add, remove, or leave a contribution unchanged. Correcting a description need not change the total. Moving a completion timestamp outside the reporting period changes membership under this example's rule.

[A duplicate candidate](</articles/crm-data-quality-automation/>) remains a candidate until reviewed. Preserve both record identifiers and the evidence linking them. Do not count the candidate as an additional service merely because its row is newly received.

If one incoming record both corrects an existing service and resembles another row, resolve identity first. Then record the contribution once. Avoid assigning the same change to multiple bridge lines.

Keep a disputed candidate outside the accepted revision. Record its possible effect separately. The reviewer should know which unresolved fact could still change the total.

<a id="reconcile-a-fictional-four-service-report"></a>

## Reconcile a Fictional Four-Service Report

Version one reports four September completions. Its retained input includes S301, S302, S303, and S304. Each service arrived before the original cutoff.

The original source evidence places all four completions in September. The later review receives two new observations, a correction, and one duplicate candidate.

| Record under review | Occurrence evidence | Receipt or correction receipt, UTC | Classification and proposed effect |
| --- | --- | --- | --- |
| S301 | 2026.09.28 10:00 UTC | Before original cutoff | Original service; retain 1 |
| S302 | 2026.09.29 11:00 UTC | Before original cutoff | Original service; retain 1 |
| S303 | Originally 2026.09.30 23:40 UTC; corrected to 2026.10.01 00:10 UTC | 2026.10.02 08:00 | Correction; remove 1 from September |
| S304 | 2026.09.30 16:00 UTC | Before original cutoff | Original service; retain 1 |
| S305 | 2026.09.30 17:00 UTC | 2026.10.01 13:00 | New late observation; add 1 |
| S306 | 2026.09.30 18:00 UTC | 2026.10.02 07:00 | New late observation; add 1 |
| D304 | Same completion event as S304, confirmed during review | 2026.10.02 08:30 | Duplicate candidate resolved as duplicate; add 0 |

The source correction for S303 explicitly replaces an incorrectly entered completion time. That is a supplied fictional fact. The reviewer does not infer it from the two timestamps alone.

D304 carries the same source completion-event reference as S304. The fictional source owner confirms one service event. Retain D304 as duplicate evidence without treating it as a seventh service.

S305 and S306 both occurred in September. Both receipts fall after 2026.10.01 09:00 UTC. Neither service appears in version one's snapshot. Together, those facts support their late-observation classification.

For version two, use receipts before 2026.10.02 12:00 UTC. Extract the new snapshot at 12:05 UTC. Every reviewed change is available before that revised cutoff.

<a id="build-the-difference-before-replacing-the-number"></a>

## Build the Difference Before Replacing the Number

Prepare [a bridge with disjoint adjustment sets](</articles/rounding-reconciliation-business-reports/>). State each record's membership decision beside its contribution.

| Bridge step | Adjustment | Running September total | Evidence |
| --- | --- | --- | --- |
| Issued version one | Starting value | 4 | S301, S302, S303, S304 |
| Accept two late observations | +2 | 6 | S305 and S306 |
| Apply completion-time correction | -1 | 5 | S303 moves outside September |
| Resolve duplicate candidate | 0 | 5 | D304 represents S304 again |
| Proposed version two | Net change +1 | 5 | S301, S302, S304, S305, S306 |

The calculation is four plus two minus one plus zero, which equals five. The proposed September membership contains five distinct service identifiers.

Three original contributions remain. Two new contributions enter. One original contribution leaves. The duplicate contributes nothing additional.

Keep the two late observations visible even though the net change is one. A reader looking only at the net change would miss the timestamp correction.

Do not describe the revision as improved service performance. The changed number reflects newly available evidence and corrected period membership. No extra service happened because the report changed.

Use the same record-level discipline when [reconciling conflicting dashboards](</articles/reconcile-conflicting-business-dashboards/>). Resolve row inclusion before accepting a displayed total.

<a id="treat-a-watermark-as-a-technical-completeness-estimate"></a>

## Treat a Watermark as a Technical Completeness Estimate

[Apache Beam's programming guide](<https://beam.apache.org/documentation/programming-guide/#watermarks-and-late-data>) uses watermarks to represent expected input [completeness](</articles/data-quality-dimensions-business-reports/>). Elements for an earlier window can still arrive after its watermark passes. A watermark is not universal proof of finality.

[Allowed lateness](<https://beam.apache.org/documentation/programming-guide/#handling-late-data>) permits late-data handling within a configured windowing policy. Triggers govern result emission. These are pipeline choices, not authorization to overwrite an issued business report.

This summary follows the online guide checked on 2026.10.28. It specifies no SDK version, runner, trigger, or lateness setting. Verify the actual configuration before describing a deployed pipeline's behavior.

Keep a technical lateness policy separate from the report owner's revision policy. An accepted late element still needs the right business period, identity, and review evidence.

For the fictional report, the cutoff is a chosen operational boundary. It is not a Beam watermark. The example runs no stream processor and makes no claim about framework defaults.

<a id="copy-a-revision-log-readers-can-follow"></a>

## Copy a Revision Log Readers Can Follow

Give each issued version a stable identifier. Link it to its input snapshot and the preceding version. Keep the original artifact readable.

| Revision-log field | Entry to complete | Synthetic version-two entry |
| --- | --- | --- |
| Report version | Identifier and predecessor | September completions v2, proposed replacement for v1 |
| Definition version | Counting and timestamp rules | `completed_services_v1`, unchanged |
| Prior value | Previously issued value | 4 |
| New value | Proposed revised value | 5 |
| Record reasons | Separate additions, removals, corrections, duplicates | S305 and S306 added; S303 removed; D304 duplicate |
| Revised cutoff and extraction | Input availability and snapshot time | Cutoff 2026.10.02 12:00 UTC; extracted 12:05 UTC |
| Reviewer | Person accepting evidence and arithmetic | Fictional report reviewer |
| Recipients to notify | Readers and dependent report owners | Original distribution list and capacity-review owner |
| Remaining provisional fields | Unknowns and their possible effects | Upstream completeness unconfirmed; further arrivals could change count |
| Issue decision | Approved, held, or rejected, with time | Proposed until reviewer records acceptance |

The original version remains four. Version two becomes five only after the fictional reviewer accepts the evidence. Keep preparation and approval as separate states.

Use [spreadsheet version control](</articles/spreadsheet-version-control-business-decisions/>) when a workbook carries the report. Connect the revision log to the retained workbook state. A renamed tab alone does not describe the inclusion changes.

<a id="notify-the-people-whose-decisions-used-the-earlier-version"></a>

## Notify the People Whose Decisions Used the Earlier Version

Before issuing a revision, [identify dependent decisions](</articles/decision-journal-business-operators/>). A capacity review might have used version one. Another summary might have copied its total. Record those destinations without guessing whether the changed count affects their conclusions.

Prepare a short notice with the report identifier, previous value, revised value, and record reasons. Include the new cutoff and a link to the retained versions.

For this fictional review, the proposed notice says: “September completions v2 changes four to five. Two late services enter; one timestamp correction leaves September. A duplicate adds no service.”

Treat that wording as an example. The actual report owner decides the audience and whether a dependent decision needs review. Do not claim every recipient has accepted the revision because a notice was sent.

If more evidence arrives later, start the next proposed version from the latest accepted version. Preserve the earlier bridge. Keep unresolved completeness visible rather than calling the latest extract permanently final.

Retain the earlier number and explain the new one.

<a id="sources"></a>

## Sources

- [Apache Beam: Programming Guide, watermarks and late data](<https://beam.apache.org/documentation/programming-guide/#watermarks-and-late-data>). Watermark completeness estimates and late elements. Online guide checked 2026.10.28.
- [Apache Beam: Programming Guide, handling late data](<https://beam.apache.org/documentation/programming-guide/#handling-late-data>). Allowed lateness and trigger context. Online guide checked 2026.10.28. No pipeline configuration was tested.
