Getting started

Mindee not working: troubleshooting a document-reading tool that fails

When a document extraction tool returns nothing or wrong totals, check file quality, format, size and your own settings before blaming the service.

Editorial illustration for Mindee not working: troubleshooting a document-reading tool that fails

When a document-reading tool such as Mindee returns nothing or the wrong numbers, the fault is usually the input rather than the service: a poor scan, an unsupported file type, a file that is too large, or a setting that points at the wrong document type. Check the input, then your settings, then the provider's own status page. we cannot describe any provider's features, so confirm specifics in its own documentation.

What does the failure look like?

SymptomCommon causeWhat to try
No result at allNetwork, key or quota issue on your sideCheck your connection and your account limits
Error on uploadFile type or sizeConvert to a common format and shrink the file
Empty fieldsLow-quality scanRescan at a steady angle in good light
Wrong totalMisread digitsCheck the digits against the original
Works on some bills, not othersLayout differencesTest with three different samples

How do I test the input properly?

  1. Open the file on your own screen. If you cannot read it comfortably, the software will struggle too.
  2. Check the page is upright, uncropped and not covered by a finger or shadow.
  3. Export as a clean PDF or a plain image rather than a screenshot of a screenshot.
  4. Try a very simple bill first. If that works, the connection is fine and the problem is the difficult document.
  5. Keep a small folder of test bills so you can repeat the check after any change.

A worked example with made-up numbers

Say a tool reads a bill with items of ₹480, ₹1,250 and ₹360 and reports a total of ₹2,190. Add them yourself: 480 + 1,250 + 360 = ₹2,090. The tool read 1,250 as 1,350, or 360 as 460, or the original total is a different number. The habit that saves you is a simple sum check on every extracted bill before it goes into your books.

If you are a developer or a small business owner

  • Log the exact error text and the time of each failed call
  • Check whether the failure is on every file or only one
  • Never paste secret keys into support tickets or chats
  • Test with a fresh key only through the provider's own dashboard
  • Keep a manual fallback for the days it is down

Where does SpendixAI fit?

If your goal is to track spending rather than build an extraction pipeline, SpendixAI starts from bank and card statements you upload as PDF, CSV or Excel, then shows the parsed rows for you to review before saving. Optional features such as reading an unfamiliar statement layout do process the uploaded document, so read its AI and privacy page first.

How do I measure whether extraction is good enough?

Pick twenty bills from the last few months, run them through the tool, and count how many totals match when you check by hand. If eighteen match, that is a ninety per cent hit rate on your own paper, which tells you more than any general claim. Note what the two failures had in common, such as faded print or a handwritten total. That tells you what to fix, or what to key in manually.

What to do next

  • Run the three-bill test today
  • Write down which document types fail
  • Add a sum check before saving anything
  • Contact the provider through its own support page with samples that contain no private details
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports