Imports and Exports Documentation
Prepare, validate, import, reconcile, and safely share household data files.
Audience: Admins and members migrating, backing up, or analyzing permitted data. · 5-page PDF · v6.26.1
How to read this document
Sections move from purpose → concepts → calculation process → worked examples → edge cases. Formula boxes use plain mathematical notation for clarity; they are conceptual summaries, not API contracts.
- Point lists call out operator-visible behaviour.
- Callouts mark warnings, limitations, or important qualifications.
- Worked examples use round numbers so you can reproduce the arithmetic by hand.
Purpose
File workflows move structured data into or out of an authorized AccountHouse scope.
- Validate before import
- Prevent duplicates
- Reconcile results
- Protect exported copies
Prepare source data
- Use supported file format and encoding.
- Normalize dates and decimal separators.
- Label currency explicitly.
- Map categories intentionally.
- Remove secrets and irrelevant columns.
Preview and validation
Validation identifies malformed or unsupported rows; it cannot determine every semantic mistake.
Importable rows
Parsed rows − rejected rows − intentionally skipped rows
Duplicates and idempotency
Preview does not guarantee uniqueness
The same transaction may arrive through multiple files or manual entry. Use stable identifiers where supported and reconcile date, amount, currency, and context.
Commit and reconcile
Import expenses
- Back up the source file.
- Map required fields.
- Preview validation.
- Import the accepted scope.
- Compare counts and totals.
- Inspect duplicates and conversion.
The imported ledger is checked against its source.
Exports
Exports reflect current filters, permissions, data, and generation time. They may not include inaccessible fields or immutable historical states.
File security
- Store exports securely.
- Encrypt when sharing.
- Verify recipients.
- Delete temporary copies.
- Do not commit data files or secrets to source control.
Limits and recovery
Large files, unsupported fields, malformed rows, or rate limits can affect processing. Keep originals and use smaller validated batches when appropriate.
Privacy, advice limits, and what we do not publish
AccountHouse is a household tracking and organisation tool. It is not a bank, payment processor, tax advisor, or investment advisor. Forecasts, health scores, balances, and alerts are informational.
- Household data is scoped to your household; other families cannot see your ledger.
- Public documentation explains product behaviour and calculation concepts, not proprietary internals.
- Exact scoring weights, anomaly thresholds, cryptography parameters beyond high-level algorithms, and operational detection rules are reserved.
- Exports leave AccountHouse access controls and become the recipient's responsibility.
Intellectual property boundary
This document describes what AccountHouse calculates and which inputs matter. It does not disclose source algorithms, secret constants, or implementation details sufficient to reconstruct proprietary systems.