Batch payment API by InvoiceNumber instead of InvoiceID
Thanks for the current batch payment API. it works with InvoiceID.
Can you please update this API by allowing to use the InvoiceNumber instead of InvoiceID.
The InvoiceNumber is much more user-friendly and actually used by accountants instead of the long ID, that needs an extra lookup.
Can you please let us know when can you update it?
For example:
<Payments>
<Payment>
<Invoice>
<InvoiceNumber>ORC1039</InvoiceNumber>
</Invoice>
<Reference>ggg</Reference>
<Amount>10.00</Amount>
</Payment>
Anonymous
shared this idea
-
David_Miller
commented
This is a thoughtful approach to improving batch payment workflows, especially when invoice numbers are more practical for reconciliation. I’ve seen similar discussions where aligning reference logic helps reduce processing friction and errors across systems. Resources like https://monmouthcountycourts.org offer useful insight into how structured records and identifiers are handled at scale. Overall, this kind of API flexibility can significantly improve operational efficiency when dealing with high-volume transactions.
-
Anonymous
commented
I have received the validation error while tried with InvoiceNumber:
<ErrorNumber>10</ErrorNumber>
<Type>ValidationException</Type>
<Message>A validation exception occurred</Message>
<Elements>
<DataContractBase xsi:type="BatchPayment">
<ValidationErrors>
<ValidationError>
<Message>You must specify the invoice id</Message>
</ValidationError>
</ValidationErrors>