What Each Role in General Accounting Knows That the Others Do Not

Each role holds a fragment. Subledger owners know why a transaction happened. The general ledger team knows where it landed. Consolidation knows how entities net together. Management knows which numbers will be challenged. Trouble starts at handoffs, where context is stripped out and only an amount travels forward.

Who holds which piece

The person who maintains the chart of accounts understands what each account was meant to capture when it was created. That intent rarely survives in the account description. Years later, people post to an account because it is familiar or because a template points there. The original meaning drifts, and nobody tells the owner.

Accounts payable, receivables and payroll staff know the source documents. They know a vendor invoice was split because the purchase order was wrong. They also know a customer receipt went to suspense because the remittance was unreadable. Most of that knowledge lives in email threads and memory.

General ledger accountants see journals arrive in batches. They know which feeds break and which preparers make errors. What they cannot see is the business reason behind an unusual entry unless someone writes it down.

The intercompany team knows the agreements between entities and which counterparty tends to book late. Consolidation staff know the elimination logic. They often discover a mismatch only when the eliminations fail to clear.

Controllers and finance leads know what management will ask about. They post top side adjustments with a clear view of the story the numbers must support. The accountants who reconcile the underlying accounts often never learn why those adjustments were made.

In public sector settings, a budget or funds control officer adds another layer. That person knows which amounts are legally available to spend. Proprietary accountants may record an expense correctly and still breach a funds limit they could not see.

Where the gaps bite

Allocations are a common failure point. The basis was agreed in a meeting long ago. The person running the allocation each month applies the drivers without knowing whether they still reflect how the business operates. Department heads notice a charge that looks wrong, but they have no way to trace it.

Period end accruals depend on operational knowledge that finance does not own. A project manager knows work was delivered but not billed. If nobody asks, the accrual is missed or estimated from last month.

Reconciliations suffer when the reconciler and the poster are different people. A difference gets explained as timing and carried forward. Eventually it ages into something nobody can explain, because the person who knew has moved on.

Intercompany balances break when each side books from its own records. One entity records on invoice and the other on receipt. Neither is wrong by its own rules, yet the totals refuse to agree at consolidation.

Management adjustments create the sharpest asymmetry. They sit above the ledger detail, so a later reconciliation of the trial balance to subledgers will not catch them. If the reversal is forgotten, the error persists quietly into the next period.

Cash is a quieter gap. The treasury or cash team sees what actually cleared the bank. The ledger shows what was recorded. Differences are often parked in a clearing account that only one person truly understands.

Questions to ask the people who run the process

What people do often differs from the documented procedure. Ask them directly, one role at a time.

• Which accounts do you post to out of habit, and do you know what they were set up for?
• When a journal looks unusual, who do you call to find out why?
• Which reconciling items have been carried forward for a long time, and who last understood them?
• How do you learn about work delivered but not yet invoiced?
• When were the allocation drivers last reviewed, and by whom?
• Which counterparty entity is usually late or different, and how do you work around it?
• Which adjustments are made after the trial balance is drafted, and where is the reasoning kept?
• What do you fix manually every close that the system should handle?
• If you were away during close, what would go wrong first?
• Can every balance you report be traced back to a source document today?

The answers to the last two questions usually reveal the real process.

Changing the process without losing what people know

New systems and shared service moves tend to formalise the posting and drop the explanation. Before redesigning anything, capture the reasons behind recurring manual entries and long standing reconciling items. Require a short business rationale on any journal above routine thresholds. Make the chart of accounts owner review new usage patterns, not just new account requests.

Put reconcilers and preparers in the same conversation at least during close. Give consolidation early sight of intercompany mismatches instead of letting them surface at elimination. Where funds control applies, let budget staff see commitments as they form.

Most importantly, identify the individuals whose departure would leave a balance unexplained. Their knowledge is a control, even if no procedure names it.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.