Appearance
Payment runs
Also known as
- payment run
- payment batch
- bank file
- BACS
- SEPA
- payment proposal
- pay run AP
- batch payments
- supplier payment run
- cheque run
A payment run pays many vendor bills at once: it proposes the bills due by a date, you review the selection, and confirming it creates and posts one payment per vendor and produces a bank file for your bank. AP clerks prepare runs; a controller usually confirms them.
| Column | Meaning |
|---|---|
| Run | PR-YYYY-0000. |
| Payment date | The date of the payments. |
| Bills due by | The due-date cut-off used to propose bills. |
| Bills, Payments | Bills selected and vendor payments created. |
| Total | Amount paid. |
Statuses
| Status | Meaning | What you can do next |
|---|---|---|
| Draft | Proposed; the selection can change. | Review, Save selection, confirm, Cancel run. |
| Confirmed | Payments created and posted. | Download bank file. |
| Exported | The bank file has been downloaded at least once. | Download it again if needed. |
| Cancelled | Cancelled while draft; no payments were made. | Read-only. |
Filter the list by Status or Payment date; select a row to open the run.
Start a run
Select New payment run (needs Permission: finance.payment_run.manage), or press CtrlK and type payment run. See Payment run.
Differences by role
- Permission:
finance.payment.viewlists runs; Permission:finance.payment_run.managecreates, edits, confirms, cancels and exports them.
Related
- Payment run
- Vendor payments, Vendor bills, AP aging
- Vendor detail: bank details used in the bank file
- Cash forecast
- Procure to pay
