What is the same-day ACH cutoff in SinglePoint?

Same-day ACH submitted through SinglePoint must be fully authorized and released before 2:45 PM Eastern Time to settle the same business day. Batches submitted after the cutoff settle on the next business day. The 2:45 PM cutoff aligns with the NACHA third same-day ACH processing window. Treasury teams building time-sensitive vendor payments or late payroll corrections build approval workflows that complete well before the cutoff to accommodate approver availability.

How are ACH returns handled in SinglePoint?

ACH returns in SinglePoint arrive as NACHA return codes from the receiving bank — R01 insufficient funds, R02 account closed, R03 no account, R04 invalid account number, R05 unauthorized debit, R07 authorization revoked, R08 payment stopped, R10 customer advises not authorized, and additional reason codes. SinglePoint delivers returns to a dedicated dashboard where treasury operators review each item, re-originate corrected transactions, or contact the counterparty to resolve authorization disputes before re-submitting.

Does SinglePoint require dual authorization for ACH?

Yes. SinglePoint ACH origination requires dual authorization as a standard control. One operator prepares or imports the batch and submits it for approval, and a separate operator with the approver role reviews the batch totals, counterparty list, and effective date before releasing the file to the ACH operator. Batches above configurable thresholds require a third supervisor approval. Dual authorization aligns with OCC and NACHA operating rules for commercial ACH origination.

ACH Origination in SinglePoint — Batch Electronic Payments With Same-Day Settlement

ACH origination is the core payments module of SinglePoint. Treasury teams upload NACHA-formatted batches or enter transactions manually, schedule effective dates for same-day or next-day settlement, and release payments for dual authorization. The module handles credits for payroll, vendor disbursements, and tax payments, plus debits for customer collections under pre-authorized mandates.

Over 85,000 US businesses originate ACH through SinglePoint every business day. The same-day ACH cutoff of 2:45 PM ET processes late payroll corrections, urgent vendor payments, and last-minute tax filings. Recurring templates remove re-keying for periodic payments — once the counterparty is configured, only amount and date change between runs. NACHA returns route to a dedicated exception dashboard for correction and re-origination.

SinglePoint Login Guide Treasury Support

SinglePoint ACH origination dashboard showing pending NACHA batch, same-day cutoff timer, and dual authorization queue

ACH Origination in SinglePoint — Summary for Treasury Operators

NACHA file upload accepts batches generated by payroll, AP, or ERP systems with validation before submission
Manual entry interface for ad hoc payments, one-off refunds, and emergency tax deposits
Same-day ACH cutoff: 2:45 PM ET — all authorization must complete before the cutoff for same-day settlement
Next-day ACH: submissions after 2:45 PM ET settle the following business day through standard ACH processing
Recurring templates store counterparty, routing, account, and transaction code for repeat payments
Return handling: NACHA return codes R01–R99 route to a dashboard for review, correction, and re-origination
Dual authorization required on every batch; third supervisor approval triggers above configurable thresholds

NACHA File Upload

Upload a NACHA-formatted file produced by your payroll or AP system. SinglePoint validates the file header, entry class codes, routing numbers, and batch control totals before queueing for authorization.

Manual Entry

Enter individual transactions one at a time — useful for emergency wires, one-off refunds, or correcting a failed payment. Manual entries pass the same authorization controls as uploaded batches.

Recurring Templates

Stored templates release payroll, rent, and vendor payments on a schedule. Change only the amount and effective date; counterparty, routing, and account stay locked to prevent fraud.

API Origination

The SinglePoint API posts ACH transactions programmatically from ERP systems. OAuth 2.0 secures each request and payments flow through the same dual-authorization queue.

SEC Code	Description	Typical Use	Same-Day Eligible	Authorization Required
PPD	Prearranged Payment & Deposit	Payroll direct deposit, recurring consumer debit	Yes	Signed consumer authorization on file
CCD	Corporate Credit or Debit	Business-to-business vendor payment, tax deposit	Yes	Corporate trading agreement
CTX	Corporate Trade Exchange	B2B payment with structured remittance (EDI 820)	Yes	Corporate trading agreement
WEB	Internet-Initiated Entry	Online consumer payment, subscription billing	Yes	Online authorization + commercially reasonable verification
TEL	Telephone-Initiated Entry	Phone-authorized consumer debit	Yes	Recorded verbal authorization or written notice
ARC	Accounts Receivable Conversion	Converted paper check from lockbox or billing	No	Notice on invoice or statement
IAT	International ACH Transaction	Cross-border ACH with OFAC screening	No	Full OFAC and BSA compliance review
POP	Point-of-Purchase	In-person check conversion at retail	No	Written notice at point of sale

NACHA publishes SEC code definitions and origination requirements through NACHA operating rules. The Federal Reserve operates one of the two ACH operators that clear SinglePoint originations.

SinglePoint ACH batch upload interface with NACHA file validation, effective date selector, and approver queue

Batch Creation and Validation

Treasury operators prepare ACH batches two ways — upload a NACHA file from payroll or AP software, or enter transactions manually in SinglePoint. On upload, SinglePoint validates the file header, batch control records, entry detail counts, hash totals, and routing numbers against the Fedwire routing directory. Invalid routing numbers, malformed records, and control total mismatches surface immediately so corrections happen before submission. Large batches split into multiple file control records automatically. Operators tag each batch with an effective date — same-day if before 2:45 PM ET, next-day otherwise — and submit for approval.

BAI2 Export Reporting

SinglePoint dual authorization queue showing pending ACH batch with approver review pane and release button

Dual Authorization and Release

Every SinglePoint ACH batch routes to a dual-authorization queue. The approver sees batch total, counterparty count, largest single transaction, and any items flagged for review — new counterparty, amount exceeding a historical pattern, or OFAC hit on a name. Above configurable thresholds, a third supervisor approval adds another control layer. Once released, the batch transmits to the ACH operator and SinglePoint records the release timestamp, approver IDs, and IP addresses into an audit trail retained for seven years. Finance and compliance teams review the audit trail during internal audits and OCC examinations.

Positive Pay Details

SinglePoint NACHA return code dashboard showing R01 insufficient funds, R02 account closed, and corrective action workflow

Settlement, Returns, and Reconciliation

Same-day batches clear the ACH network the same business day and post to the counterparty account in the afternoon settlement window. Next-day batches post early the following business day. SinglePoint updates the cash position view as funds move, shifting memo-posted entries to posted status at settlement. NACHA returns — R01 insufficient funds, R02 account closed, R05 unauthorized debit, R10 customer advises not authorized — arrive within the NACHA return windows and land on the exception dashboard. Operators correct routing errors, re-originate after insufficient funds hold, or escalate disputed authorizations to compliance. All of it feeds into ERP integration so the AP ledger matches bank activity.

ERP Integration

R01 — Insufficient Funds

The receiving account lacked available balance. For debits, re-originate after verifying with the payer. For credits, this code shouldn't appear — contact the RDFI.

R02 — Account Closed

The counterparty account is closed. Update AP or payroll master data with a new account and re-originate the payment against the updated counterparty record.

R03 / R04 — Unknown Account / Invalid Number

Account number doesn't exist or fails routing validation. Verify the account number directly with the payer before attempting re-origination.

R05 — Unauthorized Debit to Consumer

A CCD debit landed on a consumer account. Re-originate as PPD with consumer authorization, or correct the classification in your AP system.

R07 / R10 — Authorization Revoked / Not Authorized

The consumer revoked or disputes the authorization. Stop recurring debits immediately, obtain fresh authorization, and consult compliance before re-originating.

R08 — Payment Stopped

The receiver placed a stop-payment order. Contact the counterparty to resolve the underlying dispute before attempting any re-origination of the debit.

Wire Transfers

Fedwire and SWIFT wire transfers for same-day domestic and 1-2 day international settlement with dual authorization.

Positive Pay

Check and ACH positive pay flags exceptions for review, with ACH whitelist to block unauthorized debits to your accounts.

Remote Deposit

Remote deposit capture via scanner or mobile app with duplicate detection and same-day morning posting.

Start Originating ACH Through SinglePoint

Finance teams across 85,000 US businesses run payroll, vendor payments, and tax deposits through SinglePoint ACH origination. Same-day cutoff at 2:45 PM ET. Follow the login guide to reach the origination console or call +1-877-272-2265 for implementation help.

What is ACH origination in SinglePoint?

ACH origination in SinglePoint initiates batch electronic payments through the Automated Clearing House network. Upload a NACHA file or enter transactions manually, tag an effective date, and release through dual authorization. Supported entry class codes include PPD, CCD, CTX, WEB, TEL, ARC, and IAT. See wire transfers for faster single-payment rails.

What is the same-day ACH cutoff?

Same-day ACH through SinglePoint must be authorized and released before 2:45 PM Eastern Time. Batches submitted after cutoff settle next business day. The 2:45 PM cutoff matches the NACHA third same-day processing window. Build approval workflows with buffer time so approvers complete reviews before cutoff.

How do recurring ACH templates work?

Recurring templates store counterparty, routing number, account number, and SEC code so only amount and date change between runs. Use templates for payroll, rent, lease payments, and repeating vendor invoices. Templates lock counterparty details so operators can't accidentally redirect a payroll to an unauthorized account.

How are ACH returns handled?

NACHA return codes route to the SinglePoint exception dashboard: R01 insufficient funds, R02 account closed, R03 unknown account, R04 invalid account number, R05 unauthorized consumer debit, R07 authorization revoked, R08 payment stopped, R10 customer advises not authorized. Operators review each item, correct counterparty data, and re-originate when appropriate.

Does SinglePoint ACH require dual authorization?

Yes. Every SinglePoint ACH batch requires dual authorization — one operator prepares or uploads, a separate approver releases after review. Batches above configurable thresholds add a third supervisor approval. Dual authorization follows OCC expectations for commercial payment controls and appears in the seven-year audit trail.