What a Journal Entry Is, and What Makes One Valid

A journal entry is the basic unit of bookkeeping — a dated record with a short memo describing what happened, and two or more lines underneath it, each naming an account and an amount. The one hard rule: the amounts across all the lines must net to zero. That requirement isn't a formatting nicety; it's the entire mechanism that makes double-entry bookkeeping work.

Take the same example from earlier: $120.50 spent at Home Depot on materials, paid from checking. As a journal entry, that's a date, a memo like "Home Depot #4021 — materials," and two lines: Materials expense debited $120.50, Checking credited $120.50. Two lines, one event, net effect zero.

Where entries come from varies. You or your AI assistant can post one directly by hand — a manual adjustment, a correction, something with no bank transaction behind it. Far more commonly, an entry gets created automatically the moment you categorize a bank transaction: the bank's side of the entry is filled in for you, and categorizing is really just naming the other side. Either way, every entry records which of these paths produced it, so you can always trace a number back to whether a person typed it, it came from a bank import, or an AI assistant posted it.

For an entry to be accepted, it needs at least two lines — one debit, one credit, at minimum — and the amounts have to sum to exactly zero, not approximately. Amounts are whole cents, not dollars-and-cents decimals: a $12.50 credit is entered as -1250, not -12.50. That's a real, specific gotcha worth knowing about if you're ever looking at the raw numbers, because a fractional cent isn't rounded or forgiven — it's rejected.

If the lines don't balance, the entry doesn't get partially accepted or silently adjusted — it's refused outright, and the error names exactly how far off it was and in which direction, so the problem is something you (or an AI) can actually act on rather than a mysterious failure.

Take a slightly more textured example: a $310.00 charge that's actually $280.00 of Materials and $30.00 of Supplies, paid from checking. That's one journal entry with three lines: Materials debited $280.00, Supplies debited $30.00, and Checking credited $310.00. The two debits sum to $310.00, matching the single credit exactly — three lines, still one balanced entry, still one event.

Once an entry is posted, it's permanent. There's no edit button and no delete — the journal is append-only by design, which is a deliberate property covered in its own guide, not an oversight. Correcting a posted entry means posting a new one that reverses it, which is also covered on its own, since the mechanism has real rules worth understanding before you rely on it.

A journal entry also can't be dated into a period you've already locked closed — trying to post a January 15th entry into a book locked through January 31st is refused the same way an unbalanced entry is, with a clear message naming the lock date. That's the other half of what keeps a closed month closed.

One entry doesn't have to be a single debit and a single credit — it can split across several accounts on either side, as long as everything still nets to zero. A single credit card charge might genuinely belong partly to Materials and partly to Supplies; splitting it that way is one entry with three lines instead of two, not three separate entries.

Finally, the memo matters more than it looks like it should. For a manual entry or one an AI assistant posted on your behalf, the memo is often the only human-readable trail explaining what actually happened — months later, "reversal of misclassified rent payment" is a lot more useful to you or your accountant than a blank field next to two numbers.

Every journal entry is also permanently tied to the specific user account it was posted under, the exact moment it was posted, and its source tag. That combination — what happened, when, and how — is what turns the journal from just a list of numbers into an actual audit trail: months later, you can trace not just that $1,200 went to Subcontractors, but that it happened because a bank transaction was categorized on a specific date, or because your AI assistant posted it directly on your instruction.