Consolidated AR Invoice not editable

Kinetic ERP
1

Hi There,

We cannot save any changes to AR Invoice created from Get > Milestone Billing process for a Customer having Consolidate Milestone Billings option active.

This process results in a consolidated AR Invoice of type ‘Advanced Billing’ having Sales Order Number = zero, thus any attempt to change to the invoice results in the following error:

Business Layer Exception
Sales Order is required.
Error Detail
============
Correlation ID: 2e171bcb-7388-438f-a32c-39563254bfe6
Description: Sales Order is required.
Program: Erp.Services.BO.ARInvoice.dll
Method: InvcHeadBeforeUpdate
Table: InvcHead
Field: OrderNum

image
image1715×880 168 KB

Is this normal behavior or a bug?

TIA,
Josh

2

I see that the invoice type is Advance Billing… They require a SO number, that’s probably why it is causing and error. You may need to check the billing setup on the related project…

3

Thanks for your reply. We are using the Consolidate Milestone Billing feature. The resulting invoices seem to have a zero when you bill for multiple milestones.

image
image1711×773 57 KB

I’m thinking it’s a bug. Anybody using this feature successfully?

2 Likes
4

Josh, did you ever figure this out? We aren’t using milestone billing, just consolidated billing and this error is popping up.

5

This was a bug fixed in a fall '25 release. so 25.2 I believe.

6

Do you have a case for this or PRB?

7

Case CS0005048025 Closed - Sales Order is required error on Consolidated Milestone Billing
Customer Visible Notes:

2025-08-21 07:05:54 PDT - REDACTED Customer Visible Notes(comments)

This case is connected to an Open Problem PRB0293914 All further updates will be provided on problem PRB0293914

2025-08-19 06:49:32 PDT - REDACTED Customer Visible Notes(comments)

Hi Josh, good morning.

I’m following up with the case. Just to review if you have any additional questions regarding the solution of the issue which will be fixed in 2025.1.12, these are the release dates for the environments:

Release Date:
Between 9-10 Sept 2025 Pilot Environment for version 2025.1.12
Between 13-14 Sept 2025 Production Environment for version 2025.1.12

Once the environment is updated to this version, the issue should be fixed.

Best regards