Invoices

Every invoice in the organization. Administrators only , this is the whole membership's payment history plus revenue aggregates, so it is treated as a financial surface rather than an operational one. Dispatchers get the per-reservation invoice instead.

Bills a member for something that isn't a flight , a checkout fee, a headset, a late cancellation. Line items are validated against the organization before anything is written.

For billing a completed flight, use POST /reservations/{id}/invoices instead: it prices the booking from the meters you recorded.

One invoice with its line items. An aircraft owner from outside the organization reads only their own bills, and gets what they need to read and pay one: its number, dates, status, memo, lines with their tax, totals, how a desk payment came in (paymentMethod, checkNumber, paymentReceivedOn), the payment and PDF links, and the work order it is for. Not the organization's QuickBooks sync state, its note about the payment, or which of its staff raised, voided or marked it paid. billTo (name, billing address, phone, email) is on the bill for the person billed and for administrators.

Send markPaid: true to record a payment taken outside the card flow, optionally saying how: paymentMethod, checkNumber (only with check), paymentReceivedOn (the day it arrived, YYYY-MM-DD; today in the organization's calendar when left out, never in the future) and paymentNote. Stripe is told the invoice was paid outside it, and the person billed is sent a receipt. Or send markVoided: true. Payment fields without markPaid are refused. Requires the admin role.

Takes exactly the body of POST /invoices and answers what that call would charge: each line with its sales tax, the organization's service fee line, tax per rate, and the total. Nothing is written and Stripe is not called. The same permission as creating the invoice.

Send the total back as expectedTotal on the create to be sure nothing moved in between.

Revenue and outstanding totals for a window, in cents, with the counts behind them. Administrators only, like the list.

Takes the same startDate, endDate and q as GET /invoices, so it describes exactly the invoices that endpoint would return , except paid, which narrows the list but not this. Use it instead of adding up a list you fetched: lists are capped at 1,000 rows, so summing what you received would give you the total of an arbitrary thousand invoices for any organization with more than that.

The vendor's invoice, a receipt, an 8130-3 attached to the bill. url works for 15 minutes. Administrators read every file; the person billed reads only the ones shown to them (visibility: owner). Anybody else is answered 403, as for an id that is not this organization's.

Send fileNames (up to 5 per request; jpg, png, heic or pdf), visibility (shop by default, owner to show them to the person billed) and a label for a single file. The answer has the new rows in data and, in the same order, signedUrlData: a presigned POST for each file, which the client posts the bytes to. An invoice holds up to 30 files. Requires the admin role. Refused in the demo.

Emails the member about an outstanding invoice. Requires the admin role.

Your own, or anyone's if you are an administrator.

The bill for one flight. Dispatchers can read this even though they cannot list the organization's invoices.

Its label, or who it is shown to (visibility). Requires the admin role.

It stops listing; the stored object is kept. Requires the admin role.

Copies the work order's files onto the invoice raised for it: every one not already there, or those named in fileIds. Each keeps its label and who it is shown to. Nothing is uploaded. Requires the admin role. Refused in the demo.

What the flight comes to, broken down, without creating an invoice.