warningFINfinvoice

FI-R-002:Finvoice format for Finnish B2B

Finnish domestic B2B may prefer Finvoice format.

Severity
Warning
Rule set
finvoice
Country
FIN
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: Finnish domestic B2B invoices often require Finvoice format instead of UBL/Peppol. This requires generating the invoice in Finvoice XML format from your invoicing software. Contact your software vendor for Finvoice support.

What is FI-R-002?

FI-R-002 is a warning validation rule defined in the finvoice specification (FIN national rules). It validates the Finvoice 3.0 schema compliance element in the UBL invoice XML.

This is a soft validation failure. The invoice may pass initial transmission, but non-compliant values in this field can cause problems during tax audits, buyer-side processing, or downstream VAT reconciliation.

Target path: Finvoice 3.0 schema compliance

This error requires manual correction — financial fields are protected by policy.Get API Access

Why This Error Matters

Finvoice integrates with Finnish banking.

FI-R-002 is a soft failure. The invoice may pass initial validation, but the non-compliant field can cause issues at the receiving end — tax authorities may flag it during audits, buyer ERP systems may fail to process it, or VAT reconciliation may produce mismatches. Fixing warnings before they accumulate prevents larger compliance gaps.

Validator Behavior

  • ·Generates validation warning
  • ·Error returned: FI-R-002
  • ·Specification: finvoice

How to Fix It

1.

Check recipient

Do they prefer Finvoice?

2.

Convert if needed

Transform to Finvoice 3.0

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Triggers validation error -->
<Finvoice 3.0 schema compliance></Finvoice 3.0 schema compliance>
After
<!-- Corrected -->
<Finvoice 3.0 schema compliance>VALID_VALUE</Finvoice 3.0 schema compliance>

Technical Reference

XPathFinvoice 3.0 schema compliance
Specfinvoice

Common Causes

  • ·Using Peppol only
  • ·Bank requires Finvoice

Seeing this in production? The API handles FI-R-002 automatically. See the fix response →

Frequently Asked Questions

Finnish domestic B2B may prefer Finvoice format.

Consider Finvoice format for Finnish bank integration. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

FI-R-002 is a warning that may not always cause rejection, but should be addressed for full compliance.

Related Content

Last updated: 3 March 2026

Share this guide:

Detect FI-R-002 Before Submission

This error involves a financial or legal field that cannot be auto-modified. The compliance engine flags it immediately with a clear diagnosis so your team can fix it at the source.