Custom development where off-the-shelf offerings end.
For commodity flows we almost always recommend the standard offering. A Klippa or Basecone for pure receipt scanning is faster and cheaper than anything we could build, and we say so. We only come into the picture when more than three systems need to work together, or when the AI layer requires its own risk framework or sector-specific flow that the standard packages do not cover.
Think of healthcare accountancy with automatic DBC checks, housing association audits with a DAEB/non-DAEB split, or a cooperative of independent bookkeepers that wants a shared white-label AI tool. For these kinds of challenges we build the custom solution and integrate it tightly with your existing stack, often drawing on our experience with custom LLM integrations and custom accountancy software.
The architecture always follows the same pattern. We place a thin abstraction layer between the AI model and the accounting package, so that either the model or the underlying stack can be swapped out without rewriting the business logic. Prompts and model choices are version-controlled, tested against representative client data, and automatically evaluated for accuracy before a new version reaches production. That is deliberate: the LLM landscape changes every few months, and a firm running GPT-4 today should be able to move to Claude 5 or an open-source alternative next year without fuss, if that suits better on price, speed or compliance.