Skip to content

Journal Entry Controls

Journal Entry Controls explain how Pinkapple ERP protects manual and system-generated journal activity from unsupported edits, unbalanced entries, unauthorized posting, and weak audit trails.

Workspace Reference

WorkspaceHow Users Reach ItWhat Users Usually Do There
GL JournalsAccounting -> Operations -> GL JournalsReview journal lifecycle, batches, entries, lines, reversals, voids, and status.
Back-Office PostingAccounting -> Operations -> Back-Office PostingCreate controlled manual journals from approved posting rules.
GL Posting ApprovalAccounting -> Setup -> GL Posting ApprovalConfigure and review approval controls for journal batches.
Posting Dates And PeriodsAdministration -> Financial Setup and Accounting posting workspacesConfirm whether a journal date is allowed before posting.

Journal Lifecycle

Journal entries normally move through these stages:

StageMeaning
DraftEntry is being prepared and can still be changed.
Pending ApprovalEntry has been submitted and is locked for review.
ApprovedEntry passed review and is ready for posting.
PostedEntry is part of the ledger and cannot be edited.
RejectedEntry was returned for correction.
ReversedA posted entry has been corrected by an opposite entry.
VoidedAn unposted entry has been marked invalid.

Creation Controls

When creating a journal, users should confirm:

  • Journal date.
  • Business unit.
  • Currency.
  • Description or narration.
  • Debit and credit lines.
  • GL accounts.
  • Sub-ledger details where required.
  • Supporting documents or notes where policy requires them.

The system should block entries that are incomplete, unbalanced, posted to invalid accounts, or dated into a period where posting is not allowed.

Approval Controls

Approval controls protect sensitive journals before they reach the ledger.

Common controls include:

  • Only authorized users can create or submit journals.
  • The creator may be blocked from approving the same journal.
  • Larger amounts may require additional approval.
  • Rejected entries should include a reason.
  • Pending entries should be locked from editing until returned or approved.

Approval behavior depends on the tenant's approval configuration.

Posting Controls

Posting confirms the journal into the ledger.

Before posting, confirm:

  • Approval is complete.
  • The posting date is allowed.
  • The fiscal period is open or otherwise postable by policy.
  • Debits equal credits.
  • Control accounts have required sub-ledger details.
  • Currency and exchange rate behavior are correct.
  • Supporting notes are sufficient.

Posted entries should not be edited or deleted. Corrections should use reversal or an approved correcting journal.

Batches

Journal batches group related entries. Batches help users review, approve, post, and audit journals together.

Use batches for:

  • Month-end adjustments.
  • Accruals.
  • Reclassifications.
  • Imported journals.
  • Multi-entry correction exercises.

Do not leave draft batches open indefinitely. Stale drafts should be reviewed, posted, voided, or cancelled according to policy.

Reversals And Corrections

Use reversal when a posted journal is wrong. A reversal preserves the original entry and adds an opposite entry for audit.

Use a correcting journal when the original entry should remain but an additional adjustment is needed.

Use voiding only for entries that have not been posted.

Control Accounts And Sub-Ledgers

Some GL accounts require supporting sub-ledger detail. Examples may include customer receivables, supplier payables, loans, deposits, wallets, bank accounts, or other controlled balances.

If a journal line uses a control account, users must provide or select the correct supporting context. Missing sub-ledger detail should be treated as a setup or entry error, not bypassed.

Good Practice

  • Use clear narrations that explain why the journal exists.
  • Attach or reference supporting evidence for material entries.
  • Avoid generic account names when a specific control or sub-ledger account is required.
  • Review period status before posting.
  • Do not correct posted entries by editing source records outside the proper workflow.
  • Separate journal preparation and approval where possible.

Pinkapple ERP by Stat Solutions Network