Does anyone else integrate with Tipalti? If so, what has been your situation/solution regarding their Invoice Dates? It's been a bit of a nightmare for us, with having to create custom date fields and swapping dates and lots of manual intervention on bills that we'd just like to avoid. TIA To expand on my definition of the challenge, in case it's unclear: a bill comes into their system today with an invoice date of 8/31. When they push that to NS, it goes into the trandate field, as they have told us that they can only map native-to-native and custom-to-custom fields. Problem is, that would put it in the August period, which we don't want. They have also told us that the Due Date can't be earlier than the Invoice Date, so we couldn't input 11/8 as the Invoice Date and 9/30 as the Due Date. That has led to lots of custom fields and workarounds that seem to be causing more harm than good.

Not sure there's a way outside of custom fields. We've been looking into a lot of AP automation systems as well and haven't found any that would actually overcome this outside of custom fields

Well, that's a NS setting that can be overcome. But moreover, we don't want the transaction date to be different from the period even if the NS settting is set to allow, since that means your GL and aging are different.

Script something to match the period if there is a mismatch?

Just put your settings to Allow for the mismatch. These things are not a big deal. Also aging reports can be run by period rather that date which kills the other issue