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.

What completeness means

Completeness answers one question: do the accounts you've given us show the customer's whole financial picture, or is some of their banking missing? A customer who banks across several accounts but connects only one will look very different on paper from how they actually operate. Completeness flags that before you rely on the numbers.

It is not a measure of data quality in the sense of errors or formatting, and it says nothing about creditworthiness. A customer can have a high completeness score and a poor risk profile, or the reverse. It tells you how far to trust the other reports, not what they say.

How it's assessed

Walker Street Data looks at the customer's enriched transactions from the last 180 days, across all the accounts you've provided, and compares their shape against what a complete set of business banking typically looks like. Signs that something is missing include:

• An unusual income mix - for example, sales making up almost all of the credits, or hardly any, which suggests another account receives income
• Missing commitments - few or no loan, lease or credit facility repayments, which usually means they're paid from an account you haven't provided
• Missing costs - operating expenses that look too low (or too high) relative to everything else
• Low activity - fewer transactions per day than an active business account would show
• Heavy external transfers - a large share of money moving to or from accounts outside the data you've provided
• Short history - less than about six months of transactions

Each of these is a feature in rankedFeatures, compared against a benchmark. The features that deviate most from their benchmark contribute most to the missing-data estimate, and each one produces a plain-language recommendedActions entry telling you what to ask the customer for.

Reading the score

completenessScore is on a 0 to 100 scale and is the estimated share of the customer's financial picture the data captures. totalMissingness is its complement (the two add up to 100). The score is banded into completenessTier:

Tier	Score	What it suggests
high	Above 85	The data likely reflects the customer's full banking
medium	Above 40 to 85	Some activity is probably missing; check the recommended actions
low	40 or below	Significant banking is likely missing; request more data before use

Fewer than 75 transactions

Completeness needs at least 75 transactions in the 180-day window to produce a score. Below that it returns a placeholder (completenessScore of 1, tier low) and dataQualityAssessment.coverage explains that the score could not be calculated. Treat this as "not assessed", not as a genuine score of 1.

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	Estimated share of the customer's financial picture the data captures, from 0 to 100
completenessTier	Band indicating the level of overall data completeness: high, medium, or low. Empty when no tier could be calculated
totalMissingness	Estimated share of the customer's financial picture that is missing, from 0 to 100 (100 minus completenessScore)

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