Appearance
Payment run
FinancePayment runsPayment runPermission:
finance.payment.viewAlso known as
- new payment run
- propose bills
- pay due bills
- batch payment
- bank file
- CSV bank file
- SEPA
- BACS
- early-payment discount
- remittance
The payment run wizard has four steps: Criteria → Review → Confirm → Bank file. It opens on New payment run (/app/finance/payment-runs/new) and on every existing run, at the step that run has reached.
Pay due bills with a payment run
- Go to FinancePayment runs and select New payment run.
- Criteria: fill in the fields below and select Propose bills. The run is saved as a draft ("18 bills proposed") and moves to Review. "No open bills match these criteria." means nothing is due.
- Review: clear the diamond on a row to leave a bill out, or change its Amount (pay part of it) or Discount. Totals per vendor shows what each vendor will get. Select Save selection to keep changes (enabled when you changed something), then Next.
- Confirm: check the selected bills and totals, then select Create and post payments and confirm. The dialog states the result, for example "18 bills are paid with one payment per vendor (11 payments, 92,438.75 USD) from … on 28 Sep 2026. The payments post immediately."
- Bank file: select Download bank file and upload the CSV to your online banking. The run becomes Exported and the step shows when it was exported. You can download it again.
| Field | Required | What to enter |
|---|---|---|
| Bank account | Yes | The account to pay from. Only bills in its entity and currency are proposed. |
| Payment method | No | Recorded on the payments (transfer, cheque …). |
| Payment date | Yes | The date of the payments; default today. |
| Bills due by | Yes | Propose posted or partially paid bills due on or before this date; default a week ahead. |
| Vendors | No | Only these vendors. Empty = All vendors. |
| Include bills with an early-payment discount still available | No | Also propose bills not yet due whose discount date is on or after the payment date; their amount is the balance minus the discount. On by default. |
| Notes | No | Internal note. |
Bills on hold and bills already in another draft run are not proposed.
Posts one entry per vendor payment when you confirm the run
| Account | Debit | Credit |
|---|---|---|
| Accounts payable, per bill (party = vendor) | ✓ | |
| Bank (the run's bank account) | ✓ | |
| Purchase discount, for discounts taken | ✓ |
The bank file
The CSV has one transfer per vendor payment with the columns payment_number, payment_date, debit_account, debit_iban, currency, amount, beneficiary_code, beneficiary_name, beneficiary_iban, beneficiary_account, beneficiary_swift, beneficiary_bank, reference (the run number) and remittance_info (the vendors' invoice numbers). The beneficiary columns come from the bank details stored on each vendor (IBAN, account number, SWIFT/BIC, bank name). The vendor form does not show these details yet; they are set through the API, so check the file for empty beneficiary columns before you upload it.
Cancel a run
While the run is a draft, select Cancel run and confirm: "The draft run PAYRUN-… is cancelled; no payments are made." A confirmed run cannot be cancelled; void its payments one by one in Vendor payments.
Statuses
| Status | Steps available |
|---|---|
| Draft | Review, Confirm, Cancel run. |
| Confirmed | Bank file. |
| Exported | Bank file (download again). |
| Cancelled | Read-only. |
Differences by role
- Every step that changes the run needs Permission:
finance.payment_run.manage. Users with onlyPermission:finance.payment.viewsee the run read-only.
Related
- Payment runs, Vendor payment
- Vendor bills, AP aging
- Bank accounts, Payment methods, Payment terms
- Reconciliation: match the bank's debits to the payments
- Procure to pay
