Hi Tim,

I am curious to know how you resolved this issue. I have a customer who is looking into Pagero and have line level matching needs. Any thoughts are appreciated.

Thanks,

Manasee

I am no longer on the ERP side of things but I still keep in touch with how they are progressing.  I believe they ended up having to create a custom tax code and assign it to the supplier level.  The problem is that some of our suppliers ship to all our sites across multiple states.  

I do know they went away from Pagero PDC to another system as Pagero dropped their email management company.

I will see if there are more details and provide once received.

We’re also using Pagero (and have a similar issue)
The issue is that there is no IFS tax code in the XML sent from Pagero.
You get the Net Amount and the Vat RATE and IFS works out the VAT amount and Gross amount.
So, the only thing you can do is to add a default tax code for ‘standard’ vat and zero rated on the supplier\invoice\tax Information tab (tax code and tax free tax code)

These are then used as a default value for lines that either have a vat rate or are zero rated.

The only problem with this cunning plan is that IFS doesn’t know what to do if the default vat rat eis not applied to an invoice line but some other rate is. You will get a validation error as there is then a mismatch between the calculated vat and the value you would get if you used the standard rate.

So this works for MOST of your invoices and you have to fix the ones that are different.

I agree with this assessment.  Unfortunately, in the US, the tax codes are all over the place not just by state, but also by city, county, etc.  We have no base rate that is even close to one another.  Essentially eliminates our ability to use this as a vast majority of our invoices would fail and need to be fixed anyway.

If this is for IFS Cloud, what version?  I see in 24R1 this flag on external supplier invoice parameters

as well as the ability to input supplier tax defaults

Does this not assist with the issue?  We are using Pagero in Apps9 and have a custom event to recalculate taxes when we get an XML file from Pagero as Apps9 didn’t have functionality for non deductible tax codes.   Hoping this will be resolved by the above in Cloud.

I know that Pagero offer ‘data enrichment’ options to massage the data before it hits IFS, I wonder whether this might be an option to explore?

​@KIMKIMANDREW 

Using custom events (either SQL events or workflows) in conjunction with pagero “data enrichment” could be an option.

We have been using PAGERO as follows with SQL events for more control of setting taxes:

• Have Pagero calculate the taxes (or whatever enhancement you need) and have them populate an unused field in the EXT_INC_INV_HEAD_TAB table. (We use the correction reason field as it otherwise wasn’t being used)
• Have a custom event fire against the invoice tab after it is created. We have created our own procedures which call IFS logic to set taxes. This custom event will read the correction reason field set on the ext_inc_inc_head record, and using the information there will make the required tax updates.
  • This allows you to create your own tax logic, whether by company, country, state, whatever you need. Since this happens after the invoice is created, we can query whatever we need to determine how the taxes should be set. 
  • While we haven’t done this using workflows, it should be equally possible as an enrichment workflow if you prefer that route

This cuts down on the amount of fixes required on invoices after they are brought in. This strategy for enhancing pagero also allows flexibility and agility within your company (presuming you have a developer that can make the required logic changes)

-LEdwards