Payments and Payment Process Requests
Selection and build
A payment process request (PPR) is the normal way to pay. On submission you choose a business unit, payment method, pay-through date, supplier or pay group, and optionally a payment process profile. The request runs in stages: selection, payment build, formatting, print or transmission, and confirmation. Invoices must be validated, approved, off hold, and due on or before the pay-through date to be selected.
Profiles and formats
The payment process profile determines payment method, disbursement bank account, payment file format, and whether files are transmitted or printed. A mismatch - for example an electronic method with a check-only format - leaves the request in Needs Attention until corrected.
Manual and exception payments
Create Payment and quick payment create a single payment outside a PPR. Stop payment prevents a payment from completing before confirmation; void reverses a confirmed payment and requires accounting reversal. Payment status moves from created to formatted, printed or transmitted, confirmed, and eventually cleared.
Discounts and priority
Payment terms drive discount dates; paying after the discount date loses the discount. Payment priority and pay groups control selection order when cash is limited.
Worked example
An invoice for 5,000 with terms 2/10 Net 30 goes into a PPR with a pay-through date of day 12. The payment date falls after the discount date, so the invoice is paid at 5,000, not 4,900. Submitting with a pay-through date of day 10 or earlier captures the 2% discount.
Traps
A PPR never pays an invoice on hold, unapproved, or unvalidated. Voiding is not the same as stopping a payment. Changing a supplier bank account after the build stage can leave the request in Needs Attention.