The most important boundary is equally clear: electronic invoicing is excluded from the preview. Organizations evaluating the release should treat tax reporting and invoice submission as separate requirements, rather than assume one announcement covers both.
What Argentina localization is expected to include
Microsoft’s Argentina roadmap entry describes three principal areas of planned functionality:
- VAT and provincial sales taxes: tax determination and calculation, imports of taxpayer registers known as padrones, and customer tax-situation certificates.
- Vendor-payment withholding: withholding-tax determination and calculation.
- Regulatory reporting: migration of Argentina tax reports to Electronic Reporting, or ER.
The entry warns that the country-specific scope remains provisional and that not every listed capability will necessarily appear in preview. That distinction matters for implementation planning: an October preview target is not a promise that every report and tax scenario is ready for testing.
Microsoft Learn independently reinforces that caution. Its cross-LATAM overview directs Argentina readers to release plans rather than a completed country overview, and warns that delivery schedules and projected functionality can change.
The planned regulatory-reporting coverage
The roadmap’s reporting list spans national and provincial requirements. These are the named outputs in the planned scope—not a confirmed inventory of available preview features.
| Reporting area | Planned coverage |
|---|---|
| ARCA / IVA Simple | Sales, purchases, imports, other fiscal debit and credit items, withholdings, and perceptions, supporting monthly VAT-operation registration and VAT-return submission through Portal IVA. |
| SICORE | National withholding and perception tax transactions in TXT/Excel files. |
| SIRE (SUSS) | Social-security withholdings, identified as Retenciones de Seguridad Social, in TXT/Excel files. |
| SIFERE | Withholdings, perceptions, bank collections, and customs perceptions in TXT/Excel files. |
| SIRCAR | Gross Income Tax withholdings and perceptions in TXT/Excel files. |
| E-ARCIBA | A Gross Income Tax withholding/tax-collection—or perception—file. |
| ARBA Tax Collection Agents | IIBB perceptions and withholdings in TXT/Excel files. |
The practical distinction is between producing a reporting file and completing an entire regulatory workflow. The roadmap names outputs and, for IVA Simple, the intended Portal IVA process; it does not establish unattended submission across every listed reporting system.
Why the shared framework matters
Microsoft positions Argentina as the final step in this LATAM expansion, describing coverage for 14 countries through the cross-LATAM framework, in addition to Brazil and Mexico. That is the roadmap’s regional framing, not evidence that Argentina has already reached general availability.
Microsoft Learn supplies a useful architectural distinction: cross-LATAM uses a common transaction extension, while countries retain their own reports. Those reports use Electronic Reporting. The overview also explicitly excludes Brazil and Mexico from its scope, so organizations should not assume identical configuration across every regional deployment.
A shared foundation can make regional standardization more practical. It does not make local tax differences disappear. The same framework still requires country-specific settings.
What implementation teams should prepare
The most consequential verified detail is Microsoft’s warning that reporting output depends on correct cross-LATAM configuration and consistent use of the LATAM extension in transactions. Incorrect setup can produce incomplete or unexpected reports. In other words, a successfully generated file is not, by itself, proof of a successful implementation.
For teams assessing Argentina, a sensible preparation checklist is:
- Separate required capabilities from preview assumptions. Track which tax scenarios and reporting outputs are actually delivered before scheduling acceptance testing.
- Plan transaction-to-report reconciliation. Validate representative transactions and withholding calculations against the resulting files, rather than checking only whether an export completes.
- Keep electronic invoicing on a separate workstream. Its exclusion from preview leaves an explicit gap for any deployment that requires it.
- Review framework prerequisites without treating them as Argentina release instructions. Microsoft’s general documentation requires appropriate setup privileges, the LATAM globalization expansion extension, and the target country feature. Argentina-specific activation details still need release-specific confirmation.
The bottom line: this is a concrete expansion of Dynamics 365 Finance’s planned Argentina coverage, not a finished compliance package. Its value will depend on the delivered preview scope, correctly configured transactions, and validated reporting—not merely the arrival of a roadmap month.