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

Importing invoices doesn't allow to import amounts or rows #368

Open
bmalynovytch opened this issue Apr 19, 2022 · 3 comments
Open

Importing invoices doesn't allow to import amounts or rows #368

bmalynovytch opened this issue Apr 19, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@bmalynovytch
Copy link

When importing invoices history, the import tool doesn't allow to import rows or amounts, leaving all the imported invoices at 0, which is of no interest.

@genglert
Copy link
Contributor

We can imagine several solutions:

  • allowing 1 column (in the CSV file) with the total amount, & the import engine creates one product line which corresponds to this amount (but why a product and not a service? Is an automatic name for the product useful ? [easy to implement]
  • allowing N columns to describe one product line (for N fields: name, amount, VAT...), and M columns for one service line. So an imported Invoice could have 1 product line & 1 service line, the amount being automatically computed as usual [moderate amount of work].
  • allowing to import several product/service lines from a row in the CSV file. It means that you configure the columns N product/service lines where N in the maximum number of lines in your Invoices [several days of work].
  • allowing to import product/service lines separately (ie: from their own list-view) ; it means your must link each line to the related Invoice with a unique field (invoice numbers, names if their are unique etc...) [easier than the previous solution].

What would be the solutions which correspond to your use case ? (I don't mean we will implement it, but it's interesting to collect users' needs to take our decisions)

@bmalynovytch
Copy link
Author

Hi @genglert !

Importing invoices covers two different goals IMHO, each of them being treated differently:

  • populating history for statistics (partial migration of the invoices)
  • having an exhaustive history (complete migration of the invoices)

In the first case, just having a placeholder service that holds the total amounts would be fine, which can be done using your proposal #1.

In the second case, I guess best would be to import all the lines separately (proposal #4) : first you import your invoices with the main informations, then you add your lines individually, hoping 🙏 that the total amounts match the orignal ones.

I don't think that #2 and #3 are flexible enough to cover most needs.

@genglert
Copy link
Contributor

Thanks for your return ; I'll try to discuss about it with my teammates in our next meeting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants