Invoices
Route: Finance → Invoices (/finance/invoices)
This page answers one question: who owes what, and how late is it? It lists every booking with an open or recently settled bill, broken down into its individual payment steps (the deposit instalments and the final payment), with a due date, an amount, what has been paid, and a status for each. A summary strip and a receivables-by-age bar sit above the list so you can see the total exposure before you scroll a single row.
Who can access this: requires the Bookings permission (view). Amounts, the KPI strip, the receivables-by-age bar, and both exports additionally require the Booking payments (read) permission — see Amounts and permissions below.
Invoices page with KPI strip, receivables by age, filters, and the payment-step table
Payment steps and terms of payment
Each row is a booking; open it to see its payment steps — the schedule generated from the booking's Terms of Payment (for example a 30% deposit and a 70% balance). The last step always absorbs whatever the earlier ones didn't cover, so it works as the "final payment" even though it isn't labelled differently from the others.
Every step shows the booking's own invoice number — Gurita doesn't generate a separate invoice per instalment, so a three-step schedule shows the same number three times, on the step where that document was actually issued to the guest.
Note: A booking with no payment schedule at all (no terms of payment applied) gets a single Full payment step for its whole balance, with no due date — it can never show as Due soon or Overdue, only Open, Partial, or Paid.
The summary strip
| Card | What it shows |
|---|---|
| Outstanding | The total still owed across every open payment step in the filtered set, with the number of open steps and bookings underneath. |
| Not yet due | Open amount whose due date hasn't arrived and isn't within the due-soon window yet. |
Due in N days | Open amount falling due within the due-soon window — N is your configured number of days. |
| Overdue | Open amount past its due date, with the step count and the age of the oldest one. |
| Paid | Amount already collected, with how many steps are fully settled. |
The strip and the Receivables by age bar below it (Not yet due / 1–30 days overdue / 31–60 days / 60+ days, plus how much has been collected this period) always describe the whole filtered set — every booking that matches your filters, not just the page you're looking at.
Status of a payment step
| Status | Meaning |
|---|---|
| Paid | Fully settled — nothing left to collect. |
| Overdue | Past its due date and still owes money. |
| Due soon | Falls due within the due-soon window and still owes money. |
| Partial | Part of the amount has been paid; the rest isn't due soon or overdue yet. |
| Open | Nothing has been paid yet, and it isn't due soon or overdue yet. |
A booking's own status badge takes the worst status among its steps — one overdue instalment marks the whole booking Overdue, even if its other instalments are paid. The Payment status filter's Open option matches both Open and Partial steps.
The due-soon window
The number of days that counts as "due soon" (used by the Due in N days KPI, the Due soon status, and the Due this week group on the timeline view) defaults to 7 days. An administrator can change it with the booking.dueSoonDays setting under Configuration, filtered to the booking group.
Filtering
| Filter | What it does |
|---|---|
| Payment status | All / Open / Due soon / Overdue / Paid — narrows the bookings shown to those with at least one matching step. |
| Date basis | Due date (default), Travel date, or Payment date — see below. |
| Date range | Combined with the date basis above. |
| Sort | Next due, Open amount, or Travel date. |
| Resorts / assets | Limit to one or more properties. |
| Booking state | Chips for Confirmed, Option / Hold, and Cancelled — these narrow the page's own default set (confirmed and cancelled bookings, plus options/holds that already carry an invoice), they don't widen it. |
| Search | Booking number, invoice number, customer, or agency. |
Date basis changes what the date range and sort apply to:
- Due date — the day each payment step is scheduled to be paid. This is what drives Overdue/Due soon.
- Travel date — the booking's arrival date, useful for "what do I still expect to collect before this month's departures".
- Payment date — when money was actually received, useful for "what came in last month".
Tip: The default date range covers every still-open payment step, regardless of date, plus anything due in the next 12 months — so an instalment from three years ago that's still unpaid stays visible even though it falls outside a "next 12 months" window.
The three views
Switch between Table, Board, and Due timeline above the list. Group by agency and Expand all / Collapse all apply to the table.
- Table — one row per booking (travel period, agency, customer, next due date, a schedule bar, total, and status); click a row to expand its payment steps.
- Board — four columns: Overdue, Due soon, Not yet due, Paid, each step shown as a card.
- Due timeline — payment steps grouped by horizon: Overdue, Due this week, Due later, Paid.
Warning: Board and Due timeline only show the bookings on the current table page — they do not describe your whole filtered set the way the KPI strip and the receivables-by-age bar do. If you've filtered down to hundreds of bookings, page through the table (or narrow your filters) before trusting what Board or Due timeline show. Switching to the Board view also drops the Payment status filter, so it always shows every status.
Amounts and permissions
Viewing the list itself only needs the Bookings permission — rows, travel dates, due dates, and status badges always show. Every amount (the KPI strip, the receivables-by-age bar, the booking and step totals) additionally requires the Booking payments (read) permission. Without it, those numbers are simply absent from the page rather than shown as zero.
The same rule applies to both exports, which additionally require Booking payments (read) — without it, exporting returns an error instead of a file.
Exporting
| Button | Where | What you get |
|---|---|---|
| Download | Top-right of the page | One row per booking. |
| CSV | Above the list | One row per payment step. |
Both carry every filter you currently have set — status, date basis and range, assets, booking state, and search — so the file matches exactly what's on screen.
Scale guard
If a filter matches more than 2,000 bookings, the page shows a banner ("Only the first 2,000 of N bookings are shown") and works from that capped set. Narrow the date range or your filters to bring the rest back into view.
