Immediate batch responses

A description of the Immediate batch response and the Immediate batch response plus reports.

Immediate Batch Response

The immediate batch response (also referred to as an IBR) is a proprietary report that acknowledges accepted claims and identifies rejected claims due to HIPAA edits and payer-specific edits (PSEs) that Availity conducted on behalf of payers. The report also includes claim counts and charges at the claim level and file level. Only claims that passed file format and syntax validations are included in this report.

Note: The IBR and IBRP are the same report with the exception that the IBRP includes payer-specific warning messages that Availity relays on behalf of the payer. You only need to select one immediate batch report.
File extensions

  • .IBR (delimited file) – This is the default format.

  • .IBT (human readable text file)

  • .277IBR – 277CA claim acknowledgement format.

When is this response file sent?

Within minutes after transmission or up to 24 hours depending upon the volume of claims processing at that time.

  • Immediate batch responses are sent only for claims, not non-claim transactions.

  • This is an optional response file.
Additional details

  • Availity generates the IBR after an accepted (A), accepted with errors (E), or a partial accepted (P) Implementation Acknowledgement (999) has been posted to your ReceiveFiles mailbox.

  • If any errors display in this report, you can correct the claims, rebatch them, and resubmit them. This response file benefits you because it allows you to correct problems without having to wait for the payer to finish processing the rest of the transmission file.

  • Unless your administrator selected grouping options, each IBR represents one ISA – IEA. If a file contains multiple ISA – IEA, Availity generates an IBR for each ISA – IEA.

  • Rejected claims on the IBR also appear as rejected claims on the electronic batch report (EBR).

  • Availity does not generate or return an IBR in the following situations:

    • If the complete batch file rejected on a negative ACK, TA1 or 999 file.

    • If the batch file contained non-claims transactions (27x.).

Next steps

For every claim identified as rejected in the IBR, you must correct the errors in your EDI transactions system or practice management system, rebatch the claims with a new interchange control number, and upload the new file to Availity again. Claims that contain no HIPAA-compliance errors or payer-specific errors are routed to the payer.

Immediate Batch Response Plus

The immediate batch response plus (also referred to as an IBRP) is a proprietary report that acknowledges accepted claims and identifies warning messages and rejected claims due to HIPAA edits and payer-specific edits (PSEs) that Availity conducted on behalf of payers. The report also includes claim counts and charges at the claim level and file level. Only claims that passed file format and syntax validations are included in this report.

Note: The IBR and IBRP are the same report with the exception that the IBRP includes payer-specific warning messages that Availity relays on behalf of the payer. You only need to select one immediate batch report.
File extensions

  • .IBRP (delimited file) – This is the default format.

  • .IBTP (human readable text file)

  • .277IBRP – 277CA claim acknowledgement format.

When is this response file sent?

Within minutes after transmission or up to 24 hours depending upon the volume of claims processing at that time.

  • Immediate batch responses are sent only for claims, not non-claim transactions.

  • This is an optional response file.
Additional details

  • Availity generates the IBRP after an accepted (A), accepted with errors (E), or a partial accepted (P) Implementation Acknowledgement (999) has been posted to your ReceiveFiles mailbox.

  • If any errors display in this report, you can correct the claims, rebatch them, and resubmit them. This response file benefits you because it allows you to correct problems without having to wait for the payer to finish processing the rest of the transmission file.

  • Unless your administrator selected grouping options, each IBRP represents one ISA – IEA. If a file contains multiple ISA – IEA, Availity generates an IBRP for each ISA – IEA.

  • Rejected claims on the IBRP also appear as rejected claims on the electronic batch report (EBR).

  • A warning on a claim is informational content from Availity on behalf of the payer and can be added to an accepted or rejected claim. Warnings are informational only and do not cause a claim to be rejected.

  • Warnings are only available on the IBRP and not IBR.

  • Availity does not generate or return an IBRP in the following situations:

    • If the complete batch file rejected on a negative ACK, TA1 or 999 file.

    • If the batch file contained non-claims transactions (27x.).

Next steps

For every claim identified as rejected in the IBRP, you must correct the errors in your EDI transactions system or practice management system, rebatch the claims with a new interchange control number, and upload the new file to Availity again. Claims that contain no HIPAA-compliance errors or payer-specific errors are routed to the payer.