Date‑Range Report Exports Produce Non‑Numeric Start Dates and Concatenate Date Ranges

Question

Summary:    Reports that use date ranges export non‑numeric start dates that cannot be used directly in Excel. Only the CSV export path separates the start and end dates into distinct cells; all other export paths concatenate the two dates with padding characters. Even in CSV, the start date contains a trailing hyphen, making it non‑numeric.

* Can this export behavior be reviewed for improved usability and consistency?

Reproduction Steps

This occurs in any report that groups data by date ranges.   A minimal reproducible example:

* Open Reports → Spending → Spending by Category, set Date Range: Year to Date, set Columns: Month, then click Show Report
* Export using: Clipboard, CSV, Excel (XLSX), Text, or PDF→CSV
* Inspect the date‑range row(s) in Excel or a text editor

Observed Behavior

* Clipboard: start/end concatenated; hyphen + space (ASCII 32)
* XLSX: start/end concatenated; hyphen + line feed (ASCII 10)
* CSV: start and end dates in separate cells; end date is numeric, start date has trailing hyphen (non‑numeric)
* PDF→CSV: same as CSV

Across all export paths except CSV, the dates are concatenated.  Across all paths, the start date is non‑numeric.

Impact

The exported date‑range values cannot be used directly for Excel analysis. Users must manually remove padding characters or split concatenated date ranges before performing basic operations such as sorting, grouping, pivoting, or date arithmetic. This affects all export methods and any report that produces date‑range rows.

pablomiller · Answer

Thanks, @q_lurker — agreed. Clipboard is often the most convenient path when pasting values into an existing workbook with established formatting.

@NotACPA — the Print → Export → CSV path is documented in the originally reported behavior above. It does separate the start and end dates into distinct cells, but the start date still contains a trailing hyphen, making it non‑numeric.

Quicken actually provides multiple export pathways — four under the Export button (Clipboard, Excel, Text, and PDF) and three legacy options under Print (CSV, Text File, and Tab‑Delimited). The specific number isn’t the issue; the issue is that none of these pathways produce consistent, clean, fully numeric date values suitable for direct use in external tools such as Excel. Each path introduces a different formatting complication, which is why the originally reported behavior compares them side‑by‑side.

I’m hoping this can be reviewed for improved usability and consistency, and also to understand whether there is a root reason why the export logic does not produce clean, fully numeric start and end date values for external analysis.

If a Moderator or SuperUser has time to review and confirm the reported behavior across the export paths, that would be very helpful. And if there are any questions about what I’ve documented, I’m happy to clarify.

q_lurker · Answer

@NotACPA I use Clipboard whenever I can for moving a report into Excel.  It can be pasted in to an existing file and the formatting in that existing file is maintained.  In contrast, a csv file opens as a unique file within Excel with no formatting applied.

NotACPA · Answer

Why are you using the Clipboard instead of the PRINT, Export to CSV file option?  The CSV file produced thereby can be imported directly into Excel.