How Tymit Cut Software Reconciliation From a Day to 15 Minutes

Tymit is a fast-growing UK FinTech with operations and tax reporting across the UK and Spain. For its small finance team, the work was never only tracking spend; it was managing software: 102 subscriptions, each with a renewal to track, a recurring stream of invoices to capture and reconcile into NetSuite, and a clear owner. Tymit ran that work through a generic corporate card tool. That tool was built to manage company spend. Managing software subscriptions is a different job, and Daniel Chen, Accounting and Financial Reporting Senior Specialist at Tymit, was doing most of it by hand. Cledara is software subscription management built for finance, and the shift was less about a better tool than a different one, built for the job Tymit actually needed done.

On the previous tool, the monthly reconciliation routinely took Daniel close to a full working day, and that was at a fraction of the volume Tymit runs now.

“Before Cledara, the reconciliation process previously required nearly a whole day of work”.

The tool was not failing at spend management; it simply was not built to manage software subscriptions, so the subscription work landed on Daniel manually, on top of it. He points out that the old tool ran "maybe one-tenth of the transactions" he now has on Cledara, yet still took him longer to get through.

As companies grow, software ownership scatters. At Tymit, requests funnelled through a single coordinator, and spend sat on shared corporate cards. When an invoice went missing, the finance team could not easily say who owned the tool. Daniel describes a technology function with three cards and ten people behind them, and no clear answer to a simple question: who do I ask?

A spend tool is organised around the transaction: what was spent, on what card, by whom. Cledara is organised around the subscription itself, and every subscription has one named owner. That is a different unit of analysis, not a longer feature list. A spend tool can issue a card for every tool and still leave you asking who owns the renewal, because the thing it manages is the spend, not the subscription.

“It's much less about hiding behind a card and much more about fostering genuine accountability.”

The change at Tymit was operational, not cosmetic. As Daniel puts it, the team is now "forcing all employees to be responsible, not just cardholders." Ownership moved from a shared card to a person, so a missing invoice now points to an owner instead of a department.

"f I can narrow that responsibility down to one person for each software,”, Daniel says, "we know exactly who to consult."

Most support is built to close tickets. A question comes in, an answer goes out, the case is marked resolved. For a lean team accounting for more than a hundred apps, that model hands the actual work, managing the software, straight back to the customer.

What Daniel describes is a different scope. Rather than resolve one query and move on, Cledara's team asked about his specific scenario and walked him through the workflow, so the same question would not come back the following month.

“The support team provided concise, clear, and actionable guidance.”

His own test for support is a scope test, not a speed test.

“The true measure of effective support is a resolution so thorough that no further follow-up is required. Which is exactly the experience we had.”

It is the same difference the platform makes, expressed through people. A spend tool's support is scoped to spend. Cledara's is scoped to managing software, which is the job Daniel needed help with.

One month into running the close on Cledara, Daniel sees a platform he can grow with.

“The initial value has been impressive, and I anticipate continued improvement as we scale.”

The takeaway from Tymit is not that one tool beats another. If the job is managing company spend, a spend tool is the right choice. If the job is managing every software subscription, the renewals, the owners, the invoices, the monthly reconciliation, before it gets out of hand, that is a different job, and it needs a tool built for it. Tymit needed the second.