Finance Index
What is an off-cycle payment and when is one justified?
Reference guide to off cycle emergency payments, including payment timing, method choices, control points, reconciliation, and vendor communication.
An off-cycle payment is any payment processed outside the scheduled payment run. Legitimate triggers include supplier credit holds threatening operations, contractual same-day obligations, legal settlements, and genuine emergencies. Each should require documented justification and the same - or stronger - approvals as a normal run, because urgency is the most common cover for both error and fraud.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| An off-cycle payment | An off-cycle payment is any payment processed outside the scheduled payment run. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | Ranked by speed: RTP/FedNow (seconds, if both banks participate), wire (hours, highest cost, irrevocable), same-day ACH (end of day, up to $1M, cheapest of the three). | Reduces payment errors, timing issues, and reconciliation cleanup. |
| How do we keep "urgent" | Track off-cycle rate as a standing metric - healthy shops keep it in the low single digits as a percentage of payments. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Approval path | Written justification with a reason code, approval one level above the normal threshold, verification of payment details against vendor history, and same-day recording - no verbal-only approvals. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Vendor impact | Use your documented delegation: a pre-named backup approver with time-boxed authority approves, payment details are verified by callback, and the payment goes same-day ACH or wire. | Reduces payment errors, timing issues, and reconciliation cleanup. |
What's the fastest compliant way to pay a vendor today?
Ranked by speed: RTP/FedNow (seconds, if both banks participate), wire (hours, highest cost, irrevocable), same-day ACH (end of day, up to $1M, cheapest of the three). "Compliant" means the off-cycle request still gets independent approval, beneficiary details verified against payment history (not against an email), and immediate recording in the AP system - speed never waives verification, because fraudsters manufacture exactly this scenario.
How do we keep "urgent" from becoming the norm?
Track off-cycle rate as a standing metric - healthy shops keep it in the low single digits as a percentage of payments. Require a reason code on every off-cycle payment and review the distribution monthly: recurring reason codes point to broken upstream processes (slow approvals, missed runs, bad vendor terms), which is where the fix belongs. Charging requesting departments a visible internal "rush" process also dampens false urgency.
What approval and documentation should emergency payments require?
Written justification with a reason code, approval one level above the normal threshold, verification of payment details against vendor history, and same-day recording - no verbal-only approvals.
A vendor is threatening to stop shipping and my CFO is traveling - what do we do?
Use your documented delegation: a pre-named backup approver with time-boxed authority approves, payment details are verified by callback, and the payment goes same-day ACH or wire. If no delegation exists, that's the gap to fix - not a reason to bypass approval.
What percentage of off-cycle payments signals a broken process?
Sustained rates above roughly 5% of payment count usually indicate upstream failure - slow invoice approval, unrealistic run cadence, or vendors gaming the exception path.
How should one-off payments to non-vendors (refunds, settlements, honorariums) be handled?
Through a controlled one-time-payee process with its own approval path and tax screening (W-9 where reportable) - not by minting junk vendor records that pollute the master file.
Should manual / out-of-system payments ever be allowed?
Only as a last resort with mandatory same-day recording against the invoice and a monthly reconciliation that hunts for bank debits with no AP record; every manual payment is a control bypass by definition.
Someone paid a vendor from the bank portal bypassing AP - now what?
Record the payment against the invoice immediately, trace who initiated it and under what authority, then close the gap: restrict bank-portal payment rights to treasury, and reconcile bank-to-ledger frequently enough to catch the next one fast.
How do I process a partial payment when cash is tight?
Pay the partial amount against the specific invoice (not on-account), document the plan for the balance with the vendor, and make sure the open invoice reflects the remaining balance so nobody double-pays later.
What's the right policy for vendor prepayments and deposits?
Require contract-backed approval, record them as prepaid assets (not expense), tie each to the PO or contract, and enforce clearing against the final invoice - unapplied prepayments are a classic source of duplicate payment and escheatable credits.
Stampli perspective
Because Stampli separates invoice approval from payment approval and enforces approval rules by amount and bank account, an off-cycle payment still passes the same control gates as a scheduled one - with the full audit trail of who requested, approved, and released it and why.