We have historical customer invoices (already paid\settled\closed) that we’d like to get into the CustInvoiceJour and CustInvoiceTrans tables for visibility to our users and reporting purposes. Anything we’ve tried is posting the transaction as open to the customers account. Are there any suggestions for how to do this? We need it in the actual Dynamics tables not a data lake or other such suggestions.
Totally get it—seen this come up a lot. If it’s just for visibility in CustInvoiceJour and CustInvoiceTrans, and you don’t want them open:
- You can use a custom import/X++ script to insert the data directly—just follow the invoice format and test in a sandbox.
- Or post through a journal with custom logic so it’s closed from the start.
Just tag them as historical so they don’t impact aging or reports.
Wouldn’t it be better to import them as is then post journals to mark them as paid and note it as historical for visibility on all aspects rather than just sales numbers?
Thank you. Our consulting firm does not think this is best practice and is discouraging it but we do not understand why. Have you done this in Microsoft Dynamics F&O (cloud) before and if so can you explain how. The data entities exist but don’t allow for it and we’ve tried to replicate the entities and change the read only property but have not had success. We have a programmer in house who is very familiar with doing things like this but is unsure of exactly how we can do this.
Hi Chris,
I completely understand why your partner might not be recommending this as best practice. To your question, have we done this in Microsoft Dynamics F&O (cloud) before? - Yes, we have implemented it, but only for very specific customer needs. Since we knew the flow end-to-end, we were able to manage the impact on the system.
If you’d like, we can go over the details in a quick call—that might be easier to walk through. You can also connect with me directly at hardik.gupta@allgrowtech.com if that works better for you.
Keep Growing.