The Form TA-2 Files dataset is the complete EDGAR archive of Form TA-2 and Form TA-2/A annual reports filed by registered transfer agents under Rule 17Ac2-2 promulgated by the SEC under Section 17A of the Securities Exchange Act of 1934. Each record represents one transfer agent's annual operating report for a single calendar reporting year (period of report YYYY-12-31), packaging the filing's structured XML payload, an XSL-rendered XHTML view, and a JSON submission envelope under the EDGAR accession number. The filer is the registered transfer agent itself — bank trust departments, broker-dealer transfer agents, independent corporate agents, and captive in-house agents — reporting transfer volumes, securityholder account counts, dividend and interest disbursements, service-company arrangements, lost-securityholder searches, and turnaround-time compliance. Coverage runs from February 2001, when EDGAR began accepting Form TA-2 electronically, through the present, and the dataset is distributed as monthly ZIP containers organised by year, with XML and JSON file types.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset packages every Form TA-2 and Form TA-2/A submission accepted by EDGAR since electronic filing began in February 2001. Form TA-2 is the annual report registered transfer agents must file under Rule 17Ac2-2 promulgated by the SEC under Section 17A of the Securities Exchange Act of 1934: every entity registered as a transfer agent on December 31 of a given year is required to file Form TA-2 covering that year by the following March 31. The form is a fixed-shape questionnaire of twelve numbered items (Q1 through Q12) covering filer identity, service-company arrangements, regulatory agency, transfer volumes, master securityholder file maintenance, securityholder account counts, issue counts by operational role, DRIP and Direct Registration System participation, dividend and interest disbursements, aged record differences, turnaround-time compliance, open-end fund transaction processing, lost-securityholder database searches, and the responsible officer's signature.
The dataset covers the entire registered transfer-agent population, aggregating filings across all four appropriate regulatory agencies (OCC, FDIC, Federal Reserve Board, and SEC) because all four ARAs use the same Rule 17Ac2-2 form and route filings through EDGAR. A TA-2/A record represents an amendment to a previously filed annual report and is structurally identical to a TA-2 record. The records are tightly typed XML forms — there are no financial statements, no MD&A narrative, no auditor reports, and no exhibits. The dataset is delivered as monthly ZIP containers (one per YYYY-MM), with XML and JSON file types only; image assets referenced from the rendered XHTML view (radio-button glyphs, EDGAR logos) are deliberately omitted.
One record is a single Form TA-2 or Form TA-2/A submission accepted by EDGAR, identified by its SEC accession number and corresponding to one transfer agent's annual report for one calendar reporting year. On disk, each record is a folder named after the dashless accession number (for example 000073492425000003 for accession 0000734924-25-000003) containing the structured XML payload of the form, an XSL-rendered XHTML view of the same payload, and a JSON sidecar describing the EDGAR submission envelope. A TA-2/A record is structurally identical to a TA-2 record except that headerData/filerInfo/flags/isFilingAmendment is true and submissionType is TA-2/A.
The form is a fixed-shape questionnaire of twelve numbered items requiring the transfer agent to:
The dataset is delivered as monthly ZIP containers organised by year, addressed as <YYYY>/<YYYY>-<MM>.zip. Inside a container, the top-level directory is the matching YYYY-MM folder, and inside it sits one subdirectory per accession number containing exactly that record's files. Because TA-2 has a March 31 due date, container volume concentrates in March and April of each year, with sparse months elsewhere reflecting late filings, amendments, and stragglers.
The on-disk shape of a single record is:
1
YYYY-MM/
2
└── <accession-no-dashes>/
3
├── metadata.json
4
├── primary_doc.xml
5
└── xslFTA2X01/
6
└── primary_doc.xml
The accession-folder name uses the dashless variant of the EDGAR accession number, which doubles as the path segment under Archives/edgar/data/<cik>/<accessionNoNoDashes>/ on sec.gov.
metadata.jsonmetadata.json is the JSON envelope describing the EDGAR submission, derived from the original .txt complete-submission file. It is the join key between the dataset and the live EDGAR archive. Its meaningful fields are:
formType: TA-2 or TA-2/A.accessionNo: the dashed accession identifier, e.g. 0000734924-25-000003.filedAt: ISO-8601 timestamp with timezone offset for the moment EDGAR accepted the submission.effectivenessDate: the calendar date the filing took effect.periodOfReport: the reporting-period end date, always YYYY-12-31 for TA-2.description: human-readable label, typically Form TA-2 - Annual disclosure filing made by all bank and non-bank Transfer Agents.linkToFilingDetails: canonical EDGAR URL of the XSL-rendered view (.../xslFTA2X01/primary_doc.xml).linkToHtml: URL of the EDGAR filing index page (...-index.htm).linkToTxt: URL of the full submission .txt bundle (linked but not redistributed inside the container).linkToXbrl: empty for TA-2.documentFormatFiles[]: a list mirroring the <DOCUMENT> blocks of the EDGAR submission .txt, with sequence, size, documentUrl, and type for each entry. For a TA-2 record this list typically contains the XSL-styled HTML rendering, the raw XML payload, and the complete-submission .txt bundle.entities[]: the filer entities. Per entity the structured fields are cik, companyName (with the (Filer) role suffix appended, e.g. KANSAS CITY LIFE INSURANCE CO TA /TA (Filer)), fileNo in the 084-XXXXX transfer-agent file-number range, irsNo, stateOfIncorporation, fiscalYearEnd formatted as MMDD, act (e.g. 34 for the Securities Exchange Act of 1934), type, and filmNo.seriesAndClassesContractsInformation[] and dataFiles[]: present in the schema but empty for TA-2 filings.id: an opaque hex record identifier.primary_doc.xml (the TA-2 form payload)primary_doc.xml is the canonical EDGAR XML for the filing, scoped to the namespace http://www.sec.gov/edgar/ta/tatwofiler and tagged with <schemaVersion>X0606</schemaVersion> for current-era submissions. The root element is <edgarSubmission>, with two ordered children: headerData (filer identification and filing-envelope flags) and formData (the answers to the twelve numbered questions). The schema is strict and positional: every record of a given schema version carries the same element tree, with leaf values populated from the filer's annual data.
headerDataThe headerData block carries the EDGAR submission envelope:
submissionType: literal TA-2 or TA-2/A.filerInfo/periodOfReport: the December 31 reporting-period end (e.g. 2024-12-31).filerInfo/filer/fileNumber: the SEC-assigned transfer-agent file number, in the 084-XXXXX range (e.g. 084-00893).filerInfo/filer/filerCredentials/cik: the 10-digit zero-padded Central Index Key.filerInfo/filer/filerCredentials/ccc: the CIK Confirmation Code, redacted in the public archive as XXXXXXXX.filerInfo/testOrLive: LIVE or TEST.filerInfo/flags/returnCopy: boolean.filerInfo/flags/isFilingAmendment: boolean, true for TA-2/A filings.filerInfo/entityName: the registrant's full legal name.formDataThe body of the form maps each numbered question on Form TA-2 to a named XML element. Children of <formData>, in order:
<engagedServiceCompany> (Q2): serviceCompany (the name of an outside service company, or None) and registrantEngagedService (Y/N, Q2(a)).<registrantRegulatoryAgency> (Q3): regulatoryAgency (the appropriate regulatory agency, e.g. Securities and Exchange Commission, Q3(a)) and amendmentFiled (Yes / No / Not applicable, Q3(b)).<serviceCompanyData>: the bulk of the report, covering Q4 through Q11. Its children, in order:
numberItemsReceivedForTransfer (Q4(a)) — integer count of items received for transfer during the reporting period.numberMasterSecurityHolderFilings (Q4(b)) — integer count of master securityholder file maintenance items.numberIndividualAccounts (Q5(a)) — total individual securityholder accounts as of December 31.numberDivReinvDirPurPlanAccounts (Q5(b)) — accounts in dividend reinvestment / direct purchase plans.numberDirectRegistSystemAccounts (Q5(c)) — accounts held under the Direct Registration System.securityHolderAccounts (Q5(d)) — percentage breakdown of accounts by security category, with the six children equitySecurity, debtSecurity, openEndInvestmentCompany, limitedPartnership, municipalDebt, and other. Values are decimal percentages summing to 100.00.securityHolderData — Q6 through Q11, with these children in order:
transMaintainMasterSecHolder (Q6(a)), transNotMaintMasterSecHolder (Q6(b)), and notTransMaintMasterSecHolder (Q6(c)). Each of the three contains the same six numeric children (equitySecurity, debtSecurity, openEndInvestmentCompany, limitedPartnership, municipalDebt, other), here representing issue counts in the three exclusive operational categories: "receives items and maintains master files", "receives but does not maintain", and "does not receive but maintains".dividendReinvDirectPurchasePlan (Q7(a)) — issue count for DRIP-eligible securities.directRegistrationSystem (Q7(b)) — issue count for DRS-eligible securities.dividendAndInterest (Q7(c)) — paired children numberIssues and amountIssues (dollar value, e.g. 5422712.00) for dividends and interest disbursed.priorAgent and currentAgent (Q8(a)) — each with numberIssues and amountIssues, capturing aged record differences attributable to the prior agent and accumulated under the current agent.numberFiled (Q8(b)) — count of quarterly buy-in reports filed under Rule 17Ad-11.alwaysCompliant (Q9(a)) — Yes / No / Not Applicable, attesting to turnaround-time compliance under Rule 17Ad-2.total (Q10(a)) — total open-end investment company transactions processed.totalOtherThanReceiptOrderDate (Q10(b)) — "as-of" transactions priced other than at the receipt-order date.databaseSearches (Q11(a)) — a repeating element (zero or more occurrences), one per lost-securityholder database search performed during the reporting period under Rule 17Ad-17. Each occurrence carries databaseSearchDate in MM/DD/YYYY form, numberLostAccountsSearched, and numberAddressesFromSearch.numberLostAccountsRemittedToStates (Q11(b)) — count of lost-securityholder accounts remitted to states under escheat.<signatureData> (Q12): signatureName (the responsible officer's name), signaturePhoneNumber (10-digit string), signatureTitle (e.g. Assistant Secretary), and signatureDate (MM/DD/YYYY).Numeric leaves are emitted as bare numbers without thousands separators; percentage leaves use two decimal places; date leaves use YYYY-MM-DD inside headerData but MM/DD/YYYY inside databaseSearches and signatureData. Yes/No fields use the literal strings Y/N, Yes/No, and Not applicable / Not Applicable; capitalisation varies by question.
xslFTA2X01/primary_doc.xml (rendered XHTML view)The third file is the human-readable rendering of the same XML payload. Despite the .xml extension, it is XHTML produced by EDGAR's FTA2X01 XSL transform and is the document served at metadata.linkToFilingDetails. It references SEC-hosted CSS (e.g. /css/SDR_print.css) and lays the form out as five labelled sections that mirror the questionnaire:
Form TA-2 Filer Information (Q1) — CIK, file number, period of report, entity name.TA-2: Service Company Information (Q2) — service-company arrangements.TA-2: Registration Information (Q3) — appropriate regulatory agency and amendment status.TA-2: Annual Report Information (Q4–Q11) — operational metrics.TA-2: Signature (Q12) — signer block.Field values from the XML appear inside <div class="fakeBox2">…</div> slots in the rendered view. The rendering exists for human inspection; the structured XML is the authoritative copy for extraction.
A record includes the structured XML payload (primary_doc.xml), the XSL-rendered XHTML view (xslFTA2X01/primary_doc.xml), and the JSON metadata envelope (metadata.json). The complete-submission .txt bundle that EDGAR distributes (linked from metadata.linkToTxt) is referenced by URL but is not redistributed inside the container. Image files referenced from the rendered XHTML (radio-button glyphs, EDGAR logos) are intentionally omitted, consistent with the dataset's exclusion of image files. Because Form TA-2 is filed as a structured XML form, there are no exhibit attachments, no XBRL instance documents, no graphics carrying disclosure content, and no separate financial statements to package.
Form TA-2 has been filed via EDGAR since February 2001, and dataset coverage extends from then to the present. Two structural inflection points matter for cross-year interpretation:
http://www.sec.gov/edgar/ta/tatwofiler and <schemaVersion>X0606</schemaVersion>. Older filings use earlier schema versions of the same tatwofiler namespace; the question-to-element mapping is broadly stable, but specific element names and the precise children of securityHolderAccounts and securityHolderData evolved with successive schema revisions.databaseSearches, numberLostAccountsRemittedToStates) and the Direct Registration System reporting (numberDirectRegistSystemAccounts, directRegistrationSystem) reflect rule changes that expanded the operational data points required from transfer agents during the dataset's coverage window. Filings predating those expansions report fewer fields or carry empty values for the corresponding elements.The dataset preserves the original XML payload as filed. Consumers comparing values across years should consult <schemaVersion> to detect schema-driven differences in element presence and ordering, and should be aware that a TA-2/A amendment (flagged by isFilingAmendment=true and submissionType=TA-2/A) supersedes the prior TA-2 filing for the same (cik, periodOfReport) pair.
metadata.accessionNo. The dashless form is also the EDGAR archive path segment under Archives/edgar/data/<cik>/<accessionNoNoDashes>/, allowing direct round-trip to the live EDGAR copy.metadata.entities[].cik and metadata.entities[].fileNo align with <filerCredentials><cik> and <filer><fileNumber> inside primary_doc.xml; metadata.periodOfReport aligns with headerData/filerInfo/periodOfReport; metadata.formType aligns with headerData/submissionType. This redundancy lets either file serve as the indexable face of the record.filerCredentials/ccc is always redacted as XXXXXXXX in the public archive and carries no information.databaseSearches element may occur zero, one, or many times. A record with no lost-securityholder search activity simply omits the element rather than emitting an empty placeholder.transMaintainMasterSecHolder, transNotMaintMasterSecHolder, notTransMaintMasterSecHolder) are mutually exclusive partitions of the issue population; per-category counts add up to the total issues serviced under that operational mode. The Q5(d) securityHolderAccounts percentages, by contrast, must sum to 100.00 across the six security-type children..xml extension, naive file-type detection on extension alone will misclassify it. The authoritative structured copy is the top-level primary_doc.xml, not the file nested under xslFTA2X01/.metadata.linkToXbrl is empty and dataFiles[] is empty for TA-2 records. All structured extraction should target the tatwofiler XML directly, keying on element local names within the namespace http://www.sec.gov/edgar/ta/tatwofiler.The filer is the registered transfer agent itself, reporting in its capacity as a regulated entity under Section 17A of the Securities Exchange Act of 1934. Issuers whose securities are serviced and the securityholders whose accounts are maintained are not filers; they appear only as aggregate counts inside the form. A "transfer agent" is defined in Section 3(a)(25) of the Exchange Act as any person who, for Section 12-registered securities (or securities exempted only by Section 12(g)(2)(B) or (G)), countersigns issued securities, monitors issuance to prevent overissue, registers transfers, exchanges or converts securities, or transfers record ownership by bookkeeping entry. Any person performing any one of those functions must register before acting.
The Form TA-2 filing population therefore includes four operating types:
An entity enters the population by filing Form TA-1 (the registration form) with its appropriate regulatory agency (ARA). Once registered and still registered on December 31, it owes a Form TA-2 for that calendar year.
Form TA-2 is calendar-year periodic, not event-driven. The trigger has two conjoined conditions under Rule 17Ac2-2:
If both are met, the report is due by March 31 of the following calendar year and covers activity from January 1 through December 31 of the prior year. The deadline is fixed; it does not vary by filer type, fiscal year, or volume, and there is no Form 12b-25-style automatic extension. A transfer agent registered for only part of the year but still registered on December 31 still owes a full annual report by the next March 31. Withdrawal via Form TA-W before December 31 is the only way to avoid the next year's filing.
The ARA is determined by the institutional character of the filer:
All four ARAs use the same Rule 17Ac2-2 form, instructions, and March 31 deadline, and all filings flow through EDGAR regardless of which ARA supervises the filer.
Rule 17Ac2-2 lets low-activity registrants complete a reduced subset of the form. A transfer agent that during the reporting year acted only for its own securities, or whose activity fell below the form's de minimis thresholds, completes only the identifying questions (typically Questions 1–3) and skips the volume-driven operational sections covering items processed, dividend and interest disbursement, proxy distributions, turnaround times, aged items, and service company use. A transfer agent above those thresholds completes the full form.
This is not an exemption from filing — every registrant on December 31 must file. It is an exemption from completing the activity sections. The dataset therefore contains a long tail of compact filings from captive and small in-house agents alongside very long filings from large bank and independent agents.
Form TA-2/A amends a previously submitted Form TA-2. The trigger is corrective rather than scheduled; common reasons include misreported volumes, restated figures, updated service company lists, corrected identifying or ARA information, and supplementation in response to ARA examination findings. There is no fixed amendment deadline, but Rule 17Ac2-2 requires material inaccuracies to be corrected promptly. A TA-2/A references the same calendar reporting year as the original; amendments to prior-year filings can appear well after that year's March 31 deadline, and there is no cap on amendments per reporting year.
Form TA-2 sits in a narrow cluster of Section 17A filings that govern the registration, ongoing reporting, and deregistration of transfer agents and clearing agencies. The forms most likely to be confused with TA-2 — or used alongside it — are the rest of the transfer-agent family (TA-1, TA-W, TA-2/A), the clearing-agency analogue (CA-1), and the parallel periodic reports filed by broker-dealers (Form 17-H, FOCUS / X-17A-5).
Form TA-2 is the only public, annual, structured operating report on the back-office mechanics of U.S. securities ownership transfer. TA-1 and TA-W bracket it as entry and exit records with no activity data. TA-2/A amends rather than replaces it. Form CA-1 covers a parallel registrant class with no equivalent annual operating disclosure. 17-H and Form X-17A-5 are sibling Section 17 reports with non-overlapping content and, for 17-H, different confidentiality treatment. Issuer- and ownership-level filings cannot be aggregated to reproduce what TA-2 reports. For transfer-agent-level activity volumes, service-company relationships, dividend disbursement counts, proxy mailing volumes, or industry concentration, this dataset is not substitutable; for identity and registration status only, TA-1 plus the SEC transfer-agent registration list is sufficient; for lifecycle reconstruction, combine TA-1, TA-2/TA-2/A, and TA-W.
Form TA-2 is the only annual, public, firm-level disclosure of how registered transfer agents service issues, process transfers, disburse dividends and interest, and distribute proxies. Its users cluster around three jobs: studying the transfer-agent industry, supervising it, or making commercial decisions inside it.
Analysts covering post-trade and securities services use TA-2 as the primary public source for sizing the registered transfer-agent population and tracking concentration. They aggregate the Q6 issue tables (issues serviced by asset class), Q5 (securityholder accounts), and the activity-volume questions (items received and processed, transfers, dividend and interest payments) into market-share rankings, growth rates, and concentration measures. Output: market-sizing reports, consolidation studies, and rulemaking comment letters.
Economists supporting Section 17A rule review pair the volume and account-count fields with the Q2 service-company attribution to measure how much of the registered population actually performs core functions in-house. Output: economic analysis in proposing and adopting releases.
Examination staff at the federal banking agencies use TA-2 in routine oversight of depository institutions registered as transfer agents. They track year-over-year changes in issue counts, account counts, and processed volumes, verify the attribution between the bank and its service companies, and flag material changes disclosed in the narrative items. Output: off-site monitoring, exam scoping, and peer comparisons among bank agents of similar scale.
Buy-side corporate-development teams and their banking and consulting advisors use TA-2 to source and value transfer-agent acquisitions and carve-outs. They pull target-level operating metrics rarely disclosed elsewhere — issues by type, total accounts, transaction throughput, dividend and proxy volumes, share of work outsourced — to feed valuation, synergy modeling, and customer-overlap analysis.
Strategy teams at large transfer agents build longitudinal panels of competitor filings to track gain or loss of issues, account-count drift, and changes in service-company relationships. A small filer reporting that a service company performs most of its functions signals a white-label relationship or migration target. Output: win/loss analysis, prospecting lists for sub-servicing, and pricing-committee inputs.
Assistant treasurers, corporate secretaries, and stock-administration leads use TA-2 during transfer-agent RFPs and periodic vendor reviews. They check the candidate's issue and account totals for scale, the activity-volume questions for throughput, the service-company tables for what is actually done in-house, and the material-change narrative for service-quality signals. Output: vendor due diligence and audit-committee briefings.
Researchers studying the registered-holder side of the proxy plumbing use the proxy, interim communication, and annual report counts together with account-count fields to estimate registered-holder populations relative to the street-name universe. Output: academic and policy research on retail participation and the cost structure of investor communications.
Compliance officers benchmark their own draft TA-2 against peer filings before submission — how peers classify issues, complete the volume questions, attribute work under Q2, and describe material changes. Output: calibrated draft filings and exam preparation packs.
Vendors building filing-prep and supervisory tools for the transfer-agent industry parse the full XML and JSON corpus to derive field distributions, validation rules, and amendment patterns visible in TA-2/A filings. Output: automated form-completion products, anomaly-detection rules, and benchmarking dashboards.
Credit and operational-risk analysts at banks and asset managers exposed to transfer agents combine the activity-volume questions with the service-company disclosures to gauge how much processing capacity a counterparty controls versus depends on a third-party platform. Output: counterparty reviews and shared-service-company concentration analysis.
Enforcement researchers, investigative journalists, and litigation-support analysts use TA-2 to reconstruct which agent serviced a given issuer, what volumes it processed, and which service companies sat behind it. They chain the identifying header, issue counts, and service-company tables against TA-1 registration data and issuer filings, often in microcap and shell-company investigations.
Teams building extraction and retrieval systems use TA-2 as a narrow, clean, well-structured corpus that mixes XML fields with short free-text narrative on material changes — useful for evaluating field-extraction accuracy, cross-year change detection, and entity linking between agents, service companies, and issuers.
The following workflows tie directly to specific TA-2 fields and to the multi-year, agent-level structure of the dataset.
Ranking transfer agents by issues serviced and accounts under administration. Aggregate the six asset-class children of transMaintainMasterSecHolder, transNotMaintMasterSecHolder, and notTransMaintMasterSecHolder (Q6) per filer-year to derive total issues serviced, then join to numberIndividualAccounts, numberDivReinvDirPurPlanAccounts, and numberDirectRegistSystemAccounts (Q5) to produce annual league tables segmented by equity, debt, open-end fund, limited partnership, and municipal-debt issues. Output feeds market-share dashboards, HHI-style concentration metrics, and Section 17A rulemaking comment letters.
Detecting white-label and sub-servicing relationships from Q2 attribution. Filter records where engagedServiceCompany/registrantEngagedService is Y, then read the named serviceCompany together with the percentage attribution between filer and service company. Filers reporting that an outside service company performs the bulk of regulated functions are surfaced as candidates for migration, acquisition targeting, or supervisory follow-up. Roll the named service companies up across the panel to quantify shared-service-company concentration risk for counterparty reviews.
Year-over-year change detection for bank examiners and CCOs. Diff successive (cik, periodOfReport) records on numberItemsReceivedForTransfer (Q4(a)), numberMasterSecurityHolderFilings (Q4(b)), the Q6 issue tables, dividendAndInterest/amountIssues (Q7(c)), and priorAgent/currentAgent aged-difference counts (Q8(a)). Materially shifting volumes, a flipped Q2 attribution, or a new service-company name trigger off-site monitoring alerts and exam-scoping notes for bank-affiliated agents.
Tracking amendments and restatements via TA-2/A behaviour. Use headerData/filerInfo/flags/isFilingAmendment=true and submissionType=TA-2/A to identify amended reports, key them to the original filing on (cik, periodOfReport), and compute field-level deltas against the superseded TA-2. The result is an amendment ledger showing which filers restate which questions (commonly Q4 volumes, Q5 percentages, or Q8 aged differences) and how long after the March 31 deadline corrections land.
M&A and RFP scale benchmarking for issuer-services targets. During transfer-agent acquisitions, carve-outs, and RFP scoring, pull the target's last three to five TA-2s and extract numberIndividualAccounts, the Q6 issue mix by asset class, total and totalOtherThanReceiptOrderDate open-end fund transactions (Q10), DRIP/DRS issue and account counts (Q5(b), Q5(c), Q7(a), Q7(b)), and the Q2 percentage split with any service company. These feed valuation comparables, synergy modelling, customer-overlap analysis, and audit-committee vendor-review packs.
Lost-securityholder and escheat compliance benchmarking. Iterate the repeating databaseSearches element to get per-search databaseSearchDate, numberLostAccountsSearched, and numberAddressesFromSearch, and pair with numberLostAccountsRemittedToStates (Q11(b)) and numberFiled quarterly buy-in reports (Q8(b)). Compliance teams use the resulting per-agent profile to benchmark Rule 17Ad-17 search cadence and Rule 17Ad-11 buy-in volumes against peers of similar account scale before exam season.
Lifecycle reconstruction and microcap investigations. Chain a registrant's TA-1 registration, full TA-2/TA-2/A history (keyed on 084-XXXXX file number and CIK), and any TA-W to reconstruct who serviced a given issuer in a given year, what they processed, and which service companies sat behind them. Investigative researchers cross-reference the serviceCompany field and Q6 issue counts against issuer 10-Ks and Schedules 13D/13G to trace recordkeeping responsibility in shell-company and microcap matters.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-ta2-files.json
This endpoint returns dataset metadata (name, description, last updated timestamp, earliest sample date, total records, total size, form types, container format, and file types), the full dataset download URL, and the list of individual container files with per-container size, record count, updated timestamp, and download URL. Poll this endpoint daily to detect which containers were modified in the latest refresh and selectively download only the changed containers. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-692d-a670-d92811e10ccb",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-ta2-files.zip",
4
"name": "Form TA-2 Files Dataset",
5
"updatedAt": "2026-05-07T02:51:43.282Z",
6
"earliestSampleDate": "2001-02-01",
7
"totalRecords": 14488,
8
"totalSize": 50199515,
9
"formTypes": ["TA-2", "TA-2/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["XML", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-ta2-files/2026/2026-03.zip",
15
"key": "2026/2026-03.zip",
16
"size": 1382183,
17
"records": 154,
18
"updatedAt": "2026-05-07T02:51:43.282Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-ta2-files.zip?token=YOUR_API_KEY
Downloads the complete Form TA-2 Files dataset as a single ZIP archive covering all filings from 2001-02-01 to the most recent refresh, including form types TA-2 and TA-2/A in both XML and JSON formats. This endpoint requires a valid sec-api.io API key passed as the token query parameter.
Download Single Container: https://api.sec-api.io/datasets/form-ta2-files/2026/2026-03.zip?token=YOUR_API_KEY
Downloads one individual container, such as a monthly archive, instead of the full dataset. Use the downloadUrl values from the index JSON response to fetch specific containers. This endpoint requires a valid sec-api.io API key passed as the token query parameter.
The dataset covers Form TA-2 and its amendment variant Form TA-2/A, the annual report registered transfer agents file under Rule 17Ac2-2 promulgated by the SEC under Section 17A of the Securities Exchange Act of 1934. It does not include Form TA-1 (registration), Form TA-W (withdrawal), or Form CA-1 (clearing-agency registration).
One record is a single Form TA-2 or Form TA-2/A submission accepted by EDGAR, identified by its SEC accession number and corresponding to one transfer agent's annual operating report for one calendar reporting year (period of report YYYY-12-31). Each record is a folder containing the structured XML payload, an XSL-rendered XHTML view, and a JSON metadata envelope.
Every entity registered as a transfer agent on December 31 of a given year must file Form TA-2 covering that year by the following March 31. The population spans bank transfer agents (supervised by OCC, FDIC, or the Federal Reserve Board), broker-dealer transfer agents, independent corporate agents, and captive in-house agents (issuers acting as their own transfer agent), all routing through EDGAR regardless of which appropriate regulatory agency supervises them.
The dataset covers all Form TA-2 and TA-2/A filings submitted to EDGAR from February 2001, when electronic filing of TA-2 began, through the most recent refresh. Pre-2001 paper filings are not included.
The dataset is distributed as monthly ZIP containers organised by year, addressed as <YYYY>/<YYYY>-<MM>.zip. File types inside each container are XML (the canonical EDGAR XML payload and the XSL-rendered XHTML view) and JSON (the metadata envelope). Image files referenced from the rendered XHTML are intentionally omitted.
A TA-2/A is structurally identical to a TA-2 except that headerData/filerInfo/flags/isFilingAmendment is true and submissionType is TA-2/A. Amendments share the same (cik, periodOfReport) as the original filing they correct and supersede the prior TA-2 for that pair; there is no fixed amendment deadline and no cap on amendments per reporting year, so they can land well after the original March 31 deadline.
Form TA-1 is the one-time registration filing capturing the agent's identity, organizational form, appropriate regulatory agency, and control persons. Form TA-2 is the annual operational report covering what the agent actually did during the year — transfer volumes, securityholder accounts, dividend and interest disbursements, service-company arrangements, and turnaround-time compliance. TA-1 contains no activity data; TA-2 contains no static registration metadata beyond the identifying header.