Journal Entry

Definition — what it is

A journal entry is the fundamental record of a financial transaction in double-entry accounting: a dated, balanced set of debits and credits posted to general ledger accounts, with a description and supporting reference. Every number in a contractor's financial statements is ultimately the sum of journal entries, and the requirement that debits equal credits is what keeps the books self-checking. Journal entries are not the same as source documents like invoices or timecards — those are the evidence a transaction occurred, while the journal entry is how that transaction enters the ledger — and they are not the same as the subledgers, which summarize into the general ledger through posted entries. In construction, journal entries carry the accruals, revenue recognition adjustments, over/under billing reclassifications, and cost reallocations that translate project reality into financial statements, which makes their accuracy and traceability a core control.

Also known as: JE, Journal Voucher, GL Entry, Accounting Entry, Adjusting Entry

Why it matters — what it protects

The journal entry is the atom of the audit trail, so its quality determines whether the financial statements can be trusted and defended. Every reported figure decomposes into entries, and an auditor's work is fundamentally the tracing of entries back to their support. An entry without a clear description, reference, and approval is a hole in the record that undermines confidence in everything built above it.

In construction, the most consequential entries are judgmental, not mechanical. Accruals for incurred-but-unbilled cost, revenue recognition and cumulative catch-up adjustments, over/under billing reclassifications, and cost-code reallocations are all posted by journal entry, and each embeds an estimate. These adjusting entries are where reported earnings are actually shaped, which is exactly why they attract control scrutiny.

Journal entries are the primary vector for both honest error and fraud. A miskeyed amount, a reversed debit and credit, or a wrong account distorts the statements silently, while manual entries with weak controls are the classic mechanism for concealment. Segregation of duties, approval thresholds, and support requirements exist because the journal entry is where the books are most exposed.

The discipline of clean entries is what makes month-end close fast and the ledger reconcilable. Recurring accruals that reverse automatically, entries that reference their source, and balanced subledger-to-GL postings are what let a controller close on time and tie the job cost report, the WIP schedule, and the general ledger to each other. Sloppy entries turn every close into a forensic exercise.

Lifecycle — how it moves

1. Trigger and identification

   A transaction or accounting event occurs — an invoice, a payroll run, an accrual need, a revenue adjustment. Someone identifies that a ledger entry is required and which accounts it touches.

2. Drafting

   The entry is written with debits, credits, accounts, amounts, a description, an effective date, and a reference to supporting documentation. An entry that does not balance cannot post, which is the first control.

3. Support attachment

   Source documents or a calculation supporting the amount are attached. Adjusting and manual entries especially need their basis documented, because they are the ones an auditor will question.

4. Review and approval

   A second person reviews and approves the entry, with approval thresholds escalating by amount. Segregation between who prepares and who approves is a core anti-fraud control that a small accounting team often struggles to maintain.

5. Posting

   The approved entry posts to the general ledger, updating account balances. Posting to a closed period, or posting an unbalanced or misdated entry, are the common mechanical failures caught here.

6. Reversal or recurrence

   Accrual entries reverse in the following period automatically so cost is not double-counted, and recurring entries repeat on schedule. A missed reversal is one of the most common causes of period distortion.

7. Reconciliation

   Account balances driven by entries are reconciled — subledgers to the GL, bank to book, job cost to GL. Entries that do not reconcile are investigated and corrected before close.

8. Close and retention

   At period close the ledger is locked and entries are retained as the permanent audit trail. Post-close adjustments require documented reopening or a subsequent-period correcting entry.

Anatomy — the data it carries

Entry number and date

The unique identifier and effective date. The date determines the period the entry hits, and a wrong date misstates period results.

Debit and credit lines

The accounts and amounts, which must balance. A reversed debit and credit posts a real transaction backward and distorts two accounts at once.

GL accounts

The specific ledger accounts affected, which determine how the entry rolls into the financial statements. A wrong account is a silent misstatement.

Amount

The transaction value. Miskeyed amounts are the most common honest error and the reason support and review exist.

Description / memo

The plain-language explanation of what and why. A vague memo makes the entry unauditable and is a control weakness in itself.

Source reference

The link to the invoice, timecard, calculation, or contract behind the entry, the thread an auditor pulls to verify it.

Entry type

Standard, adjusting, accrual, reversing, recurring, or reclassification. The type dictates whether and how it reverses and how closely it is scrutinized.

Preparer and approver

Who created and who authorized the entry, the segregation-of-duties record that anti-fraud controls depend on.

Approval status and threshold

Whether the entry cleared the required approval for its amount, the gate that manual high-value entries must pass.

Reversal flag and date

Whether the entry auto-reverses and when, which prevents accruals from double-counting into the next period.

Cost-code / project reference

For construction, the job and cost code the entry relates to, which is what keeps job cost accounting and the GL reconcilable.

Failure modes — how it breaks

Missed accrual reversal

An accrual is posted but its reversal in the next period is skipped, so the cost is counted twice — once as the accrual and again when the invoice posts. The double count overstates cost in one period and understates it in another, and it is a frequent close-quality defect.

Reversed debit and credit

The entry balances but the debit and credit are swapped, so a real transaction posts backward. Two accounts are wrong by twice the amount, and because the entry balances, the error passes the basic check and hides until reconciliation.

Manual entry without segregation or support

A high-value manual entry is prepared and posted by the same person with no attached support. This is the classic concealment vector, and even when innocent it leaves an unverifiable hole in the audit trail.

Wrong period or closed-period posting

An entry is dated into the wrong period or forced into a closed one, misstating both periods' results. Late entries dated to the prior period without proper reopening corrupt already-reported figures.

Vague or missing description

The memo says 'adjustment' or nothing at all, so no one can later reconstruct what the entry did or why. The transaction may be correct, but it is unauditable and forces guesswork at close and audit.

Cost reclassifications that break job-cost-to-GL tie

An entry reclassifies cost between accounts or cost codes in the GL but the corresponding subledger or job cost record is not updated, so job cost and the GL no longer reconcile. Month-end becomes a manual bridging exercise.

Round-number plug entries

An unexplained round-number entry is posted to force a balance or hit a target, with no transaction behind it. Plugs mask underlying reconciliation problems and are a red flag auditors specifically hunt for.

Metrics — how it is measured

Manual entry volume and value

Count and dollar value of manual entries relative to system-generated ones. High manual volume signals weak automation and elevated error and fraud risk.

Entries lacking support or description

Share of entries without an attached reference or a meaningful memo. A direct measure of audit-trail quality.

Segregation-of-duties exceptions

Entries prepared and approved by the same person. Each is a control breach and a concentration of fraud risk.

Missed or reversed-in-error reversals

Accruals whose reversal was skipped or mis-timed. A leading cause of period distortion and a close-quality signal.

Post-close and prior-period adjustments

Entries dated into already-closed periods. High volume indicates a rushed or unreliable close.

Reconciliation break count

Accounts where entries leave the subledger, bank, or job cost out of balance with the GL. The count of unresolved breaks measures ledger integrity.

The AI shift — what actually changes

Conversational

The ledger becomes interrogable at the entry level. You ask which manual entries this period lack support, which accruals were posted without a scheduled reversal, and which high-value entries were prepared and approved by the same person — and get the specific entries and their memos cited, so review starts from exceptions rather than from scrolling the journal.

Generative

Routine and adjusting entries are drafted from their source. Given an invoice batch, a payroll run, or an accrual calculation, a model produces balanced entries with correct accounts, descriptions, references, and reversal flags, and — for judgmental accruals and reclassifications — states the basis so a human approves the reasoning rather than re-keying the mechanics.

Orchestrated

The entry stops being a manual bridge between systems. Subledger activity, payroll, and revenue calculations generate proposed entries, which are checked for balance, account correctness, and period, matched to their source, and reconciled against the affected account balances — so a broken job-cost-to-GL tie or a missing reversal is caught at posting rather than at close.

Autonomous

The routine posting runs unattended: system-sourced entries drafted, balanced, referenced, and posted within thresholds; accruals scheduled with their reversals; reconciliations checked continuously; and any entry that is manual, high-value, unsupported, period-crossing, or breaks a reconciliation flagged — while humans own every judgmental adjustment, every entry above the approval threshold, and anything the system cannot tie to a source.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Reviewing the journal for control weaknesses before close.

Audit this period's journal entries for control and quality issues before we close. Flag every manual entry that lacks an attached source reference or has a vague description like 'adjustment.' Identify entries prepared and approved by the same person, and any that exceed our approval threshold without the required sign-off. Find accruals posted this period that have no scheduled reversal, and any reversals that were missed from last period, since those double-count cost. Flag round-number entries with no transaction behind them and any entry dated into a closed period. For construction cost reclassifications, check that job cost still ties to the GL. Cite the entry numbers, amounts, and memos behind each finding and rank by financial-statement risk.

What good output looks like: A control-focused journal review that names unsupported, segregation-breaching, unreversed, and period-crossing entries with their amounts and memos, ranked by risk, plus the job-cost-to-GL ties they break.

Follow-ups:

• For the unsupported high-value entries, draft the documentation requests to the preparers.
• Which missed reversals will distort next period, and by how much?
• Where a reclassification broke the job-cost-to-GL tie, show me the reconciling entry needed.

Generative — Month-end and you need the standard adjusting entries drafted.

Draft this month's adjusting journal entries from the data attached. Create accrual entries for cost incurred but not yet invoiced, with the calculation as the support and an automatic reversal flagged for next period. Draft the over/under billing reclassification entries from the WIP schedule, moving amounts to contract asset and contract liability accounts. Draft the revenue recognition entry and any cumulative catch-up from the estimate changes provided. For each entry, provide balanced debit and credit lines, the correct GL accounts, a clear description, the source reference, the entry type, and the reversal treatment. Present them as a review-ready package, note which require approval above our threshold, and flag any entry whose amount or account you are not confident about rather than guessing.

What good output looks like: A review-ready set of balanced adjusting entries — accruals with reversals, over/under reclassifications, revenue and catch-ups — each with accounts, memo, source reference, and type, with approval-threshold and low-confidence items flagged.

Follow-ups:

• Show me the reversal entries these accruals will generate next period.
• Which of these entries change reported earnings, and by how much each?
• Reconcile the over/under entries back to the WIP schedule they came from.

Orchestrated — You want entries generated across systems and reconciled as they post.

Generate and reconcile this period's journal entries across the connected systems. From the payables subledger, payroll, and revenue calculations, propose the entries needed to post activity to the general ledger, each balanced with correct accounts, descriptions, references, and reversal flags. As each entry is proposed, verify it against its source, confirm it will not post to a closed period, and reconcile the affected account balances — subledger to GL, and for construction, job cost to GL. Flag every entry that breaks a reconciliation, lacks a source, or crosses a period boundary. Return the proposed entries grouped by type, the reconciliation status of each affected account, and a list of exceptions with the specific accounts and amounts that do not tie.

What good output looks like: Cross-system proposed entries reconciled to their affected accounts as they are generated, with reconciliation breaks, missing sources, and period-crossing entries flagged and attributed to cause rather than posted blindly.

Follow-ups:

• For accounts that do not reconcile, tell me whether it is a missing entry or a coding error.
• Which proposed entries need human approval before posting, and why?
• Show me the subledger-to-GL tie-out after these entries would post.

Autonomous — Standing policy for how routine journal entries should be posted and controlled.

Post routine journal entries continuously under these rules. Draft system-sourced entries from the payables, payroll, and revenue subledgers, balanced with correct accounts, clear descriptions, source references, and reversal flags, and post only those below the approval threshold that reconcile cleanly to their source and affected accounts. Schedule every accrual with its reversal so nothing double-counts. Reconcile subledger, bank, and job cost to the GL each period and flag breaks. Never post a manual or judgmental entry — accruals requiring estimation, revenue recognition, over/under reclassifications, cost reclassifications, or anything above the threshold — without human approval, and never post to a closed period. Route all such entries to me with their support and reasoning, and give me a daily exception queue of entries needing approval, reconciliation breaks, and missed reversals rather than the full journal.

What good output looks like: A controlled posting process where routine system-sourced entries post automatically within thresholds with reversals scheduled, and every manual, judgmental, above-threshold, or period-crossing entry stays a human decision, with exceptions escalated and a full audit trail.

Follow-ups:

• Show me the manual and above-threshold entries you queued and what I approved.
• Report our manual-entry ratio and reconciliation-break count trend this quarter.

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Manual and undocumented

   Entries are keyed by hand, often without support or a second reviewer, and reversals are tracked by memory. The audit trail is thin and close is a forensic exercise.

1. Level 1 — Controlled manual

   Entries carry descriptions and references, approval thresholds and segregation of duties are enforced, and accruals reverse on schedule. Reliable but labor-intensive.

2. Level 2 — System-sourced and reconciled

   Most entries are generated from subledgers, reconciliations tie subledger, bank, and job cost to the GL each period, and manual entries are the monitored exception.

3. Level 3 — Assisted

   Routine and adjusting entries are drafted from source with correct accounts and reversals, and control exceptions — unsupported, segregation-breaching, unreversed entries — are flagged for review.

4. Level 4 — Operated

   Routine system-sourced entries post and reconcile unattended within thresholds, while humans own every judgmental adjustment, above-threshold entry, and reconciliation exception.

Common questions

Why must every journal entry balance?

Because double-entry accounting records every transaction as equal debits and credits, which keeps the accounting equation intact and makes the books self-checking. If an entry does not balance, the general ledger will not tie out and the financial statements cannot be prepared, so accounting systems refuse to post unbalanced entries. The balance requirement is the first and most basic control, though it catches only arithmetic errors — a balanced entry can still hit the wrong accounts or reverse its debit and credit.

What makes an adjusting entry different from a standard one?

A standard entry records a completed transaction with clear source documentation, like an invoice or a payment. An adjusting entry records an accounting estimate or allocation that has no single invoice behind it — an accrual for unbilled cost, a revenue recognition adjustment, a depreciation charge — and it embeds judgment. Adjusting entries are where reported earnings are actually shaped, which is why they demand documented calculations, review, and, for accruals, an automatic reversal so the estimate does not persist into the next period.

Why do auditors focus so heavily on manual journal entries?

Because manual entries are the point in the ledger most exposed to both error and fraud. System-generated entries follow rules and leave a clean source trail, but a manual entry can post any amount to any account, so it is the classic vector for concealment and for honest mistakes alike. Auditors test manual entries for support, segregation of duties, round-number plugs, and unusual timing, because a well-run set of automated postings with a small, well-controlled set of manual exceptions is the signature of a trustworthy ledger.