ZERO-UPLOAD BROWSER WORKFLOWTier-B Portal SpecVerified Nov 2026

QuickBooks Desktop (.IIF) to Truist Bank Positive Pay Guide

Step-by-step guide to exporting checks from QuickBooks Desktop (.IIF) and converting them into a bank-ready Truist Bank 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

Truist Bank

Portal-issued specification — sanitize raw ERP export or compile your portal PDF in 10s.

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 Truist Bank Positive Pay specification

    Review your Truist Bank portal import template (Headerless CSV or Digital Treasury Fixed-Width), compile your custom or portal-issued spec via our zero-PII AI Bank Spec Compiler if fixed-width, and run the 8-rule Pre-Flight sanitizer before portal upload.

    Truist Digital Treasury CSV maps omit column headers and require ASCII uppercase vendor strings.

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
  • Accented characters in QBD .IIF NAME columns triggering Truist Payee Match failures

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 Truist Bank format (Headerless CSV or Digital Treasury Fixed-Width)

Integration FAQ

Why does Truist Bank 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 Truist Bank (Headerless CSV or Digital Treasury Fixed-Width) 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 Truist Bank?

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.