Dynafis Tax Engine

Resolving conflicting tax data

When invoice, master data, contract and evidence do not describe the same transaction.

Updated: 2026-07-11 Rule version: tax-knowledge-2026.07 Valid from: 2026-07-11
Global B2B businessB2C consumerUnclear GoodsServicesDigital servicesMixed supply

Dynafis must not silently prefer one source when data conflict. Each mismatch carries a code, affected fields, sources and recommended resolution.

Typical conflicts

VAT-ID country differs from entity, delivery address conflicts with movement, contract names another company, invoice and tax currencies differ, or PDF and XML totals do not match.

Evidence priority

Verified originals and confirmed master data may outrank OCR. A human override needs a reason and audit record.

Completion

After correction, extraction, tax decision, validators and exports are recalculated together. Old results remain marked superseded.

Official references

Sources support traceability; national implementation and the individual case still require review.

conflictreviewtax data
Back to Help CenterContact support