Bryskalon Bryskalon
Open ledger spread and a printed bank statement on a practice-room desk under soft overcast window light

Bank reconciliation · Explainer

Does your bank balance match your books?

True your books, one line at a time. This is how bank feeds, transaction matching and a weekly reconciliation habit keep a Korean small business ledger accurate and ready for month-end review.

Everything below is one ledger read top to bottom — the ruled line is the through-line, and the blue is the figure that agrees.

Where this sits

Bank reconciliation within the Bryskalon corpus

Reconciliation is one chapter of ten. Read it in order, or jump to the chapter that answers today's question.

  1. I
    Home

    What Bryskalon is and the platforms it compares.

  2. II
    About Bryskalon

    Who writes this resource and how the material is kept current.

  3. III
    Compare Cloud Platforms

    How the leading cloud accounting tools handle feeds and matching.

  4. IV
    Bank Reconciliation Explained

    You are here: feeds, matching, exceptions and audit-ready books.

  5. V
    Korea Accounting Essentials

    VAT, e-tax filing and the documents Korean accountants ask for.

  6. VI
    Invoicing and Expenses Guide

    Raising invoices, coding card spend and attaching receipts.

  7. VII
    Contact

    Ask a question about your own reconciliation before you start.

The whole idea

Bank reconciliation is the habit of matching what your bank reports against what your ledger records.

In cloud accounting it usually means connecting bank feeds, applying matching rules, and reviewing exceptions each week. Done regularly, it keeps the general ledger accurate and month-end review short — and it is the practice that turns a bank statement from a document you file into a set of lines you can trust.

Section 01

Feeds first, then rules

Bank feeds pull transactions into your accounting tool so you do not retype statements. After connection, most tools suggest matches based on amount, date and payee. You confirm or correct them.

A cafe in Seongsu-dong

Daily card settlements arrive as a steady feed. A stable connection saves hours each month compared with typing settlements from the statement.

What the feed does

Import, dedupe, classify

What you confirm

Suggested matches

What needs care

Exceptions

The feed

Daily

A connected bank feed posts new lines as they clear the account. It catches card settlements, transfers, fees and reoccurring debits without you opening the banking app.

Works best when every account you actually use is connected, not only the main current account.

The match

Amount · Date · Payee

A three-field suggestion from the tool: same amount, same date within tolerance, same counterparty name. You confirm with one click, or correct it when something is off.

Recurring rent, telecom and utilities are usually safe to remember as rules once they have matched twice.

The exception

Flagged

Anything the rule cannot place — a small bank fee, an FX difference, a duplicate import — sits in its own state until a person decides how to code it.

Leave it flagged rather than forcing a match. A padded entry is worse than an honest exception.

The description above reflects how the leading cloud accounting tools present bank feeds and matching. Depth of rules, tolerance windows and supported Korean banks still vary product by product — check the platform you intend to use.

Section 02

Why matching speed matters

Reconciliation speed is one of the most repeated differentiators in cloud accounting reviews. Faster matching means fewer unreconciled lines sitting at month-end — the queue is short, the older items do not accumulate interest of their own.

It also surfaces duplicates and missing entries early. A duplicate card settlement caught in week one is a five-second correction; the same duplicate discovered on the last day of the month is a half-day of untangling. Xero, for example, is known for bank reconciliation habits that reviewers mention often — a deep and reliable matching workflow is treated as a baseline expectation, not a premium one.

Where the delay shows
Stale lines accumulate at month-end and hide duplicates.
What speeds it up
Well-trained rules, connected accounts, and a weekly review slot.
What slows it down
Retyping statements by hand and forcing matches that do not agree.
Close view of a bank-feed import screen with an incoming transaction queue and a progress bar during a reconciliation session
A bank-feed import queue during the week — new lines arriving, most already suggested a match.
A matched ledger line under a hand holding a bank statement edge in low-key overcast light

The moment the line agrees

Every reconciled line is a small settled argument.

When the figure in your ledger and the figure on the statement finally agree, the line flips from a pending row into a matched one. No drama, no ceremony — just the ledger returning, one row at a time, from a question to a fact.

Matched

Reconciliation does not file taxes for you — it hands clean totals to whoever does.

Sections 03 & 04

A weekly routine that holds

Set a fixed time to review new lines, confirm suggested matches, and code the rest to the right ledger account. Keep receipts attached for card purchases. Leave notes on anything unclear so your accountant in Korea can resolve it without a long email thread.

A routine that fits inside a single sitting each week beats a heroic monthly session every time. The point is not to empty the queue completely — the point is to keep the current week's queue from rolling into the next one.

  1. Mon

    Open the feed, look at what arrived since the last review, and scan for anything obviously new — a first-time vendor, an unfamiliar payment.

  2. Wed

    Confirm the suggested matches in one pass. Anything you do not recognise, leave it visible and move on — do not force it.

  3. Fri

    Code the flagged exceptions. Attach receipts for anything paid by card. Leave a one-line memo on whatever you had to make a judgement call about.

Exceptions deserve attention

Unmatched deposits, small fees, and foreign-currency differences are normal. Handle them with separate categories and short memos rather than forcing a match. Over time, rules can auto-code recurring items like rent for an office near Gangnam Station. Manual review stays for new vendors and odd amounts.

Treating exceptions as a normal part of the routine keeps the ledger honest. A row that has been autopiloted into the wrong account is harder to find later than a row you flagged and left for the next look.

Hands at a keyboard on a Monday morning reconciling two lists, most rows paired and one row flagged
The Monday sitting: paired rows up top, one flagged line waiting for a decision.

The rhythm in practice

A short sitting each week with the whole feed visible

The point of the routine is not to clear the entire queue — it is to keep the current week's queue short enough to read. When each new line has a place to land, exceptions stay visible instead of hiding under a growing backlog.

When you do have to leave something unresolved, leaving it plainly unresolved — with a memo — is a healthier state than a forced match. The next sitting starts where the last one stopped.

Sections 05 & 06

Audit-ready without stress

When every bank line ties to a ledger entry with a source document, review and statutory reporting get simpler. Reconciliation does not file taxes for you, but it gives your tax agent clean totals to work from. Keep statements, invoices and receipts organized by month.

The tidy end state is not a special one. It is what a month looks like when the weekly sittings have actually happened — the statements and receipts grouped by month, the ledger reconciled line by line, nothing sitting unexplained.

A pencil-marked line on a printed bank statement beside a phone showing the bank app and a small stack of receipts
A flagged line, a pencil mark, a screened receipt — the raw material of a clean audit file.

When to ask for help

If unreconciled differences grow, if multi-currency balances confuse the ledger, or if feeds stop syncing with your Korean bank, pause and ask your bookkeeper. Bring the last three statements and a list of unmatched items. That makes the fix faster than re-entering everything.

The signal is simple: a growing pile of unmatched items and an uncomfortable feeling when you open the reconciliation screen. That is the moment to stop pushing lines through and hand the ledger to someone who works with the same tools every day.

Bring these three things

  • Your last three bank statements, monthly, in order.
  • A short list of unmatched items, even if the totals disagree by only small amounts.
  • Receipts for card purchases made in the same period, attached or scanned.
Ask Bryskalon a question

Questions that come up

Bank reconciliation, in plain answers

Is automated matching a premium-only feature?

No. Automated transaction matching against statements and feeds is described as a basic expectation in modern cloud accounting, not a premium-only feature. Availability and depth still vary by product and bank connection — check the platform you intend to use.

How often should a small business reconcile?

Weekly works for most SMBs with regular sales and expenses. High-volume sellers may reconcile twice a week; very small operators can manage every two weeks if feeds stay connected.

What if a matched line still disagrees?

Un-match it. A forced match that hides a small difference is more expensive than an honest pending row — small bank fees and FX differences belong in their own categories, not folded into a row that only nearly agrees.

How does this relate to VAT and e-tax filing?

Reconciliation gives your tax agent clean totals to work from — it does not replace filing. Keeping statements, invoices and receipts organized by month is what makes the compliance side simpler once your books are true.

Where to go next

Read the next chapter, or bring your own numbers

Reconciliation is one habit inside a wider workflow. The next chapters explain which platform best fits your business, what the Korean compliance steps look like, and how invoicing and expenses stay attached to the same ledger.

Bryskalon · 26 Eulji-ro 5-gil, Jung-gu, Seoul 04522, South Korea · Monday to Friday, 9:00 AM – 6:00 PM

The balance

One more rule about the practice: the reconciliation is never done — it is only up to date.

That is the whole discipline. A weekly sitting that keeps the ledger current, an honest pending row where the figures disagree, a receipt attached to every card purchase. Do that, and month-end stops being a scramble.

The practice file

Address
26 Eulji-ro 5-gil, Jung-gu, Seoul 04522, South Korea
Phone
+82 2-6473-3408
Hours
Monday to Friday, 9:00 AM – 6:00 PM

Bryskalon is an educational cloud accounting resource for founders operating in South Korea. Content on this page describes commonly used bank feed and reconciliation workflows; product features and bank connection support vary. Nothing on this page constitutes tax or accounting advice for your specific situation.