Skip to content

CSV Import: Deduplication / idempotency strategy #23

Description

@azunaVT

Epic: Import

Description

Prevent duplicate transactions when the same CSV file is imported multiple times.

Acceptance Criteria

  • Define a deterministic transaction fingerprint strategy
    • Example: hash of occurred_on + amount_cents + description
  • Enforce uniqueness per household
  • Re-importing the same CSV does not duplicate transactions
  • Covered by tests

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions