No.

BP-AT-004

Scale

1 : 1

Date

2026-05-25

Rev.

A

Werkstatt 4notify · E-invoicing B2GReleased

Blueprint BP-AT-004 of BP-AT-008 · E-invoicing B2G

EmailWebhook

E-invoicing to the federal government: status notifications via PEPPOL & ebInterface

Received / rejected / paid status updates in the federal procurement flow

§ AThe problem

Many federal suppliers check status manually via USP login — impractical at high invoice volume. When an invoice is rejected (typical reasons: missing VAT-ID, wrong order reference, rounding mismatch on VAT rate), the correction often goes unnoticed, payment slips by weeks and liquidity management suffers. Programmatic notifications — email to accounting, webhook to the ERP, optional SMS to the managing director on rejection — close that gap.

§ BMain view

Since 1 January 2014, suppliers to the Austrian federal government must submit invoices electronically — in ebInterface (ATCC standard) or PEPPOL BIS Billing 3.0 format. Bundesbeschaffung GmbH (BBG) runs the Unternehmensservice-Portal (USP), through which status responses also flow. For companies with significant federal turnover (construction, wholesale, IT services), timely status notifications are critical: a rejected invoice must be corrected before payment terms run out — Bundesimmobiliengesellschaft, for instance, runs a 30-day net term as standard; without automated status notifications, liquidity gaps become a real risk.

§ CParts list

Channel	Primary provider	Fallback
PEPPOL-Eingang	BRZ Access Point	Direct-XML ebInterface upload USP
Statuswebhook	USP Webhook (signiert)	Polling auf USP API (5-Min-Intervall)
E-Mail an Buchhaltung	4notify Mail (DKIM/DMARC)	MS Teams / Slack Konnektor
ERP-Webhook	SAP / BMD / DATEV via 4notify	REST-API Polling
Critical-SMS bei Ablehnung	BP-AT-002 SMS-Routing	Phone call escalation (3rd-party)

§ DTolerances

Status notification on receipt

≤ 5minutes

Status notification on rejection

≤ 10minutes

Payment notification

≤ 30days (standard term)

E-invoice archive retention

7years (UStG § 132)

Webhook replay

30days

§ ENormative references

BBG-Verordnung 2013 (IKT-Konsolidierungsgesetz)

Mandates electronic invoicing for all federal suppliers since 1 January 2014. Paper or PDF invoices are not accepted.

ebInterface 5.0/6.x — ATCC-Standard

Austrian XML standard, maintained by WKO + austriapro. Accepted in parallel to PEPPOL; mostly regional contracting authorities prefer ebInterface.

PEPPOL BIS Billing 3.0

EU-wide standard for cross-border B2G invoices. Signed exchange runs through the PEPPOL network (access points) — Bundesrechenzentrum (BRZ) operates an access point.

UStG § 11 (Umsatzsteuergesetz)

Defines the minimum content of an invoice — VAT-ID, sequential number, VAT rate, VAT amount, service period. Errors here are the most common rejection reason in the BBG portal.

§ FBuild steps

Register a PEPPOL ID at the BRZ access point

Every supplier needs a PEPPOL participant ID (format `0192:VAT-ID` for AT). Registration is a one-time setup via a PEPPOL service provider; the ID is published in the SMP (Service Metadata Publisher) so federal entities can find the supplier.

Validate against Schematron rules before sending

ebInterface and PEPPOL BIS Billing 3.0 each have extensive Schematron rule sets (CIUS-AT profile for PEPPOL). 4notify runs validation before submit — errors are reflected back with ATCC-compliant codes.

Receive and normalise the USP status webhook

USP sends signed status webhooks to a pre-registered endpoint. 4notify receives them, normalises the identifiers (USP-specific codes → canonical ATCC codes), enriches with recipient metadata and fans out to email/ERP webhook/SMS.

Critical path: SMS to managing director on rejection > EUR 10 000

A configurable threshold: above a given invoice amount, a rejection also triggers an SMS to a pre-defined recipient (managing director, head of accounting). So even a EUR 50 000 rejection doesn't sit unread in an email inbox alongside countless other messages.

§ GTest procedure

Test procedure: (1) Upload a test ebInterface XML with an intentional error (wrong VAT-ID) into the USP test environment. (2) Verify the status webhook arrives within 10 minutes. (3) Email to accounting with the rejection reason and correction hint must arrive. (4) For a test invoice > EUR 10 000, an additional SMS to the configured managing-director number must go out. (5) Test the correction and resubmit; the `accepted` status change must come as a second notification — no double SMS, because the threshold only fires on rejections.

§ HCode

bash
curl -X POST https://api.4notify.net/v1/einvoice/dispatch \
  -H "Authorization: Bearer $API_KEY' \
  -H "Content-Type: application/json' \
  -d '{
    "format': 'ebinterface_6_0",
    "recipient_participant_id': '0192:ATU12345678",
    "invoice_id': '2026-AT-04471",
    "amount_total_eur": 18450.00,
    "vat_rate": 20,
    "service_period_from': '2026-04-01",
    "service_period_to': '2026-04-30",
    "buyer_reference': 'BBG-2025-IT-0314",
    "notify": {
      "email': ['[email protected]"],
      "webhook': 'https://example.at/erp/invoice-status",
      "sms_threshold_eur": 10000,
      "sms_recipient': '+436641234567"
    }
  }'

§ ISample message

EmailE-invoice 2026-AT-04471 rejected — reason: VAT-ID missing

E-invoice 2026-AT-04471 for EUR 18,450.00 was rejected by the federal procurement portal. Reason: mandatory field — VAT-ID of recipient — is empty (code CIUS-AT-EN16931-R-007). Please add the VAT-ID and re-submit using the original XML template.

§ JCommissioning checklist

PEPPOL participant ID (0192:VAT-ID) registered with a PEPPOL service provider
Schematron validation against CIUS-AT profile active before every submit
Status webhook endpoint with HMAC signature verification
Multiple recipients per status event (email, ERP, SMS) configured
Critical-path threshold for SMS escalation on rejection set
Archive retention: keep signed XML for 7 years (UStG § 132)

What 4notify does differently

4notify normalises the different response codes from ebInterface and PEPPOL into a unified status flow — one webhook, one vocabulary, regardless of the underlying standard.

§ KFAQ

Does the e-invoicing obligation apply B2B as well?

Not currently. The 2013 BBG regulation only covers B2G (federal suppliers). A B2B e-invoicing mandate is under EU discussion (ViDA initiative); no concrete Austrian implementation date has been announced.

What happens if the PEPPOL access point goes down?

PEPPOL is multilateral — if the BRZ access point fails, a second Austrian access point (e.g. Pagero, Tradeshift, Basware) can be used. 4notify maintains mappings to the three most-used AT access points and falls back automatically.

How does this work with cash-discount terms?

Cash-discount terms are passed structurally in ebInterface under `PaymentConditions` and in PEPPOL BIS under `cbc:PaymentTerms`. 4notify parses them and can send a reminder X days before the discount window closes — useful for receivables management.