Bookkeeping Basics
Sage Month End: A Beginner’s Guide
Use a controlled Sage month-end process to finish posting, reconcile subledgers and balance-sheet accounts, review reports, record adjustments, protect the audit trail, and manage the accounting period.
Sage month end is the controlled process of completing transaction posting, reconciling accounts, reviewing subledgers and financial statements, recording supported adjustments, and protecting the finished period. It is not one universal button. Sage Accounting, Sage 50, Sage 100, Sage 200, Sage 300, and Sage Intacct have different menus, modules, period controls, and edition-specific features.
Use the current help for your exact product, country, version, modules, and permissions before changing a period. The accounting sequence below is designed to remain useful across editions.
Prepare the close calendar
Define the month-end date, report basis, responsible preparer, reviewer, client or department dependencies, and target completion date. A checklist should identify the evidence needed for each task and the person who approves exceptions.
Request bank and card statements, processor reports, payroll records, customer and vendor information, inventory or project data, loan statements, fixed-asset invoices, and explanations for unusual transactions before the deadline.
1. Finish routine posting
- Enter or import sales, customer receipts, purchases, vendor payments, payroll, expenses, bank activity, and journals through the correct module.
- Review batch status, rejected imports, interface logs, recurring entries, and transactions held for approval.
- Match transfers and payment-processor settlements without duplicating income or expense.
- Resolve transactions dated in the wrong period and documents that remain incomplete.
Module activity often feeds control accounts in the general ledger. Direct entries to receivable, payable, inventory, payroll, or other control accounts can break the agreement between the ledger and its supporting detail.
2. Close operational subledgers
Review accounts receivable for unapplied cash, credit balances, old invoices, write-offs, deposits, and bad-debt decisions. Review accounts payable for duplicate bills, unapplied credits, old checks, missing approvals, and bills received after the period.
Complete payroll posting and reconcile wage expense, employer cost, cash, and payroll liabilities to the payroll registers and filings. If the business uses inventory, jobs, projects, fixed assets, or sales-order modules, complete the product-specific processing and capture the supporting reports before the general-ledger review.
3. Reconcile cash and payment accounts
Reconcile each bank, credit-card, loan, and payment-clearing account to an independent statement. Enter the correct statement ending date and balance, match cleared activity, and investigate the remaining difference.
Outstanding checks and deposits in transit may be valid timing items. Old or unusual items require follow-up. Never enter an unexplained adjustment solely to make the reconciliation difference zero. See the Sage bank reconciliation guide for the detailed workflow.
4. Reconcile control accounts to detail
| General-ledger balance | Supporting report | Common difference |
|---|---|---|
| Accounts receivable | Customer aging or trial balance | Direct GL journal, backdated invoice, report filter |
| Accounts payable | Vendor aging or trial balance | Direct GL journal, unposted batch, date mismatch |
| Inventory | Inventory valuation | Negative quantity, missing receipt, cost update, timing |
| Payroll liabilities | Payroll register and liability detail | Manual payment, mapping error, filing adjustment |
| Fixed assets | Fixed-asset register | Unrecorded addition, disposal, depreciation, wrong account |
| Loans | Lender statement or amortization schedule | Principal and interest split, fees, late posting |
Use the same cutoff date and reporting basis on both reports. Save evidence of the reconciliation and any approved correction.
5. Record supported month-end adjustments
Review accrued expenses, prepaid expenses, deferred revenue, fixed assets, depreciation, inventory, payroll, debt, bad-debt estimates, intercompany activity, foreign currency, and other areas applicable to the business. Every adjustment should have a clear description, date, account, amount, preparer, reviewer, and supporting calculation.
Use recurring journals only when the assumptions remain valid. Update the amount and support when the contract, service period, loan, headcount, or other driver changes.
6. Review the trial balance and general ledger
Run the trial balance and general ledger for the month. Sage products provide different general-ledger report sets and drill-down options, so confirm the date and filter settings. Look for:
- Unexpected debit or credit balances.
- Large or round-dollar journals without support.
- Entries posted directly to control accounts.
- Negative cash, receivable, payable, inventory, or fixed-asset balances that do not fit the facts.
- Activity in inactive, suspense, clearing, or prior-period accounts.
- Duplicate, reversed, or late-posted transactions.
7. Review financial statements
Run the balance sheet and income statement for the closed month and compare them with the prior month, prior year, budget, or operating expectation. Investigate whether a change results from price, volume, timing, classification, missing data, or an error.
Review gross margin, payroll, contractor cost, occupancy, software, debt, owner activity, cash, receivable aging, payable aging, and other business-specific indicators. Confirm that net income connects properly with equity in the report design.
8. Manage period access
After review and approval, use the product’s period or date controls to prevent unintended changes. Some Sage products treat month-end processing differently by module and may allow transactions in more than one period. Sage 200 documentation, for example, explains that module month-end routines and period controls are separate considerations.
Before restricting access, confirm all required modules have completed their current workflow, recurring items are handled, reports are saved, and authorized users understand the process for a necessary late adjustment. Do not assume that running a routine creates an immutable close in every product.
9. Preserve the close package
Save the final trial balance, general ledger, financial statements, bank and control-account reconciliations, aging reports, payroll reports, debt and fixed-asset schedules, journal support, exception log, and sign-off. Use a consistent folder and file naming convention.
Back up or export data according to the product and company policy. Test restoration and access controls. A download that has never been tested is not a complete recovery plan.
Handle late information after close
Define what happens when a vendor bill, payroll correction, customer credit, bank notice, or professional adjustment arrives after sign-off. The policy should consider materiality, reporting deadlines, whether statements were distributed, tax or lender effects, and the product’s period controls. It should not rely on an invented universal dollar threshold.
If the period must change, preserve the originally issued reports, approve the entry, post it through the correct source or journal workflow, and rerun every affected schedule and statement. Record who received the revised report. If the item is handled in the current period under an approved policy, document why.
Use a reconciliation ownership matrix
List every material balance-sheet account with its Sage account number, supporting source, preparer, reviewer, due date, and expected reconciling items. The matrix makes missing ownership visible and prevents accounts such as payroll clearing, payment processors, deposits, or intercompany balances from being overlooked.
Track open reconciling items by origin date, owner, planned resolution, and risk. Completion should mean that unexplained differences are resolved or formally documented, not that a checklist box was marked.
Review the matrix when accounts, modules, integrations, staff, ownership, deadlines, or reporting requirements change, and retain the approved revision with the close procedures.
Sage month-end checklist
- Confirm cutoff, product, modules, period, and close responsibilities.
- Complete transaction posting and resolve import or approval exceptions.
- Review receivables, payables, payroll, inventory, projects, and fixed assets.
- Reconcile bank, card, processor, loan, and control accounts.
- Post and approve supported adjustments.
- Review the trial balance, general ledger, and comparative financial statements.
- Resolve exceptions and document expected differences.
- Apply appropriate period controls.
- Save the close package and record preparer and reviewer sign-off.
Common Sage close mistakes
- Following instructions for a different Sage product or version.
- Running financial statements before subledgers are complete.
- Posting direct journals to control accounts.
- Forcing bank reconciliations with unsupported adjustments.
- Changing prior periods without preserving the original reports and approval.
- Closing access before payroll, inventory, or project workflows are finished.
Use a broader month-end close checklist to assign responsibilities. Businesses that want recurring close support can review bookkeeping services.
Frequently asked questions
Does Sage have one month-end close process?
No. The workflow and controls differ across Sage products, countries, versions, and modules. Use the current documentation for the exact system.
Should bank reconciliation happen before financial review?
Yes. Cash and other material balance-sheet accounts should be reconciled before management relies on the financial statements.
Can I post into a prior month in Sage?
That depends on product configuration, period status, date controls, modules, and permissions. Follow the approved late-entry process and preserve the prior reports.
What reports belong in the month-end package?
Keep the trial balance, general ledger, financial statements, reconciliations, aging reports, supporting schedules, journal support, exception log, and sign-off.
Why does a Sage subledger not match the general ledger?
Possible causes include direct GL entries, unposted batches, different cutoff dates, report filters, failed integrations, reversals, or module-processing differences.
Do I need to back up before month end?
Follow the product and company recovery policy. Maintain protected backups or exports at meaningful close points and test that authorized staff can restore or retrieve them.
Turn this guide into action