Two Accepted LinkedIn Bookings Swapped Invite-Delivery Receipts: Verify Both Attendees

A swapped receipt is a record-matching failure. Two bookings may both show an accepted status while the evidence for invitation delivery points at the other attendee or event.

Start by freezing attendance assumptions. Keep the booked time intact unless the event record itself is wrong, but stop treating either receipt as proof of delivery for a named attendee.

Google Calendar lets an organizer view guest response status on an event. A response is attached to the event and guest record, so the attendee address and event identifier must agree before it can support an attendance assumption. Google Calendar Help

Which record fields must match before a receipt belongs to a booking?

Build the check around immutable or provider-issued identifiers first. Names and meeting titles are useful for review, but they are weak matching keys when two bookings have similar titles or occur close together.

For each booking, capture the booking-system record ID, attendee email as submitted, calendar event ID, organizer account, scheduled start time with timezone, provider event ID, receipt ID, receipt recipient, event version or sequence where available, and current RSVP status.

Google Calendar event records include event ID and attendee fields, plus response status and event sequence fields. Microsoft Graph attendee records likewise identify the attendee email address and response status. Google Calendar API reference Microsoft Learn

• Use the attendee email address as the expected recipient binding.
• Use the calendar event ID and provider event ID to identify the intended meeting.
• Keep receipt IDs separate from RSVP and attendance fields. They answer different questions.

How do you build a booking-to-invite receipt ledger?

Create one row per booking, not one row per receipt. Then attach the receipt currently associated with that booking and test whether every expected binding matches.

Use the ledger as the change record. Do not overwrite the original association without retaining the prior receipt ID and the reason for correction.

The values below are field instructions, not sample evidence. Enter the exact IDs from the booking system, calendar provider, and delivery provider.

How should you correct swapped invite-delivery receipts?

First, compare both possible mappings. A correction is justified only when Booking A's attendee and event identifiers align with Receipt B, while Booking B aligns with Receipt A.

Update the internal evidence binding or booking metadata after that comparison. Do not change a guest's RSVP status merely to make the records look consistent.

If the calendar event or guest list was wrong, fix that source record. Google Calendar says organizers can update guest events and choose whether to email invitations or updates. It also notes that guest calendars may update without an email in some cases, so record what you actually sent and what the provider returned. Google Calendar Help

• Preserve the original receipt ID and the correction timestamp.
• Record the operator and reason for the change, along with the system used.
• Send an update only when changes to the guest list or event details, including invite state, require it.
• Do not infer delivery from a corrected internal label. Retest it.

Which reminder and attendance assumptions must be reset?

Reset both attendees to unknown until the retest is complete. This applies to invite delivery and to reminder receipt or attendance. An accepted response is not the same thing as proof that a reminder was delivered or that the person attended.

For Google Calendar guests, event reminders are based on each guest's own settings. Non-Google Calendar guests can receive the notifications set for the event or selected in their calendar service. That means a reminder outcome must be checked for the relevant attendee and calendar service, not copied from the other booking. Google Calendar Help

If the scheduling provider exposes its own event and webhook records, use those records to reconcile the booking with the calendar event. Calendly documents REST API and webhook support for Scheduling data, but its documentation does not establish delivery for a specific recipient. Calendly Developer Documentation

What does a clean retest look like?

Retest one booking at a time. Confirm that the booking record points to the intended calendar event, the intended attendee appears on that event, and the delivery evidence names the same recipient and provider event.

Then review the response status in the calendar record. Google Calendar supports Yes, No, and Maybe responses, while Microsoft Graph exposes attendee response status. Record the status exactly as returned rather than translating it into an attendance prediction. Google Calendar Help Microsoft Learn

Close the incident only when both ledger rows have verified bindings, an auditable correction record where needed, and separate retest results.