Sales Tax for Batched Invoices

SUGGESTED

We have orders importing from our eCommerce platform through ROI's Insynch.  Most of these orders have individual addresses that the customer types in, so we do not have these address saved in Sage or on their web stores.  In turn we do not have "shiptocodes" on most of the orders.  When we go to batch invoice orders the sales tax defaults to the "sold to" address and is greyed out in the SO Invoice data entry screen.  I read about someone trying to script an override ten years ago, I hoping there is an easy way by now.  I don't know how we would assign "shiptocodes" to all the addresses that are being imported.

  • 0

    What matters most is the TaxSchedule (and TaxClass on line data), not the ShipToCode.  I've done scripts to set TaxSchedule for Canadian clients, with sales taxes being much less complex up here... but I understand things are significantly more complicated in the US for understanding sales tax. 

    If you have solid logic to properly determine the schedule to use, a PreTotals script to SetValue on TaxSchedule might work.

  • 0 in reply to Kevin M

    Yes, I was referring to the greyed out area as the TaxSchedule, the schedule is pulling the soldto address when no shiptocode is populated.  All our line data has the correct taxclass.  Could a script allow the user to pull up the "Sales Tax Schedule" list and let them manually change the code?  I could base the logic on if the "shiptocode" = "" ? 

  • 0 in reply to jland47

    Do Sales Taxes work normally (separate from the imports)?  (Sales Tax enabled in AR Options)?

    Do you have Avalara (sales tax calculation enhancement) installed?

  • 0 in reply to Kevin M

    Oh, and scripts normally automate things that you could do manually.  If you are not able to change Tax Schedule normally, focus on why.  I've never seen TaxSchedule disabled for invoices before, and have no idea why that might be happening for you.

  • 0 in reply to Kevin M

    Yes, sales tax normally works and we have that check box checked off.  We do not have any sales tax enhancements installed, every tax code/schedule has been entered manually.  I took these screen shots to show the Taxschedule being disable when batch invoicing orders and another screen shot showing the tax schedule pulling the "ShipTo" Taxschedule.

    soinv.pdf

    See the tax schedule pulls from the shipto customer maintenance when there is a shiptocode.

    soinv1.pdf

  • 0 in reply to jland47
    SUGGESTED

    Click the Payment tab.  The only thing I can think of is that a CC transaction might be locking fields related to $'s after processing.

    The only other suggestion I'd have would be to enter a similar transaction manually, Accept (do not post) then compare the raw table data in SO_InvoiceHeader, looking for any significant differences.

    Or just call ROI to ask for their advice.

  • 0 in reply to Kevin M

    I went in the DFDM for the SO_InvoiceHeader on one of the batched invoices.  The only field I noticed different was the "131 MultipleSalesOrdersApplied131 MultipleSalesOrdersApplied$.... [Y]$.... [Y]" , for testing purposes I edited this field which was a read only.  Once the field was changed to "N" I was able to change the "TaxSchedule" to the correct value.  It looks like by changing MultipleSalesOrdersApplied=N allows us to do what we need.  So, my question is can I change a read only field in a script and is there any other issues that might come up.  I checked my crystal report and all the field are still coming over correctly.

    I did put in a ticket with ROI, but I'd rather figure it out on my own.

  • 0 in reply to Kevin M

    Created a script on a Pre-totals event and everything works, referred to ShipToCode because all orders importing will have a blank value, even if it is not an imported order the user usually manually checks the Tax Schedule to make sure the right tax is charge.  I am thinking it should be ok even though I had to use SetValueNoValidate.  The only thing I can see that the MultipleSalesOrdersApplied field affects is the displaying of certain fields on the lines tab of the SO Invoice data entry panel.  This doesn't affect the fields available in the crystal report to create our invoice form.  Script below.

    'initialize variables
    
    retVal = 0
    sShipTo = ""
    
    retVal = oBusObj.GetValue("ShipToCode", sShipTo)
    
    if sShipTo = "" then
    
    	retVal = oBusObj.SetValueNoValidate("MultipleSalesOrdersApplied$", "N")
    
    end if

  • 0 in reply to jland47

    Be very very very careful with changes to field data like that.  Sage programmed those fields with such limitations for a reason.  If you are not invoicing more than one SO in the invoice, ask ROI to change their import to not set that flag.

    (You may be able to print OK, but the posted data may be corrupted).