Jexmavon — Cloud Accounting for Business Jexmavon

Korean compliance guide

Can your ledger prove every VAT line?

Korean VAT runs on evidence. This guide explains how electronic tax invoices, ledger postings, and bank movement fit together in KRW, so your VAT review rests on documents, not memory. General education only — confirm filing positions with your accountant.

A cream tax invoice sheet lying on a printed ledger page, warm lamp light across one side and cool shadow across the other, a pen resting below.
A cream tax invoice laid on a ruled ledger page under a warm desk lamp — the shape every Korean VAT review rests on.
  1. 01 — evidence

    A chain you can walk

    Every invoice stitched to a customer, a revenue account, and a VAT code.

  2. 02 — review

    Monthly, not annual

    Short cycles catch miscoded lines before they compound on the return.

  3. 03 — currency

    KRW as the working record

    Foreign amounts converted and documented where they occur, not quietly.

  4. 04 — handover

    A shorter accountant meeting

    Bring the summary, the aging reports, and the list of corrected lines.

Chapter one

Electronic tax invoices, in plain terms

An electronic tax invoice is a structured tax document exchanged through approved channels — issuance, delivery, and storage traceable by design. Your accounting should mirror that structure, linking each invoice to a customer, a revenue account, and a VAT code.

Cancellations and corrections must post as traceable entries, not silent edits. When that chain holds, VAT review moves quickly, because each number the reviewer sees can be walked back to the document it came from.

Ask any vendor to walk issuance, receipt, correction, and cancellation live. Watch where the history lives. If staff cannot explain a corrected line to an auditor in one minute, the workflow needs work before the filing date does.

Issuance Seller posts the invoice on the approved channel; the ledger receives the same header.
Receipt Buyer accepts; a matching entry appears on the purchase side with its VAT code.
Correction Amount or code changes as a new line, with a note; the original stays visible.
Cancellation Reversal posts on both sides; nothing disappears from the review trail.
A fingertip on the last empty box of a printed arrow flow on paper, a clipped stack of cream tax invoice sheets beside it.
The VAT summary is a printed flow. If a box cannot tie back to a ledger line, the box is telling you something.

Chapter two

From invoice to VAT summary

Each sale or purchase carries a tax treatment that should post automatically, and still be reviewable line by line when the period closes.

Stage 01 — scan

Sweep the new lines first

Before closing, scan every item posted in the period for the wrong VAT code. Overseas sales, mixed supplies, and platform fees are the usual offenders because their treatment flips between categories.

Stage 02 — tie

Tie each summary line back

Run the VAT summary inside the software and tie every line back to its ledger detail. A summary you cannot drill into is a summary an accountant cannot sign off without a second conversation.

Stage 03 — reconcile

Reconcile cash against paper

Match the bank feed to the ledger so paper and reality agree. Then lock the period so later edits leave a history instead of rewriting the return.

Do this monthly even when the filing period spans longer. Short cycles catch miscodes while the memory of the transaction is still fresh, and they turn the return into a confirmation rather than a rescue.

Lock the period after review. Later edits keep history instead of erasing it.

Chapter three

KRW reporting discipline

Keep KRW as the working and reporting currency for domestic compliance, with foreign amounts converted and documented where they occur. Rounding, fees, and timing differences deserve explicit handling, not quiet adjustment.

Reports should read clearly in KRW for accountants in Korea while still supporting group views abroad. Clean currency habits reduce month-end questions.

Confirm how your tool stores source amounts alongside converted values. Export one month and check its readability outside the application. Your accountant should not need a login to follow the logic of a number.

What is held Where it lives State
Source currency amount On the original transaction Kept
Converted KRW value Beside the source figure Documented
Rounding and fee delta On the posting itself Named
KRW reporting figure Reads in the ledger Reconciled

One ledger, two poles: the money as it arrived, and the money as Korea reads it. Both stay in the record so the conversion is documented, not assumed.

Chapter four

Controls that prevent repeat errors

Who can issue, approve, correct, and lock? The answer should live in roles, not in memory. Small, visible controls beat heroic cleanups when the VAT clock runs short.

Require approval on bills above a threshold, restrict edits inside a closed period, and keep attachment rules simple enough that staff actually follow them. Review open receivables and payables weekly so problems surface before VAT week.

For multi-entity teams, add intercompany discipline early. Sage Intacct and NetSuite are built with that scope in mind, while lighter tools need manual care. Match control depth to entity reality, not ambition.

  1. Issue

    Sales and operations raise invoices inside the approved channel; the ledger receives the entry directly.

  2. Approve

    Bills above a threshold go to a named approver. The rule sits in the role, not in a manager's inbox habit.

  3. Correct

    Corrections post as new lines with a note. Staff explain the change in one minute; the original stays visible.

  4. Lock

    The period closes once reviewed. Later entries leave a trail instead of silently rewriting a filed line.

For teams working across more than one entity, the same ladder applies twice and intercompany rules take the place of ad-hoc agreements. The platform you choose should be able to hold that shape.

Chapter five

When to ask your accountant

Jexmavon explains flows; it does not file for you. Filing turns on your facts. Use this guide to make the accountant conversation shorter and sharper.

Bring the four artefacts and leave with a written close checklist for next period. The pack below is the shape most Korean SMEs can assemble in an afternoon.

  • VAT summary tied to ledger detail

    The summary every number can be walked back from, drilled in front of the accountant.

  • Receivables and payables aging

    Open items with dates, so the review can flag anything aged past the usual window.

  • Bank reconciliation status

    What matched, what did not, and where the feed is still waiting for a row.

  • List of corrected invoices

    Each correction, what triggered it, and which period it landed in.

Also bring

Bank statements for the period, the current chart of accounts, and any new counterparty the team has started invoicing this quarter.

Ask before you leave

Which documents to keep, for how long under current practice, and which new business lines or hybrid ledger setups might change their treatment.

Common questions

Answers a Korean SME operator asks before a filing

Three recurring questions. They are the ones a vendor walkthrough, an accountant meeting, or a first VAT close usually surfaces.

Do global platforms support Korean e-tax invoices?

Often through connectors, localizations, or partner add-ons, while domestic options build closer to the local steps. Ask for a live issuance-to-ledger walkthrough with corrections included.

How often should we review VAT codes?

Monthly. New items, new counterparties, and platform fees are the usual sources of miscodes. Lock periods after review so later edits keep history.

What reports should we bring to our accountant?

VAT summary tied to ledger detail, receivables and payables aging, bank reconciliation status, and a list of corrections. Add bank statements for the period.