EDI TXI Segment Processing

 1 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
Matt_B
Advanced Member
Posts: 22
Advanced Member

    Hey all, 

     

    We're having issues with vendors that are sending taxes in the 810 TXI segments instead of the SAC02 segments where Lawson is not picking up that value and we're getting the a message from MA126 of "Tax out of balance".  The only documentation I could find on this is in the Cloudsuit documentation which theoretically should work on Version 10 based on KB Article 1449847, this functionality was introduced in version 9 back in 2013. 


    This table shows the generic entry for mapping TXI segment to AOC.

    Field Value Comments/Examples
    List name L1_TAX_TO_AOC
    Your value AOC CODE
    External value tax type code in TXI01

    So this is what we have in our Substitution Table: The assumption is all vendors that have a value of "ST" in the TXI01 field should process that as an addon cost. 

    List name- L1_TAX_TO_AOC

    Your value- ST

    External value- ST


    We do have the AOC code setup in MA08.1 as "State Tax"


    Here is part of the 810 transaction where based on the documentation, should process this tax as an AOC. At least that's how I understand it. 

    IT1*1*1*PK*88.16*PE*VC*SCWP02500*IN*892077*VP*SCWP02500|

    PID*F****FILTER 25MM SCWP 100/PK|

    TDS*9479|

    TXI*ST*6.63|

    CTT*1| 

     

    Is there anything that I'm missing that is preventing Lawson from applying these segments and throwing the invoices out of balance? 


    Matt_B
    Advanced Member
    Posts: 22
    Advanced Member
      Whooops wrong forum section, meant to go to SCM