Connections

Banks, accounting, payroll, commerce and spend, connected once and kept authorised.

Connections in SigmaPointPi
/connect

Every connection is read-only unless it is explicitly a payment rail. A bank connection can see balances and transactions and cannot move money.

Connections expire. Institutions rotate credentials and require periodic re-authorisation, and a connection that has lapsed says so on itself rather than quietly serving stale data.

Where everything sits

Stripe
Stripe
Connected
Connected
Available
Available
Categories
Categories
Health Score
Health Score
Integration Hub
Integration Hub

How to work this page

Authorise on the provider's own screen

Credentials go to the institution, never to us. What comes back is a scoped token.

Check what each connection pulls

Every connector lists exactly what it reads. Nothing is pulled that is not listed.

Watch for re-authorisation

A lapsed connection is shown as lapsed on the connection and on any figure that depends on it, so a stale balance is never presented as current.

Disconnect cleanly

Disconnecting revokes the token and keeps the history already imported. Removing a connection does not delete your books.

On a phone

Connections on iPhone 15 Pro Max

Every figure from the desktop appears here, stacked rather than reduced. Tables scroll inside themselves so the page never moves sideways, and figures keep their separators and their alignment at every width.

Questions people actually ask

What if my bank is not listed?

Statement import through Workbooks handles any institution. Columns are matched by meaning, so a statement in an unusual format still lands correctly.

Who can see the connection?

It belongs to one business. Another business under the same account has no path to it, enforced in the database rather than in application code.