I am using the ReceiveEinvoiceService.svc to create External Supplier Invoices. My desire is to send all the necessary information (Header, Lines, Taxes, Charges, Purchase Orders) to IFS so that a Posting Proposal / Manual Supplier Invoice can be generated.
Sadly, the endpoints at the ReceiveEinvoiceService.svc only supports sending a limited properties. I have to call the ExternalSupplierInvoiceTaxInformationHandling.svc manually in order to configure the individual Tax Codes on the External Supplier Invoice. Additionally, I have to call ExternalSupplierInvoiceLineInformationHandling.svc to update the Lines with the Purchase Part Description, whether it is a Charge Line or not, and the total tax from the tax detail.
Once I am done configuring the External Supplier Invoice, I have to call the ExternalSupplierInvoicesHandling.svc to check and create endpoints in order for the Posting Proposal / Manual Supplier Invoice to be generated.
My code / flow works fine currently except for 1 problem. The Posting Proposal is not automatically matching invoices with the Purchase Order receipts.
I currently have the following configured in IFS for the ReceiveEinvoiceService.svc endpoints.
Having the Automatic Approval = 'No' allows the ability to call the ExternalSupplierInvoiceTaxInformationHandling.svc and ExternalSupplierInvoiceLineInformationHandling.svc endpoints before the Posting Proposal / Manual Supplier Invoice is generated. I am unable to call these endpoints unless this setting is configured like this.
If I switch Automatic Approval = 'Yes', it will automatically generate the Posting Proposal / Manual Supplier Invoice along with matching invoices with the Purchase Order receipts. But, this does not help me with the other information I need to adjust.
I see an endpoint on PostingProposalHandling.svc called AutomaticallyMatchPoReceipts. I can see that this endpoint is called when I click the 'Automatically Match PO Receipts' on the Posting Proposal IFS page by looking at the network traffic. It works as I would expect it to.
If I try to call PostingProposalHandling.svc with the exact same request I see through the network traffic, it does not do anything and it still returns a success response code. I know it isn't a timing issue because I am able to navigate to the Posting Proposal before even trying to call the endpoint.
Why is calling the API outside the IFS page not working as expected? What should I do so that I can have the 'Automatically Match PO Receipts' be ran without user interaction or have it be placed on a schedule?