SVDP Versions 1.2 vs 1.3 is the technical comparison that every Malaysian business currently preparing retroactive MyInvois submissions under the Special Voluntary Disclosure Programme must understand because submitting historical invoices in the wrong SVDP schema version causes immediate MyInvois validation rejection, restarting the preparation cycle and potentially delaying compliance within LHDN’s SVDP disclosure window. Understanding SVDP Versions 1.2 vs 1.3 at the format and field level enables finance teams and ERP administrators to confirm their systems are generating correct-version structured invoices before beginning bulk SVDP submission. The Advintek Malaysia e-invoicing portal provides SVDP Versions 1.2 vs 1.3 implementation advisory and MyInvois compliance support for businesses across all ERP environments.
Overview of SVDP Versions 1.2 and 1.3
What Are SVDP Schema Versions?
SVDP Versions 1.2 vs 1.3 refers to the successive revisions of LHDN’s MyInvois PINT (Peppol International) schema specification for Malaysian e-invoices under the SVDP programme. Each SVDP version number identifies a specific schema release a defined set of mandatory and optional invoice fields, data types, code lists, and validation rules that structured invoices submitted through MyInvois must conform to. In the SVDP Versions 1.2 vs 1.3 comparison, Version 1.2 was the preceding production schema; Version 1.3 is the current mandatory schema that all MyInvois submissions including SVDP retroactive submissions must now use. Businesses using Zoho Books Implementation Malaysia with MyInvois certification should confirm which SVDP version their integration generates to ensure current-version compliance.
Why Schema Versions Matter for SVDP
The SVDP Versions 1.2 vs 1.3 distinction matters for SVDP submissions specifically because retroactive invoice preparation where businesses recreate historical invoices to submit under the SVDP disclosure programme must use the current schema version rather than the version in use at the time of the original transaction. This means a business submitting invoices originally generated in 2024 under SVDP in 2026 must prepare those retroactive invoices in SVDP Version 1.3 format even though Version 1.2 was the applicable standard when the transactions occurred.
Key Changes Introduced in SVDP Version 1.3
New Mandatory Fields in Version 1.3
The SVDP Versions 1.2 vs 1.3 comparison reveals several categories of change in Version 1.3. The most significant are new mandatory fields that Version 1.2 treated as optional or conditional field additions that LHDN introduced to strengthen tax reporting completeness and reduce ambiguity in invoice data interpretation. Businesses preparing SVDP retroactive invoices must confirm that every new Version 1.3 mandatory field is populated in their invoice generation output missing any new mandatory field causes MyInvois validation failure at the schema level.
Updated Code Lists and Enumeration Changes
SVDP Versions 1.2 vs 1.3 also introduces changes to enumeration code lists the defined sets of acceptable values for specific invoice fields such as tax category codes, payment means codes, and unit of measure codes. Version 1.3 code list updates may deprecate code values that Version 1.2 accepted and add new code values for transaction types not previously covered. Businesses whose accounting software populates invoice code fields from internally maintained lists must update those lists to reflect SVDP Versions 1.2 vs 1.3 code list changes before generating SVDP retroactive invoices. Platforms such as Oracle Opera PMS Implementation Malaysia with MyInvois integration should receive vendor-issued updates confirming Version 1.3 code list compliance.
Structural XML Changes
Beyond field-level additions, SVDP voluntary disclosure includes structural XML changes modifications to element nesting, namespace declarations, or CustomizationID values that identify the document as conforming to the Version 1.3 schema. Accounting software that generates SVDP invoices by populating a fixed XML template must update that template to the Version 1.3 structure. A correctly populated Version 1.2 template with Version 1.3 field values but a Version 1.2 CustomizationID will still fail MyInvois schema validation because the CustomizationID signals which version the validator applies.
Comparing SVDP 1.2 vs 1.3 for Malaysia e-Invoicing
Field-by-Field Comparison Approach
The most reliable SVDP voluntary disclosure comparison method is a systematic field-by-field review of LHDN’s published schema documentation for both versions mapping every Version 1.2 field to its Version 1.3 equivalent, identifying new Version 1.3 mandatory fields with no Version 1.2 predecessor, and confirming deprecated field handling. LHDN publishes the official SVDP voluntary disclosure schema documentation through the MyInvois developer portal. Businesses should use the official documentation as the authoritative source rather than relying on third-party summaries that may be incomplete or outdated.
Using the MyInvois Validator for Version Confirmation
The most practical SVDP voluntary disclosure compliance check is submitting a sample structured invoice through the MyInvois sandbox validation environment and reviewing the validation response. A Version 1.3-compliant invoice passes schema validation and returns no schema-level errors; a Version 1.2 invoice submitted after LHDN’s Version 1.3 effective date returns schema validation failures identifying the specific version mismatch. The Oracle NetSuite Accounting Software Malaysia MyInvois integration includes sandbox validation tooling that supports SVDP voluntary disclosure compatibility testing before SVDP batch submission.
How the New Format Affects Businesses
Impact on Retroactive SVDP Invoice Preparation
The SVDP voluntary disclosure change creates a specific challenge for businesses preparing SVDP retroactive invoice batches historical transaction records captured in Version 1.2 field structures must be mapped to Version 1.3 mandatory fields before retroactive structured invoices can be generated. For businesses with large SVDP disclosure volumes, this field mapping exercise must be completed and validated before batch invoice generation begins. SVDP voluntary disclosure mapping errors discovered mid-batch require restarting invoice preparation from the mapping correction point, adding significant time pressure in businesses with tight SVDP disclosure windows.
Impact on Live Invoice Generation
Beyond SVDP retroactive preparation, SVDP voluntary disclosure affects ongoing live invoice generation for all Malaysian businesses with MyInvois integration since Version 1.3 is now the required production schema for all new invoices as well as SVDP submissions. Businesses that have not yet confirmed their accounting or ERP software generates Version 1.3-compliant invoices may be producing live invoices that currently pass MyInvois validation under a transition grace period but will fail when LHDN enforces Version 1.3 as the sole accepted production schema.
Preparing Your Systems for the Latest SVDP Version
ERP and Accounting Software Version Confirmation
Preparing for SVDP voluntary disclosure compliance begins with confirming which schema version your accounting or ERP software currently generates. Contact your software vendor or implementation partner to confirm current schema version output and request the Version 1.3 update timeline if Version 1.3 is not yet deployed. For businesses managing their own ERP invoice generation configurations, review LHDN’s official SVDP voluntary disclosure schema documentation and update all template files, code mapping tables, and CustomizationID references to the Version 1.3 specification. Advintek’s Singapore e-Invoicing compliance work documented through Singapore E-Invoicing Compliance 2026 demonstrates the structured version migration approach applicable to Malaysia’s SVDP voluntary disclosure transition.
Testing Before Production SVDP Submission
Before submitting any SVDP retroactive invoices to MyInvois production, validate a representative sample against the MyInvois sandbox covering every invoice type included in the SVDP disclosure batch. SVDP voluntary disclosure sandbox testing should specifically include: invoices with each tax category code used in the disclosure batch; invoices with each payment means code represented; and any invoice type that had field structure differences between Version 1.2 and Version 1.3. A clean sandbox validation result for all tested invoice types before production submission is the most reliable SVDP voluntary disclosure compliance confirmation available.
Best Practices for Staying LHDN Compliant
Subscribe to LHDN Schema Update Notifications
SVDP voluntary disclosure will not be the last schema version update Malaysian businesses navigate LHDN continues to refine the MyInvois PINT schema as the mandate matures and new transaction type coverage is added. Subscribing to LHDN’s official MyInvois developer update communications ensures finance teams and ERP administrators receive advance notice of upcoming schema version changes before they affect live invoice generation. Businesses that monitor SVDP voluntary disclosure and subsequent version announcements proactively can plan accounting software updates before LHDN’s version effective dates rather than reacting to live validation failures.
Maintain Schema Version Documentation
Document which SVDP version each accounting software release generates and maintain a version history log capturing the schema version in use for each production invoice batch and SVDP submission cohort. This SVDP voluntary disclosure and beyond documentation provides evidence that each submission batch used the correct schema version at the time of submission, supporting audit trail completeness for LHDN compliance assessment. Businesses maintaining structured SVDP voluntary disclosure version documentation are prepared to respond to any future LHDN query about historical submission schema compliance with accurate, documented evidence.
E-invoicing markets that have navigated similar schema version transitions such as the UAE e-invoicing framework accessible through UAE Advintek confirm that businesses that updated their invoice generation systems before the version effective date consistently achieved higher first-pass validation acceptance rates than those relying on grace period extensions. Malaysian businesses should treat the the schema version transition transition as a defined project with a completion deadline, not an indefinite migration window.
Frequently Asked Questions
Q1. What is the difference between SVDP Versions 1.2 and 1.3?
Version 1.3 adds new mandatory fields, updated code lists, and structural XML changes that Version 1.2 did not require.
Q2. Which SVDP version must Malaysian businesses use for SVDP submissions?
All SVDP retroactive submissions must use the current Version 1.3 schema regardless of when the original transactions occurred.
Q3. How can businesses test SVDP Version 1.3 compliance before production submission?
Submit representative sample invoices through the MyInvois sandbox and confirm clean schema validation results before production submission.
Q4. Does the SVDP version change affect live invoice generation as well as SVDP submissions?
Yes — Version 1.3 is the required schema for all new live invoices and all SVDP retroactive submissions from LHDN’s Version 1.3 effective date.
Q5. Where can businesses find the official SVDP voluntary disclosure schema documentation?
LHDN publishes official SVDP schema documentation through the MyInvois developer portal use this as the authoritative source.
Source by:
Image by Gemini
