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

QuickBooks Online to Bank of America Positive Pay Guide

Step-by-step guide to exporting checks from QuickBooks Online 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

Check Detail Report (filtered to Paid / Printed Checks & Voided Checks)

Export File: CSV / Excel Export (.csv / .xlsx)

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

    Run the QuickBooks Online Check Detail report

    Open Reports -> Search for "Check Detail", set Transaction Date to your check run range, and click Customize -> Filter -> Checking Account so only one bank account is exported per file.

    Never use Expenses by Vendor Summary; QBO inserts "-Split-" lines and multiple expense lines for single checks.
  2. 2

    Enable Num, Date, Name, Amount, and Memo/Description columns

    Ensure "Num" (Check Number), "Date", "Name" (Payee), "Amount", and "Memo/Description" appear before exporting via Export -> Export to CSV.

  3. 3

    Do NOT reopen the raw CSV directly in Excel

    Drag the untouched QBO CSV directly into PositivePayFileGenerator.com. Our browser engine automatically strips top company banner lines, skips "-Split-" allocation lines, removes the bottom "TOTAL" row, converts parenthesized negatives "($245.50)" into Void flags, and preserves leading zeros.

    Opening and saving a CSV in Excel strips leading zeros from 8-digit account numbers and check serial numbers and adds a UTF-8 BOM that breaks byte-1 parsers.
  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.

    CashPro® 316-byte ARP expects letter "O" (not zero) in byte 13 for Issues, "V" for Voids, and H/T wrapper totals.

Portal Rejections Prevented Automatically

  • Split expense lines duplicating the same check number inside Check Detail exports
  • Parenthesized negative voids "($245.50)" and "-$1,500.00" rejecting numeric bank parsers
  • Top company header rows and bottom "TOTAL" summary row corrupting line counts
  • Excel silently dropping leading zeros and injecting UTF-8 BOM (EF BB BF) bytes
  • Including Void check sums inside the CashPro® T-trailer when Issue-only net total is expected

Controller Pre-Upload Verification Checklist

  • Filtered Check Detail to single bank account
  • Confirmed "-Split-" sub-rows collapsed to one item per Check #
  • Verified Voids carry explicit Void indicator instead of negative signs
  • Checked ASCII payee transliteration (no curly quotes or diacritics)
  • 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 Online CSV exports?

Raw QuickBooks Online 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 Online 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.