Live Demo BPVBook a Demo

MIXCONIX is an SAP partner.

ISO 9001:2015ISO/IEC 27001:2022SAP partner
Business Partner Validator
Business Partner Validator · runs on SAP® BTP

clean master databefore the e-invoice is rejected

Business Partner Validator checks your SAP S/4HANA® partner records against EU VIES, IBAN structure, Peppol participant IDs and Leitweg-IDs — before the first e-invoice is handed to SAP® Document and Reporting Compliance.

Book a demoTry the live demo
Deterministic checks
155 rules in 28 groups
Standards covered
EN 16931 · Peppol BIS 3.0 · XRechnung
Runs on
SAP BTP, Cloud Foundry environment, EU region
Availability
Coming to SAP Store
Market context · billentis Market Report 2026

E-invoicing becomes mandatory — and master data becomes a compliance issue.

Europe issues around 26.8 billion B2B invoices a year, 64% of them already electronic. Mandates that have already been announced lift that share to 85% by 2030 — the largest jump of any region. With every new mandate the invoice is validated automatically — by a platform, a network or the recipient — and a master data error becomes a rejected invoice.

Europe: electronic share of B2B invoices

2026, and 2030 in the mandate scenario

Electronic B2B share by region

2026 → 2030, officially announced mandates only

European mandate roadmap 2026–2030

B2B e-invoicing and e-reporting, selection. Germany highlighted; * planned or expected.

2026
  • PLKSeF mandatory, phases from Feb and Apr
  • GRfrom Mar (revenue > €1m), all from Oct
  • FRfrom Sep: receipt for all, issuance for large and mid-sized companies
2027
  • DEfrom Jan: structured EN 16931 e-invoices for revenue > €0.8m
  • HRfrom Jan: small taxpayers, Peppol
  • SKfrom Jan: EN 16931, Peppol BIS
  • PLfrom Jan: final phase
  • NOfrom Jan: B2B issuance*
  • FRfrom Sep: SMEs and micro-enterprises
  • ESfrom Oct: revenue > €8m*
2028
  • DEfrom Jan: all businesses
  • LVfrom Jan: B2B and e-reporting
  • SIfrom Jan: B2B
  • BEe-reporting, Peppol 5-corner*
  • ESfrom Oct: all others*
  • IEfrom Nov: phase 1
2029
  • UKall VAT invoices, B2B and B2G*
  • IEfrom Nov: phase 2
2030
  • EUfrom Jul: ViDA — e-invoicing for intra-EU B2B supplies, no thresholds
  • IEfrom Jul: phase 3
  • SKfrom Jul: cross-border transactions*
  • NOfrom Jan: capability to receive*

“The quality of master data — VAT numbers, tax codes, bank details — becomes critically important, since errors in these fields can cause invoices to be rejected automatically.”

billentis, Market Report 2026, p. 62

That is exactly where BPV works: on the business partners in SAP S/4HANA, before the first e-invoice is created.

See the solution in detail ↓

Source: billentis GmbH, “Riding the Tornado: A Guide to Mastering Multinational E-invoicing and Compliance”, June 2026. Data re-charted by MIXCONIX; billentis is not responsible for this presentation. 2030: mandate scenario, officially announced mandates only. Mandate status as of June 2026.

The problem

Invoices are rejected for data that went wrong months earlier.

SAP Document and Reporting Compliance validates the document it is given. It cannot repair the business partner behind it — and by the time the clearance platform answers, the invoice is already late.

Rejected documents

A wrong VAT ID or a missing Leitweg-ID stops the invoice at the clearance platform, not in your inbox. Nobody in finance finds out the same day.

Mandates, not guidance

EN 16931, Peppol BIS Billing 3.0 and XRechnung are legal requirements. Repeated rejections turn into penalties and receivables that age past terms.

Spreadsheets do not scale

Checking a few hundred partners by hand catches the obvious errors and misses the ones that matter: a valid-looking IBAN registered in the wrong country, a duplicate hiding under a second tax number.

The solution in detail

Where BPV sits — and what it catches before the e-invoice is created.

SAP Document and Reporting Compliance builds the e-invoice from what the business partner record says. If the VAT ID there is invalid or the electronic address is missing, it is not one invoice that fails but every invoice to that partner. BPV checks one step earlier: the master data in SAP S/4HANA, through released APIs.

When the error surfaces

The same faulty partner record, two paths.

Without a prior check

  1. Business partner in SAP S/4HANAVAT ID outdated, Peppol ID missing
  2. The e-invoice is built in SAP Document and Reporting Compliancetakes the master data as it is
  3. Platform, network or recipientvalidates and rejects
  4. Reworkclarify, correct, resend

The error surfaces after sending — and repeats on every invoice to that partner.

With BPV

  1. Business partner in SAP S/4HANAread through API_BUSINESS_PARTNER
  2. BPV on SAP BTP155 rules · EU VIES · OpenIBAN · Peppol Directory
  3. Finding with rule and fieldremediation suggestion, applied by the master data team
  4. The e-invoice is built in SAP Document and Reporting Compliancefrom checked master data

The error surfaces before the first invoice — once per partner record, not once per invoice.

What BPV checks — and where it lands in the e-invoice

Every finding carries the EN 16931 business term the invoice will later be judged against.

Check areaWhat BPV checksField in the e-invoiceWithout the check
VAT IDCountry-specific format, real-time EU VIES lookup, duplicate VAT IDsBT-31VAT identifierRejected by platform or recipient; invoice open to tax challenge
Electronic addressPeppol participant ID in the Peppol Directory, Leitweg-ID (MOD 97-10), GLN (GS1 MOD-10), emailBT-34electronic addressInvoice never reaches the recipient
Name and addressMandatory fields, country-specific postal code format, ISO 3166-1 country codeBT-27name, postal addressValidation errors against EN 16931 or XRechnung
Bank detailsCountry-specific IBAN length, MOD 97-10 checksum, OpenIBAN, BIC/SWIFT formatBT-84IBAN, BT-86BICPayment fails or is delayed; receivable ages past terms
DuplicatesFuzzy matching with AI assistance; the rules engine decides, with a confidence scorewhole partner recordInvoices sent to a duplicate or wrong partner

Three typical uses

Readiness check before the deadline

Check the whole partner base ahead of the 2027 and 2028 mandate dates. billentis recommends starting every e-invoicing initiative with a maturity and gap assessment, data quality included. BPV delivers that assessment for business partners, with a finding per partner.

New and changed partners

Filter by date range and validation status to check the business partners that were created or changed — before the first invoice goes to them.

Ongoing monitoring

A valid VAT ID does not stay valid on its own. Scheduled runs keep the partner base current; findings remain exportable to Excel or PDF as compliance evidence.

What it checks

Six layers of validation, all deterministic.

VAT ID validation

Real-time EU VIES verification for all EU countries, with country-specific format rules (DE, AT, CH, FR, IT, NL, BE, ES, PL, CZ, HU, SK, RO), duplicate VAT detection and Plants Abroad checks.

Electronic address validation

Peppol participant ID verification, German Leitweg-ID with MOD 97-10 check digit across Bundesländer 01–16, GLN with GS1 MOD-10, and email with disposable-domain detection. Mandatory for XRechnung (BT-34).

IBAN and bank data

Country-specific length validation (DE 22, AT 20, CH 21, FR 27, IT 27 characters), MOD 97-10 checksum, OpenIBAN lookup for real bank data, and BIC/SWIFT format validation.

Address completeness

Country, city, street and postal code checked against country-specific formats (DE 5 digits 01001–99998, AT 4 digits, CH 4 digits) and ISO 3166-1 alpha-2 country codes.

Duplicate detection

AI-assisted fuzzy matching through SAP® AI Core, with data quality scoring and correction suggestions. The rules decide; AI assists and can be switched off per tenant.

Batch runs and EN 16931 reporting

Up to 500 business partners per batch with progress tracking, reported against the mapped business terms BT-27, BT-31, BT-34, BT-84 and BT-86, exportable to Excel or PDF.

How it works

Three steps, no development in your core system.

A wizard guides the run: choose the partners, choose the checks, read the findings.

1

Select

Filter business partners by company code, country, category, date range and validation status. Up to 500 partners per batch.

2

Configure

Choose the validation groups — VAT, electronic address, address, IBAN, AI analysis .

3

Validate and review

Read findings by severity (critical, high, medium, low, info) with remediation suggestions, and export to Excel or PDF for the audit file.

Technical specifications

What it is built on.

Framework and runtime

SAP Cloud Application Programming Model (CAP) v9 on Node.js 20+, SAPUI5 1.139+, SAP Fiori.

API and data model

OData V4 in the backend with a V2 adapter for SAP S/4HANA. 155 deterministic rules organised in 28 validation groups.

Deployment

Multitenant SaaS on SAP BTP, Cloud Foundry environment (EU10, US10), with XSUAA and SaaS Registry authentication.

External sources

EU VIES (SOAP) for VAT, OpenIBAN (REST) for bank data, the Peppol Directory, and Cloud Connector for on-premise systems.

SAP integration

API_BUSINESS_PARTNER OData V2 — real-time bidirectional access to SAP S/4HANA master data through released APIs only.

AI integration

SAP AI Core with generative AI hub for duplicate detection and scoring. Personal data is masked before any prompt is sent.

The output

What a validation run returns.

A run does not hand back a pass-or-fail flag. For every business partner it returns the finding, the rule that produced it, and the field to correct — so the person fixing the record does not have to guess.

Per partner

Each check, its verdict, and the source consulted: EU VIES for the VAT ID, MOD 97-10 for the IBAN, the Peppol Directory for the electronic address.

Mapped to the standard

Findings carry their EN 16931 business term — BT-27, BT-31, BT-34, BT-84, BT-86 — so the result reads the same way the e-invoice will be judged.

Duplicates, with a reason

Suspected duplicates come with the matched fields and a confidence score, not a bare pairing. The rules engine decides; AI assists and never gates on its own.

In a form you can hand on

Up to 500 partners per batch with progress tracking, exportable to Excel or PDF for the master data team.

For enterprise IT

A companion to SAP Document and Reporting Compliance, not a replacement.

BPV never modifies, replaces or extends SAP Document and Reporting Compliance or the SAP core. It runs side by side, on your own SAP BTP subaccount.

Isolation and residency

An isolated SAP HANA® Cloud HDI container and a dedicated SAP AI Core resource group per tenant. EU data residency on SAP BTP, Frankfurt.

Nothing in your core is touched

Released SAP APIs only — API_BUSINESS_PARTNER OData. No direct database access, no RFC_READ_TABLE, no ODP, no screen scraping, and no Z* objects in the runtime.

Access and audit

SAP XSUAA (OAuth 2.0) with role-based access and five role templates. Secrets held only in SAP Credential Store; the audit trail goes to SAP Audit Log.

Privacy by construction

Personal data is masked on every AI path. GDPR obligations are addressed in the design: data processing agreement, erasure on request, tenant offboarding.

Its own lifecycle

Side by side on SAP BTP, decoupled from the SAP S/4HANA release train. MTA packaging, semantic versioning, cTMS, runbook and backup/DR.

Cost you can see

AI usage is billed by SAP to your own SAP BTP account — BPV charges nothing for AI, and metering is visible call by call. Bring your own SAP AI Core if you prefer.

Getting started

From subscription to first findings.

1

Subscribe from your subaccount

BPV is subscribed from your own SAP BTP subaccount. Onboarding, upgrades and offboarding are managed for you.

2

Assign the roles

Five role templates ship with the application. Assign them in your identity provider — no development in your core system.

3

Run against real data

Point BPV at a batch of business partners and read the findings.

Questions

What we are asked most.

Does BPV replace SAP Document and Reporting Compliance?

No. SAP Document and Reporting Compliance transmits what your master data contains. BPV checks that data upstream, before the document is created. It never modifies, replaces or extends the SAP solution or the SAP S/4HANA core.

Is the application SAP certified?

Not yet. The SAP Store readiness review is in progress and SAP ICC certification for the Business AI use case is targeted for Q4 2026, against the July 2026 framework, Category 2. Until certification is granted we do not use certification wording in the product or in its published materials.

Where does our data live?

On SAP BTP in the EU, Frankfurt region, in an SAP HANA Cloud container isolated to your tenant. A dedicated SAP AI Core resource group is provisioned per tenant.

What does the AI decide?

Nothing on its own. The rules engine is deterministic and decides; AI assists with fuzzy duplicate matching and scoring, and never gates a result by itself. Personal data is masked on every AI path.

Do we pay extra for the AI?

Not to us. AI usage is billed by SAP directly to your SAP BTP account, and you can see the metering call by call. You may also bring your own SAP AI Core.

Which languages does the interface support?

English and German.

Pricing

Published pricing, per tenant.

One onboarding fee, one subscription, and usage counted per business partner. No user licences, no tiers, no minimum volume.

Setup feeOne-time — onboarding, connection to your landscape, rule-set baseline
€5,000
SubscriptionPer tenant — the application, updates and support
€1,000 / month
Per business partner validatedUsage-based, counted once per validated business partner
€0.10
Per compliance verificationUsage-based, counted per business partner checked against the electronic-invoicing requirements
€0.10

All prices in EUR, excluding VAT. Billed monthly in arrears; the setup fee is invoiced once, at onboarding.

AI cost: billed by SAP directly to your own SAP BTP account — we charge nothing for AI, and the metering is visible call by call.

Standards: validates against EN 16931, XRechnung and Peppol BIS Billing 3.0.

Book a demoComing to SAP Store
See it running

An interactive walkthrough, on sample data.

Six steps: select business partners, run the AI analysis on SAP AI Core, run the deterministic rule engine, review findings, schedule jobs, monitor compliance evidence. No customer system is connected.

Open the interactive demo

Ready to check your business partners?

Book a demo, or open the interactive walkthrough first.

Book a demoTry the demo