Quicken positive pay: export the register, map the columns, convert
Quicken keeps an accurate record of every check you write, but it will not hand your bank a positive pay file. There is no "positive pay" command in the menus and no built-in bank layout. What Quicken does give you is a clean export of the check register, and that export is most of the work. Once the data is in a spreadsheet, turning it into your bank's check issue file is a mechanical step: line up your columns with the fields the bank expects, then save in the format the bank accepts.
This guide covers the export path for both Quicken for Windows and Quicken for Mac, which columns matter, and how to convert the result without buying installed software you may not need.
What positive pay actually needs
Positive pay (sometimes called a "check issue" or "issued checks" file) is a daily list you send the bank of the checks you wrote. The bank matches incoming checks against that list and flags anything that does not match: wrong amount, unknown check number, a check you never issued. Almost every bank's file boils down to four or five fields:
- Account number the checks are drawn on
- Check number
- Amount
- Issue date
- Payee name (some banks require it, some treat it as optional)
- Sometimes a void indicator for canceled checks
Your Quicken register already holds every one of those values. The job is formatting, not data entry.
Export the check register from Quicken
In Quicken for Windows and Quicken for Mac, open the account register you write checks from, then choose File > Export > Register Transactions to CSV File. You can choose all visible transactions or only the ones you select, so you can filter the register to a single date range or to checks only before exporting.
If that menu item is missing in your version of Quicken for Windows, use the alternative: click the gear icon in the upper right of the register and choose Export to Excel Workbook. Either path gives you a spreadsheet you can open in Excel, Numbers, or Google Sheets.
Before you export, make sure the columns you need are visible in the register. Use the register's column settings to show Check #, Date, Payee, and Amount. If a column is hidden, it may not come through in the export. Filtering the register to show only the checks you issued today (not deposits, transfers, or scheduled reminders) keeps the file clean and saves you from deleting rows later.
Clean the export before you convert
A raw Quicken export usually needs a few small fixes so the bank will accept it:
- Keep checks only. Remove deposits, transfers, and any non-check rows. Positive pay files describe issued checks, nothing else.
- Make amounts positive. Quicken stores payments as negative numbers. Most bank formats want the check amount as a positive value. Strip the minus sign, and remove any currency symbols or thousands separators if your bank wants a plain number.
- Match the date format. Banks are picky here. Some want MM/DD/YYYY, others want YYYYMMDD with no slashes. Use the format in your bank's spec, not whatever Quicken exported.
- Confirm check numbers are present. Blank check numbers will fail validation. If a row has no check number, it does not belong in the file.
- Decide on payee. If your bank uses "payee positive pay," the name has to be there and spelled the way it prints on the check.
Get the exact layout from your bank, not from a guess
The single most important point: the precise field order, column headers, and file type come from your bank, not from a generic template. A regional bank's CSV might be Account, Check Number, Amount, Date, while another wants a fixed-width text file with the amount right-justified and padded with zeros. Getting one field position wrong means the upload rejects.
Your bank publishes its own positive pay specification through its treasury or business-banking portal. If you cannot find it, your treasury management contact or business banker can send the exact file format, including whether it expects a header row, the date format, and how to mark voids. Many banks run their positive pay on third-party treasury platforms (Centrix, Q2, Fiserv, or FIS are common), so the upload screen and file rules are set by that platform rather than by Quicken. Ask for the spec sheet and a sample file before you build anything.
Convert the spreadsheet into the bank's file for free
Once you have your cleaned Quicken export and your bank's field requirements, you need to reshape the columns into the bank's order and save in the right format. PositivePayMaker does exactly this step in your browser. It is free and runs entirely client-side, so your check data never leaves your computer and nothing is uploaded to a server. You load the CSV or Excel file you exported from Quicken, map each column to the bank field it represents, and download a file ready to send.
It ships with 11 bank layouts, including formats built from published specifications such as Chase and Huntington. If your bank is not in the list, the custom format builder lets you recreate any CSV or fixed-width layout from the spec your bank gave you: set the field order, delimiters, date format, and padding to match. There is also a file format reference if you want to understand what each field does before you map it, plus a built-in validator to sanity-check the output.
When a paid desktop tool makes sense
If you generate large batches every day, or you want a tool that reads directly from QuickBooks or a fixed bank list without manual mapping, an installed product may be worth the cost. Big Red Consulting's PositivePay File Creator runs about $119 the first year and $99 a year after that; it is Windows-only and supports a large predefined bank list (the QuickBooks Online edition needs Excel installed). Treasury Software's Bank Positive Pay is installed Windows software, roughly $29.95 to $89.95 per month depending on tier, with a library of around 350 verified bank formats. MoneyThumb and ProperSoft also sell paid desktop converters. These suit higher-volume or heavily automated shops. For occasional check runs out of Quicken, the free browser converter usually covers it.
Always verify the first file with your bank
No matter how you build it, treat the first file as a test. Send it through your bank's positive pay upload and confirm it is accepted and that the check numbers, amounts, and dates match what you issued. A single wrong date format or a stray header row is the usual reason a first upload fails, and it is far better to catch that on a test run than on a day when real checks are clearing. Once one file goes through clean, the same export-and-convert routine will work every time.
For the bigger picture on how this fits a QuickBooks-plus-Quicken workflow, see the QuickBooks positive pay guide.