Verify Brazil Predefined Records Import Status in NetSuite

To verify Brazil predefined records import status in NetSuite, open Setup > Import/Export > View CSV Import Status and review all 11 expected jobs in the Job Status list. Each must show Complete, 100%, and All records were imported successfully. Check these values after installing the SuiteTax Latam Engine - Brazil Records SuiteApp and before using its predefined records.

Key takeaways

Predefined-record imports start automatically after the SuiteApp installation finishes; installation and import completion are separate checkpoints.
Match all 11 CSV import job names below, including their exact prefixes.
Confirm all three completion indicators for every job, rather than relying on a percentage or a single completed import.
If predefined records are missing, review the respective scripts’ execution logs for errors.
The 2026.2 documentation update dated 2026-09-21 states that FTEBR SDF Installer no longer creates predefined records. Do not use its older description as current troubleshooting guidance.

Before you start

Begin this review after installing the SuiteTax Latam Engine - Brazil Records SuiteApp. If installation is still pending, complete the process covered in installing SuiteTax Latam Engine for Brazil Records first.

Have the expected job checklist available while reviewing the account. The task is to compare every listed job, not simply establish that some Brazil-related imports exist. Keep the review scoped to the Brazil Records SuiteApp: an import associated with another SuiteApp does not establish the outcome of these predefined-record imports.

If access questions arise during the review, roles and permissions for Brazil Records is related reading. Keep an inability to inspect something separate from an observed import error; those are different findings and should not be recorded as interchangeable conclusions.

1. Open the CSV import status page

Navigate to Setup > Import/Export > View CSV Import Status. In the Job Status list, locate the jobs in the checklist below.

Record the job name and all three completion indicators rather than writing only “Brazil import done.” A per-job observation gives the next administrator a specific starting point if someone reports a missing record. An installation-complete note does not provide that same evidence.

If you cannot locate an expected job during the review, record it as unresolved rather than assuming success. “Not located during review” is a suggested note for your checklist, not an additional NetSuite status value. This distinction keeps your observations precise without inventing a diagnosis.

2. Match all 11 expected CSV import jobs

Use these job names exactly as written. The list contains both CUSTOMRECORD_FTEBR_ and CUSTOMRE_FTE_ prefixes. Do not normalize them into one naming pattern: that would change the identifiers you are trying to match.

Check	Expected CSV import job name
1	`CUSTOMRECORD_FTEBR_CFOP`
2	`CUSTOMRECORD_FTEBR_CITY`
3	`CUSTOMRECORD_FTEBR_CRT`
4	`CUSTOMRECORD_FTEBR_SPECIAL_TAXREGIME`
5	`CUSTOMRECORD_FTEBR_TAX_ASSESSMENT`
6	`CUSTOMRE_FTE_ITEMCODE`
7	`CUSTOMRE_FTE_LOB`
8	`CUSTOMRE_FTE_PARAMTYPE`
9	`CUSTOMRE_FTE_TAXMAPPING`
10	`CUSTOMRE_FTE_TAXPARAMETER`
11	`CUSTOMRE_FTE_TAXREGIME`

These predefined records cover several tax-data categories. The source describes CFOP code as a code used for classifying goods in Brazil, Brazil City as municipal tax information, and CRT code as tax regime classification. It also identifies Item code for item identification, Line of business for business activities, and Parameter type for tax calculation parameters, alongside tax regimes and mappings.

That breadth makes a spot check inadequate. Finding the CFOP import does not establish the outcome of the parameter or mapping imports. Treat each row as an independent verification item, then assess the complete set together.

For an implementation administrator, the practical benefit is a clear handoff: the checklist shows which imports were inspected and which observations still need investigation. It avoids leaving another reviewer to infer completion from a few familiar record categories.

3. Confirm all three completion indicators

For every expected job, verify these values in its status information:

Indicator	Required value
Status	`Complete`
Percent Complete	`100%`
Message	`All records were imported successfully`

Apply the values as a combined completion test. A percentage alone does not satisfy the verification procedure, because the procedure also requires the status and success message. Likewise, seeing Complete for one job does not establish completion for the remaining ten.

Keep observations separate from conclusions. “CUSTOMRECORD_FTEBR_CITY shows all three required indicators” is an observation about one import. “All expected Brazil predefined-record imports meet the completion criteria” is a conclusion that requires reviewing the full list.

Example: write a useful verification note

The following is an illustrative, manually prepared note—not a NetSuite export, script, or command. Replace the example observations with what you actually see in your account.

SuiteApp: SuiteTax Latam Engine - Brazil Records
Page: Setup > Import/Export > View CSV Import Status
List: Job Status

Example job reviewed: CUSTOMRECORD_FTEBR_CITY
Status: Complete
Percent Complete: 100%
Message: All records were imported successfully

Scope of this observation: Brazil City import only.
Remaining review: Confirm the other 10 expected jobs.

This deliberately limited example shows how to avoid overstating progress. Even a fully successful observation for Brazil City is not a completed review of the SuiteApp’s entire predefined-record import list.

For your final handoff, attach or retain observations for every expected job. If a job has not been inspected, leave that part of the review open rather than copying the example success values into your record.

4. Investigate missing predefined records in script execution logs

If some predefined records are missing, check the execution logs of their respective scripts for errors. The Script Execution Log is the investigation point identified for determining whether problems occurred during the import process.

Capture the missing record category, the corresponding job observation where available, and any relevant logged error together. This gives the administrator investigating the issue a coherent account of what is missing and what the import review showed. It is more useful than separate notes that say only “record missing” and “import checked.”

The import description identifies FTEBR SC SDF Installer (customscript_ftebr_sc_sdf_installer) as the script that triggers CSV imports, including records such as CFOP code, Brazil City, and CRT code. That script is relevant context when investigating the CSV-import portion of the process.

Apply the 2026.2 correction to older installer descriptions

Older material describes FTEBR SDF Installer (customscript_ftebr_sdf_installer) as creating records such as Nexus, Tax code, and Tax type. However, the 2026.2 documentation update dated 2026-09-21 removes mentions of that script from the verification topic because it no longer creates predefined records.

Treat the older description as historical context, not a current instruction to investigate that script as a predefined-record creator. This distinction matters when reviewing implementation notes written before the update: an older two-script explanation should not silently become the basis for a current troubleshooting checklist.

The supplied verification procedure points to log review but does not prescribe a universal rerun or reinstall remedy. Investigate the evidence before choosing corrective action rather than treating either remedy as the automatic response to every missing-record report.

5. Reconcile the checklist before signing off

Before closing the review, compare your observations with all 11 expected job names. Confirm that every job meets the three completion criteria and that no row remains unchecked.

Keep two questions separate in the handoff:

Did every expected CSV import meet the required completion criteria?
Are there unresolved reports of missing predefined records?

If a missing-record report remains open, preserve it as an unresolved finding and continue the script-log investigation. A completed checklist should not erase a specific report that still needs explanation. After investigating an issue, repeat the relevant checks rather than relying solely on observations captured before the investigation.

Ensure all predefined records are successfully imported before attempting to use the SuiteTax Latam Engine - Brazil Records SuiteApp. Once that checkpoint is satisfied, accessing Brazil’s predefined tax determination rules is a relevant next task.

Import verification establishes the record-import outcome. It should not be presented as proof that every subsequent tax configuration or calculation has been validated.

FAQ

Where do I check Brazil predefined-record import status?

Open Setup > Import/Export > View CSV Import Status and review the 11 expected jobs in the Job Status list.

What confirms a successful import?

Every expected job must show Status: Complete, Percent Complete: 100%, and Message: All records were imported successfully.

Does FTEBR SDF Installer still create predefined records?

No. The 2026.2 documentation update dated 2026-09-21 states that FTEBR SDF Installer (customscript_ftebr_sdf_installer) no longer creates predefined records and removes its mentions from the verification topic.