Tricky tax rulings, answered with a single question
Connects ERP data with tax law grounds through an ontology — from input VAT deduction rulings to real-time preliminary closing, all with one natural language question.
Challenges
ERP Tax & Accounting: Today's Challenges
Multi-Level ERP Menu Navigation
Checking even a simple tax ruling means clicking through 5–6 levels of ERP menus and compiling figures by hand.
Hard-to-Verify Legal Grounds
Staff must separately look up and cross-check the legal basis (corporate tax law, VAT law provisions) for deductions and limits.
No Visibility Before Monthly Close
Preliminary closing is only possible after month-end, so executives can't see cash and P&L status when decisions are being made.
Use Cases
Use cases drawn from real demonstration scenarios
Q.“Is the repair cost for a company car eligible for input VAT deduction?”
The ontology checks vehicle type and usage data against tax regulations, returning a non-deductible ruling with the VAT Act §39 as its basis.
Q.“Show me today's preliminary closing and cash position”
Even before month-end close, journal entries are aggregated in real time to return preliminary P&L and cash status within 30 seconds.
Q.“How much have we exceeded this year's entertainment expense limit?”
Automatically computes the revenue-based limit under Corporate Tax Act §25 and reports the excess amount together with its tax impact.
Q.“Client meal for ₩300,000 — which account should this go to?”
Understands the transaction context and suggests the appropriate account (entertainment expenses) with journal entry guidance.
Impact
Impact
Time per tax ruling
Preliminary closing cycle
Ruling reliability
Reference — Tax & accounting ontology PoC with a leading Korean ERP company (MOU signed)
ERP Tax & Accounting — want to see it with your own data?
We'll arrange a demo tailored to your data environment and a 4–6 week PoC.