> ## Documentation Index
> Fetch the complete documentation index at: https://docs.go.aiinsurance.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Linking, Unlinking, or Moving an Invoice
> Change the event scope of an existing invoice
Change an invoice's event when unassigned activity has found its claim, the
wrong event was selected, or the invoice should no longer count toward an
event. Linking is a company-wide task because it moves activity into or out of
event scope.
## Before You Move an Invoice
Open **Financials → Event Financials** and locate the invoice in the company-wide
list. Add an Event Name filter or search by invoice number when needed.
Check the invoice's current:
* Event Name;
* status and recorded payments;
* Invoice Type, especially whether it is Loss/Recovery; and
* destination event's reserve position when payments will move.
The event's own Financials tab does not show Link or Unlink because every row is
already scoped to that event. Return to the company-wide list to change scope.
## Link or Move to an Event
1. Select one or more invoices in **Company Event Financials**.
2. Select **Actions → Link**.
3. In **Relink Invoices**, choose the **Destination event**.
4. Review how many invoices will move and how many are already linked to that
event and will be skipped.
5. Select **Relink Invoices**.
The same action covers both cases: an unlinked invoice becomes linked, and an
invoice already linked elsewhere moves to the selected event. A policy-linked
invoice in the selection moves off the policy and onto the event.
### When Recorded Payments Move
A paid or partially paid invoice cannot simply point somewhere else because
its payment activity belongs to its current event. The app completes the move
as one composed change:
1. remove each recorded payment from the current link;
2. relink the invoice; and
3. re-record the same payment amounts, dates, and memos against the
destination.
For Loss/Recovery invoices, the dialog checks the destination event's reserves.
If the destination cannot cover an eroding payment, the warning explains that
the excess will be recorded without eroding reserves. Adjust the destination's
expected totals first if that is not the intended result.
Read the destination and reserve warning before confirming. The invoice may end
with the same status and paid amount even though the event-level reserve and
payment history have moved.
## Unlink an Invoice
Use unlinking when the invoice should remain valid but should not count toward
an event or policy.
1. Select the invoice or invoices in **Company Event Financials**.
2. Select **Actions → Unlink**.
3. Review the confirmation. Already-unlinked invoices are skipped.
4. Select **Unlink Invoices**.
If an invoice has payments, unlinking performs the same remove-and-re-record
composition. With no destination event, those re-recorded payments cannot erode
reserves and post as additional incurred activity.
## Verify the Result
After the action finishes, the app reports updated, skipped, and failed counts.
Failed rows remain selected so you can correct the problem and retry.
Confirm that:
* **Event Name** shows the destination, or an em dash after unlinking;
* the invoice status and paid amount are correct;
* the source event no longer includes the invoice in its totals;
* the destination event includes it after a link or move; and
* reserve balances reflect the choice shown in the dialog.
For the distinction between an event link and a payee, see [Invoice to Entity
Linking](/financials/attaching-invoices).