Imports guidance
Import historical purchase data
Preserve prior records as provenance-labelled evidence without creating live operational states.
- FOR
- Organisation administrator, Finance, Auditor
- OUTCOME
- Use RAQOZ to preserve prior records as provenance-labelled evidence without creating live operational states.
Before you begin
- A source file you are authorised to use.
- Stable identifiers and clean headers for the records being imported.
Guidance
- 1
Prepare historical identifiers, dates and source references needed for reconstruction.
- 2
Map and validate the file, including duplicate treatment.
- 3
Import history as evidence-only records with explicit provenance.
- 4
Never treat imported history as a live approval, receipt, payment state or current control decision.
Evidence RAQOZ retains
- Source and mapping
- Evidence-only provenance
- Import outcomes and validation errors
Common issues
Rows fail validation.
Correct required fields, formats or mappings in the source and validate again. Review duplicate treatment before any write.
Imported history appears incomplete.
Check mapping and row outcomes. Historical data remains provenance-labelled evidence and must not create live approvals, receipts or payment states.
Related articles
Last reviewed 2 September 2026. Review against the current production release before relying on exact screen behavior.