API Endpoint InvoiceDetails: alternate item descriptions are missing
- Description of the issue: The invoiceDetails are missing the item alternate descriptions, which they need for international invoice recipients.
- Account name: Mcon
- Region: EMEA
- Client version: 26.2
-
Steps to reproduce:
- Go to https://supportwebemea.ungerboeck.com/mcon_prod/api/help/index
- Expand InvoiceDetails from the list and select GET /api/v1/InvoiceDetails/{OrgCode}
- In the Code paragraph select “Model”
- Expand Array of InvoiceDetailsModel
- Expand InvoiceDetailsModel
- See that the alternative descriptions are not featured in the Model list:
- Observed results vs Expected results: The alternate descriptions should be featured, so that international invoices can be properly issued.
- What is the job the client is trying to accomplish: They want to issue invoices addressed to international recipients featuring the proper language.
- Business impact if not resolved: Big impact - As of January 1st 2027 they have to create electronic invoices by law, where they need the invoice items in English language for our international customers.
- Links to articles where you've looked for solutions and also other steps you've taken to research the issue:
https://supportcenter.ungerboeck.com/hc/en-us/articles/115004480314-Explore-the-API
https://connect-emea.gomomentus.com/api-documentation#overview--introduction - Link to Zendesk ticket: https://ungerboeck.zendesk.com/agent/tickets/363129
- Local v30 URL: https://supportwebemea.ungerboeck.com/mcon_prod/app85.cshtml?ReturnUrl=%2fmcon_prod
Pieter Fourie Mike Schepker Nicole Loh Satya Ram Nukala
-
Seth Halvaksz The alternate descriptions are not endpoints that can be used, and As of January 1st 2027 they have to create electronic invoices by law, where they need the invoice items in English language for our international customers.
Will those endpoints be added? do we need an enhancement request? -
Yes this will be an enhancement request if the endpoints do not exist.
Are they using our new e-invoices product? If so i'll ask Lori to review this.
-
I will check with AM if they will be using the new e-invoice
-
The customer will not be using the e-Invoice
-
Please reach out to Lori anyway, since she owns e-invoicing. This sounds like a one-off request, and not the standard behavior we want to promote.
And please submit an enhancement request.
-
Josiane Mikhael Thanks so much for flagging this, and for checking in with the AM already!
My suggestion would be to go ahead and create the enhancement request like Seth mentioned. I'd frame it as a general Connect API prioritization item rather than an e-Invoicing one, since it's really about the InvoiceDetails model overall.
That said, I'm curious about something. I know m:con isn't using E-Invoicing today, but when I looked in Gong, it doesn't look like it was ever really discussed with them. Would you be able to check with the AM whether E-Invoicing was pitched to m:con, and if so, why it didn't meet their needs? The API enhancement may not be a near-term add, so I want to make sure we're exploring every route with the customer, including whether E-Invoicing itself might actually solve what they're after. Thanks!
Please sign in to leave a comment.
Comments
6 comments
Date Votes