SuiteBanking
NetSuite Unknown
2026-11-13

IPA Now Supports International Vendor Payments Through BILL

Intelligent Payment Automation (IPA) extends to international vendors via BILL, supporting local and wire transfers with automatic exchange-rate handling and GL impact tracking through System Notes.

Affects:IPA / Payment DashboardVendor RecordsVendor Payment ProfilesBILL IntegrationSystem NotesGL Impact / Exchange Rates

What changed

Intelligent Payment Automation (IPA) now lets you pay eligible international vendors electronically through BILL. International payments flow through the same IPA workflow used for domestic payments — create, approve, submit, and track from the Payment Dashboard.

Key details:

  • Transfer method is automatic. BILL determines whether to use a local transfer or wire transfer based on the vendor's country and payment currency. Check payments are not available for international vendors.
  • Exchange rates come from BILL. Before submission, IPA displays an estimated exchange rate and estimated USD funding amount. The final rate is confirmed when BILL accepts the payment for processing. If the final rate differs, NetSuite updates the payment record with the confirmed rate and USD funding amount.
  • GL impact is logged in System Notes. Exchange-rate changes and their GL impact are recorded in System Notes on the payment record.
  • No future-dating. Foreign-currency payments must use the current payment date. The bill payment must post to an open accounting period at submission time.
  • Processing cutoff. Payments submitted before 6:00 PM Pacific (UTC−8) are processed same business day. Later submissions process next business day.

Prerequisites

Before paying an international vendor through IPA, verify all of the following:

  1. BILL supports the vendor's country and payment currency combination (see Oracle's Country information for international payments reference).
  2. The vendor record contains the billing information required for that country. Some countries also require a phone number.
  3. The vendor is synchronized with BILL.
  4. The vendor has the required bank information stored in BILL — NetSuite does not store complete bank account details on the vendor record.
  5. For vendors with multiple supported currencies, a Vendor Payment Profile is configured for each currency.

Technical notes

  • Vendor record limitations. Complete bank account information lives in BILL, not on the NetSuite vendor record. Any SuiteScript or integration that reads bank details from the vendor record will not see international banking data — you must query BILL.
  • Exchange-rate source. If BILL cannot provide an exchange rate for a given currency, the foreign-currency payment cannot be submitted. USD payments in the same batch remain unaffected.
  • System Notes dependency. Automations or saved searches that monitor payment records for exchange-rate changes should key on System Notes entries, since the rate may be updated after initial submission.

What to do

  1. Audit vendor records. Identify international vendors that need to be synchronized with BILL and ensure each has a Vendor Payment Profile for every payment currency.
  2. Check country/currency support. Cross-reference your international vendor list against BILL's supported country and currency combinations before enabling IPA for those vendors.
  3. Review integrations. If you have SuiteScript customizations, workflows, or third-party integrations that read bank details from vendor records, note that international bank data is stored exclusively in BILL.
  4. Update saved searches / analytics. If you track exchange rates or GL impact on payment transactions, add System Notes fields to your saved searches or N/search / N/query queries.
  5. Coordinate with accounting. Ensure accounting periods remain open through the payment submission window, especially for foreign-currency payments that cannot be future-dated.

Note: The source documentation does not specify which NetSuite release introduced this feature or which SuiteScript API version is required. Verify availability in your account's release notes and test in Sandbox before enabling for production vendors.