If it isn’t evidenced, it didn’t happen (caped heroes optional).
Manual journals are the unsung plot twists of month-end: a late revenue accrual here, a tax true-up there, and an equity tidy-up that everyone swears they approved (somewhere). This playbook makes adjustments boring—in the best way. You’ll standardise journal types, attach the right evidence at the right moment, and route approvals by materiality so reviewers can say “yes” without spelunking inboxes. By the end, adjustments are fast, explainable, and audit-ready—and Day 0 is consolidation, not archaeology (tea encouraged).
Day-in-the-life: before → after
Before: A late email requests “urgent top-side” revenue. The spreadsheet has a tab called FINAL2. Evidence lives in someone’s downloads. Approver replies “Approved” from a phone mid-commute. Audit asks where the calculation came from; six people go hunting (boots not included).
After: Journal types are standard (accrual, reclass, IC true-up, FX reval, policy). Submitter must attach evidence and select the driver. Thresholds route approvals by materiality; the cockpit shows status by owner and ageing. Reviewers see numbers, support, and policy in one place; Day 0 is calm.
So what? Structure + evidence + routing turns last-minute chaos into quick, defensible decisions.
Journal types, evidence, approvals (table)
| Type | Evidence required | Approval route |
|---|---|---|
| Accrual/deferral | Calc sheet + contract/PO + cut-off note | Entity controller → Group review (materiality) |
| Reclassification | Mapping rationale + before/after view | Controller (auto if non-material) |
| IC true-up | Counterparty confirmation + rate/price proof | Pair owners → Group (see IC playbook) |
| FX revaluation | Stamped rate pack + listing of monetary items | Controller; CTA link (see FX guide) |
| Policy adjustment | Policy reference + calc + sign-off note | Group technical accounting |
So what? With clear types, reviewers know what “good” looks like before they open the file.
Before vs After: five practical switches
- From free-text journals → standard types with required fields and attachments.
- From inbox approvals → in-tool routing by materiality and account class.
- From “trust me” evidence → “no proof, no post” (block missing attachments).
- From duplicate topsides → validations that prevent re-posting the same key.
- From narrative drift → linked disclosures so notes update after final posts (see disclosure management).
So what? Small design choices turn journals from folklore into a process.
Control matrix for adjustments (table)
| Control | What it prevents | How to evidence |
|---|---|---|
| Required attachments | Unsupported postings | System block + file in journal record |
| Approval thresholds | Under/over-review | Audit log with materiality band |
| Duplicate prevention | Double counting | Unique key validation (period+type+ref) |
| Posting window | Late, unreviewed entries | Close calendar lock & reopen protocol |
| Link to disclosures | Narrative misalignment | Note references to controlled cells |
So what? Controls should be visible and testable in minutes, not days.
Stakeholder talk tracks
CFO: “Faster, safer close.” — Materiality-based routing gives time back; variance between dry-run and final shrinks.
Group Controller: “Fewer late ‘surprises’.” — Posting windows lock; reopen requests need rationale and evidence.
Audit: “Show me the trail.” — Evidence lives with the journal; approvals are timestamped; samples take minutes.
IT/Data: “Keep it maintainable.” — Rules live in metadata; validations are transparent (vintage is great for wine, not ledgers).
So what? Clear benefits per stakeholder accelerates adoption.
Objections & responses + real-world moments
- Objection: “Attachments slow us down.” — Response: They speed reviewers up; net time falls when questions stop.
- Objection: “Materiality is subjective.” — Response: Set bands by entity; tune quarterly with audit.
- Objection: “We’ll miss the window.” — Response: Reopen protocol exists—for justified cases with evidence.
- Late revenue estimate: Contract and calc attached; routed to group due to size; approval in tool.
- IC freight error: Counterparty confirmation attached; auto-approved within tolerance (see IC playbook).
- FX revalue miss: Blocked at load—wrong pack; re-posted with stamped rates (see FX guide).
- Equity reclass: Before/after view attached; disclosure note updates automatically.
So what? Typical “gotchas” become quick, documented tasks.
Pitfalls → fixes
Pitfall 1: Journals as free-text. Fix: Enforce types + required fields.
Pitfall 2: Evidence scattered. Fix: Store with the journal or block posting.
Pitfall 3: Approval by email. Fix: Route in-tool with thresholds and logs.
Pitfall 4: Duplicate topsides. Fix: Unique key and period lock rules.
Pitfall 5: Narrative lags numbers. Fix: Link disclosures to controlled cells (see disclosure management).
So what? Guardrails prevent “new month, same mess.”
30–60–90 plan to operationalise journals
Journal types → Evidence & routing → Locks & disclosures
Days 0–30 — Stabilise: Publish 5–7 journal types with definitions and examples. Add required fields (reference, counterparty, period, driver). Mandate attachments for accruals, IC, and policy journals. Pilot with two entities.
Days 31–60 — Streamline: Configure approval thresholds by entity and account class. Enable duplicate prevention and posting windows with a reopen protocol. Train reviewers to use “exceptions-only” dashboards, not email threads.
Days 61–90 — Scale: Roll out globally; link affected disclosures to controlled cells; add a Day −2 dry-run report highlighting journals lacking evidence or stuck in routing. Close out manual email approvals.
So what? Three sprints convert journals from craft to choreography.
How CCH Tagetik helps with journals & evidence
A platform like CCH Tagetik turns “auditor-ready” from aspiration into default. Configure the rails once; every period benefits (you still make the judgement calls—the system removes the scavenger hunt).
| Capability | What it enforces | Result in the close |
|---|---|---|
| Journal types & templates | Standard fields, mandatory attachments | Consistent submissions; faster reviews |
| Approval workflows | Routing by materiality, class, entity | Right eyes on the right entries |
| Validation & blocking | Duplicate keys, missing pack/evidence | Errors caught early; fewer restatements |
| Audit log & attachments | Timestamps, approver IDs, file history | Sampling turns into confirmation |
| Disclosure linkage | Notes pull from controlled cells | Narrative updates after final posts |
Submit → Validate → Approve → Post → Disclose
Practical tips: Block posts without attachments for accruals and IC; publish posting windows in the workflow cockpit; and surface journals that change OCI so the disclosures update immediately.
So what? Configure once; every month gets easier—and more defensible.
Metric that matters
% of journals with complete evidence at submission (target ≥ 95%). Pair with median approval time and dry-run vs final variance caused by journals. Healthy processes show high evidence completeness, fast approvals, and shrinking journal-driven variance. If the KPI stalls, tighten required fields and thresholds first.
Standardise the journal, attach the proof, enjoy the quiet.
Adopt clear types, require evidence on entry, and route approvals by materiality. Lock the posting window, prevent duplicates, and link disclosures so the story stays in sync. Tie journals to your pre-close cadence and workflow cockpit. The result: auditor-ready adjustments, fewer fire drills, and a final pack that explains itself.
Word count: 1,178