You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been evaluating the Commerce B2B invoice list page and also using the same methods via Headless CSU. In both cases when payments are submitted using the PayInvoices method the HQ payment journal is created and posted without capturing the Payment reference or any detail in CreditCardAuthTrans or anywhere in the HQ Retail tables.
The initial response from MS acknowledged this was a bug and resolved this stating that it was now in the payload but that "The partners can use this information to update the customer payment journal as needed."
I'm not sure why partners need to complete the journey here and not Microsoft - which we've raised with them - but in the meantime has anyone got any experience of this or guidance as to exactly what one would expect to be populated to record this detail in HQ.
From a standard perspective I can't see how this works with any expectation of Omnichannel processing or being able to manage audit / reconciliation / refund processes...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We have been evaluating the Commerce B2B invoice list page and also using the same methods via Headless CSU. In both cases when payments are submitted using the PayInvoices method the HQ payment journal is created and posted without capturing the Payment reference or any detail in CreditCardAuthTrans or anywhere in the HQ Retail tables.
The initial response from MS acknowledged this was a bug and resolved this stating that it was now in the payload but that "The partners can use this information to update the customer payment journal as needed."
https://fix.lcs.dynamics.com/Issue/Details?bugId=970771&dbType=3&qc=145a5390ad8565d8af114e3e50f2cc78e58976a491e908dd677350e8368b0505
I'm not sure why partners need to complete the journey here and not Microsoft - which we've raised with them - but in the meantime has anyone got any experience of this or guidance as to exactly what one would expect to be populated to record this detail in HQ.
From a standard perspective I can't see how this works with any expectation of Omnichannel processing or being able to manage audit / reconciliation / refund processes...
Beta Was this translation helpful? Give feedback.
All reactions