Required dates, delayed payment, and payroll deduction

This article covers gifts made through GiveCampus. Payment and recurring-gift options depend on the institution and the form.

A single-payment pledge requires a payment date. Multiple installments require a first and last payment date and an offered frequency. Pledge forms support autofill for payment_date, or for multiple installments first_installment, last_installment, and installment_frequency. Open the pledge form’s Tracking & Analytics → Links & Appeal Codes → Generate Autofill Links, select the available pledge fields and generate the link. Dates must be within the form’s allowed range and the frequency must be enabled; donors can edit the prefilled schedule. See Autofill pledge payment dates and installment schedules. The minimum last date depends on frequency, and a configured maximum payoff date limits selection.

To collect a card now for payment in two months, the form must allow future automatic pledge payments and support the payment-information flow. Choose a single payment, select the future date within the permitted range, and enter payment information now. Confirm the displayed schedule before submitting. A pledge without payment information is a different flow and cannot charge a missing card.

The date and payment-choice controls are built into this pledge flow. Adding a payroll-deduction checkbox does not remove them or implement payroll collection. The pledge settings do not provide a control to remove the scheduled date; have support evaluate a different collection workflow if no scheduled fulfillment date is appropriate.

Why does a one-time future pledge say recurring gift?

A pledge scheduled to charge in the future uses GiveCampus's recurring-payment scheduling system even when it has only one installment. Seeing “recurring” or an associated subscription record does not by itself mean the donor selected monthly or annual giving, that the pledge form offered recurring gifts, or that the pledge was entered incorrectly.

For example, a pledge for one payment on January 31, 2027 can correctly use a subscription with one scheduled installment on that date. It remains a pledge; the subscription supports collecting the future payment. A one-installment schedule does not authorize ongoing monthly or annual payments.

To confirm the setup, review the pledge's scheduled payment date, installment amount, total/remaining installment count and whether the schedule is finite rather than set to run indefinitely. When the intended single installment has been successfully collected, there are no further scheduled installments under that one-payment schedule. Payment failure or retry handling is separate from adding an ongoing giving commitment.

Do not cancel, recreate, convert or shorten the pledge solely to remove a recurring label. If the record shows one installment for the agreed amount and date, no schedule correction is needed on that basis. If the actual date, amount or installment count is wrong, ask Support to review the specific pledge before changing it.

This explanation applies to pledges set up for future automatic payment with payment details. A pledge recorded without payment information is a different workflow and cannot automatically charge a missing payment method.

For reporting, distinguish the pledge commitment from payments collected. Pledge subscriptions retain a pledge subscription type, while an individual payment may be an installment. Use pledge commitment/payment reporting and, where needed, Subscription Type and Installment Subscription ID rather than interpreting a recurring label as proof of an ordinary recurring gift.

Suggested answer: “This is expected for a pledge scheduled to charge in the future. GiveCampus uses its recurring-payment system to schedule that charge, even for a single installment. That does not mean the donor signed up for ongoing recurring gifts. If the pledge shows one payment for the agreed amount on January 31, 2027, it is set up as a one-time future payment and does not need to be recreated.”