T Tulphenix
An open course ledger with a stitched gutter, an ink pad and stamp resting beside it on a maple desk under cool overcast daylight.

01 — Public filing room, 08:10

Your Korean ledger, already clear on Tuesday morning.

An independent reading room for cloud accounting and ERP work — plain guides on KRW ledgers, VAT, e-tax invoices and month-end close, written for the people who actually run them.

Chapter 01 — in one paragraph

Tulphenix is an independent educational site about cloud accounting and ERP workflows for South Korean businesses.

We publish plain-language guides on general ledger structure, bank reconciliation, accounts payable and receivable, VAT handling, and month-end close. The work runs on systems like WEHAGO T, Xero, Zoho Books and NetSuite — each of them handles those Korean routines a little differently.

Every entry describes the workflow first, then how a platform supports it. Readers include owners, bookkeepers and advisors who need operational answers before talking to a vendor. No downloads are required, and no account is needed to read a page.

How we research a topic

Every guide starts with the workflow, not with the brand. We map the steps a Seoul service firm or a trading company actually follows, then check how local and global systems support those steps — and where they do not.

  1. 01

    Map the workflow

    We trace the routine end to end — who raises the invoice, who books it, who reconciles the bank line — before we look at any product tour.

  2. 02

    Check local coverage

    For Korean context we review Douzone coverage of WEHAGO T and market listings that mention KRP, then compare the local outcome against what the platform documents.

  3. 03

    Compare global tools

    We review integration coverage for QuickBooks, Zoho Books, Xero and NetSuite in South Korea so the same routine can be judged against both local and global tools.

  4. 04

    Add enterprise notes

    Enterprise entries draw on ERP market material for SAP S/4HANA Cloud Public Edition and OmniEsol, kept as context rather than as a vendor summary.

A note on sources

We read the platforms' own documentation, the National Tax Service's published practice, and public market material. When two sources disagree, we say so in the guide and describe what changes in the workflow rather than picking a side.

An open ledger spread with a thread running through the spine gutter and a hand entering a figure in the right column under cool afternoon light.

Chapter 02 — the actual work

Two sides, one paper — matching rows until they agree.

Reconciliation is where most cloud accounting projects actually get judged. Our guides describe who does the work, how long the match takes on a typical Korean month, and where the errors enter — the same questions a bookkeeper asks before the month-end close.

Debit and credit are shown facing, always.

How we keep guides useful

Tax forms and portal screens change. A guide that keeps an outdated click path is worse than no guide at all, so upkeep is part of the work.

Review

Scheduled sweeps

We re-read guides for outdated steps and unclear tax-code advice. Process logic stays; button labels and menu names do not, because they move too often to be worth freezing in a screenshot.

Correct

Reader corrections

When a reader reports an error through the contact page, we check it against current National Tax Service practice and update the text. Cite the guide title and paragraph so we can find it quickly.

Mark

Honest labels

A guide that skips VAT mapping or e-invoice matching is marked as introductory, not complete. That is how experienced users evaluate quality, and it is the bar we try to hold.

What we do not do

Our limits, stated plainly

  • We do not provide tax filing services, audit opinions or implementation contracts.

  • We do not publish benchmarks, uptime figures or security certifications for vendors.

  • When a question needs licensed advice, we point readers to their own accountant or tax agent.

  • There are no demo traps and no forced sign-ups; the site is funded as a content resource.

Who reads Tulphenix

The same guide needs to be useful to an owner signing off on the ledger and to an advisor briefing a client on global SaaS options. We write for all three readers without dumbing down the ledger detail.

01

SMB owners

Owners and founders in South Korea who need to understand what a systems change costs them operationally before they sign anything.

02

In-house bookkeepers

The people who actually post the entries. They come to us for the VAT mapping, the matching rules, and the practical order of a month-end close.

03

Advisors & mid-market teams

Accountants briefing clients on WEHAGO T or global SaaS options, plus a smaller group supporting subsidiaries and multi-entity finance teams.

Three accountants around a shared table reviewing a month-end close schedule on a laptop and on paper under daylight from tall windows.
Month-end close as it usually happens — one screen, one printed schedule, and the matching that has to agree before the ledger can close.

Corrections and suggestions

Found an error in a VAT step or a product description? The contact page is the right channel. Cite the guide title and the paragraph so the fix lands in the right place.

Correspondence
[email protected] — reviewed on business days in Seoul.
Phone
+82 2-6167-8357 — Monday to Friday, 9:00 AM to 6:00 PM.
Post
14 Teheran-ro 88-gil, Gangnam-gu, Seoul 06179, South Korea.
Where we operate
An online publication read across South Korea. There are no branch offices to visit; tulphenix.digital is the address that reaches us.