Exporting invoices to QuickBooks

Edited

Overview

The QuickBooks export produces a CSV in QB's native invoice import format, with QB-compatible date formatting, line items, and a structure that maps cleanly to your QuickBooks chart of accounts. Use it to bulk-load invoices instead of manual data entry.

Before you start

  • Confirm your QuickBooks file accepts CSV imports (QuickBooks Online or Desktop with the IIF/CSV import tool).

  • Map your Chamberly events or sponsorships to QB income accounts in Settings > Integrations > QuickBooks.

  • Decide a date range — typically a closed accounting period.

Step-by-step

  1. Go to Sidebar > Orders.

  2. Apply filters: date range, status (typically committed and completed).

  3. Click Export > QuickBooks invoices.

  4. Confirm the QB-compatible date format (MM/DD/YYYY).

  5. Choose whether to include refunded orders as credit memos.

  6. Click Generate export.

  7. Download the file and import it into QuickBooks via File > Utilities > Import > Excel Files (Desktop) or via the bulk import tool (Online).

What's in the file

  • Customer name (sponsor business), invoice number (Chamberly order ID), invoice date.

  • One line per sponsorship or package item with description, quantity, rate, and amount.

  • Discount line if a coupon or package discount was applied.

  • Total and balance fields formatted to match QB invoice templates.

Tips & best practices

  • Run a small test import first (5-10 invoices) to verify your account mapping.

  • Map sponsorship categories to specific QB income accounts for cleaner reporting.

  • Export monthly so QB stays in sync with Chamberly without huge backfills.

FAQ

Are taxes included?
If your sponsorships have tax configured in Chamberly, the export includes a tax line per invoice.

Can I include refunds?
Yes — toggle Include refunds as credit memos at export time.

Related articles

  • Exporting orders to CSV

  • Order status lifecycle

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.