Banks: statements and API connections

Centa AI receives bank transactions in two ways: by uploading an Excel/CSV statement from any bank (available) or through a bank API connection (beta). Either way, transactions go through the same classification, posting and reconciliation with documents.

  • Status:Bank statements (Excel/CSV)Live
  • Status:Bank APIsBeta

Centa connects through your own organization’s API access. The integration is not an official partnership.

Last updated:

Excel/CSV statements

Export the statement from your online bank and upload the file. Centa finds the header row even when a title and blank rows sit above it, and understands columns in Russian, Uzbek and English: date, purpose, counterparty, STIR, debit/credit or a Direction column.

  • The payment direction comes from the file: an In/Out column wins over the sign of the amount.
  • Foreign-currency rows are skipped and counted — the books are kept in UZS.
  • Uploading the same statement again creates no duplicates.

API connection (beta)

Centa’s connector follows one API contract: accounts, balances, paginated transactions, retries under rate limits and webhooks, after which the transaction is re-read from the bank. Your bank issues the access key; it is stored encrypted.

What the software does with a statement after upload — reconciliation, journal entries, taxes — is on accounting software for businesses and in the bank reconciliation guide.

Frequently asked questions

Do I have to connect my bank by API?

No. Uploading statements is enough — the result in the books is the same. The API saves the manual upload.

Try Centa AI on a demo company

No sign-up: a ready demo company with real scenarios. When you are ready, connect your own company by its STIR.