QuickBooks Journal Entry CSV Import for Payment Processor Payouts

QuickBooks Online provides more than one CSV import path, and choosing the correct one matters for processor payouts. A payout is a split accounting event, so the journal-entry import is the useful target.

The six QuickBooks journal columns

QuickBooks' journal-entry import uses Journal No., Journal Date, Account Name, Description, Debits and Credits. Multiple rows can share one Journal No., allowing the lines for one payout to stay together.

Map source columns instead of renaming them by hand

Processor exports use different labels such as Settlement ID, Deposit Date, Gross, Fees, and Payout Amount. The builder inspects the CSV, suggests common mappings, and lets you choose the actual source columns. Payout ID, date and gross are required; fee, net and description are optional.

Validate before export

The preflight catches malformed dates, invalid monetary values, ragged CSV rows, bad QuickBooks account paths, zero-value payouts, and net values that do not equal gross minus fees. It creates no download until the source rows pass.

Import through Journal Entries

In QuickBooks Online, use the Journal Entries import workflow, upload the prepared CSV, map the six headers, and review the preview before importing. Do not upload this file through the banking transaction uploader; that workflow expects bank-transaction rows rather than a multi-line journal.

Local processing

The CSV is inspected and transformed in the browser through Nablyx's shared Processing SDK. The payout rows are not uploaded to Nablyx to build the output file.

quickbooks-processor-payout-csv-import-builder

See the transformation

Awkward source headers become import-ready columns.

Rename the columns you need while keeping every value under the correct header.

cust_idcustomer_id

given_namefirst_name

mailemail

✓ Values stay with the right column