A Monday morning ACH file can expose a CEF's weakest operating assumptions quickly. Two church loan payments may post as expected, while an investor note disbursement fails and the treasury analyst has to determine whether the entry was consumer or business, which authorization supported it, and whether the payment should be re-originated or allowed to return. The question isn't whether the money moved. It's which ACH payment type was used, whether that type matched the underlying relationship, and what the code permits the operations team to do next.
For a Church Extension Fund, ACH classification affects loan collections, investor distributions, donor contributions, escrow transfers, reconciliation, and audit evidence. The ACH network processed 21,585 million commercial transactions in 2025, with a total value of $47.101 trillion, according to the Federal Reserve's annual ACH data. CEFs may operate within a specialized ministry-focused niche, but their payment controls sit on one of the largest payment rails in the United States.
Why ACH Payment Type Choices Matter in a CEF
A CEF file can contain church loan debits, investor note disbursements, escrow transfers, and donor contributions at the same time. Their ledger amounts may look similar, but the ACH payment type determines the authorization evidence, account classification, return handling, and audit trail required for each entry.
A payment from an individual church officer's personal account may require a consumer code and consumer authorization. The same loan payment drawn from a church operating account may be a business entry supported by the loan agreement. The relationship behind the account, not the department requesting the payment, determines the correct classification.
Operational rule: Select the SEC code from the account relationship and authorization evidence. Never select it from the requesting department.
CEF operations must keep these relationships distinct. An individual can hold an investment note, a congregation can borrow for construction, and a denominational entity can receive an escrow transfer. Donors may authorize contributions through a different channel again. Treating every debit as a generic ACH transaction leaves staff unable to prove why the entry was permitted or how it should be handled after a return.
The Federal Reserve's national payment data shows that ACH activity has grown substantially, making disciplined classification an operating requirement rather than a technical preference. Correct coding supports reliable loan-subledger posting, accurate investor statements, cash forecasting, and defensible evidence for auditors and examiners.
CEF leadership should test whether staff can explain why an entry used PPD instead of CCD, or WEB instead of TEL. If they cannot, the process has a control gap. The code belongs in the payment request, linked to the authorization record, and preserved through file creation, settlement, return handling, and reconciliation. In 2026, fraud monitoring and standardized labels make that traceability even more important for daily CEF operations.
How SEC Codes Define ACH Payment Type
A Standard Entry Class, or SEC, code identifies how an ACH entry was authorized, whether it involves a consumer or business account, and what supporting data may accompany it. For a Church Extension Fund, that classification connects the payment file to the underlying relationship: a church loan payment, investor note disbursement, escrow transfer, or donor contribution. The Nacha ACH rule highlights identify consumer-facing codes such as PPD, WEB, and TEL, while business-to-business debits use CCD.
Before treasury approves a batch, require four answers:
- Whose account is being debited or credited? Identify an individual, church, corporation, or CEF-controlled account.
- Is the account treated as consumer or business? The account holder's legal and operating relationship controls the classification, not the requesting department.
- How was authorization obtained? Written recurring authorization, online consent, telephone authorization, and a business contract support different codes.
- Does the entry need remittance detail? Loan numbers, investor identifiers, and allocation instructions may require a code with addenda capacity.
PPD generally fits consumer credits and debits supported by a standing authorization. Examples include a recurring debit from an individual's account for a church loan payment or a payment to an individual investor. A repeated payment does not automatically qualify. The authorization must support the transaction pattern.
CCD applies to business accounts and depends on a contractual relationship permitting ACH activity. It can fit a church loan payment, an escrow movement, or a vendor payment when the account and agreement support that treatment. Extensive remittance information may call for CTX rather than CCD.
SEC code decision factors
| Decision Factor | PPD, Consumer | CCD, Business |
|---|---|---|
| Account classification | Individual or consumer account | Church, nonprofit, corporation, or other business account |
| Authorization basis | Consumer authorization, often recurring | Written agreement, loan note, or contractual authorization |
| Typical CEF use | Recurring consumer loan debit or investor payment | Church loan payment, escrow movement, or vendor payment |
| Remittance need | Limited entry detail | Use CTX when extensive remittance information is required |
| Primary control | Match the debit to the consumer authorization | Match the entry to the business agreement and account |
The file specification should require the requestor to identify the account type, authorization source, and remittance requirement. Preserve those fields with the authorization record through file creation, settlement, returns, and reconciliation. A payment can be expected and still carry the wrong authorization classification.
Consumer-Facing SEC Codes Used in CEF Operations
A consumer ACH entry can represent a church loan payment, an investor distribution, a donor contribution, or a note purchase. The correct SEC code depends on the account classification, the authorization channel, and the way the CEF created the entry. Treat those fields as operating controls, not file decoration.
PPD is the standard choice for recurring consumer debits and credits. It can support a church loan payment drawn from an individual's account under a standing authorization, or recurring interest paid to an individual investor, when the authorization and account treatment match. A repeating transaction does not, by itself, justify PPD. The authorization must permit the recurring activity.
WEB applies when the consumer authorizes the entry through an online channel. It fits donor contributions submitted through a CEF portal or investor note purchases initiated online, provided the authorization clearly identifies the debit, date, and amount. Retain the online authorization details with the transaction record and confirm that the file classification matches the channel used.
TEL supports a consumer debit authorized by telephone. For example, a church may call after missing a scheduled payment and approve a one-time catch-up collection. Record the call, authorization, and required disclosures. Do not use TEL to imitate a standing recurring arrangement that should use PPD or a properly configured WEB process.
Consumer code selection
| SEC Code | Authorization | CEF Use Case | When to Avoid |
|---|---|---|---|
| PPD | Written or otherwise valid recurring consumer authorization | Recurring church loan debit or investor interest credit | Avoid when authorization was collected only through an online session or phone call |
| WEB | Online consumer authorization | Portal-based donor contribution or investor note purchase | Avoid when staff initiated the transaction by phone or from a paper instruction |
| TEL | Recorded or documented telephone authorization | One-time catch-up debit after a church staff call | Avoid for routine recurring debits without call-specific authorization |
| ARC | Eligible paper check converted to ACH | Signed check from a donor church or investor note purchaser | Avoid when the check is ineligible for conversion or required notice was not provided |
| RCK | Re-presentment of an eligible returned paper check | Redepositing a bounced or rejected paper check | Avoid as a substitute for new authorization or an ordinary ACH debit |
ARC and RCK are check-conversion tools, not general-purpose consumer codes. Preserve the check image, notice, transaction context, and return history. For a recurring obligation, PPD or WEB generally gives the CEF a cleaner authorization trail and more reliable control than repeatedly converting paper instruments. Use the Nacha rule highlights as a reference when validating SEC-code treatment and authorization procedures.
Business-Facing SEC Codes Used in CEF Operations
A church borrower's operating account, a denominational entity, a vendor, and an internal treasury account are business relationships. For these CEF transactions, the authorization should come from a loan note, participation agreement, treasury agreement, or vendor contract. Classify the account and business purpose before choosing the ACH payment type.
CCD is the standard choice for a business credit or debit. Use it for a church loan payment from the church's operating account, a vendor payment, or an escrow transfer between business accounts when ordinary entry information is sufficient. Keep the agreement and account classification with the transaction record.
Use CTX when the receiving party needs detailed remittance information. A CEF might send a loan number, investor note reference, construction draw allocation, or several posting instructions with one payment. CTX supports multiple addenda records, but the receiving institution and the CEF's posting workflow must be able to read and reconcile them. Choose CTX for a documented remittance need, not because it offers more fields.
CCDI covers an inbound business entry initiated by another originator for the CEF. Treasury should verify the originating arrangement, agreement, company identification, and file mapping before the item reaches the subledger. An unexplained inbound entry belongs in exception review, not automatic posting.
| SEC Code | Direction | Addenda Allowed | Typical CEF Use Case |
|---|---|---|---|
| CCD | Credit or debit | Standard addenda capability | Church loan debit, vendor payment, or escrow transfer |
| CTX | Credit or debit | Multiple remittance records | Investor or loan batch with allocation detail |
| CCDI | Inbound business entry | Depends on the arrangement and file format | Third party initiates a business payment for the CEF |
Business entries still require control. The CEF needs a valid agreement, correct account classification, restricted file access, and evidence that each entry matched its stated purpose. Reconcile the SEC code, amount, counterparty, and addenda details before releasing the item for posting.
ACH Settlement Timing and Same-Day Windows for CEFs
Settlement timing drives when a CEF can post cash, release an investor distribution, or update a church borrower's payment status. Standard ACH generally settles on the next banking day, while Same Day ACH can settle on the same day when the entry is eligible and submitted within the applicable operator window. The Federal Reserve FedACH processing schedule identifies a later Same Day ACH processing window with settlement at 6:00 p.m. ET, while standard items not eligible for same-day processing settle at 8:30 a.m. ET on the next banking day.
That timing should be built into the cash forecast, not left to the file operator's memory. A routine loan collection can use standard processing. A time-sensitive investor redemption or urgent borrower payment may justify Same Day ACH, but only after treasury confirms the cutoff, available cash, return exposure, and posting procedure.
Nacha launched Same Day ACH in 2016 as the faster option for sending and receiving funds on the same banking day, according to its ACH payments fact sheet. The Federal Reserve reports that same-day debit transfers grew 39% per year by value from 2018 to 2021, while same-day credit transfers grew 21% per year by value over that period, as shown in its payments study.
For a practical explanation of why files miss expected posting dates, use this ACH settlement timing guide. The rule is simple: schedule the file around the settlement date, then reconcile actual posting rather than assuming the effective entry date equals available cash.
Fees and Cost Modeling by ACH Payment Type
Fee modeling should separate origination, returns, and exception handling. Consumer entries often carry different pricing from business entries because the operating and return environment differs by transaction family. Exact pricing comes from the CEF's ODFI or processor, so finance should use contracted rates rather than generic assumptions.
A useful model starts with the payment population. For a portfolio of 200 monthly church loan debits, multiply the contracted CCD origination fee by the number of entries, then add expected return fees and staff time for corrected account information. A separate investor program may combine PPD credits for routine distributions with CTX entries where remittance detail is needed. Same-day credits should be approved only when the timing benefit outweighs the added fee and control burden.
| SEC Code Family | Origination Range | Return Fee Range | Same-Day Surcharge |
|---|---|---|---|
| Consumer, PPD, WEB, TEL, ARC, RCK | Use the ODFI contract | Use the ODFI contract | Use the ODFI contract |
| Business, CCD, CTX, CCDI | Use the ODFI contract | Use the ODFI contract | Use the ODFI contract |
The verified operating data here supports the network's scale, settlement rules, and Same Day ACH limit, but it doesn't establish universal fee ranges. Don't copy a fee figure from another institution into the CEF budget. Ask the ODFI for separate prices by SEC family, return type, same-day processing, file correction, and exception support, then compare those costs with the staff hours required by manual reconciliation.
Authorization, Recordkeeping, and Audit Trail Requirements
Authorization evidence should be retrievable from the underlying loan, investor, donor, or vendor record. An auditor will want to know who authorized the entry, which account was covered, what amount or recurring instruction was permitted, when consent was obtained, and whether the submitted entry matched that permission.
For PPD, retain the signed recurring authorization or other valid consumer authorization. For WEB, retain the completed electronic consent, the displayed debit language, transaction date and amount, timestamp, and relevant access information such as the IP log. TEL requires a recording or documented record of the telephone authorization and the disclosures provided during the call.
ARC and RCK require careful handling because the source instrument is a paper check. Preserve the check image, conversion notice, eligibility determination, and return history. CCD authorization should connect to the signed loan agreement, debit clause, participation agreement, or vendor contract that permits the business entry.
Evidence checklist by code
- PPD: Store the recurring authorization against the investor or loan record.
- WEB: Preserve the electronic consent, presented terms, timestamp, and IP evidence.
- TEL: Retain the recorded call or approved call record with the required disclosures.
- ARC and RCK: Keep the check image, notice, and evidence supporting conversion or re-presentment.
- CCD and CTX: Link the entry to the business agreement and preserve any remittance mapping.
| SEC Code | Authorization Form Required | Retention Period | CEFCore Storage |
|---|---|---|---|
| PPD | Recurring consumer authorization | Follow applicable Nacha and institutional retention policy | Signed authorization attached to the account record |
| WEB | Electronic consent with transaction details | Follow applicable Nacha and institutional retention policy | Consent record, timestamp, and IP log |
| TEL | Recorded or documented oral authorization | Follow applicable Nacha and institutional retention policy | Audio or call record attached to the account |
| ARC | Check conversion notice and eligible paper check | Follow applicable Nacha and institutional retention policy | Check image and conversion evidence |
| RCK | Evidence supporting eligible re-presentment | Follow applicable Nacha and institutional retention policy | Original return and re-presentment record |
| CCD or CTX | Signed business agreement or contractual clause | Follow applicable Nacha and institutional retention policy | Agreement and remittance mapping |
A CEF should test retrieval before an examination, not during one. Review security design reviews for financial services alongside the payment-control review, especially where authorization files, audio, and identity logs are stored across several systems.
2026 NACHA Fraud Monitoring and Standardized Labeling Rules
CEF originators need to treat ACH classification as part of the fraud-control environment. The 2026 changes described in NACHA's 2026 rule update overview require risk-based fraud monitoring processes for all non-consumer originators, third-party service providers, and many receiving institutions, with the final phase taking effect June 22, 2026.
The practical work starts with transaction risk. A CEF should define what makes a payment unusual for its portfolio, such as a new account, changed payment instructions, unexpected velocity, an unusual amount for the borrower, or a new beneficiary. Staff should document the review, record the disposition, and coordinate thresholds with the ODFI.
Standardized descriptions add another control point. The 2026 rules update requires specific entry descriptions such as PAYROLL for PPD wage credits and PURCHASE for certain WEB debits. The broader lesson for CEFs is that payment labels should help banks and account holders recognize legitimate activity. A donor contribution, investor redemption, and church loan debit shouldn't appear as indistinguishable internal abbreviations.
Read the 2026 NACHA rule changes with your ODFI and compliance officer. Then update templates, staff training, transaction screening, exception queues, and board reporting. A non-bank CEF can't delegate responsibility for knowing what its files mean.
Building, Returning, and Reconciling ACH Files
A controlled ACH lifecycle has identifiable owners. Loan or investor operations creates the approved payment batch. The CEF's origination system generates the NACHA file. The ODFI validates and submits it, the RDFI processes the receiving entry, and settlement moves the funds between institutions. Finance then reconciles the bank activity to the loan, investor, escrow, and general ledger records.
Returns need the same discipline. Common CEF return codes include R01 for insufficient funds, R02 for an account closed, R03 for no account or inability to locate it, R04 for an invalid account number, R07 for authorization revoked, R10 for a consumer claim of unauthorized activity, R29 for a corporate customer advising that an entry wasn't authorized, and R85 for an incorrectly coded outbound international payment.
NACHA's 2025 Operations Bulletin explains that a same-day processing window can return an original transaction even when that original wasn't a Same Day ACH entry. It highlights administrative returns such as R02, R03, and R04, which gives operations teams a faster path to correct account information.
| Return Code | Meaning | CEF Scenario | CEFCore Action |
|---|---|---|---|
| R01 | Insufficient funds | Church loan debit lacks available cash | Flag for collection review and borrower notice |
| R02 | Account closed | Borrower changed banks without updating instructions | Stop repeat origination and request new authorization |
| R03 | No account or unable to locate | Routing and account combination fails | Hold re-origination pending verified details |
| R04 | Invalid account number | Data-entry or account-format error | Correct source data and require approval |
| R07 | Authorization revoked | Consumer withdraws permission | Suspend the instruction and review replacement authorization |
| R10 | Consumer advises unauthorized | Individual disputes the debit | Escalate compliance review and preserve evidence |
| R29 | Corporate customer not authorized | Church or business denies the entry | Check agreement, approval, and account classification |
| R85 | Incorrectly coded outbound international payment | Entry is treated incorrectly for international activity | Stop resubmission and correct coding or payment rail |
Use a documented return workflow that separates administrative repairs from collection activity. A practical ACH payment processing workflow should include reconciliation reports, controlled auto-resubmission flags, and borrower or investor notifications that show the original entry, return reason, and next action.
Authoritative ACH References Every CEF Should Bookmark
A CEF operations team needs three reference points, each serving a different purpose. Nacha provides the operating rules, bulletins, and SEC-code guidance. The Nacha rules and resource library is the right place to verify rule language and implementation dates.
The Federal Reserve FedACH Service supplies operational material, including settlement schedules, processing windows, fee information, and holiday calendars. Use the FedACH resource center when treasury needs to validate timing.
MACHA, the Mid-Atlantic ACH Association, provides practical education for operations staff, including webinars, templates, and compliance discussions. Its ACH operations resources can help smaller non-bank originators translate rule changes into procedures.
| Source | Primary Use for CEFs | Bookmark Path |
|---|---|---|
| Nacha | Rule text, bulletins, SEC-code guidance | Nacha rules and resource library |
| Federal Reserve FedACH | Settlement timing, schedules, and operations | FedACH resource center |
| MACHA | Training, templates, and peer education | MACHA operations resources |
Assign one staff member to review all three sources quarterly and route material changes to treasury, compliance, IT, and the audit committee.
CEF ACH Payment Type Quick Reference
Use this as a workstation reference, not as a replacement for the governing rule or your ODFI agreement. The correct code still depends on the account relationship and authorization evidence.
| CEF Use Case | Preferred Code | Authorization | Settlement Choice | Cost Control |
|---|---|---|---|---|
| Church loan from consumer account | PPD | Recurring consumer authorization | Standard unless timing requires same day | Use routine processing |
| Church loan from business account | CCD | Loan agreement or business authorization | Standard for planned collections | Reconcile returns promptly |
| Online donor contribution | WEB | Online consent | Same day only when justified | Validate portal records |
| Phone-authorized catch-up debit | TEL | Recorded or documented call authorization | Submit within the available window | Don't turn one-time calls into recurring instructions |
| Investor distribution with detail | CTX | Business agreement where applicable | Match the promised funding date | Use addenda only when needed |
| Escrow transfer | CCD | Internal business authorization | Standard planned settlement | Segregate and reconcile accounts |
| Paper check conversion | ARC or RCK | Required check notice and eligibility evidence | Follow conversion rules | Preserve check and return records |
The decision shortcut is concise: consumer account, PPD or WEB; business account with detail, CTX; standard business account, CCD; check conversion, ARC or RCK; telephone initiation, TEL.
ACH Payment Type Questions CEF Teams Ask Most
When should a CEF use Same Day ACH for an investor redemption? Use it when the investor is closing on a property purchase or facing another time-sensitive transaction, and the operational value justifies the added processing cost and return exposure. Don't make same-day service the default for routine distributions.
What if a church loan debit returns R01 after the CEF already credited its master account? Treat the credit as provisional until the return risk has cleared. Review whether an available administrative return path applies, then pursue collection under the loan agreement when it doesn't. Document the event for the CEF's fraud-monitoring process.
Can one originator routing number support both consumer and business codes? Yes, but the ODFI agreement must list the codes being used, and each authorization template must match its SEC classification.
Should staff use ARC or RCK for in-church check scanning? ARC is for an eligible original check conversion. RCK is for eligible re-presentment after a returned check. TEL authorization should preserve the required call record, while CTX should be reserved for business payments where remittance detail is operationally useful.
CEFCore supports ACH and NACHA file generation, SEC-code handling, return workflows, loan payments, investor distributions, and escrow transfers in a unified financial platform. Visit CEFCore to see how those controls can connect payment operations with loans, investor notes, cash management, and reconciliation.
