feat(multi-entities) Invoices services with billing entities #3371
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this service is needed for an smooth migration to multientities allowing single entity organizations to skip the billing entity code in their requests.
also apply some code improvements to the service to improve code expressiveness
as part of the multi entity migrations we assign all existing invoices to the default (and first) billing entity matching the billing_entity_id with the organization_id of the invoices as it is expected the ids are the same...
929cb02 to
30f8c23
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR depends on #3377 that needs to be merged first.
Roadmap Task
👉 https://getlago.canny.io/feature-requests/p/support-billing-from-multiple-entities
Context
Users who invoice the same products across multiple entities face the challenge of managing separate Lago organizations.
This requires duplicating all billable metrics, plans, and setup, while also implementing additional logic to handle two different API keys and ensure the correct one is used for each affiliated entity. This process adds complexity and overhead to their billing operations.
Description
On invoice generation assign customer's billing entity reference.
Also assign all existing Invoices to the organization default billing entity (matching the organization_id). This is needed to later implement and populate the billing_entity_sequential_id for each invoice.