Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8.0 l10n nl tax declaration reporting dev #18

Merged
merged 4 commits into from
Apr 2, 2016
Merged

8.0 l10n nl tax declaration reporting dev #18

merged 4 commits into from
Apr 2, 2016

Conversation

RichDijk
Copy link

The report has been rewritten into a Qweb report in order to make ik easy to maintain.

@oca-clabot
Copy link

Hey @RichDijk, thank you for your Pull Request.

It looks like some users haven't signed our Contributor License Agreement, yet.
You can read and sign our full Contributor License Agreement here: http://odoo-community.org/page/website.cla
Here is a list of the users:

Appreciation of efforts,
OCA CLAbot

@StefanRijnhart
Copy link
Member

Hi @RichDijk, thanks! Please check the Travis CI output. It will give you some comments on style and inconsistancy that you need to follow up. And please register at the OCA with your Github login as a member of the Onestein team (no membership fee required for that).

@RichDijk
Copy link
Author

@StefanRijnhart, Thank you for your feedback. I'ĺl take care for the subscription.

@diellenne
Copy link

Now the module should be ready to be reviewed


i = 0
while i < len(res):
# TODO refactor, e.g. using map or switch case?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use a mapping, indeed. That allows you to raise properly when you encounter an unrecognized code as well.


from . import report
from . import wizard
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vim: lines are optional, and can be better removed in new modules

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually they are completely useless: you should configure your vim to use 4 spaces for all python files, and it probably does already.

I think this should be removed.

@krijn1981
Copy link

Hi,

I just join this team to give some input.
I reviewed the report and works en look fine, give better insight to the numbers.
Functional review 👍

@oca-clabot
Copy link

Hey @RichDijk,
We acknowledge that the following users have signed our Contributor License Agreement:

Appreciation of efforts,
OCA CLAbot

@ploegvde
Copy link
Contributor

I think there is a bug when you make a supplier invoice for importing outside the EU. You pay 21% tax and that tax is returned in the 'voorbelasting'. The result is zero. But on the report you print a negative tax amount in 'rubriek 4a' and then extract the 'voorbelasting'. This leads in a tax return and not a zero result. Can you check?

@RichDijk
Copy link
Author

@erwin,
5b is the total of the 4 section, this is also included in 5a. 5c is 5a minus 5b.
Despite the sign the calculation is correct, and the sign is minus because the tax paid and will be received from the tax authority.

@ploegvde
Copy link
Contributor

Sorry, I think it is not correct. See image.

tax

@krijn1981
Copy link

I think before we doubt to the report. Let's check the settings of the tax at 4a.
There should be a positive VAT amount when the base is also positive.
When we follow the calculation of -21(4a) minus 21 (5b) the outcome is mathematical correct (-42).

Therefore I think the issue is in the Tax definition. could you check that?

@ploegvde
Copy link
Contributor

Tax is the standaard Dutch tax template. Nothing changed to that. I add images onb the invoice adn the standard tax report. In this case the tax total should be zero.
tax2
tax3

@RichDijk
Copy link
Author

@erwin @krijn
I changed the calculation so the net result is 0.

@RichDijk RichDijk closed this Sep 22, 2015
@RichDijk RichDijk reopened this Sep 22, 2015
fy = self.cr.fetchall()
self.cr.execute(
"select id from account_period where fiscalyear_id = %s",
(fy[0][0],))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean to select all periods from the current fiscal year? In that case, you need do make sure you select the right fiscal year (in this case the order seems to be undefined). Also, make the query company aware (or use the ORM to select the fiscal year, which applies standard company filters).

@StefanRijnhart
Copy link
Member

@RichDijk thanks for the updates so far! @erwin-bas-solutions can you confirm that the results are correct now?

@hbrunn
Copy link
Member

hbrunn commented Mar 1, 2016

@RichDijk please rebase

@hbrunn hbrunn added this to the 8.0 milestone Mar 1, 2016
@nielsmiddeldorp
Copy link

Are there still any issues with this? I think it's time to merge 👍

@hbrunn
Copy link
Member

hbrunn commented Mar 9, 2016

there's still a couple of comments by @StefanRijnhart pending

@hbrunn hbrunn merged commit 3913c85 into OCA:8.0 Apr 2, 2016
@astirpe astirpe deleted the 8.0-l10n_nl_tax_declaration_reporting-dev branch April 2, 2016 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.