A journal entry can balance perfectly and still be wrong.
The debits and credits may tie, but that does not mean the entry is supportable, approved, or recorded in the right period. A weak journal entry can create audit issues, distort reporting, and slow down the close when nobody can explain why it was posted.
This guide covers the basics of journal entries, how they are recorded, common examples, approval controls, and what changes when accounting teams manage them at month-end.
What a journal entry actually is
A journal entry is the formal record of a financial transaction in an organization’s accounting system. It captures the accounts affected, the amounts debited and credited, the date, a description of the business purpose, and the supporting evidence. Under double-entry accounting, every entry must balance: total debits equal total credits.
Most definitions stop there. They describe the syntax but miss the control dimension entirely.
A journal entry is a controlled accounting assertion. It states that this expense belongs in this period, this liability existed at month-end, this balance sheet account required correction, this cost belongs in COGS rather than SG&A. Every one of those claims needs to be supported, reviewable, and approved by someone with authority to challenge it.
The debits and credits are the syntax. The rationale, support, policy basis, approval, and evidence trail are what make the entry defensible. The accounting conclusion itself also needs to hold up under GAAP. Whether the entry involves revenue recognition under ASC 606, capitalization under ASC 340, or a prior-period correction under ASC 250, the treatment has to be traceable to a specific standard or documented company policy, not just internal convention.
Under SOX Section 404, PCAOB AS 2201, and the COSO Internal Control Framework, the approval and documentation around a journal entry are control activities that support reliable financial reporting. The entry is not complete when it balances. It is complete when the accounting conclusion, support, and approval trail can stand on their own.
Debits and credits in journal entries
Every journal entry moves value between accounts using two sides: debits and credits. Each account type has a normal balance, and debits or credits either increase or decrease that balance depending on the account type.
Account type | Normal balance | Debit effect / Credit effect |
Assets | Debit | Debit increases / Credit decreases |
Liabilities | Credit | Debit decreases / Credit increases |
Equity | Credit | Debit decreases / Credit increases |
Revenue | Credit | Debit decreases / Credit increases |
Expenses | Debit | Debit increases / Credit decreases |
A cash sale increases cash (debit an asset) and increases revenue (credit revenue). A loan payment decreases cash (credit an asset) and decreases the loan liability (debit a liability). If the entry does not balance, the accounting is wrong.
How to record a journal entry
Identify the transaction. Determine what economic event occurred and when. Cutoff errors start here: the wrong date lands the entry in the wrong period regardless of everything else.
Identify the accounts affected. Determine which GL accounts are impacted. Reference the chart of accounts, confirm account numbers, and identify any dimensions such as department, class, or location.
Assign debits and credits. Apply the rules from the table above. The entry must balance before you proceed.
Enter amounts and write the description. Include the source reference, business rationale, and any reversal date. “Reclass per controller” is not a description. “Reclassify $42,000 of March freight-in costs from SG&A to COGS per direct fulfillment cost policy” is.
Attach support and route for approval. Attach source evidence before submitting. The entry posts only after approval.
General journal vs. special journals
A general journal is the catch-all record where any transaction can be recorded. It handles non-routine entries, adjustments, corrections, and anything that does not fit a specialized workflow.
Special journals are purpose-built for high-volume, repetitive transaction types: sales, cash receipts, purchases, and cash disbursements. In modern ERP environments, subledger modules like AR, AP, and payroll serve the same function. The general journal handles what the subledgers do not: manual accruals, reclassifications, corrections, and period-end adjustments.
This is where manual journal entry risk concentrates. Subledger transactions follow structured, system-enforced workflows. General journal entries do not. They are prepared manually, often under time pressure, with no built-in validation of account mapping, period, or support completeness. That combination of judgment, volume, and limited structure is why auditors focus their JE testing here first.
The anatomy of a complete journal entry
A complete journal entry has two layers: the record itself and the packet around it. Controllers who have been through a SOX audit know that every missing component below creates a specific problem.
Component | What it contains | What breaks when it is missing |
Posting date and period | Transaction date and accounting period | Cutoff errors and wrong-period reporting |
Entity / subsidiary | Legal entity or subsidiary | Entry lands in wrong books or creates consolidation issues |
Accounts | GL account numbers for each debit and credit line | Misclassification and misstated financial statement lines |
Debit and credit amounts | Balanced amounts for each line | Entry fails validation or posts wrong economics |
Dimensions | Department, class, location, project, customer, product | Bad reporting cuts, variance noise, and allocation errors |
Memo / description | Explanation of what happened and why, specific enough that a reviewer can re-perform the logic without asking the preparer. | “Reclass per controller” fails audit. “Reclassify $42,000 of March freight-in from SG&A to COGS per direct fulfillment cost policy” passes. |
Reversal flag / date | Whether the entry reverses, and when | Accruals linger, double-count, or reverse in the wrong period |
The types of journal entries you will actually book
Not every journal entry carries the same risk. A recurring payroll summary is a different problem from a top-side correction posted late in close. Teams that treat them the same over-review low-risk entries and under-review high-risk ones.
Type | When and why | What makes it risky |
Standard | Routine transactions not captured by subledger modules (e.g., bank fees, wire transfers) | High volume makes weak review easy to miss |
Adjusting | End-of-period entries to bring balances into correct position (e.g., depreciation, allowance updates) | Often schedule-driven and time-sensitive |
Reversing | Posted at period start to reverse a prior-period accrual, preventing double-counting | Easy to miss, duplicate, or reverse in the wrong period |
Reclassifying | Moving an amount between accounts, departments, or entities without changing the total | Net-zero entries are easy to under-review |
Accrual | Recording expenses incurred or revenue earned but not yet invoiced or collected | Requires judgment and strong support; stale assumptions accumulate quietly |
Deferral | Postponing recognition of revenue received in advance or expenses paid in advance | Release pattern can drift from economic reality |
Compound | Single entry with more than one debit, more than one credit, or both (e.g., payroll split across departments) | A single misallocated line can be invisible in the total |
Consolidation and elimination | Removing intercompany balances when preparing consolidated financial statements | Sits above the operational subledger flow |
Top-side | Manual adjustments at the consolidation level to correct or reclassify entity-level data | Bypasses normal entity-level controls; carries heightened scrutiny |
Closing | Year-end entries to zero out temporary accounts and transfer net result to retained earnings | Errors carry into opening retained earnings and affect the following year’s equity rollforward |
Opening entries establish opening balances when a new entity or accounting period begins, bringing forward prior-period closing balances or recording initial capital contributions.
Transfer entries move balances between accounts or cost centers for planned, recurring allocation workflows, such as allocating shared service costs from a central overhead pool to operating departments.
Journal entry examples: from basic entries to close adjustments
Before looking at close-specific entries, it helps to start with three simple journal entries. These show the basic mechanics of debits, credits, and compound entries.
Basic journal entry examples
Cash sale: $5,000 product sold for cash
Date | Account | Debit | Credit |
Jun 15 | Cash (1000) | $5,000 | |
Jun 15 | Sales Revenue (400100) | $5,000 |
Office supplies purchase: $800 paid in cash
Date | Account | Debit | Credit |
Jun 18 | Office Supplies Expense (640010) | $800 | |
Jun 18 | Cash (1000) | $800 |
Loan payment: 2,000 monthly payment ($1,400 principal, 600 interest)
Date | Account | Debit | Credit |
Jun 30 | Loan Payable (2100) | $1,400 | |
Jun 30 | Interest Expense (710010) | $600 | |
Jun 30 | Cash (1000) | $2,000 |
This is a compound entry: two debits, one credit. Total debits equal total credits: $2,000.
Once the mechanics are clear, the examples below show the types of judgment-heavy entries controllers actually deal with during close.
Close entry 1: unbilled revenue accrual with reversal
A SaaS company completed a $90,000 implementation project on March 28. The invoice will not be sent until April 5. Revenue belongs in March under the accrual basis.
March 31 accrual entry:
Date | Account | Debit | Credit |
Mar 31 | Unbilled Accounts Receivable (1250) | $90,000 | |
Mar 31 | Service Revenue (400100) | $90,000 |
Memo: “Accrue $90,000 implementation revenue for [Customer]. SOW #2024-0147, all deliverables completed 3/28. Invoice to be issued 4/5. Reverses 4/1.”
April 1 reversing entry:
Date | Account | Debit | Credit |
Apr 1 | Service Revenue (400100) | $90,000 | |
Apr 1 | Unbilled Accounts Receivable (1250) | $90,000 |
When the invoice posts through AR on April 5, it debits Accounts Receivable and credits Service Revenue. The reversal prevents double-counting. Without it, both March and April show $90,000 of revenue for the same project. If it reverses twice, April understates revenue. If it reverses in the wrong period, both months are misstated.
Evidence: Statement of work with completion date, customer completion confirmation, revenue recognition policy memo confirming point-in-time recognition, billing schedule showing April 5 invoice date.
Close entry 2: expense reclassification from SG&A to COGS
During the March close, the controller spots $42,000 of packaging materials coded to Marketing Expense (630020). These are direct materials and belong in Cost of Goods Sold (500100). The AP team used the wrong default account on the vendor record.
March 31 reclassification entry:
Date | Account | Debit | Credit |
Mar 31 | Cost of Goods Sold (500100) | $42,000 | |
Mar 31 | Marketing Expense (630020) | $42,000 |
Memo: “Reclassify $42,000 of packaging materials from Marketing Expense to COGS. Vendor: PackageCo, PO #3847. Original AP coding used default vendor account mapping. Corrected per updated cost allocation policy. No reversal needed. Vendor record updated to prevent recurrence.”
This entry is net-zero to the income statement total but moves $42,000 between line items. Gross margin decreases and operating expenses decrease by the same amount. A reviewer who only checks that total expenses are unchanged will miss this entirely.
Evidence: Original AP invoice, purchase order, updated vendor record showing corrected account mapping, controller approval.
Close entry 3: prior-period error correction (ASC 250)
During Q2 close, the controller discovers $175,000 of SaaS implementation labor incorrectly capitalized as contract fulfillment assets across Q4 of the prior year and Q1 of the current year. After reviewing ASC 340-40, the controller concludes the costs should have been expensed as incurred.
The first question is materiality. For a company with 80 million in annual revenue and $11.7 million in operating income, 175,000 is approximately 0.2% of revenue and 1.5% of operating income. Quantitatively, this may fall below typical thresholds. But SAB 99 requires qualitative consideration too. The error affects gross margin, spans two reporting periods, and involves a judgment area auditors will examine. The controller concludes the error is immaterial to prior periods and records an out-of-period correction rather than restating previously issued financial statements.
June 30 correcting entry:
Date | Account | Debit | Credit |
Jun 30 | Implementation Labor Expense (620050) | $175,000 | |
Jun 30 | Contract Fulfillment Asset (1400) | $175,000 |
Memo: “Record out-of-period correction for prior-period capitalization error. 175,000 of SaaS implementation labor incorrectly capitalized in Q4 FY25 ($95,000) and Q1 FY26 (80,000). Costs should have been expensed under company policy and ASC 340-40. Immaterial to prior periods individually (SAB 99 analysis attached). Corrected as out-of-period adjustment per ASC 250. No restatement required.”
Evidence: Materiality analysis (quantitative and qualitative per SAB 99), ASC 340 policy memo, detail of costs by quarter, controller sign-off, auditor communication documented.
The correcting entry itself is two lines. The judgment behind it requires understanding ASC 250, SAB 99, and the company’s specific facts. That judgment, and the evidence trail supporting it, is what separates a defensible correction from an audit finding.
The JE packet minimum standard
Most JE review failures are not caused by wrong numbers. They are caused by incomplete packets that force the reviewer to chase evidence after the fact. Every non-trivial journal entry should include the following before submission:
Business rationale. Why does this entry exist? “Record accrual” is not a rationale. “Accrue $90,000 implementation revenue for [Customer], SOW #2024-0147 completed 3/28, reverses 4/1” is.
Source evidence attached. The supporting document itself, not just a reference to it. Evidence that lives only on someone’s desktop does not exist for audit purposes.
Tie-out to schedule or calculation. “Per amortization schedule v3, tab Q1, row 14” is a tie-out. “Per schedule” is not.
Policy basis or accounting conclusion. For judgment-heavy entries, state the accounting policy or standard that supports the treatment. This matters most for entries touching ASC 250, ASC 340, or revenue recognition.
Preparer and reviewer/approver trail. Who created the entry and who approved it for posting. Under PCAOB AS 2201, auditors evaluate whether the control operated at the right point in the process.
Review timestamp before posting. Timestamps demonstrate that review happened before the entry posted. A pre-posting review is a preventive control. A post-hoc review is a detective control. Under SOX 404, the question is who reviewed it, what they reviewed, when, and whether exceptions were addressed.
Reversal ownership if applicable. When does it reverse? Is the reversal automatic or manual? If manual, who is responsible? Undocumented reversal rules are how accruals get double-counted.
Exception or root-cause note if applicable. If the entry corrects an error or overrides a standard process, document what went wrong and what will prevent recurrence.
The JE approval matrix
Match the level of review to the level of risk. The preparer should never be the approver, and approval should happen before the entry posts.
JE category | Risk level | Required reviewer / approver | Required support | Escalation trigger |
Standard / recurring | Low to Medium | Designated reviewer per close policy | Source report, template support, prior-period tie-out | Amount exceeds materiality threshold or account mapping deviates from template |
Accrual / deferral | Medium | Designated reviewer; Controller if material or judgment-heavy | Calculation schedule, source support, policy basis, reversal or release logic | Estimate changed from prior period, no reversal date set, or amount exceeds materiality threshold |
Reclassifying | Medium to High | Designated reviewer; Controller if KPI-sensitive | Original posting, rationale, policy basis, root-cause note | Entry moves costs between gross margin and operating expense lines, or affects a KPI reported to the board |
Error correction | High | Controller or designated senior reviewer | Error analysis, corrected calculation, root cause, preventive step | Error spans multiple periods, affects a previously reported balance, or root cause is systemic |
Prior-period error correction / ASC 250 | Critical | Controller; CFO/CAO if material or reporting-sensitive | ASC 250 memo, SAB 99 materiality analysis, auditor communication if relevant | SAB 99 qualitative factors present, auditor involvement required, or restatement is being evaluated |
Consolidation / elimination | High | Consolidations Lead / Controller | Intercompany confirmation, elimination schedule, entity tie-out | Intercompany balances do not agree across entities or elimination differs from prior period without explanation |
Top-side | High to Critical | Controller; CFO/CAO if material or reporting-sensitive | Detailed rationale, consolidation support, entity-level tie-out, approval trail | Entry was not anticipated in the close plan, affects a reported segment, or lacks a corresponding entity-level entry |
How this works in NetSuite
NetSuite provides two approaches to journal entry approval. The basic approach uses the “Require Approvals on Journal Entries” accounting preference, which adds an Approved checkbox to each record. The more structured approach uses SuiteFlow or custom approval routing to direct entries to specific approvers by amount, subsidiary, or other criteria. Both enforce the core control: unapproved entries do not post.
The default configuration does not prevent self-approval, so teams should verify that the workflow explicitly routes entries to a different approver than the preparer.
NetSuite supports memorized transactions for recurring journal entries. Teams should verify that memorized transactions created before enabling the Approval Routing feature are governed by the new workflow. Older templates may need review or re-creation.
Once an entry is approved and posted, correcting it requires posting a separate reversing entry and resubmitting a corrected entry through the approval workflow. Teams that catch errors before approval save significant rework.
For intercompany journal entries, NetSuite OneWorld creates mirror postings across subsidiaries. Approval may apply to each subsidiary independently, meaning the same entry can be approved on one side and pending on the other. Controllers managing multi-entity closes should track approval status across the group.
In practice, many NetSuite teams still supplement the native workflow with spreadsheets because the preparation layer sits outside the journal record. The posting step is system-native. Everything before it often is not.
Where teams get stuck
Net-zero entries that hide real mistakes. A $150,000 reclassification nets to zero on the trial balance, so total expenses are unchanged. But the entry moved costs between segments, changing the gross margin the board reviews most closely. Net-zero entries receive less scrutiny, which is precisely why they are the most common vehicle for misclassification errors.
Copy-paste accruals that never get revisited. A 65,000 monthly accrual for legal fees was set up 14 months ago based on a litigation estimate. The litigation settled eight months ago for $30,000. The accrual still posts every month at 65,000. Without a defined expiration or reassessment date, recurring entries operate on autopilot and become the most dangerous items in the ledger.
“Temporary” reclassifications that become permanent. A controller posts a reclassification in January to move 200,000 of hosting costs while the cost allocation methodology is being finalized. It carries forward into February, then March. When the final methodology is approved in Q3, it differs from the reclassification by 45,000 per month. Unwinding five months of incorrect classifications takes longer than the original entry took to post.
Missing support that surfaces during audit. The preparer saved the calculation locally. The approver reviewed it on screen but did not attach it. When the auditor requests support six months later, the team spends two hours reconstructing evidence for an entry that took five minutes to post.
Approvers who review without re-performing. An approver who clicks “Approve” without inspecting the support is performing a ceremony, not a control. For the approval to function as a control, the reviewer needs to verify the amount against the support, confirm the account mapping, check the period, and assess consistency with prior periods. That distinction is what auditors evaluate under PCAOB AS 2201.
What changes at month-end
Journal entry work during the month is relatively steady. At month-end, volume spikes and the nature of the work changes.
The volume problem is predictable. A company that posts 30 to 40 journal entries during the month may post 150 to 200 during the close window. Accruals, deferrals, depreciation runs, prepaid amortizations, intercompany eliminations, and correcting entries all converge into the same 72- to 96-hour period.
The quality problem is less obvious but more dangerous. Under time pressure, descriptions get shorter, support gets attached later, and reviewers approve batches instead of individual entries. The entries that receive the least scrutiny are often the ones that carry the most risk: late accruals booked on the last day, top-side adjustments made after the preliminary trial balance is pulled, correcting entries created under pressure to make the numbers tie.
The interdependency problem compounds both. A correcting entry posted at 4 PM on day three of close can invalidate flux commentary written at 9 AM the same day. Journal entries are the mechanism through which every adjustment flows, and the close is a network of dependencies.
The solution is not more reviewers. It is fewer entries that require manual assembly in the first place.
What agentic AI changes about journal entries
What AI changes is not the accounting principle. It is the preparation burden around the entry.
The most time-consuming part of journal entry work is not posting the entry. It is everything before the entry is ready to post: gathering source data, formatting it for the ERP, determining the correct accounts and amounts, writing a description, attaching evidence, and routing to the right approver. For a single entry, this takes minutes. For 150 entries during a close window, this is where the days go.
This is where platforms like Maxima change the workflow. Preparation shifts from the accountant to an agent, and the accountant’s role shifts from assembling entries to evaluating the proposed accounting.
For recurring, rule-driven entries like bank cash activity, payroll, and benefits, a controller configures matching rules that map transaction types from source data to journal entry templates. New transactions arrive, the platform applies the rules, populates the header and line detail, writes the description, and routes the drafted entry for approval. Employee-level payroll data can be aggregated to the department level before posting, keeping sensitive compensation detail out of the GL. The entries arrive pre-prepared with source data attached. The controller evaluates the output, not the input.
For complex entries requiring judgment, like stock-based compensation from Carta or multi-step accrual calculations, a controller can instruct the agent in plain language. The agent reads the source data, builds the intermediate calculations, produces the final figures, and feeds them into the journal entry workflow. Before executing, the agent presents its plan and waits for approval. Every step is logged.
For structured close tasks with documented procedures, the agent reads the SOPs attached to each checklist task and executes the workflow: run the journal entry automation, run the reconciliation, prepare manual entries for any unreconciled items. The controller opens prepared work with source data, rules applied, calculations performed, and exceptions surfaced.
In all three modes, the control pattern is the same: the agent prepares, and the human evaluates, challenges, and approves. Proposed entries do not post without approval, and the audit trail captures every action the agent took, every source it referenced, and every rule it applied. Evidence is assembled as the work is performed, not reconstructed after the fact.
What remains human-owned is exactly what should remain human-owned: policy judgment, materiality assessment, approval decisions, non-routine exception review, and final sign-off.
See how Maxima helps accounting teams prepare entries that arrive ready for review.
Frequently asked questions
What is a journal entry in accounting?
A journal entry is the formal record of a financial transaction in an organization’s accounting system. It captures the accounts affected, the amounts debited and credited, the date, a description of the business purpose, and the supporting evidence. Balance alone does not make the entry review-ready. The evidence, rationale, and approval trail are what make it defensible.
What are the main types of journal entries?
The types most commonly encountered during close are standard, adjusting, reversing, reclassifying, accrual, deferral, compound, consolidation and elimination, top-side, and closing entries. They differ not just by form but by risk and control burden.
Who should approve journal entries?
Standard and recurring entries can be approved by a designated reviewer. Error corrections, material reclassifications, and top-side entries should require controller review. Prior-period corrections under ASC 250 should escalate to controller and CFO/CAO if material. The preparer should never be the approver.
What is the difference between a standard and an adjusting journal entry?
A standard journal entry records a routine transaction not captured through a subledger, such as a bank fee or recurring allocation. An adjusting journal entry is posted at period-end to bring the books into the correct accounting position. Accruals, deferrals, depreciation, and allowance updates are common examples. Adjusting entries usually require more support because they involve cutoff, estimates, or management judgment.
How do you document a journal entry for audit?
A journal entry packet should include the business rationale, source evidence, tie-out to the calculation or schedule, policy basis where judgment is involved, preparer and reviewer/approver trail, and evidence that review occurred before posting. The goal is that a reviewer or auditor can re-perform the logic without reconstructing the entry from emails, spreadsheets, or memory.
Can journal entries be automated?
Yes, but the best automation opportunity is the preparation layer, not just the posting step. Systems can pull source data, transform it, apply rule logic, prepare journal lines, assemble support, and route the proposed entry to the right reviewer. Entries involving estimates, materiality, error correction, or policy judgment still require human evaluation and approval.
What is a reversing journal entry and when do you use it?
A reversing entry is posted at the beginning of a new period to reverse a prior-period accrual. It prevents the transaction from being counted twice when the actual invoice or payment posts through the normal subledger workflow. Reversing entries should be flagged at the time the original accrual is created, with the reversal date documented in the entry.
What is a top-side journal entry?
A top-side entry is a manual adjustment booked at a parent or consolidation level rather than through the operating subledger workflow. Because it often bypasses normal entity-level controls, it requires stronger support and approval. Controllers and auditors apply heightened scrutiny to top-side entries.
What makes a journal entry high risk?
Non-routine nature, high materiality, prior-period correction, manual top-side posting, KPI sensitivity, missing support, unusual account combinations, and weak approval lineage all increase JE risk. The most dangerous journal entry is often not the largest one. It is the one the team has normalized.
What is a compound journal entry?
A compound journal entry has more than one debit line, more than one credit line, or both. A payroll entry is a common example: gross wages split across multiple department expense accounts on the debit side, while net payroll payable, payroll taxes payable, and benefits payable each appear as separate credit lines. Compound entries are efficient but require careful line-by-line review. A single misallocated line can be invisible when reviewers focus only on whether the entry balances in total.
What is a closing journal entry?
A closing entry is posted at year-end to zero out temporary accounts, specifically revenue, expense, and dividend accounts, and transfer the net result to retained earnings. Closing entries reset the income statement so it starts fresh in the new fiscal year. Errors carry directly into the opening retained earnings balance and affect the equity rollforward in the following year.
What is the difference between a general journal and special journals?
A general journal records any transaction and handles non-routine entries, adjustments, and corrections. Special journals are purpose-built for high-volume, repetitive transaction types such as sales, cash receipts, purchases, and cash disbursements. In modern ERP environments, subledger modules like AR, AP, and payroll serve the same function. The general journal handles what the subledgers do not, which is where most manual journal entry risk concentrates.
Move closer to an audit-ready, continuous close
Request demo
Insights, news and content
The latest
See all
