Invoice CSV Preflight & Whole-Invoice Batch Pack

Review a supplied invoice CSV before manually mapping it into an eligible US QuickBooks Online invoice-import workflow. Keep each invoice together, retain source cell values, and get a traceable receipt with original record ordinals, line counts, item-amount totals and input hashes.

This Actor processes your supplied CSV in Apify cloud. It does not connect to QuickBooks, import data, verify account/customer/item existence, or certify tax/accounting correctness. Before uploading any financial CSV, set your Apify account/resource access to Restricted. The platform stores input before Actor code starts, so the Actor cannot retrospectively guarantee the privacy of the upload window. Use only data you are authorized to upload. Run inputs, receipts and CSV files are stored in your Apify run storage; do not share run links or credentials with unauthorized people.

The source schema marks csvText as isSecret: true. Apify documents encrypted Console input and field encryption before default INPUT storage for API runs. Actor.get_input() decrypts the field for processing. The existing anonymous-denial check and Restricted run, dataset and output requirements continue to apply. Other input fields and generated CSV files retain their storage access controls.

Exact supported profile

• UTF-8 CSV text with exact headings: InvoiceNo,Customer,InvoiceDate,DueDate,ItemAmount. Optional columns are preserved.
• Explicit declarations: region: "US", salesTaxEnabled: false, currency: "USD", and dateFormat: "ISO", "DMY" or "MDY". Unknown context is blocked. USD-only and these exact headers are this tool's restrictions.
• At most 1,000,000 CSV UTF-8 bytes, 5,000 source records and 500 whole invoices per run; total input JSON at most 2,000,000 UTF-8 bytes. Output batches retain at most 100 invoices and 1,000 rows. One invoice larger than a batch is blocked.
• Conflicting customer/dates/currency within an invoice, negative amounts, unsupported number/date formats, formula-like text and unreviewed identical rows block the entire input. This is a conservative local-profile review, not a prediction of every native importer outcome.

Try the fictional sample

The prefilled input contains 3 fictional invoices / 5 CSV line records. No QuickBooks login/token, external vendor fetch or customer data is needed. Platform storage/privacy API checks run under your existing Apify permissions. package saves at most three invoice receipts for that sample; preview produces a free diagnostic summary without CSV/ZIP.

{
  "csvText": "InvoiceNo,Customer,InvoiceDate,DueDate,ItemAmount\nDEMO-001,Fictional Company,2026-01-01,2026-01-31,12.50\n",
  "region": "US",
  "salesTaxEnabled": false,
  "currency": "USD",
  "dateFormat": "ISO",
  "mode": "package"
}

Outputs and charges

$0.002 per saved whole-invoice validation receipt ($2 per 1,000 invoices), a single invoice-receipt event. A receipt includes invoice ordinal/key hash, source record and physical-line ordinals, line count, item-amount sum and input SHA256. It contains no CSV row cells or customer names. The item-amount sum is not a verified invoice grand total.

Preview and blocked/invalid input produce diagnostics without invoice receipt charges. There is no startup fee or positive dataset-item charge. Apify documents standard PPE platform-usage accounting and an optional PPE + usage setting. Check the live Apify pricing panel for any platform-usage component; the receipt-event rate alone does not establish that setting. Set maxTotalChargeUsd explicitly in API/CLI run options (for example 0.01); it limits invoice receipt events. The default fictional 3-invoice sample has $0.006 of receipt events in receipt-event charges; an owner smoke test is not customer revenue.

STATE identifies completion, acknowledged receipt count, budget-limited delivery and available export keys. A budget-limited run can complete with a smaller whole-invoice subset. CSV batches and native-review-pack.zip contain only the invoices whose receipt push/charge acknowledgement was confirmed. Zero receipt budget creates no CSV/ZIP. Preview does not expose a hidden CSV download.

Apify dataset writes and billing are not one atomic transaction. If a receipt push/charge acknowledgement is uncertain, the Actor stops without its wrapper retrying that uncertain operation or exporting its invoice. A receipt row may already exist or be charged. A later CSV/storage failure can leave useful paid receipts while exports are unavailable: STATE is incomplete/failed, and no successful package is claimed. Inspect existing run state before any manual rerun; a new run can incur new charges.

REVIEW contains free error codes and source ordinals for preview/blocked inputs. ERROR omits supplied values. Each hosted run checks anonymous INPUT access before reading CSV, rejects public/unknown input access, and requests Restricted access for only that run and its default dataset/key-value store. It requires restricted API readback plus unsigned anonymous access denial before processing/charging. If protection cannot be confirmed, it stops. These checks do not change account-wide settings, revoke existing explicit collaborators or prove upload-history privacy. Keep storage/run links, signed share URLs and access permissions under your control. Export download links can be absent until saved; check STATE first.

Native and integrated alternatives

QuickBooks' native importer already imports and validates invoice CSVs, with up to 100 invoices / 1,000 rows per file; its documented route is unavailable when sales tax is set up. Manual spreadsheet grouping plus the native importer may be enough.

SaasAnt Quick Import and Transaction Pro provide broader connected import, mapping and validation workflows. This Actor offers hosted exact-profile preparation and record receipts, rather than those integrations. It is not a unique invoice validator or a replacement for native account checks.

Limits

No QBO API/import, credentials, tax validation, live tenant validation, automatic repair, XLSX/PDF/OCR, multicurrency or general header mapping. Original cells are preserved, including optional fields; that does not prove native acceptance of every Unicode/control value. Inspect the files and map columns/dates manually before importing. This independent tool is not affiliated with Intuit.