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.
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.
Multi-country rollout
Section titled “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.
Your first Unified API country is the investment — every next one is nearly free. The first integration builds your reusable foundation: authentication, the transaction lifecycle, and the export/receipt patterns. Every additional Unified API country reuses that same foundation, so the incremental effort drops from weeks to days:
- 1st Unified API country — 1–3 weeks (builds the reusable foundation)
- Each additional Unified API country — ~days, not weeks (reuses auth, resource model & exports; only country-specific compliance differs)
A Specialized API, by contrast, has to be integrated from scratch for every country. So the more markets you roll out, the more that first Unified API integration pays off — the up-front investment is amortized across every country that follows.
| 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) |
Effort by country
Section titled “Effort by country”Germany — SIGN DE (Specialized API)
Section titled “Germany — SIGN DE (Specialized API)”Estimated effort: 1-3 weeks
- Week 1 — Sandbox setup, authentication, first signed transaction
- Week 2 — TSS lifecycle management, receipt QR codes, DSFinV-K export
- Week 3 — Production go-live, monitoring, compliance validation
Prerequisites: HUB account, understanding of KassenSichV requirements
Austria — SIGN AT (Specialized API)
Section titled “Austria — SIGN AT (Specialized API)”Estimated effort: 1-2 weeks
- Week 1 — Sandbox setup, RKSV signing flow, DEP export
- Week 2 — FinanzOnline registration, production go-live
Prerequisites: HUB account, FinanzOnline credentials for production
France — SIGN FR (Unified API)
Section titled “France — SIGN FR (Unified API)”Estimated effort: 1-3 weeks
- Week 1 — Sandbox setup, Unified API authentication, first signed transaction
- Week 2 — JCD archive export, receipt data integration
- Week 3 — NF525 compliance validation, production go-live
Prerequisites: HUB account, NF525 certification awareness
Italy — SIGN IT (Unified API)
Section titled “Italy — SIGN IT (Unified API)”Estimated effort: 1-3 weeks
- Week 1 — Sandbox setup, RT signing flow, AdE transmission
- Week 2 — Receipt data and correction flows
- Week 3 — Production go-live, Agenzia delle Entrate validation
Prerequisites: HUB account, Italian tax ID for production
Spain — SIGN ES (Specialized API)
Section titled “Spain — SIGN ES (Specialized API)”Estimated effort: 1-2 weeks
- Week 1 — Sandbox setup, TicketBAI, Verifactu or SII flow, digital receipt
- Week 2 — Production go-live
Prerequisites: HUB account
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.