DATEV Export module about ledger123-2.8.30 HOT 10 OPEN

Please also add the option to select GIFI account number in DATEV export file.

from ledger123-2.8.30.

I have added GIFI option on the export screen. Code is pushed to github.

This code is in 'develop' branch. The other changes were already done.

Kindly confirm this closes this issue.

from ledger123-2.8.30.

Tested and got the following error message. Any ideas?

Two more things:

a.) When I start the export procedure by clicking 'Export--Prepare DATEV file', first nothing seems to happen and it takes quite a while before anything appears on the screen. Would it be possible to add a screen that appears immediately after clicking 'Export-Prepare DATEV file' which says something like "Preparing DATEV file..."?

b.) Would it be possible to add a feature that immediately prepares the CSV file, so that the user does not need to copy and paste all the data into a spreadsheet?

from ledger123-2.8.30.

Both items done in ledger123/develop branch and code pushed to github.

from ledger123-2.8.30.

Still having some problems with AP transactions with equal amounts in debit and credit. We added the following routine (see above) to eliminate the equal amounts in debit and credit that are usually caused by the use of summary accounts in AP and AR transactions:

a.) When values are equal in amount, check if the account is the same in debit and credit.
b.) If the account is the same in debit and credit, check if there is another equal value in the opposite group that is booked on a different account.
c.) If so, remove these values from the transaction and write them into the "DATEV-Export" file and goto 3.)
d.) If not, remove the values with equal amounts and same account in debit and credit from the transaction and write them into the "DATEV-Export" file, flag "ERROR" in the error column next to this transaction and goto 3.)

In my opinion the following ERROR booking should have been solved with the above routine, or am I missing something here?

a.) There are equal amounts and the accounts are the same in debit and credit.
b.) Since the accounts are the same in debit and credit, the routine should check if there is another equal value in the opposite group that is booked on a different account; and there is -> 4200 and 1220.
c.) So, I think it should then have removed these values from the transaction and written them into the "DATEV-Export" file and gone to 3.)

But for some reason our routine did not work correctly here. Don't you agree?

from ledger123-2.8.30.

And when I try to export to csv format, I get the following error message:

from ledger123-2.8.30.

The csv export error has been fixed.

Can you email me the dataset from which you have shown the above example. I look at that particular example and see how it can fixed.

Regards

from ledger123-2.8.30.

Perfect, thanks.

You will find exactly the same issue as shown above in the dataset on our demo server (app.sql-ledger-network.com).

Check these transactions for example:

Regards
Sebastian

from ledger123-2.8.30.

Hi Sebastian,

In case of all above transactions there is no other transaction with same amount but different accounts so this cannot be used for testing.

Could you just add some transaction to reproduce the error on online server?

Regards

from ledger123-2.8.30.

Hi Armaghan,

I sent you an email giving you access to server and sample database. Did you receive this mail? Were you able to access the server?

Regards

from ledger123-2.8.30.