Hi Evan,
I love your reaction. I would appreciate if you donate your smile to everyone around the world!
With the building logic outsite of AX, I mean that you should try to prevent to build too many integrations so the capture software will replace your complete invoice matching. I will explain in detail:
An invoice contains some header data like, vendor, invoice number, amounts. But it also contains line data. These line details can be really anything:
- Invoicing of received products
- Project (item) expenses
- Various costs not known on purchase orders, like water or electricity.
- Aqcuisition of an asset.
OCR Software can read all the data. Some programs do also have a function for approval and matching.
I think you only need header data and when possible or required only the raw data of the lines. Try to do the matching in AX, or the integration must be already perfect.
When the matching is in the third party software, from AX you have to provide:
- Vendors
- Sales Tax data
- Open purchase orders
- Project data
- Asset data
- Main accounts
- Dimensions
and some more.
The logic how to apply and all valid combinations is in AX. If you e.g. want to provide a valid combination of main account, business unit, department and cost center, this logic needs to be rebuild in the third party software.
Also how to apply the Sales Tax logic? The invoice contains probably only one amount. AX needs to have a Sales Tax Group, Item Sales Tax Group preferrably per line if the combination on one invoice is different.
Then when all information is matched, you overlooked some combinations and the data cannot be processed by AX... This is a common scenario.
From my experience rebuilding this kind of logic in third party applications is insane. I have seen many issues when trying this.
So I would advice to look at getting the data in AX and let AX apply all logic.
If you have some new questions, do not hesitate to ask them here.
