ADM & ACM In-Depth: Top Causes, Dispute Workflows in BSPlink & ARC Memo Manager

How airline automated audit systems detect agency ticketing violations and the exact operational playbook for disputing debit memos.

Dr. Marcus Vance
Dr. Marcus Vance

Chief Research Architect & Airline Systems Specialist

Published: Sep 25, 2026
•
Updated: Oct 6, 2026
Information Verified: October 6, 2026•Next Audit: January 2027•Sources: IATA, ATPCO, ARC/BSP & Official Handbooks
Our Research Methodology
ADM & ACM In-Depth: Top Causes, Dispute Workflows in BSPlink & ARC Memo Manager
Key Architecture Takeaways
  • An ADM (Agency Debit Memo) is a financial claim issued by an airline to recover revenue lost due to travel agency ticketing errors or policy violations.
  • An ACM (Agency Credit Memo) is a credit issued by an airline to refund money owed to an agency (e.g. overpaid ADMs, commission adjustments, authorized exceptions).
  • Over 80% of ADMs stem from automated revenue accounting scans catching fare basis violations, incorrect tax collection, ticketing time limit (TTL) breaches, and uncollected change penalties.
  • Agencies have a strict dispute window under IATA Resolution 850m (typically 14 to 30 days) to challenge an ADM before automatic bank settlement deduction.

1. The Anatomy of an ADM vs. ACM

In the commercial aviation distribution chain, an Agency Debit Memo (ADM) serves as an invoice issued by an airline against a travel agency. Under IATA Resolution 850m, airlines use automated audit engines such as Amadeus Fare Expert, Sabre Ticket Audit, or SITA Revenue Accounting to scan 100% of ticketed coupons against filed ATPCO tariffs.

Conversely, an Agency Credit Memo (ACM) acts as an accounting credit. When an agency successfully disputes an erroneous ADM or when an airline authorizes an incentive rebate or manual refund adjustment, an ACM is credited directly to the agency's ARC or BSP settlement statement.

2. The Top 10 Root Causes of Agency Debit Memos

Airlines do not issue ADMs randomly; automated scrapers flag discrepancies according to strict rule triggers:

RankViolation CategoryTypical Trigger MechanismAverage Financial Severity
1Incorrect Tax CollectionFailing to collect new local airport departure taxes or miscalculating YQ/YR surcharges.$25 - $200 per ticket
2Cat 16 / 31 Change Fee UndercollectionReissuing a ticket without collecting the mandatory change penalty or miscoding the EMD.Full penalty ($150 - $400) + admin fee
3Booking Class / Fare Basis MismatchBooking inventory class Q but issuing ticket under lower priced class V.Full fare differential ($300 - $1,500)
4Ticketing Time Limit (TTL) BreachHolding confirmed segments past airline ticketing deadline.$50 per segment or segment cancellation
5Married Segment BreakageCircumventing origin-destination (O&D) married segment logic using unbundled booking tricks.Full fare differential to highest unbundled class
6Churning & Inactive Segment AbuseRepeatedly cancelling and rebooking identical flights to hold seats without ticketing.$10 - $25 per un-ticketed transaction
7Credit Card ChargebacksPassenger disputes fraudulent or unauthorized ticket charge through issuing bank.Full value of ticket + chargeback fee

3. Step-by-Step Dispute Playbook in BSPlink & ARC Memo Manager

When an ADM appears in BSPlink or ARC Memo Manager, the clock starts immediately. Under IATA Resolution 850m, agencies generally have 14 days (or up to 30 days depending on national market guidelines) to formally log a dispute with supporting documentation.

1. Initial Review: Verify the ticket number, issue date, and specific ATPCO rule cited in the memo.

2. Historical PNR Dump: Extract the GDS PNR history showing pricing commands (e.g. WPNCB in Sabre, FXP in Amadeus) proving automated GDS pricing was utilized.

3. GDS Guarantee Assertion: If the GDS automated pricing system priced the ticket and the agency did not alter the fare calculation string, file a claim under the GDS Fare Guarantee Policy to have the GDS pay the airline directly.

4. Submission in BSPlink / ARC: Submit the PNR history and e-ticket receipt with clear factual justifications before the settlement cutoff to freeze automated bank debit.

Topics:#ADM#ACM#Agency Debit Memo#Agency Credit Memo#BSPlink#ARC Memo Manager#Revenue Protection

Frequently Asked Questions

If an agency fails to dispute an ADM within the allowed window, the amount is automatically deducted from the agency's bank account during the next BSP or ARC direct debit settlement. Refusing payment can result in immediate loss of airline ticketing authority and IATA accreditation suspension.
Dr. Marcus Vance
About the Author

Dr. Marcus Vance

Chief Research Architect & Airline Systems Specialist

Dr. Marcus Vance has over 18 years of technical leadership in global airline reservation systems, inventory caching, and PSS migrations. He previously led core ticketing migration squads at major European carriers and regularly consults on IATA NDC and ONE Order transitions.

Verified Industry Credentials:
  • Ph.D. Distributed Systems (MIT)
  • Former Principal Architect at Amadeus IT Group
  • IATA Distribution Data Standards Contributor (14+ yrs)

Related Technology Guides