Journal Entry Examples

Journal entry examples matter because they show how everyday business activity turns into accounting records. In a South African SME, the same logic supports monthly reporting, VAT review, payroll control, and year-end schedules.

Journal entries are one of the clearest ways to understand how accounting works beneath the reports.

A profit and loss statement or balance sheet is a summary. The journal entry is the line-level record showing how a transaction moved through the books in the first place.

The numbers first

That is the core logic: every entry affects at least two sides of the accounting records.

What a journal entry is supposed to do

A journal entry should:

1. record the financial effect of the transaction
2. keep the ledger balanced
3. leave a clear explanation for later review

Without that clarity, the numbers may still move, but they become harder to trust.

Step 1: Identify the real transaction

Before choosing debits and credits, identify what actually happened. A bank movement is not always the full accounting story. The business may have made a sale, collected an old debtor, paid a supplier, repaid a loan, moved money between accounts, or corrected an earlier posting.

That distinction matters because the journal should record the commercial event, not only the bank line. If a customer pays an old invoice, the entry should clear debtors rather than create new revenue. If a director pays a business cost personally, the entry may affect a director loan account rather than the bank. If stock is purchased, the entry may differ from a simple operating expense.

For the wider sequence, compare this page with the accounting cycle example. Journal entries sit inside that cycle. They are not isolated fixes.

Step 2: Choose the accounts and keep the entry balanced

Every journal needs at least one debit and one credit. The total debits must equal the total credits. The accounting system may enforce that mechanically, but the preparer still needs to choose the right accounts.

Useful review questions are:

• Is this income, an asset, a liability, equity, or an expense?
• Is cash involved now, or is the amount still owed?
• Does VAT apply, and is the business registered for VAT?
• Is this a normal transaction or a correction?
• Does the entry affect management reporting?

Those questions help prevent the common SME problem where transactions are captured quickly but coded to accounts that make reporting misleading.

Step 3: Add support and review before month-end

The description and support are part of the journal. A good journal should let another reviewer understand what was posted and why. That is especially important for adjustments, accruals, prepayments, depreciation, director loan movements, and VAT corrections.

At month-end, review journals for large values, unusual account combinations, missing descriptions, repeated corrections, and postings made directly to control accounts. Where the business relies on monthly management accounts, weak journals can make the reporting pack look more reliable than it is.

For the close process around these entries, use the monthly close checklist and what to send your accountant each month as supporting resources.

Example 1: Cash sale

If a business sells services for cash:

The bank increases because cash was received. Revenue increases because the business earned income.

Example 2: Credit sale

If the business invoices a client and expects payment later:

This is different from a cash sale because the business has earned income, but cash has not yet arrived.

Example 3: Supplier expense on account

If a supplier invoice is received and not yet paid:

The expense is recognised, but the liability sits in creditors until payment is made.

Example 4: Paying the supplier

When the supplier is paid:

This clears the liability and reduces cash.

Example 5: VAT-type logic

Where VAT applies, the entry is often split between the net amount and the tax element. The exact treatment depends on the transaction and the business’s VAT position.

That is one reason VAT journals should be reviewed carefully within accounting processes rather than assumed automatically.

Example 6: Owner pays a supplier personally

If a director or owner pays a business supplier from a personal account, the business still needs to record the cost and the amount owed back to the owner, if reimbursement is expected.

The support should include the supplier invoice and proof of payment. Without that support, owner-funded costs become difficult to explain at year-end.

Example 7: Reclassifying an expense

If an amount was posted to the wrong expense account, the correction should move it without changing the bank.

The description should explain the original error. Reclassification journals are useful, but repeated reclasses can point to weak coding rules or unclear capture responsibilities.

Example 8: Depreciation at month-end

For a fixed asset, depreciation may be posted monthly so management reports show the cost of using the asset over time.

This entry should tie back to the asset register. For the supporting schedule, see the fixed asset register template.

Review checks for journal examples

Before relying on a journal, check the practical evidence behind it:

These checks are simple, but they prevent many accounting clean-up problems. They also help owners see which journals are routine and which ones need a professional review before reports are finalised.

When a journal should be escalated

Escalate the journal before posting if it affects VAT, PAYE, income tax, director loans, intercompany balances, fixed assets, financing arrangements, or prior-year numbers. Those entries can be valid, but they need stronger support because they may affect SARS filings, financial statements, or management accounts.

Also escalate when a correction is being repeated every month. Repeated correction journals usually point to a process problem in capture, account mapping, supplier coding, or month-end review.

A practical comparison table

Management does not need to post every journal personally, but it helps to understand the categories.

Why descriptions matter

A journal entry should never be a mystery.

The description should make it possible for another reviewer to understand:

1. what happened
2. why the journal was needed
3. what support exists behind it

This matters especially for corrections. Large unexplained journals are one of the fastest ways to weaken confidence in the reporting pack.

When businesses should pay closer attention

Journal-entry discipline matters more when:

• there are many month-end corrections
• owner or director transactions are common
• VAT or payroll complexity is increasing
• management accounts depend on cleaner monthly reporting

This is where bookkeeping and management accounts connect. Weak entry quality eventually weakens reporting quality.

Related accounting resources

Use these pages with the examples above:

• Transaction in accounting example
• Accounting cycle with example
• Accounting requirements for South African businesses
• Monthly accounting packages

What to keep with each journal

Every non-routine journal should have a short support trail. Keep the reason for the entry, the source document or schedule, the person who prepared it, the person who reviewed it, and the month it affects.

This is especially important for accruals, prepayments, owner accounts, VAT-sensitive entries, payroll corrections, fixed assets, and prior-period corrections. The journal may be technically balanced, but it is still weak if nobody can explain it later. A clear support trail turns the entry from a mystery movement into a reviewable accounting decision.