The quick answer
In the demonstrated electronic payments SuiteApp, open Electronic Bill Payments, choose the Euro bank account, mark the open bills and the vendor bill credit, lower the payment on any bill you only want to part-pay, and select Process Payments. That creates the bill payments with an Approval Status of Pending Approval 1. An approver then marks them on Approve/Reject Bill Payments and selects Approve. Only after that does Generate Bank File list them: mark them, select Submit, and the SEPA XML file lands in the File Cabinet folder set up for that bank. Upload the file to the bank yourself. Generating it doesn't mean the bank accepted or paid anything.
This is an account-specific example of one configured third-party flow. Test it in a sandbox before you pay anyone with it. The page names, buttons, status wording, approval fields and file folder belong to an installed electronic payments (EP) SuiteApp and its optional bill payment approval module. They change with the SuiteApp version, the account, the role and the settings, and they aren't standard NetSuite navigation. The Bill Payments list and the Bill Payment record are NetSuite's own. The account isn't OneWorld, so no subsidiary is picked. Person and operating-company names in the screenshots are fictional example data.
Before you start
You need the EP SuiteApp with its approval module installed, a Euro company bank setup that points at a SEPA XML payment definition and a File Cabinet folder, vendors activated for electronic payment with bank details your team has verified (IBAN and BIC), and roles that can process payments, approve them and generate the file. The bills have to be approved, open and on the A/P account you pick. A bill that's missing from the list is usually missing one of those. Check the bank's SEPA requirements against the payment definition, payment holds, the accounting period and the aggregation setting before you process.
The example pays four vendors from 1120 Harbor Bank EUR: Nordhavn Packaging ApS (bills NP-20418 for 840.00 and NP-20466 for 312.50, and credit CR-5521 for 60.00), Bergmann Werkzeug GmbH (BI-77310 for 1,275.00 and BI-77344 for 460.80), Lumen Capital Services (LC-3092 for 2,000.00, part-paid at 750.00) and Vestkyst Logistics ApS (VL-1187 for 3,150.00 and VL-1203 for 215.40). The Euro rate to the base currency is 1.07426318.
01. Open Electronic Bill Payments and pick the Euro account
Open Electronic Bill Payments from the SuiteApp. In Account, choose 1120 Harbor Bank EUR. The EP Bank Account Setup fills in as Harbor Bank EUR and Bank Payment Definition as SEPA XML. Payment Date and End Date both show 11/04/2026, and A/P Account is Accounts Payable.
The Electronic Payments sublist then lists what's open in Euro: seven bills and the credit CR-5521, each with its due date and exchange rate.
02. Select the bills and credit, with one partial payment
Select Mark All. Each Payment takes the amount due. The credit appears with a negative amount, (60.00), so Nordhavn Packaging ApS is paid its two bills less that credit.
Say Lumen Capital Services should only get part of bill LC-3092 this week. Set its Payment amount to 750.00 instead of 2,000.00. The other 1,250.00 normally stays open on the bill, though discounts, holds and custom workflows can change that.
Scroll up and check the totals before you process anything. Amount is 6,943.70 and Count is 8. Amount is the sum of the Payment column with the credit subtracted: 1,275.00 + 460.80 + 750.00 + 840.00 + 312.50 - 60.00 + 3,150.00 + 215.40.
03. Process the payments
Select Process Payments. Electronic Payment Status shows Current Status as Complete with 4 record(s) processed. Eight rows became four bill payments because, with the grouping this SuiteApp applied, there is one payment for each vendor. Other setups can group by payee, entity bank or currency, and Count is just the rows you marked, so don't read the number of payments off it. Check the processed and unprocessed counts too.
Select Review Bill Payments to open NetSuite's Bill Payments list. The four new payments are dated 11/04/2026 and paid from 1120 Harbor Bank EUR, and each Memo lists the bills, and the credit, it covers.
04. Review a payment that is awaiting approval
Open the payment for Nordhavn Packaging ApS. It's for 1,092.50 in Euro at an Exchange Rate of 1.07426318: 840.00 + 312.50 - 60.00.
Further down, Pay by EP is checked, File Format is SEPA XML, and Payment Reference names the credit and both bills. The SuiteApp builds that reference, and whether it reaches the bank file depends on the file definition. On the Apply subtab the 60.00 credit comes off bill NP-20466, so that bill's Payment is 252.50 and Applied To totals 1,092.50.
Open the Custom subtab. Approval Status (2) is Pending Approval 1 and Last Approver is empty.
That status is a custom field. It doesn't tell you whether the payment has posted. Open GL Impact, check the accounting period and the bill balance, and ask how your account handles a rejected payment before you rely on this step as a control.
05. Approve the four bill payments
The approver opens Approve/Reject Bill Payments and chooses Harbor Bank EUR in Account. The recording reaches it through the global search; your account's SuiteApp menu may have its own entry. The EP Bill Payment sublist lists the four unapproved payments. Foreign Currency is the Euro amount, and Amount is its base-currency equivalent at the payment's exchange rate.
Select Mark All. FX Total is 6,943.70, Amount is 7,459.37 and Count is 4. Check payees and amounts here, along with the rate, then select Approve. Don't recalculate the base-currency total from one multiplication, because NetSuite converts and rounds each transaction.
Bill Payments Approvals Status reports Completed. Reopen the Nordhavn Packaging ApS payment and look at the Custom subtab: Approval Status (2) is Approved and Last Approver is Alex Morgan.
06. Generate the bank instruction file
Back on the approval status page, select Generate Bank Instruction File. On Generate Bank File, choose Harbor Bank EUR. Bank Payment Definition shows SEPA XML, and the Bill Payments sublist lists only the four approved payments. Select Mark All, then Submit.
Electronic Payment Status shows Complete with 4 record(s) processed and a Download File link.
07. Find the SEPA XML file
The file is also in the File Cabinet. Open Documents > Files > File Cabinet and then the EP Bank Files folder, which is the location set on the company bank setup. SEPA0042.xml is the new file, an XML File last modified on 11/04/2026.
Download it and upload it to the bank's portal, or hand it to whatever integration your team uses. This SuiteApp doesn't send it. Before you upload, look at the run for errors or payments that didn't make it into the file, and open the XML to check the payment count, total and creditor details. After you upload, confirm the bank accepted the file, and match the bank activity to these bill payments later.
Common questions
Why is an approved, open bill missing from the payment list?
It probably fails another condition. The list depends on the bank account and A/P account you chose, the currency, whether the vendor is set up for electronic payment, the date filters and any payment hold. Check those before you look at the bill's approval status.
Why does the page show eight selected rows but create four bill payments?
Count is the number of rows you marked. In this example the SuiteApp created one bill payment for each vendor, so eight rows became four payments. In other configurations payments can stay separate by vendor, entity bank or currency, so check the aggregation setting instead of counting rows.
How do I make a partial payment?
Edit the Payment amount on the row before you process; don't touch the bill total. Lumen Capital Services was paid 750.00 of bill LC-3092's 2,000.00, and the rest normally stays open on the bill. Confirm the remaining balance afterward, and expect an edit after approval to need a fresh approval. Discounts, holds, rejection and custom workflows can change the outcome.
How is a vendor bill credit handled?
It shows with a negative amount, and the vendor's bill payment is its marked bills minus the credit. The credit isn't a negative cash payment. Here the 60.00 credit came off bill NP-20466, which made that bill's payment 252.50. The credit and the bills need to belong to the same vendor and currency.
Does Approved mean the payment has posted or been paid?
No. Approval Status is a custom field that this SuiteApp adds. It says an approver signed off, and Last Approver says who, but not that every required level approved. The bill approval, the payment approval, the posting and the bank settlement are four separate things. Check GL Impact and the posting period, and remember that approval doesn't move money.
Does generating the bank file mean the bank paid the vendors?
No. The file is an instruction file. The SuiteApp in the example doesn't transmit it, so you upload it or use an integration. The bank still has to accept it, and the bank activity should be matched to the bill payments later.
What if the run shows errors, or the bank rejects the file?
Bank rejection is separate from NetSuite generating the file. Open the status page and look at the processed and unprocessed counts, then check the affected vendor's bank details, currency, amount, date and approval status. Don't regenerate the file or delete bill payments before you know whether the SuiteApp wants the original file cancelled, reversed or recreated, because a second file can pay a vendor twice.
Will my account show these pages?
Only with the same SuiteApp installed and set up. These are the demonstrated SuiteApp's pages, so names, status wording, defaults and the file folder can differ by version and configuration. NetSuite's native Electronic Bank Payments links its generated file from a Payment File Administration record instead.