Building a PNC positive pay file for PINACLE

If PNC has enrolled you in Check Positive Pay, you owe the bank a file every time you cut checks. That file lists each check you issued so PNC can match it against checks that come in for payment. Anything that does not match becomes an exception you review and decide to pay or return. The work that trips most people up is producing the file itself in the layout PNC expects, on the schedule PNC expects.

This page explains how PNC handles positive pay through its PINACLE platform, where to find your exact file specification, and how to turn a check register into a matching file without buying desktop software.

How positive pay works at PNC

PNC runs its commercial and treasury services through PINACLE, the bank's online banking platform for business and corporate clients. Positive pay is one of the fraud-prevention modules inside it. PNC offers a few variations:

The core loop is the same regardless of variant. You issue checks, you upload an issue file (sometimes called a check issuance or issued check file), PNC matches incoming checks against it, and you clear exceptions before a daily cutoff. Miss the file or miss the cutoff and legitimate checks can be returned, which annoys your vendors.

Getting your file into PNC

PNC supports more than one delivery channel for the issue file. Two common ones are direct transmission (an automated feed, typically for higher-volume clients) and PINACLE File Import, where you upload the file through the online banking portal. For most small and mid-size businesses, file import through PINACLE is the path you will use.

You will find positive pay inside PINACLE under the treasury or fraud-prevention area. If you cannot locate it, your account may not be enrolled yet, or your user profile may not have the entitlement. Both of those are fixed by your PNC Treasury Management Officer (TMO), not by something you can toggle yourself.

Where to get the exact PNC file spec

This is the part we will not guess at. PNC provides the precise file specification for your account, and the layout that applies to you depends on how your service is configured, whether you are sending payee data, and which channel you use. We have seen PNC accept fixed-width text layouts as well as comma-delimited (CSV) layouts, and PNC also supports structured XML (ISO 20022) for certain ERP-integrated setups. Because the details differ by account, the field order, padding rules, and date format that work for one PNC customer may not match yours.

So the reliable move is to ask. Request the current check issue file specification from your PNC Treasury Management Officer or through PINACLE support. The spec sheet tells you exactly which fields to include, in what order, how to format the date, how to mark a void versus an issue, and whether the file needs header and trailer records. Build to that document, not to a layout you found on a forum, and not to one this page invented.

If you have an old working file from a prior period, keep it. A known-good sample is the fastest way to see the real field order and spacing PNC is accepting on your account.

Build the file from your check register

Whatever tool you use to write checks, the source data is the same handful of fields: account number, check number, amount, issue date, and usually payee name. The hard part is reshaping that data into PNC's exact layout. QuickBooks, for example, will not export a positive pay file on its own. You get a check register or a report, and you have to convert it.

PositivePayMaker does that conversion in your browser. You export your check register to CSV or Excel, load it, map your columns to the fields PNC wants, and download a file in the format you need. It is free, and because it runs entirely client-side, your check data never leaves your computer and is never uploaded to a server.

For PNC specifically, where the layout is account-dependent, the custom format builder is the right tool. You tell it the field order, delimiter or column widths, date format, and any header or trailer rows from your PNC spec sheet, and it produces a file that matches. If PNC gave you a simple CSV layout, a generic CSV preset will get you most of the way there. See the positive pay file format reference for an explanation of how these layouts are structured and what each field means.

Always validate the first file with PNC

Treat your first generated file as a test, not a submission you trust blindly. Generate it, open it in a plain text editor, and check it against the PNC spec line by line: are the dates in the right format, are amounts formatted the way PNC asks (decimal point or implied cents), is the account number correct and padded as required. Then run it through PNC's import and confirm the bank accepts it cleanly with no rejected records.

You can also run a copy through the built-in file validator to catch structural problems before you upload. But the validator does not know PNC's account-specific rules, so the bank's own acceptance of the file is the real test. Once one file goes through clean, save your column mapping so every future file comes out the same way.

Is a paid tool worth it for PNC?

If you cut a high volume of checks across many accounts, or you want a desktop app that lives next to QuickBooks, paid converters exist. Big Red Consulting's PositivePay File Creator runs about $119 the first year and $99/year after, is Windows-only, and the QuickBooks Online edition needs Excel installed. Treasury Software's Bank Positive Pay is an installed Windows product roughly in the $29.95 to $89.95/month range and ships with hundreds of bank layouts. Those can be a fair fit for larger or more complex shops.

For most businesses sending a PNC issue file from a check register, a free browser tool with a custom builder covers the job without a subscription or an install. If you want to see other layouts we support, browse the bank formats list.

Create your positive pay file