Skip to content

1099FIRE Report

The 1099FIRE Report is listed in the Reports pop-up accessed when clicking the Reports button It can be run either on Search results or Portfolios, and takes two parameters, Start Date and End Date (referring to the Purchase Date or the Closing Transaction’s Completed Date, see below).

This Excel file is designed to be used with the 1099FIRE software to generate 1099-LS forms. This application allows the import of an Excel file (with extension xls or xlsx) via the Import button or the drag and drop area. More information is available at https://www.1099fire.com.

The red area above is further described below by splitting it into TOP LEFT, BOTTOM LEFT and BOTTOM RIGHT sections. The report extract below shows these sections and the table beneath describes the information displayed in the report depending on whether there is a closing transaction and the transaction origination.

Have Closing Transaction?Transaction OriginationTOP LEFT ("Acquirer")BOTTOM LEFT ("Payment Recipient")BOTTOM RIGHT ("Entity" / "Acquirer's information if different from Acquirer")
YES[blank] or SecondaryPrice Allocation: ProviderRepeated for Price Allocation: Sellers, Brokers, AgentsCase Participant: Buyer
YESTertiaryCase Participant: Securities IntermediaryRepeated for Price Allocation: Sellers, Brokers, AgentsCase Participant: Buyer
NONot applicableCost/Maturity/Disposal: PSA Purchase EntityRepeated for Cost/Maturity/Disposal: PSA Purchase Origination Counterparty, PSA Purchase Counterparty, PSA BrokerServicing: Customer Service Address

If a Case has a completed Closing Transaction, where the Completed Date is between the Start and End Date (inclusively) when running the report, then the report uses the mappings associated with the Closing Transaction; see the Closing Transaction Mapping column in the annotated example below. There can be multiple rows for each Case, corresponding to the split of payments in Price Allocations.

If there is no Closing Transaction in scope for a Case, then the report will source the data instead from the Cost/Maturity/Disposal page, if the Purchase Date falls between the Start and End Date specified when running the report. Again, there can be multiple rows for each Case – one for PSA Purchase Origination Counterparty, PSA Purchase Counterparty and PSA Purchase Broker, if they are populated. The mappings in this scenario, when no ClosingTRransaction exists, are shown in the far right column in the table below.

The colors in the table below correspond to the section colors in the graphic above.
HeadingReport ColumnMapping when a Closing Transaction existsMapping when no Closing Transaction exists, using Purchase Sale Agreement/PSA
Case ReferenceACase/Case Reference (Note: this is not required by the 1099FIRE software, but added by ClariNet LS for clarity)Case/Case Reference (Note: this is not required by the 1099FIRE software, but added by ClariNet LS for clarity)
VoidBBlankBlank
CorrectedCBlankBlank
1 row x Price Allocation (for Sellers, Brokers, Agents, with a Payment Type of Compensation Fee or Premium Reimbursement):1 row for Case/Cost, Maturity, Disposal/Cost: PSA Purchase Counterparty 1 row for Case/Cost, Maturity, Disposal/Cost: PSA Purchase Origination Counterparty 1 row for Case/Cost, Maturity, Disposal/Cost: PSA Purchase Broker
Policy NumberQCase/Policy: Policy NumberCase/Policy: Policy Number
Issuer NameTCase/Policy: CarrierCase/Policy: Carrier

Top Left ("Acquirer")

🟨 Yellow Top Left Section

HeadingReport ColumnMapping when a Closing Transaction existsMapping when no Closing Transaction exists, using Purchase Sale Agreement/PSA
Acquirer
Name
Dif Tertiary: Closing Transaction/Case Participant: Securities Intermediary else (Secondary or blank): Closing Transaction/Price Allocation: ProviderCase/Servicing/PSA Purchase Entity
AddressEFirst Address from selected CRM: Street AddressFirst Address from selected CRM: Street Address
CityFFirst Address from selected CRM: CityFirst Address from selected CRM: City
StateGFirst Address from selected CRM: StateFirst Address from selected CRM: State
ZipHFirst Address from selected CRM: ZipFirst Address from selected CRM: Zip
PhoneIFirst Telephone in Contact Details from selected CRM: PhoneFirst Telephone in Contact Details from selected CRM: Phone
TINJSelected CRM: Tax IDSelected CRM: Tax ID

Bottom Left ("Payment Recipient")

🟩 Green Bottom Left Section

HeadingReport ColumnMapping when a Closing Transaction existsMapping when no Closing Transaction exists, using Purchase Sale Agreement/PSA
TINKSelected CRM: Tax IDSelected CRM: Tax ID
Payment
Recipient Name
LSelected CRM: NameSelected CRM: Name
AddressMSelected CRM: Street AddressSelected CRM: Street Address
CityNSelected CRM: CitySelected CRM: City
StateOSelected CRM: StateSelected CRM: State
ZipPSelected CRM: ZipSelected CRM: Zip
AmountRPer Price Allocation row: AmountFor PSA Purchase Counterparty: Case/Cost, Maturity, Disposal/Cost: PSA Purchase Price For PSA Purchase Origination Counterparty : Case/Cost, Maturity, Disposal/Cost:Origination Fee For PSA Purchase Broker: Case/Cost, Maturity, Disposal/Cost: PSA Purchase Broker Fee
DateSPer Price Allocation row: Payment DateCase/Cost, Maturity, Disposal/Cost: Purchase Date
AmountRPer Price Allocation row: AmountFor PSA Purchase Counterparty: Case/Cost, Maturity, Disposal/Cost: PSA Purchase Price For PSA Purchase Origination Counterparty : Case/Cost, Maturity, Disposal/Cost:Origination Fee For PSA Purchase Broker: Case/Cost, Maturity, Disposal/Cost: PSA Purchase Broker Fee
DateSPer Price Allocation row: Payment DateCase/Cost, Maturity, Disposal/Cost: Purchase Date

Bottom Right ("Entity" / "Acquirer's information if different from Acquirer")

🟪 Purple Bottom Right Section

HeadingReport ColumnMapping when a Closing Transaction existsMapping when no Closing Transaction exists, using Purchase Sale Agreement/PSA
Entity NameUClosing Transaction/Case Participant: Buyerempty
AddressVFirst Address from selected Buyer CRM: Street AddressCase/Servicing: Customer Service Address: Street Address
CityWFirst Address from selected Buyer CRM: Cityfrom selected Address: City
StateXFirst Address from selected Buyer CRM: Statefrom selected Address: State
ZipYFirst Address from selected Buyer CRM: Zipfrom selected Address: Zip
PhoneZFirst Telephone in Contact Details from selected Buyer CRM: PhoneCase/Servicing: Customer Service Telephone
In the 1099FIRE software, if the grey input boxes do not line up with the red lines of the form, check the Properties of the Windows shortcut for the app, on the Compatibility tab, click the Change high DPI setting button, and in the lower part in the High DPI scaling override section check the box Override high DPI scaling behaviour and for Scaling performed by choose System (Enhanced). The relevant screens are shown below.