We are raising invoices from projects module or from AR module and want to be able to make the customer order field mandatory.
In payables there is a data entry setting to require a supplier reference but doesn’t seem to be any equivalent for a customer reference (PO number).
It would also be great if we could also amend the customer reference number for corrections after the invoice has been released without having to reverse and re-raise.
Sorry rookie question!
Best answer by Steve Milner
There's no AR equivalent, you're reading it right. AR Preferences only offers Require Payment Reference on Entry, and that applies to Payments and Applications (AR302000) and Cash Sales (AR304000), not to invoices.
The only Require Customer Order Nbr. setting Acumatica ships sits on Order Types (SO201000), so it covers sales orders and never reaches an invoice you raise in AR or from project billing.
You can enforce it with a small customization, no code needed. In the Customization Project Editor, add a condition on the Conditions page (Type Equals Invoice, so credit memos don't get blocked), then on the Fields page set that condition as the Required property of the Customer Order Nbr. field (ARInvoice.InvoiceNbr). Do it at screen level. At DAC level it applies anywhere ARInvoice is used, including invoices generated by project billing and anything arriving through import scenarios or the API, and those will start failing to save.
If you bill through pro formas, PM307000 has its own Customer Order Nbr. box, so capture it there before you release.
On amending after release, there's no stock way. Once an invoice is released the only editable fields are the cash discount date and due date while it's open, so a credit memo is the only route today without further customization.
+4There's no AR equivalent, you're reading it right. AR Preferences only offers Require Payment Reference on Entry, and that applies to Payments and Applications (AR302000) and Cash Sales (AR304000), not to invoices.
The only Require Customer Order Nbr. setting Acumatica ships sits on Order Types (SO201000), so it covers sales orders and never reaches an invoice you raise in AR or from project billing.
You can enforce it with a small customization, no code needed. In the Customization Project Editor, add a condition on the Conditions page (Type Equals Invoice, so credit memos don't get blocked), then on the Fields page set that condition as the Required property of the Customer Order Nbr. field (ARInvoice.InvoiceNbr). Do it at screen level. At DAC level it applies anywhere ARInvoice is used, including invoices generated by project billing and anything arriving through import scenarios or the API, and those will start failing to save.
If you bill through pro formas, PM307000 has its own Customer Order Nbr. box, so capture it there before you release.
On amending after release, there's no stock way. Once an invoice is released the only editable fields are the cash discount date and due date while it's open, so a credit memo is the only route today without further customization.
Hi
You are correct that while the AP module has a built-in "Require Vendor Ref." setting, the AR and Projects modules do not have an exact equivalent checkbox for the Customer Order Nbr out of the box.
Depending on how you generate your invoices, here is how you handle it:
CustomerOrderNbr field to "Required" for the AR Invoice screen. Alternatively, a quick DAC (Data Access Class) extension can append a [PXDefault] attribute to the field to force a value before saving.In standard Acumatica, you cannot edit the Customer Order Nbr (or most other fields) once an invoice is released.
Hope above helps!!
+20
If invoices are being generated from the Projects module, I would recommend validating the customer reference when the AR invoice is created/released, so the requirement is enforced regardless of where the invoice originates.
Regarding corrections after release, the standard behavior generally doesn't allow the customer reference to be freely changed on a released AR invoice. If the requirement is only to correct the PO/customer reference without affecting the financial transaction, this could potentially be handled through a customization, depending on the specific field and business requirements.
I’d first check whether the Customer Order field is required at the time of invoice creation in your version, and if not, a small customization should be able to enforce it.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.