# SyteLine posting out of current period: causes and a safe fix > Source: https://netray.co/erp-help/syteline-posting-out-of-current-period > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer A posting-out-of-period message means the transaction date on the document falls in a fiscal period that is closed, locked for that module, or not defined for that site. Check the transaction date first, then the period status for the module and site, and only then decide whether to change the date or reopen the period. Wording and form names vary by release, so confirm against your version. ## Kind error ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module General Ledger / Accounting Periods ## Query syteline posting out of current period ## Alternate Queries - SyteLine transaction date not in open period - SyteLine cannot post to closed fiscal period - SyteLine posting date outside current period error ## Applies To SyteLine 9.x and CloudSuite Industrial 10.x, single-site and multi-site ## Steps ### Resolve the period error without damaging the ledger **Items:** - Read the exact message and note which transaction raised it (invoice, voucher, inventory transaction, job material issue, payment). - Look at the transaction date on the form. Most postings use the transaction or invoice date, not today's date, so an old default date is the usual culprit. - Open the accounting periods setup under General Ledger and check that the period covering that date exists for the fiscal year and is open. - Check whether the module (AP, AR, Inventory, Job) has its own period lock or close flag. A period can be open in GL and closed for a subledger. - In a multi-site setup, repeat the check for the specific site, since periods and close status are maintained per site. - If the date is simply wrong, change it to a date in an open period and repost. This is the preferred fix. - If the date is right and the period is closed, get Finance approval before reopening. Post, then close the period again and record why. - Rerun the GL trial balance for the period and confirm subledger totals still tie to the control accounts. ## Sections ### Why the transaction date drives everything **Body:** SyteLine posts subledger activity to the general ledger using the document's transaction date, then maps that date to a fiscal period. If no open period covers the date, the posting stops rather than landing in the wrong month. That is a control, not a bug. The common triggers are a user keying an invoice or voucher with last month's date after close, a default date carried from a template or recurring entry, a back-dated inventory transaction such as a receipt entered late, and a job transaction processed by a background task whose date is not today. Fiscal calendar gaps also cause it. If the next fiscal year's periods were never generated, the first posting of the new year fails even though nothing is closed. ### Open, closed and locked: what to check **Body:** Treat three layers separately: the period definition (does a period exist for the date), the GL period status (open or closed), and any module-level close. Many shops close the subledgers a few days before GL, so a user can be blocked in AP while GL is still open. Where your release offers a per-site or per-module period view, use it instead of assuming GL status applies everywhere. Also check whether a user has a permission that allows posting to closed periods. Do not grant that casually, because it defeats the control. **Code:** -- Read-only sanity check of period dates (table and column names vary by release; -- confirm in your schema before running) SELECT TOP 20 * FROM fiscalperiods ORDER BY 1 DESC; ### Reopening a period safely **Body:** Reopening is sometimes right: a missed supplier invoice, a late receipt, or an audit adjustment. Do it with a written approval, post only the intended transactions, and close again the same day. Keep a list of what was posted while the period was open. The safer alternative is to post the correction in the current open period with a clear description and reference to the original period. Auditors generally prefer that to reopening, unless the correction changes reported results that are already issued. Never edit period status directly in SQL on a live database. It bypasses the validations that keep the ledger and subledgers consistent. ## Pitfalls - Changing the transaction date to get past the error when the real business date matters for cost or tax. - Reopening GL for everyone and leaving it open after the fix. - Forgetting to generate periods for the next fiscal year before year-end. - Checking only the GL period when the AP or inventory module has its own close. - Assuming a closed period at one site applies to all sites, or the reverse. - Fixing by SQL update to period status instead of the application form. ## Ai Angle An assistant grounded in your SyteLine data (ERPray, or SyteRay for SyteLine) can answer the first diagnostic questions for you: which period covers this date at this site, which modules are closed, and which other transactions are stuck for the same reason. It reads the data and shows the query it ran. It does not reopen periods; that stays a human, approved action. On-prem deployments keep the ledger data inside your network. ## Faq ### Why does SyteLine block a posting even though today's period is open? **Answer:** Because the posting uses the document's transaction date, not today's date. If that date maps to a closed period, a missing period, or a closed subledger, the posting is blocked regardless of what is open today. Correct the date or get approval to reopen the period. ### Should I reopen the period or post in the current one? **Answer:** Prefer posting the correction in the current open period with a clear reference, unless Finance needs the original period adjusted and has not yet issued reports. Reopening should be approved, brief and logged. ### Can I fix this by updating the period table in SQL? **Answer:** Do not. Direct updates skip the application's validation and can leave subledgers out of sync with GL. Use the accounting period and close forms, and test the sequence in a test environment first. ### Why does it only fail at one site? **Answer:** Periods and close status are maintained per site in a multi-site setup. One site may have closed while another is still open, or its next-year periods may be missing. Check the failing site specifically. ## Search terms syteline posting out of current period, syteline closed period error, syteline fiscal period open, syteline transaction date period, syteline reopen accounting period, csi general ledger period close, syteline subledger close, syteline period not defined --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json