Loading…

Mitek Systems (MITK) backlog: remaining performance obligations

How much revenue Mitek Systems already has under contract, how fast it converts, and who it is with.

Data as of .

Mitek Systems backlog history

$0$100M$200MSep 2022Sep 2024Mar 2025Sep 2025Mar 2026Jun 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
30 Jun 2026$102M$198M0.5 yrs$34.5M
31 Mar 2026$115M$190M0.6 yrs$36.1M
31 Dec 2025$104M$187M0.6 yrs$25.2M
30 Sep 2025$87.4M$180M0.5 yrs$29.1M
30 Jun 2025$80.6M$178M0.5 yrs$25.9M
31 Mar 2025$81.0M$177M0.5 yrs$29.3M
31 Dec 2024$95.5M$172M0.6 yrs$21.7M
30 Sep 2024$81.1M$172M0.5 yrs$21.2M
30 Sep 2023$18.3M$173M0.1 yrs$17.4M
30 Sep 2022$23.1M$145M0.2 yrs$21.4M

Questions

What is Mitek Systems's backlog?
Mitek Systems reported $102M of remaining performance obligations at 30 Jun 2026, up 27% from a year earlier and down 11% from the previous quarter. That is 0.5 years of trailing revenue already under contract. Book-to-bill last quarter: 0.77.
How fast does Mitek Systems's backlog turn into revenue?
Over the last twelve months Mitek Systems recognised revenue equal to about 206% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.