Original Summary

I’m in second year of a CS degree in Dublin and I’ve been building Paprly on the side. You upload a supplier invoice (PDF, scan, phone photo) and it pulls out the supplier, dates, line items and VAT, then pushes it into Xero, QuickBooks or Sage as a bill, so nobody has to retype it. The thing that taught me the most so far: an accountant tested it on a real invoice and it read 9 September as 9 of... something else. It had assumed US-style dates. Anywhere that writes day/month, that’s a quiet way to get every bill wrong. Fixed now, so European dates read day-first, but it’s the kind of bug you’d never find with your own test files. A few other things I’ve had to learn the hard way: credit notes shouldn’t be exported as normal bills (it now flags them instead), and exporting the same invoice twice needs a warning, because people do it. Still very early. If you’ve built something where real-world messy input breaks your clean assumptions, I’d like to hear how you test for it. paprly.org if you want to poke at it. Free to try, no card.   submitted by   /u/Hashtag_Maybe [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/18 06:19:12