SyteLine posting out of current period: causes and a safe fix

Resolve the period error without damaging the ledger

1. 1Read the exact message and note which transaction raised it (invoice, voucher, inventory transaction, job material issue, payment).
2. 2Look 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.
3. 3Open the accounting periods setup under General Ledger and check that the period covering that date exists for the fiscal year and is open.
4. 4Check 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.
5. 5In a multi-site setup, repeat the check for the specific site, since periods and close status are maintained per site.
6. 6If the date is simply wrong, change it to a date in an open period and repost. This is the preferred fix.
7. 7If the date is right and the period is closed, get Finance approval before reopening. Post, then close the period again and record why.
8. 8Rerun the GL trial balance for the period and confirm subledger totals still tie to the control accounts.

Open, closed and locked: what to check

-- 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;

Common 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.