Methodology

Rates are served through a snapshot plus caching model. Static-page examples use the reference snapshot dated April 13, 2026, while the live calculator may use a newer runtime snapshot.

The salary tool uses country-level tax, deduction, and insurance rules from dataset 2026.04.19, dated April 19, 2026.

It uses representative regions rather than claiming complete tax-filing coverage.

• Tax outputs are comparison estimates
• Real card fees and customs outcomes can differ
• The EUR zone is represented by Germany and France only

Import-cost estimates use thresholds, representative duty rates, VAT, and special-tax rules to estimate landed cost rather than sticker price alone.

Outputs should be read for direction and budget feel, not as filing or settlement guarantees.

Published and updated timestamps appear in the pages and structured data. They are freshness signals, not promises that every displayed amount is a guaranteed live settlement figure.

The final check still belongs with the real provider documentation.

The calculator is more useful when readers know its trust boundary first. That awareness makes it easier to separate baseline comparison from final provider confirmation.

This is especially important in salary, tax, import, and travel decisions where mistakes have real cost.

• Understand the comparison baseline
• Separate final-confirmation areas
• Reduce overconfidence
• Especially useful in high-cost decisions

Many users want to jump straight to the number. In money-related comparisons, that instinct can create overconfidence because the visible output is only one layer of the real-world result.

The methodology page matters because it explains where the tool is using representative assumptions, where simplification exists, and why some outcomes still require provider-side confirmation.

In practice, that makes the calculator safer to use. The number becomes easier to interpret as a baseline instead of being mistaken for a final filing or settlement value.

• Understand representative rules versus full real-world rules
• Separate static examples from live calculations
• Keep baseline output distinct from final settlement values
• Know where reconfirmation is still required

Users naturally want to jump straight to the result. But the trust boundary of a number depends on the inputs, source dataset, simplification rules, and freshness signal behind it.

The methodology page exists to expose those pieces so that the result is read more responsibly.

• Check the meaning of the inputs
• Check the source dataset
• Understand the simplification rules
• Check the update timestamp

Why does the site sometimes use representative regions only
Because exposing every local rule would make the input flow too heavy. The site prioritizes a comparable baseline over a full filing engine.

Why can a longer methodology page be more helpful
A short statement can say what the tool does, but a longer methodology page explains how far the result can be trusted and where reconfirmation is still needed. That boundary matters in comparison tools.

How often should users revisit the methodology page
It is worth revisiting whenever the comparison becomes important again, especially for larger payments or decisions. Updated assumptions can change how a result should be interpreted.