Known Limitations of the Brazil Localization SuiteApp

Note:

To access the Brazil Localization SuiteApp documentation in Brazilian Portuguese (Português do Brasil), see Brazil Localization.

When using the Brazil Localization SuiteApp, keep in mind the following limitations:

SuiteApp updates may fail if you inactivate roles that have been granted permission to transaction types.
Tip:
You can view which role has access to each transaction type:
- In custom transaction type records, inside the Permissions subtab.
  
  For more information, see Configuring Permissions by Editing the Custom Transaction Type.
- In role records, inside the Transactions subtab.
  
  For more information, see Configuring Permissions by Editing the Role.
The custom address form for Brazil only displays the customized labels when the account's language is English (U.S.), Español (Latinoamérica), or Português (Brasil).

If you're using NetSuite with different account language preferences, instead of Address from Brazil, Number, and District, the fields show up as Address 1, Address 3, and Address 2, respectively.

For more information, see General Personal Preferences.
Brazil Localization only supports the Generate, Certify e-document automation type.

When setting up the e-document processes for automation feature from the Electronic Invoicing SuiteApp, you can only configure the Process E-Document button to automate the e-document generation and certification.

For more information, see Processing E-Documents Automatically for Individual Transactions.
Transactions that leverage Brazil Localization's electronic invoicing and tax determination features can have a maximum of 200 items and calculate up to 7 taxes.
Brazil Localization doesn't support the generation or certification of the following tax collection forms:
- Documento Único de Arrecadação (DUA) for the state of Espírito Santo.
- Guia Nacional de Recolhimento de Tributos Estaduais (GNRE) for the state of São Paulo.
By default, Brazil Localization sets the Override Installments field as true when saving transactions with installments. If you import CSV files to edit transactions with installments, having the Override Installments option enabled may cause issues.

When the Override Installments field is set as true and you import a CSV file, NetSuite expects you to provide information to overwrite anything about the installments. The system doesn't update any information that you have not provided yourself.

The Override Installments option can cause errors if you try to import a CSV file that affects the transaction amount, but doesn't provide new installment amounts. In this case, the sum of the installments won't match the transaction amount. Then, NetSuite won't be able to save the update and the CSV import will fail.

To prevent the CSV import failure, you can:
- Add the updated installment amounts to the CSV files before you import them to NetSuite.
  
  If taxes apply and you chose to split withheld taxes amounts, you must also include the updated taxes amounts.
- Let NetSuite calculate the updated installments amounts.
  
  If you want NetSuite to recalculate installment amounts when importing CSV files that affect transactions amounts, do the following:
  1. In the CSV file, set the Override Installments field to F (false).
  2. In NetSuite Import Assistant, on the Import Options step, under Advanced Options, check the Run Server SuiteScript and Trigger WorkFlows option.
    
    With these import settings, if taxes apply and you chose to split withheld taxes amounts, NetSuite splits tax amounts evenly across the installments.
When you create or edit a transaction, don't check the Tax Details Override box or edit any tax information under the Tax Details subtab. Brazil Localization doesn't support this feature. If you override tax details, you may encounter issues when certifying e-documents, calculating withheld taxes on payments, generating statutory reports, and more.
When adding an item to a transaction, the unit of measure can't be different from the primary unit type defined on the item record.

For example, if an item's primary unit type is kilograms, you can't select milligrams as its unit on an invoice. If you select a different unit of measure, you may encounter errors on the electronic invoice generated from the transaction.
Brazil Localization doesn't support the addition of the same item on multiple lines of intercompany transfer orders.

When adding the items to be transferred, don't add the same item on multiple lines of the intercompany transfer order. Instead, if you're transferring more than one unit of the same item, specify it in the Quantity column.
Brazil Localization doesn't support the Represents Subsidiary option for intercompany customers and vendors.

The SuiteApp is able to identify a customer or vendor as representative of a subsidiary based on the number you enter in the Federal Tax Registration field. For more information, see Transferring Inventory Between Subsidiaries in Brazil.
When generating delivery files with the Centro Nacional de Automação Bancária (CNAB) 240 standard, you can't add or edit fine and interest amounts for expense reports, vendor prepayments, and custom transactions enabled for CNAB.
The PDF templates provided by the SuiteApp don't support the advanced PDF/HTML template editor's What You See Is What You Get (WYSIWYG) mode.

You can edit the PDF templates with the editor's source code mode. For more information, see Advanced Templates Customization in the Template Editor.
In sales transactions, you can't change the origin code directly on the transaction record.

If you define the origin code for your items, the code appears after you add the item to the transaction. You can define the origin code in the item record. For lot numbered and serial numbered items, you can also define the origin in the inventory details. The origin from the inventory details precedes the origin from the item record.

To set a different origin in sales transactions, you must either:
- Edit the item record and select a different origin code.
- Create or edit the transaction through an integration or import.
In purchase transactions, you can enter different origin codes directly on the transaction record. The origin code from the transaction precedes the origin from the inventory details and item record.

Related Topics