Repository navigation
[29.X]-[CH] SEPA XML Files should append the Address 1 + '' + Address 2 fields under <PstlAdr><StrtNm> node if we use "Address 2" as Building Number for QR-Bills - #13301
Fixes4BC (neeleshsinghal) wants to merge 2 commits into
Conversation
Good Sense Reviewer - Round 1Recommendation: Accept with SuggestionsWhat this PR doesThis change appends Address 2 to the recipient street for Swiss payment exports when it contains the building number. The helper also handles either address field being blank and limits the combined value to 70 characters. The reported vendor case is fixed, and both Swiss SEPA credit-transfer formats have direct buffer tests. However, the shared recipient methods also change other CH payment formats, and the current payment-export suites show that broader effect. Problem-solution fitFit: Partial The change produces the requested street and building number for Swiss SEPA exports. Its shared placement also changes non-SEPA receiver addresses, so that extra behavior needs to be confirmed or limited. SuggestionsS1 (🟠 Moderate): Resolve the non-SEPA export impact S2 (🟠 Moderate): Cover the 70-character address boundary Risk assessment and necessityRisk: The shared table methods feed several CH payment formats and four recipient account types. The concatenation is simple, but it currently changes AMC Banking output and leaves those payment-export suites failing; the 70-character boundary is also not covered. Necessity: The change is needed because Swiss QR-Bill data stores the building number in Address 2, and omitting it creates an incomplete creditor street in the SEPA file. The production change should stay limited to formats where the combined street is intended.
|
Good Sense Reviewer - Round 2Recommendation: Accept with SuggestionsWhat this PR doesAppends Address 2 to the creditor street for Swiss SEPA credit transfers, with a space between nonempty fields and a 70-character limit. The only own-new change in round 2 adds a SwissExport guard so other export formats keep the original address-only behavior. The new SwissExport guard restores Address-only output for other export formats while preserving concatenation in both Swiss credit-transfer formats. The export buffer sets the flag before choosing the recipient, and both XMLports consume the resulting Recipient Address. Existing tests cover short combined values and blank Address 2; S2's 70-character boundary case is still missing. Problem-solution fitFit: Strong The reported building-number omission is corrected for both Swiss credit-transfer formats, and the follow-up change confines concatenation to the intended export path. The remaining 70-character boundary coverage request is non-blocking. Status of previous suggestions
New observations (commits since round 1)None - no new issues found in the changes since the previous round. Risk assessment and necessityRisk: The helper is shared by several recipient types, but concatenation is now limited to explicitly enabled Swiss exports. Amounts, posting logic, stored schema, and public signatures are unchanged. The remaining non-blocking gap is regression coverage of the truncation boundary. Necessity: Swiss payment exports need the building number when it is stored separately in Address 2. Without the concatenation, the creditor street is incomplete; the guard is needed to avoid changing other formats while fixing that scenario.
|
Fixes AB#656863