There is currently no reliable way to know if an invoice is associated with a specific appointment via the API. When building unified payment reports, we end up with duplicate entries because the same transaction appears both as an appointment payment and an invoice.

We need an explicit field (e.g. appointment_id on the invoice, or invoice_id on the appointment) so developers can deduplicate correctly without relying on fragile heuristics like matching by contact + date + amount.