The MVP delivers coding proposals for invoices, allowing users to adjust prefilled suggestions with confidence levels color-coded for focus and efficiency. It emphasizes simplicity, core functionality, and continuous improvement via a feedback loop.
The core idea behind an MVP is to develop a product with just enough functionality to address the most critical needs of your target users, allowing you to validate assumptions and learn from real-world usage.
By focusing on essential features, an MVP lets us bring the product to the market quickly, where we can test it, gather feedback, and iterate based on real customer interactions. This approach helps minimize the risk of investing time and resources in unnecessary features while ensuring that the most important aspects of the product are thoroughly validated.
In the MVP, we focus on the core feature of providing coding proposals to streamline the customer’s invoice handling process. The aim is to prefill the invoice with coding proposals before the end-user interacts with it. This allows the user to focus primarily on reviewing and adjusting the proposal rather than manually coding from scratch.
Kaunt provides coding proposals with three confidence levels: HIGH, MEDIUM, and LOW. Each of these levels represents how confident the system is in the correctness of the proposed coding. To help users quickly assess which proposals require attention, we recommend color-coding the confidence levels in the following way:
This approach provides a simple, intuitive way for users to identify potential issues, streamlining their workflow and making it easier to prioritize which dimensions to review.
There are multiple ways to present coding proposals in the user interface, depending on the design flexibility of the existing system.
By structuring the MVP UI in this way, we ensure that end-users have the tools they need to interact with the invoice in a straightforward manner, allowing them to benefit from automation without losing the ability to intervene where needed.
Kaunt provides up to three coding proposals for each invoice, each assigned a confidence level (HIGH, MEDIUM, or LOW). These proposals can be utilized in three distinct ways: Individual Dimensions, Dimension Combination, and Proposal Groups. Each method offers a unique approach to handling invoice coding based on how you want to treat the dimensional relationships and groupings in the coding process.
When using the Individual Dimensions output, each dimension (e.g., GL account, Cost Center, Tax Code) is treated independently. There is no correlation between the dimensions in the output. This means that even if a specific combination of these dimensions has never been used together, Kaunt can still provide proposals for each dimension on its own.
When should I use this output?
In contrast to Individual Dimensions, the Dimension Combination output provides coding proposals that maintain correlation between the dimensions. The output is restricted to combinations of dimension values that have been seen before in previous codings.
When should I use this output?
When dealing with multi-line invoices, it's common for multiple invoice lines to be coded in the same way. Proposal Groups group these lines together based on the Dimension Combination output, producing a single proposal for the group rather than individual proposals for each line.
When should I use this output?
In an MVP, especially during pilot phases with customers, gathering feedback is critical to refining the product and improving its core functionality.
By implementing a posting feedback loop, Kaunt can:
The feedback loop is essential for continuous improvement, allowing Kaunt to enhance its proposal system based on real-world user interaction and invoice outcomes.