Year-end problems in Sage 300 rarely begin with the Create New Year button. More often, the difficulty is an unfinished transaction, an unreconciled account, an inventory adjustment that has not reached General Ledger, or a report that finance needs after historical data has been cleared.
For companies preparing to close a fiscal year ending on December 31, 2026, the weeks before 2027 provide an opportunity to identify those issues before they affect opening balances and financial reporting. Businesses with a different fiscal year-end should use the same checks against their own closing calendar.
A Sage 300 year-end checklist needs to cover more than General Ledger. It should connect operational transactions, subledger balances, accounting decisions, system integrity, and the work required to open the next fiscal year.
This guide sets out 12 checks for finance teams, controllers, Sage administrators, and support partners. It is a planning and verification framework, not a substitute for the year-end procedures applicable to your Sage 300 version, modules, and accounting policies.
What Should Be Included in a Sage 300 Year-End Checklist?
The objective is to confirm that 2026 activity is complete and supported, that balances reconcile, and that the organization can begin processing 2027 transactions without losing required evidence.
| Review area | What should be confirmed before year-end processing |
| Fiscal calendar | Correct fiscal periods, cutoff dates, and responsibility for the close |
| Operations | Outstanding orders, receipts, shipments, invoices, and batches are reviewed, completed where required, or documented for carry-forward. |
| Subledgers | AP, AR, inventory, and bank balances reconcile to relevant control accounts |
| General Ledger | Adjustments, closing accounts, and financial statements have been reviewed |
| Supporting systems | Imports, integrations, and reports have completed their year-end handoffs |
| System controls | Data integrity, backups, retention settings, and processing approvals are documented |
Sage’s periodic processing guidance explains why sequence matters: the normal period-end work must be completed in the relevant modules before year-end activities are performed. The following checklist turns that guidance into a practical cross-team review.
Before the Cutoff: Confirm the Calendar and Complete Transactions
1. Confirm the Fiscal Calendar and 2026 Closing Schedule
Do not assume every Sage 300 company database follows a January-to-December fiscal year. Verify the year-end date, period structure, and any differences between entities before scheduling the close.
For each company, document:
- The final fiscal period and transaction cutoff for 2026
- Who can enter, approve, import, and post late transactions
- When subledger and General Ledger reports will be captured
- Which teams will remain operational during the close
- Who is authorized to run year-end processing
Decide how post-cutoff adjustments will be handled. For example, finance may need to post an accrual after routine sales and purchasing activity has stopped. That should be a controlled exception, not an undocumented reopening of the period.
- Ready when: finance and operations agree on dates, posting responsibilities, and the treatment of late entries.
2. Resolve Unposted Transactions and Incomplete Batches
A clean year-end starts with complete transaction processing. Outstanding invoices, receipts, payments, credit notes, and journal batches can cause General Ledger totals to differ from reports produced by other modules.
Review the batch status and error reports for the modules in use, including Accounts Payable, Accounts Receivable, Order Entry, Purchase Orders, and General Ledger. Identify items still awaiting posting, correction, or approval.
Pay special attention to imports and transactions originated outside Sage 300. An ecommerce order may appear as completed in one system while its invoice or accounting entry remains unposted in Sage.
Confirm whether the transaction belongs in 2026 must be corrected, or should be carried into the next period under the organization’s accounting policy.
- Ready when: every material outstanding batch has been posted or has a documented owner and treatment.
3. Reconcile Inventory and Complete Day End Processing
For organizations using Inventory Control, year-end should include a review of physical quantities, valuation, adjustments, and accounting entries generated by purchasing and order activity.
Sage identifies inventory counts, variance adjustments, and Day End Processing as part of its year-end preparation. Inventory Control, Order Entry, and Purchase Orders do not use a separate Year End function in the same way as some financial modules.
Check that:
- Physical-count differences have been investigated and approved
- Receipts, shipments, transfers, and adjustments are recorded in the correct period
- Day End Processing has completed where required
- Inventory-related General Ledger batches have been created and posted
- Inventory valuation agrees with the relevant financial records, with differences explained
If a warehouse system or barcode solution feeds Sage 300, reconcile the final transactions from that source as well. A successful interface job does not prove that inventory quantities and values are correct.
- Ready when: operations and finance have signed off on the inventory position and related entries.
Reconcile Financial Modules Before Closing General Ledger
4. Review Accounts Payable and Vendor Balances
Accounts Payable year-end preparation goes beyond paying outstanding invoices. The team must establish which obligations belong to 2026 and ensure that AP balances and related expense entries are represented accurately.
Review open vendor documents, unposted payments, unapplied items, credit notes, recurring payables, and invoices awaiting approval. Reconcile the AP aging or other appropriate subsidiary report with its General Ledger control account.
Separate legitimate timing differences from errors. A vendor invoice dated in December but received in January may require different treatment from an invoice entered twice or a payment posted to the wrong vendor.
Sage provides an A/P Year End process with choices related to activity statistics, recurring payables, and batch-number resets. These choices should be reviewed deliberately; they are not interchangeable with closing General Ledger.
- Ready when: AP totals reconcile; adjustments are documented, and the intended year-end options have been approved.
5. Review Accounts Receivable and Customer Balances
Accounts Receivable requires the same discipline on the customer side. Confirm that year-end billing is complete; customer receipts and credit notes are applied correctly, and open balances represent collectible amounts supported by the underlying records.
Review aging reports, unapplied receipts, disputed balances, write-offs requiring approval, recurring charges, and any invoices created from Order Entry. Compare the relevant AR reports with the General Ledger control account.
Sage’s A/R Year End options can move current-year activity statistics into prior-year fields and, if selected, reset certain batch information. Some reset options affect drill-down visibility. Review these implications before processing, particularly if finance or auditors rely on historical transaction navigation.
Do not treat a balanced AR control account as evidence that every customer’s balance is correct. Finance should investigate material customer-level exceptions as well.
- Ready when: AR reconciliation differences are resolved or explained, and year-end option choices are documented.
6. Reconcile Bank Accounts, Cash, and Clearing Accounts
A General Ledger trial balance can balance mathematically while bank and clearing accounts remain incorrect. Complete bank reconciliations for the final period and review outstanding deposits, withdrawals, transfers, and bank charges.
Check the timing of payments and receipts between Bank Services, AP, AR, and any connected banking tools. Unrecorded bank fees and uncleared transactions should be evaluated according to the close policy.
Clearing accounts deserve particular attention. For example, goods-received-not-invoiced balances, payment-clearing balances, and integration suspense accounts may contain transactions that were not fully matched before year-end.
For each material reconciling item, keep the amount, reason, owner, and expected resolution date. This gives reviewers a usable audit trail without requiring them to rediscover the issue in January.
- Ready when: cash is reconciled and material clearing account balances have supporting explanations.
7. Review General Ledger Adjustments and Financial Statements
Once operational modules and subledgers are reconciled, confirm that General Ledger contains the intended 2026 activity. Review recurring journals, accruals, prepayments, depreciation entries from applicable systems, reallocations, and authorized manual adjustments.
Print or retain the required trial balance, General Ledger transaction listings, posting journals, and financial statements. Compare the final results against management expectations and investigate unexplained movements rather than assuming that a posted batch is correct.
For multi-entity organizations, confirm that intercompany balances and consolidation inputs follow the agreed reporting process. If reports use external spreadsheets or custom financial statement definitions, verify that those outputs reflect the final posted data.
Sage’s General Ledger year-end guidance specifically calls for outstanding transactions and audit-trail reports to be addressed before processing.
- Ready when: the controller has approved final balances and retained the supporting reports.
8. Review Multicurrency Balances Where Applicable
Organizations using multicurrency accounting should check whether the applicable year-end exchange rates, currency revaluation, and any related adjustments have been completed under the company’s accounting policy.
Confirm the applicable rate sources and dates, identify foreign-currency accounts that require review, and reconcile resulting General Ledger entries. Multi-entity operations may also have separate currency requirements for reporting and consolidation.
This check is not a reason to revalue every balance automatically. The correct treatment depends on the account, currency, reporting framework, and system configuration. Finance should determine which balances require adjustment and confirm that those entries have posted before final financial statements are approved.
Ready when: currency-related assumptions, entries, and reconciliations are documented and approved.
Protect History and Prepare the New Fiscal Year
9. Verify Closing Accounts and Retained Earnings Setup
Before running G/L Create New Year, verify how the system is configured to close income and expense accounts. In Sage 300, the default closing account is defined in General Ledger options. Organizations using account segments may have additional retained earnings mappings by segment.
An incorrect setup can create opening-balance problems even if all 2026 transactions were posted correctly. Review the intended account assignments with the controller before processing.
According to Sage’s G/L Create New Year documentation, the process closes income and expense accounts, carries forward appropriate balance sheet opening balances, and advances the current fiscal year.
For a segmented chart of accounts, verify that each relevant closing segment maps to the intended retained earnings account.
Ready when: closing-account configuration has been checked against the approved chart of accounts.
10. Capture Reports and Review History-Retention Choices
Year-end reporting is not complete simply because the final statements have been printed. Confirm that finance can retrieve the transaction evidence, aging reports, journals, supporting schedules, and custom reports it will need for audit, tax, or future comparisons.
Review the retention settings before any history-clearing or batch-reset process. Sage’s Period End Maintenance guidance warns that deleting historical information is permanent. Year-end processing and history maintenance should not be treated as the same decision.
This matters particularly where multiple teams rely on historical detail. Finance may need prior-year transaction drill-down, while operations may need older purchasing or inventory information to investigate later issues.
Preserve evidence according to company retention policy and applicable requirements. Record where files are stored and who can retrieve them.
Ready when: required historical records are accessible and any proposed clearing action has explicit approval.
11. Validate Integrations, Data Integrity, and Recoverable Backups
Sage 300 year-end depends on surrounding systems. Confirm the final scheduled imports, banking feeds, ecommerce orders, warehouse postings, AP automation transactions, and reporting exports have been processed and reconciled.
An integration marked as successful may still have failed to create the expected accounting entry.
Back up the data before running any integrity check that could apply fixes. Then run the appropriate Sage 300 data-integrity checks and investigate reported errors before year-end processing. Take another complete, restorable backup immediately before Create New Year or other year-end processing if your recovery plan requires it.
Take a complete, restorable backup before processing, coordinated with the infrastructure or hosting team. Confirm the backup covers the required company data and associated dependencies, and that someone is responsible for restoring it if necessary. The existence of a backup job is not the same as recovery readiness.
- Ready when: critical data handoffs, integrity checks, and backup evidence have been reviewed.
12. Create the New Year and Verify the 2027 Opening Position
Treat the final processing step as a controlled change, with clear authorization, a processing window, and a documented verification plan.
There are two separate concepts to understand:
- Fiscal Calendar: the next year and its periods must exist with the correct dates.
- G/L Create New Year: General Ledger cannot post for a future year. Create New Year closes income and expense accounts, creates opening balances, and advances the current fiscal year before G/L batches can be posted to it.
ADSS already provides a step-by-step guide to adding a new year to the fiscal calendar in Sage 300. Use that article for the interface steps and confirm procedures against the installed Sage 300 release.
After authorized processing, review the resulting batch status and posting journal, confirm the new fiscal year is active, and check the expected opening balances. Verify that income and expense accounts begin with the correct opening position while balance sheet balances and retained earnings reflect the close.
Sage documentation also explains that postings to a previously closed year may remain possible, with related retained earnings updates. This does not remove the need for controls over late adjustments and refreshed reports.
Ready when: finance signs off on the opening position and understands the process for any permitted prior-year changes.
Sage 300 Year-End Readiness: A Final Sign-Off Table
Before the team proceeds, use a short decision record rather than a verbal assurance that everything is complete.
| Control question | Evidence of readiness | Owner |
| Are 2026 transactions complete? | Batch reports and approved exception log | Module owners |
| Do subledgers agree with GL? | AP, AR, inventory, and bank reconciliations | Finance |
| Are financial statements approved? | Final trial balance, reports, and adjustments | Controller |
| Is the closing configuration correct? | Reviewed retained earnings mappings | Controller / Sage admin |
| Is required history protected? | Retention decisions and archived reports | Finance / IT |
| Can the system be recovered? | Integrity results, backup record, recovery owner | IT / hosting provider |
| Is 2027 posting readiness verified? | New-year processing results and opening-balance checks | Finance / Sage admin |
A ‘not ready’ answer should produce a specific action: what is outstanding, who owns it, and whether it prevents year-end processing.
Common Sage 300 Year-End Questions
Does every Sage 300 company need to close on December 31?
No. The closing date follows the organization’s fiscal calendar. A company with a March or June fiscal year-end should apply the same controls to the appropriate period, rather than automatically closing General Ledger in December.
Is adding 2027 to the fiscal calendar the same as closing 2026?
No. Adding the fiscal year establishes its periods. G/L Create New Year performs the General Ledger year-end process. The procedures are related but serve different purposes.
Do Inventory Control and Order Entry have their own Year End function?
Not in the way General Ledger, Accounts Payable, and Accounts Receivable do. Sage directs users to perform applicable period-end procedures, including inventory reconciliation and Day End Processing, for Inventory Control, Order Entry, and Purchase Orders.
Can adjustments still be posted to the closed year?
Sage’s General Ledger documentation allows posting to a previously closed year and describes corresponding retained earnings updates. Whether staff should do so, and who can authorize it, must be governed by the organization’s close and reporting controls.
Prepare the Records Before You Process the Year-End
A successful Sage 300 year-end is not defined by reaching the next fiscal year without an error message. It is defined by supported balances, completed business processes, accessible audit evidence, and a clear opening position for the next period.
The most useful approach is to complete operational processing first, reconcile the financial modules, verify General Ledger and close accounts, protect historical records, then run and validate the applicable year-end procedures.
For organizations with complex integrations, multiple company databases, or unresolved reconciliation issues, a pre-close review can identify dependencies before they become a January support problem. ADSS Global works with Sage 300 customers on system reviews and ongoing support. For product context, see the ADSS Sage 300 overview, or contact ADSS Global to discuss year-end readiness in your environment.