Track an ACH transaction from the initial API response through batch processing and any subsequent return.

For API transactions, a successful Create Transaction API response confirms the initial submission of one ACH transaction.

For file-based transactions, you will submit all transactions and can use the Processed File to confirm a successfull submission.

After Submitting an ACH Transaction

A successful ACH submission via API or file-based confirms that TabaPay accepted the transaction for processing. It does not confirm final ACH settlement.

An ACH transaction may still be returned after it has been successfully processed. Returns are reported in the ACH Return File.

ACH API Transactions

For API transactions, use Retrieve Transaction API to retrieve the current transaction status.

• BATCH: TabaPay has received the payment request(s), but the transaction has not been processed.
• COMPLETE: TabaPay has received the payment request(s) and submitted batch to the banks.

See ACH Transaction Statuses for status details.

ACH API Processing Flow

The following flow shows how to track an ACH transaction from the initial API response through batch processing and subsequent reporting.

flowchart TD
    A["1. Create Transaction API"]
    B["2. Status: BATCH"]
    C["3. ACH Cut-Off"]
    D["4. TabaPay Batch Processing"]
    E["5. Status: COMPLETE"]
    F["6. Bank Processing"]
    G["7. Transactions (Daily) Report"]
    H{"8. ACH Return Reported?"}
    I["9. Exceptions (Daily) Report"]
    J["10. No Return Reported Yet"]

    A --> B
    B --> C
    C --> D
    D --> E
    E --> F
    F --> G
    G --> H
    H -->|Yes| I
    H -->|No| J

1. Create Transaction: Submit the Create Transaction API request. A successful response returns a transactionID and status: BATCH.
2. BATCH: TabaPay has accepted the transaction, but it is waiting for the applicable processing window. Use Retrieve Transaction API to check the status. You can also find the transaction listed in the TabaPay Portal.
3. ACH Cut-Off: TabaPay processes transactions according to the ACH processing and cut-off times.
4. TabaPay Processing: The transaction is processed and sent to the ODFI as part of the ACH batch.
5. COMPLETE: TabaPay has completed batch processing. This does not confirm final settlement or prevent a subsequent return. Use Retrieve Transaction API to check the status. You can also find the transaction listed in the TabaPay Portal.
6. Bank Processing: The ACH transaction continues through the banking network.
7. Transactions Reporting: Review ACH transaction activity in the Transactions (Daily) report.
8. ACH Return received? Choose one
9. Yes --> ACH Returns: Review the Exceptions (Daily) report for subsequent ACH returns.
10. No --> ACH Successful: When an ACH transaction is successful (No return file), you can find it in the Transactions (Daily) with a Complete status.

File-Based Transactions

For file-based transactions, use the Processed File to confirm whether TabaPay accepted or rejected the transaction for processing. If available, the Output File provides bank processing information.

Review the Processed File

The Processed File identifies which transactions were accepted or rejected during TabaPay ACH processing.

Review the file after the applicable processing window. A rejected record includes the corresponding processing result or error information.

Review the Output File

The Output File provides downstream bank-processing information when available. It is delivered after bank processing, and may include additional values like the traceID, or unique bank specific values.

ACH File-Based Processing Flow

flowchart TD
    A[1. Submit ACH Input File] --> B[2. ACH cut-off]
    B --> C[3. TabaPay processing]
    C --> D[4. Processed File]
    D --> E[5. Bank processing]
    E --> F[6. Output File, if available]
    F --> G{7. Return received?}
    G -- Yes --> H[8. ACH Return File / Exceptions Report]
    G -- No --> I[9. No return reported yet]

1. Input File: Submit ACH transactions through SFTP.
2. ACH Cut-Off: TabaPay processes transactions during the applicable ACH processing window.
3. TabaPay Processing: TabaPay validates and processes the submitted transactions.
4. Processed File: Review transactions accepted or rejected by TabaPay.
5. Bank Processing: Accepted transactions are processed by the originating bank.
6. Output File (If Available): Review bank processing information, including the ACH Trace Number when available.
7. ACH Return Received?
8. Yes --> ACH Return: Review subsequent returns in the ACH Return File or Exceptions (Daily) report.
9. No --> ACH Successful (No Return): When an ACH transaction is successful (Not in return file), you cam find it in the Transactions (Daily) with a Complete status.

For file formats, refer to ACH via Batch File Exchange.

Monitor for Returns

ACH processing does not prevent a later return from the receiving financial institution.
For ACH transactions, returns can appear in the Exceptions (Daily). ACH Return Files are also available to display any returned transactions.