ACH Rejects and Collections Export Data

The ACHRejectsCollects export file details failed ACH transactions (rejects) and associated collection activity. It is used to identify and manage unsuccessful fund transfers, trigger recovery workflows, and ensure unsettled transactions are tracked through to resolution. Each record carries a NACHA return reason code, the dollar amount impacted, and whether the entry affects residual income calculations.

Endpoint

GET /download/YYYYMMDD/ACHRejectsCollects

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Use this file when reconciling failed ACH entries and determining which merchants require corrective action. Process it alongside the ACH file to identify entries that were submitted but subsequently returned by the receiving bank. The AchCode field identifies the specific NACHA return reason, which determines whether re-presentment is permitted and what follow-up action is required.

Query Parameters

None. The file is identified by the date path segment (YYYYMMDD) and delivered via SFTP.

Response

200 OK — Returns XML content with the following structure:

XML Hierarchy: ACHRejectsCollects > Data > ACH

<ACH> fields:

Common NACHA Return Codes:

<?xml version="1.0" encoding="utf-8"?>
<ACHRejectsCollects xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Data>
    <ACH>
      <MID>9180000000001234</MID>
      <Type>Reject</Type>
      <Category />
      <AchCode>R01</AchCode>
      <Amount>-843.50</Amount>
      <Date>2026-05-27T00:00:00</Date>
      <Note />
      <AchDescription>Insufficient Funds</AchDescription>
      <ReportPeriod>2026.05</ReportPeriod>
      <ExcludeFromResiduals>No</ExcludeFromResiduals>
    </ACH>
    <ACH>
      <MID>9180000000005678</MID>
      <Type>Collect</Type>
      <Category>Collections</Category>
      <AchCode>R02</AchCode>
      <Amount>-215.00</Amount>
      <Date>2026-05-27T00:00:00</Date>
      <Note>Second collection attempt</Note>
      <AchDescription>Account Closed</AchDescription>
      <ReportPeriod>2026.05</ReportPeriod>
      <ExcludeFromResiduals>Yes</ExcludeFromResiduals>
    </ACH>
  </Data>
</ACHRejectsCollects>

Error Codes

Common Mistakes

• Confusing Type: Reject with Type: Collect — a reject means the bank returned the ACH; a collect means a recovery attempt was initiated.
• Not checking NACHA rules before re-presenting a returned entry — codes R07 and R10 prohibit re-presentment; always verify the applicable re-initiation rules.
• Ignoring ExcludeFromResiduals: Yes — these entries must be omitted from agent/partner residual income calculations.
• Using Date alone for period reporting — always use ReportPeriod (YYYY.MM) for grouping, as the reporting period window does not align with calendar months (rejects run 10th–9th; collects run 13th–12th).

Related Endpoints

• GET /download/YYYYMMDD/ACH — base ACH deposit records
• GET /download/YYYYMMDD/Transactions — transaction-level data for reconciliation
• GET /download/YYYYMMDD/Chargeback — chargeback records (separate from ACH rejects)

Example

curl -X GET "https://hq.staging.netevia.dev/download/20260528/ACHRejectsCollects" \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"