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

Project Costing and Billing #26268

Open
heyberting opened this issue Jun 30, 2021 · 4 comments
Open

Project Costing and Billing #26268

heyberting opened this issue Jun 30, 2021 · 4 comments

Comments

@heyberting
Copy link

Is your feature request related to a problem? Please describe.
Project Module's Costing and Billing portion does not include costs/expenses logged manually under Journal Entry. It does not reflect the accurate gross margin compared to the Profit and Loss Statement.

Describe the solution you'd like
Total Purchase Cost (via Purchase Invoice) can be modified to Total Purchase Cost (via Purchase Invoice and Journal Entry) and perform adjustment in the calculation to include manual JVs.
The same with Total Sales Amount to include manual JVs.

Describe alternatives you've considered
Make a separate field for Other Costs (via Journal Entry)

Additional context
image

@mujeerhashmi
Copy link
Contributor

Also, include the Total Purchase Amount (via Purchase Orders).
Total Advances (Payment Entries) received from the client for the project.

@heyberting
Copy link
Author

If we add Total Purchase Amount (via Purchase Orders), it might include items that are already booked in the expenses (via Purchase Invoice).
How about only filter those unbilled PO items tagged under the Project?

Also can we also add the total advance payments made for the pending Purchase Orders under the Project. Others might be interested in the information.

@ankush ankush added the to-validate Old issues pending validation label Dec 10, 2021
@ankush ankush removed the to-validate Old issues pending validation label Dec 18, 2021
@stale
Copy link

stale bot commented Feb 19, 2022

This issue has been automatically marked as inactive because it has not had recent activity and it wasn't validated by maintainer team. It will be closed within a week if no further activity occurs.

@stale stale bot added the inactive label Feb 19, 2022
@stale stale bot closed this as completed Feb 26, 2022
@federicocalvo
Copy link

the JV's have the link to the project, but have no implications as this issue states in terms of cost calculations.

Besides it also does not have the linkage on the dashboard.

Although they then comment on the POs, this could be separated in another issue, to validate the JV issue and be able to perform a PR, as it is extremely necessary.

@ankush with three users validating the request (also not very complex to understand in this case) shouldn't it reopen?

@ankush ankush reopened this May 9, 2022
@ankush ankush added the valid label May 9, 2022
@stale stale bot removed the inactive label May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants