About this desk
Why we started Bryskalon in Seoul.
An independent educational site for founders and teams who keep cloud books in English and KRW — and who never trained as accountants to end up responsible for them.
Why we started
The first chart of accounts we ever set up took a weekend.
It should have taken an afternoon. What slowed it down was not the software — it was the vocabulary. Bank feeds, general ledger, statutory reporting, VAT returns: every guide we found assumed we already knew what those words meant, or was written for a reader with a finance team behind them. Neither was true.
We started Bryskalon in Seoul so that the next founder would not have to assemble the same picture from twelve tabs. The site is a research desk for cloud accounting in Korea — one place where the platforms, the workflows, and the compliance habits are explained in plain English, in the order a person actually encounters them.
The site is written for the person who ends the month reconciling a bank statement at 7pm, not for the accountant they eventually hire. We do not sell software, we do not run a demo environment, and we do not publish anything we cannot source from public platform coverage and publicly described workflows.
Written from Seoul, South Korea.
Reading language English.
Currency focus KRW and multi-currency.
Reviewed on Korean business days.
Who reads Bryskalon
Founders, remote teams, and the person holding the receipts.
A reader at a Seoul window, working through a comparison page after hours.
Our readers are small business owners in Seoul and other Korean cities, remote teams billing across currencies, and finance assistants setting up their first chart of accounts. Many work in mixed Korean and English environments: an invoice in English, a supplier in Won, a bank that reads neither the same way twice.
We keep language direct and define terms like general ledger, bank feeds, and statutory reporting on first use. If a page assumes knowledge the reader may not have, that page has a job left to do — and we would rather add a sentence than a glossary.
Solo operators
One-person businesses that need bookkeeping that does not need them.
Small teams
Two to twenty people, often with a founder still approving every invoice.
Finance assistants
The person asked to own reconciliation without a title for it.
What we research
Cloud accounting platforms, tracked from basic bookkeeping to mid-market finance.
We follow public 2026 comparison coverage and the workflows it keeps describing — reconciliation, invoicing, expense tracking, multi-currency, and VAT organization. We do not publish prices, offers, or rankings that imply testing we did not do.
Xero
Bank feeds, small-business bookkeeping, multi-currency invoices.
SMB
Zoho Books
Workflow automation, expense capture, VAT organization for smaller entities.
SMB
NetSuite
Consolidation, multi-entity reporting, larger finance operation scope.
ERP
Kashoo
Lean bookkeeping for solo operators who want fewer screens.
Basic
Business Central
ERP-style finance alongside operations, inventory, and reporting.
ERP
Sage Intacct
Mid-market finance with dimensional reporting and approval structure.
Mid-mkt
Xledger
Automation-leaning cloud ERP for structured finance operations.
ERP
Plus your vendor
If a platform is widely used in Korea and we haven't covered it, tell us.
Each platform is tracked on the same axes: scope, currency handling, integration habits, and how the workflow reads to a non-accountant. When coverage disagrees, we say so rather than pick a winner.
How comparison pages are built
The order matters more than the feature list.
Each comparison starts with scope and only then moves into detail. That order is what keeps a solo operator from buying consolidation they will never use — the trap that a features-first page sets for every reader.
-
Step 01
Establish scope
Is the product basic bookkeeping, SMB accounting, or ERP-style finance? Until that is answered, every other comparison is noise.
-
Step 02
Weigh fit, not features
Team size, entity count, currency needs, and how the team already handles tools. A feature that no one will touch is not an advantage.
-
Step 03
Then discuss automation
Transaction matching, recurring entries, and adjustments only earn a paragraph once scope and fit are settled.
-
Step 04
State the limits
Every comparison ends with what we did not test, what may vary by entity structure, and where a licensed professional in Korea should be consulted.
Independence and funding
We do not sell software. We do not run a demo environment.
Bryskalon is an independent educational site. We do not sell accounting software, we do not operate a demo environment, and we do not run vendor-funded comparison placements. Our pages are exploratory, and every call to action points outward — to a workflow the reader can review, or to the vendor directly.
When we mention a vendor capability, we stay within what 2026 public comparison coverage states. We avoid enterprise logos, badges, and invented benchmarks, because those are the things that turn an editorial page into an advertisement without telling the reader.
-
Editorial only
No sponsored rankings, no paid placements, no vendor logos.
-
Sourced claims
Every platform statement stays inside public comparison coverage.
-
Reader-first CTAs
We point to workflows and vendor pages, not to our own sales funnel.
-
No benchmarks
If we did not run the test, we do not publish a number that suggests we did.
Corrections policy
Accounting rules change. When a page is wrong, we fix the page.
What to send
The page address, the sentence that looks wrong, and what you believe the correct wording should be.
What we check
KRW handling, VAT wording, e-tax filing workflow descriptions, and platform scope claims.
When we reply
We review messages from the contact form on business days in Korea Standard Time.
What changes
Substantive fixes are updated on the page itself. We do not publish contributor names without permission.
Or write to [email protected].
What we do not do
Bryskalon is preparation, not a substitute for a professional.
We do not provide tax filing, audit, or legal advice. We do not set up your chart of accounts for you. We do not recommend a single product for every reader — the right answer for a design studio in Hongdae is not the right answer for an importer in Busan.
The useful version of this site is a shorter conversation. A founder arrives at their accountant with the right questions in order: what our entity actually is, what the bank feeds already reconcile, what will need a manual adjustment at month-end. Those answers are what make the paid hour worth its fee.
Based in Korea, written in English
Seoul districts. KRW amounts. Bilingual teams.
Our examples use Seoul districts, KRW amounts, and the situations foreign founders and bilingual teams actually meet: a client who pays in Won and expects an English invoice, a supplier who mails a paper statement, a bank feed that arrives in a format the accountant did not expect.
The statutory reporting and e-tax filing sections describe organization and workflow — what belongs where, what the month looks like, what the season changes — and not filing instructions. Always confirm filing steps with a licensed professional in Korea.
Operating base
Seoul, South Korea
Reading hours
Mon–Fri, 9:00–18:00 KST
Contact
How to suggest a topic
A short, specific request helps more than a broad one.
Use the contact page to suggest a workflow or comparison you want explained. We prioritize topics that help many readers run receivables, payables, and month-end more cleanly — so a real situation often carries further than a genre.