{"id":22231,"date":"2021-04-14T12:28:14","date_gmt":"2021-04-14T12:28:14","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/sagex3\/?p=22231"},"modified":"2021-04-14T12:28:17","modified_gmt":"2021-04-14T12:28:17","slug":"how-to-solve-error-outside-of-validity-date-limit-in-journal-entries","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2021\/04\/14\/how-to-solve-error-outside-of-validity-date-limit-in-journal-entries\/","title":{"rendered":"How to Solve error \u201dOutside of validity date limit\u201d in Journal Entries"},"content":{"rendered":"\n<p>In Sage X3, any transaction that impacts a company\u2019s profit and loss needs to be recorded in their accounting system is called &#8216;Journal Entries&#8217;.<\/p>\n\n\n\n<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A journal entry is used to record a business transaction in the accounting records of a business. A journal entry is usually recorded in the general ledger; alternatively, it may be recorded in a subsidiary ledger that is then summarized and rolled forward into the general ledger.<\/p>\n\n\n\n<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In Sage X3, all documents such as Purchase Invoice, Sales Invoice, Shipment, etc. are coded to \u2018automatic journals\u2019, thus creating journal entries automatically when the documents are validated. Each document is coded to specific accounts in the \u2018automatic journal\u2019 setup, thereby posting the entries in the desired accounts during a transaction. However, these entries are posted in the \u2018temporary\u2019 mode which allows the user to modify the entry in terms of accounts, business partner, amount and description fields, before it is changed to \u2018final\u2019 during final validation.<\/p>\n\n\n\n<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When the status is Temporary, journals can be deleted or modified, but journals generated in other modules are subject to consistency checks. Once the status is Final, some accounting elements included in a journal can no longer be modified.<\/p>\n\n\n\n<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Depending on the setup of the transaction and journal type used, the following elements can be specified in journal entry:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Purely analytical journals<\/li><li>General and analytical journals<\/li><li>IAS documents, etc.<\/li><\/ul>\n\n\n\n<p><strong><u>STEPS <\/u><\/strong><strong><u>:-<\/u><\/strong><strong><u><\/u><\/strong><\/p>\n\n\n\n<p><em>Navigate to: &nbsp;Financials -&gt; Journals -&gt; Journal Entry<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Open the Journal Entry screen from Financials &gt; Journals &gt; Journal Entry<\/li><li>Click the New button to open a blank entry<\/li><li>Select a Site (defined as a financial site)<\/li><li>Select an Entry Type from the list according to the nature of the transaction. Each type is loaded with its required settings.<\/li><li>The Number field will be automatically generated by X3 when the document is created.<\/li><li>Select the accounting Date of posting this entry.<\/li><\/ul>\n\n\n\n<p>&nbsp; Here, we can see that we are facing the below issue while creating journal entry. Refer the below figure:<\/p>\n\n\n\n\n\n<p>Follow the steps given below to solve this error:-<\/p>\n\n\n\n<p><em>&nbsp;Navigate To: All -&gt; Setup -&gt; Financial&nbsp; -&gt; Journal Entry Transaction<\/em><\/p>\n\n\n\n<p> As we are creating journal entry for STDCO transaction, Select the same transaction in entry transaction screen.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><imgtarget=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2021\/04\/Journal-entry-screen.png\" alt=\"\"\/><figcaption><strong>Fig02: Journal Entry Transaction Screen<\/strong><\/figcaption><\/figure>\n\n\n\n<p>Here, we can see that the value in the field Validity End date is set to &#8217;04\/12\/20&#8242;,&nbsp; that means the validity of this transaction is valid only till 2020, but we are creating the transaction for 2021 so we are facing the error. Refer the below figure.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<\/p>\n\n\n\n<p>We need to change the &#8216;<strong>Validity end date<\/strong>&#8216;, till which date we want for the particular entry transaction of the Journal Entry.<\/p>\n\n\n\n<p>So here we are changing the value to 12\/31\/21. Save and validate the same entry transaction.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><imgtarget=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2021\/04\/Date-Field.png\" alt=\"\"\/><figcaption><strong>Fig03: Validity end date<\/strong><\/figcaption><\/figure>\n\n\n\n<p>Hence, our journal entry has been created successfully. Refer the below screen shot<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><imgtarget=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" class=\"size-full\" style=\"border: 1px solid #A9A9A9; padding: 2px; margin: 2px;\" src=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-content\/uploads\/2021\/04\/Journal-screen2.png\" alt=\"\"\/><figcaption><strong>Fig04: Journal Entry Screen<\/strong><\/figcaption><\/figure>\n\n\n\n<p>This blog helps to solve the error \u201cOutside of validity date limit \u201d while creating journal entry.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>About Us<\/strong><\/h2>\n\n\n\n<p>Greytrix \u2013 a globally recognized and one of the oldest Sage Development Partners is a one-stop solution provider for Sage ERP and Sage CRM organizational needs. Being acknowledged and rewarded for multi-man years of experience and expertise, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third-party add-on development, and implementation competence.<\/p>\n\n\n\n<p id=\"block-28013e99-0882-44c6-b705-7b16c85053b2\">Greytrix&nbsp;has some unique integration solutions developed for&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-crm\/\">Sage CRM<\/a>&nbsp;with Sage ERPs&nbsp;namely&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-x3-erp\/\">Sage X3<\/a>,&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-intacct\/\">Sage Intacct<\/a>,&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-100-erp\/\">Sage 100<\/a>,&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-500-erp\/\">Sage 500<\/a>,&nbsp;and&nbsp;<a href=\"https:\/\/www.greytrix.com\/sage-300-erp\/\">Sage 300<\/a>. We also offer best-in-class&nbsp;Sage ERP&nbsp;and&nbsp;Sage CRM&nbsp;customization and development services&nbsp;to&nbsp;Business&nbsp;Partners,&nbsp;End&nbsp;Users, and Sage PSG worldwide. Greytrix&nbsp;helps in&nbsp;the migration of Sage CRM from&nbsp;Salesforce | ACT! | SalesLogix | Goldmine | Sugar CRM | Maximizer. Our Sage CRM Product Suite includes&nbsp;addons like&nbsp;&nbsp;Greytrix Business Manager,&nbsp;Sage CRM Project Manager,&nbsp;Sage CRM Resource Planner,&nbsp;Sage CRM Contract Manager,&nbsp;Sage CRM Event Manager,&nbsp;Sage CRM Budget Planner,&nbsp;Gmail Integration,&nbsp;Sage CRM Mobile Service Signature,&nbsp;Sage CRM CTI Framework.<\/p>\n\n\n\n<p id=\"block-4bc42a09-fb13-4598-8137-ce5f7b91ce28\">Greytrix is a recognized&nbsp;Sage Champion Partner&nbsp;for GUMU&#x2122; Sage X3 \u2013 Sage CRM integration listed on&nbsp;<a href=\"https:\/\/www.sage.com\/marketplace\/asb_ListingDetail?listingId=a1h24000007PC3aAAG\" target=\"_blank\" rel=\"noreferrer noopener\">Sage Marketplace<\/a>&nbsp;and Sage CRM \u2013 Sage Intacct integration listed on&nbsp;<a href=\"https:\/\/marketplace.intacct.com\/MPListing?lid=a2D0H000007kiHyUAI\" target=\"_blank\" rel=\"noreferrer noopener\">Sage Intacct Marketplace<\/a>. The&nbsp;<a href=\"https:\/\/www.greytrix.com\/gumu\/\" target=\"_blank\" rel=\"noreferrer noopener\">GUMU&#x2122; Cloud framework<\/a>&nbsp;by Greytrix forms the backbone of cloud integrations that are managed in real-time for the processing and execution of application programs at the click of a button.<\/p>\n\n\n\n<p id=\"block-76376301-1c3e-4250-8a09-727595a606f0\">For more information on our integration solutions, please contact us at&nbsp;<a href=\"mailto:sage@greytrix.com\">sage@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In Sage X3, any transaction that impacts a company\u2019s profit and loss needs to be recorded in their accounting system is called &#8216;Journal Entries&#8217;. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A journal entry is used to record a business transaction in the accounting records of a business. A journal entry is usually recorded in the general ledger; alternatively, it may\u2026 <span class=\"read-more\"><a href=\"https:\/\/www.greytrix.com\/blogs\/sagex3\/2021\/04\/14\/how-to-solve-error-outside-of-validity-date-limit-in-journal-entries\/\">Read More &raquo;<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,3162,8,10,11],"tags":[1123,2806,1124,3278,3276,1839,2871,3277],"class_list":["post-22231","post","type-post","status-publish","format-standard","hentry","category-configuration","category-greytrix","category-sage-erp-x3","category-standard","category-tips","tag-journal-entry","tag-journal-entry-transaction","tag-journals","tag-manual-journal-entry","tag-outside-of-date-validity-limit","tag-sage-x3-blogs","tag-sage-x3-functional-blogs","tag-stdco"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/22231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=22231"}],"version-history":[{"count":2,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/22231\/revisions"}],"predecessor-version":[{"id":22243,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/22231\/revisions\/22243"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=22231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=22231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=22231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}