Generate PNC payment files without an ERP

Yes — and this is one of the things PNC’s ACH origination service handles cleanly. PNC’s published ACH origination guidance is explicit that a single ACH file can contain multiple batches with different Standard Entry Class codes, and gives the example directly: a batch of PPD entries and a batch of CCD entries within one file. PPD is the SEC code for payments to individuals (employees on payroll, contractors, individual vendors); CCD is the SEC code for payments to businesses (corporate vendors, suppliers). A finance team that runs both payroll and vendor payments through PNC doesn’t need to produce, upload, and track two separate files — the two batches travel together.

That’s exactly what PayFile Pro’s /ach generator produces. You maintain one payee list in your XLSX template. When you generate, PayFile Pro sorts each payee into the right batch — individuals into a PPD batch, businesses into a CCD batch — and emits both as batches inside a single NACHA file (PPD as Batch 1, CCD as Batch 2). One file, one upload through PINACLE’s ACH module, one settlement debit per batch against your PNC funding account. If a given run only has individual payees, you get a PPD-only file; only business payees, a CCD-only file; both, the two-batch file. You don’t decide the batch structure — the payee type does, and PayFile Pro handles the sorting.

Two practical notes. First, PNC matches the Batch Header of each batch — the Company Name and Company Identification combination — against the batch header it has registered for your business, so both batches in a multi-batch file need to carry the originator details PNC registered (see the batch-header registration FAQ below). Second, the Company Entry Description differs by batch: a PPD payroll batch should carry PAYROLL; a CCD vendor batch carries ACH PMT, VENDOR PAY, or a similar short value. PayFile Pro reads the Company Entry Description from your template per batch, so a single file can correctly carry PAYROLL on the PPD batch and VENDOR PAY on the CCD batch at the same time.

To submit a generated file, yes — your business needs to be set up with PNC for ACH origination through PINACLE, with a Company Identification value assigned, a registered ACH batch header (Company Name + Company Identification), your funding account entitled for ACH origination, and the PINACLE ACH module enabled on your operators’ entitlements. PayFile Pro generates the file; your PNC enrollment as an ACH Originator is what authorizes you to upload it. PNC enrolls business customers in ACH origination through PNC Treasury Management. The right channel is your PNC Treasury Management Officer (or your PNC business banking relationship manager, who can route you to Treasury Management). They set up the ACH origination service on your PINACLE profile, register your ACH batch header, entitle your funding account, and configure your operators’ ACH privileges. If your business was previously a BBVA USA customer that migrated to PNC, your ACH origination service, settlement account instructions, and routing numbers were updated as part of that conversion — confirm with your Treasury Management Officer that your current PNC Company Identification and registered batch header are the ones you should be using, since legacy BBVA values are no longer active. PINACLE itself requires a security token at sign-in, and ACH batch approval is gated by operator entitlements, so a business typically has at least one operator who can create or import batches and at least one who can approve them. None of the PNC-side setup is something PayFile Pro does or needs visibility into — PayFile Pro generates a correctly formatted NACHA file; PNC’s enrollment is what makes it submittable.

Four values in the File Header and Batch Header of every PNC NACHA file need bank-specific attention, plus one registration check — the ACH batch header PNC has on file for your business — where PNC’s most common source of upload rejections lives.

• Immediate Destination — a 9-digit PNC ACH routing number placed in a 10-character field with a leading blank space. PNC uses state- and region-based routing numbers, broadened substantially through the National City Corporation acquisition (2008) and the BBVA USA acquisition (2021); the routing number for your account is the one for the state or region where the account was originally opened, regardless of where the business operates today. PNC’s most widely used ACH routing number is 043000096, which covers the Pittsburgh area of Pennsylvania (PNC’s headquarters region) and much of PNC’s Southeast and Mid-Atlantic footprint — including Alabama, Florida, Georgia, Indiana, and North Carolina. Other common state and region values include 031100089 (Philadelphia region of Pennsylvania, and Delaware), 042000398 (Ohio), 041000124 (Michigan), 071921891 (Illinois, and Missouri), 031207607 (New Jersey), 021272655 (New York), 054000030 (Maryland, Washington D.C., and Virginia), and 083000108 (Kentucky). PNC operates in roughly 28 states post-BBVA, and a number of states share 043000096, so the practical point is the same as on any large multi-acquisition bank: the routing number tied to your account is determined by where the account was opened, not selected from a menu. You can confirm the routing number for your specific account by signing in to PNC online banking or the PNC mobile app under your account details, at the bottom of any PNC business check, inside PINACLE under information reporting, by using the routing-number lookup on pnc.com, or by contacting your PNC Treasury Management Officer. PayFile Pro reads the PNC routing number you enter in the originator-details section of your XLSX template and inserts it into the File Header automatically.
• Immediate Destination Name — PNC BANK (uppercase, left-justified, blank-padded to 23 characters). The network-standard convention is uppercase without punctuation, and PayFile Pro defaults to PNC BANK.
• Company Identification — a 10-digit numeric value PNC assigns and registers when they enroll your business for ACH origination. 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 PNC provides. It goes in the Batch Header Record (positions 41–50) and the Batch Control Record (positions 45–54). PNC uses this value — in combination with your Company Name — to match every batch you submit against the ACH batch header it has registered for your business, so the Company Identification in your file has to be exactly the value PNC registered.
• Company Name — what appears on your payee’s bank statement, and the second half of the pair PNC matches against your registered batch header. NACHA rules require this 16-character field to clearly identify the entity originating the entries; it should not contain a phone number or a name your payee won’t recognize. Because PNC matches the Company Name + Company Identification combination, the Company Name in your file has to match the registered batch header just as exactly as the Company Identification does.
• File ID Modifier — a single character A–Z or 0–9 that lets you distinguish multiple files originated on the same day. PNC accepts the network-standard single-character alphanumeric convention without customer-side configuration (unlike Wells Fargo, which locks the File ID Modifier format to digits-only, letters-only, or alphanumeric through its Set-Up Forms). PayFile Pro defaults to alphanumeric and increments the modifier on subsequent files originated the same day.

The registration check, rather than a file-content field, is the ACH batch header PNC has on file for your business — the Company Name + Company Identification combination, registered with PNC through its ACH Origination New Batch Header Request Form. On every upload, PINACLE matches your batch’s header against that registered value. A file that’s well-formed against the NACHA spec but carries a Company Name or Company Identification that doesn’t match the registered batch header gets flagged before it reaches the ACH operator. New or revised batch headers must be communicated to PNC at least two weeks before first use — so if your business name changes, or you’re setting up a new originating entity, the new batch header has to be registered and the notification window cleared before a file using it will process. (See the batch-header registration FAQ below.)

(Different US banks use different conventions for these fields, and PayFile Pro now has a dedicated page for each of the five largest. 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, 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) or full SinglePoint (the corporate tier), distinguishes PAYROLL from PENSION at the Company Entry Description level per its published 2026 Operating Rule guidance, validates each upload against your SinglePoint Essentials ACH service-profile entitlements, and uses state-based routing numbers inherited from legacy Firstar / Mercantile / Star Banc / Union Bank acquisitions. PNC uploads through the PINACLE ACH module, matches the Company Name + Company Identification combination in each Batch Header against an ACH batch header registered with PNC ahead of time — new batch headers requiring roughly two weeks’ advance notice through PNC’s New Batch Header Request Form — explicitly supports a single ACH file carrying multiple batches with different SEC codes (a PPD batch and a CCD batch together), requires advance notification to Treasury Management for WEB / TEL / IAT origination, and uses state- and region-based routing numbers broadened through the National City and BBVA USA acquisitions.)

PNC follows the NACHA network-level Company Entry Description conventions. The Company Entry Description goes in Batch Header positions 54–63 and describes the purpose of the batch in a short customer-entered value: PAYROLL, ACH PMT, VENDOR PAY, BONUS, EXPENSE, REVERSAL, 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. This is a network-level rule — it applies on PNC the same as everywhere else. PayFile Pro defaults PPD payroll batches to PAYROLL in the Company Entry Description to satisfy it. For CCD vendor batches, the Company Entry Description is a short value you choose — ACH PMT and VENDOR PAY are both common — entered in the Company Entry Description column of your XLSX template per batch.

PNC’s posture on the 2026 rule changes is an active, educational one. PNC co-presented a January 2026 webinar on the 2026 Nacha rule changes alongside Nacha and PaymentWorks, and PNC payments leadership has spoken publicly on the fraud-monitoring shift at Nacha’s Smarter Faster Payments conference — framing the change as moving ACH risk management from origination-only screening to end-to-end oversight. If you’re running ACH credits through PNC, your PNC Treasury Management Officer is the right channel for how the 2026 rules apply to your specific origination profile. The PAYROLL Company Entry Description requirement is the one 2026 change that touches what’s actually in the file PayFile Pro generates; the other 2026 changes (the Phase 2 fraud-monitoring obligation effective June 2026, funds-availability timing, and the IAT definition update) are procedural or out of PayFile Pro’s PPD/CCD scope. 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.

This is the PNC-specific detail most likely to flag a first-time originator’s file, so it’s worth getting right before your first upload.

Every ACH batch carries a Batch Header Record, and two fields in it identify your business: the Company Name and the Company Identification. PNC doesn’t just read those fields — it matches them, as a combination, against an ACH batch header it has registered for your business. PNC’s ACH origination setup includes registering your batch header with the bank, and PNC uses both the Company Name and the Company ID to match your submitted batches against that registered header. A batch whose Company Name or Company Identification doesn’t match what PNC registered won’t process.

That has two practical consequences:

• Your file has to carry the exact registered values. Not a close variant of your company name, not an old Company ID, not a Tax-ID-derived value you assumed PNC would use — the specific Company Name and Company Identification PNC registered. With PayFile Pro, those live in the originator-details section of your XLSX template, so you set them once to match what PNC registered and every file you generate carries them. If you’re unsure what PNC has on file, your Treasury Management Officer can confirm both values.
• A new or changed batch header needs advance notice. New or revised ACH batch header information must be communicated to PNC at least two weeks before you first use it, through PNC’s ACH Origination New Batch Header Request Form. So if your business changes its legal name, sets up a new originating entity, or otherwise needs a new batch header, the new header has to be registered and the two-week notification window has to clear before a file using it will process. This isn’t a PayFile Pro limitation — PayFile Pro will happily generate a file with any Company Name and Company ID you put in the template — it’s a PNC registration requirement, and submitting a file with an unregistered batch header is a rejection waiting to happen.

This is PNC’s analog to the originator-identity matching other large banks do — Wells Fargo’s Customer Application ID matched against a processing profile, U.S. Bank’s SinglePoint Essentials ACH service-profile validation. The mechanism differs bank to bank, but the underlying point is the same: the bank validates who is originating the batch against what it has on file, and a mismatch stops the file regardless of how well-formed the file content itself is. PayFile Pro generates the file content correctly against the NACHA spec; making sure the Company Name and Company Identification in your template match PNC’s registered batch header is the one originator-side step that’s on you.

PINACLE ACH origination setup is the configuration that has to be completed before you can submit your first NACHA file to PNC. It runs through your PNC Treasury Management Officer and generally involves several distinct steps:

• PINACLE access — if your business doesn’t already use PINACLE, PNC sets up the platform, your operators, and their entitlements. PINACLE uses a security token at sign-in.
• ACH origination service — the ACH module is enabled on your PINACLE profile, and PNC’s underwriting reviews your business for ACH credit origination (business type, expected origination volume, business history, basic risk factors). Credit origination is the typical SMB starting point; ACH debit origination, if you need it, is underwritten separately.
• Company Identification assignment — PNC provides the 10-digit Company Identification value your business will use in the Batch Header of every file.
• ACH batch header registration — your Company Name + Company Identification batch header is registered with PNC through the ACH Origination New Batch Header Request Form. New batch headers require roughly two weeks’ lead time before first use, so this step is worth starting early.
• Funding account entitlement — the specific PNC business account that will be debited when each batch settles is entitled for ACH origination. More than one account can be entitled if you originate from multiple funding accounts.
• Operator entitlements — your PINACLE operators are given the ACH privileges they need. Creating or importing a batch and approving a batch are separate entitlements, so a business using dual control typically has at least one operator who can build or import files and at least one separate operator who can approve them.
• WEB / TEL / IAT notification (only if applicable) — if your business originates WEB, TEL, or IAT entries, you have to notify PNC Treasury Management in advance so PNC can collect the additional information those SEC codes require. This step doesn’t apply to PayFile Pro users, since PayFile Pro generates only PPD and CCD.
• First-file submission — once setup is complete, your Treasury Management Officer confirms the upload path inside PINACLE, you submit your first batch, and (assuming validation passes and any dual-control approval is given) the file moves into PNC’s processing queue for release on the Effective Entry Date.

The timeline depends on your situation. An existing PNC business banking customer who already uses PINACLE and just needs the ACH module enabled and a batch header registered may be ready in a couple of weeks — gated mostly by the two-week batch-header registration window. A business new to PNC, or one that needs underwriting for a higher origination volume, should plan for a longer onboarding. Once setup is complete, the configuration rarely changes; each subsequent file just needs to match the registered batch header and the network spec, both of which PayFile Pro handles on the file-content side.

PNC publishes input deadlines by transmission method. For traditional ACH — processing that can result in settlement and receipt as early as the next business day — PNC’s published deadlines are 10:00 p.m. ET for direct file transmission (and SWIFT FileACT), 8:00 p.m. ET for the PINACLE ACH module, 8:45 p.m. ET for the EDI platform, and 9:00 p.m. ET for Integrated Payables. For most PayFile Pro users, the relevant deadline is the PINACLE ACH module’s 8:00 p.m. ET cutoff, since that’s the channel a file you generate is uploaded through; businesses on PNC’s direct file transmission (Secure FTP) path have the later 10:00 p.m. ET window. You can also future-date, or “warehouse,” ACH entries up to 45 days ahead — PNC releases them automatically on the Effective Entry Date you set — so cutting it close to a cutoff is avoidable for any payment you can stage in advance.

For Same Day ACH, PNC requires you to enroll for the service ahead of time. PNC publishes a same-day input deadline of 3:45 p.m. ET for direct file transmission. Same Day ACH submitted through PINACLE has an earlier same-day input deadline than the direct path; PNC’s same-day windows are tighter than the traditional next-day windows across the board. Because Same Day ACH cutoffs are the kind of operational detail that changes, and PayFile Pro doesn’t sit in the submission path, confirm the exact current Same Day ACH cutoff for your transmission channel with your PNC Treasury Management Officer before relying on it for a time-sensitive payroll or payment run. The file PayFile Pro generates is the same NACHA file whether it settles same-day or next-day — Same Day ACH is a processing election you make on the PNC side, not a different file format — so nothing in the file changes based on which window you’re targeting.

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 separately by PNC — your business may be enabled for credit origination, debit origination, or both, and credit-only is the typical SMB starting point. Originating ACH debits requires PNC’s separate underwriting and approval, since you’re pulling funds from third parties rather than pushing your own funds out, and PNC’s review for debit origination is more rigorous than for credit-only. If debit file generation is something you need, email us — it’s on the roadmap, and customer demand is what moves it up.

Yes. PayFile Pro generates the NACHA file; PINACLE is what you use to submit it. They’re complementary tools — no integration or API connection required. From PINACLE: sign in (PINACLE requires your security token), go to the ACH module under Payments & Transfers, use the module’s file-import function to attach the NACHA file PayFile Pro generated, select the PNC funding account that will be debited at settlement, review the batch summary PINACLE displays, and submit. PINACLE validates the file against the NACHA format and against the ACH batch header PNC has registered for your business; if it passes, the file moves into PNC’s processing queue for release on the Effective Entry Date in each Batch Header. If your account uses dual control for ACH, a second authorized PINACLE operator with approval entitlements reviews and releases the batch before it goes to the ACH operator. Higher-volume PNC customers using direct file transmission (Secure FTP) submit the same NACHA file through their managed-file-transfer tooling with the transmission profile PNC assigned at setup — same NACHA file, different delivery channel. PayFile Pro doesn’t generate any PINACLE-specific or transmission-specific wrapper around the NACHA file (no PGP encryption envelope, no transmission metadata); businesses on the Secure FTP path handle those layers through their own tooling. Exact screen labels inside PINACLE’s ACH module depend on how your operators’ entitlements and file-import profiles were configured during your PNC Treasury Management onboarding — your Treasury Management Officer confirms the precise path for your profile.

PINACLE’s ACH module saves payees and batch templates, and lets you build a batch from scratch or from a saved template directly inside the platform. The templated-batch 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 PINACLE. Every run, you’re either keying transactions in or maintaining pre-saved templated batches inside the portal — and editing 30 vendors at once inside PINACLE 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 PINACLE — PayFile Pro doesn’t bypass PNC or sit in the payment flow. Bank-side controls, dual-control approval, batch release, payment 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, an 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 PNC still rejects a file after generation, the most likely causes are bank-specific and outside the file-format spec itself:

• Company Name or Company Identification doesn’t match the registered batch header — the single most common PNC-specific upload rejection. PNC matches the Company Name + Company Identification combination in each Batch Header against the ACH batch header it has registered for your business. If either value is off — an old Company ID, a company-name variant, a Tax-ID-derived value PNC didn’t actually register — the batch won’t process. Confirm both registered values with your PNC Treasury Management Officer and set them in your XLSX template once.
• Unregistered new batch header — a new or revised batch header used before its two-week notification window with PNC has cleared. New batch headers have to be registered through PNC’s ACH Origination New Batch Header Request Form ahead of first use.
• 15-character ID Number field not fully populated — PNC expects the Identification Number field in the Entry Detail Record (a 15-character field) to be fully populated, padded with leading zeros where needed rather than left partially blank. PayFile Pro pads fixed-width fields automatically, so this is mainly a hand-built-file pitfall.
• Ineligible PNC funding account — the account you’re funding the batch from isn’t entitled for ACH origination on your PINACLE profile. Your Treasury Management Officer can confirm which accounts are entitled and add others if needed.
• Same Day ACH submitted after the cutoff — a Same Day ACH batch submitted after PNC’s same-day input deadline settles the next business day instead of same-day. If timing matters, confirm the current same-day cutoff for your channel with PNC (see the submission cutoffs FAQ).
• WEB / TEL / IAT without advance notification — originating those SEC codes without notifying PNC Treasury Management in advance. This doesn’t apply to PayFile Pro users, since PayFile Pro generates only PPD and CCD — but it’s worth knowing if you also originate those codes through PINACLE directly.
• Operator entitlement or approval gap — a batch that was imported but not approved by an operator with approval entitlements, where dual control is in effect. This is a PINACLE workflow step, not a file-format problem.

Email hello@payfilepro.com with the rejection message and we’ll help you debug — if the rejection is PNC-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.