- Overview
- BIN-PCN for Routing Supplemental Transactions
- Part D Plans
- - Nx Reject Reports
- - Annual Report Distribution Email Setup and Changes after Annual Submission
- - Nx Realtime
- - Nx Update Process
- - Nx Replay Request
- - Nx History Request
- - FAQ
- - Nx Implementation and Testing
- - Business Associate Agreement (BAA)
- Supplemental Payers
- How are claims reversals handled with regard to generating an N2?
- How can I differentiate a TrOOP information reporting transaction (N) from other types of information reporting transactions?
How are claims reversals handled with regard to generating an N2?
How can I differentiate a TrOOP information reporting transaction (N) from other types of information reporting transactions?
For TrOOP Ns the request transaction header record will contain one of the following values in the Software Vendor/Certification ID field (110-AK):
- TROOP - to indicated the N was generated from supplemental B transactions
- TROOPBATCH – to indicate that the N was generated from an N transaction batch file provided by the supplemental payer