Most international ERP platforms are built around IFRS or US GAAP. When deployed in Vietnam without proper localisation, they produce financial outputs that fail statutory audits, generate incorrect tax filings, and create reconciliation headaches that drain finance teams for months. The fix is not a workaround patch -- it requires understanding exactly where VAS diverges from global standards and configuring your chart of accounts, tax engine, and reporting modules accordingly before go-live.
TL;DR
VAS uses a mandatory, government-prescribed chart of accounts that global ERP systems do not ship with by default.
Vietnamese books must be maintained in Vietnamese language and Vietnamese Dong (VND), with strict form requirements.
VAS and IFRS differ materially on revenue recognition, asset valuation, and financial instrument treatment.
Both Odoo and SAP Business One can be configured for full VAS compliance, but this requires deliberate localisation work, not default installation.
Vietnam's accounting landscape is evolving: Circular 99 introduces new disclosure requirements that ERP configurations must accommodate.
About the Author
724SOFTWARE is a Vietnam-based technology partner and top 5 Odoo service provider in Vietnam, with hands-on delivery of VAS-compliant ERP implementations across retail, F&B, hospitality, and distribution -- including SAP Business One and Odoo deployments for clients such as TocoToco, Oakwood Residence, and Samsung's largest Vietnam dealer.
Why Does VAS Create So Many Problems for International ERP Systems?
VAS compliance is not just a configuration setting -- it reflects a fundamentally different accounting philosophy. Vietnam's Ministry of Finance prescribes specific account codes, reporting formats, and language requirements that have no direct equivalent in IFRS-oriented platforms.
The core friction points are:
Prescribed chart of accounts: Vietnam mandates a specific numbering system for account codes. Global ERP structures may not align with this prescribed chart, requiring substantial customisation.
Language and currency rules: VAS books must be maintained strictly in Vietnamese and VND. Dual-currency or multi-language setups common in regional ERP deployments can break compliance.
Form-based reporting: Financial statements follow prescribed formats defined by the Ministry of Finance, not the flexible presentation allowed under IFRS.
Tax engine complexity: Vietnam's VAT, foreign contractor tax (FCT), and corporate income tax (CIT) rules interact in ways that standard international tax modules do not anticipate.
Building on these structural gaps, the divergence between VAS and IFRS goes deeper than form. It reaches into how transactions are recognised and measured.
How Does VAS Differ From IFRS in Ways That Actually Break ERP Configurations?
VAS and IFRS share surface-level similarities but diverge significantly in areas that directly affect how transactions post in an ERP.
Area | VAS Approach | IFRS Approach | ERP Impact |
|---|---|---|---|
Revenue recognition | Follows specific VAS rules, generally more conservative | IFRS 15: performance-obligation model | Revenue posting logic and deferred revenue accounts differ |
Fixed asset valuation | Historical cost; revaluation is restricted | Allows revaluation model | Depreciation schedules and asset registers require separate treatment |
Financial instruments | Limited scope; no IFRS 9 equivalent | Full fair-value measurement under IFRS 9 | Investment and derivative accounts need custom mapping |
Consolidation | VAS consolidation standards differ from IFRS 10 | Full control-based consolidation | Group reporting modules require reconfiguration |
Disclosures | Circular 99 has introduced new mandatory disclosures | Extensive but principle-based | Report templates need updating to capture new fields |
Foreign-invested enterprises that attempt to run a single IFRS-oriented ERP configuration for both group reporting and local statutory reporting often face audit risks and difficulties reconciling the two sets of books.
What Specifically Goes Wrong in SAP Business One and Odoo Without Proper VAS Localisation?
Stepping back from the standard comparison, the practical consequences in real deployments are worth naming directly.
In SAP Business One:
The default chart of accounts does not match the Vietnamese prescribed structure. Without remapping, account codes used in trial balances and tax returns will not match what the Ministry of Finance expects.
The tax determination engine requires manual configuration for FCT and the specific VAT treatment of imported services.
Financial report templates, including balance sheet, P&L, and cash flow, need rebuilding to match Ministry of Finance form layouts.
Integration with the e-invoice platform, required under Vietnam's mandatory e-invoicing rules, is not included in the standard SAP B1 package for Vietnam.
In Odoo:
Odoo's Vietnam localisation module exists but covers the basics. Complex scenarios -- multi-branch consolidation, lot/batch-level COGS tracking, dealer promotion accounting -- require custom development.
The Vietnamese chart of accounts module needs validation against the latest Ministry of Finance circulars, since community-maintained localisations can lag regulatory changes.
Payroll modules require configuration for Vietnamese social insurance, health insurance, and PIT withholding, which differ materially from regional defaults.
In the 724SOFTWARE deployment for Taco Service and Trading, TocoToco's 101 F&B stores, SAP B1 required custom configuration of manufacturing modules for semi-finished goods and automated COGS calculation to produce financial reporting aligned to VAS. Similarly, the Oakwood Residence SAP B1 engagement required building VAS-compliant management reports with reliable data mapping from the Suite8 property management system.
How Do You Fix VAS Compliance in Odoo or SAP B1? A Practical Configuration Checklist
A related but distinct question is: once you know where the gaps are, what does the remediation actually look like? Here is a structured approach.
Step 1: Chart of Accounts Alignment
Map every default account code to the VAS-prescribed numbering system.
Remove or reclassify accounts that have no VAS equivalent.
Validate the mapping against the current Ministry of Finance chart before go-live.
Step 2: Tax Engine Configuration
Configure VAT rates, including 0%, 5%, 8%, and 10%, with correct account assignments.
Build FCT logic for payments to foreign entities.
Set up CIT provision accounts and quarterly accrual workflows.
Step 3: Financial Report Templates
Rebuild the balance sheet, income statement, and cash flow statement to match Ministry of Finance prescribed forms.
Incorporate the new disclosure fields introduced by Circular 99.
Step 4: E-Invoice Integration
Connect Odoo or SAP B1 to a certified e-invoice provider via API.
Validate the invoice numbering, digital signature, and XML format against the tax authority's technical specification.
Step 5: Ongoing Compliance Monitoring
Assign an internal owner to track Ministry of Finance circulars and update configurations when rules change.
Schedule an annual review of the chart of accounts and report templates.
Frequently Asked Questions
Q: Does Odoo have a built-in Vietnam localisation?
Yes, Odoo includes a Vietnam localisation module covering the basic chart of accounts and tax configuration. However, it requires validation and additional customisation for complex business scenarios, multi-branch operations, and the latest disclosure requirements under Circular 99.
Q: Can SAP Business One be made fully VAS-compliant?
Yes, but it requires rebuilding the chart of accounts, reconfiguring the tax engine, and creating custom financial report templates. Standard SAP B1 installations do not ship VAS-ready for Vietnam.
Q: What is the risk of running an IFRS configuration in Vietnam?
Foreign-invested enterprises running IFRS-only configurations face audit risks and may be subject to arrears or reconciliation difficulties when local statutory filings do not match VAS requirements.
Q: What is Circular 99 and why does it matter for ERP?
Circular 99 introduced significant changes to the Vietnamese accounting system, focusing particularly on disclosure requirements in financial statements. ERP report templates built before Circular 99 may not capture the required fields, creating compliance gaps in statutory filings.
Q: Is VAS converging with IFRS?
Vietnam has a roadmap for standard convergence, and the gap between VAS and IFRS is narrowing over time. However, full convergence has not occurred, and businesses must maintain VAS-compliant books for statutory purposes regardless of how they report to parent companies.
Q: Should I use Odoo or SAP B1 for VAS compliance in Vietnam?
Both platforms can achieve VAS compliance with proper localisation work. The right choice depends on company size, complexity, and existing ecosystem. SAP B1 suits mid-market companies with complex inventory or multi-entity needs; Odoo offers more flexibility and lower total cost of ownership for growing businesses.
Q: How long does VAS localisation typically take?
Duration depends on business complexity, the number of legal entities, and integration requirements, including e-invoice, payroll, and POS. A focused localisation engagement for a mid-sized business typically spans 4 to 12 weeks, with the timeline scaling based on regulatory scope and system integration complexity.
About 724SOFTWARE
724SOFTWARE is a Vietnam-based technology partner with a 200+ person team, 58% of whom are senior-level engineers, and delivery experience across 10+ countries. As a top 5 Odoo service provider in Vietnam and an experienced SAP Business One implementer, 724SOFTWARE has delivered VAS-compliant ERP configurations for retail chains, F&B groups, hospitality operators, and distribution businesses across Vietnam. The company holds ISO 9001, ISO 27001:2022, and SOC 2 Type II certifications and maintains GDPR compliance, and maintains a 95% client retention rate built on long-term partnership, not one-off project delivery. The team scales from 1 to 50+ pre-vetted engineers in 2 to 4 weeks, enabling rapid deployment of dedicated delivery squads for localisation, configuration, and ongoing support without sacrificing quality.
Getting VAS compliance right in Odoo or SAP B1 is a solvable problem but it requires a partner who has done it before in real Vietnamese business environments, not one who is learning the regulatory landscape on your budget.
If you are planning an ERP implementation or fixing a non-compliant configuration, reach out to the team at https://724software.com.vn to discuss a structured localisation approach built around your specific business requirements.
