Palatin Technologies, Inc.: research and development expense

At a glance

Palatin Technologies reported research and development expense of $14.9 million for the year ending 2025-06-30, down 33.5% from $22.4 million a year earlier. From 2010 to 2025 it grew at a compound 1.3% a year, from $12.3 million to $14.9 million. Across the last five reported years it ranged from $12.9 million (2021-06-30) to $22.6 million (2023-06-30).

Computed from the values in the table below, in USD; each links to the filing it came from.

What this measure means

Research and development costs recognized as expense. Capitalization policies and acquired projects can make this differ from total cash invested in development.

Exact concept: us-gaap:ResearchAndDevelopmentExpense. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2009-07-01 to 2025-06-30. The SEC response was captured on 2026-09-20.

Selected filing history

Related PALATIN TECHNOLOGIES, INC. histories

• Revenue
• Cost of revenue
• Operating expenses
• Selling, general and administrative expense
• General and administrative expense
• Operating income or loss
• Total assets
• Total liabilities

All 54 Palatin Technologies histories

Inspect the source

Entity

PALATIN TECHNOLOGIES, INC. / CIK 0000911216

Captured

2026-09-20 05:06 UTC

SEC response SHA-256

dea0c935057d0b00b98869e527ab39e8e66171ec9db0dd9125f9020a11f753cc

Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON

Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.

Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.

Use this in research

A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.

These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.

Research methodology · Execution and cost assumptions · Check backtest overfitting

Build with the open-source tools

Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.

• Get an API key and run your first validation
• Connect the MCP server to your coding assistant
• Inspect the ALPHAC engine on GitHub
• Read the MCP server source and integration examples

The MCP server is free and MIT-licensed: npx -y canli-mcp. If these records help your research, a star on GitHub helps other researchers find them.

import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0000911216.json") as response:
    record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
    print(concept["tag"], next(iter(concept["observations"])))