What is Rejected Journal Entry?
Definition
Rejected Journal Entry is an accounting journal entry that has been returned, declined, or not accepted for posting because it does not meet required review, validation, approval, support, coding, or policy standards. A journal may be rejected when the amount is unsupported, the account coding is incorrect, the entry is incomplete, the approval route is wrong, or the accounting treatment needs correction.
A rejected journal entry is an important control signal in financial reporting because it shows that the entry requires further attention before it can affect the general ledger. Rejection helps finance teams preserve ledger accuracy, close discipline, approval evidence, and audit readiness.
How Rejected Journal Entry Works
The rejection usually happens during validation, review, approval, or posting checks. A preparer submits the journal with account details, debit and credit amounts, entity, period, explanation, and supporting documents. The reviewer then checks whether the entry is accurate, balanced, supported, and aligned with accounting policy. If the reviewer identifies an issue, the journal is rejected with comments and returned for correction.
For example, a journal may debit consulting expense but credit the wrong liability account. The reviewer rejects the entry, explains the coding issue, and asks the preparer to revise the account combination. Once corrected, the entry can be resubmitted for review and approval.
Submission: The preparer creates and submits the journal for review.
Review: The approver checks support, coding, amount, and policy treatment.
Rejection: The journal is returned with a reason and correction request.
Resubmission: The preparer updates the journal and sends it back for approval.
Core Components
The core components of a rejected journal entry include rejection reason, preparer name, reviewer comments, journal category, account coding, posting period, supporting evidence, correction status, resubmission date, and audit trail. These details help finance teams understand why the journal was not accepted and what needs to be resolved.
A Standard Journal Entry Template helps reduce avoidable rework by capturing consistent fields such as entity, account, amount, description, reversal date, and support. Smart Journal Entry Classification can group rejected entries by source, account, preparer, entity, value, and issue type so finance teams can identify repeated correction themes.
Rejected entries may include a Reconciliation Journal Entry with unsupported variance, a Consolidation Journal Entry with incorrect elimination logic, or an Intercompany Journal Entry where the trading partner or entity mapping needs revision.
Controls and Governance
Rejected journal entries are closely connected to journal controls because they prevent incomplete or unsupported entries from entering the ledger. Segregation of Duties (Journal Entry) separates preparation, review, approval, and posting responsibilities so that one user does not control the full journal lifecycle.
A Preventive Control (Journal Entry) helps stop journals from posting when required fields, support, approvals, or account validations are incomplete. A Detective Control (Journal Entry) helps identify rejected, corrected, duplicate, late, or unusual journals after submission so reviewers can monitor recurring issues and close activity.
Strong Journal Entry Governance defines rejection reasons, correction standards, approval rules, documentation expectations, and escalation paths. This keeps journal decisions consistent across entities, departments, and reporting periods.
Practical Finance Use Cases
Rejected journal entries appear during month-end close, account reconciliation, tax accounting, treasury accounting, fixed asset accounting, intercompany accounting, and consolidation. A Non-Standard Journal Entry may be rejected if it includes unusual account combinations or lacks enough explanation for a judgment-based adjustment.
A Rule-Based Journal Entry may be rejected when it fails a configured rule, such as invalid cost center, closed accounting period, missing attachment, restricted account, or unbalanced debit-credit amount. In automated environments, Journal Entry Automation can support rejection routing, reviewer comments, resubmission tracking, and exception dashboards.
Practical Example
Assume a finance team submits a $58,000 marketing accrual in September. The journal debits marketing expense for $58,000 and credits accrued liabilities for $58,000. The reviewer rejects the entry because the attached campaign schedule supports only $51,500 of services received in September, leaving $6,500 without sufficient evidence.
The preparer reviews the campaign support, updates the journal to $51,500, and resubmits it with a corrected calculation. The revised journal debits marketing expense for $51,500 and credits accrued liabilities for $51,500. This supports accrual accounting by recording only the supported expense in the correct period.
Review and Resolution
A rejected journal entry should include clear reviewer comments so the preparer can correct the issue efficiently. Good rejection comments explain whether the issue relates to account coding, amount support, period cutoff, approval route, documentation, reversal logic, or accounting policy.
Finance teams should track rejected entries by reason, preparer, entity, account, journal type, and close day. This helps identify training needs, template improvements, recurring coding issues, and areas where review rules can be strengthened.
Best Practices
Effective rejected journal entry management depends on clear rejection codes, practical templates, complete support, and timely resubmission. Finance teams should make rejection comments specific enough for the preparer to correct the entry without ambiguity.
Use standard rejection reasons for support, coding, period, approval, and policy issues.
Require corrected journals to retain the original rejection history.
Track repeated rejection patterns by preparer, entity, and account.
Prioritize material rejected journals during the close calendar.
Review rejected journal trends after each reporting cycle.
Summary
Rejected Journal Entry is a journal entry that has been returned or declined because it does not meet required accounting, support, approval, validation, or policy standards. It improves financial reporting accuracy, audit readiness, close discipline, and business performance visibility by ensuring that only corrected, supported, and approved entries affect the general ledger.
