Bookkeeping controls · 6 minute read
Draft vs. Posted Entries: What Approval-First Really Means
Approval-first bookkeeping is a deliberate split between working drafts and entries that actually count. Here is what that means for your day-to-day control.
Published · Last reviewed
The short version
- Drafts are working proposals; posted entries are the records that count.
- Owner approval is the hinge that turns a suggestion into a fact.
- Friction at approval time is a feature when it protects the books.
Two states for every entry: draft and posted
Bookkeeping problems can start when the line between a suggestion and a recorded entry becomes unclear. A draft is a proposed entry, often prepared by software, that has not yet been accepted. A posted entry is one that has been approved by the owner and written into the books.
Keeping those two states separate is the foundation of approval-first bookkeeping. The software can prepare, group, and link as many drafts as it likes, but the books only change when the owner says so.
In Fionas, connector, agent, and ingest activity produces source-linked drafts. None of that activity posts on its own. That is the point.
Related reading: How it works
What source evidence actually looks like
A draft is only useful if you can see where it came from. Source evidence is the link back to the original activity: a bank line, a statement row, a processor payout, a payroll record. Without that link, a draft is just a guess with formatting.
When you review a draft, the source link is the first thing to look at. Read the description in the draft, then read the source. If the two tell the same story, the draft is probably fine. If they do not, the draft needs attention.
When evaluating a system, ask whether that source link remains available after posting so the evidence and the recorded decision stay connected.
- Bank line is the source for a deposit or a withdrawal.
- Statement upload is the source when a bank does not connect directly.
- Processor report is the source for payouts and processor fees.
- Payroll report is the source for pay, taxes, and net amounts.
Why owner review is the hinge of the system
Approval-first systems put the owner between the draft and the post. That gap is intentional. It is where the owner adds context the software may not have, such as whether a transfer came from the owner or a customer.
The review may be brief for familiar activity or longer for an exception, but its meaning is the same. After approval, the entry is treated as the owner's recorded view of what happened.
Fionas calls this out clearly: posting requires owner approval. Software never moves money, and approval does not mean the books are correct in a tax sense. It means the owner has reviewed and accepted the entry.
- Owner adds business context the software cannot guess.
- Approval turns a draft into a recorded entry.
- The recorded entry still needs a CPA for tax and accounting conclusions.
Related reading: Founder
Risk tiers and when to slow down
Not every draft carries the same uncertainty. Familiar recurring activity may be easier to verify, while a one-off wire, an unfamiliar vendor, or a payroll adjustment deserves a slower look. Familiarity is not a substitute for checking the source.
A simple review tier can help. Straightforward entries still receive a source check; unusual entries are reviewed one at a time; entries you cannot explain stay in draft until you have enough context or professional guidance.
Approval-first software does not assign those tiers for you. The owner decides what deserves extra care.
- Straightforward: familiar activity whose source and proposed treatment agree.
- Needs attention: a new vendor, unusual timing, or a changed amount.
- Keep in draft: a wire, adjustment, refund, or other item you cannot explain confidently.
Audit history as a calm record of what happened
Every approval, edit, and post should leave a trail. An audit history is a log of who did what, when, and to which entry. For a small business, this is less about regulation and more about being able to answer your own questions later.
When a number looks wrong three months after close, the audit history is what lets you trace it back. Without it, you are guessing. With it, you can usually find the source line and the decision that put the entry there.
Fionas keeps an audit history of approvals and posts so the period's record is reconstructable, not just trusted.
Why a little friction is a feature
Friction in approval sounds like a downside, but in bookkeeping it is often a safeguard. A draft that posts instantly can bury an error before anyone notices. A draft that waits for approval slows the process just enough to be read.
Approvals matter because they create a deliberate pause between suggestion and record. The faster a workflow moves on its own, the less time there is for a human to notice something off. Approval-first designs intentionally trade raw speed for visibility.
The right amount of friction is the amount that lets you read the work without turning bookkeeping into a constant interruption. Choose a review cadence that fits your transaction volume, and keep the explicit close as a separate final decision.
Related reading: Month-end close checklist
What the software never does on its own
Fionas does not hold or move money. Mercury is the only direct bank integration. For other U.S. banks, Fionas relies on PDF or CSV statement uploads. It does not file taxes, and it does not replace a CPA.
Treat these limits as features, not flaws. They are the line between bookkeeping software and the people and institutions that actually move money, give advice, and file returns.
The owner's job is to use the software within those limits and to bring in professional advisors where the limits show.
- Fionas never holds or moves money.
- Only Mercury connects directly; other U.S. banks use PDF or CSV.
- Fionas is not a CPA, accountant, bank, lender, or advisor.
A practical approval routine
Review new drafts often enough that questions are still easy to answer. Approve proposals whose source and context you understand, flag the rest, and avoid letting unresolved items disappear into a large backlog.
During the close, use a consistent order and reconcile against the period's statements before deciding the period is ready. Close it explicitly when you are done so the workspace becomes a record.
The cadence can be daily, weekly, or tied to your transaction volume. Consistency matters more than copying someone else's schedule.
- During the period: review source-linked drafts and keep exceptions visible.
- At close: reconcile against statements and resolve or document open items.
- When ready: explicitly close the period.
- When professional review is needed: use the export format your CPA requests.
Related reading: How it works · Founder
Try approval-first drafts in your own books
Fionas prepares source-linked drafts and waits for your approval before posting. Compare plans to find the right approval rhythm for your business.