Completeness

Completeness evaluates whether available transaction data is sufficiently complete and reliable to support a lending decision. It provides a scored assessment of coverage, data quality, and recommended actions for borderline cases.

Retrieving this report

Completeness is returned as the completeness entry of the report bundle - one call returns it alongside Risk Score and Aggregate. Check the entry's status before reading its data; the fields below describe that data payload.

Interpreting results for credit

• A higher completenessScore supports greater confidence in decisioning
• Review largestGapDays and percentDaysMissing on each account - large or recent gaps may indicate suppressed or unavailable data
• Use recommendedActions to determine whether to request additional statements or escalate to manual review
• Apply a minimum completeness threshold as part of your credit policy before relying on the Aggregate or Risk Score reports in the same bundle

Response fields

Summary

The summary object gives the top-level completeness picture:

Field	Description
completenessScore	Numeric score representing overall data completeness
completenessTier	Band indicating the level of overall data completeness: high, medium, or low. Empty when no tier could be calculated
totalMissingness	Overall proportion of missing data across the customer's transaction history

Bank account coverage

The bankAccounts array reports coverage metrics per account:

Field	Description
bankAccountId	Unique identifier for the account
bsb	Bank State Branch number
bank	Institution name
accountNumber	Account number
accountPurpose	Identified purpose of the account
sourceOfAwareness	How Walker Street Data became aware of the account: provided (you submitted its data), inferred, or wsd
dataStatus	Status of the data for this account: complete, partial, or missing
coverage.startDate	Earliest transaction date in the available data
coverage.endDate	Latest transaction date in the available data
coverage.largestGapDays	Largest continuous gap in transaction history, in days
coverage.percentDaysMissing	Proportion of days between the start and end date with no transaction data

Additional assessment fields

Field	Description
rankedFeatures	Features ranked by their contribution to the completeness score, each with rank, featureName, benchmark comparison, and missingness contribution
dataQualityAssessment	An object with a single coverage field. When the transaction history is too short to assess reliably, coverage contains a note describing the shortfall; when coverage is sufficient it is null
recommendedActions	Prioritised actions to improve data coverage or address gaps, each with a description and priority

Next steps

• Reports - How to retrieve this report and read its status
• Aggregate - Review cashflow and behavioural summaries once data coverage is confirmed
• Risk Score - Proceed to predictive risk assessment after validating completeness
• API Reference - Full endpoint schema and parameter details