> For the complete documentation index, see [llms.txt](https://docs.loopit.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loopit.co/bookings/lifecycle-of-a-booking/editing-a-booking/backdating-end-dates.md).

# Backdating End Dates

{% embed url="<https://www.loom.com/share/d2131655947f48658c38bf0fc89fac2c>" %}

Backdating end dates in Loopit allows you to finalise a booking even after the vehicle has already been returned. This ensures your records reflect the real-world hand-back date, helping you maintain accurate utilisation and billing.

You can select a drop-off date that falls either within the current billing cycle or up to 30 days prior (or back to the original start date if sooner).

***

### When to Use Backdated End Dates

This functionality is useful when:

* A customer returned a vehicle earlier than scheduled
* The booking wasn’t ended in Loopit at the time of return
* Operational delays or corrections require a more accurate end date

No matter the scenario, Loopit will always respect historical availability to prevent overlapping bookings.

***

### What Happens When You Select a Past Drop-Off Date

#### If the date is within the current billing cycle

Loopit will calculate any unused days and give you the option to:

* **Issue a Credit Note** for the unused portion of the current cycle, or
* **Proceed without crediting** if charges are handled another way

#### If the date is before the current billing cycle

You will see a message explaining:

* The invoice for the current cycle will be **cancelled**
* Any required adjustments to earlier billing cycles should be **managed manually**

This ensures you retain full control over complex or multi-cycle billing changes.

***

### How to Apply a Backdated End Date

1. Open an **Active** recurring booking
2. Select **Mark as Ended**
3. Choose a past **Drop-off Date**
4. Review the message shown
5. Confirm to complete the update

***

### Helpful Tips

* Review the **Billing** tab to understand what charges may be affected
* Apply credit notes only where they are operationally required
* Keep customers informed if billing corrections change their fees