Closing a GL period in Acumatica is not a single button — it's the last step in a sequence, and the sequence is what people get wrong. A financial period can only be closed in General Ledger once it's been closed in every activated sub-ledger module: Accounts Payable, Accounts Receivable, Cash Management, Inventory, and Fixed Assets. Skip that ordering and GL501000 (or the close action itself) will simply refuse, or worse, you'll close GL and then discover a sub-ledger still has open transactions dated into the period you just locked.
Close the sub-ledgers first, and in the right order
GL depends on every sub-ledger being closed, not the other way around, so the sub-ledgers go first. In practice I close AP and AR before CA and IN, because cash and inventory transactions often reference AP bills and AR invoices — clearing payments and receipts, for instance — and closing CA while AP still has open items you'd want to match against tends to surface reconciling items you'd rather catch before GL is locked. Fixed Assets closes last among the sub-ledgers, since depreciation runs for the period typically depend on transactions already being final in the other modules. The exact order matters less than the principle: every activated sub-ledger needs a "Closed" status for the period before GL close will even be a clean action rather than a forced one.
The Unposted Documents report is your gate
Before you touch any close screen, run the Unposted Documents report. It should come back blank. If it doesn't, you have transactions sitting in a state where they were never posted to the GL — and closing periods around unposted documents is how you end up with a document dated in a period that's now closed, with nowhere clean to post it except a later period where it doesn't belong. Treat a non-blank Unposted Documents report as a hard stop, not a warning to note and move past.
An unposted document from a closed period has to land somewhere. That somewhere is always a later period, which distorts that period's numbers and creates exactly the kind of reconciling item that takes an afternoon to explain to an auditor. Clear the Unposted Documents report to zero before you close anything.
Run FX revaluation before you close
If the tenant carries any foreign-currency balances, currency revaluation runs before the GL period closes, not after. Revaluation posts the auto-reversing unrealized gain/loss entries that mark open foreign-currency balances to the period-end rate — if you close first and revalue later, either the entry lands in the wrong period or you have to reopen a period you just locked. I go into the mechanics of why the entry is auto-reversing and how the account mapping works in the FX revaluation at end of month post — the short version here is: revaluation is a pre-close step, not a post-close cleanup.
Close the period on GL503000
With sub-ledgers closed, the Unposted Documents report clean, and revaluation run, use the Manage Financial Periods screen (GL503000) to close the GL period. Closing a period there assigns "Closed" status to that period and to every preceding period in the range — so if you're catching up after a backlog, one close action can lock a whole run of periods at once, which is worth knowing before you click it on a range you didn't mean to close.
"Restrict Access to Closed Periods" is the safety net, not the default
The request that always comes eventually is "we need to post one more thing into last month." If "Restrict Access to Closed Periods" is checked on GL Preferences, a closed period simply isn't selectable in transaction entry — except for users holding the Financial Supervisor role, who can still post into it deliberately. That's the intended safety net: close periods hard by default, and give a narrow, named role the ability to override it when there's a genuine late adjustment, rather than leaving every user free to post into a period that's supposed to be final.
The order, as a checklist
| Step | Screen / report | Why it matters |
|---|---|---|
| 1. Close AP | Accounts Payable period close | GL close depends on all activated sub-ledgers being closed first |
| 2. Close AR | Accounts Receivable period close | Same dependency; also clears the way for CA reconciliation |
| 3. Close CA | Cash Management period close | Cash transactions reference AP/AR — close after those settle |
| 4. Close IN | Inventory period close | Stock transactions need to be final before FA depreciation and GL close |
| 5. Close FA | Fixed Assets period close | Depreciation runs depend on the period being otherwise final |
| 6. Check unposted items | Unposted Documents report | Must return blank — an unposted document from a closed period has nowhere clean to land |
| 7. Run FX revaluation | Currency Management revaluation process | Posts auto-reversing unrealized gain/loss before the period locks |
| 8. Close the GL period | Manage Financial Periods (GL503000) | Assigns Closed status to this period and all preceding periods in range |
| 9. Confirm the safety net | GL Preferences — Restrict Access to Closed Periods | Locks the period for everyone except the Financial Supervisor role, for the inevitable late-post request |
Wrapping up
A reliable GL close in Acumatica is really a dependency chain: sub-ledgers close before GL will let you close cleanly, the Unposted Documents report has to come back blank before you trust any of it, and FX revaluation runs before the lock, not after. GL503000 is where the period actually closes, and "Restrict Access to Closed Periods" paired with the Financial Supervisor role is what keeps a closed period closed while still giving someone a deliberate way back in when a genuine late adjustment shows up. Follow that order every month and period-end stops being an event and starts being a checklist.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.