Original Summary

I've been building out my document intelligence app DocReadi, an AI-powered document extraction app, with human-in-the-loop features to allow for the accuracy that finance processes require. Think of it as OCR 2.0 AI-edition You send it invoices, receipts, credit notes or supplier statements by email, upload, the API, or a watched SFTP, S3, OneDrive or SharePoint folder. It reads the fields and the line items and checks the arithmetic: the lines have to add up to the subtotal, and subtotal plus VAT has to equal the total. Then the document waits in a review queue. Once you approve it, the data goes out as CSV, Excel, JSON, a Xero Bills import file, through the API or as a signed webhook. It deliberately stops there, with the idea that it sits in front of your established business processes. No approvals, payments, bank feeds or reconciliation. Most people who'd use it already have tools for those. The model only reads what's printed, and anything missing is left blank and flagged. That's why the video shows an empty PO reference. If you're building anything that reads documents with an LLM, steal this: make it say "not on the page" out loud, and treat a confident value nobody printed as a bug. What I'd like feedback on: Does the video make sense and explain what the product does? And if you happen to sign up for a trial acount, I'm really battling to streamline the first 5 minutes for a new user and to explain the user interface and how to navigate the app. There's a free trial of 200 pages over 90 days, no card, at docreadi.com . Any and all feedback is welcomed - my biggest challenge is on UI/UX - I have a very logical mind and can't always see things from a users perspective 😂   submitted by   /u/Dangerous-Baby838 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/7 04:50:42