AMIPI INC — ACH Generator

Sign in to access the payment system

Chase CCD Credits · NACHA File Specifications
All records: 94 characters fixed-width

AMIPI INC — Chase ACH NACHA Generator

Chase CCD Credits · Multi-batch · Vendor Book
File Header — Company Info
Discretionary data: — Set by the server configuration (ACH_COMPANY_NAME / ACH_COMPANY_ACCOUNT), not per file.
Letters, digits and spaces. Not PAYROLL, REVERSAL, NONSETTLED, RECLAIM, RETRY PMT or RETURN FEE (CCD credits).
Every batch in the file settles on this date (written as YYMMDD). Weekends and Federal Reserve holidays are not allowed.
Assigned by the server: A for the day's first file, then B, C… so no two files sent on the same day share one.
Assigned automatically when the file is generated, so numbers never repeat. Only an administrator can choose the starting number.
Invoice details for the vendor's bank Optional CCD addenda (record 7, up to 80 characters). Off by default, like every file sent so far; payments without an invoice number get none.
Chase Specification: dest=021000021  ·  origin=0000000000  ·  DFI=02100002  ·  SEC=CCD
Payment Entry (Batch 1)
Drop payment spreadsheet here or click to browse
Excel (.xlsx) or CSV (.csv), up to 10 MB. Legacy .xls files must be re-saved as .xlsx.
payments.xlsx (12 KB)

Enter manual payments for Batch 1 below. Click + Add Row to add more. Every batch in the file settles on the same effective date.

Settles on — · the file's Effective Entry Date, set in File Header
# Vendor * Routing # Account # Type Amount ($) * Invoice / Ref # * Remove
Duplicate Transactions Detected in Batch 1
These rows match payments already recorded in the system. Nothing was generated.
    0
    Total Rows
    0
    Valid Rows
    0
    Validation Issues
    $0.00
    Total Credit Amount
    0
    Total Rows
    0
    Valid Rows
    0
    Validation Issues
    $0.00
    Total Credit Amount
    Duplicate Transactions Detected
    One or more payment rows match existing transactions previously uploaded to the system.
    Row Validation Issues 0 issue(s)

    The following rows could not be parsed as valid payments and were skipped:

    Row # Raw Data Validation Errors
    Parsed Valid Payments (Batch 1) Staged · not yet in a file
    # Payee / Vendor Name Routing # Account # Amount ($) Invoice / Ref # Status Action
    Manual Payment Entry (Batch 2)

    Enter payment rows below. Click + Add Row to add more. Every batch in the file settles on the same effective date.

    Settles on — · the file's Effective Entry Date, set in File Header
    # Vendor * Routing # Account # Type Amount ($) * Invoice / Ref # * Remove
    Duplicate Transactions Detected in Batch 2
    These rows match payments already recorded in the system. Nothing was generated.
      0
      Total Rows
      0
      Valid Rows
      0
      Validation Issues
      $0.00
      Total Credit Amount
      Adds another manual entry batch below.
      Generate Combined Chase NACHA File

      Combines all valid payments from Batch 1 (spreadsheet or manual entry), Batch 2 and any added batches into a single Chase CCD credit NACHA file (94 characters fixed-width per record, 10-record block padded).

      Manual batches are recorded only when the file is generated; if anything fails, nothing is kept.
      NACHA Flat File Output
      —
      Generated & Verified
      0
      Credit Entries
      0
      Total Batches
      0
      Total Blocks (10x)
      $0.00
      Total Credit Amount
      0000000000
      Entry Hash (Chase Checksum)
      —
      File Record ID
      NACHA 94-Character Fixed-Width Line Preview All records padded to 94 chars
      
      
                  
                  

      Edit Payment Item Details

      Vendor Directory & Bank Details
      View registered vendors and submit bank detail change requests for approval.
      Pending Bank Detail Change Requests
      0 change request(s) awaiting admin review.
      0 Pending
      0 Vendor(s) Selected Admin action: Permanently remove selected vendors from database
      Payee / Vendor Name Vendor Email Routing Number Account Number Account Type Status Actions

      Request Bank Change

      CURRENT REGISTERED BANK DETAILS
      Routing #: —
      Account #: —
      Account Type: —

      Edit Vendor Profile

      Stored in full. The bank file uses the first 22 characters. Renaming changes which spreadsheet rows match this vendor.
      Remittance advice is sent here. Leave blank if unknown: no advice is sent rather than guessing an address.
      Written in the ACH ID field of every payment to this vendor. Leave blank to use the invoice number (one invoice) or the last 5 digits of the account (several invoices).
      Set status to Active or Inactive. Inactive vendors are preserved in directory for history and audit tracking.
      Access Denied Admin authorization is required to access the Change Request Review Panel. Standard users cannot review, approve, or reject vendor bank detail change requests.
      Admin Review — Vendor Bank Detail Change Requests
      Review pending bank detail change requests. Approvals mutate database vendor records and log to AuditLog. Rejections leave records unchanged.
      0 Pending
      Pending Requests Awaiting Decision
      # Vendor Name Requested By Bank Details (Current → Requested) Reason / Notes Status Admin Action
      User Accounts & Access Control
      Provision new user accounts, manage roles, toggle activation status, and reset user passwords.
      0 Users
      # Username Email Address Role Status Created Date Admin Actions
      Access Denied Admin authorization is required to access the Security Audit Trail. Standard users cannot view security activity logs.
      Security Audit Trail & Activity Logs
      Immutable audit logs of all batch uploads, NACHA file generations, bank approvals, profile updates, and email dispatches.
      Timestamp (ET) User Action Event Target Entity Details / Audit Payload

      Payment History — Last 12 Months

      0 records
      0
      Payments
      0
      Vendors
      $0.00
      Total paid
      Filter by Range (Months & Amount)
      0 transaction(s) selected Total: $0.00
      Payment Remittances
      # Eff Date Vendor Name Recipient Email Amount ($) Invoice / Ref # Sequence # Generated By Status Ready (ET) Actions
      Showing 0 records
      Page 1 of 1

      Mark Remittance Advices Ready

      Email delivery is not set up yet
      Nothing will be emailed. The advices for the selected vendor(s) below will be marked Ready, to be sent from your own mail program. Vendors with no email on file are skipped.
      Selected: 0 vendor(s), totaling $0.00.
      Downloadable Spreadsheet Import Templates
      Download pre-formatted import templates matching our system's spreadsheet parsing specifications. Routing and account columns are formatted to preserve leading zeros.
      Payment Import Template (.csv / .xlsx)
      Pre-formatted structure for Batch 1 payment uploads. Pre-populates sample rows with valid ABA routing numbers, account numbers, amounts, and invoice references.
      Columns: Vendor Name, Routing Number, Account Number, Account Type, Amount, Invoice Number
      Vendor Master Import Template (.csv / .xlsx)
      Template for bulk importing vendor directory records into the Vendor Master Book.
      Columns: Vendor Name, Routing Number, Account Number, Account Type, Payee Reference (optional), Email
      Remittance Advice Email Template
      Customize the automated payment confirmation emails sent to vendors when ACH payments are processed.
      Click a variable button to insert automatic payment information into your template:
      Note: The Tabular Form Method of Payment & Sub-Invoices Table with itemized breakdown is automatically placed between the invoice intro and the closing sign-off.
      From: ap-remittance@amipi.com
      To: ap@samplevendor.com
      Subject: Payment Remittance Advice — SAMPLE VENDOR INC ($53,413.06)
      —
      System Usage Guide & NACHA Rules
      1. Batch 1 Upload & QuickBooks Support:

      Supports QuickBooks Desktop payment exports (.xlsx) and standard tabular files (.csv, .xlsx). The parser extracts vendor names, amounts and invoice numbers and matches them against active Vendor Book entries. Payments always go to the bank account on file; a row whose routing/account columns disagree with the Vendor Book is rejected. Only administrators can add a new payee from a spreadsheet.

      2. Manual Payment Entry (Batch 1 manual mode, Batch 2 and added batches):

      Enter payments for vendors already in the Vendor Book. Every batch settles on the file's single Effective Entry Date. Duplicate checking flags identical payments (same vendor, amount, invoice ref and effective date); overriding requires ticking "Allow Duplicate Override" for that batch, and resets after each run.

      3. Combined NACHA Transmit File Specifications:

      Generates 94-character fixed-width NACHA flat files complying with Chase CCD Credit specifications. Automatically computes entry counts, batch counts, block counts, entry hash checksums, and total credit amounts.

      4. Vendor Directory & Bank Detail Change Approvals:

      Standard users see bank details masked to the last 4 digits and submit change requests. Bank detail updates enter a PENDING state and take effect only after an administrator approves them in Admin Review. Adding, editing, merging and deleting vendors is administrator-only.

      5. Transaction History & Remittance Email Notifications:

      All payment transactions record vendor remittance entries. Users can filter by vendor, status, or date range, select multiple items, and trigger bulk email dispatches with an explicit confirmation step.

      Field Technical Specifications & Validation Rules
      Field Name NACHA Standard Validation & Formatting Rules
      Routing Number 9 Digits Must be a valid 9-digit ABA routing number passing the Modulus 10 checksum algorithm (e.g., 021000021).
      Account Number Up to 17 Chars Must preserve leading zeros. In spreadsheets, format account cells as TEXT to avoid truncation.
      Account Type Checking / Savings Transaction code 22 for Checking credits; transaction code 32 for Savings credits.
      Invoice / Ref # 15 chars in the file Stored and shown in full (up to 80 characters) for remittance matching. The bank file carries the first 15 letters and digits, upper-cased; other characters are dropped.
      Reserved Keywords Disallowed Chase CCD Credit guidelines strictly prohibit reserved terms PAYROLL and REVERSAL in entry descriptions.

      Itemized Invoice Breakdown

      Sub-bill line items contributing to total payment amount
      # Sub-Invoice # Invoice Date Amount ($)

      Add Vendor(s) to Master Book

      Stored in full (up to 120 characters). The bank file uses the first 22.
      Written in the ACH ID field of every payment to this vendor. Leave blank to use the invoice number (one invoice) or the last 5 digits of the account (several invoices).
      Need a format template?
      Download our standardized import template with pre-formatted column headers.
      Supported columns: Vendor Name, Routing Number, Account Number, Account Type, Payee Reference (optional), Email.
      Duplicate Detected

      Update Existing Vendor?

      An existing record was found in the Vendor Book for — with modified details.
      Proposed Field Changes:
      Admin Authorization: Overwriting sensitive banking details (routing/account) will update the vendor directly and generate an immutable audit log entry.

      Review Bulk Vendor Import

      Review detected new vendors and proposed updates to existing vendor master records.
      0
      New Vendors
      0
      Existing Updates
      0
      Unchanged (Skipped)
      0
      Row Errors
      Detected Modifications: Changes to existing vendors
      Vendor Name Field Current Value New Value Type

      Confirm Permanent Deletion

      Are you sure you want to delete the selected vendor(s) from the directory? This action will remove them from future payment batches.

      Transaction History Protection: All past payment history, remittances, and audit records related to this vendor will remain safely preserved and intact in Payment History.

      Review Duplicate Vendors Before Merging

      History is preserved: payments, remittances and change requests belonging to a removed record are re-linked to the record that is kept. Only the duplicate vendor row itself is deleted.

      Delete Payment Record

      Are you sure you want to delete this payment record?

      Generated NACHA Files

      Downloads are recorded in the audit trail. Mark a file as uploaded once it is with Chase; until then an administrator can cancel it.
      Generated NACHA files, newest first
      File Created (ET) Effective Entries Total By Status Actions
      Loading…

      Cancel NACHA File

      Cancelling — releases its payments and batches so a corrected file can be generated. The file can no longer be downloaded; its File ID Modifier and trace numbers stay used.

      Change Password

      At least 8 characters, not only spaces. Your other signed-in sessions will be signed out.

      Last Generated NACHA ACH File

      94-Character Line Formatted Chase ACH Flat File Payload
      File Name —
      Creation Date/Time —
      Total Credits $0.00
      Entry Count 0
      Entry Hash —
      Loading NACHA content...

      Remittance Email Template Settings

      Customize corporate email formatting and sub-invoice tabular layout
      Note: The Tabular Form Method of Payment & Sub-Invoices Table is automatically placed between the invoice intro and the closing sign-off.
      Dynamic Placeholders (Click to insert):
      Subject: Payment Remittance Advice
      From: ap-remittance@amipi.com  ·  To: ap@samplevendor.com

      Reset Email Template?

      Are you sure you want to reset to default?
      This will restore the standard default email wording and automatically save the template. Any custom text or edits will be replaced.

      Remittance Advice Email Preview

      Viewing email sent to vendor
      Recipient:
      Subject:
      Status:

      Provision New User Account

      Create a new user account with specified system role.

      Reset User Password

      Set a new password for this user.