# Import review, duplicates and corrections (/docs/imports/review-and-corrections)

## Preview before committing [#preview-before-committing]

Check company, perimeter, coverage and mapping version. Inspect statements and reconciliation, not just the upload success message. Drill into contributing accounts when a total is surprising.

**Checks passed** means implemented checks passed, not that finance approved every source and definition.

## Duplicate packages [#duplicate-packages]

An exact duplicate package using the same mapping is blocked. Review the existing receipt and financial history. Do not rename files to bypass the check.

## Correcting historical values [#correcting-historical-values]

Changed historical values can create new revisions while retaining earlier values. Unchanged reported values are kept. Inspect proposed revisions before **Import actuals**, then review **Sources & history**.

Monthly and YTD coverage can conflict. Portcora blocks unresolved overlap rather than silently changing interpretation. Do not split a SuSa total into invented monthly figures.

## Mapping versions are separate [#mapping-versions-are-separate]

New mapping affects future imports. Old receipts keep their original version. Ask the finance reviewer how to correct an earlier import's exact scope; saving new mapping alone is not a retroactive correction.

## When to stop and ask [#when-to-stop-and-ask]

Stop for the wrong company or perimeter, unexplained opening-balance checks, incomplete coverage or unresolved source mismatches. [Prepare a support request](/docs/support) with the exact context and error, without publicly sharing the financial file.