Settlement document - multiple tax codes

[JanSAP1]

Hi Guys, 

I need help with some standard logic. We have an italien rebate document (credit memo) which has 2 tax conditions included (via external tool determined) - this all works perfectly fine. We have two tax conditions which determines correct tax codes wihtin the condition. 

But on WBRP-MWSK2 only the last determined is saved and only one tax code is transferd to accounting which is wrong! I´m not 100% sure if this would work as per standard or if our consulting company has played around to much in transfer manager and messed things up. Any helpful input on how it should work as per standard or what to look out for in transfer manager?! Any help highly appriciated!

[GauthierVictor]

Hi @JanSAP1 ,

Thanks for providing the background on your issue. Based on your description, here are a few points you should check:

1. Transfer Manager Configuration

You can review the Transfer Manager setup by navigating to:
WLFA > Settlement Management > Settlement Documents > Specify Settings for Transfer Manager > Assign Transfer Groups to Settlement Document Type.
Select your Settlement Document Type and review all assigned rules to understand how field values are transferred during settlement.
Misconfigurations or customizations here could cause only one tax code (the last one) to be transferred incorrectly.

1. External Tax System and MWST Condition Type

Even if your external tax tool is determining tax conditions correctly, ensure that the MWST condition type in your pricing procedure is properly populated.

• I believe in your case, the MWST condition should carry the tax code that Settlement Management will pick up and transfer to the settlement document line item.
• Often a custom pricing routine is needed in the pricing procedure to support tax logic from external systems and ensure the correct mapping into MWST.

1. Pricing Procedure Review

Double-check your pricing procedure to ensure that multiple tax conditions are handled appropriately and that the MWST condition is filled correctly at the end of pricing.
If MWST is not correctly populated, the system will not know which tax code to transfer reliably, leading to inconsistencies.

It’s difficult to diagnose the exact root cause without direct system access, but focusing on Transfer Manager settings, pricing procedure, and MWST determination should help you narrow it down.

Let me know if you'd like more guidance on where to focus your troubleshooting!

Best regards,
Gauthier Victor

[JanSAP1]

Hi Gauthier,

thx for your comments. I think from all of your points only transfer manager could cause this behavior.

Do you have any sepcial transfer group in mind? I cant find anything in our config that manipulates the MWKS2 (WBRP)

And how would the logic actually be if we have two tax codes? Would the MWSK2 field be empty? I tried to forcfully clear the MWSK2 field with transfer manager by transfering a "fixed value" but when I put "0" it makes the tax code actually "0" and system gives a tax error.

Any additional infos you might have to share here?

Many thx!

BR Jan