Tax compliance is where projects get stuck.

CFDI 4.0, the payment complement, VAT and income tax withholdings, the DIOT file and electronic accounting all come from Oracle's localization. Stamping does not, and never is part of NetSuite. It always goes through a SAT-authorized PAC, contracted separately. NetSuite ships with the connection ready for two, MySuite and Solución Factible. If the company already works with a different PAC, connecting it is development work and has to be budgeted.

Yes, at no extra cost. It comes as its own SuiteApp within the Mexico package, Mexico Bill of Lading, which complies with version 3.1 of the complement. What it does not come with is the configuration, which requires setting up SAT operators, fleet codes and origin and destination addresses. If you move goods it is covered, but it is implementation work and belongs in the scope from the start.

No. NetSuite's own payroll only runs in the United States. In Mexico payroll stays in an external system, and what gets integrated into NetSuite is the accounting entry and the cost per cost center. It is the most common surprise when it comes up with the project already underway.

Not a native Oracle one. The tax side (electronic invoicing, perceptions, withholdings and VAT ledgers) is built on the platform. It's known work, but it has to be budgeted from the start, because ignoring it is the most expensive mistake in an Argentine implementation.

Where a native one exists, native. Oracle maintains it and updates it with every release. A custom localization is justified only when there's no official option, or when the native one doesn't cover a specific business requirement.

Yes, with NetSuite OneWorld. One account, multiple subsidiaries, each with its functional currency, local chart of accounts and localization. Consolidation across entities is automatic.

NetSuite builds the document. Communication with the tax authority goes through an authorized provider in the countries where that's mandatory, such as Colombia, Mexico and Chile. In Argentina the integration is direct against ARCA's web services.

If the localization is native, Oracle publishes the update and it has to be tested in a sandbox before being applied. If it's custom, we make the adjustment. Support plans include regulatory changes.

Yes, and it's a frequent case. It's added on top of the existing account without reimplementing, though it usually means revisiting how taxes and GL accounts were set up.