Transaction Import via XLSX not working

I created a file exactly like the template file for transactions and tried to import it but it throws an 500 error.
THe funny thing is when I try to upload the template file itself it gives the same error.
What can I do?

Without this feature I cannot use Akaunting alltogether. That would be sad. Especially because I already bought a plugin from the marketplace...
Any support on this?

You can enable debug to see more details about the problem:

https://akaunting.com/docs/developer-manual/debug

Hi! It took a long time for me to give akaunting a second chance with this topic as well...
I enabled debug mode, but I can't find why the upload is still not working.
Where do I need to look to find the problem?

I still can't upload the template file.
Please help. I'd really appreciate it.

and also when I export my current data, then change a line with testing data and re-import it, it doesn't work. I always get the error "Undefined index: transactions"

I am in the same situation and no disrespect but without this feature, Akaunting it's pointless to me.

I did a test. created a revenue, I exported it, tried to import it....... FAILED.
So there's no solution.

And here I am.... I converted the XLSX to XLS and it worked.
The point is that you have to really prepare you data set.

There need to match in both the software and you data set:
- account names
- category names
- date format
- currency
- currency rate
- payment method (the trickiest one)

For each on I mentioned there is a specific setting which will give you the appropriate code/name.
The only real complex one is the payment method (look for offline payment methods in the settings)

I imported 10 transactions to test....
- very long
- it keeps loading but it actually completed the task, I had to open a new tab to check

Just in case this helps someone else.... I had an error 200 message on import so exported a couple of transactions manually and then made sure the data values matched in both the export and import files. Turns out I had used the wrong currency code in the import file. It wasn't obvious initially though because the currency displayed in the app was the currency code description, not the actual code.