> For the complete documentation index, see [llms.txt](https://help.flowerbuddy.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flowerbuddy.co/reference/event-settings/payments-and-invoices/set-default-payment-schedule.md).

# Set a default payment schedule

The Default Payment Schedule defines the scheduled payment rows that should start in a new event. Use it to make common payment timing consistent while leaving room to adjust an individual event later.

The image below shows two payment rows with names, amounts, timing, and calendar events.

<div data-with-frame="true"><figure><img src="https://2616748322-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtdSEPutB4SrRwwUMOIx%2Fuploads%2Fgit-blob-160ad778f08cd8b3adfcac51284de11b58317542%2Fevent-settings-default-payment-schedule.png?alt=media" alt="The Default Payment Schedule shows a Scheduled Payments heading, an Add Scheduled Payment button, a Non-refundable Retainer row set to 25 percent due 0 days after Contract Signing, and a Final Payment row set to 30 days before Event Date." width="550"><figcaption></figcaption></figure></div>

## Add or edit a scheduled payment

1. Open **Event Settings** and select **Payments & Invoices**.
2. In **Default Payment Schedule**, select **Add Scheduled Payment**. Use the existing row controls to edit a payment already in the list.
3. Enter a payment **Name** that explains the purpose of the row.
4. Choose an amount as a percentage or a dollar amount.
5. Enter the number of **Due (days)**.
6. Choose **Before Or After**.
7. Choose the **Calendar Event** that anchors the due date.

The calendar event and before-or-after choice determine how FlowerBuddy calculates the date. For example, a payment can be due after **Contract Signing** or before **Event Date**.

The row saves as you finish editing its fields. Use the row's trash icon to remove a scheduled payment that should no longer be part of the defaults.

## Final payment

The final payment collects the remaining event balance after the other scheduled payments. Its amount and percentage are calculated, so those fields cannot be entered manually. You can still set its name and due-date rule.

If the schedule needs a final payment row, the add button reads **Add Final Payment**. Select it first. Once the final payment exists, **Add Scheduled Payment** adds payments before that final balance.

For example, a schedule with a 25% retainer leaves the remaining 75% for the final payment when there are no other scheduled payments. This is an example, not a required payment policy.

## Choose percentage or dollar amounts

Use the percent choice when the payment should scale with the event total. Use the dollar choice when the payment should be a fixed amount. Keep the rows and amounts consistent with the payment terms your workspace sends.

## Organize the schedule

Use clear names and an order that matches the sequence clients will see. Remove a row when it should no longer be part of the default schedule. A change to the default list affects future events created without an event template, not schedules already copied into existing events.