What is the Payment Runs page for?

Where the group pays its suppliers. Build run lists every approved, outstanding bill across every company with its payee-bank verdict; tick bills into a named run, download the bank file, upload it at the bank, mark the run paid and Saral posts each payment to Xero from the account the file debited. Planning is the continuous file of bills set aside with a note; Transfers moves money with no bill behind it — company to company, to HMRC, to a lender; History holds every run paid or discarded and whether its payments reached Xero. A run over the approval limit waits for a second person before its file is made. You enter: Which bills go in: a tick on each, a part-payment amount where a bill is paid in pieces, a planned payment date pushed to Xero, or Hold with a reason; The run itself — a name, the bank file for it, Mark as paid once the bank has paid, Discard, Post to Xero — and the run's approval where you are the second person; Planning: a note and an amount to pay per supplier and paying company, and the move from the plan into a run; Transfers: one row per payment — from which company and bank, to which company or outside payee and bank, each side's statement reference, and the amount. Saral fills: The outstanding bills from every organisation: supplier, company, project, dates, outstanding, CIS, discounts, chasing and statement verdicts, the credit line's limit, used and available, and the bank verdict — matched to the latest scanned invoice, unchecked, no bank details, or a mismatch; The summary strip — what is owed, what is late and the bank verdicts of the bills on screen, with a bar per due-date band — and the running total and per-company subtotals of the run being built; Which company's bills appear and which paying account each is written from; the bank file in the layout set up for that account; whether a run needs approval, and by whom; After Mark as paid: the payment on each bill in Xero, dated on the file's payment date from the account the file debited, so the bank feed matches one line to one entry; remittance advices drafted per supplier; the run's audit report; Planning's status on every line, worked out never typed; Transfers' Xero entry per row — Spend or Receive Money, named for its counterpart; History's count of payments made at the bank not yet in Xero. It produces: A bank file per run and per transfers batch, for the bank's own import; Payments in Xero that pre-match the bank feed, one bank line to one Xero entry; remittance advices to suppliers; a Xero history note where a chasing supplier is told its bill is in a run; The run's audit report — who did what and when, every payee verdict and Xero id — and the Planning workbook with its supplier summary. Where the settings live: The paying account per company and the bank-file layout are Settings → Bank files & paying accounts; whether a run needs approval, the limit (£25,000 unless your account changed it), and whether the builder may approve are Settings → Payments → Payment approval; the remittance mode, each company's pay day, whether a chasing supplier is told its bill is in a run and whether a hold is marked in Xero are Accounts → Settings → Payments; outside payees for Transfers are Settings → Payees & own accounts. The gear on this page only decides which companies' bills appear here and which other-company accounts Mark as paid may offer. Who may build, approve and mark paid is the Payment Runs permission and the Approver role.