Dynamics Community Forum Thread Details

How to handle historical standalone Sales Invoices created outside Sales Orders?

Hi Everyone,

I'd like to get some advice on a Business Central scenario involving historical transactions.

We have a customer who, for several years, has followed this process:

Create a Sales Order.
Sometimes partially or fully ship the order.
Instead of creating the invoice from the Sales Order, they create a separate Sales Invoice manually.
The Sales Invoice is posted and the customer payment is received and applied to that invoice.
The standalone Sales Invoice is not linked to the Sales Order and usually only shares the same Project Dimension.

As a result, we now have many historical cases where:

Sales Orders remain open or partially invoiced in the standard Business Central document flow.
Separate posted Sales Invoices have already been fully paid.
The accounting entries are correct, but there is no standard relationship between the Sales Order and the standalone Sales Invoice.

The challenge becomes even more complicated when a single project contains multiple Sales Orders and multiple standalone Sales Invoices, with only the Project Dimension available as a common reference.

A few questions:

Have you encountered this type of historical process?
Is there any standard Business Central approach for associating standalone posted Sales Invoices with the related Sales Orders for reporting purposes?
Since posted Sales Invoices cannot be retrospectively linked to Sales Orders, what would you consider the best practice for handling this historical data?
If a project has multiple Sales Orders and standalone invoices only contain the project reference, how would you determine which invoice belongs to which Sales Order?
Would you leave the historical transactions as they are and maintain a separate mapping for reporting, or would you recommend another approach?
Would you leave the historical documents unchanged and implement a custom reporting/mapping solution, or is there a standard approach that we may have overlooked?

We're mainly interested in understanding how others have handled similar legacy scenarios and what is considered best practice in Business Central.

Thanks for any suggestions or experiences.

Categories:

Dynamics 365 Business Central

Dynamics 365 Business Central migration

Microsoft Dynamics NAV

Hello,

Yes, this happens in legacy clean-up projects, but there is no standard way to retroactively “attach” a manually posted standalone Sales Invoice to an old Sales Order as if it was invoiced through the normal order flow. Since the invoices are already posted and paid, I would not try to change the historical accounting flow unless there is a real accounting correction needed; I would keep the posted documents as they are, close/clean up the remaining open Sales Orders carefully based on business approval, and build a separate mapping/reporting table where users can link Sales Order No. ↔ Posted Sales Invoice No. for reporting only. If the only common value is Project Dimension, then BC cannot reliably know which invoice belongs to which order when there are multiple orders/invoices under the same project, so that matching must be manual or based on agreed business rules like customer, dates, amounts, item/resource lines, shipment no., external reference, etc. Going forward, the best practice is to invoice from the Sales Order itself so BC keeps the order/shipment/invoice relationship properly.

Regards,
Oussama Sabbouh

Quick Links

Leaderboard > Small and medium business | Business Central, NAV, RMS