How to create a U.S. Bank positive pay file for SinglePoint

U.S. Bank runs positive pay through its online treasury platforms: SinglePoint for larger commercial clients and SinglePoint Essentials for smaller businesses. The idea is the same on both. Each time you cut a batch of checks, you send the bank a check issue file listing every check you wrote. When a check is presented for payment, U.S. Bank matches the serial number, the dollar amount, and (if you turned on payee match) the payee name against your issue file. Anything that does not line up becomes an exception you review and decide to pay or return.

The hard part for most bookkeepers is not the bank screens. It is producing the upload file in the layout U.S. Bank expects, because accounting software rarely exports it. QuickBooks, for example, has no native positive pay export at all. This page explains where the U.S. Bank layout comes from, the general upload workflow, and how to build a matching file from a check register without buying desktop software.

Where the exact U.S. Bank file spec comes from

U.S. Bank does not publish a single universal positive pay file format on its public website. Your account's exact layout comes from the bank during setup, through your SinglePoint treasury implementation contact or your relationship manager, and it can vary by account and by what options you enabled (such as payee name verification). That is normal for treasury services and it is the honest answer: get your spec in writing from U.S. Bank before you build anything.

That said, U.S. Bank check issue files in the field generally follow a comma-delimited (CSV) structure built around five core pieces of data:

Some U.S. Bank layouts also carry one or two payee name fields when payee match is active, and U.S. Bank supports fixed-length text variants in addition to the comma-delimited form. Field order, the date format (often MMDDYYYY or MM/DD/YYYY), whether the file includes a header or trailer row, and the exact action codes are the details that must come from your bank's document, not from a blog. Do not assume the field order above; treat it as the shape of the file, and let your bank's spec set the specifics.

The general upload workflow

Once you have your layout and have run the check batch in your accounting system, the routine looks like this:

  1. Pull a register of the checks you issued: check number, payee, amount, and issue date.
  2. Convert that register into the file format your U.S. Bank spec describes (CSV or fixed-width, with the right action codes and date format).
  3. Sign in to SinglePoint or SinglePoint Essentials and go to the positive pay / check issue section.
  4. Upload the file and confirm the bank accepted it (totals and item counts should match your register).
  5. Each day, review any exceptions the bank flags and make a pay or return decision before the cutoff time.

Submit issue files the same day you print checks, and always before the cutoff your bank gives you, so a legitimate check is never flagged simply because the bank had no record of it yet.

Build the file from your register, free

You can map a check register to a U.S. Bank-style issue file with our free, browser-based tool. PositivePayMaker takes a CSV or Excel export of your register and writes out a positive pay file. It runs entirely in your browser, so your check numbers, payee names, and amounts never get uploaded to a server.

Because U.S. Bank's layout is account-specific, the right approach is the custom format builder: set the column order, the date format, the delimiter or fixed-width positions, and the action codes (ISS, CN, or whatever your spec lists) to match the document U.S. Bank gave you. Save that arrangement and reuse it every cycle. If the bank sends you a sample file, the built-in validator can check your output against the same shape before you upload. You can read the general field rules on our positive pay file format reference.

One step you should never skip: verify the very first file you generate with U.S. Bank. Upload it, confirm the bank accepts it cleanly, and check that the item count and dollar total match your register exactly. A single wrong column or date format can cause every check to reject. Once the first file clears, the format is settled and later runs are routine.

When paid software might make sense

PositivePayMaker is free and handles the conversion for most small and mid-size payers. If you run very high check volume or want a tool wired directly into QuickBooks, a paid desktop product may fit better, and it is fair to know the options.

Big Red Consulting's Positive Pay File Creator reads directly from QuickBooks. It is Windows-only, runs roughly $119 the first year and about $99 per year after, and the QuickBooks Online edition needs Excel installed. Treasury Software's Bank Positive Pay is the installed Windows product U.S. Bank itself references as a partner for importing files into SinglePoint Essentials; it ships with hundreds of bank layouts and is sold on a monthly subscription in the roughly $29.95 to $89.95 range depending on tier. MoneyThumb and ProperSoft also sell paid desktop converters. These suit shops that want native QuickBooks integration or a vendor support line. For a free path that keeps your data on your own machine, the browser tool covers the same job.

For more on the underlying file mechanics, see our file format reference, or compare how other banks handle this on the supported formats list.

Create your positive pay file