Generate U.S. Bank payment files without an ERP

To submit a generated file, yes — your business needs to be set up with U.S. Bank for ACH origination through either SinglePoint Essentials ACH (the SMB tier) or full SinglePoint (the corporate-and- commercial-banking tier), with a Company Identification value assigned, your funding account entitled for ACH origination, and the SinglePoint Essentials ACH service (or full SinglePoint ACH service, depending on your tier) activated as a service entitlement on your portal profile. PayFile Pro generates the file; your U.S. Bank enrollment as an ACH Originator is what authorizes you to upload it. U.S. Bank enrolls business customers in ACH origination through different paths depending on the tier: for SinglePoint Essentials ACH, the path is through a U.S. Bank business banker — most SMB customers can call the U.S. Bank business banker line (855-625-7354 is the published number for SinglePoint Essentials setup) and request that the SinglePoint Essentials ACH service be activated on top of their base SinglePoint Essentials profile. For full SinglePoint, the path is through U.S. Bank Treasury Management Sales — Treasury Management Consultants can be located through TreasuryManagementSolutions@USBank.com. If you’re not sure which tier you’re provisioned for, your existing U.S. Bank business banker can confirm and route accordingly. Note that a dedicated U.S. Bank business checking account is required to use SinglePoint Essentials (the base service is $17.95/month, with the SinglePoint Essentials ACH service activated as a service entitlement on top), and the credit-and-debit underwriting for ACH origination is conducted separately from the base SinglePoint Essentials enrollment — your business may be enabled for credit origination only, debit origination only, or both. Credit-only is the typical SMB starting point through U.S. Bank business banking onboarding, and is the scope PayFile Pro generates against.

Four values in the File Header and Batch Header of every U.S. Bank NACHA file need bank-specific attention, plus one service-tier configuration check (your SinglePoint Essentials ACH service profile entitlements) where U.S. Bank’s most common source of validation rejections lives.

• Immediate Destination — a 9-digit U.S. Bank ACH routing number placed in a 10-character field with a leading blank space. U.S. Bank uses state-based routing numbers inherited from over 160 years of acquisitions — Firstar Corporation (the 2001 merger that created today’s U.S. Bancorp), Mercantile Bancorporation (1999), Star Banc (1998), and most recently MUFG Union Bank in 2022/2023; the routing number for your account is the one for the state where the account was originally opened, regardless of where the business operates today. Common examples: 091000022 (Minnesota — U.S. Bank’s headquarters routing, used for the Personal Trust ACH service and as the default Minnesota routing), 122235821 (Southern California), 121122676 (Northern California — including former Union Bank California branches transitioned in 2022/2023), 122105155 (Arizona), 102000021 (Colorado — all areas except Aspen, which uses 102101645), 121201694 (Nevada), 071904779 (Illinois — Northern), 081202759 (Illinois — Southern), 074900783 (Indiana), 104000029 (Iowa — Council Bluffs, and Nebraska), 081000210 (Missouri — Eastern, with 101200453 for Western Missouri), 092900383 (Montana), 101000187 (Kansas), 107002312 (New Mexico), 123103729 (Idaho), and 091300023 (Minnesota — Moorhead, and North Dakota), and many more state-and-region variants across U.S. Bank’s 27-state footprint. You can look up the routing number for your specific account by signing in to U.S. Bank online banking or the U.S. Bank Mobile App under Account Settings → Account details, at the bottom of any U.S. Bank business check, in your SinglePoint Essentials portal under Information Reporting → Account Information, or by contacting your U.S. Bank business banker. Important cross-bank note: unlike Wells Fargo — which maintains a separate domestic wire-transfer routing number (121000248) distinct from its regional ACH routing numbers — U.S. Bank typically uses the same routing number for ACH and domestic wires on a given account, so the wire-vs-ACH-routing gotcha that’s a common Wells Fargo originator rejection cause doesn’t apply on U.S. Bank in the same way. Most U.S. Bank wire transfers and ACH transactions route through the same state-based ABA, with edge cases (some Trust services, some legacy Union Bank wire- specific routings during the transition window) confirmed account-by-account through your business banker. U.S. Bank does not publish a single canonical enumeration of all valid SinglePoint ACH routing numbers in their public NACHA spec — the U.S. Bank ACH Implementation Guide that documents the file format is gated through SinglePoint Service Documentation, so the routing number you use is the one tied to your specific account rather than a value selected from a published menu. PayFile Pro reads the U.S. Bank routing number you enter in the originator-details section of your XLSX template and inserts it into the File Header automatically.
• Immediate Destination Name — U.S. BANK or US BANK (uppercase, left-justified, blank-padded to 23 characters) — SinglePoint accepts either casing variant as long as the underlying routing number maps to U.S. Bank’s RDFI participant ID. The network-standard convention is uppercase without periods, and PayFile Pro defaults to US BANK to minimize cross-RDFI ambiguity downstream, but U.S. BANK (with periods) also passes SinglePoint’s validation.
• Company Identification — a 10-digit numeric value U.S. Bank requires in both the Batch Header Record (positions 41–50) and the Batch Control Record (positions 45–54). This is typically your business’s federal Tax ID prefixed with 1 (e.g., a Tax ID of 12-3456789 becomes 1123456789), or another 10-digit value U.S. Bank assigns when they enroll you for ACH origination through SinglePoint Essentials ACH service activation or full SinglePoint Treasury Management onboarding. The value has to match the Company Identification on file in your SinglePoint Essentials ACH service profile — a mismatch here is one of the more common batch-level rejections at upload. Confirm with your U.S. Bank business banker which value to use if you’re not sure.
• File ID Modifier — a single character A–Z or 0–9 that lets you distinguish multiple files originated on the same day. Unlike Wells Fargo (which offers a configurable File ID Modifier format restricted to digits-only, letters-only, or alphanumeric depending on how your Set-Up Forms locked the option), U.S. Bank SinglePoint accepts the network-standard single-character alphanumeric convention without customer-side configuration. PayFile Pro defaults to alphanumeric and increments the modifier on subsequent files originated the same day.
• SinglePoint Essentials ACH service profile entitlements — this isn’t a file-content field but a service-configuration check that determines whether SinglePoint will accept the file at all. Your SinglePoint Essentials ACH service profile records which Service Class Codes your business is authorized to transmit (SCC 200 mixed credit + debit batches, SCC 220 credits-only batches, both, or — for debit-only originators — SCC 225), what Company Identification values are valid for your account, what funding accounts are entitled for ACH origination, and what dual-control approval workflow is configured. On every file upload, SinglePoint validates the file’s salient characteristics against the service profile. If the file is SCC 200 but your profile is provisioned only for SCC 220, SinglePoint rejects it. If the Company Identification doesn’t match the value on your service profile, SinglePoint rejects it. If the file’s originator routing doesn’t match the value your account is associated with, SinglePoint rejects it. This is U.S. Bank’s analog to Wells’s Customer Application ID + processing-profile match (though SinglePoint’s profile-validation is structurally simpler than Wells’s Payment Manager Set-Up-Forms-driven model — there’s no transmission envelope ID layered on top of the file in the SinglePoint web upload case). The most common version of this rejection at U.S. Bank is “I activated SinglePoint Essentials but didn’t activate SinglePoint Essentials ACH as a separate service entitlement” — the base SinglePoint Essentials portal handles checking, wires, RTP, and Positive Pay out of the box, but ACH file upload is a separately-entitled service that has to be specifically requested through your U.S. Bank business banker. Confirm with your business banker that SinglePoint Essentials ACH is activated on your service profile and that the credit-origination underwriting has cleared and that the funding account you’re planning to use is specifically entitled, before submitting your first live file.

(Different US banks use different conventions for these fields. JPMorgan Chase requires PAYROLL-only- with-PPD in the Company Entry Description, a 20-digit Company Discretionary Data field containing your Chase funding account number, and one of 16 published Chase ABA routing numbers in the Immediate Destination. Bank of America maps the Vendor ID field in CashPro to the NACHA Identification Number field at Entry Detail Record positions 40–54 — placement is the most common BofA-specific source of field- mapping rejections — and uses state-based routing numbers inherited from legacy NationsBank / Fleet / LaSalle / Countrywide acquisitions. Wells Fargo requires a Customer Application ID and Transmission ID in the electronic transmission envelope, validates each transmission against a pre-defined processing profile built from your Payment Manager Set-Up Forms, offers a configurable File ID Modifier format (digits-only, letters-only, or alphanumeric), and uses regional ACH routing numbers inherited from legacy Wachovia / First Union / Norwest acquisitions — with a separate wire-transfer routing number (121000248) that’s a common rejection cause when mistakenly used in an ACH file. U.S. Bank routes files through either SinglePoint Essentials ACH (the SMB tier, provisioned through a business banker) or full SinglePoint (the corporate-and-commercial-banking tier, provisioned through Treasury Management Sales), distinguishes PAYROLL (wages, salaries, similar compensation) from PENSION (retirement benefit payments) at the Company Entry Description level per U.S. Bank’s published 2026 Operating Rule guidance PDF, validates each upload against your SinglePoint Essentials ACH service profile entitlements (Service Class Codes, Company Identification, funding-account eligibility), and uses state-based routing numbers inherited from legacy Firstar / Mercantile / Star Banc / Union Bank acquisitions across a 27-state footprint — with the same routing number typically valid for both ACH and domestic wires on a given account, unlike Wells’s split. PNC has its own bank- specific conventions for the Company Identification, Company Entry Description, multi-SEC-code batch handling, and originator- routing values — documented on PNC’s dedicated PayFile Pro page when it launches, or available from your PINACLE relationship manager today.)

U.S. Bank follows the NACHA network-level Company Entry Description conventions and surfaces one bank-specific distinction explicitly in their published 2026 Operating Rule guidance: the PAYROLL / PENSION split for PPD credits.

The Company Entry Description goes in Batch Header positions 54–63 and describes the purpose of the batch in a customer-entered value: PAYROLL, PENSION, ACH PMT, VENDOR PAY, BONUS, EXPENSE, or whatever short label fits the batch. As of March 20, 2026, NACHA requires the value PAYROLL in the Company Entry Description field of any PPD credit entry that pays wages, salaries, or similar compensation. U.S. Bank’s published 2026 Operating Rule guidance PDF adds a specific clarification on top of the network-level rule: “Originators should continue to use PENSION for retirement benefit payments.” This is a U.S. Bank- surfaced distinction worth getting right — PAYROLL is reserved for the wage-and-salary case (where the new network rule applies); PENSION is for retirement benefit payments (where the same Company Entry Description field describes a different purpose). Both are PPD credits to consumer accounts, but the Company Entry Description differs based on the underlying payment purpose. U.S. Bank’s PDF also names HCCLAIMPMT, REVERSAL, ACCTVERIFY, and RETRY PMT as additional Nacha-specific Company Entry Description values for the corresponding transaction types.

PayFile Pro defaults PPD payroll batches to PAYROLL in the Company Entry Description to satisfy the network rule. If you’re originating a retirement-benefit-payments batch through U.S. Bank, override the value to PENSION in the Company Entry Description column of your XLSX template before generating — both pass the NACHA spec; only one matches your batch’s purpose.

U.S. Bank has the most substantive bank-specific 2026 Operating Rule communications surface in the cluster. Their dedicated Nacha rule changes page on the corporate-and-commercial-banking site covers all four 2026 rule changes (Company Entry Descriptions effective March 20, 2026; Fraud Monitoring Phase 1 effective March 20, 2026; Fraud Monitoring Phase 2 effective June 22, 2026 — the practical compliance date since June 19 is the Juneteenth federal holiday; Funds Availability and IAT Definition Update both effective September 18, 2026), the 2027 IAT-contact registration and Date-of-Birth-field amendments, and the 2028 R16 / R90 return-code changes. The published PDF dated May 23, 2025 walks through fraud monitoring obligations for Originators, TPSPs, TPSs, and ODFIs in the detail format that’s useful when your business is documenting its risk-based fraud monitoring program ahead of the Phase 2 compliance date. This is meaningfully more bank-published rule-change content than is currently available from Wells Fargo (which hasn’t published a bank-specific 2026 page) or even Bank of America (which mentions the rule on their ACH page but without the dedicated multi-year-coverage page U.S. Bank maintains). If you’re running ACH credits through U.S. Bank, the bank’s own 2026 page is the right starting point for the compliance conversation, with your U.S. Bank Treasury Management contact (or U.S. Bank business banker for SinglePoint Essentials customers, with TCOSHelp@usbank.com as the published support email for ACH rule-change questions) as the right channel for implementation specifics. See the 2026 rule changes FAQ on the US ACH hub page for the full picture across PAYROLL, PURCHASE, the Phase 2 fraud monitoring deadline, funds availability for non–Same Day ACH credits, and the IAT scope update.

U.S. Bank operates two related cash management platforms that share the SinglePoint name and the underlying NACHA file format but are provisioned, priced, and accessed through different paths:

• SinglePoint Essentials — the SMB-tier cash management service. Costs $17.95/month, requires a dedicated U.S. Bank business checking account, and is provisioned through a U.S. Bank business banker (the published business banker line for Essentials setup is 855-625-7354). SinglePoint Essentials covers checking-and-balance reporting, statements, multi-user controls, fund transfers between U.S. Bank accounts, stop payments, Positive Pay, wire transfers, and ACH and instant payment initiation. ACH file upload is a separately-entitled service — SinglePoint Essentials ACH — that has to be specifically activated on top of base SinglePoint Essentials before you can submit a NACHA file. The credit-and- debit underwriting for SinglePoint Essentials ACH is conducted separately, with credit-only as the typical SMB starting point.
• Full SinglePoint — the corporate-and- commercial-banking-tier treasury management portal. Provisioned through U.S. Bank Treasury Management Sales (Treasury Management Consultants can be located through TreasuryManagementSolutions@USBank.com). Full SinglePoint covers everything SinglePoint Essentials covers plus international wire transfers and international ACH, foreign exchange trading, global trade activity, advanced fraud-mitigation services (IBM Security Trusteer Rapport, IP-address whitelisting, configurable approval workflows), connectivity options including ERP connectors and SFTP transmission, and broader API integration with U.S. Bank’s payment networks. Full SinglePoint is sized for mid-market and larger commercial customers; SMBs typically don’t need it.

The two platforms share the same underlying NACHA file format and the same SinglePoint ACH service architecture under the hood — a file that’s well-formed for SinglePoint Essentials ACH is also well-formed for full SinglePoint ACH, and vice versa — but the upload-surface workflow inside the portal, the per-tier underwriting boundaries for credit-versus-debit origination, the per-tier service entitlements (Positive Pay, RTP, international, etc.), and the provisioning path are different. The most common version of the U.S. Bank-specific tier-routing rejection is “I activated SinglePoint Essentials but didn’t activate SinglePoint Essentials ACH as a separate service entitlement” — the base SinglePoint Essentials portal handles checking, wires, RTP, and Positive Pay out of the box, but ACH file upload requires SinglePoint Essentials ACH as a specifically-requested service activation. The second most common version is “I assumed full SinglePoint was just an upgraded SinglePoint Essentials and tried to call the SMB business banker line for setup” — full SinglePoint goes through Treasury Management Sales, not the SMB business banker channel.

For PayFile Pro’s typical user (SMB, bookkeeper, or finance team running vendor payments and payroll through U.S. Bank without an ERP), the relevant tier is SinglePoint Essentials ACH. The path to get there: call your U.S. Bank business banker, confirm SinglePoint Essentials is active on your account, request that SinglePoint Essentials ACH service be activated as an entitlement on top, confirm which Service Class Codes (220 credits-only is sufficient for PayFile Pro’s scope; 200 mixed is needed if you also originate ACH debits), confirm the funding account is entitled for ACH origination, confirm the Company Identification value U.S. Bank has on file for your business, and complete the credit-origination underwriting. Once active, the SinglePoint Essentials ACH upload path is straightforward — PayFile Pro generates the NACHA file, you upload through SinglePoint Essentials → Payables → ACH → File Upload and submit, SinglePoint validates the file against your service profile, and (assuming dual approval is enabled) a second user releases the batch.

What makes the tier-routing question genuinely the U.S. Bank- specific value moment of this page is that the NACHA file content is identical across tiers — PayFile Pro doesn’t need to know which tier you’re on to generate the right file — but whether the file gets accepted depends on your service profile on the tier you’re provisioned for. A file that’s well-formed against the NACHA PPD/CCD spec and matches your tier’s service-profile entitlements goes through cleanly; a file with the wrong Service Class Code for what your tier provisioned, or uploaded to a tier where the SinglePoint Essentials ACH service isn’t activated, or with a Company Identification that doesn’t match what your service profile records, gets flagged at SinglePoint’s validation layer regardless of how well-formed the file content itself is. PayFile Pro generates the file content correctly against the network spec; the service-profile-side values (which tier, which Service Class Codes, which Company ID, which funding account) live in your U.S. Bank business banker’s setup of your SinglePoint Essentials ACH service.

SinglePoint Essentials ACH setup is the configuration layer that has to be completed before you can submit your first NACHA file to U.S. Bank through the SMB tier. Plan for a 2–4 week timeline for new originators from initial business banker conversation through live file submission, though existing U.S. Bank business banking customers who already have SinglePoint Essentials active and just need the SinglePoint Essentials ACH service entitlement added typically complete the process faster.

The setup involves several distinct steps your U.S. Bank business banker walks you through:

• U.S. Bank business checking account — a dedicated U.S. Bank business checking account is required to activate SinglePoint Essentials. If you don’t already have one open, your business banker handles the account opening as part of the SinglePoint Essentials onboarding.
• SinglePoint Essentials activation — the base SinglePoint Essentials service ($17.95/month) is activated on the account, providing online access to checking, balance reporting, fund transfers, Positive Pay, wire initiation, and the multi-user controls that the ACH service builds on top of.
• SinglePoint Essentials ACH service entitlement — separately requested and underwritten. Your business banker submits the service entitlement request, U.S. Bank’s ACH-origination underwriting team reviews your business profile (typically including business type, expected origination volume, business history, and basic risk factors), and ACH credit origination is approved (or, in some cases, both credit and debit origination, depending on what you requested). Credit-only is the typical SMB starting point.
• Company Identification value assignment — U.S. Bank provides the 10-digit Company Identification value your business will use in the Batch Header of every file. Typically your federal Tax ID prefixed with 1, sometimes a U.S. Bank-assigned alternative; your business banker confirms the exact value during service activation.
• Funding account entitlement — the specific U.S. Bank business checking account that will be debited when each batch settles is entitled for ACH origination on your service profile. Multiple accounts can be entitled if you originate from more than one funding account.
• Service Class Code configuration — your profile is configured for SCC 220 (credits-only), SCC 200 (mixed credit + debit, if your business is approved for both), or SCC 225 (debits-only, in the unusual case you’re set up for debit origination without credit).
• Dual control configuration (optional) — if your account configuration requires dual-control approval for ACH origination above a certain dollar threshold (typical for businesses originating larger batches), the approval workflow and authorized-user list is set up alongside the ACH service entitlement.
• First-file submission — once setup is complete, your business banker confirms the upload path, you submit a small test batch through SinglePoint Essentials ACH, and (assuming validation passes) the file moves into U.S. Bank’s processing queue for release on the Effective Entry Date.

Once setup is complete, the profile values rarely change. Subsequent file submissions just need to match the service profile that’s already in place — SinglePoint validates the file’s salient characteristics on every upload, accepts the file into the queue, and releases it to the ACH operator on the Effective Entry Date in the Batch Header. The 2–4 week timeline reflects the underwriting and entitlement-provisioning steps; if you’re already deeply established as a U.S. Bank business banking customer with a long origination history, your business banker may complete the SinglePoint Essentials ACH service entitlement in a few business days. New U.S. Bank business banking customers should plan for the longer end of the range. The setup timeline is notably faster than Wells Fargo’s 6–8 week Payment Manager implementation window — partly because U.S. Bank’s SinglePoint Essentials ACH service is tiered for SMBs by design (Wells’s CEO Payment Manager is the commercial-banking platform, sized for mid-market and larger commercial customers regardless of whether the originator is small or large), and partly because SinglePoint Essentials’ service-entitlement model is simpler than Wells’s Payment Manager Set-Up-Forms / processing-profile model.

Not currently. PayFile Pro generates credit files — vendor payments, payroll, supplier disbursements (Service Class Code 220). Debit files for customer collections, pre- authorized debits, or bill pay aren’t supported. ACH credit and ACH debit origination are underwritten and enabled separately on a U.S. Bank SinglePoint Essentials ACH service profile — your business may be enabled for one, both, or only credit (which is the typical SMB starting point). If debit file generation is something you need, email us — it’s on the roadmap and customer demand is what moves it up. Note that originating ACH debits requires separate underwriting and approval from U.S. Bank: your SinglePoint Essentials ACH service profile has to be enabled for ACH debit origination specifically, distinct from credit origination, with the profile configured for either SCC 225 (debits-only) or SCC 200 (mixed credit + debit) batches. U.S. Bank’s risk review for debit origination is more rigorous than for credit-only since you’re pulling funds from third parties rather than pushing your own funds out — the underwriting timeline can be longer than the credit-origination underwriting that’s part of standard SinglePoint Essentials ACH service activation.

Yes. PayFile Pro generates the NACHA file; SinglePoint Essentials ACH is what you use to submit it. They’re complementary tools — no integration or API connection required. From SinglePoint Essentials: SinglePoint Essentials Sign In → Payables → ACH → File Upload → Browse → select the file PayFile Pro generated → review the file summary → submit. SinglePoint validates the file against the NACHA PPD/CCD spec and against your SinglePoint Essentials ACH service profile (Service Class Codes, Company Identification, funding-account eligibility); if both pass, the file moves into U.S. Bank’s processing queue for release on the Effective Entry Date in the Batch Header. If your account has dual approval enabled for ACH (often optional below a monthly threshold, often required above one), a second authorized user reviews and approves the batch before it’s released to the ACH operator. The SinglePoint Essentials ACH web upload path works for SMB customers using the SinglePoint Essentials portal; higher-volume U.S. Bank customers using full SinglePoint (the corporate-and- commercial-banking tier) submit the same NACHA file through their SinglePoint upload path, and SFTP-transmitting customers (typically running ERP-integrated origination at higher volumes) submit through SFTP using the bank-issued transmission profile assigned by U.S. Bank Treasury Management at SFTP setup — same NACHA file format, different delivery channel. PayFile Pro doesn’t generate any SinglePoint- specific wrapper around the NACHA file (e.g., PGP encryption envelopes, transmission-envelope metadata, security-record headers); SFTP customers handle those layers through their existing managed-file-transfer tooling, with the transmission profile U.S. Bank provided at SFTP setup. Mobile SinglePoint (the U.S. Bank mobile app for SinglePoint and SinglePoint Essentials clients) supports approval of pre-staged ACH batches and templates — useful when a dual-control approver needs to release a batch from outside the office — but doesn’t support raw NACHA file upload from mobile; the file-upload step has to happen through the SinglePoint web portal or the SFTP path. The services, accounts, and access entitlements each user has on SinglePoint or SinglePoint Essentials determine which functions are available through Mobile SinglePoint.

SinglePoint Essentials’ ACH payee setup screens save your payee list and let you key transactions directly in the platform — Add Vendor, Add Employee, create scheduled payment runs, manage recurring schedules. The data-entry flow works, especially if you’re paying the same handful of vendors the same amounts on the same schedule.

What it doesn’t have is a per-payee template layer that lives outside SinglePoint. Every run, you’re either keying transactions in or releasing pre-saved templated batches that you have to maintain inside the portal — and the SinglePoint Essentials UI for editing 30 vendors at once is slower than editing a spreadsheet. With PayFile Pro, your Excel sheet is the template. Leave an amount blank to skip a vendor — their row stays in next week’s template. Add a row to add a vendor — they’re part of your reusable template from then on. The spreadsheet is the state; each run is just what’s in the amount column.

You still upload the file through SinglePoint Essentials ACH — PayFile Pro doesn’t bypass U.S. Bank or sit in the payment flow. Bank-side controls, dual-control approval, batch release, payment activity tracking, reversals, all stay where they are. PayFile Pro replaces the variance-management step (editing 30 amounts, skipping 2 vendors, adding a new one) with editing a spreadsheet column. That’s it.

Yes. PayFile Pro generates files entirely in your browser. Routing numbers, account numbers, amounts, and payee lists never leave your machine — no upload to our servers, no storage on our disk, no transmission anywhere. The only data we store is your account info: email, company name, primary bank, credit balance.

PayFile Pro validates files against the NACHA PPD/CCD spec before generation, which catches most common rejection causes (wrong field length, missing required fields, invalid characters, malformed dates, mismatched record counts, Entry Hash that doesn’t tie to the routing-number sum, batch totals that don’t tie to entry totals, PAYROLL paired with the CCD SEC code, pre-note transaction codes 23/28/33/38, and offset records). If U.S. Bank still rejects a file after generation, the most likely causes are bank-specific and outside the file-format spec itself:

• SinglePoint Essentials ACH service not activated — the single most common U.S. Bank- specific upload rejection for first-time originators. Base SinglePoint Essentials covers checking, wires, RTP, and Positive Pay out of the box, but ACH file upload is a separately-entitled service that has to be specifically activated. If you’re seeing a “service not available” or “ACH origination not enabled” error rather than a file-format error, that’s the issue. Your U.S. Bank business banker activates the SinglePoint Essentials ACH service entitlement; the published business banker line is 855-625-7354 (see the SinglePoint tier-routing FAQ for more on the tier-routing question).
• Service Class Code not matching profile entitlement — your profile is provisioned for SCC 220 credits-only but you’re transmitting SCC 200 mixed, or vice versa. U.S. Bank underwrites credit and debit origination separately on each SinglePoint Essentials ACH service profile; your business banker can confirm which Service Class Codes your profile is enabled for.
• Company Identification mismatch — the 10-digit value in the Batch Header doesn’t match the value U.S. Bank has on file in your SinglePoint Essentials ACH service profile. Usually your Tax ID prefixed with 1; confirm with your U.S. Bank business banker.
• Ineligible U.S. Bank funding account — the account you’re trying to fund the batch from isn’t entitled for ACH origination on your SinglePoint Essentials ACH service profile. Your business banker can confirm which accounts in your profile are entitled and add additional accounts if needed.
• Routing number doesn’t match account home state — using the Minnesota 091000022 when the account was originally opened at a former Union Bank California branch with the 121122676 routing, for example. U.S. Bank’s state-based ACH routing numbers are tied to where the account was opened (often inherited from one of the legacy acquisitions — Firstar, Mercantile, Star Banc, or Union Bank), not where the business operates today. Unlike Wells Fargo’s wire-vs-ACH-routing split, U.S. Bank typically uses the same routing for both ACH and wires, so the routing- number rejection is almost always a state-mismatch rather than a wire-routing-in-an-ACH-file mistake.
• PAYROLL used for retirement-benefit payments (or vice versa) — U.S. Bank’s published 2026 Operating Rule guidance PDF distinguishes PAYROLL (PPD credits for wages, salaries, and similar compensation) from PENSION (PPD credits for retirement benefit payments). If you’re originating a retirement-benefit-payments batch under the PAYROLL Company Entry Description (or originating a wage-and-salary batch under PENSION), the file may flag at U.S. Bank’s validation layer for an entry- description-mismatch error. PayFile Pro defaults to PAYROLL for PPD payroll batches; override to PENSION for retirement-benefit batches in the Company Entry Description column of your XLSX template (see the Company Entry Description FAQ above).
• Full SinglePoint required for the volume / SEC-code mix — for businesses originating at higher volumes, originating international ACH (IAT), or using SEC codes outside PPD and CCD (CTX for EDI 820, WEB for consumer- authorized internet debits, etc.), full SinglePoint may be the right tier rather than SinglePoint Essentials. If your business is hitting SinglePoint Essentials’ SCC or volume boundaries, your U.S. Bank business banker can route you to U.S. Bank Treasury Management Sales to evaluate the full SinglePoint upgrade path.

Email hello@payfilepro.com with the rejection message and we’ll help you debug — if the rejection is U.S. Bank-specific and frequent enough, it gets documented here so the next person hits a known-resolved issue.

PayFile Pro uses prepaid credits. One credit per generated file. Credits never expire. Packs start at $10 USD for 5 credits ($2.00 per file) and scale to $1.50 per file at 50 credits. No subscription, no monthly minimum, no auto-renewal. Buy credits when you need them.