AWRA OpsHub Search
Intermediate Certificate on pass

Journal Entry Controls

Draft balanced manual journals, route them through approval when it is switched on, and correct a posted journal by reversing it, never by deleting it.

3 lessons 40 min 5-question assessment 70% to pass

What you’ll learn

  • Connect finance reports to source modules, controls, and operational decisions
  • Review accounting, tax, budget, payment, reconciliation, and close evidence
  • Identify finance exceptions before they distort reports or manager decisions
  • Prepare finance records for audit, period close, and executive review

Course content

3 lessons · 40 min of reading
01
Lesson 1 of 3 Reading 12 min

Draft and post balanced entries

Journal Entry Controls focuses on manual journal drafts and posting, balancing to the cent, memos and tags, the approval switch and threshold, rejection with a reason, Reverse journal, and the period lock. In AWRA, finance control works best when operational activity, accounting records, tax treatment, approvals, attachments, and reports stay connected.

The practical goal is trust. Finance users should know where a number came from, which source module created it, who reviewed it, and what evidence supports the balance, tax, payment, budget, or close decision.

In practice, a finance user opens Accounting, Manual Journals, New journal, dates an accrual in an open month, enters debit and credit lines that balance to the cent with their branch and department tags, and clicks Save draft. When it is ready they post it; because journal approval is on in Accounting Defaults with a 50,000 threshold, the 120,000 journal waits for the financial controller, who cannot approve a journal they drafted themselves. A week later a line is found on the wrong account, so the controller opens the posted journal, clicks Reverse journal, gives the reason and a date, and AWRA posts the mirror entries before the right journal is entered. Nothing posted is ever deleted.

Journal control path

1

Draft

Balanced lines, memo and tags are saved as a draft.

2

Submit

Post, or submit for approval when the amount is at or above the threshold.

3

Approve

Someone other than the author approves, or rejects with a reason.

4

Post

The journal posts under one MJ reference with who and when.

5

Reverse

A mistake is reversed with a reason and date, then re-entered correctly.

Finance model

  • Finance reports should trace back to source records and review decisions.
  • Tax, budget, and accounting setup choices affect many downstream reports.
  • Attachments and review notes make balances defensible during audit or close.
  • Exceptions should be owned before they become reporting noise.
02
Lesson 2 of 3 Workshop 14 min

Approve or reject before posting

The operating routine is to confirm the adjustment reason, date the journal in an open month, enter balanced lines with tags, save a draft, post or submit it for approval, and reverse any posted mistake instead of trying to delete it. This keeps finance work from becoming a spreadsheet-only exercise disconnected from AWRA source activity.

Before acting, check journal date and whether its month is open, debit and credit totals, memo, tags, approval status and approver, rejection reason, and any reversal with its reason and date. These checks protect report accuracy, cash visibility, tax treatment, procurement decisions, and audit readiness.

A strong finance user can explain the next action from the record itself, whether the action is reviewing a ledger line, chasing a receivable, reconciling a payment, approving a budget, or closing a period.

Journal review guide

Finance signal Review Action
Out of balance Debit and credit totals Fix in the draft before posting
Above the approval threshold Approver is not the author Approve, or reject with a reason
Wrong line posted Original MJ reference Reverse the journal, then post the right one
Closed month Period status Reverse on the first open day, or reopen with a reason

Finance decisions

  • Finance action should follow the current balance, source module, and control state.
  • High-impact edits, deletes, overrides, and close decisions need clear reasons.
  • Operational context helps finance teams interpret margins, cash, and aging.
  • Reports are more useful when exceptions have owners and next actions.
03
Lesson 3 of 3 Practice 14 min

Reverse, never delete

Finance closure should leave proof. Useful evidence includes journal memo, line accounts and descriptions, MJ reference, tags, approver or rejection reason, the reversal journal with its reason and date, and ledger impact, connected to the exact account, transaction, report, payment, tax setting, budget, reconciliation, or close item.

Managers should review patterns such as unmatched payments, aged balances, failed sync, suspicious adjustments, tax setup gaps, budget overruns, and unresolved period-close blockers.

In practice, closure means the journal is balanced, approved where required, traceable in the ledger, and any mistake is reversed rather than removed.

Journal control checklist

Memo states the reason
Debits and credits balance to the cent
Date falls in an open month
Approval was given by someone other than the author
Mistakes are reversed, not deleted

Financial proof

  • Finance work is complete only when the balance and evidence can be defended.
  • Close routines should surface unresolved risk instead of hiding it.
  • Audit packs and exports should preserve source context, not just report totals.
  • Good finance governance protects cash, tax, margins, budgets, and trust.

Finished the material?

Take the 5-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center