Month-end accruals: which to automate as rules and which stay judgment calls
Month-end accruals sorted: which accrued payables run as approved rules with auto-reversal, and which stay judgment calls with controller sign-off.
Part of the month-end close guide.
Month-end accruals fall into two groups. Automate an accrual as a rule when its amount comes from a record you already hold, such as a contract, a goods receipt or a usage feed, and the method does not change month to month. Keep it a judgment call when the amount depends on an estimate of an uncertain outcome, such as a bonus pool, a legal claim or a disputed charge. Both groups still need evidence and a named sign-off. This post sorts the common accrued payables into the two groups, shows how rule-based accruals run with an automatic reversal and explains why year-end is the time to get the split right.
Key takeaways
- An accrued payable is an expense incurred with no invoice recorded yet. Accounts payable starts when the invoice is recorded.
- Three questions sort an accrual: is the amount computed from a record you hold, is the method stable, and would two accountants get the same number?
- Formula-based accruals run well as approved rules with an automatic reversal on day one of the next period, and a controller approves the batch before it posts.
- Judgment accruals stay with people. A workflow collects the evidence, routes the estimate to its owner and records the sign-off.
- Rules need a pattern-change check. COSO's 2026 generative AI guidance describes an automated accrual that missed a supplier's move from monthly to quarterly billing.
- Year-end is the deadline. Review every rule, true up last year's accruals and agree documentation with your auditor before December.
Accrued expenses vs accounts payable: what an accrued payable is
Accounts payable is what you owe on invoices you have received and recorded. An accrued expense, often called an accrued payable, is what you owe for goods or services received in the period where no invoice has been recorded yet. Both are liabilities. The difference is the document behind them.
| Accounts payable | Accrued payable | |
|---|---|---|
| Trigger | Vendor invoice recorded | Expense incurred, no invoice recorded |
| Amount source | The invoice | A contract, receipt, usage data or estimate |
| Typical entry | Bill posted in the ERP | Journal entry at period end |
| What happens next | Paid on terms | Reversed when the invoice posts, or adjusted |
The Answer Library has a short definition of the difference between accounts payable and accrued liabilities. This post is about the next question: which of those accruals can run on rules.
The test that sorts an accrual into rule or judgment
An accrual is a rule candidate when the amount is computed from data you already hold, the method is stable, and two accountants would get the same number. If any answer is no, the accrual is a judgment call, or a rule with a person checking every result.
| Question | Rule candidate | Judgment call |
|---|---|---|
| Where does the amount come from? | A contract, PO receipt, usage feed or timesheet | An estimate of an outcome not yet known |
| Is the method stable? | Same formula every month | Changes with facts and circumstances |
| Would two accountants agree? | Yes, to the cent | Not without discussion |
| What evidence supports it? | The source record and the rule version | A memo with assumptions and an owner |
The test is deliberately strict. A formula that needs a person to adjust it most months is not a rule. It is a judgment call with a spreadsheet attached.
Accruals that run well as rules
Four common month-end accruals usually pass the test. For each one, the rule, the source record and the reviewer should be written down before the workflow runs.
Contracted recurring services
Recurring services billed in arrears, such as a software subscription invoiced quarterly, accrue at the contracted amount for each month of service. The source record is the contract. The rule divides the contracted fee by the service months and accrues all service delivered since the last invoice.
Goods received but not invoiced
Goods received but not invoiced accrue at the PO price for the quantity received. The source records are the purchase order and the receiving record. Our Answer Library page on how to accrue for goods received but not yet invoiced covers the mechanics.
Usage-based vendor charges
Usage-based charges, such as cloud hosting or API calls, accrue from the vendor's usage data at the contracted rate. The source record is the usage export. The rule multiplies usage by rate and flags any month where usage moves outside an approved range.
Wages earned but not yet paid
Wages for days worked after the last payroll date accrue from timesheets or the payroll calendar. The source records are the payroll register and the calendar. The rule counts the unpaid days and applies the daily cost.
A worked example
In this hypothetical example, the rule accrues the cumulative unbilled amount, so the expense lands at $1,000 every month. A company signs a 12-month contract for a monitoring service at $12,000 a year, invoiced quarterly in arrears. At the end of month one, no invoice exists, but one month of service has been delivered.
- Rule: accrue all service delivered but not yet invoiced, at $12,000 ÷ 12 months = $1,000 per month of service.
- End of month one: debit software expense $1,000, credit accrued liabilities $1,000.
- End of month two: the prior accrual has reversed on day one, and the rule accrues $2,000 for two unbilled months.
- End of month three: the $2,000 accrual has reversed on day one, and the rule accrues $3,000 for three unbilled months.
- Month four: the $3,000 accrual reverses on day one, the quarterly invoice for $3,000 posts, and the rule accrues $1,000 for the new quarter's first month.
| Month | Reversal of prior accrual | Invoice posted | New accrual | Expense for the month |
|---|---|---|---|---|
| 1 | $0 | $0 | $1,000 | $1,000 |
| 2 | ($1,000) | $0 | $2,000 | $1,000 |
| 3 | ($2,000) | $0 | $3,000 | $1,000 |
| 4 | ($3,000) | $3,000 | $1,000 | $1,000 |
The expense lands at $1,000 every month because the rule accrues the cumulative unbilled amount, not a flat monthly figure. A flat $1,000 accrual that reverses each month would show $1,000 in month one, $0 in months two and three (each reversal cancels the new accrual), and $3,000 in month four when the quarterly invoice arrives. The four-month total is $4,000 either way, but under the flat method months two and three are understated and month four is overstated.
Flow: contract on file → rule computes unbilled service → controller approves the accrual batch → accrual posts with reversal date → reversal posts on day one → invoice posts when it arrives.
How automatic reversal works
An automatic reversal posts the opposite entry on a set date, so the accrual clears when the real invoice is expected to post. Without it, someone has to remember to reverse each accrual, and a missed reversal doubles the expense.
Most ERPs support this natively. In NetSuite's reversing journal entries, you enter a Reversal Date "on which you want the reversing entry to be posted." Checking Defer Entry makes the reversal "a memorized transaction that is automatically created on the reversal date." Clearing the box enters the reversal immediately, dated to the Reversal Date.
The reversal is part of the rule, not an afterthought. A rule-based accrual should always carry its reversal date, and the approver should see both entries together before the batch posts.
Accruals that stay judgment calls
Accruals stay judgment calls when the amount depends on an estimate of an uncertain outcome. A workflow can still gather evidence and record approvals, but a qualified person sets the number.
Bonuses and incentive pay
Bonus accruals depend on expected performance, plan terms and management decisions that change during the year. The workflow can pull year-to-date results and the plan terms into one place. The controller or CFO sets the accrual and records the basis.
Legal claims and other loss contingencies
Loss contingencies follow a specific recognition test. Under ASC 450-20-25-2, as reproduced in Deloitte's roadmap on contingencies, an estimated loss "shall be accrued" when information available before the financial statements are issued indicates it is probable that a liability had been incurred, and "the amount of loss can be reasonably estimated." Both conditions require judgment, usually with counsel's input. No rule should set this number.
Disputed vendor charges and one-off services
A disputed invoice or a one-off project without a fixed fee needs a person to estimate what you will owe. The workflow routes the item to the budget owner with the contract and correspondence attached, and records the estimate and the approver.
| Accrual | Group | Who sets the amount | What the workflow still does |
|---|---|---|---|
| Contracted recurring services | Rule | Approved rule | Computes, posts, sets reversal |
| Goods received not invoiced | Rule | Approved rule | Matches receipts to POs, posts, sets reversal |
| Usage-based vendor charges | Rule | Approved rule | Pulls usage, flags outliers, posts |
| Wages earned not paid | Rule | Approved rule | Counts unpaid days, posts, sets reversal |
| Bonuses | Judgment | Controller or CFO | Gathers results and plan terms, records sign-off |
| Legal and loss contingencies | Judgment | Controller with counsel | Collects evidence, records the basis and approver |
| Disputed or one-off charges | Judgment | Budget owner, then controller | Routes with documents, records the estimate |
What happens when a rule meets a pattern change
A rule-based accrual is only as good as its assumptions, so it needs a check that catches when the facts change. COSO's Achieving Effective Internal Control Over Generative AI (February 2026) includes a case called "The Vanishing Accrual." A corporate accounting team used a GenAI process to accrue expenses from historical invoice patterns. When a supplier shifted from monthly to quarterly billing, the process did not detect the change and failed to record the monthly accrual. The month-end variance analysis caught it.
COSO describes three fixes: pattern-change alerts in the data transformation stage, a controller review of auto-accrual logic during each close cycle, and variance thresholds that trigger immediate human investigation. All three apply to rule-based accruals as well. A rule computed from the contract, rather than from past invoice patterns, avoids the specific failure, but it still needs an alert when a contract, a rate or a billing frequency changes. Our post on flux analysis with AI covers how variance thresholds work as rules with people writing the explanations.
If you want to see your recurring accruals mapped as approved rules, book a demo.
Year-end accruals: what to get right before December
Year-end accruals get more scrutiny than any month-end, so review the rules and the judgment items before the last close of the year. Five checks cover most of it:
- Review every accrual rule. Confirm the contract, rate and billing frequency still match the source record.
- True up last year. Compare last year's year-end accruals with the invoices that arrived afterwards, and adjust any rule that missed.
- List every judgment accrual. Give each one an owner, a due date and the evidence the auditor will ask for.
- Agree the cutoff. Set the date after which invoices are treated as next-year activity, and publish it.
- Agree the documentation. Confirm with your auditor what they want to see for rule-based and judgment accruals before fieldwork.
The month-end close checklist shows where accruals sit among the other close steps.
Where Loopfour fits
Loopfour, the deterministic finance workflow automation platform, runs formula-based accruals as approved rules and routes judgment accruals to people. An AI agent decides what to do at runtime. Loopfour does only what was approved.
In a Loopfour workflow, the rule for each accrual is written down and versioned, the controller approves the accrual batch in Slack, and only then does the entry post to NetSuite, QuickBooks, Xero or Sage Intacct with its reversal date. Where AI is used, it does a scoped task, such as extracting the fee and billing terms from a new contract under a confidence threshold, and a person reviews anything below the threshold. No AI sets an accrual amount. Judgment accruals stay with your team, and the workflow records the evidence and the approver. Our post on journal entry automation and the audit explains the evidence each entry carries.
Frequently asked questions
What is the difference between accrued expenses and accounts payable?
Accounts payable is an amount owed for goods or services where the vendor's invoice has been received and recorded. An accrued expense, or accrued payable, is an expense incurred in the period where no invoice has been recorded yet. Both are liabilities, and the accrual is usually reversed once the invoice arrives.
Which month-end accruals can be automated?
Accruals whose amount comes from a record you already hold and whose method does not change month to month are good candidates. Common examples are contracted recurring services, goods received but not invoiced, usage-based vendor charges and wages earned but not yet paid. Each still needs an approved rule, a reversal and a named approver before it posts.
Which accruals should stay judgment calls?
Accruals that depend on an estimate of an uncertain outcome should stay with a qualified person. Examples include bonuses, legal and other loss contingencies, and disputed vendor charges. A workflow can still collect the evidence and record the sign-off, but a person sets the amount.
Should accruals reverse automatically?
Most month-end accruals for expenses awaiting an invoice are reversed on the first day of the next period, so the invoice can post normally without double counting. ERPs such as NetSuite let you set a reversal date when you post the entry. Judgment accruals such as contingencies are usually adjusted, not reversed, until the outcome is known.
Can AI book month-end accruals?
AI can do scoped tasks around accruals, such as extracting amounts from a contract or flagging an unusual pattern for review. The accrual amount should come from an approved rule or a person's estimate, and a named person should approve it. COSO's 2026 generative AI guidance includes a case where an automated accrual missed a vendor's billing change.
What should we check before year-end accruals?
Review every accrual rule and confirm its method still matches the contract or the data source. Compare last year's accruals with the invoices that arrived later, list every judgment accrual with its owner and evidence, and agree the cutoff date and documentation with your auditor before fieldwork.
Conclusion
Month-end accruals split cleanly once you ask where the amount comes from. Accruals computed from contracts, receipts, usage or timesheets run as approved rules with a reversal date, and the controller approves each batch before it posts. Accruals that depend on an estimate stay with the controller, with a workflow that gathers the evidence and records the sign-off. Get the split right before year-end, and the close spends its time on the judgment calls instead of on arithmetic.
Tell us the one workflow your team dreads. We will show it running. Book a demo.