Field mapping management for e-invoice file templates for Brazil
Review the default Avalara field mappings in the Brazil e-invoice file templates to confirm that billing, tax, and response data is available to the integration.
Default templates
The Brazil pre-integrated package provides Zuora default e-invoice templates for the billing document types included in the Brazil configuration. These templates provide a starting point for generating country-specific e-invoice payloads without building the mappings from scratch.
Before submitting billing documents, confirm that the document type is supported for your Brazil configuration and that the corresponding default template is enabled for the Brazil business region.
Data mapping areas
Review the mappings for the data used by your Brazil configuration, including:
Seller legal-entity and tax-registration information.
Buyer identifiers, business information, and address details.
Billing document number, date, type, currency, and totals.
Line-item quantities, prices, discounts, and tax details, where applicable.
Brazil-specific values required by the Avalara mandate and the enabled document type.
City: Map the value to the seven-digit IBGE municipal code for the location where the NFS-e is issued.
Maintain the source data in the Zuora objects used by the templates, such as the business region, account e-invoicing profile, contacts, and billing documents. If a required value is stored in a custom field, confirm the field, its location, validation rules, and how it is populated before configuring or changing the mapping.
Response and status mappings
The Brazil configuration includes default response field mappings and status reason mappings. These mappings allow Zuora to receive Avalara processing results and store the response information associated with the billing document.
Review the Brazil mappings with your implementation team to confirm which response values are stored in Zuora and whether any of them must be displayed on invoice documents or used by downstream systems. Use the Brazil mappings provided with the pre-integration unless your implementation requirements call for a reviewed and supported change.