Month-end close has a way of exposing every timing problem at once. The vendor invoice for December utilities lands in January, payroll is half processed, a contractor has worked through the cutoff date, and someone on the team is still asking whether to wait for the bill or book the accrual now. If you're staring at a close calendar and a stack of unbilled services, you're in the exact spot where accounting entries for accruals matter most.
The rule is simple, even if the execution isn't. Under the accrual basis of accounting, revenue is recognized when it's earned and expense is recognized when it's incurred, not when cash moves. That's the mechanism that keeps the income statement and balance sheet tied to the correct reporting period, especially at month-end and year-end cutoff dates such as December 31 or June 30. Princeton Finance's year-end accrual guidance and TrueWind's accrual journal entry discussion both reflect that same core logic.
Table of Contents
- Step 1, identify what was incurred but not yet paid
- Step 2, estimate or prorate from source documents
- Step 3, post the journal with support attached
- Step 4, schedule the reversal before the next close
- The standard reversal pattern
- Which accruals should reverse automatically
- When to net against the invoice instead
- FX timing belongs beside the accrual, not inside it
- Contractor-heavy teams should accrue the full obligation
- Crypto settlement adds a second timing layer
What Accruals Are and Why They Exist
A finance team usually notices accruals because a bill has not arrived yet, but the month is already closing. The utility service was consumed in December, the invoice shows up in January, and the books still need to reflect that December cost in the right period. That is what an accrual does. It places the economic event where it happened, even if cash settles later.
Recognition comes before payment
The recognition principle is the core idea behind accruals. Revenue belongs in the period it is earned, and an expense belongs in the period it is incurred. That timing rule is built into accrual-basis accounting, which matches financial statements to the period when the activity occurred, not when cash moved. A diagram illustrating accrual basis accounting, highlighting revenue recognition and expense recognition principles in business finance.
Teams often mix up accruals with cash flow. An accrual is not a guess about a future payment. It is a current-period entry for what has already been used, earned, or owed. If a December utility bill arrives in January, the expense still belongs in December when the service was received, and the cash payment later clears the liability. The same cutoff logic appears in the guide for farm financial management, where uneven billing cycles make period timing easy to miss.
Accrued expenses and accounts payable are not the same thing
The cleanest way to separate them is to ask one question, has the invoice arrived? If the business has received the goods or services but has not been billed yet, that is an accrued expense. If the bill is already in hand, it is accounts payable. That distinction also shows up in the practical difference between acumulaciones vs. diferimientos guide for startups and fintech, where timing, not just accounting labels, drives the close.
Practical rule: if the service period ended before the cutoff and the invoice has not arrived, book the accrual. If the invoice exists, route it through AP instead.
For a team closing for the first time together, that timing rule matters more than getting every estimate perfect. A close that puts a rough but reasonable number in the correct month usually tells a truer story than a precise figure posted into the wrong month. The wrong month distorts margin, breaks comparability, and makes later analysis harder to trust.
The Core Journal Entry Pattern for Accrued Expenses and Accrued Revenue
At month-end, the entry is usually small, but the logic behind it carries the close. The question is simple: did the business earn the expense or the revenue in this period, even if cash has not moved yet? If yes, the entry records that timing mismatch so the books show the period's true activity instead of the payment date.
For an accrued expense, the company recognizes cost now and records a liability for later payment. For accrued revenue, the company recognizes income now and records a receivable until billing or collection happens. The accounting is mirrored on purpose, because both entries are trying to match the current month with the economics that happened in that month.
Accrued expense entry
December wages are the clearest place to start. If employees earned wages in December and the accrual is $10,000, including employer payroll taxes in the obligation, the entry is a debit to Wages Expense and a credit to Accrued Wages Liability. That liability should also capture related employer payroll taxes and any benefits tied to the earned labor, because those costs belong to the same period as the wages themselves.
Read the entry in plain language. The debit tells the income statement that December carried the labor cost. The credit tells the balance sheet that the company owes money for work already received, even though the cash payment will happen later.
Accrued revenue entry
Accrued revenue follows the same recognition rule from the opposite direction. If your team delivered consulting work in December and has not billed yet, you debit Accrued Receivable and credit Revenue. The service has already been delivered, so the revenue belongs in the current period, even though the invoice has not gone out.
That entry matters because it keeps the revenue from slipping into the wrong month. Revenue recognition should follow performance, not invoicing speed. A month-end close that misses this cutoff can understate the current period and overstate the next one, which makes margin analysis harder to trust.
| Scenario | Debit | Credit | When Posted |
|---|---|---|---|
| Accrued expense | Expense | Accrued liability | Period end, before invoice arrives |
| Accrued revenue | Accrued receivable | Revenue | Period end, before invoice is billed |
| Invoice later arrives for accrued expense | Accrued liability | Cash or Accounts Payable | When settled |
| Cash later received for accrued revenue | Cash or Accounts Receivable | Accrued receivable or Revenue | When collected |
Accounts payable is the follow-on, not the substitute
Teams often want to wait for AP and skip the accrual. That works only if the invoice already exists. If the invoice is missing, AP cannot carry the period-end obligation correctly, because AP is invoice-based and the accrual is the placeholder for a cost already incurred. The distinction is one of the first places new staff accountants get tripped up. A clean close depends on putting the obligation in the right bucket first, then letting AP or cash clear it later.
A Four-Step Workflow for Recording Accruals at Month-End
The journal entry is the final step. The core control work happens before anything hits the ledger, because that is where the team decides whether the accrual is supportable, estimated correctly, and ready to reverse or settle cleanly in the next period. A solid month-end process turns those judgments into a repeatable sequence instead of a last-minute scramble.
Step 1, identify what was incurred but not yet paid
Start with cutoff testing. Review goods and services received through the reporting date, then separate them from items that belong to the next period. Accrued expenses are current liabilities tied to services already received but not yet billed, so the cutoff review should focus on that population first.
A useful way to frame it is simple, ask whether the company has already taken the benefit. If the answer is yes and the invoice has not arrived, the item belongs in the accrual review.
Step 2, estimate or prorate from source documents
Estimates are acceptable when they are grounded in evidence. That evidence might be a contract, timesheet, usage report, payroll register, or vendor communication. Before posting, gather the rate, quantity, and the document that supports the calculation, then attach that support to the entry so the reviewer can follow the logic. If the cost is salaried payroll, teams commonly prorate by working days in the cutoff period. Variable items like utilities or contractor hours need source-based estimates, not guesswork.
Control point: if you cannot tie the number to a contract, timesheet, or usage report, the estimate is too loose for close.
That judgment matters because accruals are meant to record what happened, not what feels reasonable in the moment. A good estimate should let another accountant retrace the path from source to journal without guessing at the method.
Step 3, post the journal with support attached
The journal should show the account logic, the period cutoff, and the evidence trail. That documentation is the audit defense for estimate-based accruals, and it also helps the next reviewer understand why the entry exists when the invoice arrives later and AP needs to match it back to the prior estimate.
Teams often trip up here by writing the amount correctly but leaving the rationale thin. A clean entry should answer three questions at a glance: what was accrued, why it belongs in the period, and what support sits behind the number.
Step 4, schedule the reversal before the next close
The reversal should be planned as part of the original entry, not treated as cleanup work later. If the accrual is expected to be replaced by an invoice in the next period, reverse it on day one of that period and let the actual invoice flow through the normal AP process. That keeps the expense from being recorded twice and gives the invoice a clean path back into the books.
Recurring accruals are usually the best fit for automatic reversal, especially payroll, utilities, recurring contractor costs, and interest. One-off accruals need more review, particularly when the estimate is tied to a disputed amount, a project milestone, or timing that may not repeat. The reversal is the control that clears the placeholder, while the later invoice or payment becomes the final record of what was owed.
The point is not perfect precision. The point is to make sure every accrued item is tied to evidence, posted in the correct period, and cleared or reversed later without leaving stale balances behind.
Reversing Entries Without Double-Counting Expense
A month-end close can look clean on paper and still produce duplicate expense if the reversal step is handled loosely. The accrual gets booked to match the service period, then the invoice arrives later and AP posts it again unless the original entry is cleared first. The reversal entry is the control that prevents that overlap, and many close cycles lack clear documentation for how that reversal should behave.
The standard reversal pattern
If you booked a $10,000 wage accrual at month-end, the reversing entry on the first day of the next period is debit Accrued Liability, credit Expense. That clears the placeholder liability before AP records the invoice or payroll run. When the actual invoice later arrives, the expense hits once, not twice.
The logic is easier to see with a mismatch. Suppose the actual invoice comes in at $9,200 against the original $10,000 accrual. After the reversal, the invoice posts through AP for $9,200, and the $800 difference becomes the current-period true-up. That difference should be easy to trace back to the estimate, not hidden inside a broad adjustment.
Which accruals should reverse automatically
Recurring accruals are the best candidates for auto-reversal. Payroll, utilities, recurring contractor invoices, interest, and similar predictable items usually get replaced by a normal invoice or payment cycle, so the placeholder should clear on schedule. One-off accruals need more review, especially when they are tied to a disputed estimate, a project milestone, or a period-end amount that will not unwind cleanly next month.
This is the operational gap many close guides miss. A reversal calendar, a clear owner, and support that ties the accrual to the later invoice make the next reviewer's job much easier, including the reviewer handling the audit of accounts payable.
When to net against the invoice instead
If the invoice arrives quickly and matches the prior estimate closely, some teams net the actual against the accrual instead of letting the reversal and invoice run as separate events. That can work, but only if the workflow is consistent and well controlled. The risk is that AP and GL teams start handling the same transaction differently, which makes reconciliation harder and audit support weaker.
Good practice: choose one policy for recurring accruals, document when entries auto-reverse, and keep one exception path for items that will be replaced by a true-up.
The reversal step exists to protect the close from duplication. If the team cannot tell at a glance whether an accrual was reversed, netted, or left outstanding, the policy needs tighter documentation and a clearer review trail.
Common Errors That Distort Monthly Results
A month-end close can look clean and still miss the period that belongs on the books. That usually happens when the team books the right idea in the wrong month, or leaves a liability hanging after the invoice has already arrived. The result shows up later in margin reviews, working capital analysis, and any discussion of why the close moved faster than the underlying business.
The four mistakes teams repeat
Using the cash date instead of the service date. The books may show a neat AP trail, but the income statement lands in the wrong period. The cause is simple, the entry is posted when the invoice or payment arrives instead of when the work was performed. The fix is a cutoff check tied to the period of service, so the expense follows the work, not the paperwork.
Forgetting the reversal. An accrual without a reversal plan leaves a stale liability on the balance sheet after the invoice has already been booked. That creates the accounting version of a sticky note left on the monitor after the task is done. Set the reversal when the accrual is recorded, then confirm it in the next close and keep the support with the original entry.
Under-accruing variable items. Utilities, contractor hours, and interest are the places where estimates drift first. A small miss here can distort the monthly result even when the rest of the close is tight. Pull the usage, rates, and backup before posting, rather than relying on last month's amount by habit, because the estimate should match the obligation that has already been incurred.
Confusing accrued expenses with AP. The same obligation should not live in two liability buckets. The mistake usually appears when a placeholder liability is booked after an invoice already exists, which makes reconciliation messy and invites duplicate entries. Keep the line clear, accruals belong before the invoice, AP belongs after the invoice arrives. FinQuery's AP distinction is a useful way to teach that split. For a tighter review trail, the audit of accounts payable guide helps reviewers see how invoice-backed liabilities should be tested against support.
Why document attachment matters
The attachment is the proof, not busywork. A journal tied to a contract, timesheet, usage log, or payroll record gives the reviewer a way to test the estimate and trace the cutoff logic back to the underlying event. Without that support, the number may still be directionally right, but the team has a harder time showing why it belongs in that period.
That same discipline matters for any later review of settlement timing, including transactions tracked through Solana Tracker's trade insights, where the booking date and the cash event can separate quickly if the team is not watching the timing chain.
Multi-Currency, Contractor, and Crypto Settlement Timing
A close can look clean on paper and still miss the timing gap between service delivery, invoice issuance, and settlement. Cross-border teams run into that gap often. A contractor may finish the work in one currency, send the bill in another, and receive payment after exchange rates have already shifted. The accounting rule does not change, but the team has to separate the original obligation from the later settlement movement.
FX timing belongs beside the accrual, not inside it
A December service performed by a contractor may be invoiced in EUR while the books are kept in USD. The accrual should record the obligation in the reporting currency used by the ledger as of the service date. Any currency movement between that date and the payment date belongs to settlement, not to the expense itself. That keeps the expense in the right period and leaves the exchange difference available for later review.
This separation helps avoid a common month-end mistake. Teams sometimes try to fold the FX movement into the accrual entry, which muddies the cutoff and makes it harder to see whether the original estimate was sound. A cleaner approach is to let the accrual answer one question, what was earned or incurred by period end, and let settlement answer a different one, what changed because the cash moved later.
Contractor-heavy teams should accrue the full obligation
Contractor and payroll accruals work best when the full obligation is recorded together. That means wages, employer payroll taxes, and related benefits belong in the same accrual if they are all incurred with the work. Splitting those pieces into separate timing buckets usually creates confusion when the bill or payroll run arrives, because the team then has to chase several small liabilities instead of one clear obligation. Xero's accrued expenses guidance makes the same point for payroll-related accruals, including employer taxes and benefits, since they are part of the incurred cost.
For global contractor payments, the accounting issue is usually invoice timing, not whether the cost exists. The work has already been delivered, so the liability belongs in the period the service was performed. The payment process may be handled later through OneSafe's guide to paying international contractors, but that operational lag does not move the expense into a later month.
Crypto settlement adds a second timing layer
Web3 teams face a similar cutoff problem when payment starts in crypto and ends in fiat. A USDC payment that settles into fiat days after the service date still leaves a reporting gap that the finance team has to bridge with an accrual. The entry follows the same accounting logic, yet the settlement path can be more volatile and less predictable than a standard bank transfer.
That extra layer matters because the team may need to track both the service obligation and the value realized when the digital asset is converted or settled. The accrual stays anchored to the service period. The later conversion, price movement, or transfer delay becomes a separate reconciliation issue. For market-context reading on how quickly digital asset conditions can shift, Solana Tracker's trade insights can help, even though the accounting entry itself still belongs to the period when the work was completed.
The practical answer is tighter payment infrastructure and clearer cutoff discipline. Multi-currency accounts, faster conversion rails, and web3 invoicing can narrow the gap between service date and settlement date, which makes month-end reconciliation easier when the invoice or payout finally lands. That does not change the journal entry, but it does reduce the number of moving parts the controller has to explain during close.
A Reusable Month-End Checklist and Closing FAQ
The best accrual process feels boring by the third close. That's the goal. If the team can confirm cutoff, attach support, apply a materiality rule, schedule reversals, and reconcile the follow-up invoice without debate, accruals stop being a fire drill and become a routine close task.
- Confirm the cutoff date. Use the service-incurred date, not the cash date.
- Attach source documents. Keep contracts, timesheets, usage logs, or payroll support with the journal.
- Apply the estimate rule. If the amount is supported, post it. If it's too uncertain or clearly immaterial, document the judgment.
- Schedule the reversal. Set it for the first day of the next period when the accrual will be replaced by the invoice.
- Reconcile after close. Compare the actual invoice or cash settlement to the original accrual and record the difference cleanly.
FAQ. If an accrual straddles fiscal years, the service date still drives the period. If the invoice arrives later, reverse or clear the accrual according to the team's standard policy, then let AP handle the actual bill. If the actual invoice differs from the estimate, the difference should flow through the current period as a true-up, not disappear into the original entry.
A structured close checklist, plus disciplined documentation, is what keeps accruals from turning into a last-minute scramble. If your team needs a cleaner way to manage multi-currency spend, contractor payments, and crypto-fiat settlement timing in the same workflow, take a look at OneSafe and see how a unified operating stack can support the accounting discipline you're already trying to maintain.
