Juno’s Form Matching feature exists to give users more control over how extracted client data flows into their tax software. Instead of treating every document as new information, mapping allows Juno to understand where that data belongs before export.
By default, Juno creates new forms when exporting data to tax software. While this works well for many workflows, it can result in duplicate forms when working with returning clients or pro forma returns. The scanning and indexing process lets you map documents to existing forms, ensuring data is exported to the correct place rather than creating a new version of the same form. This is especially valuable for prior-year carryovers and pro forma returns, where maintaining continuity matters. By indexing documents to existing forms, users can reduce cleanup, preserve form history, and streamline review.
Juno will scan the return in your tax software before the data is exported. To use the data mapping feature, you will select the appropriate option for each document from the drop down in the Action column on the right-hand side of the integration app.
Legend
X = Form is supported for matching
Form Type | Lacerte | Drake | CCH | ProConnect |
W-2 | X | X | X | X |
1099-INT | X | X | X | X |
1099-DIV | X | X | X | X |
1099-R | X | X | X | X |
1099-G | X | X | X | X |
1099-MISC | X | X | X | X |
1099-NEC | X | X | X | X |
1099-B | X | X | X | X |
Schedule C | X | X | X | X |
Schedule E | X | X | X | X |
Schedule F | X | X | X | X |
K-1 (1065) | X | X | X | X |
K-1 (1120-s) | X | X | X | X |
K-1 (1041) | X | X | X | X |
1095-A |
| X | X |
|
1098 |
| X | X |
|
1098-T |
|
| X |
|
1098-E |
|
| X |
|
1099-LTC |
|
| X |
|
1099-SA |
|
| X |
|
The Form Matching process will look different with tax software each integration. For a detailed guide on this process, please refer to the proper article for your software: