Check that your data is flowing

What you get

A quick health check before you act on the data. The goal is to confirm that the source is connected, the expected records have arrived and anything missing is understood.

The quick check

1. Integrations — confirm the connection is active and review Sync History or Activities where the integration provides them.
2. For accounting connections with multiple organisations, check the Manage view and resolve organisations that are still unmapped.
3. Spend Overview — compare the latest imported transactions with what you expect from the accounting source.
4. Organization → Users — if you connected an identity provider, sense-check the users and app relationships that arrived.

Remember that sync behaviour differs by connector. Google Workspace and Microsoft Entra ID synchronise automatically after connection, while Okta uses Sync Now.

If something stopped syncing

A connection can need attention after permissions or credentials change at the source.

1. Go to Integrations and open the affected connection.
2. Review its status and sync history.
3. Re-authorise or refresh the connection using that provider's setup flow.
4. Re-sync where the connector offers a manual sync action.

For Google Workspace and Microsoft Entra ID, missing or outdated administrator consent can stop sync. For Okta, check the API Services credentials and remember that the sync is manual.

The check that saves you an awkward conversation

A connection that was down leaves a dip — a month of unusually low spend. Re-sync before you read anything into it.

Spend suddenly fell? Check your connection history before you tell anyone you saved money.

What you've unlocked

You now know whether an unexpected number is a real signal, a mapping issue or a connection problem worth fixing first.