Reporting large virtual currency transactions to FINTRAC

June 2021

This guidance comes into effect on June 1, 2021.

Please see the Notice on the assessment of new regulatory obligations coming into force on June 1, 2021 for information on submitting Large Virtual Currency Transactions Reports between June 1, 2021 and December 1, 2021. The Notice provides instructions for reporting entities that are not able to meet the reporting obligation as described in Section 3 of this page. 

Large virtual currency transaction reporting requirements under the Proceeds of Crime (Money laundering) and Terrorist Financing Act (PCMLFTA) and associated Regulations are applicable to all reporting entity (RE) sectors. If you are a person who is an RE, and you are an employee of an RE, your employer is responsible for meeting the Large Virtual Currency Transaction Reporting requirements associated to your activities as an employee.Footnote1

Similarly, if you are an RE, and you are an agent of, or you are authorized to act on behalf of another RE, it is the other RE's responsibility to meet the Large Virtual Currency Transaction Report requirements (LVCTR) associated to the activities you conduct on its behalf. This does not apply if you are a life insurance broker or agent (unless you are an employee as explained above).Footnote2

A service provider can submit and correct LVCTRs on your behalf. However, as the RE, you are ultimately responsible for meeting the requirements under the PCMLTFA and associated regulations, even if a service provider is reporting on your behalf. This legal responsibility cannot be delegated.

This guidance outlines the reporting obligations for submitting an LVCTR and answers the following questions:

  1. What is virtual currency?
  2. When must I report large virtual currency transactions?
  3. How do I submit LVCTRs?
  4. How do I complete LVCTRs?
  5. Do I have other requirements associated to large virtual currency transactions?
  6. What are the exceptions to reporting large virtual currency transactions?

You will also find field instructions to complete an LVCTR in Annex 1. In addition, FINTRAC has published the following LVCTR-related information:

**Note: The technical specifications documents for the LVCTR are the JSON-LD and the JSON schema file. These can be accessed through the FINTRAC web reporting system (FWR). If you do not yet have access to FWR and would like these documents, please contact us at guidelines-lignesdirectrices@fintrac-canafe.gc.ca.

Large virtual currency transactions have associated record keeping and client identification requirements. For more information, please see your sector's record keeping and client identification requirements in FINTRAC's Record keeping requirements and When to verify the identity of persons and entities guidance.

If you are unsure about your large virtual currency transaction reporting obligations, please contact FINTRAC by email at guidelines-lignesdirectrices@fintrac-canafe.gc.ca.

**Note: Throughout this guidance, references to dollar amounts (such as $10,000) are in Canadian dollars (CAD) unless otherwise specified.

1. What is virtual currency?

Virtual currency (VC) is a digital representation of value, or the private key of a cryptographic system that enables access to a digital representation of value, that can be used for payment or investment purposes. It is not a fiat currency but it can be readily exchanged for funds, or another VC that can be exchanged for funds.Footnote3

For greater clarity, this definition does not include certain digital currencies, such as those that can only be used within a self-contained virtual environment, or a digital currency that can be redeemed for goods and services, but not easily converted into funds. For example, digital currencies include those used for online gaming, which are not exchangeable for funds or VCs, or those that can only be redeemed for gift cards and loyalty programs.

2. When must large virtual currency transactions be reported?

When you receive VC in an amount equivalent to $10,000 or more in a single transaction, you must submit an LVCTR to FINTRAC.Footnote4

You must also submit an LVCTR to FINTRAC in accordance with the 24-hour rule when you receive two or more amounts of VC, that total $10,000 or more within a consecutive 24-hour window, and you know that the transactions meet one of the following:Footnote5

For more information on reporting in accordance with the 24-hour rule, please see FINTRAC's 24-hour rule guidance.

To determine if a transaction is reportable, you must first determine when you are in receipt of VC, and then determine if the amount of received VC meets the reporting threshold of $10,000. You are in receipt of VC when the transaction can no longer be reversed or cancelled.

As the Bank of Canada does not publish exchange rates for VC, you must use the rate you establish in the normal course of your business to determine whether you have reached the reporting threshold amount. Your process for establishing an exchange rate must be outlined in the policies and procedures within your Compliance Program.Footnote6

You must submit an LVCTR to FINTRAC within five working days after the day you receive the amount.Footnote7

When you submit an LVCTR to FINTRAC, you must keep a copy of it.Footnote8 For more information on your record keeping obligations see your sector's record keeping guidance.

3. How do I submit LVCTRs?

You must submit LVCTRs to FINTRAC electronically if you have the technical capabilities to do so. If you do not have the technical capabilities to report electronically, you must submit paper reports.Footnote9

Please see the Notice on the assessment of new regulatory obligations in force on June 1, 2021 for more information.

Electronic reporting

You must submit LVCTRs to FINTRAC using the LVCTR Upload found in FWR (formerly F2R). At this time, the option of manual data entry in FWR is not available. Batch reporting is also not available.

If you have not already done so, enroll with FINTRAC to gain access to FWR. Afterwards, please see FINTRAC's LVCTR Upload information page to set up large virtual currency transaction reporting.

In addition to this reporting guidance, you should familiarize yourself with the LVCTR Validation rules and technical documents.

Paper reporting

FINTRAC's LVCTR paper reporting form can be printed from the reporting forms web page, or you can request a form to be faxed or mailed to you by calling FINTRAC at 1-866-346-8722.

There are two ways you can submit an LVCTR form to FINTRAC:

There is no official acknowledgment of receipt when you submit a paper form to FINTRAC.

4. How do I complete LVCTRs?

Multiple transactions under the 24-hour rule

The LVCTR structure allows you to enter the multiple transactions that occur within a 24-hour period into a single report. Additionally, each transaction may have multiple starting and completing actions. Within each starting action you can include multiple conductors, sources of VC and third parties. Within each completing action you can include multiple account holders, beneficiaries and other persons or entities involved in the disposition. Each transaction must contain a location or receipt as well as at least one starting action, one completing action, and one beneficiary.

Review and validation of reports by FINTRAC

There are three types of validation rules used by FINTRAC to validate reports. They are described below.

FINTRAC's validation rules identify possible reporting problems and information gaps but do not cover all scenarios. While FINTRAC conducts a review of report submissions to assess the quality of reports, you should have your own proactive quality assurance practices in place.

LVCTR submission limitations  

Each LVCTR must include at least one transaction and may include up to 99 transactions. If there are more than 99 transactions, you will have to use more than one report for your transactions. You must include the RE report reference number to allow FINTRAC to apply changes to a previously submitted report and to link related reports. The RE report reference number is the unique number you assign each report. If 99 transactions are exceeded in a report, you may include a suffix (for example, -001, -002, etc.) to indicate the report is linked to another report. See below for more information on linking reports.

Every report transaction must include one starting and one completing action and may include up to 50 starting and 50 completing actions per transaction. If a transaction has more than 50 starting or completing actions, you must start a new report to continue reporting the starting or completing actions. You will use the original RE transaction reference number from the transaction in the report with the first 50 starting or completing actions. You must repeat this transaction reference number to allow FINTRAC to identify and link the starting or completing actions across reports for a given transaction.

If you need to link transactions in multiple reports, you can continue counting transactions incrementally with each report. For example, 250 transactions detailed over three (3) reports could be submitted as:

Report 1 (LVCTR999-01) : Transactions 1 to 99;
Report 2 (LVCTR999-02) : Transactions 100 to 198; and
Report 3 (LVCTR999-03) : Transactions 199 to 250.

Making changes to a previously submitted report

You can change a previously submitted report using the LVCTR Upload. You must include the full report you wish to change, and use the modified report with the original report's RE report reference number to allow FINTRAC to link the two reports.

You can delete a previously submitted report in the submitted reports page in FWR.

5. Do I have other requirements associated to large virtual currency transactions?

Third party determination

For more information on your requirements for determining whether a person is acting on behalf of a third party for the receipt of a large VC transaction, see the guidance on Third party determination requirements.

Suspicious transactions

In addition to reporting large VC transactions, you may also be required to submit Suspicious Transaction Reports (STR) when you have reasonable grounds to suspect that a transaction is related to the commission or the attempted commission of a money laundering or terrorist activity financing (ML/TF) offence. Therefore, you may be required to submit an LVCTR and an STR for the same transaction. For more information, see the following guidance:

Ministerial directives

You must consider all requirements issued under a Ministerial directive along with your large VC transaction reporting requirements. For more information, please see FINTRAC's guidance on Ministerial directives and transaction restrictions.

Compliance program

It is your responsibility to ensure that the information you provide in the LVCTR is complete and accurate. Your compliance program's policies and procedures must include details on the processes you will use to calculate exchange rates, aggregate transactions, determine if the receipt of VC is reportable and submit LVCTRs to FINTRAC. It is possible for your organization to have an automated or triggering system in place to help detect when the threshold amount is reached for reporting; however, the transaction(s) should still be assessed by a person to ensure that an LVCTR must be submitted. You must also establish a compliance program that includes training on the grounds to suspect money laundering and terrorist financing activities in relation to your business. For more information, see Compliance program requirements.

Voluntary self-declaration of non-compliance

It is strongly encouraged that instances of non-compliance be reported to FINTRAC in writing through a voluntary self-declaration of non-compliance. For more information, see Voluntary self-declaration of non-compliance.

6. What are the exceptions to reporting large virtual currency transactions?

The following exceptions refer to the initial receipt of VC, but any further transaction or activity may have reporting obligations, in addition to other obligations.

You are not required to submit an LVCTR if you receive two or more amounts in VC that are each individually equivalent to less than $10,000, but together total $10,000 or more within 24 consecutive hours, when you know the amounts are for a beneficiary that is:Footnote10

You do not need to submit an LVCTR for the receipt of VC in an amount equivalent to $10,000 or more in a single transaction if the VC is received as:Footnote11

Annex 1: Field instructions to complete a Large Virtual Currency Transaction Report

The following instructions provide REs with additional information on how to complete the report fields when submitting an LVCTR. This Annex details what is required in certain fields. Certain fields are dependent on the completion of other fields.

Standardized report instructions

This section includes standardized instructions for reporting. For more information on how to complete LVCTRs, see the Field Instructions below.

All fields are categorized as either mandatory, mandatory for processing, mandatory if applicable, or reasonable measures.

  1. Mandatory:
    • Mandatory fields must be completed.
    • These fields will be indicated with an asterisk (*).
    • Because an LVCTR can include multiple transactions conducted within 24 consecutive hours that total $10,000 or more, the information for some mandatory fields may not have been obtained at the time of the transaction. In this case, the fields become "reasonable measures" fields, and the instructions below must be applied.Footnote12
  2. Mandatory for processing: 
    • Mandatory for processing fields must be completed.
    • These fields will be indicated with a double dagger (‡).
  3. Mandatory if applicable:
    • Mandatory if applicable fields must be completed if they are applicable to you or the transaction being reported.
    • These fields will be indicated with a dagger (†).
  4. Reasonable measures:Footnote13
    • You must take reasonable measures to obtain the information for all non-mandatory fields in the report, if they are applicable.
    • Reasonable measures are the steps that you must take, as outlined in your policies and procedures, to obtain the information which can include asking the person or entity involved in the transaction for the information. If the information is obtained, it must be reported. It also means that you must provide the information if it is contained within your systems or records.

**Note: When a field is not applicable, do not enter "Not applicable", "N/A" or "n/a" or substitute any other abbreviations, special characters ("x", "-' or "*") or words ("unknown") in these fields. Fields that are not applicable are to be left blank.

Failure to provide applicable reporting information will result in non-compliance and may lead to criminal or administrative penalties. To learn more about potential enforcement actions, please see Penalties for non-compliance.

In this Annex, not all the report fields are defined. Defined fields that are used in multiple sections of the report are only defined once. Please search through the Annex to find out whether a field has been defined.

General information

*Reporting entity number

You must enroll in FINTRAC's electronic reporting system to submit reports electronically. Provide the seven-digit identifier number assigned to you by FINTRAC at enrolment.

‡Reporting entity report reference number  

A unique report reference number assigned by you or by the individual or institution submitting the report on your behalf.

Which one of the following types of reporting entities best describes you?

*Activity sector

Enter your business activity sector. If you are involved in more than one type of business activity, indicate the one applicable to the transaction being reported. If there is more than one activity for one or more transactions on the report, select only one box to indicate your principal type of activity.

Whom can FINTRAC contact about this report?

*Contact number

A unique identifier number that is automatically assigned when a new user is created in FWR. Provide the identifier number of the person for whom FINTRAC can contact about the report.

Report information

Indicate whether the report is related to one or multiple transactions that occurred within a consecutive 24-hour period. When you provide a date and time, you must include the time zone. See below for formatting.

24-hour aggregation type

Indicate the type of aggregation (conductor, beneficiary, on behalf of, or not applicable) used when multiple transactions occur within a consecutive 24-hour period. If the report is for one transaction only, or for a Ministerial directive, aggregating transactions does not apply and 'Not applicable (N/A)' should be selected.

†24-hour period start date/time

Provide the start date and time of the 24-hour period. You must include the time zone (that is, UTC offset) in the 24-hour period start time fields. The start time must be entered in the following format: HH:MM:SS±ZZ:ZZ. For example, 1:25:06 PM in Ottawa, ON would be reported as 13:25:06-05:00.

†24-hour period end date/time

Provide the end date and time of the 24-hour period. If your 24-hour period starts at 8:00 AM, it would end at 7:59 AM the following day. You must include the time zone (that is, UTC offset) in the 24-hour period start end time fields. See the above field for formatting.

Ministerial directive

If the report is being submitted under a Ministerial directive, indicate the directive the report relates to from the table (you must also select 'Not applicable (N/A)' in the '24-hour aggregation type' field). Leave this field blank if the transaction(s) are not part of a Ministerial directive.

Transaction information

Information about the transaction

Provide information about each transaction being reported.

*Date/time virtual currency was received

The date and time that the virtual currency was received for the transaction(s) being reported. It must not be earlier than June 1, 2021.

If a transaction spans multiple time zones, select the time zone based on the location of the receipt of a large amount of virtual currency. You must determine the appropriate time zone for each transaction. For online transactions, you can centralize your reporting time zone (for example, to your main location or headquarters) even if you have multiple locations.

*Method of transaction

†If "Other", please specify

‡Threshold indicator

Indicate whether the value of the virtual currency received for the transaction was above or below $10,000 at the time of receipt. Select "above threshold" if the transaction is equal to $10,000 or more.

*Transaction identifier

This is a unique identifier; it is commonly represented by a hash consisting of mixed numerical and alphabetical characters.

‡Reporting entity transaction reference number

This is a unique reference number assigned by you or your organization to the transaction.

Purpose of transaction

This is the reason for the transaction. For example, the received virtual currency may be for the purchase of a car through a private sale. The information in this field may be similar to the "details of disposition" field.

Information about where the virtual currency was received

Provide information about the physical location where the virtual currency was received. For example, if the virtual currency was received at a virtual currency ATM, provide the reporting entity location number of that ATM. If no physical location is applicable (for instance the transaction was conducted online), provide the location number of your main location, such as a head office or headquarters.

*Reporting entity location number

Starting action

Starting action details

Provide information about how the transaction was started, including the type and amount of virtual currency, where it came from, who the conductor of the transaction was and on any third party involved (if applicable).

*Amount

*Virtual currency type

Select the virtual currency type used in the transaction. If the virtual currency type is not in the list provided, you must select "Other" and provide the name of the virtual currency.

†If "Other", please specify

*Exchange rate used for the transaction

Provide the rate of exchange to Canadian dollars that you used for the transaction.

*Sending virtual currency address

Provide the sending virtual currency address(es) for every starting action for the transaction. The sending virtual currency address is made up of a number of alpha-numeric characters, its length is determined by the type of VC used.

How was the virtual currency obtained?

Explain how the conductor initially obtained the virtual currency used for the transaction if you obtained this information in the ordinary course of business. For example, the conductor originally obtained the virtual currency used in the transaction from the private sale of a car. This information must be reported "if obtained in the ordinary course of business". This means the information must be reported if you obtained it for any reason related to the services you provide to clients.

‡Was information about the source of virtual currency obtained?

This field is a "Yes/No" question. If you have the name of any person or entity that is the source of the VC involved in the transaction, their account number or policy number, or an identifying number if there is no account number or policy number, select "yes". Otherwise, select "no" to indicate you have no information.

Source of virtual currency

If you have information on any source of the VC involved in the transaction, you must report it. This includes their name and the following:

  • account number;
  • policy number; or
  • identifying number, if there is no account or policy number.

If there are multiple sources, you must provide information for each source.

This information must be reported "if obtained in the ordinary course of business". This means the information must be reported if you obtained it for any reason related to the services you provide to clients.

Person details

†Surname

†Given name

Other/initial

Account number

Policy number

Identifying number

Entity details

†Name of entity

Account number

Policy number

Identifying number

Conductor indicator

‡Have you obtained any conductor information related to this transaction?

If the conductor is a client or if you have information about a conductor that is not your client, you must answer "Yes". "No" must only be selected if, despite taking reasonable measures to do so, you were not able to obtain any information on the conductor that was not your client.

Information about the person conducting the transaction

Provide all the information you have on one, or multiple persons specified as the conductors of the transaction.

Information about the person conducting the transaction

†Is the conductor a client of the reporting entity?

†Surname

†Given name

Other/Initial

Alias

The name a person uses or by which they are known, other than the name provided under surname or given name.

Username

A username is how a person or an entity refers to themselves online. 

†Client number

A unique identifying number assigned by the RE to the person or entity conducting the transaction.

Apt/Room/Suite/Unit number

House/Building number

†Street address

†City

District

†Country

†Province or state

Sub-province and/or sub-locality

Postal or zip code

Unstructured address details

If the address of the person or entity conducting the transaction is structured in a way that it can be parsed out, you must enter the information in the structured address fields. If you use the structured address fields, you cannot use the unstructured address fields to provide additional information.

Structured address details: Provide the street address, city, country, province or state, and postal code. For example, if a person lives at:

  • #12-455 Main St., Ottawa, ON, Canada A1B 2C3

The apartment number is 12, the building or house number is 455, the street name is Main St., the city is Ottawa, the province is Ontario, the country is Canada, and the postal code is A1B 2C3.

If you are unable to parse the address information into the structured address fields, you can enter the address details in this field. You should only use the unstructured address field when it is not possible to separate the address information. If possible, please provide unstructured address information in the following format:

  • street address/city/province or state/postal code or zip code

Enter information about the country in the "Country" field.

Telephone number

Extension

Email address

†Date of birth

Country of residence

Enter the primary country of residence for the person, it can be the same or different from the country entered in the address section.

†Occupation

When entering occupation information, you should be as descriptive as possible. If the person is a manager, provide the area of management, such as "hotel reservations manager" or "retail clothing store manager". If the person is a consultant, provide the type of consulting, such as "IT consultant" or "forestry consultant". If the person is a professional, provide the type of profession, such as "petroleum engineer" or "family physician". If the person is a labourer, provide the type of labour performed, such as "road construction worker" or "landscape labourer". If the person is not working, you should still be as descriptive as possible, and indicate "student", "unemployed" or "retired" etc.

Name of employer

Enter the name of the person's employer. Do not provide the name of a supervisor or manager – this field is meant to capture the name of the business that employs the person. If the person has multiple employers, you only need to provide one.  

Identification document or information of the person and associated number

†Identifier type

†If "Other", please specify

†Number associated with identifier type

This is the number indicated on the identifier type. For example, on a driver's licence, the licence number is the identification number. If a social insurance number is used, the number must not be submitted to FINTRAC.

†Jurisdiction of issue (country)

Provide the country, province, or state that issued the documentation used to identify the person or entity who conducted the transaction, or the third party or beneficiary. If the country of issue is Canada, Mexico or the United States (US), you must provide the province or state for the jurisdiction of issue. If the documentation was issued by a different country, enter the country as the jurisdiction of issue. If you obtained information on the province or state, you must provide it.

†Jurisdiction of issue (province or state)

See above for information.

Information about conducting the transaction online

Information for this section is required only when the transaction occurs online. The following fields apply:

  • Type of device used – select which device was used to conduct the transaction online;
  • If "Other", please specify – if the device used was not in the table, you must indicate the type of device;
  • Device identifier number – see below; and
  • Internet protocol address

Type of device used

†If "Other", please specify

Device identifier number

The device identifier number is a number assigned to the device, such as a Media Access Control (MAC) address or International Mobile Equipment Identity (IMEI) number.

Internet protocol (IP) address

Date/time of online session in which request was made

This is the date and time the conductor accessed the online environment where the transaction was requested.

On behalf of indicator

Was this transaction conducted on behalf of another person or entity?

Information about the entity conducting the transaction

Provide all the information you have on one, or multiple entities specified as the conductors of the transaction.

†Is the conductor a client of the reporting entity?

†Name of entity

Username

†Client number

Apt/Room/Suite/Unit number

House/Building number

†Street address

†City

District

†Country

†Province or state

Sub-province and/or sub-locality

Postal or zip code

Unstructured address details

Telephone number

Extension

†Nature of entity's principal business

You should be as descriptive as possible when entering the entity's principal business. If the entity's principal business area is "sales", provide the type of sales, such as "pharmaceutical sales" or "retail sales".

†Is the entity registered or incorporated?

†Registration or incorporation number

Provide the registration or incorporation number of the entity conducting the transaction. You must provide the jurisdiction of issue if you provide a registration or incorporation number.

†Jurisdiction of issue (country)

†Jurisdiction of issue (province or state)

Identification document or information of the entity and associated number

†Identifier type

†If "Other", please specify

†Number associated with identifier type

†Jurisdiction of issue (country)

†Jurisdiction of issue (province or state)

Person(s) authorized to bind the entity or act with respect to the account (max. 3)

If the conductor is an entity, you must provide the information for up to three persons who are authorized to bind the entity or act with respect to the account.

†Surname

†Given name

Other/Initial

Information about conducting the transaction online

Type of device used

†If "Other", please specify

Device identifier number

Internet protocol address

Date/time of online session in which request was made

On behalf of indicator

†Was this transaction conducted on behalf of another person or entity?

Information about the person on whose behalf the transaction was conducted

If the transaction was conducted on behalf of another person or entity, you must include the relevant information.

†Surname

†Given name

Other/Initial

Alias

Client number

Apt/Room/Suite/Unit number

House/Building number

†Street address

†City

District

†Country

†Province or state

Sub-province and/or sub-locality

Postal or zip code

Unstructured address details

Telephone number

Extension

Email address

Date of birth

Country of residence

Occupation

Name of employer

Identification document or information of the person and associated number

Identifier type

†If "Other", please specify

Number associated with identifier type

Jurisdiction of issue (country)

Jurisdiction of issue (province or state)

Relationship of the person or entity conducting the transaction to the person named above

†Relationship

The relationship between the "on behalf of" party with the person or entity that conducted the transaction. The "on behalf of" party is understood to be the person or entity who gives the instructions for the transaction.

†If "Other", please specify

Information about the entity on whose behalf the transaction was conducted

†Name of entity

Client number

Apt/Room/Suite/Unit number

House/Building number

†Street address

†City

District

†Country

†Province or state

Sub-province and/or sub-locality

Postal or zip code

Unstructured address details

Telephone number

Extension

Email address

Nature of entity's principal business

Is the entity registered or incorporated?

Registration or incorporation number

Jurisdiction of issue (country)

Jurisdiction of issue (province or state)

Identification document or information of the entity and associated number

Identifier type

†If "Other", please specify

Number associated with identifier type

Jurisdiction of issue (country)

Jurisdiction of issue (province or state)

Person authorized to bind the entity or act with respect to the account (max. 3)

Surname

Given name

Other/Initial

Relationship of the person or entity conducting the transaction to the entity named above

†Relationship

†If "Other", please specify

Completing action

Provide information about how the transaction was completed, including the details of disposition, the amount, information on any other person or entity that may have been involved in the completing action and, on any person or entity that was the beneficiary of the transaction.

*Details of disposition

This describes what happened to the virtual currency involved in the transaction. For example, if the disposition was an amount added to a VC wallet at a money services business you would select "added to a virtual currency wallet" from the table. If the values provided do not adequately describe the disposition of the transaction, indicate "Other" and provide details in that field.

†If "Other", please specify

†Amount

†Virtual currency type

†If "Other", please specify

†Receiving virtual currency address

†Currency

†Value in Canadian dollars

Provide the Canadian dollar value of the disposition if it is not virtual currency. For example, the VC was used to purchase jewellery.

†Reference number

If the transaction involved a reference number that is used as an equivalent to an account number, provide it, as well any other number connected to the reference number. Do not include account information in these fields.

†Other number related to reference number

†Financial institution number

†Branch number

†Account number

†Account type

†If "Other", please specify

†Account currency

†Account virtual currency type

†If "Other", please specify

†Date account opened

‡Was there any other person or entity involved in the completing action?

Name of person account holder

†Surname

†Given name

Other/Initial

†Username

Name of entity account holder

†Name of entity

†Username

Information about the person involved in the completing action

If you have information about other persons involved in the completing action, you must include it. These persons or entities cannot be the conductor, on behalf of party, or beneficiary to the transaction.

†Surname

†Given name

Other/Initial

Account number

Policy number

Identifying number

Information about the entity involved in the completing action

If you have information about other entities involved in the completing action, you must include it. These persons or entities cannot be the conductor, on behalf of party, or beneficiary to the transaction.

†Name of entity

Account number

Policy number

Identifying number

Beneficiary indicator

‡Was there a beneficiary for this completing action?

There must always be a minimum of one beneficiary per transaction.

Person beneficiary

†Surname

†Given name

Other/Initial

Alias

Username

Client number

Apt/Room/Suite/Unit number

House/Building number

†Street address

†City

District

†Country

†Province or state

Sub-province and/or sub-locality

Postal or zip code

Unstructured address details

Telephone number

Extension

Email address

Date of birth

Country of residence

Occupation

Name of employer

Identification document or information of the person and associated number

†Identifier type

†If "Other", please specify

†Number associated with identifier type

†Jurisdiction of issue (country)

†Jurisdiction of issue (province or state)

Entity beneficiary

†Name of entity

Username

Client number

Apt/Room/Suite/Unit number

House/Building number

†Street address

†City

District

†Country

†Province or state

Sub-province and/or sub-locality

Postal or zip code

Unstructured address details

Telephone number

Extension

Email address

Nature of entity's principal business

†Is the entity registered or incorporated?

†Registration or incorporation number

†Jurisdiction of issue (country)

†Jurisdiction of issue (province or state)

Identification document or information of the entity and associated number

†Identifier type

†If "Other", please specify

†Number associated with identifier type

†Jurisdiction of issue (country)

†Jurisdiction of issue (province or state)

Person authorized to bind the entity or act with respect to the account

†Surname

†Given name

Other/Initial

Date Modified: