[Bug][SubscriptionBilling] Contract lines of type G/L Account never post to the selected G/L account (backport to releases/28.x) - #10091
Open
Miljan Milosavljević (miljance) wants to merge 1 commit into
Conversation
Subscription Billing contract lines of type "G/L Account" always posted to the Customer/Vendor Subscription Contract Account from the General Posting Setup, ignoring the account actually selected on the contract line. - Without deferrals, CustomerDeferralsMngmt/VendorDeferralsMngmt now skip the General Posting Setup account lookup for "G/L Account" lines so the invoice posts directly to the line's account. - With deferrals, a new "G/L Account No." field (27) on Cust./Vend. Sub. Contract Deferral carries the account from the sales/purchase line, and is surfaced on the Customer/Vendor Contract Deferrals pages. - ContractDeferralsRelease now posts to that account when releasing the deferral, falling back to the General Posting Setup account when it is blank, and only requires the General Posting Setup account to be filled when no contract-line account is available. - Added TDD tests to CustomerDeferralsTest and VendorDeferralsTest covering both the immediate-posting and deferral-release paths, with a shared fixture in ContractTestLibrary. Fixes microsoft#9885 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Miljan Milosavljević (miljance)
requested a review
from a team
as a code owner
August 10, 2026 13:16
Miljan Milosavljević (miljance)
temporarily deployed
to
triage
August 10, 2026 13:16 — with
GitHub Actions
Inactive
1 task
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
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.
What & why
Linked work
Fixes #9885
How I validated this
What I tested and the outcome
Risk & compatibility
deferrals now post to the G/L account selected on the line instead of the
Cust./Vend. Subscription Contract Account from General Posting Setup. Anyone
who relied on the old (incorrect) routing will see revenue/cost on different
accounts going forward.
Cust./Vend. Sub. Contract Deferral tables. No breaking changes, no upgrade
code needed: the field is blank on pre-existing deferral rows, and release
falls back to the General Posting Setup account, so existing deferrals
release exactly as before.
General Posting Setup contract account when the deferral carries its own
account — setups with a blank GPS account now succeed where they previously
errored (intended).
propagated automatically.
CreateServiceObjectForGLAccountWithServiceCommitments signature is unchanged.
🤖 Generated with Claude Code