Kehai - evidence pack

DE · German e-invoicing readiness: fictional case

Item key fictional-demo-de-einvoice · generated 2026-09-05T09:00:00.000Z by Fictional local demo / no live database / no legal verification

Not signed off - review status: ai_generated

1 · The claim

TitleGerman e-invoicing readiness: fictional case
Topiceinvoicing
Dated-
Impact levelhigh
SummaryFictional workflow example: compare how German e-invoicing affects three separate legal entities. The linked BMF guidance is a real reference; no source fetch, legal verification or AI execution is performed in this recording.
Business-specific impactFor this fictional group, check the German entity's invoice workflow, confirm the UK seller's establishment status, and keep the South African entity's separate scope visible. Proposed tasks and dates are illustrative.
Preliminary confidence0 / 100 (recorded advisory score)
First seen2026-09-05T09:00:00.000Z

2 · Official-register grounding

No deterministic official-register identifier (CELEX / ELI / ECLI / CJEU) is attached to this item.

3 · Source evidence — point in time

SourceBMF e-invoicing FAQ (reference only)
Source URLhttps://www.bundesfinanzministerium.de/Content/DE/FAQ/e-rechnung.html
Domainbundesfinanzministerium.de
Source typeauthority
Approved official domainno
Reachability (when last fetched)untested - reachability only; NOT proof the source supports the claim
Source language (as fetched)- not declared by the source
Content fingerprint (change-detection checksum)- no point-in-time snapshot captured
Recorded content length-
Fetched at-
Recorded fetches0

Recorded content length uses the provider's measurement and need not equal the raw response size in bytes.

The content fingerprint is a non-cryptographic checksum recorded when the source material was captured on the fetched-at date. It supports change detection between fetches - a changed source produces a different fingerprint - but it is not a cryptographic hash of the raw fetched bytes and is not, by itself, proof of what the source said. The captured excerpt and the cited authority are what to verify against.

4 · Claim support — human-assessed, separate from reachability

ClaimSupport levelAssessmentAssessed byAt
No per-claim support has been assessed. Claim support is unknown.

5 · Human sign-off lineage

Current review statusai_generated
Reviewed by-
Reviewed at-

No structured impact assessment recorded.

Append-only audit trail (oldest first):

WhenEntityFieldFromToActor
2026-09-05T09:00:00.000Zactioncreated-Demo finance lead (fictional); internal target 2026-09-18; simulated local actionDemo Reviewer (simulated, local fixture only)
2026-09-05T09:00:00.000Zentity assessmentdemo-de reviewStatus (simulated)ai_generatedreviewed (simulated, not a real sign-off)Demo Reviewer (simulated, local fixture only)

6 · Business relevance (org-level)

Verdictaffects
WhySIMULATED LOCAL DATA. Illustrative assessment: this fictional German supplier issues domestic B2B invoices. Confirm the invoice-system requirements against the authority before acting.
Suggested actionMap invoice intake and outbound formats; document gaps for review.
Owner roleDemo finance lead (fictional)
Footprint pre-filterin
Assessed bylocal-demo-fixture (machine-derived)
Review statusai_generated · assessed 2026-09-05T09:00:00.000Z
This verdict is specific to the configured business profile. It is machine-generated and has NOT been human-reviewed.