saascode
finance, accounting & spend·run 143 · Jun 2026

Bordervat

A multi-jurisdiction e-invoicing preparation and evidence workspace for international agencies that validates identity and structured documents, routes them through provider connections, and keeps tax judgment, acceptance, filing, and payment distinct.

Genesis score6.98/10
Make Bordervat real.0/500
500 more votes and Bordervat is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
30+Frameworks cited
2Poland mandate phases cited
2027/28Spain dates cited
The case

International agencies billing customers across the EU and UK face changing structured-invoice mandates, recipient identifiers, network routing, tax treatment, clearance, acknowledgments, corrections, and VAT preparation. Infrastructure providers expose broad connectivity, but an accepted document is not proof that the VAT treatment, return, or payment is correct. Bordervat layers jurisdiction-specific rule packs, pre-submission conformance tests, source-linked change control, human tax review, and end-to-end receipts over provider connections—without replacing the accountant, access point, tax authority, or customer system.

Who pays — and why

The finance controller, billing operations lead, or external accountant for an international agency operating across several invoicing jurisdictions, with tax and legal owners approving local treatment.

What it unlocks
A jurisdiction and counterparty profile that separates legal entity, tax registration, business-identity lookup, invoice format, transport network, clearance, archive, return, and payment obligations
A pre-submission conformance harness that preserves rule source, version, effective date, validation result, reviewer decision, provider submission, authority or recipient acknowledgment, rejection, correction, and resubmission
A VAT-preparation packet that exposes calculations and evidence to a qualified owner instead of presenting automated tax treatment as filing authority
How Genesis scored it
6.98across seven criteria
tension 6temporal 7blindspot 7buyer 7leverage 8convergence 5why-not 7
8
Asymmetric leverage

Rule packs, validation, evidence, routing adapters, and exception workflows can be reused across customers and jurisdictions.

7
Temporal window

Poland's cited 2026 phases and Spain's cited 2027 and 2028 dates create a phased adoption window that requires current revalidation.

5
Convergence

Two cross-references and seven inbound links show adjacency but no supplied cross-vertical cluster.

Why it scored well

Two dated mandate programs, a free identity-validation source, broad commercial network infrastructure, and recurring multi-country agency workflows make the product layer concrete and software-leveraged.

What's holding it back

Convergence is limited, delivery is ULTRA, jurisdictional correctness and tax liability remain expert domains, the proposed customer price is unobserved, and infrastructure providers can move up-stack.

Signals detected5 sources crossed
SignalPeppol mandate research

SignalRoyal Decree implementation research

SignalStorecove product research

SignalEuropean Commission VIES documentation

SignalSource-run pricing review

Direction briefbordervat.md
bordervat.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.