Where it usually breaks
And how to keep it from happening.
- Equal totals hide a line coded to the wrong account.
- The entry date falls outside the selected period.
- A later correction loses the original journal reference or supporting explanation.
Check account coding, line totals and the accounting period before posting review.
Staff Accountant creates a Draft journal with an entry date, organization, source and tax period. Write a description that explains the business event. Attach the supporting evidence so Controller can inspect the basis for the entry.
Staff Accountant reviews the debit and credit amounts and selected ledger accounts. Compare the header totals with the linked lines and examine any out-of-balance indication. A balanced entry still needs the correct account treatment and source explanation.
Staff Accountant checks that the intended date and tax period agree. Controller resolves an entry aimed at a Closed or Locked period through the customer's agreed correction procedure. Keep the original reason and the permitted accounting date visible.
Controller reviews the account treatment and balance before the entry moves from Draft to Posted under the agreed posting procedure. Staff Accountant retains the support and checks the final status. Rehearse this procedure during setup with the ordinary role accounts.
Staff Accountant brings a later correction to Controller with the original entry reference and reason. Use the agreed reversal procedure when Reversed applies and retain the original evidence. The reviewer should be able to understand both entries without reconstructing the story from memory.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.