---
title: "Event Payments: deposits, instalments and balances | Havenue"
description: "Quotes and invoices raised from the event, deposits and balances with due dates relative to the event date, and a branded payment page your client opens on a phone. Card payment is handled by Stripe and card details never touch Havenue. The same money state shows inside the event and in Finance."
canonical: https://havenue.co/features/payment-management/
markdown: https://havenue.co/features/payment-management.md
language: en
last_updated: 2026-07-27
---
# Know who owes what, and by how many days

Quotes and invoices raised from the event. Deposits, instalments and balances with due dates that move when the event date moves. A branded page your client pays on their phone.

Money in, joined to the event it came from. Set menus times guests at your configured prices become a quote, the quote becomes an invoice, the invoice carries a schedule, and every payment that arrives is matched against it. The same state shows in Finance and inside the event, because they are reading the same record.

## The problem this solves

You are invoicing a £25,000 wedding out of a spreadsheet. The deposit went in three weeks ago and you think the balance is due a week before, but the event moved, and now nobody is sure. So either somebody spends the morning reconstructing it, or the money sits uncollected. Both are expensive.

## How it works

1. **Raise it from the event** : Set menus times guests at your configured prices, with a minimum-spend line where it applies. Fully editable before you send.
2. **Plan how it gets paid** : A deposit, instalments, and a balance. Due dates can be relative to the event date, so "balance due 7 days before" stays true when the date changes.
3. **Send a link they can use** : A branded page your client opens on a phone. Card payment is handled by Stripe and card details never touch Havenue. Sent to the wrong client? Kill the link.
4. **Watch it land** : Payments arrive against the schedule. Bank transfers and cash are recorded by hand and clearly marked as such, never conflated with a card payment.

## What you get

- **Money states in real words** : "On its way", "Received", "Part refunded". A payment on its way says bank transfers take a few days, because money already coming is not money to chase.
- **Margin on either question** : Margin against what the event was booked for, or against what the client has actually paid. On a booked but unpaid event those are wildly different and both are legitimate.
- **A link you can cancel** : Payment links can be seen and killed. Sent to the wrong client, or the event was cancelled? The link stops working.
- **Card details never touch Havenue** : Your client pays on a branded page and card details never touch Havenue. Card collection is available to UK and EU accounts; UAE accounts get the whole billing suite except card collection, and the product says so on screen.
- **Documents your accountant can use** : Every document exports with net, tax and total kept separate, because they go to different ledger accounts, plus UBL 2.1 electronic invoices per document. Export-ready, not a compliance claim.
- **It shows up in the CRM** : Invoiced, paid, outstanding, billing status and next due date join the event grid you already filter and sort, and hide entirely from anyone without finance access.

## Who this is for

- Event managers
- Sales teams
- Finance
- Operations managers
- Owners
