Connecting SAP to Baltic Banks and Lithuanian Tax Authorities
Companies running SAP in Lithuania exchange data with banks, the tax authority, customs and their business partners every day. We build these connections in SAP Process Orchestration, so that the data leaves and enters SAP without manual exports and uploads.
- Clients
- Companies running SAP in Lithuania and the Baltics
- Scope
- Banking, tax and excise reporting, business platforms
- Platform
- SAP PI / PO
Technologies
- SAP PI/PO
- ABAP
- i.MAS (i.SAF, i.VAZ)
- SAF-T
- AIS-EMCS
The Challenge
Payments, bank statements and mandatory reports live in SAP, but the counterparties — banks, the State Tax Inspectorate, customs — each have their own formats, channels and deadlines.
Without an integration, finance teams export files, upload them to portals and re-enter responses by hand. Every manual step is a chance for a missed deadline or a mismatch between SAP and what was reported.
The Solution
Banking
Connections to SEB, Swedbank and Luminor: payment orders go from SAP to the bank, account statements come back into SAP for posting.
Tax reporting (i.MAS)
Data for the Lithuanian smart tax administration system: invoice registers (i.SAF) and waybills (i.VAZ), plus SAF-T files, generated from SAP data.
Excise (AIS-EMCS)
Exchange of excise movement documents with the customs AIS-EMCS system.
Business platforms
Integrations with Microsoft Dynamics CRM, the Adyen payment platform and e-commerce shops such as OpenCart.
Key Results
One integration hub
All external connections run through SAP PI/PO instead of scattered point-to-point scripts, with monitoring in one place.
No manual re-entry
Reports and payment files are built from the data already in SAP, and responses flow back into SAP automatically.
Ready for change
New banks, report types and partners are added as new interfaces on the same platform.
Have a similar challenge?
Tell us about your systems and processes — we will show how an integration or an AI agent can take the manual work off your team.