The rule about void deadlines is designed around where the processing window is anchored. For IAR, the deadline is expressed in Eastern Time, providing a single, standard reference point for centralized processing. For GDS, the deadline uses the local time of the agency’s location, so the cutoffs align with the agent’s own business hours and time zone. This combination prevents cross‑time‑zone confusion: an IAR void must be submitted by the ET cutoff, while a GDS void must be submitted by the local-time cutoff of the station. If you’re working across time zones, this means you’ll convert accordingly to ensure you meet the correct deadline.

Liability protection in card-present sales hinges on having verifiable evidence of the cardholder's authorization. Obtaining an imprint of the card and a signature on the Universal Credit Card Charge Form provides concrete proof that the cardholder was present and approved the charge. The imprint captures the card data and confirms the card used matches the cardholder, while the signature confirms consent. Together, they create a defensible record against chargebacks because a dispute would have to argue that the cardholder did not authorize the transaction, which is supported by documented authorization and tangible evidence. Relying on the cardholder's email for authorization isn’t a reliable, verifiable record and can be forged or intercepted. Capturing only the card number without the name fails to tie the transaction to a specific cardholder and lacks essential identifying details. Requesting a secondary authorization from the issuer isn’t a standard method for preventing chargebacks and can’t replace the merchant’s own authorization record.

Document Retrieval Services is a secure, paperless record-keeping system that ARC-accredited agencies and participating carriers use to access IAR-reported ticketing data online. It provides immediate online access to a long history of data—specifically more than three years (39 months)—so agencies can quickly retrieve past ticketing records without handling physical documents. This focus on secure storage and fast retrieval distinguishes it from other functions like payments, airline schedules, or automatic report generation.

The concept here is how an IAR adjustment is used to handle leftover value from an exchange. When a ticket is exchanged, there can be a residual amount that isn’t returned to the passenger and isn’t issued as a separate Miscellaneous Charge Order (MCO). The IAR adjustment is the mechanism that records and reconciles that remaining value within the ARC settlement so the agency’s accounts reflect the correct balance. This is specifically about capturing that residual value in IAR rather than issuing it on an MCO or treating it as a routine tax adjustment, a class change, or a generic discount.

The concept here is how many PEDs can be actively online in the IAR system at once. The system is designed to support up to three PEDs concurrently online. This limit is set to keep processing stable and data integrity solid: with three active PEDs, the reconciliation, updates, and validation can run without excessive contention or delays. Allowing more than three would risk processing bottlenecks, timeouts, or data conflicts, which could compromise accuracy. Therefore, three is the maximum allowed online at any time.