How the work is done
How Omzarell checks facts before publishing
Readers trust guidance they can verify. This page explains how Omzarell selects topics, checks claims, updates pages, and stays separate from software vendors. It is the working manual behind the comparisons and reviews.
- Postal address
- 12 Teheran-ro 14-gil, Gangnam-gu, Seoul 06235
- Reader mail
- [email protected]
- Desk hours
- Mon–Fri, 9:00–18:00
Seven working rules sit behind every page on this site. They apply the same way to a one-paragraph note and to a full platform review, and each one is written down here so a reader can hold us to it. Where a rule has a limit, the limit is stated next to it rather than buried in a footnote.
Topic selection starts with reader mail
The queue is written by the people keeping the books
We prioritize questions that arrive from owners and staff: VAT prep confusion, invoice matching breaks, close delays, and tool shortlists. If several messages from Seoul, Suwon, or Busan point the same way, that topic moves up. We do not chase release hype. Usefulness to KRW bookkeeping decides the queue.
A message that arrives with a screenshot of a broken invoice match outranks a press release every time. Where several readers describe the same problem from different offices, we treat it as a pattern rather than an incident and give it a full page instead of a note.
VAT preparation and e-tax invoice questions from small offices
openInvoice matching that breaks at month-end
openClose delays where two staff share one ledger
openShortlists readers are comparing this quarter
open
Sources we accept
Every sentence names the weight behind it
We use vendor documentation, integration directories, and market coverage that names real products. For this site that means the eight listed platforms and their stated scope.
Primary
Vendor documentation
Help centres, release notes and published scope statements. What the vendor itself says the product does, read for a stated behaviour rather than for its marketing framing.
Primary
Integration directories
Published connectors between accounting tools, banks and the Korean e-tax invoice flow. Useful for checking whether two systems actually speak to each other.
Context
Market coverage
Trade and market writing that names real products. It sets context and pricing expectations; it does not carry a verdict on its own.
We do not cite anonymous forums as fact or repeat reseller claims without checking. When only a listing supports a point, we label it as such. Readers should see the weight behind each sentence.
Comparison method
Same job, same path, same verdict scale
We compare tools that solve the same job. Entry tools face entry tools. Korean SME suites face each other. Global ERP faces global ERP.
Each test follows the same path: invoice entry, bank match, correction, and report export. That shared path keeps verdicts fair. Cross-category claims get flagged as context, not conclusions.
A number that appears in a comparison is a number the product's own documentation states. We do not estimate a value to make a table look complete.
-
01
Invoice entry
We enter a small batch of sales and purchase invoices and note how defaults are set. Whether the tax code carries over from the customer record is part of the observation.
-
02
Bank match
We match a statement line to its invoice and record how the tool handles a near-miss. Some accept an approximate match; others return it to a holding queue.
-
03
Correction
We reverse a posting and inspect the trail it leaves. Whether a correction overwrites or appends is a practical difference at close.
-
04
Report export
We export the period and check whether the figures reconcile with the ledger we just entered. Where an export loses a column, the note says so.
Need the outcome on a specific pair? The platform comparison lists the tools we hold to this same path side by side.
General ledger accuracy checks
Is the posting in the place a reviewer would expect?
Before publishing, we trace postings: does a sale hit the right ledger, tax code, and customer record, and does a correction leave a trail? We look for period controls and document links that support audit review.
If a flow is unclear in sources, we describe the limit instead of filling gaps. Accuracy notes stay practical, not theoretical: what a bookkeeper can check on a normal Tuesday, not what a textbook chapter would say about the same posting.
What we trace
Ledger account, tax code, customer record, and whether the correction is appended or replaced.
What we look for
Period locks, attached documents, and an audit trail a second person can follow months later.
Audit support standards we describe
We describe the trail, not the outcome
We describe audit support as traceability: vouchers, approvals, attached files, and exportable histories. We do not promise outcomes or filing acceptance. Each platform note states what the system records and where a reviewer finds it.
Your accountant decides sufficiency for your case. That boundary keeps advice honest: a tool can make a record easy to find, and the judgement of whether a record is enough belongs to the reviewer, not to the vendor and not to us.
Vouchers and approvals: we state what the system attaches and how the attachment is reached from the posting.
Exportable histories: we note the period length and the format a reviewer would receive.
What we do not state: that a filing will be accepted, or that a record will be judged sufficient for your situation.
Update rhythm and corrections
Rolling rechecks, with a fast lane for small fixes
Core guides are rechecked on a rolling cycle and after notable product changes such as SaaS relaunches. Small fixes go live fast. Larger changes get a full read for consistency across comparison and review pages.
Small fixes
A renamed field, a changed help-centre path, a corrected scope line. These go live quickly because they affect a single sentence rather than a verdict.
Rolling rechecks
Core guides and the eight platform profiles are re-read on a cycle, so a page that has sat untouched for a long stretch is still checked against current documentation.
Full reads
When a product relaunches, the review and its comparison row are re-read together so the two pages do not end up saying different things about the same platform.
Readers can report errors through the contact page. Confirmed fixes are noted in the text where the change affects meaning — not as a silent overwrite, so a reader returning to a page can see what moved.
Independence and money
No payment for placement. No vendor previews.
Omzarell earns nothing from rankings and takes no payment for placement. Outbound links to vendors exist so you can verify claims yourself. No vendor previews drafts.
If that policy ever changes, we will state it here first. Until then, read every comparison as editorial work.
How to test us
Follow any vendor link on a comparison page and read the same statement on the vendor's own site. Where we cite a listing rather than documentation, the note says so; where we are unsure, the note says that too.
What we will not publish
Less published, but each line stands
Some things are easy to write and impossible to check. Those are the ones we leave out, even when a topic would read better with a number attached.
-
Invented integrations, uptime stats, logos, or benchmarks. If a number would need to be estimated, it does not ship.
-
Testimonials without verifiable records. We would rather show the working than quote a customer we cannot point you to.
-
Automation promises that no demo could prove. A claim we cannot reproduce on a normal subscription is not a claim we make.
-
A requested topic that needs proof we lack. We decline or narrow the scope instead of filling the gap with a guess.
Where to go next
If you found a claim on this site that does not match what you are seeing in your own books, tell us where. That is the fastest route to a corrected page.