Skip to main content

Human In The Loop

An overview of how Juno ensures human involvement in our automated data extraction and export process.

Updated over 2 weeks ago

Human-in-the-Loop is the review screen where users can confirm, validate, and adjust data extracted by Juno. It presents a structured, field-by-field view of detected values along with confidence indicators, highlighting areas that may require attention. This step allows for human judgment in your preparation workflow, ensuring extracted information is accurate and complete before it is validated and exported to tax software.

Once you click “Review Data” you’ll be able to validate your documents. It’s important to know what each field status means:

  • Possibly Missing - The system did not extract a value and believes there might be a value missing. In most cases, fields with this status are blank on the form and require you to validate that it is in fact blank. You can do this by hitting the “Validate” button below the field.

  • Flagged for Review - The system suggests taking a look at this field to double check. Oftentimes a value may be calculated (such as gain/loss on a 1099B) but the system will request verification of correctness.

  • Validated - The value was extracted with near perfect confidence and doesn’t require review.

Human-in-the-loop for IRS Source Documents

For forms such as W-2s, 1098s, and 1099s, K-1s, Juno displays the source document on the left hand side and lists each of the data field boxes on the right. (Only fields with data extracted will appear, you can view empty boxes by opening up Filter Options and selecting Show Empty Fields).

Best Practices:

  • Ensure to validate using the "Validate" button after making changes (to items like Taxpayer/Spouse)

  • When you change a box, click the “Validate” just below it to lock in the change

  • Utilize the Next and Previous Document buttons at the top and bottom of the screen for quick and easy navigation

Explaining Date Acquired and Date Sold Logic in Juno

When Juno processes forms containing transactions, individual transactions are aggregated into summary rows. These rows are grouped by transaction type (short-term vs. long-term) and reporting status. Because these entries are aggregated, tax software requires standardized placeholder values for certain fields.

Year-Specific Behavior

Juno automatically applies the correct year-specific dates based on the return you’re preparing. The long-term acquisition date stays the same because it represents assets held for more than one year.

User Experience

These dates and quantities are expected and won’t affect the accuracy of your reported gains or losses. They’re simply placeholders that allow your 1099-B data to be accepted and processed correctly by tax software.

Human-in-the-loop for Schedules C, E, and F

For source documents uploaded for Schedules, Juno does not display the document itself. Instead, it pulls all of the information from the document and groups items into categories. You are able to review the information as an individual item and the category total. When validating the data, you are able to move items between categories if they have been classified incorrectly. You are also able to edit the title and amount of each item, delete them, and add new ones if needed. When reviewing the data, you can validate each category one by one or use the “Mark as Validated” feature to validate all at the same time.

Best Practices:

  • If you want to move multiple items from a category at once, you can select a group of items by checking the box next to the specific items on the left and use the “Move Selected Items To” drop down feature on the top right.

  • If your documents don’t have the business name and information listed, you can enter that directly in Juno

Did this answer your question?