Ability to Limit Invoice Date Range

Business Central/NAV User Forum
1

Hello Experts,

Is there a way to create an acceptable range for invoice dates being entered? We would like to limit the date range for invoice dates the same way we are able to restrict posting dates.

Or is there a way to create validation criteria so that there is a warning if an invoice date is entered outside of a range? For example: if the invoice date is more than one year older than the current work date or more than two months in the future of the current work date, a validation warning would occur.

I appreciate any feedback or guidance you can provide.

2

Hi @MariBeth_Theusch ,
I’m not sure about Invoice Date range restriction without customization but you can restrict posting date via “Sales & Receivable Setup”
Enable Posting Date Check on Posting.

3

Thank you for the response @Sajjad_Yousuf. I should have clarified that we are looking to restrict Purchase Invoice dates. We have an integration outside of BC that posts our Sales Invoices. We are currently restricting the posting dates via General Ledger Setup but we are having issues with users entering Purchase Invoice dates that are either extremely old or several years in the future. That is what we would like to limit - or at least create a validation warning so that the user takes a closer look at the invoice date before posting.

4

Are you posting from API?
You can also restrict it via API then

5

You can do this with customization and use Event Subscriber on Post Invoice and also you can restrict by validate posting date.

6

Thanks again, @Sajjad_Yousuf! I will take these options back to the team to see if they are workable for us.

7

If you need my more assistance, you can DM me.
Thanks

8

Thanks, again, @Sajjad_Yousuf !

9

Hi @MariBeth_Theusch

Have you got this issue sorted? Or is something I can still help.

10

Hi @Hardik_Gupta , I didn’t get this sorted. We don’t use Event Subscriber so I couldn’t find another way to restrict the invoice date ranges that are being posted. Thank you for checking!

11

Hi @MariBeth_Theusch

Got it, thanks for sharing. Just wanted to check, are you planning to handle this internally, or would you be open to some support on it?

If it’s something you’d rather not spend more time digging into, happy to jump on a quick call and see how we can help get a clean solution in place.

12

Hi @Hardik_Gupta,

I hadn’t planned on spending any more time digging into this since there didn’t seem to be a quick solution.