FatturaElettronica APP API integration (FatturaPA / SDI / OpenData)

1. Account login & tenant binding

Mirror the in-app authorization handshake so a SaaS, ERP, or accountant dashboard can act on behalf of a single VAT number or a portfolio of clients. We deliver an OAuth-style token broker, refresh-token rotation, multi-tenant scoping, and a hardened logout/revoke path. Useful when accountants ("commercialisti") onboard 50–500 client accounts in a single console.

2. Issued invoice (Fatture emesse) export API

Page through every invoice issued from the app: header, line items, IVA breakdowns, recipient code, transmission progressive number, and the final SDI identifier. Filter by date range, customer VAT, document type (TD01, TD02, TD06, TD24, TD29) or status. Output is JSON, CSV, or original FatturaPA XML — whichever the consuming system prefers.

3. Received invoice (Fatture ricevute) sync

Continuously fetch the inbound side — supplier invoices delivered through SDI to the user's recipient code — for automated AP posting, three-way match, and VAT register generation. Deduplicates by SDI identifier and exposes the original signed XML so downstream OCR or reconciliation logic stays trustworthy.

4. SDI status webhooks

Stream the SDI lifecycle (delivery receipt, customer acceptance, refusal, expiry, missed delivery to PA) into your own queue. We provide retry semantics, signature verification, and an idempotent event store so a single network blip does not desync the audit trail.

5. Customer/supplier registry export

Pull the in-app anagrafica clienti/fornitori — VAT, codice fiscale, recipient code, PEC address, billing addresses — and keep it aligned with your CRM or ERP master data. Includes a delta endpoint so daily syncs only transfer changed rows.

6. Conservazione (10-year archive) bridge

Mirror the legally compliant 10-year preservation receipts and signed packages out of the app into your document management system. Ideal for groups that already operate their own conservatore accreditato but want a unified vault.

A. Accounting firm portfolio dashboard

An Italian commercialista manages 250 client VAT numbers, several of which use FatturaElettronica APP. Business context: the firm needs a single ledger view to prepare quarterly LIPE submissions and the new pre-filled VAT return. We expose the issued/received XML stream per tenant and feed it into the firm's gestionale. The OpenData mapping is straightforward: Fatture emesse → registro IVA vendite, Fatture ricevute → registro IVA acquisti, with TD29 entries flagged for follow-up.

B. ERP synchronisation for SMEs

A mid-sized retailer uses FatturaElettronica APP for outbound invoicing and an external ERP (e.g. Odoo, Dynamics 365, SAP B1) for everything else. We build a bidirectional bridge: orders trigger invoice creation through the integration API, and SDI confirmation events feed back into the ERP's payment-tracking module. Field-level mapping covers CedentePrestatore, CessionarioCommittente, DatiGenerali, and DatiBeniServizi.

C. Open Banking reconciliation

A fintech under PSD2 already pulls bank transactions for SME customers. By layering FatturaElettronica APP integration on top, the fintech matches each bank entry to the underlying issued or received invoice, computes outstanding receivables, and offers invoice-financing pre-approvals. The OpenFinance angle: invoice ledger + account information service = a richer credit signal than either alone.

D. Compliance and tax-authority reporting

Larger groups need to feed the same FatturaPA XML into both the SDI and internal compliance systems. We deliver a thin API that emits canonical XML, the SDI progressive number, and the receipt timestamps so the firm's tax, internal audit, and ESG reporting modules all consume one source of truth — including the new TD29 omitted/irregular invoice flow that shifts liability onto the buyer.

E. Cross-border B2B reporting (post-2027 readiness)

The EU has granted Italy the SDI derogation until 31 December 2027, and ViDA / EN 16931 alignment will move cross-border B2B onto a similar rail. We architect the integration with that future in mind: a clean separation between the FatturaElettronica APP adapter and a generic EN 16931 canonical model, so tomorrow's cross-border invoices flow through the same pipeline with minimal rework.

Authentication & tenant binding

POST /api/v1/fattura-app/auth/login
Content-Type: application/json

{
  "username": "studio.rossi@example.it",
  "password": "<REDACTED>",
  "tenant_vat": "IT01234567890"
}

Response 200:
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8c1e...",
  "expires_in": 3600,
  "tenant": {
    "vat": "IT01234567890",
    "codice_destinatario": "ABCDE12",
    "regime_fiscale": "RF19"
  }
}

Issued invoice statement query

POST /api/v1/fattura-app/invoices/issued
Authorization: Bearer <ACCESS_TOKEN>

{
  "from": "2026-01-01",
  "to":   "2026-03-31",
  "doc_types": ["TD01","TD24","TD29"],
  "status":    ["delivered","accepted"],
  "format":    "fatturapa_xml",
  "page":      1,
  "page_size": 100
}

Response 200:
{
  "items": [
    {
      "sdi_id": "1234567890",
      "progressivo_invio": "00042",
      "doc_type": "TD01",
      "issue_date": "2026-02-14",
      "customer_vat": "IT09876543210",
      "total_amount": 1830.00,
      "vat_amount":   330.00,
      "xml_url": "https://api.example/.../inv_42.xml"
    }
  ],
  "page": 1, "total": 187
}

SDI status webhook

POST  https://your-app.example/webhooks/sdi
X-Signature: sha256=...
Content-Type: application/json

{
  "event": "sdi.notification",
  "sdi_id": "1234567890",
  "type":   "RC",   // RC, NS, MC, NE, DT
  "occurred_at": "2026-04-02T08:14:55Z",
  "payload_xml_url": "https://api.example/.../msg_RC_42.xml"
}

// Acknowledge with HTTP 200; non-2xx triggers
// exponential retry up to 24h, then dead-letter.

What we deliver

• OpenAPI / Swagger specification for every endpoint
• Protocol & auth flow report (token broker, refresh, revoke)
• Runnable source for login + invoice statement APIs (Python, Node.js, or Go)
• FatturaPA XSD validation harness and golden-file regression tests
• Compliance pack: GDPR data-flow map, retention schedule, SDI alignment notes
• Optional hosted gateway with pay-per-call billing

Engagement workflow

1. Scope confirmation: target tenants, document types, SDI events.
2. Protocol analysis and API design (2–5 business days).
3. Build and internal validation against FatturaPA 1.9.1 (3–8 business days).
4. Docs, sample clients, and acceptance test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; production cutover scheduled with the client.

About us

We are an independent technical studio specialising in App interface integration and authorized API integration. Our engineers come from fintech, e-invoicing service providers, and EU compliance backgrounds, and we have shipped FatturaPA, PEPPOL BIS, and EN 16931 pipelines for accounting platforms, ERP integrators, and embedded-finance startups across Italy and the wider EU.

• E-invoicing, OpenFinance, Open Banking, and ERP / accounting integrations
• Custom Python, Node.js, and Go SDKs with reproducible test harnesses
• Full pipeline: protocol analysis → build → validation → compliance review
• Source-code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted gateway and pay only per call, no upfront cost

Contact

For quotes or to submit your target app and requirements (sandbox accounts, SDI accreditation status, expected call volume), open our contact page:

Contact page

NDAs available on request. We sign a Data Processing Agreement (DPA) compatible with GDPR Art. 28 before any production data is touched.

FAQ

What do you need from me to start?

How long does delivery take?

Is the integration compliant?

Do you also build the receiving/issuing side toward SDI directly?

Long-tail topics we cover

• FatturaElettronica APP transaction export OpenBanking
• FatturaPA XML statement API integration
• Sistema di Interscambio webhook integration service
• Italian e-invoicing OpenData ERP sync
• TD29 omitted invoice reporting automation
• Conservazione sostitutiva 10-year archive bridge