Language:
Start Serverless STFL Preise Defence 🏰
Zugang anfragen →
Sovereign Transaction Finance Layer Forensic Infrastructure

A compliance event is a billing event. A receipt is a booking document. A Merkle chain is an audit trail. This is not a feature combination — it is an ontological statement about what a regulated financial event actually is.

€0
Market intersection until now
€20B
Addressable market Europe
<2s
Invoice in recipient ERP
302%
ROI YEAR 1
HOW IT WORKS

From Receipt to Ledger. In Real Time.

1
Receipt erstellt
HMAC-SHA256
2
Automation Trigger
Sofort · 0ms
3
ReceiptLedgerEntry
append-only · WORM
4
Invoice Matching
XRechnung · Peppol
5
Audit Export
GoBD · CSV · DATEV
Append-only
delete: false
Tenant-linked
Multi-Tenant
Timestamped
ISO 8601
Product code
IGE-5 · MAD-1
Net & Gross
19% MwSt.
Billed flag
false → true
RECEIPT_LEDGER_ENTRY.json
{   "ledger_id": "BLG-20260626-00042",   "receipt_id": "RPE-SHA256:79505C823",   "product_code": "IGE-5",   "price_net": 75.00,  "price_gross": 89.25,   "entity_name": "Deutsche Bank AG",   "executed_at": "2026-06-26T14:32:00Z",   "billed": false,  "hmac": "sha256:2c44bfd3..." }
The compliance event becomes the accounting event · Cryptographically bound · Forensically immutable
ARCHITECTURE

Same data foundation. Same Merkle chain. Two perspectives.

The two infrastructures share the same append-only ledger — they are not integrated, they are the same object viewed from two perspectives.

INFRASTRUCTURE 1 — COMPLIANCE ENGINE
Rechtskonformer Nachweis
GLEIF · AML · Sanctions (14 Listen)
Gate 0 · Constitutional Layer
HMAC-SHA256 · Merkle-Chain · WORM
RDR · Portable RDR · Chained Reliance
evidentiary_grade: true · expires_never: true
INFRASTRUCTURE 2 — FORENSIC BILLING ENGINE
Steuerrechtlicher Buchungsbeleg
XRechnung 3.0 · EN 16931 · Peppol AS4
ZUGFeRD PDF/A-3 · GoBD §146 AO
Reverse Charge §13b UStG
SKR03 · ReceiptLedgerEntry · append-only
gobd_compliant: true · delete: false
Bound by the same Merkle chain · same HMAC-SHA256 signature · same append-only ledger
MARKET GAP

Why no one else sits in this intersection.

Anyone who starts the other way around — billing first, compliance as an add-on — never achieves the forensic depth. The order of operations is the moat.

KATEGORIE COMPLIANCE ENGINE BILLING ENGINE FORENSISCH VERBUNDEN
RegTech (ComplyAdvantage, Regnology, WorldCheck) ✓ ✗ ✗
FinTech / Billing (Stripe, Billie, Candis, Bilendo) ✗ ✓ ✗
ERP (SAP, Oracle, DATEV, Dynamics) ✗ ✓ ✗
immo.quick FORENSIC INFRASTRUCTURE ✓ ✓ ✓
EXTERNAL PRODUCTS

Three products. One cryptographic foundation.

PRODUKT A · Compliance-triggered Invoice
Invoice is created with the receipt.
Every compliance check automatically triggers the invoice. XRechnung in the client's SAP — in the same millisecond window in which the AML receipt is signed. No human touches anything. No email. No manual invoice.
EXAMPLE
Estate agent checks GwG compliance for buyer. Receipt: CLEAR. → Immediately: XRechnung for due diligence, GoBD-archived, via DATEV export to tax advisor, with HMAC hash of GwG receipt as documentary proof.
PRODUKT B · Transactional Billing Engine
Alle Parteien. Gleichzeitig. Merkle-gekettet.
M&A receipt on CLEAR_TO_PROCEED: the engine identifies all parties (PE Buyer, Target, Notary, Law Firm) and simultaneously issues correct invoices to all — bound in a Merkle chain with the M&A receipt. No coordination chaos.
EXAMPLE
PE fund acquires mid-market company, €45M deal. MDD receipt: CLEAR_TO_PROCEED. → Immediately: invoice PE fund (On request), invoice target (€320), invoice law firm (€450). All three Merkle-chained. All Peppol-delivered.
PRODUKT C · Forensic Billing API
Ein API-Call. Fertig.
Tech partners and enterprise call the engine directly. POST with compliance_event_id and parties → response: validated XRechnung, HMAC-signed, GoBD-archived, Peppol-delivered. In under 2 seconds.
POST /api/v1/stfl/generate-invoice
→ invoice_id: INV-2026-06-000042
→ hmac: sha256:a1b2c3...
→ delivery_status: peppol_delivered
→ latency: <2000ms
DELIVERY MODES

Four paths to the recipient. No manual step.

Peppol AS4
The European SWIFT for invoices. Directly into the recipient's SAP/Oracle/Dynamics. Receipt confirmation in cockpit. No human opens an email. Dark processing.
B2G Pflicht ab 2025
ZUGFeRD PDF/A-3
PDF with embedded EN 16931 XML. Humans read the PDF. DATEV automatically extracts all booking data from the XML. Only an email address needed.
No setup at recipient
XML API-Push
Synchronous POST to client ERP endpoint. 200 OK = document in ERP database. Done. No email. No Peppol network needed.
30 Min. Konfiguration
DATEV / SKR03-Export
Monthly SKR03-compliant booking dataset directly to tax advisor. Already categorised. With compliance reference. No year-end chaos.
For German SMEs
ONBOARDING

Under 2 hours. No IT project.

01
Tenant-Profil anlegen
30 Minuten
Choose delivery route (Peppol/ZUGFeRD/XML/DATEV). VAT number, company name, address. BT-10 routing ID or email. ISO country code — Reverse Charge detected automatically.
02
Trigger-Events definieren
1 Stunde
Which compliance events should trigger invoices? GLEIF check? AML clearance? M&A receipt? All? Which amount per event? Which parties should be invoiced?
03
Erste Testrechnung
15 Minuten
Run one compliance check. Invoice appears automatically in delivery log. For Peppol: receipt confirmation in cockpit. Done. The engine now runs forever.
ROI ANALYSIS

302% ROI. 4 months payback.

EXAMPLE — REGIONAL BANK · 500 AML CHECKS/MONTH
€145.000
Annual saving
€130k FTE + €15k error costs
€48.000
STFL cost / year
€8 × 500 × 12 months
302%
ROI Year 1
Net €97,000 gain in year one
4 months
Payback period
After that: pure gain
M&A advisor (12 deals/year): €350,000 early liquidity through immediate invoicing · €11,400 STFL costs. ROI not quantifiable.
MARKET SIZE

€20B addressable market. Intersection until now: €0.

~€8B
REGTECH MARKET EUROPE
ComplyAdvantage · Regnology · LSEG WorldCheck · Refinitiv
~€12B
B2B E-INVOICING MARKET EUROPE
Peppol · XRechnung · ZUGFeRD · SAP · Oracle · DATEV
Intersection until now: €0 — because no one has served both. immo.quick is the first Forensic Infrastructure.
MOAT — WHY NO ONE REPLICATES THIS QUICKLY
Technisch
HMAC binding between receipt and booking document runs through the entire data model. Replication: 3–5 years, €10–30M.
Regulatorisch
XRechnung 3.0, EN 16931, Peppol BIS 3.0, GoBD §146, §257 HGB — years of legal work as executable code.
Netzwerk
Every Peppol partner is a network node. Metcalfe's law: value grows quadratically with number of participants.
Lock-in
Anyone who has switched to automatic invoice generation never returns to manual. Value lock-in, not technical.
Daten
After 2 years: the only database corpus in the world correlating compliance events with transaction values. Not catchable.
SCP-1.0 ON INVOICES

Our invoice to you is the same artifact.

No other compliance provider in the world can say this: our invoice to you is itself a cryptographically verifiable artifact — with the same evidentiary force as the compliance proof we generate for you.

INVOICE_ARTIFACT.json — SCP-1.0
Invoice RPE-XXX-20240315-000042
  "hmac_sha256": "3f8a9c2d..."
  "merkle_link": "SHA256(payload_hash:prev_invoice_hash) = a71b2d..."
  "valid_time": "2024-03-15"  ← invoice date
  "transaction_time": "2024-03-15T14:32:07Z"  ← issuance timestamp
  "xml_validated": true  ← EN 16931 Schematron
  "archive_uri": "private://invoices/2024/03/RPE-000042.pdf"
  "gobd_compliant": true  ← Sec. 146 AO / 257 HGB / 10 years
  "delete": false  ← append-only / tamper-proof
What this means: Every invoice is Merkle-chained. An auditor can retrieve any invoice in 10 years — with cryptographic proof it has not been altered since dispatch. SAP cannot do this. DATEV cannot. Lexoffice cannot.
ENTERPRISE MAPPING · BT-10 / BT-12 / BT-24

The difference between 2 seconds and 3 weeks.

Without these three fields, every invoice gets stuck in a manual SAP approval workflow. Set once — automatic forever.

BT-10
Buyer Reference / Leitweg-ID
Mandatory for all B2G invoices. Without this ID: invoice goes to manual review workflow. Weeks of delay. Required for SAP Ariba, Tradeshift, Coupa.
BT-12
Contract Reference
The framework contract number. Enables automatic cost centre assignment in ERP. Applied to every monthly invoice automatically.
BT-24
Purchase Order Reference
Standard PO number for automatic ERP processing. Without PO: manual order matching required in client SAP. Automatic payment impossible.
OHNE STFL
Manual process · SAP queries · 3-week approval workflow · payment delay
MIT STFL + BT-10/12/24
Configured once · automatically matched · booked · paid · in 2 seconds
FINANCE LAYER — NOT A BILLING MODULE

The term is deliberately chosen.

A billing module is a feature of an application. A finance layer is an infrastructure layer. The difference is not semantic — it is architectural.

BILLING MODULE
FINANCE LAYER — STFL
Belongs to an application
Independent of the product
Can be switched off
Structurally necessary
Generates invoices
Generates cryptographically bound financial artifacts
Accountant reviews
Schematron validates (EN 16931)
Archives optionally
Archives mandatorily (GoBD Sec. 146 AO)
No cryptographic chain
Merkle chain across all invoices
SAP · DATEV · Lexoffice
immo.quick STFL
DER BEWEIS-DER-KONZEPT-EFFEKT
If immo.quick issues its own invoices in XRechnung 3.0 and Merkle-chains them — it can do the same for mine. That is institutional credibility through lived architecture.
No provider in the world can say:
»Our compliance clearance and our invoice are the same cryptographic object.«
immo.quick can say that.
That is the difference between a tool and an infrastructure.
STFL anfragen →