Documentation Index

Fetch the complete documentation index at: https://help.infoodle.com/llms.txt

Use this file to discover all available pages before exploring further.

Editing a pledge

Prev Next

You can edit an existing pledge at any time. The options available depend on whether any pledge dates have already been paid or scheduled.

How to Access Pledges

  1. Search for the person or organisation whose pledge you want to manage.
  2. If Finance is not showing on the persons profile, then you will need to add it. To see how to do this, look at Profile Layout
  3. Then in the Finance section on the profile page, open the Pledges tab.

Image

  1. Click the Actions menu next to the pledge (you may have to scroll across to the right side of the screen, or zoom out). Then click Manage Pledge to edit it.

Image

The actions menu options

Menu item Description
Notes Add or view notes attached to this pledge. A note count badge shows how many notes exist. Notes are stored against the pledge record itself, so they stay with the pledge even if other details change.
Manage Pledge Open the pledge editor to make changes to the pledge. Also provides options to cancel or delete the pledge.
Move to Another Contact Transfer this pledge to a different person or organisation.

How to Edit a Pledge

Click the Action drop down next to the pledge you want to edit, then click Manage Pledge. Then you will see a pop up on the right side of your screen that may look like this.

Image


How to Use the Edit Pledge Options

Schedule

Image
A read-only overview of every planned payment in the pledge. Shows the number, date, status (e.g. Planned, Paid, Failed) and amount for each occurrence. You can change the date or amount of an individual payment, or delete a specific occurrence, directly from this list.

Duration

Image

Set or change the start and end dates of the pledge. Adjusting the duration will add or remove planned payment occurrences from the schedule. Leave the end date open to create an open ended (no end date) pledge.

Specific payment date

Image

Change the date of one particular payment without affecting the rest of the schedule. Use this when a single occurrence needs to be rescheduled (for example, to avoid a public holiday) while leaving all other dates in place.

Frequency

Image

Change how often payments are due, for example, from monthly to fortnightly, or from weekly to annually. Changing the frequency will recalculate and regenerate the planned payment dates from the next unpaid occurrence onwards.

Series of payments

Image

Update the amount for a group of future payments in one go. Use this when the donor has agreed to a new regular amount and you want all remaining planned occurrences updated together.

Specific payment

Image

Change the amount for a single occurrence without affecting any other payments in the schedule. Useful when one instalment differs from the regular amount (for example, a partial payment arrangement).

Payment method

Image

Update how the donor pays — for example, switch between credit card, direct debit, or manual payment. If the pledge is auto-collected through a payment gateway (Stripe, GoCardless, Ezidebit), this also controls which saved payment token is used for future collections.

Allocations

Image

Assign or update the account code, campaign, or pledge drive that this pledge's payments should be tracked against. This controls how payments are categorised in financial reports and how they reconcile against pledge-vs-actual targets.

Cancel Pledge

See Cancelling a Pledge for more information

Delete Pledge

See Delete Pledge for more information


Things to note

  • Start and end date restrictions are enforced
  • Pledges are split when required (amount, frequency, and allocations from a specific date)
  • Paid and scheduled items cannot be modified
  • Payment method restrictions on successfully scheduled items are enforced
  • Changes to the pledge token record also update the related pledge date records
  • An error is returned if a requested change is not permitted
  • Lastly, the importer and reports are not affected by these changes