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

Feat(revshare): self billed invoices numbering #3078

Merged
merged 14 commits into from
Jan 22, 2025

Conversation

annvelents
Copy link
Contributor

Roadmap Task

👉 https://getlago.canny.io/feature-requests/p/calculate-revenue-share

Context

Self-billed invoices should be numbered by customer and should not affect rest of the invoices generated for the organization

Description

Modified rules for numbering to not include self-billed invoices when calculating sequential id
Always use customer numbering for self-billed invoices
Added self-billed invoice scenario test

annvelents and others added 13 commits January 20, 2025 15:39
also add tests for customer creation with account type partner
- remove filter customers by account type
- fix linter issues
- do not allow to update customer account type if customer is not
editable
- fix tests
## Roadmap Task

👉  https://getlago.canny.io/feature-requests/p/{{FEATURE_SLUG}}

## Context

Include relevant motivation and context.

## Description

Describe your changes in detail.

List any dependencies that are required.
Copy link
Contributor

@ancorcruz ancorcruz left a comment

Choose a reason for hiding this comment

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

cool stuff, thanks.

@ancorcruz
Copy link
Contributor

:shipit:

@annvelents annvelents merged commit 65f187d into main Jan 22, 2025
6 checks passed
@annvelents annvelents deleted the feat/revshare-self-billed-invoices-numbering branch January 22, 2025 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants