Hi,
One of our client has a third-party integration with Salesforce which connects through our own middleware tool, which pushes Invoices from Salesforce into MYOB Acumatica and creates the corresponding Invoices.
However, despite Numbering Sequences being specified in Accounts Receivable Preferences, how was the integration able to create an Invoice and a Credit Memo with the same Ref. Nbr.?
Any idea how can this happen?
Thanks!
Best answer by KrunalDoshi
Hi
I am not familiar with MYOB Acumatica. The first thing I would investigate is how your middleware creates the AR document, rather than the Numbering Sequence configuration itself.
In a normal Acumatica transaction, the Invoice and Credit Memo can have different document types but their RefNbr is still controlled by the AR numbering-sequence setup.
This is particularly important because DocType is part of the AR document primary key, so an Invoice and Credit Memo are not simply the same record because they have the same displayed reference number.
Also check whether the numbering sequences are configured to use prefixes. As you have indicated from your screenshot that both document types uses the same numbering sequence, then having the same numeric portion isn't necessarily evidence of corruption, although Acumatica's sequence mechanism should normally advance the number rather than reuse it.
Hope this helps you to find the cause of an issue.
+13I’m not as familiar with MYOB, but in standard Acumatica, I have seen this occur. Because Invoice and Credit Memo are two different document types, it is possible to have an Invoice and Credit Memo with the same reference number. The only time I’ve seen this occur (and this appears to be default behaviour from Acumatica) is when a user opens an invoice and uses the “reverse” or “reverse and apply” option. Something in how the system copies the original document to create the reversing document keeps the original document number.
ARInvoice also has a composite key, DocType & RefNbr, so this won’t cause any system issues.
+9Hi
I am not familiar with MYOB Acumatica. The first thing I would investigate is how your middleware creates the AR document, rather than the Numbering Sequence configuration itself.
In a normal Acumatica transaction, the Invoice and Credit Memo can have different document types but their RefNbr is still controlled by the AR numbering-sequence setup.
This is particularly important because DocType is part of the AR document primary key, so an Invoice and Credit Memo are not simply the same record because they have the same displayed reference number.
Also check whether the numbering sequences are configured to use prefixes. As you have indicated from your screenshot that both document types uses the same numbering sequence, then having the same numeric portion isn't necessarily evidence of corruption, although Acumatica's sequence mechanism should normally advance the number rather than reuse it.
Hope this helps you to find the cause of an issue.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
