Effort Estimator

Understanding integration timelines is critical for project planning. The benchmarks below are based on real customer integrations and reflect effort from API key to production go-live.

💡Multi-country advantage

Customers using the Unified API (France, Italy, Sweden) report 60-80% less effort when adding a second or third country, since the API surface and resource model are shared.

Effort by country

Germany — SIGN DE (Specialized API)

Estimated effort: 1-3 weeks

1. Week 1 — Sandbox setup, authentication, first signed transaction
2. Week 2 — TSS lifecycle management, receipt QR codes, DSFinV-K export
3. Week 3 — Production go-live, monitoring, compliance validation

Prerequisites: HUB account, understanding of KassenSichV requirements

---

Austria — SIGN AT (Specialized API)

Estimated effort: 1-2 weeks

1. Week 1 — Sandbox setup, RKSV signing flow, DEP export
2. Week 2 — FinanzOnline registration, production go-live

Prerequisites: HUB account, FinanzOnline credentials for production

---

France — SIGN FR (Unified API)

Estimated effort: 1-3 weeks

1. Week 1 — Sandbox setup, Unified API authentication, first signed transaction
2. Week 2 — JCD archive export, receipt data integration
3. Week 3 — NF525 compliance validation, production go-live

Prerequisites: HUB account, NF525 certification awareness

---

Italy — SIGN IT (Unified API)

Estimated effort: 1-3 weeks

1. Week 1 — Sandbox setup, RT signing flow, AdE transmission
2. Week 2 — Receipt data and correction flows
3. Week 3 — Production go-live, Agenzia delle Entrate validation

Prerequisites: HUB account, Italian tax ID for production

---

Spain — SIGN ES (Specialized API)

Estimated effort: 1-2 weeks

1. Week 1 — Sandbox setup, TicketBAI, Verifactu or SII flow, digital receipt
2. Week 2 — Production go-live

Prerequisites: HUB account

---

📘These are estimates

Actual integration time depends on your team’s familiarity with fiscal compliance, existing POS architecture, and the number of transaction types you need to support. Contact your fiskaly account manager for a tailored assessment.

Multi-country rollout

If you plan to operate in multiple countries, consider starting with a Unified API market (France, Italy, or Sweden). The shared resource model means subsequent countries reuse the same authentication, transaction lifecycle, and export patterns — reducing incremental effort to days rather than weeks.

Rollout scenario	Estimated total effort
Single Specialized API country	1-3 weeks
Single Unified API country	1-3 weeks
Two Unified API countries	2-4 weeks (second country adds ~1 week)
Three Unified API countries	3-5 weeks (third country adds ~1 week)
Mixed: 1 Specialized + 1 Unified	3-5 weeks (parallel workstreams)