Product documentation
Connect financial accounts and import bank activity
How Aiviance keeps account ownership, provider consent and reviewed financial records separate.
Open
A connection brings financial activity into Aiviance. It does not change who owns an account, and it does not turn every imported row into a confirmed accounting record.
Keep ownership explicit
Each financial account belongs to an entity. A person may start the connection, but the account remains attached to the person, family structure or business that legally owns it. This boundary keeps consolidated views useful without mixing ownership.
Connect a supported source or import a statement
Where a supported provider is available, Aiviance uses that provider's consent flow to connect account data. Provider availability depends on the account's banking region and the services enabled for that region.
Aiviance also supports importing compatible CSV or text statement exports into an existing account. The import shows readable and skipped rows for review before processing. It does not collect an online-banking password.
Imported activity remains reviewable
Connected and file-imported activity enters the same reconciliation boundary. Aiviance can suggest matches with existing records and identify exceptions, but a suggestion is not a silent posting decision. Users review matches, create missing records where needed and retain a route back to the source evidence.
What this public page does not replace
Exact screens, permissions, supported formats and region-specific availability can change as the product evolves. Signed-in users should use the Aiviance Guide for the workflow available to their active entity.
For the broader handling boundary, read How data moves through Aiviance and AI and Access controls. Formal privacy and consent commitments are defined in the Legal Center.