Building a Regions Bank Positive Pay File for iTreasury

Regions Bank runs check positive pay through Regions iTreasury, its in-house treasury management platform, with a lighter version called Check Inspect for smaller accounts. The service compares every check presented against your account to the list of checks you actually wrote. If the dollar amount, serial number, or (optionally) the payee name does not match your issue file, Regions flags the item as an exception in iTreasury and waits for you to pay or return it.

The piece that trips people up is the issue file itself. Your accounting software has the check data, but it almost certainly will not export in the shape Regions wants. QuickBooks, for one, has no native positive pay export at all. This page walks through the published Regions CSV layout, where the file goes inside iTreasury, and how to produce it without retyping your register by hand.

The published Regions CSV layout

Regions publishes a CSV (comma-delimited) help card for the issue file. The layout is five columns, in this order, with no extra fields:

A few details from the help card are worth repeating because they are the usual cause of a rejected file. The check number in Column C has to equal what is encoded in the MICR line, not a display number or a memo reference. The amount needs the trailing cents even when the figure is round, so 100 should read 100.00. And the issue/void flag is case-sensitive: a lowercase i will not be read as an issue record.

That layout is the format Regions published broadly. Even so, treasury setups get customized per client, and Regions also supports fixed-width and other delimited formats depending on how your account was provisioned. Before you rely on the five-column CSV above, confirm against the spec attached to your own iTreasury profile or ask your Regions treasury management contact for the file specification tied to your account. The published help card is a strong default, not a guarantee for every account.

Where the file goes in iTreasury

Positive pay lives inside iTreasury under the fraud or risk management area, alongside the daily exception decisioning screen. The general workflow at Regions looks like this:

  1. Write or print your checks as usual in your accounting system.
  2. Export or assemble the check register for the batch you just issued.
  3. Convert that register into the Regions CSV layout described above.
  4. Upload the issue file in iTreasury so Regions knows which checks are legitimate.
  5. Each business day, log in to review any exception items and choose pay or return. You can also set an automatic pay-or-return default for items you cannot get to in time.

Voided checks belong in the same file. Send the void as its own record with a capital V in Column E so Regions stops honoring a check you canceled. If a check clears that you never reported, it shows up as an exception, which is the system working as intended rather than an error on your end.

Getting your register into the right shape

If you keep books in QuickBooks, Xero, or a spreadsheet, the export you already have is close but not identical to what Regions reads. The columns are usually in a different order, dates come out as YYYY-MM-DD instead of MM/DD/YYYY, amounts may carry a dollar sign, and there is no issue/void indicator column at all.

PositivePayMaker handles that reshaping. It is a free, browser-based tool: you load your CSV or Excel register, map your columns to the Regions fields, and it writes a clean file in the five-column layout. Everything runs locally in your browser, so your check numbers, amounts, and account data never get uploaded to a server. If your account uses a layout that differs from the published CSV (fixed width, a different field order, or a header row Regions expects), the custom format builder lets you match it field by field, and the positive pay file format reference explains how issue files are structured in general.

Because QuickBooks cannot produce a positive pay file on its own, this conversion step is unavoidable for QuickBooks users no matter which tool they pick. If you are on QuickBooks specifically, the QuickBooks positive pay guide covers the export and mapping in more detail.

Paid alternatives, and when they make sense

There are commercial tools that do the same job, and for some shops they are a reasonable fit. 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 the exported file. Treasury Software's Bank Positive Pay is an installed Windows product in the roughly $29.95 to $89.95 per month range and ships with 350-plus bank layouts already built. MoneyThumb and ProperSoft sell paid desktop converters in a similar vein.

If you generate positive pay files across many accounts, pull directly from QuickBooks Desktop on a Windows machine every day, or want vendor support with a contract behind it, a paid desktop tool can earn its cost. For a single business converting a register now and then, a free client-side converter covers the same ground without a subscription or an install.

Always verify the first file

Whatever you use to build it, treat your first Regions file as a test. Upload it in iTreasury and confirm Regions accepts it cleanly, then check that the checks you reported actually clear without being flagged. Banks reject files over small format issues: a missing leading zero on an account number, a date in the wrong order, or a lowercase issue indicator. Catching that on the first batch is far cheaper than discovering it when a legitimate check gets returned. Once one file goes through clean, the same mapping will work for every batch after it.

Create your positive pay file