How to Create a Positive Pay File From FreshBooks
FreshBooks does not produce a positive pay file, and it does not keep a check register the way a desktop accounting package does. There is no "check issue file" export anywhere in the product. So when your bank asks for positive pay, the job has two parts: pull the right export out of FreshBooks, supply the check numbers it does not track for you, then convert that data into the exact layout your bank expects.
This guide covers where FreshBooks holds your check payments, why the check number is the field most likely to be missing, and how to turn a clean export into a bank-ready file. If positive pay itself is new, start with what is positive pay. In one line: the bank matches every check that clears against a list you send (check number, amount, and often the payee), and flags anything that does not match before it pays.
Why FreshBooks is a special case
FreshBooks was built around invoicing and getting paid, not around writing checks. It has no bank-account check register, no "print check" workflow with a running check sequence, and no field formally labeled "Check Number" in most places you record money going out. That is fine for how most FreshBooks users work, but it means the check number, the single most important field in a positive pay file, is something you have to be deliberate about capturing.
You will pull your outgoing payments from one of two places depending on how you record them: Expenses, or Bills and their bill payments (the vendor-bill workflow). Both can be exported to CSV. Neither was designed to carry a check number unless you put one there.
Step 1: Decide which export holds your checks
Look at how your check payments are recorded in FreshBooks:
- If you log them as Expenses, go to the Expenses area and use Export Expenses, or run the Expense Report and export it to CSV. You can scope it by date (This Month, This Quarter, This Year, or a custom range) so you only pull the checks you need to report.
- If you use Bills and pay them from the Bills page, that is the vendor-bill flow. Pull the export that lists those bill payments for the period. Vendors themselves also export to CSV with their address details, which is handy if your bank's layout matches on payee and you need clean vendor names.
Whichever you use, the goal of this step is one spreadsheet with a row per check and, at minimum, a date, an amount, and an identifier you can turn into a check number.
Step 2: Supply the check number FreshBooks did not
This is the step that decides whether the whole file works. A positive pay file with blank or wrong check numbers is useless to the bank, because the check number is the primary thing it matches on.
FreshBooks does not auto-assign physical check numbers. So in your export, look for where the number actually lives:
- A notes, reference, or memo column. If your team typed the check number into a notes or reference field when recording the payment, that is your check number column. Confirm it is populated for every row.
- Nothing usable. If no one captured the check number at entry time, the export will not have it, and there is no way for the tool to invent it. You will need to add a Check Number column to the spreadsheet and fill it from your physical checkbook or check stock. Going forward, record the check number in a consistent field in FreshBooks so future exports carry it.
One more cleanup: the bank wants the bare number. If a cell reads "Check 1042" or "1042 rent," edit it down to 1042. Mixed-in text will either reject the row or push the wrong value into the check-number field.
Step 3: Confirm the amount and date columns
The amount is usually the cleanest field in a FreshBooks export, but verify two things. First, make sure you are pulling the payment amount for each check, not a bill subtotal or a partial-payment artifact, so the figure matches what actually cleared. Second, if a single bill was paid with two checks, each check needs its own row with its own number and amount; do not let two physical checks collapse into one line.
For dates, FreshBooks exports in a standard format, but your bank's spec expects one specific format, commonly MM/DD/YYYY or YYYYMMDD. Check the bank's layout and make the export match before you generate the file. A date format mismatch either rejects the batch or, worse, gets silently misread.
Step 4: Convert the export into your bank's layout
Once you have a spreadsheet with check number, amount, and date per row, reshape it into your bank's exact file format. Banks each define their own fixed-width or delimited layout, and field positions are not interchangeable between banks. PositivePayMaker does this conversion in your browser: you upload the FreshBooks CSV or Excel file, map the columns (your check-number field to check number, the payment amount to amount, the date column to issue date), choose your bank's layout, and download a file ready for the bank's portal. It is free and runs entirely client-side, so your check data never leaves your browser and is never sent to a server.
It ships with 11 bank layouts, including specs published by Chase and Huntington. If your bank is not in the list, the custom format builder lets you match any layout field by field. See all supported formats to check yours, and the file format guide if you want to understand the structure first.
Where to find your bank's exact spec
FreshBooks cannot tell you the layout; only your bank can. Positive pay setup lives in the bank's business or treasury online banking portal, usually under a "Positive Pay," "Fraud Prevention," or "Check Management" section, and the bank publishes a file specification (a PDF that lists each field, its width, and its position). Many banks run positive pay on a treasury platform such as Centrix, Q2, Fiserv, or FIS, so the upload screen and accepted file types depend on which platform your bank uses. If you cannot find the spec, ask your treasury or business-banking contact for the "check issue file format" document, then reproduce it with the custom format builder.
Validate the first file before you rely on it
Treat your first FreshBooks-to-positive-pay file as a test. Run it through the file validator to catch structural problems, then upload it to your bank and confirm two things: that the bank accepts it, and that the check numbers and amounts line up with what you actually wrote. A field off by one position rejects the whole batch, and bank specs do change. Verify once, and every later file becomes routine.
Is a paid desktop tool worth it for FreshBooks?
For most FreshBooks users, no, but it depends on volume (pricing current as of 2026). Big Red Consulting's Positive Pay File Creator is built around QuickBooks, runs only on Windows, and starts around $119 the first year then about $99 a year; it is not aimed at FreshBooks. Treasury Software's Bank Positive Pay is installed Windows software at roughly $30 to $90 per month, and it carries 350-plus bank layouts, which can earn its keep if you issue large volumes across many banks. MoneyThumb and ProperSoft also sell paid desktop converters. If you already have a clean export from FreshBooks and a handful of bank accounts, a free browser tool covers the same ground with no install and no subscription. Higher-volume treasury teams may still prefer a paid package for its layout library and batch features.
The workflow here is the same one users of other cloud accounting tools follow, with different field names. If you also run QuickBooks, see the QuickBooks positive pay guide, which notes that QuickBooks also cannot export a positive pay file natively.