Mapping VAT Codes, Units and Currencies Between Systems — Odoo & ERP article by Rui Codex

Map VAT codes, units and currencies by building an explicit crosswalk table for each field, agreeing one meaning per source value, and recording the rule that converts each value into the target system. Keep tax treatment, unit conversion and rate sources separate, test with real edge cases, and review the mapping whenever either system changes its configuration.

Key takeaways

  • VAT codes must be mapped on their tax meaning, not on their labels.
  • Unit conversions need documented factors and a rule for rounding.
  • Currency conversion should record the rate date and rate source with every amount.
  • Totals should be compared per code and per currency, not only as grand totals.

What needs to be mapped between two business systems?

Three kinds of reference data usually need explicit crosswalks: tax codes, units of measure and currencies. Each looks simple on its own, but each system encodes its own meaning, and the differences appear at invoice time or in month-end reporting.

A mapping is not a rename. When a source system calls a rate 'standard' and the target calls it 'S21', the two only match if they share the same rate, scope and recovery rules. Where they differ, the mapping has to say so explicitly.

Integration projects often start with a spreadsheet of codes that someone exports from each system and matches by eye. That works for a short list, but it hides assumptions. A written crosswalk with a column for the rule behind each match is easier to review, test and change later.

How do you map VAT codes without losing tax meaning?

Map each source code to the target code that applies the same treatment in the same situations. Compare rate, scope, exemption reason, reverse-charge flag and the transaction types each code may be used for, not just the displayed name.

The VAT Directive, Council Directive 2006/112/EC, sets the common framework that member states implement, and the rates and exemptions behind your codes come from national law built on it. This article is general information and not legal or tax advice. Read the consolidated text of Directive 2006/112/EC on EUR-Lex to check the framework your codes rely on.

Build the crosswalk in four steps

  1. Export every tax code in use, including inactive codes that still appear on old invoices.
  2. Write down the meaning of each code in plain language, with its rate, scope and conditions.
  3. Match each source code to one target code, or to several target codes with a stated selection rule.
  4. Mark every code with no match as an open exception that needs a decision from the finance owner.
Tip: Do not finish a crosswalk by mapping unmatched codes to a generic default. A default hides the decision that someone should have made.

Teams that build this kind of mapping as part of a wider ERP and CRM integration usually keep the crosswalk in version-controlled configuration, so changes to tax codes leave a traceable history.

How should units of measure be mapped?

Map units only when you have a conversion factor that both sides agree on. A unit that is a count in one system and a weight in another cannot be mapped by name alone, because the conversion depends on the product.

Standard unit vocabularies help. The UN/CEFACT Recommendation 20 unit codes give you a neutral set of identifiers to map onto, but they do not tell you how many pieces fit in a case or how a pallet is counted. Those facts come from your product master data and must be checked product by product.

Common failure points include packaging units that change between suppliers, decimal places that were rounded in one system and not the other, and units used for pricing that differ from units used for stock. Record the factor, the source of the factor and the rounding rule for each conversion.

Tip: Store the original unit alongside the converted quantity. When a quantity looks wrong later, you can see which conversion produced it.

How should currencies and exchange rates be handled?

Keep each amount in its transaction currency and convert only where a report requires it. Currency codes should follow the three-letter identifiers defined in ISO 4217, which makes the mapping a lookup rather than a guess.

The harder question is where the conversion happens. Converting in the source system keeps the target simple but hides the rate used. Converting in the target keeps the original currency intact but requires both systems to agree on the rate source and timing.

Store the rate date, the rate source and the rounding method with each converted amount. Without these fields, two reports built from the same transactions can disagree and nobody can explain why.

Hypothetical examples

Here are two hypothetical scenarios:

In the first, a distributor sells the same product in a standard unit in one system and in a case in another. The team mapped the two by name, so every order line was counted with the wrong factor. The error appeared only in stock reconciliation, because invoices were correct. A check on stock movements per unit, run before go-live, would have caught it.

In the second, an online shop sends invoices in a foreign currency to a finance system that converts them at month end. Credit notes issued in the following month were converted at a different rate, so the net amounts per currency did not match the source ledger. Storing the rate date with each document would have made the mismatch visible at once.

When do mappings fail, and how do you limit the damage?

Mappings fail most often where the business has rules that the source system never wrote down. A tax treatment that depends on a customer's registration, or a unit that depends on the buyer, cannot be captured in a one-to-one table.

The trade-off is between precision and maintenance. A detailed mapping with conditions catches more cases but needs an owner who updates it when tax codes or products change. A simple mapping is easier to keep current but pushes exceptions into manual work.

Limit the damage with three controls: reconcile totals per code and per currency after each batch, log every unmatched or manually overridden value, and re-run the test sample after each configuration change. Rui Codex builds these reconciliation checks as part of its system integration services, and API integration articles on the Rui Codex blog cover the wider data flow.

Frequently Asked Questions

Can one VAT code map to several codes in the target system?

Yes, one source code often maps to several target codes when the target system distinguishes cases the source does not. For example, a single domestic rate in the source may need separate target codes for sales, purchases and reverse-charge transactions. Record the condition that decides which target code applies, such as customer country or product type, so the choice is repeatable and auditable.

Should currency conversion happen in the source system or the target system?

Decide this once per data flow and document it. Converting in the source keeps the target simpler but hides the rate used, while converting in the target keeps the transaction currency intact and lets the rate source be audited. Whichever you choose, store the rate date and rate source alongside every converted amount.

How do you test a mapping before going live?

Test with a sample of real transactions that includes edge cases: zero-rated items, credit notes, foreign-currency invoices and products sold in more than one unit. Compare totals per tax code and per currency between systems, not only grand totals, because offsetting differences can hide errors. Repeat the test after every configuration change.

Does a mapping table make a system compliant with tax rules?

No. A mapping table only carries decisions you have already made into the other system. Confirming the tax treatment is the job of your accountant or tax adviser, while Rui Codex provides technical implementation support for the mapping itself.

Conclusion

Mapping VAT codes, units and currencies works best when each crosswalk records its meaning, its rule and its owner. Start with the tax codes, since they carry the most risk, then move to units and currencies with the same discipline. Test with edge cases before go-live and reconcile after every change. If you are planning a data flow between two systems and want a second engineering view, request a project consultation with Rui Codex or email info@ruicodex.com to discuss your project.

Sources

Tags: VAT codes unit of measure mapping currency conversion system integration data mapping API integration ERP integration data reconciliation

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request