ZERO-UPLOAD BROWSER WORKFLOWVerified Tier-A (bofa-arp-316-payee)Verified Nov 2026

QuickBooks Desktop (.IIF) to Bank of America Positive Pay Guide

Step-by-step guide to exporting checks from QuickBooks Desktop (.IIF) and converting them into a bank-ready Bank of America Positive Pay file without Split duplicates, negative amounts, or leading-zero corruption.

Recommended Accounting Report

QuickBooks Desktop .IIF Transaction Export (!TRNS / !SPL / !ENDTRNS)

Export File: Intuit Interchange Format (.IIF)

Target Bank Specification

Bank of America

Verified Tier-A layout (bofa-arp-316-payee) with 8-rule Pre-Flight & Byte Ruler.

Step-by-Step Export & Positive Pay Compilation Checklist

  1. 1

    Export check transactions or check batch from QuickBooks Desktop

    In QuickBooks Desktop, export your check register batch to .IIF (preserving !TRNS header rows, TRNS primary check lines, SPL GL distribution lines, and ENDTRNS markers).

  2. 2

    Parse TRNS rows and drop SPL GL offset rows locally

    Drop your .IIF file into PositivePayFileGenerator.com. The browser normalizer reads ONLY TRNS lines (filtering TRNSTYPE = CHECK or BILLPMT) and ignores all SPL allocation lines so split invoices never duplicate check serials.

    Uploading raw .IIF files or manually opening .IIF in Excel exposes multi-line SPL rows and negative GL amounts to the bank.
  3. 3

    Review extracted Voids and Payee strings

    Verify checks marked "VOID" in MEMO or represented by reversing +/- pairs carry the bank-specific Void transaction code.

  4. 4

    Compile to Bank of America Positive Pay specification

    Select the verified Bank of America preset (bofa-arp-316-payee) inside PositivePayFileGenerator.com, verify the 8-rule Pre-Flight Check banner shows 0 blocking errors, and download your 316-byte Fixed-Width ARP (H/O/V/T) ready for upload.

    BofA CashPro® 316-byte files pad Check # to 10 zeros, Amount to 12 implied cents, and Payee up to 256 bytes.

Portal Rejections Prevented Automatically

  • SPL expense/invoice allocation rows creating 2x-10x duplicate check entries if converted naively
  • Negative GL offset amounts on TRNS/SPL pairs confusing fixed-width implied cents fields
  • Tabs or quotes inside vendor names shifting QuickBooks Desktop column alignment
  • QBD .IIF multi-split expense amounts misstating CashPro® T-trailer dollar hashes

Controller Pre-Upload Verification Checklist

  • Verified only TRNS check rows are included (all SPL rows skipped)
  • Confirmed MEMO "VOID" checks flagged with correct Void status code
  • Validated serial numbers against check stock printed batch
  • Selected Bank of America format (316-byte Fixed-Width ARP (H/O/V/T))

Other Accounting Integrations for Bank of America

Integration FAQ

Why does Bank of America reject raw QuickBooks Desktop (.IIF) CSV exports?

Raw QuickBooks Desktop (.IIF) exports include report banner lines, split/GL detail rows, parenthesized negatives, or UTF-8 BOM markers that conflict with Bank of America (316-byte Fixed-Width ARP (H/O/V/T)) requirements. Running the export through PositivePayFileGenerator.com normalizes the register 100% locally in your browser first.

Does QuickBooks Desktop (.IIF) accounting data leave my browser when formatting for Bank of America?

No. PositivePayFileGenerator.com parses your check register, calculates integer-cent batch totals, applies byte alignment rules, and builds your upload file entirely client-side with zero server uploads.