How Laka removed the one person its invoice routing depended on

Background

Laka is a tech-enabled insurance company with a small finance team managing a shared finance inbox that receives invoices and other emails every day across six entities.

The Problem

• Invoices landed daily across six entities. Each one had to be opened, read and identified to work out which entity it belonged to.
• Once identified, each invoice was forwarded by hand to the correct Spendesk inbox for that entity.
• Direct debits followed a different routing path to standard invoices, adding another manual judgement.
• The whole process sat with one person, which became a problem whenever cover was needed.
• Everything else in the inbox was noise that had to be waded through to find what mattered.

The Solution

Numra built an inbox agent for Laka's finance inbox that handles:

• Identification of invoices and the correct entity across six companies.
• Routing of each invoice to the correct Spendesk inbox.
• Separate routing logic for direct debits.
• Labelling of processed emails so the team keeps full visibility of what the agent has done.
• Filtering of irrelevant emails so only what matters gets attention.

The Results

• Every invoice across six entities routed to the correct Spendesk inbox automatically.
• The process no longer depends on one person. Cover is no longer an issue.
• Half the inbox is filtered out as noise before anyone reads it.
• A full working day a month returned to a two-person finance team.