Atlantis Reports Breakdown (available in Notifications)

Reports Available in Atlantis Notifications

The following reports are created for each Participant and are available either via the Notifications page in the Atlantis User Interface or can be accessed via sftp.  Please reach out to atlantis.support@fia-tech.com if your firm is interested in accessing these reports via sftp. These reports are available to download by 3am Eastern Time.

• YTD Trade Metrics
  • Naming Convention: <Participant Code>_PRELIM_Mon-Year_YTD_YYYYMMDD.xlsx
  • Distribution Frequency: Daily; Cycle Business Day 1 to Payer Lock
  • Trade Population: All Atlantis trades for Participant – YTD
  • Suggested Use: Measure Year To Date performance in Atlantis and identify problem areas for remediation
• MTD Trade Metrics
  • Naming Convention: <Participant Code>_PRELIM_Mon-Year_MTD_YYYYMMDD.xlsx
  • Distribution Frequency: Daily; Cycle Business Day 1 to Payer Lock
  • Trade Population: All Atlantis trades for Participant – MTD
  • Suggested Use: Measure Month-To-Date performance in Atlantis and identify problem areas for remediation
• Trade Metrics Detail CSV
  • Naming Convention: <Participant Code>_PRELIM_Mon-Year_DETAIL_YYYYMMDD.csv
  • Distribution Frequency: Daily; Cycle Business Day 1 to Payer Lock
  • Trade Population: All Atlantis trades w/ details for Participant – MTD
  • Suggested Use: View current state of all MTD Atlantis trades at individual level
• Aged Receivable Trades CSV
  • Naming Convention: <Participant Code>_RCV_AGED_TRADE_YYYYMMDD.csv
  • Distribution Frequency: Weekly; File is made available each Sunday
  • Trade Population: Unsettled receivables trades from previous settlement cycles with following Cannot Settle Reasons
    • Fee Amount Missing
    • Fee Amount from Unofficial Agreement
    • Fee Currency Cannot Settle at Receiver
    • Fee Currency Cannot Settle at Payer
    • Fee on Hold
    • Fee Rejected
    • Fee Modified During Lock Period
    • Fee Missing Approval
    • Bank Account Missing
    • Pending Clearing Account Addition by Payer
    • Fee Missing Affirmation
  • Suggested Use: Identify largest causes of receivables trade backlog broken out by counterparty, exchange, currency etc. Focus backlog remediation efforts.
• Aged Payable Trades CSV
  • Naming Convention: <Participant Code>_PAY_AGED_TRADE_YYYYMMDD.csv
  • Distribution Frequency: Weekly; File is made available each Sunday
  • Trade Population: Unsettled payables trades from previous settlement cycles with following Cannot Settle Reasons
    • Fee Amount Missing
    • Fee Amount from Unofficial Agreement
    • Fee Currency Cannot Settle at Receiver
    • Fee Currency Cannot Settle at Payer
    • Fee on Hold
    • Fee Rejected
    • Fee Modified During Lock Period
    • Fee Missing Approval
    • Bank Account Missing
    • Pending Clearing Account Addition by Payer
    • Fee Missing Affirmation
  • Suggested Use: Identify largest causes of payables trade backlog broken out by counterparty, exchange, currency etc. Focus backlog remediation efforts.
• Legacy Prelim Settlement CSV
  • Naming Convention: <Participant Code>_LEGACY_PRELIM_SETTLEMENT_YYYYMMDD.csv
  • Distribution Frequency: Daily; Cycle Business Day 1 to Payer Lock
  • Trade Population: All Atlantis trades for Participant in current settlement cycle – Aggregations
  • Suggested Use: View status of all current cycle trades (aggregations) and determine steps needed to settle
• Legacy Prelim Trade CSV
  • Naming Convention: <Participant Code>_LEGACY_PRELIM_TRADE_YYYYMMDD.csv
  • Distribution Frequency: Daily; Cycle Business Day 1 to Payer Lock
  • Trade Population: All Atlantis trades for Participant in current settlement cycle – Individual Trades
  • Suggested Use: View status of all individual current cycle trades and determine steps needed to settle
• Daily Digest
  • Naming Convention: ATL_OUT_<Participant Code>_YYYYMMDD.zip
  • Distribution Frequency: Daily
  • Trade Population: Daily snapshot of trades processed for Participant – XML format
  • Suggested Use: Review and measure Participant activity for each day
• Legacy Daily Trades CSV
  • Naming Convention: <Participant Code>_LEGACY_DAILY_TRADE_YYYYMMDD.csv
  • Distribution Frequency: Daily
  • Trade Population: Daily snapshot of trades processed for Participant – Legacy Format
  • Suggested Use: Review and measure Participant activity for each day
• Legacy Final Settlement CSV
  • Naming Convention: <Participant Code>_LEGACY_FINAL_SETTLEMENT_YYYYMMDD.csv
  • Distribution Frequency: Monthly; Created on day after Payer Lock each Settlement Cycle
  • Trade Population: Final Settlement Status of all Atlantis trades for Participant in current settlement cycle – Aggregations
  • Suggested Use: View final settlement results for all current cycle trades (aggregations)
• Legacy Final Trade CSV
  • Naming Convention: <Participant Code>_LEGACY_FINAL_TRADE_YYYYMMDD.csv
  • Distribution Frequency: Monthly; Created on day after Payer Lock each Settlement Cycle
  • Trade Population: Final Settlement Status of all Atlantis trades for Participant in current settlement cycle – Individual Trades
  • Suggested Use: View final settlement results for all individual current cycle trades
• Docs Agreement Rate Schedule Issues
  • Naming Convention: <Participant Code>_RateScheduleIssues_YYYYMMDD.xlsx
  • Frequency: Weekly; File is made available each Sunday
  • Category: Performance Improvement
  • Content: Rate schedule issues (exchange or product) by counter-parties and contract volumes that do not result in rates on trades
  • Suggested Use: Helps firms identify Docs agreements with rate schedule issues that need to be fixed in order to improve match/settlement %
• No Agreement Found
  • Naming Convention: <Participant Code>_NoAgreementFound_YYYYMMDD.xlsx
  • Frequency: Weekly; File is made available each Sunday
  • Category: Performance Improvement
  • Content: Clearing accounts by counter-parties and contract volumes that do not result in rates on trades
  • Suggested Use: Helps firms identify accounts on trades that are not matching and need to be added to Docs agreements
• Estimate for Storage of Unsettled Contracts 
  
  • Naming Convention: <Participant Code>_MaintStorageEstimate_YYYYMMDD.xlsx
  • Frequency: Weekly; File is made available each Sunday
  • Category: Atlantis Billing
  • Content: Shows firm's estimates of maintenance fees to be charged monthly under the new pricing model for unsettled fees greater than 6 months from trade date
  • Suggested Use: Helps firms identify historic trades that should be settled in order to reduce maintenance fees
• Non Executed Match Report 
  
  • Naming Convention: <Participant Code>NonExecutedMatches_YYYYMMDD.csv
  • Frequency: Weekly; File is made available each Sunday
  • Category: Performance Improvement
  • Content: Allows firms to prioritize their non-executed agreements based on number of outstanding contracts in Atlantis that could become matched and/or become Settled as a result of executing these agreements
  • Suggested Use: Prioritization of which Docs agreements need to be executed based on outstanding brokerage
  • More information regarding how to read this report can be found here
• End of Cycle Banking Report
  • Naming Convention: <Participant Code>_FINAL_Banking_<Settlement Cycle YYYY>_YYYYMMDD.xlsx
  • Frequency: Monthly – Settlement Cycle Close
  • Category: Banking
  • Content: Report of payable/receivable settlement amounts broken out by counterparty and currency
  • Suggested Use: Provides firms with comprehensive view of what they will pay and be paid for recently closed settlement cycle

• Counterparty Rules Report

  • Naming Convention: <Participant Code>_LdebCounterpartyRulesReport_YYYYMMDD.csv
  • Frequency: Weekly; File is made available each Sunday
  • Category: OPB/ TPP and Translation Rules
  • Content: Summarized details of fee counts, quantity and translation rules where the counterparty on a trade has been affected by a translation rule and moved to a new participant. Report created for each participant code will only populate details if/when the participant’s counterparty on the trade(s) has been affected by a translation rule.
  • Suggested Use: Identify trade(s) where your counterparty has changed due to a translation rule and identify the trade facts (firm codes, accounts, etc) used for the translation rules on the trade(s).