Skip to main content

Understanding Juno's Additions to Issuer Name

Why Juno adds in details for the Taxpayer/Spouse, Account Number and EIN to the Issuer Name of Source Documents

Updated over a week ago

Juno includes the option to add a Taxpayer (TP) or Spouse (SP) designation to source document names, along with the issuer’s EIN or account number.

This naming convention is designed to make form identification clearer, especially in returns where there are more than one document from the same issuer (for example, two W-2s from the same employer). By including the TP/SP and number, you can quickly distinguish the forms without needing to open each document.

This is particularly helpful during export when form matching with year over year returning clients. Juno scans issuer names when mapping documents during export, and having clear, consistent identifiers, like TP/SP designations and EINs, can make that process significantly easier for users. When these details are included, they appear in the Action column drop down during export. This gives you immediate clarity on which forms match between Juno and your tax software, allowing you to confidently choose the correct mapping without needing to open or cross-check documents.

Without these identifiers, existing forms in your tax software from the same issuer can appear identical during the scan. In those cases, additional manual review may be required to confirm you’ve selected the correct form, which can slow down the export workflow.

Important Note: This is an Optional Setting

If you prefer to not have this added to the Issuer names for documents in your tax software, you can switch to a simplified naming format at any time.

To do this:

  • Open Organization Settings

  • Toggle Use Simple Issuer/Payer Names on

  • Scroll down and click Save

This allows your team to choose the document naming convention that best fits your process.

If you have additional questions on this feature, please contact Customer Support via [email protected] or in live chat inside of the Juno Web App.

Did this answer your question?