CSV to positive pay: map your columns, then convert

You have a check register exported to CSV. Your bank wants a positive pay file, also called a check issue file, that lists every check you wrote so the bank can flag anything that does not match. The two files describe the same checks, but they almost never share the same column order, date format, or layout. The work in between is mapping: deciding which column in your CSV becomes the check number, which becomes the amount, and so on, then writing the result in the exact shape your bank expects.

This guide walks through that mapping, the delimiter and formatting choices that trip people up, and how to produce the file without editing it by hand in a spreadsheet.

What your bank actually needs from the CSV

Almost every positive pay layout is built from the same handful of fields. The names and order change from bank to bank, but the data does not:

• Check (item) number, the number printed on the check.
• Amount, the dollar amount, almost always to two decimal places.
• Issue date, the date the check was written or printed.
• Account number, the checking account the check draws on.
• Issue/void indicator, usually a single letter, often I for issued and V for void.
• Payee name, required by some banks, optional or ignored by others.

Published bank specs show how much the order varies. Regions Bank's CSV layout puts the account number in column A, amount in B, check number in C, issue or void date in D, the I/V indicator in E, and payee in F. FC Banking's format leads with the issue date, then the check number, then the payee, then the amount. Same six pieces of data, two completely different column orders. That is why you cannot reuse one bank's template for another, and why a raw QuickBooks or accounting-software CSV rarely uploads as-is.

Step 1: Find the columns in your CSV

Open your exported register and identify which header maps to each required field. A typical accounting export might have columns like Num, Date, Name, Amount, and Account. Your job is to connect each of those to the field your bank wants:

• Num → check number
• Amount → amount
• Date → issue date
• Name → payee
• Account → account number

Two things to watch here. First, registers often mix checks with other transaction types (deposits, transfers, card charges). Positive pay should contain checks only, so you will usually filter to rows that have a check number. Second, amounts in a register can be signed or split across debit/credit columns. The positive pay amount should be a positive number, so confirm you are pulling the right column and dropping any minus sign.

Step 2: Get the delimiter right

CSV means comma-separated values, and a comma is the default delimiter. But two complications come up often. Payee names like Smith, Jones & Co. contain commas, which can shift every field to the right if the value is not quoted. And some banks specifically ask for a different separator, such as tab-delimited or pipe-delimited text, even though they call the upload a CSV.

If your data has commas inside field values, make sure those values are wrapped in quotes, or switch to a delimiter that does not appear in your data. When in doubt, check the bank's file specification for the exact delimiter it expects, and open your converted file in a plain-text view to confirm each field landed in the right place before you upload.

Step 3: Normalize dates and amounts

Most format mismatches come down to dates and money:

• Date format. Banks commonly want MM/DD/YYYY, but YYYYMMDD and MMDDYYYY show up too, especially in fixed-width layouts. A spreadsheet may also reformat dates on open, so verify the actual text in the file matches the spec.
• Decimal places. Amounts usually need exactly two decimals (1500.00, not 1500 or 1,500.00). Thousands separators almost always have to go.
• Leading zeros. Check numbers and account numbers sometimes need to keep leading zeros. Spreadsheets love to strip these by treating the field as a number, which is a frequent cause of rejected files.

Step 4: Convert the file

You can do all of this by hand in Excel: reorder columns, reformat dates, force text formatting on number fields, and save as CSV or fixed-width. It works, but it is fiddly and easy to get wrong on the leading-zero and date-format details, and you repeat it every time you cut checks.

PositivePayMaker does the mapping for you in the browser. You upload your CSV or Excel register, match your columns to the fields once, pick your bank's layout, and download the file. It is free, and because it runs entirely in your browser, your check data never gets uploaded to a server. The tool ships with 11 bank layouts, six built from published specifications including Chase and Huntington, plus a custom format builder for any layout not on the list and a validator to check a file's structure before you send it.

This matters especially for QuickBooks users, because QuickBooks Online cannot export a positive pay file natively. Intuit's own community guidance points people to third-party tools for exactly this reason. You export your register from QuickBooks as a CSV or Excel file, then convert it.

If your bank's layout is not built in

No converter ships with every bank's exact spec, and inventing field positions is how files get rejected. The reliable source is always the bank itself. Your bank publishes its positive pay file specification through its treasury management or business banking portal, and your treasury or cash management contact can send it to you. Many banks run positive pay on a third-party treasury platform such as Centrix, Q2, Fiserv, or FIS, and the upload screen usually lives under cash management or fraud control inside online banking.

Once you have the spec, the custom format builder lets you reproduce it: set the delimiter or fixed-width column positions, the date format, the field order, and any header or trailer row the bank requires. Match the layout to the document, then convert.

When a paid tool makes more sense

For low to moderate check volume, a free browser converter covers the job. Higher-volume shops or accountants handling many clients sometimes prefer a paid desktop product with a large prebuilt format library. Big Red Consulting's PositivePay File Creator runs about $119 the first year and $99 a year after, is Windows-only, and the QuickBooks Online edition needs Excel installed to process exports. Treasury Software's Bank Positive Pay is installed Windows software with 350-plus verified layouts, sold as a month-to-month subscription. Both are reasonable if a wide format library or QuickBooks integration is worth the cost to you.

Always verify the first file

Whichever route you take, treat your first generated file as a draft. Upload it to your bank's positive pay portal, or send it to your treasury contact, and confirm it imports cleanly before you rely on it for a real check run. A single wrong date format or a stripped leading zero can cause a whole file to bounce, and it is far easier to catch that on the first try than after checks have cleared.

Create your positive pay file