Skip to main content

Compliance Framework

Compliance Framework Document

Project: DropBilkoPSD2Balkan Pass-ThroughAccounting Payment AppSaaS Version: 1.0 Date: 2026-02-23 Author: SecurityCompliance Architect Status: Draft Reviewers: DPO, Legal Counsel, CEO Classification: Confidential

Document History

Version Date Author Changes
0.1 2026-02-23 SecurityCompliance Architect Initial draft — multi-jurisdictionthree-country compliance mapping RS/BA/HR

1. Applicable Regulations

Compliance Owner: CISO / Compliance OfficerArchitect ([email protected])[email protected]) External Auditor: To be engaged (Phase 2) Last Audit:Review: 2026-02-12 (internal security audit)23 | Next Audit:Review: 2026-Q3 (external pentest)08-23

Regulation ApplicabilityCountry Effective DateApplicability Status
PSD2GDPRBetalingstjenestelovenRegulation (LOV-2018-11-23-85)EU) 2016/679 YESHRDirectly applicablecore:EU AISP/PISP paymentsmember In force8% ready (BankID Phase 2)1
GDPR — Personopplysningsloven (LOV-2018-06-15-38)YES — processes personal data of all Norwegian usersMay 25, 201815% ready (DPIA done, processing register pending)
AML — Hvitvaskingsloven (LOV-2018-06-01-23)YES — payment service provider, remittanceIn force5% ready (procedures done, real KYC Phase 2)
IKT-forskriften (FOR-2003-05-21-630)YES — financial enterprise IT securityIn force25% ready
DORA (EU) 2022/2554YES — payment institutions (Norway EEA incorporation expected 2026 H2)Jan 17, 2025 (EU); ~2026 H2 (NO)Preparing
Finansforetaksloven (LOV-2015-04-10-17)YES — governance, licensingIn force0% licensed
Valutaregisterloven (LOV-2004-12-17-109)YES — all cross-border remittanceIn forceNot yet registered
Betalingssystemloven (LOV-1999-12-17-95)YES — payment systemsIn forceMonitoring
Finansavtaleloven (LOV-2020-12-18-146)YES — consumer protection2023Draft vilkår exists

Source: legal/drop-regulatory-map-v2.md, legal/drop-gap-analysis-v2.md


2. Norway — Finanstilsynet & Core Regulatory Compliance

2.1 Finanstilsynet Licensing

Applicable law: Betalingstjenesteloven (LOV-2018-11-23-85)

License OptionRequirementStatus
Begrenset betalingsforetak (§ 2-10c)Max 6M NOK/month, simplified applicationTarget for Phase 1 launch
Ordinært betalingsforetak (§ 2-3)125,000 EUR capital, EEA passportTarget for Scandinavia scaling
Agent model (§ 2-12)Operate under licensed PSP — fastest routeActively exploring partners

Current status: Not licensed. No live transactions until license or agent arrangement secured.

2.2 PSD2 / Betalingstjenesteloven Requirements

RequirementArticle/SectionOur Implementation
Strong Customer Authentication (SCA)§ 4-28, Del. Reg. (EU) 2018/389Phase 2: BankID OIDC (possession + knowledge)
Dynamic linking (amount + payee)Del. Reg. Art. 5Phase 2: Shown in BankID signing dialog
AISP — account information§ 4-41Phase 2: Open Banking AISP integration
PISP — payment initiation§ 4-44Phase 2: Open Banking PISP integration
No storing user bank credentials§ 4-44(3)✓ — Drop never stores bank login credentials
Pre-transaction fee disclosure§ 3-23Partial: fee shown in API, not pre-auth
Transaction receipt§ 3-22 to § 3-26Phase 1 prerequisite
Framework agreement (rammeavtale)§ 3-1 to § 3-8Draft exists: legal/brukervilkar.md
Execution time D+1 (EEA) / D+4 (non-EEA)§ 4-15Dependent on PISP partner SLA

2.3 AML — Hvitvaskingsloven

Full procedures: legal/hvitvaskingsrutiner.md

RequirementSectionOur Implementation
Enterprise risk assessment§ 6Document: legal/risikovurdering-hvitvasking.md
Written AML procedures§ 8Document: legal/hvitvaskingsrutiner.md
Customer identification (KYC)§ 12BankID: name + fødselsnummer (Phase 2)
Electronic verification§ 12(3)BankID qualifies as electronic verification
PEP screening§ 18Integration: ComplyAdvantage / Refinitiv (Phase 2)
Sanctions screeningSanksjonsforskrifterIntegration: EU/UN/Norwegian/OFAC lists (Phase 2)
Transaction monitoring§ 24Rules defined in hvitvaskingsrutiner.md
STR filing to EFE (Økokrim)§ 26Process documented; system Phase 2
No tipping off§ 28Policy: never inform customer of STR
Record keeping — 5 years§ 30Policy defined; technical implementation Phase 2
AML officer appointment§ 8(4)Required before licensing

Corridor risk classification:

RisikonivåLand/korridorerTiltak
LavEU/EØS-land, StorbritanniaStandard CDD
MiddelsSerbia (RSD), Bosnia-Hercegovina (BAM), Tyrkia (TRY)Utvidet overvåking
HøyPakistan (PKR)EDD obligatorisk
SperretFATF/EU sanksjonslisterBlokkert i system

2.4 GDPR — Personopplysningsloven

See dedicated DPIA: data-protection-impact-assessment.md. Full privacy notice: legal/personvernerklaering.md.

ArticleRequirementOur Implementation
Art. 5Data minimization, purpose limitationCollect only necessary fields; defined purposes
Art. 6(1)(b)Contract basis — core service deliveryRemittance, QR payments, account management
Art. 6(1)(c)Legal obligation basis — AML/KYCHvitvaskingsloven §§ 4, 10-18
Art. 6(1)(a)Consent basis — AISP balance accessUser grants PSD2 consent for Open Banking
Art. 13Privacy noticelegal/personvernerklaering.md — Norwegian
Art. 28Data processor agreementsDPAs required with BankID, cloud provider, Sumsub
Art. 30Register of processing activities (behandlingsprotokoll)Pending
Art. 32Appropriate technical/organisational measuresSee security-architecture.md
Art. 3372-hour breach notification to DatatilsynetSee data-breach-response-plan.md
Art. 35DPIA for high-risk processingDocument: legal/dpia-vurdering.md
Art. 37DPO designationDPO contact: [email protected]

2.5 Valutaregisterloven

RequirementSectionOur Implementation
Register with SSB as reporting entity§ 3To be completed before first cross-border transaction
Report all cross-border payments§ 4Monthly reporting to SSB
Transaction data: amount, currency, country, purpose code§ 5recipients.country in DB schema
Retention — 5 years§ 6Policy defined

3. Serbia — Multi-Jurisdiction Compliance

3.1 Data Protection

Applicable law: Zakon o zaštiti podataka o ličnosti (ZZPL, Sl. glasnik RS br. 87/2018) RS GDPR-aligned — in force Nov 2018 Phase 2 Zakon o zaštiti ličnih podataka (LawZZLP, onSl. Personalglasnik BiH 49/2006, 76/2011) BA State-level data protection law Phase 3 Zakon o računovodstvu (Sl. glasnik RS 73/2019, 44/2021) RS Accounting law, double-entry, retention Phase 2 Zakon o računovodstvu i reviziji FBiH (Sl. novine FBiH 83/2009, 56/2023) BA (FBiH) Accounting and audit law Phase 3 Zakon o računovodstvu i reviziji RS BiH (Sl. glasnik RS BiH 96/2005) BA (RS) Accounting and audit law Phase 3 Zakon o računovodstvu HR (NN 78/15, 120/16, 116/18) HR Accounting law, CFRS, retention Phase 2 Zakon o PDV (Sl. glasnik RS 84/2004 et al.) RS VAT law, 20%/10%/0% rates Phase 2 Zakon o PDV BiH (Sl. glasnik BiH 9/2005 et al.) BA VAT law, 17%/0% rates, UIO Phase 3 Zakon o porezu na dodanu vrijednost HR (NN 73/13 et al.) HR VAT law, 25%/13%/5%/0%, ePorezna Phase 2 Zakon o elektronskom dokumentu (Sl. glasnik RS 51/2009) RS Legal validity of electronic records Phase 2 Opći porezni zakon HR (NN 115/16 et al.) HR General tax law framework Phase 2 Pravilnik o kontnom okviru RS (2021) RS Chart of accounts standard Phase 2 FBiH Pravilnik o kontnom okviru (2022) BA (FBiH) Chart of accounts standard Phase 3 RRiF Kontni plan HR HR Standard chart of accounts Phase 2


2. Serbia (RS) — Regulatory Compliance

2.1 Data Protection — Zakon o zaštiti podataka o ličnosti (ZZPL)

Full name: Zakon o zaštiti podataka o ličnosti Citation: Sl. glasnik RS br. 87/2018 In force: November 21, 2018 Description: Serbia's GDPR-aligned legislation,personal indata forceprotection Novemberlaw. 21,Mirrors 2018)GDPR structure and principles. Supervisory authority: Poverenik za informacije od javnog značaja i zaštitu podataka o ličnosti (Commissioner for Information of Public Importance and Personal Data Protection) Website: https://www.poverenik.rs

/account,GET
Requirement LawZZPL Article OurBilko Implementation
Lawful basis for processing ZZPL Art. 12 Contract performance(Art. 12 st. 1 tač. 2) — accounting service delivery
Data minimizationArt. 5 st. 1 tač. 3Collect only email, name, tax ID (PIB/JMBG) — required for remittance; legal obligation for AMLinvoicing
Data subject rights (access, erasure, portability) ZZPL Art. 26-41 ViaEndpoints: DPOGET process/account/data, atDELETE [email protected]
Data transfer outside SerbiaZZPL Art. 64-65Drop's servers in Norway/EEA — transfer covered by adequacy assessment
Notification to PoverenikZZPL Art. 5672-hour breach notification to Commissioner for Information of Public Importance and Personal Data Protection/account/export
Register of processing activities ZZPL Art. 50 PendingInternal processing register — required
Security of processingArt. 50TLS 1.3 + AES-256 + bcrypt + RBAC
Breach notification to PoverenikArt. 56Within 72 hours of becoming aware
Cross-border data transferArt. 64-65Railway EU West — within ZZPL scope

TransferBreach mechanismnotification — Norway → Serbia:contact:

  • NorwayAuthority: isPoverenik EEAza butinformacije notod EU;javnog Serbiaznačaja hasi nozaštitu EUpodataka adequacyo decisionličnosti
  • TransferAddress: basis:Bulevar Standardkralja ContractualAleksandra Clauses15, 11000 Belgrade
  • Email: [email protected]
  • Deadline: 72 hours from awareness (SCCs) per ZZPL Art. 65 + GDPR Art. 46(2)(c)
  • Transfer Impact Assessment (TIA): Required — assess Serbian law on government data access
  • Minimal data transferred: Only avsender's name (lawpålagt) + mottaker's name/IBAN + amount56)

3.2.2 AMLAccounting Law — Zakon o računovodstvu

ApplicableFull law:name: Zakon o sprečavanjuračunovodstvu pranja novca i finansiranja terorizma (ZoPNFT,Citation: Sl. glasnik RS br. 113/2017, 91/73/2019, 153/2020)44/2021 (LawDescription: onDefines Preventionaccounting ofobligations Moneyfor Launderingall andlegal Terrorismentities Financing)in Serbia.

Requirement OurBilko RoleImplementation
CorrespondentDouble-entry bankbookkeeping in Serbia performs CDD on recipientsmandatory CorrespondentPrisma bankschema responsibilityenforces debitAccountId + creditAccountId — debit = credit validated
DropChart providesof completeaccounts: senderPravilnik informationo perkontnom FATFokviru Recommendation(2021) 16— 10 class system (0-9) Serbian CoA name,seed account,data referencewith standard 3-digit accounts
SerbianFinancial NBSstatements required: Bilans stanja (NarodnaBalance bankaSheet), Srbije)Bilans oversightuspeha of(Income payment systemsStatement) ViaReport correspondentgeneration bankmodule (Phase 2)
Large entities: Izveštaj o novčanim tokovima (Cash Flow), Napomene (Notes)Phase 2
Filing institution: APR (Agencija za privredne registre) — https://www.apr.gov.rsPDF export in Serbian format
Annual filing deadline: June 30Filing reminders in app
Document retention: 10 yearsSoft delete — financial records never hard deleted

3.2.3 PaymentVAT ServicesLaw — Zakon o PDV

ApplicableFull law:name: Zakon o platnimporezu uslugamana (dodatu vrednost Citation: Sl. glasnik RS br. 139/2014,84/2004, 44/2018)86/2004, 61/2005 et al. (Lawconsolidated) on Payment Services —Description: Serbia's PSD2-equivalent)VAT law.

RateDescriptionApplication
20% (opšta stopa)Standard rateGeneral goods and services
10% (snižena stopa)Reduced rateFood, medicines, utilities
0%Zero rateExports, international transport

VAT registration threshold: 8,000,000 RSD annual turnover Return frequency: Monthly (>50M RSD) or Quarterly (<50M RSD) Filing deadline: 15th of following month Portal: ePorezi — https://www.poreskauprava.gov.rs Penalties: 50,000 – 2,000,000 RSD for SEF non-compliance

2.4 E-Invoice — SEF (Sistem e-Faktura)

Platform: https://efaktura.gov.rs Mandatory since:

  • B2G (suppliers to government): May 2022
  • B2B (business-to-business): January 2023

Format: UBL 2.1 XML Integration: API available — @bilko/country-rs package (Phase 2) Penalties: 50,000 – 2,000,000 RSD for non-compliance

2.5 Electronic Document Law

Full name: Zakon o elektronskom dokumentu, elektronskoj identifikaciji i uslugama od poverenja u elektronskom poslovanju Citation: Sl. glasnik RS br. 94/2017 Description: Legal validity of electronic documents and digital signatures.

DropBilko-generated operatesinvoices asand areports foreignconstitute PSPvalid transferringelectronic fundsdocuments towhen:

Serbia
    via
  • Generated correspondentby banking.certified Directaccounting licensesoftware
  • from
  • Stored NBSimmutably notwith requiredaudit trail
  • Exportable in PDF/XML format

2.6 APR Filing


4.3. Bosnia and& Herzegovina (BA) Multi-JurisdictionRegulatory Compliance

Complexity: BiH has two entities (FBiH and Republika Srpska) with parallel legislation. VAT is unified at state level via UIO. Direct taxes are administered separately per entity.

4.3.1 Data Protection — Entity-LevelZakon Regulationo zaštiti ličnih podataka BiH

BosniaFull and Herzegovina has two entities with separate data protection legislation:

Federation of BiH (FBiH):

  • Applicable law:name: Zakon o zaštiti ličnih podataka (ZZLPBosne BiH,i Hercegovine Citation: Sl. glasnik BiH br. 49/2006, 76/2011, 89/2011)2011 (PersonalDescription: DataState-level Protectionpersonal Lawdata protection state-level,law. administeredPre-GDPR bybut aligned in principles. Supervisory authority: Agencija za zaštitu ličnih podataka Bosne i Hercegovine (AZLP)
Website: https://www.azlp.ba

RepublikaThe Srpska:

  • Samesame state-level law applies across both entitiesFBiH forand personalRepublika data protection
  • AZLP (Agency for Personal Data Protection of BiH) is the supervisory authority for the entire country
Srpska.

Requirement LawZZLP Article OurBilko Implementation
Lawful basis for processing ZZLP Art. 4 Contract (accounting service delivery) + legal obligation (tax records)
SecurityData security measures ZZLP Art. 14 TLS 1.3,3 + AES-256,256 + bcrypt + RBAC
DataCross-border transfer to third countries ZZLP Art. 18 Norway is not inRailway EU West adequacyoutside assessment per ZZLP +BiH; SCCs mechanism
Breach notification to AZLP ZZLPArt. 14 + GDPR practice 72-hour72 notificationhours
Data subject rightsArt. 5-10Same endpoints as RS

TransferBreach mechanismnotification — Norway → BiH:contact:

  • NoAuthority: adequacyAgencija decisionza forzaštitu BiHličnih frompodataka EU/NorwayBosne i Hercegovine (AZLP)
  • TransferAddress: basis:Hamdije SCCsČemerlića +2/VI, TIA71000 Sarajevo
  • MinimalEmail: data:[email protected]
  • sender
  • Deadline: name72 +hours recipient(following name/IBAN/BAMGDPR amountbest practice)

4.3.2 AMLFBiH — Accounting Law

ApplicableFull law:name: Zakon o sprečavanju pranja novcaračunovodstvu i finansiranjareviziji terorističkihFederacije aktivnostiBosne (ZSPNFiTAi BiH,Hercegovine Citation: Sl. glasniknovine BiHFBiH br. 47/2014,83/2009, 46/2017)56/2023 (LawDescription: onAccounting Preventionand audit law for Federation of Money Laundering and Financing of Terrorist Activities — BiH)

Supervisory authority: Ured za sprečavanje pranja novca (USPN) — FATF/MONEYVAL memberBiH.

Requirement OurBilko RoleImplementation
CompleteDouble-entry sender information on transfersbookkeeping Enforced by FATF Rec. 16 compliantschema
CorrespondentChart bankof performsaccounts: beneficiaryFBiH CDDPravilnik (2022) — 10 class system (0-9) CorrespondentBiH bankCoA responsibilityseed data
BAMFinancial corridorstatements: classifiedBilans asstanja, "Middels"Bilans riskuspeha HigherReport monitoringgeneration thresholdsmodule apply(Phase 3)
Filing institution: Agency of Financial Information (FBiH)PDF export
Annual filing deadline: March 31Filing reminders
Document retention: 10 yearsImmutable storage

4.3.3 PaymentRepublika ServicesSrpska (BiH Entity) — Accounting Law

ApplicableFull law:name: Zakon o platnom prometu (FBiH); Zakon o platnim transakcijama (RS) Regulator: Centralna banka Bosneračunovodstvu i Hercegovinereviziji (CBBH)

Republike

DropSrpske transfersCitation: toSl. glasnik RS BiH viabr. correspondent96/2005, banking;74/2016 noDescription: directAccounting CBBHand licenseaudit requiredlaw for NorwegianRepublika outboundSrpska remittance.

entity
of

5. Croatia — Multi-Jurisdiction Compliance

5.1 Data Protection

Croatia is an EU member state — GDPR applies directly.BiH.

Requirement OurBilko Implementation
GDPRDouble-entry (Regulation (EU) 2016/679) directly applicablebookkeeping FullEnforced GDPRby compliance required — see §2.4schema
AZOPFiling institution: Tax Administration of RS (AgencijaBiH za zaštitu osobnih podataka) as supervisory authorityentity) BreachPDF notification within 72h to AZOPexport
Annual filing deadline: March 31Filing reminders
Document retention: 11 yearsMaximum retention applied across entities

3.4 VAT — Zakon o PDV BiH

Full name: Zakon o porezu na dodanu vrijednost Bosne i Hercegovine Citation: Sl. glasnik BiH br. 9/2005, 35/2005, 100/2008 et al. Description: Unified VAT law administered at state level. No reduced rates. Administering authority: UIO — Uprava za indirektno oporezivanje (Indirect Taxation Authority) Portal: https://www.uino.gov.ba

RateDescription
17% (opća stopa)Standard rate — all goods and services
0%Exports

Registration threshold: 100,000 BAM annual turnover Return frequency: Monthly Filing deadline: Check UIO portal

3.5 E-Invoice — CPF (Central Platform for Fiscalisation)

Status: PENDING — technical specifications not yet published Law adopted: January 2026 (FBiH only) Expected availability: ~2027

Bilko decision: Do NOT implement CPF integration until technical specs are published. Monitor UIO and FBiH government portals for updates. BiH is Phase 3 launch.

3.6 Corporate Income Tax

EntityCIT RateFiling Deadline
FBiH10%March 31
RS (BiH entity)10%March 31

Bilko provides CIT calculation support — separate fields for FBiH vs RS entity in organization settings.


4. Croatia (HR) — Regulatory Compliance

Note: Croatia is an EU member state. GDPR applies directly without separate national transposition law.

4.1 Data Protection — GDPR

Applicable law: GDPR — Regulation (EU) 2016/679 (directly applicable) National implementing act: Zakon o provedbi Opće uredbe o zaštiti podataka (NN 42/2018) Croatian implementing legislation — aligns with GDPR

Transfer mechanism — Norway → Croatia:

  • Croatia is EU — no restriction on EEA→EU data transfer
  • Drop (Norway/EEA) → Croatia (EU): Free flow under GDPR Chapter V + EEA Agreement
  • No SCCs required; no TIA required

5.2 AML

Applicable law: Zakon o sprečavanju pranja novca i financiranja terorizma (ZSPMFT, NN 108/2017, 39/2019, 151/2022) (Law on Prevention of Money Laundering and Terrorist Financing — Croatia)

Supervisory authority: UredAZOP — Agencija za sprječavanjezaštitu pranjaosobnih novcapodataka (USPM)Website: — FATF member as EU statehttps://azop.hr

name, thresholds
Requirement OurGDPR RoleArticleBilko Implementation
CompleteLawful sender information — EU Wire Transfer Regulation (2015/847) appliesbasis Art. 6 Contract IBAN,(6.1.b) referencefor service; legal obligation (6.1.c) for tax
CroatianData bank performs beneficiary CDDminimization CorrespondentArt. bank5(1)(c)Collect OIB (Croatian HNB-licensedtax institution)ID), name, email only
CroatiaRight corridor:to EUR — EU/EEA — Low riskaccess StandardArt. CDD15 GET /api/v1/account/data
Right to erasureArt. 17DELETE /api/v1/account (PII anonymized; financial records retained per law)
Right to portabilityArt. 20GET /api/v1/account/export (JSON)
Security of processingArt. 32TLS 1.3 + AES-256 + bcrypt + RBAC
Breach notification to AZOPArt. 33Within 72 hours
DPIAArt. 35This document covers accounting data
DPA with processorsArt. 28Required with Railway, Vercel, Cloudflare, SendGrid

Breach notification contact:

  • Authority: AZOP — Agencija za zaštitu osobnih podataka
  • Address: Selska cesta 136, 10000 Zagreb
  • Email: [email protected]
  • Portal: https://azop.hr/prijavapovrede
  • Deadline: 72 hours from awareness (GDPR Art. 33)

5.34.2 PaymentAccounting ServicesLaw — Zakon o računovodstvu

ApplicableFull law:name: Zakon o platnomračunovodstvu prometuCitation: (NN 66/201878/15, 120/16, 116/18, 42/20, 47/20 Description: Croatian PSD2accounting implementation)law, Regulator:aligns Hrvatskawith narodna banka (HNB)

EU WireAccounting Transfer Regulation (2015/847) applies directly. Drop must include complete originator information on all transfers to Croatia. No direct HNB license required for Norwegian outbound remittance via correspondent banking.Directive.


6. Cross-Border Data Transfer Summary

Bilko Enforced HR CFRS-compliant Report FINA flow
FromRequirement To MechanismTIA RequiredDPA RequiredNotesImplementation
NorwayDouble-entry (EEA)bookkeeping Serbia SCCsby (2021) + TIAYesYesNo adequacy decisionschema
NorwayChart of accounts: RRiF standard — 10 class system (EEA)0-9) BiH SCCsCoA (2021)seed + TIAYesYesNo adequacy decisiondata
NorwayAccounting standards: CFRS (EEA)for SMEs) or IFRS (PIEs) Croatia EEA→EU free flowNoN/AEU member statereports
NorwayFinancial (EEA)statements: Bilanca, Račun dobiti i gubitka, Izvještaj o novčanim tokovima Turkey SCCsgeneration module (2021)Phase + TIAYesYesNo adequacy decision; higher risk2)
NorwayFiling via RGFI (EEA)Registar godišnjih financijskih izvještaja) Pakistan SCCs (2021) + TIA + supplementary measuresYesYesHigh-risk jurisdictionfiling
NorwayFiling (EEA)institution: FINA — Financijska agencija — https://www.fina.hr Poland
Annual filing deadline: April 30 EEA→EUFiling freereminders
Document retention: 11 years NoImmutable storage

4.3 General Tax Law — Opći porezni zakon

Full name: Opći porezni zakon Citation: NN 115/16, 106/18, 121/19, 32/20 et al. Description: Framework tax law governing all Croatian taxes, including penalties for VAT non-compliance.

Relevant to Bilko: Defines document retention (11 years), electronic record acceptance, and obligations for digital accounting systems.

4.4 VAT Law — Zakon o porezu na dodanu vrijednost

Full name: Zakon o porezu na dodanu vrijednost Citation: NN 73/13, 148/13, 143/14 et al. Description: Croatian VAT law implementing EU VAT Directive. Portal: ePorezna — https://www.porezna-uprava.hr

RateDescriptionApplication
25% (opća stopa) N/AStandard rate General goods and services
13% (srednja stopa)Intermediate rateCertain foods, water supply, accommodation, newspapers
5% (snižena stopa)Reduced rateBooks, baby food, prescription medicines
0%Zero rateExports, intra-EU member statesupply

Registration threshold: 60,000 EUR annual turnover Return frequency: Monthly Filing deadline: Last day of following month

4.5 E-Invoice — HR-FISK / eRačun

Platform: https://hr-fisk.fina.hr Operator: FINA — Financijska agencija Status: Mandatory since January 1, 2026 (all B2B, B2G, B2C) Format: UBL 2.1 XML with HR-CIUS (Croatian Implementation User Specification) Protocol: AS4 (Peppol-compatible) Certificate: FINA qualified certificate required

Integration: @bilko/country-hr package (Phase 2) — FINA API integration required Penalties: Up to 500,000 EUR for non-compliance (severe) Archive requirement: 11 years

4.6 FINA Reporting

4.7 HNB (Hrvatska narodna banka)

For organizations with foreign currency transactions, HNB reporting may apply. Bilko supports EUR (Croatia's official currency since January 2024), with historical HRK support for data migration.


5. Cross-Country Compliance Matrix

RequirementSerbia (RS)Bosnia & Herzegovina (BA)Croatia (HR)
Data minimizationprotection lawZZPL (GDPR-aligned, 2018)ZZLP BiH (state-level, 2006)GDPR (directly applicable)
Supervisory authorityPoverenikAZLPAZOP
Breach notification deadline72 hours72 hours (best practice)72 hours (GDPR Art. 33)
Double-entry bookkeeping✅ Mandatory✅ Mandatory✅ Mandatory
Standard VAT rate20%17%25%
Reduced VAT rate10%None13% and 5%
VAT return frequencyMonthly/QuarterlyMonthlyMonthly
VAT filing deadline15th of next monthTBD (UIO)Last day of next month
E-invoice platformSEF (mandatory since Jan 2023)CPF (pending ~2027)HR-FISK (mandatory since Jan 2026)
E-invoice formatUBL 2.1 XMLTBDUBL 2.1 XML (HR-CIUS)
Annual report filingAPR — June 30Agency of Financial Info / Tax Admin RS — March 31FINA RGFI — April 30
Chart of accountsPravilnik (2021)FBiH Pravilnik (2022)RRiF standard
Document retention10 years10 years (FBiH) / 11 years (RS entity)11 years
CurrencyRSDBAMEUR
Corporate income tax15%10% (both entities)18% (10% if revenue <1M EUR)

Bilko retention policy: Apply maximum retention across all markets — 11 years for all transfers:financial records. Financial data is never hard-deleted.

  • Sender: Full name only (lawfully required per FATF/EU 2015/847)
  • Recipient: Name + account/IBAN only
  • Never transferred: fødselsnummer, IP address, device ID, transaction history

7.6. Data Classification Scheme

Level LabelDescription Examples Controls Required
L1 PublicIntended for public access Exchange rates, fee schedule, privacy policy None
L2 Internal InternalAggregated use onlyInternal wikis,analytics, non-PII analytics, logs (masked) Access control
L3 ConfidentialSensitive personal or business data User names, phone, email, transactionname, history,organization KYCdata, statusinvoice amounts Encryption + access control + loggingaudit log
L4 Restricted HighestTax sensitivity,IDs regulatory implicationsFødselsnummer,(PIB/JMBG/OIB/JIB), bank account numbers, KYCTOTP documents, JWT_SECRET, BankID certificatessecrets Field-levelEncryption encryption+ RBAC + MFA + strict access + audit + 5-10-year retention

Tax

    (Poreski identifikacionibroj)digits;JMBGmatičnigrađana)13digits
  • BiH:
  • JIB(Jedinstveni payloadsor logs.


    9.7. Data Subject Rights — Implementation

    data
    Right Endpoint / Process SLA Automated?Notes
    Access (SAR)Art. 15 GDPR / ZZPL Art. 26 / ZZLP Art. 8) [email protected]GET /api/v1/account/data 30 daysReturns user + org + invoices + expenses
    Rectification (Art. 16)PATCH /api/v1/account/profileImmediateEmail, name
    Erasure (Art. 17)DELETE /api/v1/account30 daysPII anonymized; financial records retained per law
    Portability (Art. 20)GET /api/v1/account/export 30 days PartialJSON export
    RectificationRestriction (Art. 18) App Settings → Edit Profile[email protected] Immediate30 daysManual process
    Objection (Art. 21)[email protected]30 daysNot applicable for contract processing

    Erasure exception: Financial records (invoices, expenses, transactions) are retained for the legally required period (10-11 years depending on country) even after user account erasure. Only PII (email, name, password hash) is anonymized.


    8. Third-Party Data Processors

    retention exceptions)EU
    ProcessorServiceData SharedRegionDPA Required
    RailwayPostgreSQL hostingAll accounting dataEU West (Frankfurt/Paris)Yes — sign before launch
    VercelFrontend hostingNone (static only)Global (EU edge for EU users) Yes
    ErasureCloudflare [email protected]CDN, WAF, anonymizeR2 jobstorage 30IP daysaddresses, file attachments PartialEU (AMLregion Yes
    PortabilitySendGrid DataTransactional export (JSON/CSV)email 30Email daysaddresses, invoice PDFs Planned
    Restrictionregion Support request → compliance flag30 daysNo (manual)
    Objection[email protected]30 daysNo (manual)
    Automated decision opt-outFraud detection manual review request30 daysPartialYes

    IdentityDPA verificationstatus: All DPAs must be signed before first paying customer. Railway EU West region must be explicitly configured to ensure EU data residency.


    9. Compliance Roadmap

    Phase 1 — Pre-Launch (GDPR baseline)

    •  Privacy policy published (HR GDPR applicable immediately; RS/BA when launched)
    •  Terms of Service published
    •  User consent mechanism at registration
    •  Data deletion workflow implemented and tested
    •  Data export endpoint implemented
    •  DPAs signed with Railway, Vercel, Cloudflare, SendGrid
    •  Railway EU West region confirmed
    •  Breach notification process documented

    Phase 2 — Serbia Launch (3-6 months)

    Phase 2 — Croatia Launch (concurrent or shortly after)

    Phase 3 — BiH Launch (12-18 months)


    10. AuditRisk Schedule & MethodologyAssessment

    GDPR/ZZPLimplementationSEFintegrationbeforeSerbiaB2B PhaseHR-FISKbackups,audit
    Audit TypeRisk FrequencyLikelihood ScopeImpact OwnerLast DoneNext DueMitigation
    InternalGDPR/ZZPL accessdata reviewbreach fine QuarterlyLow (if compliant) AllHigh user(GDPR accountsup +to permissions€20M / ZZPL up to RSD 2M) SecurityFull team 2026-02-13 2026-05-13before first customer
    VulnerabilitySEF assessmentnon-compliance (Serbia) QuarterlyMedium (if not integrated) ExternalHigh attack(RSD surface2M fine) SecurityPhase /2 external 2026-02-12 2026-05-12
    Penetration testAnnualFull scopeExternal firm (TBD)Not yet done2026-Q3
    AML program reviewAnnualFull AML programCompliance + externalDraft onlyPre-launch
    GDPRHR-FISK non-compliance review(Croatia) AnnualHigh (if not integrated) AllCritical processing(EUR activities500K fine) DPO 2026-02-122 (DPIA) 2027-02-12integration — mandatory
    DORAFinancial readinessdata reviewloss AnnualLow ICT resilienceCritical CISO30-day +Railway external Notimmutable yet 2026-Q4trail
    Third-partyTax riskcalculation reviewerror (VAT) AnnualLow BankID,High cloud(penalties provider,+ Sumsubreputational) ComplianceConfigurable tax rates per country, Zod validation
    BiH CPF delay Not yetMedium Pre-Low (launch delayed)Phase 3 planned, not blocking Serbia/Croatia

  • DPIA:
  • Breach
  • data-breach-response-plan.md../../products/Bilko/docs/security/COMPLIANCE.md
  • Serbia
  • Regulatory:Regulatory:
    TrainingAudienceFrequencyFormat
  • Security awarenessArchitecture: +security-architecture.md
  • phishing
    Alldata-protection-impact-assessment.md staffAnnualResponse +Plan: onboarding Online
  • Bilko +Compliance: simulation
  • GDPR../../products/Bilko/docs/regulatory/RS/README.md
  • BiH Regulatory: ../../products/Bilko/docs/regulatory/BA/README.md
  • personopplysningsloven
  • Croatia fundamentals
  • All../../products/Bilko/docs/regulatory/HR/README.md staff handling personal dataAnnualOnline
    AML / hvitvaskingsloven — GrunnkursAll staffAt employment + annualOnline
    AML / hvitvaskingsloven — AvansertCompliance, operationsAnnualWorkshop
    PEP og sanksjonerCompliance, operationsAnnualOnline
    Secure codingEngineeringAnnualWorkshop
    Incident response tabletopEngineering + ManagementAnnualTabletop exercise

    12. Critical Vendor Compliance Register

    VendorServiceTierRequirementsDPA Status
    BankID Norge ASNorwegian eID authenticationCriticalSOC 2, ISO 27001Required — databehandleravtale
    AWS App RunnerApplication hostingCriticalSOC 2 Type II, ISO 27001, PCI-DSSStandard AWS DPA
    CloudflareWAF + DDoS + CDNCriticalSOC 2 Type II, ISO 27001Cloudflare DPA
    SumsubKYC/AML identity verificationCriticalSOC 2, ISO 27001, GDPRRequired — DPA
    SentryError monitoringHighSOC 2Sentry DPA
    BetterStackUptime + log monitoringHighSOC 2BetterStack DPA

Approval

Role Name Date Signature
Author SecurityCompliance Architect 2026-02-23
DPO
CISO
Legal Counsel
CEO / Management