Get enough transaction history for statements

If you build statements, credit assessments, or affordability checks, you typically need a fixed window of history — 90 or 180 days is common. This article explains how much history you can expect and what to check when you receive less.

How much history is available

Two things determine the depth of transaction history for a consent:

1. Your consent configuration. The Data History setting in the Fiskil Console controls how much history is requested as part of consent authorisation. If it's set shorter than the window your product needs, you won't receive enough — regardless of what the institution holds.
2. The institution. In Australia (CDR), data holders must make at least 24 months of transaction history available, and some provide considerably more (up to 7 years). An account younger than your requested window can only ever return history back to its opening date.

History arrives in stages

On a new consent, the initial sync prioritises recent data — deep history can land shortly after the first basic data is available, especially for institutions that respond slowly or for consents covering many accounts. Wait for the sync-completed webhooks before generating a statement, rather than pulling data the moment the consent is created. See Data freshness and refresh timing.

When history looks short

1. Check the Data History setting in the Console for the consent configuration you're using.
2. Confirm the sync has completed — check for the banking.transactions.basic.sync.completed webhook, or the meta.updated_at timestamps on the transactions response.
3. Check your query: a from filter, status=POSTED filter, or unfollowed pagination cursor can all make history look shorter than it is. See Date ranges and pagination.
4. Consider the account's age — an account opened 60 days ago cannot return 180 days of history.
5. Re-query after a short wait. If deep history was still syncing, it may simply not have landed yet.