Data scope
Bank transaction data available through the monobank and PUMB APIs. The banks are integration endpoints.
05 / Finance
A custom API exchange with monobank and PUMB brings banking transactions into the accounting system.
Connect banking data to accounting ↗
Conceptual illustration. See the interaction diagram for data scope and directions.
The task
Banking data needs to enter the accounting workflow without manually transferring statement files.
Interaction diagram
Bank transactions
Architecture
monobank and PUMB are independent banking sources. Custom API integration retrieves transactions from each bank and transfers them to BAS for accounting work.
Bank transaction data available through the monobank and PUMB APIs. The banks are integration endpoints.
Custom API exchange and banking-data updates. Payment initiation, automatic payment matching and automatic document posting are outside this case.
Agree API access, required accounting data and the update mode. This description does not specify a fixed polling interval or numerical latency.
What we developed
Implementation result
Bank transactions reach the accounting system through the APIs and become part of the BAS workflow.
Discuss your task ↗NEXT STEP
Describe your current system, task and intended result. We will agree the scope and prepare a proposal.
[email protected] ↗Contact us on Telegram ↗Vyvick Engineering on Telegram ↗