Skip to content
D K
GoBD-compliant §203 StGB-compliant Q1

Account Coding Agent

GL account, cost centre, tax code - automatically coded, with confidence score.

Assigns incoming invoices to the correct GL account (SKR03/04 or custom), cost centre and tax code. Checks input tax deduction, capitalisation requirements and accrual boundaries.

Score Dashboard

Agent Readiness 82-89%
Governance Complexity 26-33%
Economic Impact 76-83%
Lighthouse Effect 31-38%
Implementation Complexity 31-38%
Transaction Volume Daily

What This Agent Does

Account coding is the process that turns a document into a posting. Every invoice must be assigned to a GL account, a cost centre and a tax code. For standard cases this is deterministic - for borderline cases it requires interpretation of the service description.

The Decision Layer breaks account coding into ten decision steps. GL account assignment for standard accounts uses rule-based mapping via the chart of accounts. For ambiguous service descriptions, the AI Agent classifies. The tax code is determined per UStG - 19%, 7%, intra-community, reverse charge, exempt. Input tax deductibility, capitalisation requirements and accrual boundaries are checked automatically.

The result: standard codings run through automatically. The AI Agent rates its own confidence with a confidence score. Below the defined threshold, the item is routed to a clerk. The error rate for account codings drops - and with it the risk during tax audits.

Micro-Decision Table

Human
Rules Engine
AI Agent
Each row is a decision. Expand to see the decision record and whether it can be challenged.
GL account assignment (standard) Which GL account matches the service? Rules Engine Auditor

Rule-based assignment with clear chart of accounts (SKR03/04)

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Challengeable by: Auditor

GL account assignment (interpretation) How should the service description be interpreted? AI Agent Auditor

LLM classification for ambiguous service descriptions

Decision Record

Model version and confidence score
Input data and classification result
Decision rationale (explainability)
Audit trail with full traceability

Challengeable: Yes - fully documented, reviewable by humans, objection via formal process.

Challengeable by: Auditor

Cost centre assignment Which cost centre bears the cost? Rules Engine

Derived from purchase order or contract; AI suggestion when unassigned

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Profit centre assignment Which profit centre is responsible? Rules Engine

Derived from cost centre

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Determine tax code 19%, 7%, intra-community, reverse charge or exempt? Rules Engine Auditor

UStG rules applied deterministically

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Challengeable by: Auditor

Check input tax deduction Is input tax deductible per Paragraph 15 UStG? Rules Engine Auditor

Deterministic check of deduction prerequisites

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Challengeable by: Auditor

Check capitalisation requirement Must it be capitalised? Low-value asset or fixed asset? Rules Engine Auditor

Thresholds per HGB and EStG (above EUR 800 net)

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Challengeable by: Auditor

Check accrual boundary Is there a prepaid expense item? Rules Engine Auditor

HGB Paragraph 250 - service period vs. invoice date

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Challengeable by: Auditor

Confidence assessment How confident is the overall coding? AI Agent

LLM rates its own confidence across all decision steps

Decision Record

Model version and confidence score
Input data and classification result
Decision rationale (explainability)
Audit trail with full traceability

Challengeable: Yes - fully documented, reviewable by humans, objection via formal process.

Routing decision Auto-post or clerk review? Rules Engine

Confidence threshold determines the routing path

Decision Record

Rule ID and version number
Input data that triggered the rule
Calculation result and applied formula

Challengeable: Yes - rule application verifiable. Objection possible for incorrect data or wrong rule version.

Decision Record and Right to Challenge

Every decision this agent makes or prepares is documented in a complete decision record. Affected parties (employees, suppliers, auditors) can review, understand, and challenge every individual decision.

Which rule in which version was applied?
What data was the decision based on?
Who (human, rules engine, or AI) decided - and why?
How can the affected person file an objection?
How the Decision Layer enforces this architecturally →

Prerequisites

  • ERP system with chart of accounts (SKR03/04 or custom)
  • Cost centre structure and profit centre mapping
  • Historical coding data for AI training (min. 12 months)
  • Defined confidence thresholds for auto-posting

Governance Notes

GoBD-compliant §203 StGB-compliant

GoBD relevance: high - incorrect coding leads directly to incorrect tax reporting. A frequent point of objection in tax audits. UStG rules for tax codes are deterministic and stored versioned in the rule engine. When legislation changes (e.g. tax rate change), a new rule version is deployed without altering existing postings. Paragraph 203 StGB relevant for client data.

§203 StGB-relevant data is encrypted end-to-end and never passed to AI models in plain text.

Process Documentation Contribution

The Account Coding Agent documents for every posting: chart of accounts applied (version), chosen GL account with rationale, tax code with legal basis, confidence score and whether posting was automatic or manual. During a tax audit, it is traceable why every individual coding was made.

Infrastructure Contribution

The Account Coding Agent builds the central posting logic. The chart of accounts engine (rule versioning, tax code assignment, thresholds) is reused by the Credit Note Agent, Entertainment Expense Agent and all other agents that create journal entries. The confidence assessment becomes the standard pattern for all AI-assisted decisions in the Finance catalog.

Frequently Asked Questions

Does the agent work with our custom chart of accounts?

Yes. The agent works with SKR03, SKR04 or custom charts of accounts. The mapping is configured in the rule engine. Standard charts are ready immediately; custom charts are set up during the implementation project.

What happens with incorrect coding?

Every coding is tagged with a confidence score. Below the defined threshold, it is not auto-posted but routed to a clerk. Subsequent corrections are made GoBD-compliantly via reversal and re-posting - never by overwriting.

How does the agent handle tax audits?

The agent generates the procedural documentation automatically. For every posting it is traceable: which chart of accounts (version), which rule, which input, which result. This is not a retrospective report but technical proof of the decision-making process.

Implement This Agent?

We assess your finance process landscape and show how this agent fits your infrastructure.