Prompt Title: AML SQL Data Structure

Based on the provided sample report in XML format, we can design a corresponding data structure for an AML (Anti-Money Laundering) SQL database. Here's an example of how the data structure can be organized:

1. Table: Report

   • Columns: rentity_id, submission_code, report_code, submission_date, currency_code_local

2. Table: Reporting_Person

   • Columns: rentity_id (foreign key), gender, first_name, last_name, birthdate, birth_place, id_number, nationality1, residence, occupation

3. Table: Reporting_Person_Phones

   • Columns: rentity_id (foreign key), tph_contact_type, tph_communication_type, tph_country_prefix, tph_number, tph_extension

4. Table: Reporting_Person_Addresses

   • Columns: rentity_id (foreign key), address_type, address, city, country_code, state

5. Table: Transaction

   • Columns: rentity_id (foreign key), transactionnumber, internal_ref_number, transaction_location, transaction_description, date_transaction, teller, authorized, late_deposit, value_date, transmode_code, amount_local

6. Table: From_My_Client

   • Columns: transactionnumber (foreign key), from_funds_code, from_funds_comment

7. Table: From_Account

   • Columns: transactionnumber (foreign key), institution_name, institution_code, non_bank_institution, branch, account, currency_code, account_name, client_number, personal_account_type

8. Table: T_Entity

   • Columns: transactionnumber (foreign key), name, commercial_name, incorporation_legal_form, incorporation_number, business, email, incorporation_state, incorporation_country_code, incorporation_date, comments

9. Table: T_Entity_Phones

   • Columns: transactionnumber (foreign key), tph_contact_type, tph_communication_type, tph_country_prefix, tph_number, tph_extension

10. Table: T_Entity_Addresses

    • Columns: transactionnumber (foreign key), address_type, address, city, country_code

11. Table: Director_ID

    • Columns: transactionnumber (foreign key), gender, title, first_name, last_name, birthdate, birth_place, nationality1, residence, occupation

12. Table: Director_ID_Phones

    • Columns: transactionnumber (foreign key), tph_contact_type, tph_communication_type, tph_country_prefix, tph_number, tph_extension

13. Table: Director_ID_Addresses

    • Columns: transactionnumber (foreign key), address_type, address, city, country_code

14. Table: Identification

    • Columns: transactionnumber (foreign key), type, number, issue_date, expiry_date, issued_by, issue_country

15. Table: Signatory

    • Columns: transactionnumber (foreign key), is_primary, role

16. Table: T_Person

    • Columns: transactionnumber (foreign key), gender, title, first_name, middle_name, last_name, birthdate, birth_place, passport_number, passport_country, id_number, nationality1, residence, occupation

17. Table: T_Person_Phones

    • Columns: transactionnumber (foreign key), tph_contact_type, tph_communication_type, tph_country_prefix, tph_number, tph_extension

18. Table: T_Person_Addresses

    • Columns: transactionnumber (foreign key), address_type, address, city, country_code

19. Table: Source_of_Wealth

    • Columns: transactionnumber (foreign key), source_of_wealth

Please note that this is just a suggested data structure based on the provided sample report. The actual structure may vary depending on your specific requirements and additional information that may be included in