The problem
“Before reconciliation, we download files from several banks. Then we need to check what was imported and what is missing.”
Context
- Operation
- Retail operation, Nicaragua
- Systems involved
- Bank APIs · integration · financial ERP
The approach
The integration queries each bank’s authorized APIs, normalizes transactions and delivers them to the financial ERP. Access is limited to the data needed for the agreed process.
Bank APISecure validationFinancial ERP
Frequency and sequencing
Frequency depends on the bank’s limits. A checkpoint per account allows processing to resume after the last confirmed query.
Duplicates and retries
The transaction identifier prevents repeated imports. Retries respect API limits and record their outcome.
When an API is unavailable
The query stays pending and the owner is alerted. After reconnection, the missing interval is checked before continuing.
Restricted access
Server-side secrets, account-level permissions and logs without balances or credentials. Authentication follows each bank’s API requirements.
Outcome
- Bank data available to the financial workflow.
- Less manual file exchange.
- Traceable imports and scoped access.