Analytics and Reports Documentation

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

Analytics turns ledger records into grouped views and reports. Every result should be read with its household, period, filters, currency, and inclusion rules.

• Explore spending and income
• Compare periods and categories
• Export scoped records
• Trace aggregates to source data

Insights Engine and IntelliVis

When Insights Engine is enabled for the household, Analytics also hosts suggestion cards. IntelliVis renders the charts and evidence that explain those cards. Standard trend charts and exports remain available whether or not Insights Engine is on.

• Open Analytics → Insights for the New and History feeds.
• Expand a card to read the narrative, IntelliVis chart, and evidence when present.
• Use dismiss, snooze, or guarded preview/confirm actions as appropriate.
• See the Insights Engine and IntelliVis documentation modules for full behaviour and limits.

Scope before numbers

• Household
• Date range or selected month
• Reporting currency
• Category, member, card, or status filters
• User permissions

Aggregation

Grouping changes presentation, not source values. Categories with no matching records can be absent or zero depending on the view.

Income and savings

This derived result is not a bank balance, cash-flow statement prepared under accounting standards, or net worth.

Budget analysis

• Inspect month overrides.
• Trace spend to matching expenses.
• Treat thresholds as presentation and alert states.
• Do not add overlapping budget scopes blindly.

Currency normalization

Reports use comparable reporting values while preserving original transaction context. Rate basis and rounding can affect totals.

Time grouping

Transaction dates assign rows to periods. Late entry, backdating, timezone correction, or editing can change prior-looking totals.

• Use consistent start and end boundaries.
• Distinguish calendar from rolling periods.
• Check local date near midnight.
• Record the filter state with exported analysis.

Trends and historical claims

A trend can summarize stored records or reconstruct values from current state. Labels should distinguish recorded historical observations from synthetic or recalculated series.

Changes and baselines

Large percentages can result from small baselines. Show absolute values with rates of change.

Reading charts

• Read axes and units.
• Check whether missing means zero or unavailable.
• Do not infer causation from correlation.
• Open underlying records.
• Beware rounded labels and hidden small categories.

Exports and reproducibility

An export reflects current data, filters, permissions, and generation time. Preserve those details when sharing or auditing it.

Corrections and mutable data

• Edited source rows update aggregates.
• Deleted records leave current reports unless audit history is separately exposed.
• Category changes restate category analysis.
• Rate or currency changes can restate comparable values.
• Permissions can change visible scope.

Data-quality checks

• Duplicate date and amount
• Missing or unusual categories
• Absent conversion
• Unexpected negative or zero values
• Outlier amounts
• Disabled income
• Open filters
• Incomplete imports

Troubleshooting workflow

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 can reveal sensitive household and peer data; protect downloaded copies.
• Analytics is informational and not audited accounting, tax reporting, or financial advice.