Ramp: reimbursements delayed - payroll cutoff passed

TL;DR

Reimbursements batch into payroll runs, and the report was approved after the cutoff, so it waits for the next cycle. Confirm the reimbursement is queued for the next run in Ramp, and tell the employee the expected pay date. If company policy allows off-cycle payments, ask finance to run one; otherwise the fix is the calendar, not the system.

Error

Ramp: reimbursements delayed  -  payroll cutoff passed

Steps

1. Open the reimbursement in Ramp and confirm its status is approved and queued. Expected: the status shows it is scheduled for the next payroll batch.
2. Check the payroll calendar for the next run date. Expected: you can name the date the employee will be paid.
3. Inform the employee of the scheduled pay date. Expected: the employee knows when to expect the money.
4. If the amount is urgent and policy allows, ask finance to include it in an off-cycle run. Expected: finance confirms the off-cycle payment or declines per policy.
5. For future cycles, submit and approve reports at least two business days before the cutoff. Expected: reimbursements land in the intended cycle.

When to use

• Ramp shows reimbursements delayed past the payroll cutoff.
• An employee asks where their reimbursement is after approval.
• Planning submission timing around payroll dates.

When not to use

• The reimbursement failed for invalid bank details.
• The report was never approved.
• The delay is in Ramp's bank transfer rather than the payroll batch.

Tool compatibility

Ramp reimbursements with payroll integration (current 2026 releases). Applies to ACH reimbursement payouts.

Variant phrasings

ramp reimbursement "scheduled for next cycle"

The normal post-cutoff state. The payment is queued, not lost.

employee paid late after approval in ramp

Approval after cutoff means the next cycle. Communicate the date.

off-cycle reimbursement in ramp

Possible only if finance runs off-cycle payroll. Policy decides, not the tool.

Why it happens

Payroll runs on a fixed calendar with a cutoff for inclusions; anything approved after the cutoff rolls to the next run. Ramp queues the reimbursement correctly, so the delay is the payroll schedule, not a system failure. The cutoff exists because payroll needs a frozen, auditable batch, which is why the only accelerant is an explicit off-cycle run approved by finance.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_f0ImQ9-hwl4LtQuJLqyEfA