Skip to main content

Data Synchronization

Understand when to choose API synchronization and when SAF-T upload is the better path into Kogniflow.

Kogniflow supports two ways to bring accounting data into the platform: API synchronization and SAF-T file upload.

Both methods move data into Kogniflow.

API synchronization

Choose API when the organization should maintain a direct connection from the accounting provider into Kogniflow.

What API requires

  • The user must choose API as the synchronization method
  • The user must also choose a supported accounting provider
  • The provider connection must be completed for the organization being analyzed

When API is a good fit

  • The organization wants a direct synchronization path
  • The accounting provider is already supported
  • The team expects recurring updates into Kogniflow

SAF-T file upload

Choose SAF-T when the organization should upload a standardized export file instead of connecting through API.

What SAF-T requires

  • The user chooses SAF-T file upload as the synchronization method
  • No accounting provider selection is required inside Kogniflow
  • The uploaded file should represent the bookkeeping period you want Kogniflow to analyze

When SAF-T is a good fit

  • The accounting provider is not supported through API yet
  • The team prefers a file-based onboarding flow
  • Direct API access is not available

How to decide

Use API when the provider is supported and a direct connection is preferred.

Use SAF-T when you need an alternative intake path that does not depend on provider selection.