#9354 Incident 51000001074180 : [BC-IN] GST Component code alignment issue in Pay GST Calculation details.
GST Settlement calculation now processes components in the configured Return & Reco Sequence order instead of alphabetically, ensuring correct Credit Utilized and Surplus Credit display in Pay GST Calculation Details.
- 3files
- 3AL files
- 3objects
Pull request · merged into main (BC30) on 2026-07-13 by v-ajaztabrez (community contribution) · 3 files (+6 -1), 3 AL · fix · tier official · reviewed (checked by Opus)
What changed
- Settlement procedures in GST Settlement codeunit now use SetCurrentKey with Sequence No. to iterate in correct order
- GST Payment Buffer Details table adds LineOrder key for consistent display sorting
- Pay GST Calculation Details page sorts by Line No. to show components in configured sequence
- Calculation and posting logic unchanged; only iteration and display order corrected
- Fixes GST component processing for India localization with multiple liability components
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 18318 “GST Settlement”, INGST (IN layer): modified
- Page 18324 “Pay GST Calculation Details”, INGST (IN layer): modified
- Table 18322 “GST Payment Buffer Details”, INGST (IN layer): modified
Context
- Work items: AB#642154
- Labels: ADO: Sync, From Fork
- Systems: finance
- From the description: “Process GST Payment Buffer in Return & Reco Component Sequence No. order instead of clustered GST Component Code order during settlement calculation.”
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).