VMI — Lithuanian tax authority
The VMI (Valstybinė mokesčių inspekcija — State Tax Inspectorate) is the Lithuanian tax authority, attached to the Finansų ministerija. It runs the entire tax dispositif: PVM return, audit, the i.MAS platform, the e.VMI portal, and cross-checks with bank flows and social security (Sodra). Its modernisation since 2014 makes it a European case study of digitalised tax administration — VAT gap ~14% in 2024, continuously decreasing.
History — from VMI 1990 to digital 2024
VMI was created in 1990, in the wake of independence. The Mokesčių administravimo įstatymas (Tax Administration Act) of 1994 anchored its scope. Digital transformation started in 2014 with RKDS (i.EKA), accelerated with i.SAF in 2016, and today reaches a rare degree in Europe: automatic pre-fill, real-time bank cross-check, AI-based audit selection.
1990 | VMI created in the wake of independence. Mokesčių
| administravimo įstatymas adopted in 1994.
|
2002-2008 | First web portal vmi.lt. PVM returns still mostly paper-PDF.
|
2 Jan 2014 | RKDS / i.EKA — online cash registers. First EU mandate
| for real-time reporting to the tax authority.
|
1 Oct 2015 | i.VAZ — real-time waybills.
|
1 Oct 2016 | i.SAF — universal monthly VAT register (XML SAF-T).
| World's first — model copied by Poland, Hungary, Spain.
|
2017 | e.VMI portal (eservis.vmi.lt) redesigned. Authentication
| via E.Valdžia Vartai (Smart-ID, bank ID).
|
2018 | i.APS — automatic pre-fill of PVM return from monthly
| i.SAF registers.
|
2019-2021 | i.SAF-T (full SAF-T on demand). Integration of bank flow
| analysis from Lietuvos bankas for fraud detection.
|
2023-2026 | API modernisation (REST + OAuth2), mobile e.VMI portal,
| ViDA preparation — VMI will be the official platform for
| B2B CTC reporting post-2028.Governance — Finansų ministerija + VMI
VMI is a devolved service of the Finansų ministerija. Its director (viršininkas) is appointed by the government. The legal framework — Mokesčių administravimo įstatymas (administration), PVM įstatymas (VAT), PMĮ (corporate income tax), GPMĮ (personal income tax) — is voted by the Seimas and executed by VMI.
VMI doctrine is distinguished by the choice of a massive post-fact CTC over a pre-clearance B2B e-invoicing mandate (KSeF / SdI style). This approach relies on: i.SAF (monthly register), i.VAZ (real-time waybills), i.EKA (cash registers), and bank cross-check. Result: low cost for SMEs, targeted audits, continuously decreasing VAT gap.
Architecture — e.VMI + i.MAS + bank flows
┌──────────────────────────────────────────────────────────────────────────┐
│ VMI — architecture │
├──────────────────────────────────────────────────────────────────────────┤
│ │
│ PVM taxable person (ERP) │
│ │ │
│ │ 1. PVM deklaracija FR0600 (M+25) │
│ │ 2. i.SAF (invoice register, M+20) │
│ │ 3. i.VAZ (waybills real-time) │
│ │ 4. i.SAF-T (on demand / annual) │
│ ▼ │
│ ┌──────────────────────────────────────────────────────────────────┐ │
│ │ e.VMI (eservis.vmi.lt) │ │
│ │ ─ Web portal + REST APIs (OAuth2 via E.Valdžia Vartai) │ │
│ │ ─ i.APS pre-fill │ │
│ │ ─ Smart-ID / bank ID / eIDAS │ │
│ └──────────────────────────────────────────────────────────────────┘ │
│ │ │
│ ▼ │
│ ┌──────────────────────────────────────────────────────────────────┐ │
│ │ i.MAS data warehouse — cross-check modules │ │
│ │ ─ i.SKO (risk analysis + audit selection) │ │
│ │ ─ Cross-check with Sodra (social security) │ │
│ │ ─ Cross-check with Registrų centras (JAR, cadastre) │ │
│ │ ─ Bank flows from Lietuvos bankas (VAT fraud) │ │
│ └──────────────────────────────────────────────────────────────────┘ │
│ │
└──────────────────────────────────────────────────────────────────────────┘The Lithuanian originality lies in Lietuvos bankas bank flow integration. VMI receives, under strict legal regime (Mokesčių administravimo įstatymas + GDPR), aggregated data on flows between professional accounts. Combined with i.SAF, it enables near-real-time detection of VAT cycle anomalies (fictitious invoices, intra-EU carousels).
VMI vs other Baltic tax authorities
| Authority | Country | Portal | Key mandate | VAT gap 2024 |
|---|---|---|---|---|
| VMI | Lithuania | e.VMI | i.SAF (2016), RKDS (2014) | ~14% |
| VID | Latvia | EDS | B2G e-invoice + reporting | ~17% |
| MTA | Estonia | e-MTA | e-Estonia full digital | ~5% |
| Verohallinto | Finland | Vero.fi / OmaVero | RTE voluntary + EN 16931 right | ~3% |
| Skatteverket | Sweden | skatteverket.se | Centralised Skattekonto | ~3% |
Adoption — pre-fill and efficiency
- ~120,000 active PVM taxable persons in 2024.
- ~95% of PVM returns filed via e.VMI electronically (residual paper is for specific legal cases).
- VAT gap ~14% in 2024 vs ~25% in 2014 — 10-point drop in 10 years, attributed mainly to i.MAS deployment.
- ~80% of PVM returns pre-filled via i.APS — the SME just validates or corrects.
Common pitfalls
- Thinking e.VMI = username + password. e.VMI authentication goes through E.Valdžia Vartai — Smart-ID, bank ID (Swedbank, SEB, Luminor, Šiaulių bankas), or eIDAS for non-residents. No simple password.
- Confusing return and payment deadlines. Both are M+25 by default — but a taxable person in difficulty can request a separate payment schedule. The return remains strict M+25.
- Forgetting corporate income tax (PMĮ) advance. PMĮ advances are managed by VMI with their own calendar (quarterly for large enterprises). Do not confuse with monthly PVM.
- Strict i.SAF M+20. The i.SAF register must be filed before the 20th of month M+1, i.e. 5 days before the PVM return. i.APS pre-fill depends on this synchronisation.
- e.VMI API quotas. e.VMI REST APIs have per-OAuth2 client quotas (~1000/h free, contract beyond). To budget for cross-border ERP vendors.