Editorial standards
Who Writes Our Guides and How We Keep Them Accurate
The guides explain how bookkeeping and accounting workflow automation actually works, so you can read them before you buy software. This page covers who writes them, how they are reviewed, and what happens when a platform or a practice changes.
What this site is
An educational resource, not a storefront
PaperlessFin is an educational resource. It doesn't sell software, it doesn't run a bookkeeping service, and it doesn't take a position on which tool you should buy.
The guides explain how invoice capture, coding, approvals, reconciliation, and close work, and how different categories of tools handle those steps. The goal is to help a reader understand the workflow well enough to make their own decision, not to push them toward one.
That has one practical consequence. When you read a page here, you are reading about a process and about how a category of tools behaves inside it. Naming a product is how the writing stays concrete, not how it takes a side.
Who writes the guides
Written by people who run these workflows
The guides are written by people who work with bookkeeping workflows, either in an accounting practice or in a finance function, and who have used the tools they describe.
The writing focuses on mechanics: what happens to an invoice when it is captured, how a reconciliation gets confirmed, what an audit trail needs to show. Where a tool is named, it is because the tool is a real example of the category, and the description stays within what is publicly documented about it.
-
What happens to a document between capture and posting
-
How an exception surfaces and who is expected to clear it
-
What an audit trail is expected to preserve after the fact
-
Which steps a platform handles and which stay with a person
Practice-side experience
Documentation only
Tool descriptions stay inside what the vendor publishes, and anything that goes past that is treated as an open question rather than a claim. When a guide names a product, it is to show the category at work, not to rank it against the others.
How topics are chosen
Built around the stages of the workflow
Topics come from the questions readers actually ask: how to automate bank reconciliation, what the difference is between AP automation and bookkeeping automation, when to move beyond a basic platform. The site is organized around the stages of the workflow rather than around products, so a reader can start at the stage that is causing them trouble. If a topic keeps coming up and is not covered, it gets added.
The list above is the working map, not a fixed curriculum. Pages are added when a question shows up often enough that a short answer will not do it justice, and the order you read them in does not matter.
The review process
Four checks before a guide goes live
Before a guide is published, it is checked for accuracy on the workflow mechanics and for whether the descriptions of tools match what is documented.
Steps in the right order
Does the sequence match how the work actually moves from capture to posting to reconciliation?
Exceptions covered
Duplicates, missing paperwork, a payment with no matching invoice: does the guide say who clears it?
Nothing overstated
Claims about what automation can do are held to what is realistic, with the limits written down next to the benefits.
Documentation match
Does every product description line up with what the vendor publishes today, including the parts that changed?
The line we hold
Software handles the repetition. People handle the judgment.
That distinction appears throughout the guides because it is the one readers most often get wrong. A platform can read a receipt, match a bank line, route an approval, and flag what looks wrong. It cannot decide whether an expense belongs to this period or the next one, whether a vendor is genuinely new, or whether a number needs a second look before it goes out. Those calls still belong to a person, and a guide that blurs the line sends readers into a purchase expecting something the software was never going to do.
Handled by the software
Reading documents, matching bank lines, routing approvals, flagging duplicates and mismatches.
Kept with a person
Cut-off decisions, unusual vendors, judgment calls on coding, and signing off on what goes out.
Keeping guides current
What triggers an update
Bookkeeping automation changes as platforms add features and as practices shift. Guides are reviewed periodically and updated when something material changes, whether that is a new capability in a widely used platform or a change in how a workflow is commonly handled.
The site does not chase every product announcement, because most of them do not change how the workflow works. A release note about a redesigned dashboard rarely affects the mechanics a guide describes. A change to how matching rules behave, or to what an approval step can require, usually does.
Usually worth an update
-
A capability that changes what a step can do, not how it looks
-
A shift in how teams commonly handle a step, such as where approvals sit
-
Documentation that contradicts what a guide currently says
Usually not
-
Interface refreshes that leave the workflow intact
-
Pricing changes, unless they move a tool between categories
-
Announcements with no effect on the steps a guide describes
Updates are noted where they affect the substance of a guide.
What we don't do
The limits of this resource
Stating the limits plainly is part of the editorial standard. It tells you what a guide can answer and where it stops.
- No rankings or best-of lists
- Fit depends on the workflow, and a ranking hides that. A tool that suits a two-person startup can be the wrong choice for a firm closing six sets of books.
- No invented metrics or studies
- No user counts, no survey results, no percentages we cannot point to a source for. If a number appears in a guide, it comes from something a reader can check.
- No unverifiable testimonials
- We do not publish praise we cannot trace back to a real person who agreed to it, which is why you will not find a wall of quotes here.
- No paid coverage
- We do not accept payment for coverage, and naming a tool in a guide is not an endorsement. A vendor cannot buy a mention or a favorable sentence.
- No tax or legal advice
- That depends on your situation and belongs with a qualified professional. Guides here explain how workflows and tools behave, not how your books should be filed.
Reader reports
Reviewed as they arrive
Corrections and reader input
If something is wrong, tell us
If something in a guide is wrong or out of date, we want to know. Readers can send corrections, and the ones that hold up get incorporated. The same goes for questions that are not answered anywhere on the site, since those often point to a gap.
Corrections are treated as part of keeping the resource useful, not as a complaint. A short note describing what looks off and where you saw it is enough to start. If you can point to the documented behavior you were comparing against, that usually shortens the check considerably.
Questions that come up repeatedly tend to become new pages rather than one-off replies, so a good question here can end up helping the next reader who hits the same wall.
Editorial independence
Written to explain, not to sell
No tool gets favorable treatment because of a relationship, and no tool is left out because of one. Where a category is described, the description applies to how tools in that category generally work, with a named example where it helps make the point concrete.
That is the practical test of a useful guide: the reader should be able to use it to evaluate any tool in the category, not just the one named on the page. If a description only works for a single product, it is describing the product, not the workflow, and it gets rewritten.
How to use the guides
Start with the stage of the workflow that is causing the most pain. If receipts are the problem, read the capture and reconciliation guide. If the close is always late, read the playbook. If you are comparing options, read the comparison and the evaluation criteria.
The guides are written to be read in any order, and each one stands on its own.
Found something out of date, or a question we have not answered?
Send it over and we will check it against the current documentation and the workflow itself. Corrections that hold up get folded into the guide, and questions that keep coming up tend to become their own page.
PaperlessFin, 1221 Financial District Blvd, Floor 14, New York, NY 10005 · [email protected]
Reachable Monday to Friday, 9:00 AM to 6:00 PM.