Transaction History

JE-PFM maintains a complete, append-only ledger of every transaction you import. This section explains how transaction history works and what you can expect as your data grows.

Append-Only Storage

Transactions in JE-PFM are never modified or deleted once imported. This follows standard accounting practice — the historical record stays intact. If a transaction needs correction (for example, a miscategorized expense), you change the category assignment rather than editing the underlying transaction data.

This design ensures that your records always match what your bank reported and provides a reliable audit trail.

Deduplication

Every transaction imported from an OFX/QFX file carries a FITID (Financial Institution Transaction ID) assigned by your bank. JE-PFM enforces a uniqueness constraint on the combination of account and FITID. If you import the same file twice or import overlapping date ranges, duplicates are automatically detected and skipped.

Date Handling

Transactions are stored with the date your bank recorded them (the posted date). Some banks also provide a separate transaction date (the date the purchase actually occurred). When both are available, JE-PFM stores both and uses the posted date for sorting and filtering by default.

Growing Your History

There is no limit on the number of transactions you can store. As your history grows, JE-PFM continues to provide fast search and filtering thanks to database indexes on date, account, category, and payee fields.

For the best experience:

• Import regularly so your records stay current.
• Use consistent date ranges to avoid gaps in your history.
• Start with the widest date range your bank allows on your first import to build a solid baseline.

Accessing Older Data

All transactions remain accessible regardless of age. Use the date range filter on the Transactions page to view any historical period. Reports and budget tracking can reference any date range in your history.