Mercury: monthly QuickBooks CSV or filtered transaction export?
Updated · 4 min read
Use Mercury Business’s monthly QuickBooks CSV when you need a month’s activity for bookkeeping. Use Transactions → Export filtered when you deliberately need a subset. A filtered file can be perfectly readable and still omit transactions required for historical bookkeeping. Record the account, month and filters before deciding which file to upload.
This guide concerns source selection for a US Mercury Business account. It does not certify a particular CSV’s headers or complete the QuickBooks import. If the only available source is a PDF, LocalExtract can prepare a local CSV for review; choose a suitable Mercury-native export first when one exists.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Choose the export by the question you need to answer
Mercury documents two distinct transaction export routes. Under Documents & Data → Statements, select the relevant account and use the row’s three-dot menu for QuickBooks CSV or NetSuite CSV. On Transactions, use Export all or apply filters and choose Export filtered, then select CSV or XLSX.
| Your task | Source to examine first | Remaining check |
|---|---|---|
| Prepare a complete historical month for QuickBooks | That account’s monthly QuickBooks CSV | Is the period complete and already partly recorded? |
| Investigate selected payments | Filtered Transactions export | Which transactions did each filter deliberately exclude? |
| Check the issued monthly record | Monthly statement | Do the account and document period match the working file? |
The export format names describe Mercury’s choices. They are not proof that your destination accepts every downloaded file without inspection. Keep NetSuite and QuickBooks selections distinct rather than changing a filename to make one look like the other.
Keep the monthly statement beside the transaction file
For the statement itself, Mercury’s monthly-statement instructions direct you to Documents & Data, the account dropdown and the relevant monthly statement. The page also distinguishes a current-month custom statement from a completed monthly statement.
A file made halfway through a month is not evidence that the remaining days contain no activity. For a historical-month job, record the actual coverage printed on the document and preserve the original download. If the account was opened during that month or the required statement is not yet available, resolve that source gap before treating a partial export as a full month.
Do not apply Mercury’s attachment-download limits to transaction CSVs: receipts and attachments are a separate download task. Here, the required result is the right transaction population, not a folder of supporting documents.
Work through a missing-income example
The following USD records are invented. M1–M3 are teaching aliases, not fields promised in a Mercury export.
| Alias | Monthly activity | Included in an expenses-only export? |
|---|---|---|
| M1 | +120.00 USD receipt | No |
| M2 | −35.00 USD payment | Yes |
| M3 | −5.00 USD fee | Yes |
The complete set has 3 transactions and a net change of +80.00 USD. The filtered set has 2 transactions and −40.00 USD. Both totals are internally consistent. The second set cannot answer “what happened in the whole month?” because its scope excludes M1; changing separators or converting the statement again would not fix that exclusion.
Now suppose M1 is already recorded in the destination. The full source month still contains all three events, but M1 is not automatically a new upload candidate. Distinguish source completeness from destination overlap. Confirm existing records before deciding what needs uploading or matching.
The synthetic Mercury scope exercise preserves these sets and expected totals. Python checks the example’s membership and arithmetic; it does not run a Mercury export or a QuickBooks import.
Hand off one identified source, not competing histories
Give the reviewer the account alias, month, original filename, export route and applied filters. If a filtered file was used only for investigation, label that purpose so it cannot later be mistaken for the full upload source. When replacing it with a monthly file, identify which earlier rows already reached the destination.
Follow the separate QuickBooks Online CSV import guide for destination limits, mapping and upload. Use the bookkeeping handoff guide for file revisions and receipts. This article’s deliverable is the justified Mercury source choice and its coverage, not another generic upload procedure.
For PDF-only work, LocalExtract processes one PDF at a time locally and exports date,description,amount. It does not create Mercury’s native QuickBooks export or synchronize your accounts. Download LocalExtract for a PDF source.
Official Mercury instructions checked on October 15, 2026.
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy