Objective
Design SLA thinking so subledger activity creates clear, auditable GL journals with minimal suspense.
Case study 11
Portfolio knowledge project
Subledger Accounting Rules Design
How accounting events from AP, AR, and Assets should land cleanly in GL — event classes, journal line rules, description standards, and reconciliation checkpoints.
Knowledge / portfolio case study only. Not employment history, not a named client engagement, and not a certification claim.
Context
When SLA rules are vague, journals are hard to explain and reconciliations fail.
Scope
Event inventory, account derivation intent, journal descriptions, and recon points. Not every seeded rule customization.
Approach
List key events → define debit/credit intent → map sources to accounts → standardize descriptions → test create accounting → reconcile to TB.
- 01Event inventoryAP/AR/Assets key events.
- 02Account intentNatural account & CC logic.
- 03Description standardSearchable journal text.
- 04Create accounting testsHappy path + exceptions.
- 05Reconciliation rhythmDaily and period-end.
01Event inventory
02Account intent
03Description
04Create accounting
Subledger Accounting Rules Design
Key design decisions
- Prefer clear seeded patterns before heavy customization
- Reduce upgrade risk.
- Descriptions must include business key
- Invoice/asset number in journal text.
- Suspense is temporary only
- Age and clear every close.
Walkthrough
Post AP invoice → create accounting → review journal → transfer to GL → reconcile subledger to GL.
Controls
Unaccounted transactions tracked daily; suspense accounts aged; rule changes logged.
Oracle modules in focus
Subledger Accounting
AP
AR
Assets
GL
Deliverables
Event-to-account matrix
description standard
recon checklist
UAT event pack.
Outcomes
Shows systems thinking between subledgers and GL.