NOTE: Multi-User configuration now available.  

*Please refer to IRS instructions for full detail of 2015 changes (https://www.irs.gov/pub/irs-pdf/i8966.pdf)

Important:  Each installation requires a unique authorization code in the XML so you will need to purchase your unique codes when filing (don’t give out your code to another installation!) as usage of this code will really put you in a bind with the IDES website.   As Per Pub 5124 FATCA XML v1.1:  the MessageRefID s data element is a free text field capturing the sender’s unique identifying number (created by the sender) that identifies the particular message being sent. The identifier allows both the sender and receiver to identify the specific message later if questions arise.  This is true for corrections so be sure that every physical location generating XML files has their own Authorization Code from 1099 Pro, Inc.

UPDATED: 

• Built in reports have been updated form the box changes. 
• All default maps and sample import files have been updated for 2015.
• Print layouts for all copies have been updated for 2015.
• All help files have been updated for 2015
• Includes latest IDES Packager (Please view release notes for this here). 

FORM CHANGES: 

• Renumbered boxes for 2015.
• No longer has the Direct Reporting NFFE Indicator.
• New boxes for Filer Category.
• Individual and Entity Account Holder indicators.
• Account Closed during the year indicator.

Excerpt from the FATCA XML V1.1 User Guide

Note the Unique value within the reporting FI has to be unique for all time.  That means we have to use a GUID.  Looking thru the XML spec correctable Input Types which would require a GIIN are:

Reporting FI – F
Sponsor – S or Intermediary – O
Account Report – A or Pool Report - R

C15. How can HCTAs and filers ensure that the DocRefID they are using is unique across all reporting FIs ?

The DocRefID data element should be a unique identifier of a correctable item across all reporting financial institutions and reporting periods. To ensure the identifier is truly unique, the IRS will be requiring the following format rule for creation of the DocRefID beginning October 1, 2015.  Until that time (i.e. for files submitted up through September 30, 2015), the IRS will accept DocRefIDs that comply with either the old DocRefID or this new format.  This transition period will allow those who want to begin using the new DocRefID rules to begin using them now to ensure uniqueness amongst FFIs, but it will not force those who prefer to continue using the old DocRefID rules to adopt the new rules until October 1, 2015.  

• The data format is <reporting FI GIIN><period character (.)><unique value across all time for the reporting FI>
• The first part – <reporting FI GIIN> is the GIIN for the reporting FI associated with the reporting group
• The second part is a period character (.)
• The third part – <unique value across all time for the reporting FI> is an identifying value for the referenced record that is unique within the reporting FI for all time. Use of a GUID is recommended but not required.

This element should contain at least 21 characters, which includes the first part – reporting FI GIIN, the second part – period character (.), and at least one alphanumeric character to represent the third part. The maximum length of DocRefID is 200 characters.  
DocRefID Examples:
S519K4.99999.SL.392.12291cc2-37cb-42a9-ad74-06bb5746b60b
127BM7.00001.ME.124.406abc8a1830490e847890ba3b13a646

References:

Publication 5124 FATCA XML v1.1 User Guide http://www.irs.gov/pub/irs-pdf/p5124.pdf

2015 8966 Instructions https://www.irs.gov/pub/irs-pdf/i8966.pdf