Highlights of the Rule 4530 Application
1. Customer Complaints
The minimum fields required to file a Complaint are:
- Contact Name and Contact Phone Number
- Complaint Number
- Product Code
- Problem Code
- Allegation Activity Period
- Complaint Date
- Branch ID
- Customer Account Number
- Customer Last Name
- Disputed Amount / Disputed Amount Indicator
- Security Symbol
If the "Related To Rep" box is checked, the following additional fields are required:
- Representative CRD number (FINRA no longer collects Social Security Number)
- Representative Supervisor Last Name (* - this field is only required when processing online through the Web site. It is N/A for batch data.)
- Representative Supervisor First Name (* - this field is only required when processing online through the Web site. It is N/A for batch data.)
2. Events
The minimum fields required for a Event filing are:
- Contact Name and Contact Phone Number
- Disclosure Number
- Disclosure Event Code
- Allegation Activity Period
- Discovery Date
- At least on "Related To" box must be checked
- Branch ID
- Details for Disclosure Event
If the "Related to Rep" box is checked, the Rep information must be entered (see above in formation in Complaints section).
If Event 4530(a)(1)(B) - Customer Complaint Involving Certain Allegations is selected, the following additional fields are required:
- Customer Account Number
- Customer Last Name
- Security Info (symbol and/or name)
- Product Code
- Disputed Amount / Disputed Amount Indicator
If Event 4530(a)(1)(G) Civil Litigation; Arbitration Matters; or Certain Claims for Damages is selected, the following additional fields are required:
- Case Disposition (should be documented in the Details for Disclosure Event field)
- Other Party Name
If Event 4530(a)(1)(H) Statutory Disqualification is selected, the following additional fields are required:
- Relation to Member
- Party Last Name
- Party First Name
- Party Company Name
- Explanation
If Event 4530(a)(2) Disciplinary Action Taken by a Firm Against an Associated Person is selected, the following additional fields are required:
- Disciplinary Action Code
3. File Upload Method
Complaints:
In order to import a filing containing one or more complaints the file must adhere to the following XML format:
| Tag Name | Max Length | Format | Required / Optional | Notes |
| <filings-3070> | R | Container for filings | ||
| <complaint> | R | Container for complaint | ||
| <id> | 30 | A/N | R | Member Firm's unique ID for the Complaint |
| <date> | 10 | yyyy/mm/dd | R | Date complaint was received |
| <firm-id> | 8 | number | R | Firm's CRD # |
| <branch-id> | 10 | A/N | R | Use the assigned CRD branch code, or chose "HOME" if complaint is related to Home Office |
| <branch-zip> | 5 | number | O | Branch ZIP Code |
| <contact> | R | Container for contact info | ||
| <phone-number> | 20 | A/N | R | Contact's phone number |
| <first-name> | 30 | A/N | R | First Name |
| <last-name> | 30 | A/N | R | Last Name |
| <related-to> | R | Container for related-to information. You must select at least one option. | ||
| <other> | 1 | number | O | If complaint is related to Other, Use the value '1'. |
| <rep> | 1 | number | O | If complaint is related to Rep, Use the value '1'. |
| <firm> | 1 | number | O | If complaint is related to Firm, Use the value '1'. |
| <affiliate> | 1 | number | O | If complaint is related to Affiliate, Use the value '1'. |
| <product> | 2 | number | R | Product Code |
| <problem> | 2 | number | R | Problem Code |
| <customer> | R | Container for customer info | ||
| <account-number> | 50 | A/N | O | Customer's account number |
| <first-name> | 30 | A/N | O | First Name |
| <last-name> | 255 | A/N | R | Last Name |
| <activity-date> | 10 | yyyy/mm/dd | R | First date of Allegation Activity. The Activity From date must be equal or prior to the filing submission date. The system will allow zeros in the month or day fields for those instances where all such precise dates are not known (for example, when the specific day of the month is not known, but the month and year is known, you may enter "yyyy/mm/00"). |
| <activity-date2> | 10 | yyyy/mm/dd | R | Last date of Allegation Activity. Must be equal or prior to the filing submission date and equal or subsequent to the Activity From <activity-date> field entry. The system will allow zeros in the month or day fields for those instances where all such precise dates are not known (for example, when the specific day of the month is not known, but the month and year is known, you may enter "yyyy/mm/00"). If the activity is alleged or known to be ongoing, you should provide an explanation in the <comment> field. |
| <transaction> | R | Container for transaction info | ||
| <amount> | 12 | number | O | Amount of the transaction |
| <disputed-amount> | O | Container for the Disputed Amount Information. NOTE: Required for Sales Practice complaints. | ||
| <dsptd-amt-flag> | 1 | number | O | Use 0 - exact amount is entered in <dsptd-amt> Use 1 - <dsptd-amt> is estimated to be $5,000 or more / cannot determine Use 2 - <dsptd-amt> is estimated to be under $5,000 |
| <dsptd-amt> | 12 | number | O | Amount in dispute (Required if <dsptd-amt-flag> contains a zero, otherwise not allowed) |
| <securities> | R | Container for securities information | ||
| <security> | R | Container for each security. Must supply at least one security entry. Can supply up to three securities. Use only one of the following two fields for each security being reported. | ||
| <symbol> | 14 | alpha | O | Enter a known symbol. Alphabetic characters and periods (.) are allowed. Do not use in conjunction with the <iss-descrpt> field. |
| <iss-descrpt> | 255 | A/N | O | Use this to provide the Security Description (or NOT APPLICABLE if not security related) if the issue symbol is not known. |
| <investigator> | O | Container for investigator name | ||
| <first-name> | 30 | alpha | O | First Name |
| <last-name> | 30 | alpha | O | Last Name |
| <respnse-date> | 10 | yyyy/mm/dd | O | Date that your firm responded to this complaint. |
| <representative> | O | Container for rep information. NOTE: If <rep> value is "1", then these values are Required. | ||
| <id> | 12 | number | O | Rep CRD ID. If <rep> value is "1", then this value is required. |
| <location> | O | |||
| <city> | 15 | alpha | O | |
| <state> | 2 | alpha | O | |
| <zip> | 5 | number | O | |
| <supervisor> | O | Container for Rep's supervisor. If <rep> value is "1", then this value is required. | ||
| <first-name> | 30 | alpha | O | First Name. If <rep> value is "1", then this value is required. |
| <last-name> | 30 | alpha | O | Last Name. If <rep> value is "1", then this value is required. |
| <employed> | 1 | number | O | |
| <comment> | 255 | text | O | Freeform comment |
Disclosures
The old event codes 01 through 10 pursuant to NASD Rule 3070 or NYSE Rule 351 will continue to be available for amending batch events that were reported prior to July 1, 2011.
Firms must use new event codes for batch reporting of Rule 4530(a) and 4530(b) events on or after July 1, 2011. The new codes are 11 through 20 as follows:
| Event Code | Paragraph | Description |
| 11 | (a)(1)(A) | External Finding |
| 12 | (a)(1)(B) | Customer Complaint Involving Certain Allegations |
| 13 | (a)(1)(C) | Named in a Regulatory Proceeding |
| 14 | (a)(1)(D) | Subject to Other Regulatory Actions |
| 15 | (a)(1)(E) | Criminal Actions Involving Felonies and Certain Misdemeanors |
| 16 | (a)(1)(F) | Associated with a Financial Entity Subject to Certain Actions |
| 17 | (a)(1)(G) | Civil Litigation; Arbitration Matters; or Certain Claims for Damages |
| 18 | (a)(1)(H) | Statutory Disqualification |
| 19 | (a)(2) | Disciplinary Action Taken by a Firm Against an Associated Person |
| 20 | (b) | Internal Conclusion |
In order to import a filing containing one or more Events the file must adhere to the following XML file format:
| Tag Name | Max Length | Format | Required / Optional | Notes |
| <filings-3070> | R | Container for filings | ||
| <disclosure> | R | Container for Disclosure | ||
| <id> | 30 | A/N | R | Member Firm's unique ID for this Disclosure |
| <date> | 10 | yyyy/mm/dd | R | Date disclosure was discovered |
| <firm-id> | 8 | number | R | Firm's CRD # |
| <branch-id> | 10 | A/N | R | Use the assigned CRD branch code, or chose "HOME" if complaint is related to Home Office |
| <contact> | R | Container for contact info | ||
| <phone-number> | 20 | A/N | R | Contact's phone number |
| <first-name> | 30 | A/N | R | First Name |
| <last-name> | 30 | A/N | R | Last Name |
| <related-to> | R | Container for related-to information. You must select at least one option. | ||
| <other> | 1 | number | O | If complaint is related to Other, Use the value '1'. |
| <rep> | 1 | number | O | If complaint is related to Rep, Use the value '1'. |
| <firm> | 1 | number | O | If complaint is related to Firm, Use the value '1'. |
| <affiliate> | 1 | number | O | If complaint is related to Affiliate, Use the value '1'. |
| <event> | 2 | number | R | Event Code |
| <product> | 2 | number | O | Product Code. Required if Event Code = 2 or 12. |
| <customer> | R | Container for customer info | ||
| <account-number> | 50 | A/N | O | Customer's account number |
| <first-name> | 30 | A/N | O | First Name |
| <last-name> | 255 | A/N | R | Last Name |
| <activity-date> | 10 | yyyy/mm/dd | R | First date of Allegation Activity. Must be equal or prior to the <date> field entry. The system will allow zeros in the month or day fields for those instances where all such precise dates are not known (for example, when the specific day of the month is not know, but the month and year is known, you may enter "yyyy/mm/00"). |
| <activity-date2> | 10 | yyyy/mm/dd | R | Last date of Allegation Activity. Must be equal or prior to the filing submission date and equal or subsequent to the Activity From <activity-date> field entry. The system will allow zeros in the month or day fields for those instances where all such precise dates are not known (for example, when the specific day of the month is not know, but the month and year is known, you may enter "yyyy/mm/00"). If the activity is alleged or known to be ongoing, you should provide an explanation in the <comment> field. |
| <transaction> | O | Container for transaction information. Required if Event Code = 2 or 12. | ||
| <amount> | 12 | number | O | Amount of the transaction in whole dollars. Use zero if not applicable. |
| <disputed-amount> | O | Container for the Disputed Amount Information. NOTE: Required if Event Code = 2 or 12. | ||
| <dsptd-amt-flag> | 1 | number | O | Required if Event Code = 2 or 12. Use 0 - exact amount is entered in < dsptd-amt > Use 1 - <disputed-amount> is estimated to be $5,000 or more / cannot determine Use 2 - <disputed-amount> is estimated to be under $5,000 |
| <dsptd-amt> | 12 | number | O | Amount in dispute (Required if <dsptd-amt-flag> contains a zero, otherwise not allowed) |
| <securities> | O | Container for securities Information. Required if Event Code = 2 or 12. | ||
| <security> | O | Container for each security. Must supply at least one security entry. Can supply up to three securities. Use only one of the following two fields for each security being reported. | ||
| <symbol> | 14 | alpha | O | Enter a known symbol. Alphabetic characters and periods (.) are allowed. Do not use in conjunction with the <iss-descrpt> field. |
| <iss-descrpt> | 255 | A/N | O | Use this to provide the Security Description (or NOT APPLICABLE if not security related) if the issue symbol is not known. |
| <investigator> | O | Container for investigator name | ||
| <first-name> | 30 | alpha | O | First Name |
| <last-name> | 30 | alpha | O | Last Name |
| <respnse-date> | 10 | yyyy/mm/dd | O | Date that your firm responded to this complaint. |
| <representative> | O | Container for rep information. NOTE: If <rep> value is "1", then these values are Required. | ||
| <id> | 12 | number | O | Rep CRD ID. If <rep> value is "1", then this value is required. |
| <location> | O | |||
| <city> | 15 | alpha | O | |
| <state> | 2 | alpha | O | |
| <zip> | 5 | number | O | |
| <supervisor> | O | Container for Rep's supervisor. If <rep> value is "1", then this value is required. | ||
| <first-name> | 30 | alpha | O | First Name. If <rep> value is "1", then this value is required. |
| <last-name> | 30 | alpha | O | Last Name. If <rep> value is "1", then this value is required. |
| <employed> | 1 | number | O | |
| <disciplinary-action> | 1 | alpha | O | Required if Event Code = 10 or 19. Use W = Withholding of Commissions, T = Termination, F = Imposition of Fines, S = Suspension |
| <comment> | 255 | text | O | Freeform comment |
| <statutory-disqualification> | O | Container for SD information. Required if Event Code = 9 or 18. | ||
| <party-first-name> | 30 | alpha | O | First Name. Required if Event Code = 9 or 18. |
| <party-last-name> | 30 | alpha | O | Last Name. Required if Event Code = 9 or 18. |
| <party-company> | 10 | alpha | O | Required if Event Code = 9 or 18. |
| <relationship> | 1 | alpha | O | Required if Event Code = 9 or 18. Use A = Affiliate, F = Firm, O = Other, R = Representative |
| <explanation> | 50 | alpha | O | Required if Event Code = 9 or 18. |
| <case-disposition> | 1 | alpha | O | Required if Event Code = 7 or 17. Use A = Award, J = Judgment, S = Settlement |
Hints about XML: Like HTML, every open tag must have a close tag. While indention is not necessary, it does allow potential debugging of a faulty script easier.
Sample XML Formatted Complaints Batch File
View sample file (XML 3KB)
All tags must be listed even if empty. Leading and trailing spaces, tabs, and carriage returns are dropped. Filings that do not conform to this format will not load.
The <id> field in both complaints and disclosures is required and must be unique for the complaint or disclosure. The field may be used to reload or amend a filing. Upon reading the field the system will attempt to match this number and replace (if in draft) or amend (if submitted) based on the value of this field. ID numbers may not be reused each month. It is very important that this number is unique across all submissions. (If the number 7 was used in July 98 and now appears again in the current file, the system will assume that the new filing is an amendment of the 98 filing). Numbering may begin with 1 with the start of the use of this format.
When a filing is loaded to the system via batch it is validated and if it passes it is immediately submitted. Any filing within this batch that does not pass validation will be placed in the "Draft filings" area. Users have to correct the errors and re-submit it.
4. Filing Maintenance
Users are provided with capability to:
- Edit filings that are in "Draft" status
- Amend filings that are in "Submitted" status
- Delete "Draft" or "Submitted" filings. Users should enter comments when deleting submitted filings.