In an implementation workshop, a question comes up about how a particular transaction should hit the general ledger. The finance lead looks at a screen full of configuration tables and says, reasonably, "that's technical — that's for the system team." The consultant looks back and says, just as reasonably, "that's an accounting decision — that's for you." In the silence that follows, the rule gets set by whoever is most comfortable clicking the button. That moment, repeated across a few hundred settings, decides what the financial statements will say.
Both people in that room are half right. The setting is technical, in that it lives in a configuration table and is entered by someone fluent in the software. And it is an accounting decision, in that it determines which account a real dollar lands in, whether revenue is recognized now or deferred, whether a cost hits COGS or sits in inventory. A posting rule is an accounting policy. It is just written in a table instead of a memo.
The system doesn't decide. Someone configured it to.
It is easy to talk about account determination as if the software does the deciding — "the system posts it there." It doesn't. Account determination is a set of rules someone authored that say, in effect, when a transaction of this type happens under these conditions, post it to this account. When inventory is issued against a sales order, something has to decide which COGS account, which cost center, what offsetting entry. That logic was written by a person, and it encodes a judgment about how the business accounts for the event. Judgments about accounting are the definition of accounting policy.
So when finance treats that authoring as plumbing and hands it off, it has not avoided making the policy. It has only let someone else make it — someone excellent at the software who was never hired to own the financials.
What it costs downstream
The bill arrives later, somewhere finance can't ignore. A revenue-recognition trigger set during config — does revenue post at shipment, at delivery, at invoice — turns out to be a cutoff policy nobody in finance consciously chose, and it shapes the income statement every period until someone notices. A tax-determination rule misclassifies a category for three quarters. A misdirected posting quietly accumulates in an account that only surfaces in the audit. By then it is not a config change. It is a correction, an explanation to the auditor, and on a bad day a restatement.
- Account determination. Which account a transaction type posts to, and under what conditions. This is the chart of accounts, enforced.
- Revenue and cost timing. When revenue recognizes and when cost matches it. A trigger in a table is still a cutoff policy.
- Tax and classification rules. How transactions are categorized for tax and reporting. Wrong here is wrong everywhere downstream.
The discipline
None of this asks finance to learn the configuration screens. It asks finance to read the posting logic in plain language and sign it the way they would sign any other policy — to ask, for each material rule, "is this how we have decided to account for this?" and to own the answer. The consultant builds it; finance owns what it says. The translation between the table and the policy is a meeting, not a mystery.
Because in the end it comes back to one place. Every line in the configuration is an entry someone will one day defend to an auditor. Better that someone be finance.