NetSuite IPA 6.0.0 International Vendor Payments

IPA 6.0.0 adds international vendor payments through BILL, with vendor setup requirements, FX estimates, USD funding updates, and dashboard tracking.

·6 min read·24 views·NetSuite 2026.2·View Oracle Docs

Intelligent Payment Automation (IPA) version 6.0.0 adds international vendor payments through BILL using the existing payment workflow. Teams can set up eligible vendors, review estimated exchange rates and USD funding amounts, and track payments in the IPA Payment Dashboard. Payment readiness depends on supported country/currency combinations, vendor information, synchronization, and bank setup.

What’s New in IPA International Payments?

IPA now supports creating, approving, submitting, and tracking international payments from the IPA Payment Dashboard. The feature extends the existing workflow to eligible international vendors. The Vendors page includes an International Vendors subtab for reviewing vendors and identifying missing information.

BILL determines whether an international payment uses a local transfer or a wire transfer, based on the vendor’s country and payment currency. Check payments are not available for international vendors. Payment teams should therefore confirm electronic-payment readiness rather than assume a check can serve as a fallback.

What Must Be Configured Before Paying a Vendor?

Review these requirements before preparing an international payment:

RequirementWhat to verify
Supported destination and currencyBILL supports the vendor’s country and payment currency combination.
Required billing informationThe vendor has the billing information required for its country, including a phone number where required.
BILL synchronizationThe vendor is synchronized with BILL.
Bank informationThe required vendor bank details are present in BILL.
Vendor Payment ProfilesProfiles are configured for vendors paid through multiple subsidiaries or currencies. For multiple supported currencies, configure the applicable profile for each currency.

Treat country and currency as a combined eligibility check. A vendor’s location alone does not establish that the intended payment currency is supported. For multi-subsidiary or multi-currency vendors, review the intended payment arrangement rather than assuming one completed profile covers every payment.

Bank-data boundary: BILL stores the vendor’s complete bank information. NetSuite does not store the complete bank account information on the vendor record. When checking readiness, distinguish vendor billing information from bank information maintained through BILL.

How Do You Review and Correct International Vendors?

Use the International Vendors subtab to identify eligible vendors and records requiring additional information, such as a valid address or bank details. To correct vendor information:

  1. Go to Payment Automation > Payment Dashboard > View.
  2. If you use OneWorld, on the Subsidiary Dashboard, click Enabled for the subsidiary, then click View in the Actions column.
  3. On the Payment Dashboard, click Vendors.
  4. Select International Vendors.
  5. Review the missing or incorrect information required by BILL.
  6. In the vendor’s Actions column, select Edit Vendor.
  7. Enter the required information and save your changes.

The Vendors page also provides these actions:

ActionPurpose
Add Bank InformationStart bank-information setup for the vendor.
Manage Bank InformationManage vendor bank information.
View BillsReview the vendor’s bills.

For setup reviews, separate billing validation, synchronization, and banking checks. A complete address does not replace the requirement for bank information, and bank setup does not replace the country/currency eligibility check.

When Do International Vendors Synchronize with BILL?

For existing customers, eligible international vendors synchronize automatically after the SuiteApp update. For new customers, eligible international vendors synchronize automatically after the BILL application is submitted.

Automatic synchronization requires a complete billing address, a phone number where required, an open balance, and a supported country and currency combination. These conditions matter when investigating why a vendor has not synchronized automatically: eligibility for international payments is not the only check.

The documented automatic synchronization schedule is daily at 5:00 p.m. Pacific Time (UTC - 8). To synchronize eligible vendors before that scheduled run, click Sync Vendors with BILL on the Vendors page of the IPA dashboard. Use this option when preparing an eligible vendor before the daily synchronization occurs.

An open balance is required for automatic synchronization, but it is not an absolute requirement for starting bank setup. An international vendor without an open balance can begin bank setup if it has no validation errors. Adding bank information creates the BILL vendor profile and opens the BILL widget for bank setup.

Setup exception: Do not interpret the absence of an open balance as proof that bank setup must wait. First check for validation errors; the no-balance setup path requires a clean validation state.

How Do Exchange Rates and USD Funding Work?

For foreign-currency payments, BILL supplies the exchange rate. Before submission, IPA displays both an estimated FX rate and an estimated USD funding amount. The rate can change before submission, so the displayed estimate should not be treated as a guaranteed rate or final bank debit.

BILL confirms the final exchange rate when it accepts the submitted payment for processing. If that rate differs from the estimate, NetSuite updates the payment record with the confirmed exchange rate and USD funding amount. The final USD funding amount is what BILL debits from your bank account.

Exchange rates and their GL Impact are recorded in System Notes. Accounting reviewers can use this information when investigating a difference between estimated funding and the confirmed payment values. The key distinction is between the estimate shown before submission and the rate confirmed when BILL accepts the payment for processing.

If BILL cannot provide an exchange rate, the affected foreign-currency payment cannot be submitted. Treat rate availability as a submission requirement, not merely a missing informational value.

How Do You Track International Payments?

Use the IPA Payment Dashboard to monitor international payments being processed through IPA and their current statuses. Select an individual payment to view its status details. Monitoring remains in the same dashboard used for payment creation, approval, and submission.

For payment reviews, use dashboard status details to inspect processing progress and the confirmed USD funding amount to review funding. The creation-time FX estimate and the payment’s current processing status answer different questions; neither should substitute for the other.

Who This Affects

  • Administrators and vendor-data owners: Review international vendor eligibility, billing completeness, synchronization, and bank-setup readiness.
  • Accounts payable teams and payment approvers: Use the existing IPA workflow while accounting for international payment requirements and changing FX estimates.
  • Accountants and bank-reconciliation reviewers: Review confirmed USD funding amounts and the exchange-rate and GL Impact information recorded in System Notes.
  • OneWorld and multi-currency teams: Check the subsidiary context and applicable Vendor Payment Profiles for the intended payments.

Key Takeaways

  • IPA version 6.0.0 adds electronic international vendor payments through BILL using the existing IPA workflow.
  • Eligibility depends on supported country/currency combinations, required vendor information, BILL synchronization, bank setup, and applicable Vendor Payment Profiles.
  • Automatic synchronization requires an open balance; bank setup can begin without one if the vendor has no validation errors.
  • FX rates and USD funding amounts are estimates before submission. BILL confirms the final rate when it accepts the payment for processing.
  • Use the IPA Payment Dashboard for payment status details and System Notes for recorded exchange rates and GL Impact.

Frequently Asked Questions (4)

Why might an eligible international vendor not synchronize automatically with BILL?
Automatic synchronization requires a complete billing address, a phone number where required, an open balance, and a supported country and currency combination. Eligible vendors synchronize daily at 5:00 p.m. Pacific Time (UTC - 8); you can click **Sync Vendors with BILL** on the IPA dashboard to sync before then.
Can I start bank setup for an international vendor that has no open balance?
Yes. An open balance is required for automatic synchronization, but a vendor without one can begin bank setup if it has no validation errors. Adding bank information creates the BILL vendor profile and opens the BILL widget for bank setup.
How is the final USD funding amount determined for an international payment?
Before submission, IPA displays an estimated exchange rate and USD funding amount, but the rate can change. BILL confirms the rate when it accepts the payment for processing; NetSuite then updates the payment record, and the confirmed USD funding amount is what BILL debits from your bank account.
Where can I review exchange-rate changes and international payment status?
Use the IPA Payment Dashboard to view international payment statuses and select a payment for status details. Exchange rates and their GL Impact are recorded in System Notes, while the payment record is updated with the confirmed exchange rate and USD funding amount after BILL accepts the payment.

Weekly Update History (1)

Banking SuiteAppsadded

Added an entry for Intelligent Payment Automation Version 6.0.0.

View Oracle Docs
Source: Intelligent Payment Automation Version 6.0.0 — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Banking

View all Banking articles →

Also from NetSuite 2026.2

View all NetSuite 2026.2 changes →