Transuite.Org (TRSO) Change in Accured Expenses (2025 - 2026)
Transuite.Org's Change in Accured Expenses was $51,131 in Q1 2026, up 172.1% from $18,789 a year earlier but down 16.5% from the prior quarter.
Powered by 
Analysis
Transuite.Org (TRSO) Change in Accured Expenses (2025 - 2026) Analysis & Trends
On a trailing twelve-month basis, Transuite.Org's Change in Accured Expenses was $104,790 through Mar 31, 2026; for FY2025, it was $72,448.
- In earlier years, Change in Accured Expenses was $35,149 in FY2024 (+269.6%) and $9,510 in FY2023.
- Quarterly Change in Accured Expenses has moved between -$32,257 (Q2 2025) and $61,224 (Q4 2025) over five years.
- Per Business Quant data, TRSO's Change in Accured Expenses in the three quarters before Q1 2026 was $61,224 (Q4 2025), $24,692 (Q3 2025) and -$32,257 (Q2 2025).
Peer Set
Peer Comparison
| # | Company | Market Cap | Enterprise Value | Gross Profit (Qtr) | Change Accured Exp. (Qtr) |
|---|---|---|---|---|---|
| 1 | Palo Alto Networks | 328.64 Bn | 313.71 Bn | 2.30 Bn | 369.00 Mn |
| 2 | CrowdStrike Holdings | 276.50 Bn | 256.94 Bn | 1.10 Bn | 72.38 Mn |
| 3 | Fortinet | 132.74 Bn | 118.67 Bn | 1.64 Bn | 75.10 Mn |
| 4 | Snowflake | 120.19 Bn | 107.50 Bn | 1.04 Bn | 108.85 Mn |
| 5 | Datadog | 99.51 Bn | 81.15 Bn | 881.34 Mn | 6.98 Mn |
| 6 | Okta | 35.35 Bn | 25.44 Bn | 641.00 Mn | -2.00 Mn |
| 7 | Axon Enterprise | 33.58 Bn | 28.10 Bn | 546.45 Mn | 256.58 Mn |
| 8 | Zscaler | 32.06 Bn | 18.18 Bn | - | - |
| 9 | MongoDB | 28.84 Bn | 19.30 Bn | 569.77 Mn | 43.09 Mn |
| 10 | Transuite.Org | 728,416.83 | 661,388.83 | 109,624.00 | 51,131.00 |
Historic Data
Download Data
Historic Data
| Date | Value |
|---|---|
| Mar 31, 2026 | 51,131.00 |
| Dec 31, 2025 | 61,224.00 |
| Sep 30, 2025 | 24,692.00 |
| Jun 30, 2025 | -32,257.00 |
| Mar 31, 2025 | 18,789.00 |
API Access
Transuite.Org Change in Accured Expenses API
Pull this series into your own models, spreadsheets and apps with the Business Quant
Historical Metrics API. The request below matches the chart above — change the
frequency, period or values and it follows. Swap YOUR_API_KEY for your own key.
https://data.businessquant.com/historic?slug=change-in-accured-expenses&ticker=TRSO&period=max&api_key=YOUR_API_KEYimport requests
url = "https://data.businessquant.com/historic"
params = {"slug": "change-in-accured-expenses", "ticker": "TRSO", "period": "max", "api_key": "YOUR_API_KEY"}
data = requests.get(url, params=params).json()const res = await fetch("https://data.businessquant.com/historic?slug=change-in-accured-expenses&ticker=TRSO&period=max&api_key=YOUR_API_KEY");
const data = await res.json();