Brazil Banking Integration SuiteApp: Banco do Brasil Support

TL;DR: The Brazil Banking Integration SuiteApp connects NetSuite exclusively with Banco do Brasil. It supports receivables through bank slips and Pix transfers, payable bank slip payments, and periodic bank statement imports. In NetSuite 2026.2, it also supports reconciling payable bank slips with NetSuite transactions. Appropriate installation, configuration, and permissions are required.

For finance teams, bank coverage is the first qualification question. The next is whether the SuiteApp supports the payment direction, payment method, and reconciliation process the business needs. A supported bank connection does not establish coverage for every payment workflow.

Which Brazilian bank does the SuiteApp support?

Banco do Brasil is currently the SuiteApp’s only supported bank. The SuiteApp facilitates communication between NetSuite and Brazilian banking APIs, but that integration approach does not mean it connects to every bank in Brazil.

For example, an organization might use Banco do Brasil for receivables and another institution for other operations. The Banco do Brasil relationship fits the stated bank coverage; the other institution does not become supported simply because the organization installs the SuiteApp. Evaluate each banking relationship separately before including it in an automation plan.

The SuiteApp uses custom records and these plug-in types for secure access to online banking data:

Brazil Banking Data Retrieval
Brazil Banking Integration
Financial Institution Connectivity

These are connectivity components, not additional supported banks or payment methods. For a finance-led evaluation, establish the bank restriction before estimating how much manual payment work the integration could replace.

Supported receivables, payables, and reconciliation processes

Keep the four principal capabilities separate when building requirements:

Capability	Supported scope	Automation mechanism or purpose
Accounts receivable	Incoming bank slip payments and Pix transfers	Custom records, fields, and settings eliminate manual electronic bank-file exchange for the supported process
Accounts payable	Payments made with bank slips	Custom records, fields, and settings eliminate manual electronic bank-file exchange for the supported process
Bank statement import	Periodic imports of bank statements	Reduces manual importing and matching effort for reconciliation
Payable bank slip reconciliation	Reconciling payable bank slips with NetSuite transactions in NetSuite 2026.2	Custom records, fields, settings, and periodic imports support reconciliation

Receivables: bank slips and Pix transfers

Accounts receivable automation supports accepting payments through bank slips and Pix transfers. Custom records, fields, and settings automate the supported processes without manually exchanging electronic bank files.

The operational benefit is specific: finance users can move away from manual bank-file exchange for these incoming-payment processes. That should not be presented as a promise that every activity around customer collections becomes unattended.

Consider a receivables team collecting through both bank slips and Pix at Banco do Brasil. Both incoming methods fall within the stated coverage. During evaluation, the team should assess each method separately rather than treating success with bank slips as proof that its Pix requirements are satisfied.

The Brazil Banking Integration setup overview is a useful next step once the institution and incoming-payment methods match your requirements. Identify which receipts use bank slips, which use Pix, and where staff currently exchange electronic bank files manually.

Keep payment direction explicit: Pix is included in the receivables capability described here. That does not establish support for outgoing Pix payments.

Payables: payments made with bank slips

Accounts payable automation supports payments made with bank slips. As with receivables, the SuiteApp uses custom records, fields, and settings to avoid manual electronic bank-file exchange for the supported process.

For a payables manager, making a payment and reconciling a payable bank slip are different requirements. Payment automation addresses the outgoing bank slip process. Reconciliation addresses the relationship between payable bank slips and NetSuite transactions. Evaluate them separately, even when they belong to the same operating workflow.

For example, a team may currently handle payable bank slips by manually exchanging electronic files with Banco do Brasil. Its bank and payment method align with the stated capability. Other outgoing-payment requirements still need separate assessment; bank slip support alone does not establish their coverage.

A practical assessment should:

Identify payable bank slip processes associated with Banco do Brasil.
Separate payment-processing requirements from reconciliation requirements.
Identify the manual electronic bank-file exchanges in the current process.
Include custom records, fields, settings, and permissions in implementation planning.
Validate payment and reconciliation outcomes separately.

These are evaluation recommendations, not SuiteApp configuration instructions. They help prevent approval based on bank coverage alone when the actual finance requirement is narrower or more complex.

How does bank statement import support reconciliation?

The SuiteApp supports periodic imports of bank statements to simplify reconciliation and reduce manual effort involved in importing and matching bank data.

For planning purposes, distinguish recurring imports from real-time availability. The supported capability is periodic import; it should not be presented as a promise of continuous bank-data updates. Finance should define its statement-availability requirements and validate the configured import arrangements against them.

A useful acceptance question is: does the imported statement information support the team’s reconciliation process at the required operational cadence? This keeps the evaluation focused on finance outcomes rather than treating the existence of an import as sufficient evidence of readiness.

Payable bank slip reconciliation in NetSuite 2026.2

In NetSuite 2026.2, custom records, fields, other settings, and periodic imports support reconciling payable bank slips with NetSuite transactions.

This capability is more specific than general bank statement import. Statement import brings banking information into the reconciliation process; payable bank slip reconciliation addresses a particular relationship between payable bank slips and NetSuite transactions.

Record two distinct outcomes in an acceptance plan:

The required periodic imports operate as configured.
Payable bank slips can be reconciled with the relevant NetSuite transactions using the supported process.

These checks prevent “data imported” from becoming shorthand for “reconciliation complete.” The supported description does not justify claiming that every imported item is automatically reconciled without review.

Oracle provides a dedicated Bank Slip Reconciliation for Brazil topic. For adjacent context, see the Match Bank Data enhancements overview, while keeping that discussion separate from the SuiteApp’s Banco do Brasil coverage.

Relevant documentation updates

The supplied update history helps administrators identify which areas deserve attention when reviewing an existing implementation. These are documentation-update dates, not evidence that every capability first became available on the same date.

Update date	Release	Documentation change
October 20, 2025	2026.1	Added topics covering accounts payable payment settings, scheduling verification of accounts payable integration status, and accounts payable automation
December 15, 2025	2026.1	Updated Defining Bank Slip Settings for Banking Integration for Brazil to make it bank slip-specific
February 16, 2026	2026.1	Added Monitoring Accounts Payable Payments for Brazil
April 13, 2026	2026.1	Updated Default Permissions for Brazil Banking Integration with new administrator permissions
October 19, 2026	2026.2	Added Scheduling the Import of Bank Slips for Reconciliation for Brazil and Bank Slip Reconciliation for Brazil; updated the integration overview to include the reconciliation feature

For an administrator, these changes suggest distinct review areas: payment settings, integration-status verification, payment monitoring, permissions, and reconciliation imports. For finance, they reinforce the need to assess payment execution and reconciliation as separate outcomes.

What should finance and administrators verify before rollout?

Administrators are responsible for installation and setup, and users need appropriate permissions. A capability can fit the business requirement while configuration or access work remains incomplete.

Installation planning includes prerequisites, installation, and verification of the import status of predefined records. Include that verification explicitly rather than treating installation alone as the readiness milestone.

A focused readiness review can follow this order:

Confirm the institution. Limit the proposed supported-bank scope to Banco do Brasil.
Map the processes. Separate incoming bank slips, incoming Pix transfers, outgoing bank slips, statement imports, and payable bank slip reconciliation.
Review prerequisites. Use the Brazil Banking Integration prerequisites overview to organize preparation.
Complete administrator setup. Include installation, predefined-record import verification, and relevant configuration.
Check user access. Confirm appropriate permissions for the people expected to use the features.
Validate finance outcomes. Assess receipt automation, payment automation, imported banking data, and payable bank slip reconciliation independently.

Use Oracle’s installation documentation and Roles and Permissions for Brazil Banking Integration for the corresponding setup work. Brazilian Portuguese documentation is available in the Brazil Banking Integration guide.

IT specialists oversee banking API integration and data-management security. Finance should supply process requirements, administrators should own installation and setup, and IT should address connectivity and security responsibilities. Assigning those responsibilities helps avoid mistaking a successful connection for a fully validated finance workflow.

FAQ

Does the Brazil Banking Integration SuiteApp support banks other than Banco do Brasil?

No. It currently supports connections exclusively with Banco do Brasil.

Does it support Pix payments?

It supports accepting Pix transfers through accounts receivable automation. That receivables capability does not establish support for outgoing Pix payments.

What accounts payable process does it support?

It supports payments made with bank slips, using custom records, fields, and settings instead of manual electronic bank-file exchange for the supported process.

Can it reconcile payable bank slips in NetSuite?

Yes. In NetSuite 2026.2, custom records, fields, settings, and periodic imports support reconciling payable bank slips with NetSuite transactions.

How does it import bank statements?

It supports periodic bank statement imports, helping reduce manual importing and matching effort for reconciliation.