Always use common sense when uploading documents: treat Juno like a second-year preparer. It will handle all the basic information well, but confusing data, duplicate uploads, large and complex datasets, or schedules lacking clear explanation can all cause accuracy issues.
Schedules
Best Practice
Do not duplicate line items within the document.
Clearly describe each dollar amount and, ideally, pre-categorize the type of income or expense.
Include descriptive information such as business name, address, or rental information.
Avoid more than 100 line items per document.
Hard Limitation
CSV/Excel schedules: limited to 1000 lines, up to column ZZ.
PDFs: limited to 250 pages.
Basic Source Documents (W-2s, 1099s, 1098s)
Best Practice
Non-standard IRS formats, screenshots, or scans are acceptable—but blurry images can cause errors.
Keep PDFs under 75 pages to ensure correct page orientation after processing.
Hard Limitation
No strict technical limitation, but documents over 250 pages may create classification challenges.
Brokerage Statements
Best Practice
For large accounts with thousands of transactions, consider pruning transaction pages and retaining only summary sub-totals.
Important to Note
Some brokerage statements are poorly structured. Juno performs best with summary pages and clear sub-totals.
If only raw transaction lists are provided, Juno may struggle.
Juno does not extract peripheral information like fees, but these are flagged in the Tax Preparation Report.
Hard Limitation
More than 250 pages per account will be clipped to the first 250 pages during extraction.
K-1 Documents
Best Practice
Always review K-1 data carefully, especially when supplemental or state information is included.
Important to Note
Juno’s K-1 accuracy falls below 99% when state information is included.
Many values may be flagged for review in such cases.
Treat K-1s with state and statement data carefully during review.
Hard Limitation
More than 250 pages per K-1 will be clipped to the first 250 pages during extraction.