AI tools for accountants, read by how far they can act alone

For bookkeepers, CAS teams and in-house finance teams who already run a ledger.

Not a ranking, and not a guide to choosing your first accounting system. Three purchase decisions, each read by what the software may do without a person — and each allowed to end in buying nothing.

What this page concludes

QuickBooks Online and Xero go further than most buyers expect.Both capture, code and match — and can post some transactions without a person once a setting or plan allows it.
Buy a specialist for a bottleneck or a control, not for more AI.Each decision below names the one condition that earns a second subscription.
No bottleneck? Buy nothing.Every decision below can end there. Come back when one starts to hurt.

Where should I start?

Start from what is actually hurting

If your pain isChasing receipts, paper and emailed invoices from clients01Bookkeeping intake
If your pain isGetting bills approved and vendors paid without one person doing both02AP and payment
If your pain isA month-end close nobody else reviews or signs off03Reconciliation and close
If none of these hurtCheck what QuickBooks Online and Xero already cover firstCoverage map

Which layer is actually missing

What QuickBooks Online and Xero already cover

Seven capabilities, read against the QuickBooks Online and Xero baseline reviewed here. Other ledgers were not reviewed and may differ, so check yours against the same rows before you read a shortlist.

Capability	QuickBooks Online	Xero	Buy a specialist only when
01Bookkeeping intakeLayers compared: Dext · Sage AutoEntry · Docyt
Document read	CoveredReceipt capture in the mobile app	CoveredSmart Document Capture across plans	Messy client documents, or statement pages to capture
Coding	CoveredSuggests categories; codes familiar expenses once you opt in	CoveredSuggests matches; JAX codes confident lines on Growing and above	Supplier rules across many client files, or line-item detail
Posting	CoveredA person selects Post, unless a setting or bank rule posts first	CoveredA person accepts the match, unless JAX reconciles first	Publishing held behind a review you can point to
02AP and paymentLayers compared: BILL · Ramp · Vic.ai
Approval	Higher planA designated approver only on Bill Pay Elite	Not reviewed here	Rule-based approvals, or approve and pay held apart
Payment	CoveredBill Pay: standard ACH included; checks and faster ACH carry a fee	Not reviewed here	An auditor-ready payment trail, or fees that decide it
03Reconciliation and closeLayers compared: FloQast · Rillet (replaces the ledger)
Matching and reconciliation	CoveredSuggests matches; matches its own Payroll, Payments and Bill Pay	CoveredDaily bank feeds; JAX reconciles on Growing and above	Matching becomes a job, or spans many entities
Sign-off and period lockControl not verified natively	Sign-off not verifiedClosing date documented	Sign-off not verifiedLock dates documented	A second person must sign, and software must enforce it

Documented on the plans reviewed
Documented on a higher plan only
Control not verified natively — not shown to be absent
Not reviewed here

Buy nothing ifNobody needs a sign-off that someone other than the preparer must give. In the QuickBooks Online and Xero baseline reviewed here, most intake, matching and payment capability is already present, and both document a period lock.

Sources · Reviewed Sep 18, 2026

Scoped to QuickBooks Online and Xero only. The capability lines are the same first-party reads behind the product rows above, checked 2026-09-12, with the automatic matching, posting and journal routes re-checked 2026-09-13; the period-lock lines come from each ledger’s own help centre, re-checked 2026-09-13. Neither lock article mentions a reviewer, a preparer, a second person or a sign-off, which is recorded as Not verified rather than absent. Plan gates and regional packaging are real and are named on the rows they affect; other ledgers were not reviewed.

Document read — QuickBooks Online captures receipts in its mobile app, and Xero includes Smart Document Capture across its plans rather than selling it separately. Buy a specialist only when documents arrive on paper or by email from clients whose habits you do not control, or bank and supplier statement pages have to become data.
Coding — QuickBooks Online suggests a category or match from your history and, with auto-categorize on, codes familiar expenses itself. Xero suggests matches, and on Growing and above JAX codes the lines it is highly confident about. Buy a specialist only when supplier rules have to persist across many client files, or line-item detail below the invoice total has to be captured.
Posting — Both document a person at this step, and both document a way past that person. QuickBooks Online holds a downloaded transaction in For review until someone selects Post, unless auto-categorize or a bank rule set to Auto-post adds it first. Xero has you accept the suggested match or reconcile it yourself, unless JAX, on Growing and above and turned on for that bank account, reconciles it first. Buy a specialist only when you need publishing to be an explicit, held-behind-review act you can point at during a file review.
Matching and reconciliation — Xero connects most banks through a direct feed with daily updates, and on Growing and above JAX reconciles the matches it is highly confident about. QuickBooks Online matches its own Payroll, Payments and Bill Pay transactions automatically and suggests matches by amount and date for everything else. Buy a specialist only when volume makes matching a job rather than a task, or the same reconciliation has to be evidenced across many entities.
Approval — QuickBooks Bill Pay can require a designated approver before a payment is released, but only on Bill Pay Elite, two tiers above its base bill pay; below Elite the plan table lists no approval step. Xero’s bill approval was not reviewed here. Buy a specialist only when approvals must follow amount, department or entity rules, or approval and payment must be permissions one person cannot hold at once.
Payment — QuickBooks Bill Pay pays vendors from the ledger: standard ACH is included, and checks and faster ACH carry a per-transaction fee. Xero’s payment options were not reviewed here. Buy a specialist only when the payment run itself needs a trail an auditor will accept, or you are paying enough vendors that the fee schedule becomes the decision.
Sign-off and period lock — Both document a period lock: QuickBooks Online through a closing date that later yields to a warning or a password, Xero through lock dates set by the administrator role, which can also remove them. Neither lock article mentions a preparer-and-reviewer separation or a second-person sign-off, so that control is Not verified here — not shown to be absent. Buy a specialist only when someone other than the preparer has to sign the close, and the separation has to be enforced by the software rather than kept as a convention.

Reading the tables

Automatica documented route with no person
Rule-boundno person, inside limits you set
Humana person, and no route around them found
Not verifiedno first-party source either way

Human checkpointevery documented route passes a person
Can be skippeda route skips the step — not automation
Point of no return

What each state means, and which one a cell shows

Automatic: A first-party source documents a route where this happens without a person.
Rule-bound: Documented as happening without a person, but only inside controls you define — thresholds, rules, schedules, approver tiers.
Human: A first-party source documents a person performing or approving this, and no route that does it without a person was found.
Not verified: No sufficient first-party source was established either way.

Where a product documents more than one route through a step, the cell shows the furthest the software is documented to go without a person: Automatic over Rule-bound over Human. A route that skips the step altogether is not automatic; the cell keeps its state and is marked Can be skipped. A human checkpoint is drawn only on a step every documented route has to pass through with a person. The row names the plan, the setting or the rule each route depends on, and the manual route that remains.

Decision 01 · Bookkeeping intake

Do you need a preparation layer beyond the ledger you already run?

Everything here reads documents. What separates them is the last step: whether the work stops at a suggestion you accept, or whether the product writes into your books itself.

Your ledger is enough when

The bank feed is the source, the chart of accounts is stable and documents are the exception. If intake is not what is failing, this decision ends here.

Add a specialist when

Documents arrive on paper or by email from clients whose habits you do not control, or bank and supplier statement pages have to become data.

1Read
Pulls the document or the bank feed in
2Code
Proposes an account, a supplier and a tax treatment
3Post
Writes the transaction into the books
Point of no return. Once it posts, it is your ledger. Correcting it is an audit trail, not an undo.

Bookkeeping intake: each product read across Read, Code and Post
Tool	How far it acts	When it fits	Price and gates
Already in your ledger
QuickBooks Online ↗NativeIs the ledgerThe ledger, with capture already inside the plan you pay for	ReadAutomatic CodeAutomatic PostAutomatic No human checkpoint — every step has a documented route without a person	Choose whenThe feed is the source and documents are the exception. Skip ifChasing client receipts is the job you need solved.	From $38/mo (Simple Start), by plan tier and user count. SettingPosting without a person needs an opt-in or an Auto-post bank rule
Why this reading · 6 first-party sources Checkpoint No documented human checkpoint in this path. Every step has a documented automatic or rule-bound route; where that route depends on a plan or a setting, the row says so. Authority Transactions sync automatically and QuickBooks suggests a category or match from your history. Three documented routes act without a person: auto-categorize, once someone opts in, adds the familiar expenses QuickBooks is highly confident about; a bank rule set to Auto-post adds whatever that rule covers; and automatic matching, while it is turned on, matches QuickBooks’ own Payroll, Payments and Bill Pay transactions. Anything else waits in For review until a person selects Post. What it is The ledger, with capture already inside the plan you pay for Best for Firms whose intake is already inside the ledger and whose clients send clean feeds rather than paper. Choose when The feed is the source and documents are the exception. Skip if Client-side document collection is not what this is for. If chasing receipts is the job, the ledger is not the tool that solves it. Billing driver Plan tier and users, with payroll and payments as separate add-ons. Price detail Simple Start $38, Essentials $85, Plus $140, Advanced $340 per month. The 50%-off-for-three-months rate shown first is promotional; payroll, payments and live bookkeeping are priced separately. Platform dependency Is the ledger Material risk Everything already lives here, so a suggestion posted without reading it is a wrong number in the books with nothing further between it and the report. Bank and card transactions arrive automatically; receipt capture is in the mobile app. The features page itself does not say who confirms a categorisation; the bank-transactions help below does. QuickBooks Online accounting features page, reviewed 2026-09-12 Standing US monthly plans are Simple Start $38, Essentials $85, Plus $140 and Advanced $340. The rates shown first on the page are a 50%-off-for-three-months promotion, not the renewal price. QuickBooks Online pricing, reviewed 2026-09-12 QuickBooks automatically suggests matches for downloaded transactions with the same amount within a date range, and suggests the most likely match or category from your history. Downloaded transactions "won’t affect your books until you match or categorize them": a person reviews the transaction and selects Post. QuickBooks Online help, "Match your bank and credit card transactions" and "How AI suggestions help match and categorize bank transactions", reviewed 2026-09-13 Once a user opts in with "Yes, categorize familiar expenses for me", QuickBooks categorizes and adds to the books the expenses it is highly confident about; the rest are left for a person to categorize, and auto-categorized ones can be undone back to For review. Listed for Simple Start, Essentials, Plus, Advanced and Intuit Enterprise Suite. QuickBooks Online help on automatically categorizing expenses, reviewed 2026-09-13 A bank rule categorizes the transactions it applies to. With Auto-post turned on under "Automatically confirm transactions this rule applies to", those transactions are added to the books automatically; without it they carry a RULE badge and wait in For review. Listed for Simple Start, Essentials, Plus and Advanced, among other plans. QuickBooks Online help on setting bank rules to categorize transactions, reviewed 2026-09-13 New downloaded bank transactions must be matched manually, except that QuickBooks matches transactions from QuickBooks Payroll, Bill Pay and Payments automatically. Automatic matching is turned on or off from the bank transactions settings; the article does not say whether it starts on, and notes it may not be available in all accounts yet. QuickBooks Online help on automatic matching for QuickBooks product transactions, reviewed 2026-09-13
Xero ↗NativeIs the ledgerThe other native baseline, where reconciling is left to a person or to JAX, account by account	ReadAutomatic CodeAutomatic PostAutomatic No human checkpoint — every step has a documented route without a person	Choose whenYou want to choose, account by account, what JAX reconciles. Skip ifYour practice is outside the US; plans and prices differ by country.	From $25/mo (Early), by plan tier, priced regionally. Tier gateJAX needs Growing or above, switched on per bank account
Why this reading · 3 first-party sources Checkpoint No documented human checkpoint in this path. Every step has a documented automatic or rule-bound route; where that route depends on a plan or a setting, the row says so. Authority Xero suggests a match and you accept it or reconcile the line yourself. With JAX turned on for a bank account, Xero reconciles a new statement line itself when it is highly confident, using a bank rule, an existing record or how similar lines were reconciled before, and leaves anything it is unsure of for you to accept. Plan and setting JAX, the route that reconciles without a person, needs Growing ($55/mo) or above and is turned on per bank account. Without it, the documented route is a person accepting a suggested match or reconciling manually. What it is The other native baseline, where reconciling is left to a person or to JAX, account by account Best for Firms that want to choose, bank account by bank account, whether confident matches reconcile themselves or wait for a person. Choose when You want posting held for a person on the accounts where that matters, and left to JAX on the routine ones. Skip if Plan names, payroll and expense packaging differ by country, so a US quote does not transfer to a UK or AU practice. Billing driver Plan tier, packaged differently by country. Price detail Early $25, Growing $55, Established $90 per month in the US. The $2.50 / $5.50 / $9 headline is a six-month promotion, not the standing rate. Platform dependency Is the ledger Material risk The cheapest plan caps transaction volume, so a growing practice discovers the real price at the point it can least afford to migrate. Bank feeds connect directly for daily updates, Xero suggests reconciliation matches, and the user accepts them or reconciles manually. Smart Document Capture is included across plans. Xero US accounting software page, reviewed 2026-09-12 Standing US monthly plans are Early $25, Growing $55 and Established $90. The headline $2.50 / $5.50 / $9 rates are a six-month promotion. Xero US pricing, reviewed 2026-09-12 JAX reconciles new statement lines by applying a bank rule, matching an existing Xero record, or following how you or other Xero users reconciled similar transactions. When it is highly confident it "goes ahead and reconciles the transactions"; when in doubt it suggests a match and leaves the final say to you, and you can accept it or reconcile manually. JAX needs the Growing plan or above and is turned on for each bank account. Xero US bank reconciliation page, reviewed 2026-09-13
Specialist layers
Dext ↗Document layerWrites backPractice-oriented client document collection, with extraction on top	ReadAutomatic CodeAutomatic PostNot verified No human checkpoint documented — Post not verified either way	Choose whenChasing client documents stalls everything behind it. Skip ifClients already send clean digital records.	By document volume for businesses; per client, minimum ten, for practices.
Why this reading · 1 first-party source Checkpoint No documented human checkpoint in this path. Post is not verified, so this does not mean the product runs unattended. That is the question to put to the vendor in writing. Authority The vendor states every expense is "automatically categorised and submitted to your accounting software". Whether submission can be held behind a reviewer — the difference between a suggestion and a posting — is not documented on the pages reviewed, so this is the question to settle before a client file is connected. What it is Practice-oriented client document collection, with extraction on top Best for Multi-client practices where the bottleneck is getting documents out of clients at all, not reading them. Choose when Client document chasing is the step that stalls everything behind it. Skip if If your clients already send clean digital records, you are paying per client for a collection problem you do not have. Billing driver Documents per month, or client count on a practice plan. Price detail Business plans are tiered by documents per month. Practice pricing is per client per month with a ten-client minimum. Amounts are regional, so a US figure does not transfer. Platform dependency Submits categorised documents into the connected ledger. It does not become one. Material risk A layer that submits into the ledger is writing your books. Until publishing can demonstrably be held behind review, the correction trail is the only control you have. Documents are collected by mobile scan, email, invoice fetch and bank feed; extraction is automatic; "every expense is automatically categorised and submitted to your accounting software". Practice pricing is per client per month with a ten-client minimum. Dext product site, reviewed 2026-09-12
Sage AutoEntry ↗Document layerWrites backCredit-metered capture, and the only row here that turns statement pages into data	ReadAutomatic CodeAutomatic PostRule-bound No human checkpoint — every step has a documented route without a person	Choose whenStatement pages must become data, with publishing set per supplier. Skip ifStatement-heavy months would cost several times a normal one.	From $13/mo for 50 credits, spent per document. SettingAuto-Publish is switched on supplier by supplier
Why this reading · 5 first-party sources Checkpoint No documented human checkpoint in this path. Every step has a documented automatic or rule-bound route; where that route depends on a plan or a setting, the row says so. Authority A person publishes from the inbox once a supplier, category and tax code are set. Auto-Publish removes that click for the suppliers you choose: save default codes for a supplier, switch Auto-Publish on, and AutoEntry fills in those codes and publishes each invoice from that supplier once extraction succeeds. Setting it up needs the Company Settings permission and a connected ledger, and AutoEntry advises against it with Sage 50 or QuickBooks Desktop. What it is Credit-metered capture, and the only row here that turns statement pages into data Best for Catch-up and clean-up work, where bank and supplier statements have to become data and you decide supplier by supplier whether publishing waits for a person. Choose when You need statement pages captured, with a publish click in front of the ledger for every supplier you have not chosen to automate. Skip if The credit meter punishes exactly the work it is best at. A statement-heavy month costs several times a normal one. Billing driver Credits per document — and a page of a bank statement costs three times a receipt. Price detail Bronze 50 credits $13, Silver 100 $24, Gold 200 $46, Platinum 500 $103, Diamond 1,500 $298, Sapphire 2,500 $469 per month. One credit per invoice or receipt, two with line items, two per supplier statement, three per page of a bank or card statement. Unused credits are kept for up to 90 days. Platform dependency Publishes to Sage, Xero, QuickBooks, FreeAgent and other supported ledgers, either when a person clicks Publish or through Auto-Publish for the suppliers set up for it. Material risk Budgeting on invoice count understates a clean-up engagement by a multiple, because statement pages are the expensive unit. "When you have captured and categorized your documents, all you need to do is click on the publish button!" Supported packages listed as Xero, Sage, QuickBooks, FreeAgent, KashFlow, SortMyBooks and ClearBooks. AutoEntry features page, reviewed 2026-09-12 An invoice needs a supplier, category and tax code before it can be published, and a person publishes it from the inbox or the invoice view. "If you set up default categories and activate auto-publish in your settings, you can automate the publication of your invoices." AutoEntry Help Center, "Publish an invoice to accounting software", reviewed 2026-09-13 Auto-Publish is switched on per supplier after default codes are set under Remembered VAT Code / Category; the system then fills in the default codes and triggers publication whenever an invoice for that supplier is uploaded and extracted. It needs the Company Settings permission and a connected integration, and is not recommended with Sage 50 or QuickBooks Desktop. AutoEntry Help Center, "Auto-Publish", reviewed 2026-09-13 Defaults can apply to all invoices, or rules can apply under specific conditions; automatic publication can be activated once defaults are set. The product page lists "Auto-publish rules" that publish supplier invoices matching supplier coding rules, with exceptions kept for review. AutoEntry Help Center, "Automation in AutoEntry", and AutoEntry AI accounting automation page, reviewed 2026-09-13 Credit costs and plan amounts as listed, with unused credits kept for up to 90 days. AutoEntry pricing page, reviewed 2026-09-12
Docyt ↗AI-native ledgerLedger link not verifiedA platform rather than a layer — capture, coding, bill pay and a daily soft close	ReadAutomatic CodeAutomatic PostNot verified No human checkpoint documented — Post not verified either way	Choose whenYou want daily live books and intake in one platform. Skip ifQuickBooks must stay the ledger and sync is unresolved.	Quoted, from $299/mo.
Why this reading · 2 first-party sources Checkpoint No documented human checkpoint in this path. Post is not verified, so this does not mean the product runs unattended. That is the question to put to the vendor in writing. Authority Docyt documents a daily soft close on its own ledger, near-total document-to-transaction matching, and an approval workflow on bills. None of that is a statement about who may write a bookkeeping transaction, and this page will not turn a close cadence into a posting-authority claim. Ask specifically whether posting can be held behind a reviewer — on a platform that also holds the ledger, it is the only gate there is. What it is A platform rather than a layer — capture, coding, bill pay and a daily soft close Best for Operators who want daily financials and are willing to move the book of record onto the vendor to get them. Choose when You want live books daily and the whole intake function in one place. Skip if Not a document layer on your existing ledger. If keeping QuickBooks as the system of record is non-negotiable, resolve the sync question before anything else. Billing driver Transaction volume, plus the reporting scope agreed at quote. Price detail The vendor states plans start at $299/month and asks for transaction volume, chart of accounts and reporting needs to quote a plan. Platform dependency The vendor describes Docyt maintaining its own ledger. Whether and in which direction it syncs to an existing QuickBooks file was not established. Material risk If the platform holds the ledger, it also holds your working papers. Establish the export before the migration, not after. "Automate invoice capture and coding, then route each bill through the right approval workflow"; Docyt "soft-closes the books every single day"; the vendor describes maintaining its own ledger with continuous bank and card reconciliation. Docyt product site, reviewed 2026-09-12 "Plans start at $299/month", with a custom quote based on transaction volume. Docyt pricing page, reviewed 2026-09-12

Settle firstA product that publishes into the ledger is writing your books. Before you connect a client file, establish who may publish, whether publishing can be held behind a reviewer, and what the correction trail looks like afterwards.

Sources for this decision · Reviewed Sep 18, 2026

Capture, coding and posting behaviour read from each vendor’s own site on 2026-09-12, with QuickBooks Online’s bank-transaction help, Xero’s reconciliation page and AutoEntry’s help centre read on 2026-09-13. AutoEntry documents a person clicking Publish and, supplier by supplier, an Auto-Publish setting that publishes on the default codes you saved, so its Post cell reads Rule-bound. QuickBooks Online and Xero document a person at posting too, and also a route that posts without one once a setting or plan allows it, so their Post cell reads Automatic and the row names the conditions. Dext and Docyt are recorded as the evidence found them. A cell marked Not verified means no first-party source established it either way — it is not evidence that the product cannot do it.

AI Bookkeeping Software Ranked: AI accounting software

Decision 02 · AP and payment

How far should software go from reading an invoice to moving the money?

The only decision on the page whose last step is your bank account. The question is not how much AI a product has, but whether approval and payment are separate permissions — and whether one person can hold both.

Your ledger is enough when

One named approver in front of payment covers it. QuickBooks sells payment-release approval and approval workflows in Bill Pay Elite, two tiers above its base bill pay.

Add a specialist when

Approvals have to follow amount, department or entity rules, invoices must be checked against purchase orders and receipts, or the payment run needs a trail an auditor will accept.

1Read
Captures the invoice and its line items
2Match
Checks it against the purchase order and the receipt
3Approve
Clears the bill for payment
4Pay
Releases the money to the vendor
Point of no return. The only step on this page whose failure mode is money already gone.

AP and payment: each product read across Read, Match, Approve and Pay
Tool	How far it acts	When it fits	Price and gates
Already in your ledger
QuickBooks Bill Pay ↗NativeIs the ledgerAP inside the ledger, with the approval control sold two tiers up	ReadAutomatic MatchNot verified ApproveHumanCan be skipped PayRule-bound No guaranteed human checkpoint — Approve can be skipped: no approval step below Bill Pay Elite; Match not verified	Choose whenOne approver is enough, and they are already in the ledger. Skip ifInvoices must be matched to purchase orders and receipts.	By Bill Pay tier; standard ACH included, checks $1.50, faster ACH $10. Tier gateApproval needs Bill Pay Elite ($45/mo)
Why this reading · 3 first-party sources Checkpoint No guaranteed human checkpoint in this path. Approve is done by a person when it runs, but a documented route skips it altogether — which is not the same as automating it. QuickBooks lists payment release approval, approval workflows and approval roles only on Bill Pay Elite; Bill Pay and Bill Pay Premium list no approval step between a bill and its payment. Match is not verified, so this does not mean the product runs unattended. That is the question to put to the vendor in writing. Authority Bills are pre-filled from an emailed or uploaded invoice. On Elite, a designated approver can be required before a payment is released, and approval workflows route bills by amount, vendor or location; a request nobody reviews within 30 days is denied, not approved. Whether a bill that meets none of a workflow’s conditions still needs approval is not stated. Matching against a purchase order and a receipt is not documented, so whether software acts at that step or waits for a person is not established — that is the question to settle before treating this as your AP control. Plan and setting Payment release approval, bill approval workflows and roles that limit who approves and pays all need Bill Pay Elite ($45/mo, included with QuickBooks Online Advanced). Bill Pay and Bill Pay Premium list none of them. What it is AP inside the ledger, with the approval control sold two tiers up Best for Teams whose bill volume fits the ledger and who mainly need one named approver in front of the payment. Choose when The approval you need is one person, and the ledger already has them in it. Skip if No documented two- or three-way matching. If invoices have to be checked against purchase orders and receipts, this is not the product that does it. Billing driver Bill Pay tier — and the tier is what buys the approval control, not just the payment speed. Price detail Standard ACH is included and takes 3–5 business days; checks are $1.50 per transaction and take 8–10 business days; faster ACH is $10; the instant payment option is 1% of the transaction with a $100 maximum and a $10 minimum transaction. Platform dependency Is the ledger Material risk Buying AP below Elite buys a payment rail with no sign-off in front of it, and the gap is a plan setting rather than anything visible in the workflow. "Email or upload invoices to QuickBooks. AI pulls the details and creates pre-filled bills with dates, terms, category, and line-items"; "Designate an approver so payment isn’t released without the right sign-off" (Premium and Elite); "Set rules to require sign-off before money moves" and "Route bills to the right people with custom workflows" (Elite); standard ACH included, check $1.50, faster ACH $10, instant payment 1% with a $100 maximum. QuickBooks Bill Pay product page, reviewed 2026-09-12 The plan table ticks Roles and permissions, Payment release approval ("Designate an approver so payment isn’t released without the right sign-off") and Bill approval automation for Bill Pay Elite only, not for Bill Pay ($0) or Bill Pay Premium ($15/mo); the page notes user roles and approval workflows are "Only available in QuickBooks Bill Pay Elite or QuickBooks Online Advanced". Elite is $45/mo and included with QuickBooks Online Advanced. QuickBooks Bill Pay plan table, reviewed 2026-09-13 Bill Pay Elite customers can add a bill approval workflow, and Elite or QuickBooks Online Advanced customers a payment release workflow, with conditions on amount, vendor or location. A bill or payment release not reviewed after 30 days is automatically denied. The article does not say what happens to a bill that meets no condition. QuickBooks Online help on bill approval and payment release workflows, reviewed 2026-09-13
Specialist layers
BILL ↗AP & paymentsTwo-way syncThe approval chain is the product, and it reaches the bank account	ReadAutomatic MatchAutomatic ApproveHumanCan be skipped PayRule-bound No guaranteed human checkpoint — Approve can be skipped: an administrator can turn approvals off or pay unapproved bills	Choose whenThe approval chain itself is what you are buying. Skip ifAt hundreds of payments a month, fees can outrun the subscription.	$49–$89 per user per month, plus a fee on every payment.
Why this reading · 3 first-party sources Checkpoint No guaranteed human checkpoint in this path. Approve is done by a person when it runs, but a documented route skips it altogether — which is not the same as automating it. BILL’s settings let an administrator turn the approval step off, and an administrator can pay a bill that has not been approved even when a policy is in place. Authority BILL routes each invoice to approvers under policies you configure, and payment follows across ACH, card, check and international wire. Where approval runs, a person gives it; no route that approves a bill without a person was documented. What it is The approval chain is the product, and it reaches the bank account Best for Firms and finance teams that need a documented approver chain across many vendors and a payment rail with a trail behind it. Choose when The approval chain itself is what you are buying. Skip if Per-payment fees make the meter, not the seat price. At a few hundred payments a month the fees can exceed the subscription. Billing driver Seats, then a fee on every single payment and a higher one for speed. Price detail Essentials $49, Team $65, Corporate $89 per user per month; Enterprise quoted. The accountant partner console is $49/month. Payer fees include ACH $0.59, check $1.99, virtual card free, Pay Faster ACH $11.99, overnight check $24.99, international USD wire $19.99, and 2.9% to pay by credit or debit card. Platform dependency Vendor states BILL data syncs with the accounting software to keep the general ledger up to date; QuickBooks Online, Xero, NetSuite, Sage Intacct and Dynamics are listed. Material risk A product that holds both the approval chain and the payment rail has no second pair of eyes in it unless you configure one. "BILL AI automatically codes multi line items bills"; "automates 2- and 3-way matching"; "As each invoice comes in, BILL matches it to the right workflow and directs it to the right people for approval"; payment by ACH, virtual card, check and international wire; "Sync your BILL data with your accounting software to keep your general ledger up to date automatically." BILL accounts payable product page, reviewed 2026-09-12 Approvals "are not required to pay bills through BILL": the approval step is enabled or disabled in settings by an administrator or a user allowed to edit company preferences. "Administrators can pay unapproved bills, even if an approval policy is in place, as long as those bills have the required approvers assigned." No automatic approval is described. BILL Help Center, "How to manage approval workflows and policies", reviewed 2026-09-13 Plan and per-transaction fees as listed. BILL pricing page, reviewed 2026-09-12
RampAP & paymentsTwo-way syncCard-led spend platform with AP attached, and no software fee in front of it	ReadAutomatic MatchAutomatic ApproveRule-bound PayRule-bound No human checkpoint — every step has a documented route without a person	Choose whenCard spend and bill pay should sit under one set of permissions. Skip ifYou will not move card spend onto the platform.	Bill Pay on the free plan, with no monthly software fee; you pay per payment. Tier gateRouting by vendor, department, entity or PO match needs Ramp Plus
Why this reading · 2 first-party sources Checkpoint No documented human checkpoint in this path. Every step has a documented automatic or rule-bound route; where that route depends on a plan or a setting, the row says so. Authority Ramp names the control in the buyer’s own vocabulary: "Decide who can view, approve, or pay — and keep separation of duty." Approval runs through a workflow you build, and that workflow can approve a bill itself: an Approve bill step ends the chain early, so a branch of your conditions can approve a bill without an approver, and later bills in a recurring series are auto-approved unless their creator requires approval for each one. A separate Payment Release setting can require a named payer to release every payment. Plan and setting Amount-based approval routing is on every plan; conditions on vendor, department, entity, location, purchase-order match and GL fields need Ramp Plus. What it is Card-led spend platform with AP attached, and no software fee in front of it Best for Teams that want AP without a software line item, and want approval and payment to be separable permissions by default. Choose when Card spend and bill pay should sit under one set of permissions. Skip if The economics assume you move card spend and, ideally, the cash onto the platform. If you will not, the free tier is not really the price. Billing driver Per payment and by method — and the free software is paid for by the spend you route through it. Price detail Standard ACH $0.59, check $1.99, same-day ACH $10, domestic wire $15, international wire $20. Fees are waived when paying from a Ramp Checking Account, except overnight check delivery and attachments. Ramp Plus is $15 per user per month plus a platform fee based on team size. Platform dependency Vendor states it syncs in real time with the ERP with no double entry; NetSuite, QuickBooks and Sage Intacct are named. Material risk Free software with a payment meter moves the cost where it is hardest to forecast, and the incentive is to centralise more spend than you planned to. "Ramp’s OCR captures each detail and line item with 99% accuracy"; 2-way and 3-way match; "Ramp automatically routes every bill to the right approver"; "Decide who can view, approve, or pay—and keep separation of duty"; payment by ACH, card, check and international wire; "Ramp Bill Pay is available on our free plan with no monthly software fee." Ramp Bill Pay product page, reviewed 2026-09-12 The approval workflow builder offers an "Approve bill" step, "A terminal action that ends the workflow early if added to the chain". The first bill in a recurring series goes through the workflow; when "Require approvals for each recurring bill" is off, "subsequent bills are auto-approved by Ramp". Payment Release can require a designated payer to release each payment. Amount routing is on all plans; other conditions need Ramp Plus. Ramp Help Center, "Bill Pay approvals", reviewed 2026-09-13
Vic.ai ↗Automation layerLedger link not verifiedVolume invoice processing in front of an ERP you keep	ReadAutomatic MatchNot verified ApproveNot verified PayNot verified No human checkpoint documented — Match, Approve and Pay not verified either way	Choose whenInvoice volume is the problem and the ERP stays put. Skip ifYou cannot run a months-long, sales-led evaluation.	Quoted. The vendor’s pricing page requests a demo rather than listing a plan.
Why this reading · 2 first-party sources Checkpoint No documented human checkpoint in this path. Match, Approve and Pay are not verified, so this does not mean the product runs unattended. That is the question to put to the vendor in writing. Authority This row is the reason the page has an unverified state. The vendor ships an Approvals module and a payment product, and describes processing as autonomous — but no first-party source reviewed establishes who approves or what releases a payment. Until that is answered in writing there is no locatable human checkpoint, and that is a procurement finding rather than a gap in the product. What it is Volume invoice processing in front of an ERP you keep Best for High-volume AP teams already on a major ERP, evaluating against an implementation rather than a signup. Choose when Invoice volume is the problem and the ERP is staying exactly where it is. Skip if Sales-led with no published plan, so implementation scope and support are part of the number and the evaluation is months, not an afternoon. Billing driver Invoice volume, entity count and integration scope, agreed at contract. Platform dependency Vendor states it integrates with major ERP and accounting systems. What it writes back was not established. Material risk Buying autonomy you cannot see the boundary of is how a payment authority ends up delegated by an implementation decision rather than a policy one. "Autonomous invoice processing that minimizes errors and speeds up the month-end close"; an Approvals module and VicPay are listed as products; "Vic.ai integrates seamlessly with all major ERP and accounting systems". Whether a human approves, whether it posts to the ERP, and what executes a payment are not stated. Vic.ai product site, reviewed 2026-09-12 The pricing page carries no plan amount and routes to sales. Vic.ai pricing page, reviewed 2026-09-12

Hard lineApproval authority and payment authority are separate permissions. Never give software standing payment authority without a named approver, an amount threshold and a vendor list you control — and settle in writing how a change of vendor bank details is verified, because that is the step fraud actually uses.

Sources for this decision · Reviewed Sep 18, 2026

Capability, approval and payment behaviour read from each vendor’s own product and pricing pages on 2026-09-12, with QuickBooks Bill Pay’s plan table and approval-workflow help, BILL’s approval settings and Ramp’s approval help re-read on 2026-09-13. "Supports approvals" was not accepted as evidence that every payment is human-approved; where a source did not separate the two, the cell says Not verified. An approval that a documented setting, plan or role can skip is marked Can be skipped and is not drawn as a checkpoint — and is not called automatic either, because nothing approved the bill.

On the two fee schedules

BILL and Ramp reach the same last step and charge for it in opposite ways: a seat price plus per-payment fees against no software fee and per-payment fees alone.

Neither is cheaper in the abstract. Count your monthly payments by method first, then read both fee tables against that number.

AI Accounting Software

Decision 03 · Reconciliation and close

Do you need faster matching, or a governed close?

Faster matching lives inside the ledger you already own. A governed close is a different purchase: preparer and reviewer as separate roles, evidence attached to each balance, and a period you can lock.

Your ledger is enough when

One entity, clean feeds, and a review nobody needs the software to enforce. QuickBooks Online and Xero, the two ledgers reviewed here, already match some transactions without a person on the conditions their rows name, and document a period lock.

Add a specialist when

Someone other than the preparer has to sign the close, and the software has to enforce it. If you cannot name that person today, you would be buying faster matching you already have.

1Pull
Reads balances and transaction detail out of the ledger
2Match
Reconciles transactions against the statement
3Adjust
Creates the journal entry that changes a balance
Point of no return. A journal entry changes a reported number. It is the close, not a step towards it.
4Sign off
A second person accepts the account as reconciled
5Lock
Closes the period so the numbers stop moving
Point of no return. Everything filed, reported or lent against downstream assumes this held.

Reconciliation and close: each product read across Pull, Match, Adjust, Sign off and Lock
Tool	How far it acts	When it fits	Price and gates
Already in your ledger
Xero ↗NativeIs the ledgerReconciliation as the central daily surface, already paid for	PullAutomatic MatchAutomatic AdjustRule-bound Sign offNot verified Human checkpoint hereLockHuman Human checkpoint at Lock — Sign off not verified before it	Choose whenMatching is the work; review is a conversation, not a control. Skip ifA second sign-off must be enforced, and Xero has not shown it in writing.	From $25/mo (Early), by plan tier, priced regionally. Tier gateJAX needs Growing or above, switched on per bank account
Why this reading · 6 first-party sources Checkpoint A person is documented at Lock on every route. The steps after it keep reading on their own states. Sign off before this checkpoint is not verified: the evidence does not establish whether software acts there or waits for a person. Authority With JAX turned on for a bank account, Xero reconciles the statement lines it is highly confident about and suggests the rest for a person to accept or reconcile manually. Journals belong to the administrator or manual-journals role: entered by hand, or set up as a repeating journal that Xero creates on its schedule and, when set to Post rather than Save as draft, posts without waiting for a person. A lock date is set by the administrator role, which can also remove it. Reviewer sign-off as a separate, enforceable role is not documented on the pages reviewed, and this page will not infer one from a plan comparison. Plan and setting JAX, the route that reconciles without a person, needs Growing ($55/mo) or above and is turned on per bank account. Without it, the documented route is a person accepting a suggested match or reconciling manually. What it is Reconciliation as the central daily surface, already paid for Best for One entity, one reviewer, and a close that is a routine rather than a control. Choose when Matching is the work and the review is a conversation, not a control. Skip if The pages reviewed document no preparer-and-reviewer separation. If a second person’s sign-off has to be enforced by the software, get Xero to show you that in writing before relying on it. Billing driver Plan tier; consolidation across entities is not in the plan. Price detail Early $25, Growing $55, Established $90 per month in the US, after a six-month promotional rate. Multi-entity consolidation is an add-on market rather than a plan feature. Platform dependency Is the ledger Material risk A close nobody else signed is a close with one point of failure, and nothing on the pages reviewed would flag that it happened. Bank feeds connect directly for daily updates, Xero suggests reconciliation matches, and the user accepts them or reconciles manually. Smart Document Capture is included across plans. Xero US accounting software page, reviewed 2026-09-12 Standing US monthly plans are Early $25, Growing $55 and Established $90. The headline $2.50 / $5.50 / $9 rates are a six-month promotion. Xero US pricing, reviewed 2026-09-12 JAX reconciles new statement lines by applying a bank rule, matching an existing Xero record, or following how you or other Xero users reconciled similar transactions. When it is highly confident it "goes ahead and reconciles the transactions"; when in doubt it suggests a match and leaves the final say to you, and you can accept it or reconcile manually. JAX needs the Growing plan or above and is turned on for each bank account. Xero US bank reconciliation page, reviewed 2026-09-13 Only users with the administrator or standard + manual journals role can add and post manual journals; a journal is entered by a person and saved as a draft or posted straight to the general ledger. The article does not mention a second person approving a journal before it posts. Xero Central, "Add, import and post manual journals", reviewed 2026-09-13 A repeating journal has Xero "automatically create journals in a weekly or monthly series", each set to Save as draft or Post. Xero advises Save as draft when the journal needs approving first and Post when it is the same each time; once set to Post it cannot return to draft. Creating one needs the administrator or standard + manual journals role. Xero Central, "Set up a repeating journal", reviewed 2026-09-13 A lock date stops users adding or editing transactions dated on or before it, and can apply to all user roles or all except the administrator role. The administrator role is needed to set and change lock dates, and can remove them temporarily. The article does not mention a reviewer, a preparer, a second person or a sign-off. Xero Central, "Set up or remove lock dates", reviewed 2026-09-13
QuickBooks Online ↗NativeIs the ledgerMatching and period close for one entity, inside the plan you have	PullAutomatic MatchAutomatic AdjustNot verified Sign offNot verified Human checkpoint hereLockHuman Human checkpoint at Lock — Adjust and Sign off not verified before it	Choose whenThe close is routine and the entity count is one. Skip ifYou need to consolidate a second entity.	From $38/mo (Simple Start), by plan tier and user count. SettingAutomatic matching is a setting, and covers QuickBooks’ own transactions
Why this reading · 5 first-party sources Checkpoint A person is documented at Lock on every route. The steps after it keep reading on their own states. Adjust and Sign off before this checkpoint are not verified: the evidence does not establish whether software acts there or waits for a person. Authority With automatic matching turned on, QuickBooks matches downloaded transactions from its own Payroll, Payments and Bill Pay products itself; Intuit notes the setting may not be in every account yet. Every other downloaded transaction is only suggested, and does not affect the books until a person matches it and selects Post. Roles and access levels are documented, and so is closing the books: an admin sets a closing date, after which changes need a warning or a password. Adjust and sign-off were not established on the pages reviewed. What it is Matching and period close for one entity, inside the plan you have Best for Firms whose close is a monthly routine on a single entity. Choose when The close is routine and the entity count is one. Skip if Multi-entity consolidation is not part of the standard online plans, so a second entity changes the product, not the plan. Billing driver Plan tier and users. Price detail Simple Start $38 through Advanced $340 per month, after the promotional period. Customisable user permissions and pre-defined roles are documented on the features page. Platform dependency Is the ledger Material risk Permissions and a closing date exist, but no second-person sign-off is documented on the pages reviewed, and the closing date can be configured to yield after a warning alone — so until the vendor shows otherwise, treat segregation of duties here as a convention you maintain, not a control you have verified. Bank and card transactions arrive automatically; receipt capture is in the mobile app. The features page itself does not say who confirms a categorisation; the bank-transactions help below does. QuickBooks Online accounting features page, reviewed 2026-09-12 Standing US monthly plans are Simple Start $38, Essentials $85, Plus $140 and Advanced $340. The rates shown first on the page are a 50%-off-for-three-months promotion, not the renewal price. QuickBooks Online pricing, reviewed 2026-09-12 QuickBooks automatically suggests matches for downloaded transactions with the same amount within a date range, and suggests the most likely match or category from your history. Downloaded transactions "won’t affect your books until you match or categorize them": a person reviews the transaction and selects Post. QuickBooks Online help, "Match your bank and credit card transactions" and "How AI suggestions help match and categorize bank transactions", reviewed 2026-09-13 New downloaded bank transactions must be matched manually, except that QuickBooks matches transactions from QuickBooks Payroll, Bill Pay and Payments automatically. Automatic matching is turned on or off from the bank transactions settings; the article does not say whether it starts on, and notes it may not be available in all accounts yet. QuickBooks Online help on automatic matching for QuickBooks product transactions, reviewed 2026-09-13 An admin turns on "Close the books" and enters a closing date; afterwards, changes on or before that date are allowed only after a warning, or after a warning and a password, depending on the setting chosen. The article does not mention a reviewer, a preparer, a second person or a sign-off. QuickBooks Online help, "Lock your books in QuickBooks Online", reviewed 2026-09-13
Specialist layers
FloQastClose-control layerLedger link not verifiedClose control on top of the ERP you keep	PullAutomatic MatchAutomatic Human checkpoint hereAdjustHuman Sign offHuman LockNot verified Human checkpoint at Adjust	Choose whenYou can name the reviewer, and must prove the review. Skip ifMatching is fine and nobody is waiting on a reviewer.	Quoted. The vendor’s pricing page requests a demo rather than listing a plan.
Why this reading · 2 first-party sources Checkpoint A person is documented at Adjust on every route. The steps after it keep reading on their own states. Authority The clearest authority statement of any product on this page, in the vendor’s own words: "Nothing hits your books without human approval. No exceptions." Entries are drafted continuously and you review and approve them. What it is Close control on top of the ERP you keep Best for Teams that need the review layer — drafted entries, a documented approval and a close that someone other than the preparer accepts. Choose when You can name the reviewer, and the close needs to prove they reviewed it. Skip if It is a control layer, not a ledger. If the matching is already fine and nobody is waiting on a reviewer, it solves a problem you do not have. Billing driver Team size and the modules in scope, agreed at contract. Platform dependency Connects to Workday, NetSuite, SAP, Oracle, Sage Intacct, Xero and QuickBooks. Whether it writes journal entries back, or only drafts them for you to post, was not established. Material risk Buying a review layer before you have a reviewer buys the artefacts of control without the control. "Nothing hits your books without human approval. No exceptions."; "You review, you approve."; "Journal entries drafted — continuously, not just at month-end."; Automated Reconciliations and AI Transaction Matching listed as products; connects to Workday, NetSuite, SAP, Oracle, Sage Intacct, Xero and QuickBooks. FloQast product site, reviewed 2026-09-12 The pricing page carries no plan amount and routes to a demo. FloQast pricing page, reviewed 2026-09-12
RilletAI-native ledgerReplaces the ledgerReplace the ledger rather than add a control layer to it	PullAutomatic MatchAutomatic AdjustRule-bound Sign offNot verified LockNot verified No human checkpoint documented — Sign off and Lock not verified either way	Choose whenYou are replacing the ERP anyway, for a continuous close. Skip ifYou are not a $5M–$200M+ ARR SaaS company.	Quoted. The vendor publishes enterprise pricing by demo request.
Why this reading · 1 first-party source Checkpoint No documented human checkpoint in this path. Sign off and Lock are not verified, so this does not mean the product runs unattended. That is the question to put to the vendor in writing. Authority Entries are automated from contracts under ASC 606 rules and traceable to their source, which is rule-bound rather than automatic. Whether a person reviews or approves an entry before it posts is not stated, and in a product that is itself the ledger, that is the first question to ask. What it is Replace the ledger rather than add a control layer to it Best for Scaling SaaS finance teams already outgrowing QuickBooks or evaluating a NetSuite alternative, who are replacing the system of record anyway. Choose when You are replacing the ERP regardless, and a continuous close is why. Skip if The vendor targets Series A to pre-IPO SaaS companies at $5M–$200M+ ARR. Outside that, this is not a close purchase, it is a migration you did not ask for. Billing driver Contract scope, plus a CPA-led implementation the vendor sizes in weeks. Price detail CPA-led implementation is stated as 45 days, against 6–18 months the vendor attributes to traditional ERPs. Implementation is part of the number. Platform dependency The vendor positions Rillet as an AI-native ERP replacing NetSuite or QuickBooks, implemented in 45 days. This is not a layer on your close; it is a different system of record. Material risk Switching the system of record costs a migration and a year of comparatives. No layer decision on this page is reversible in the way this one is not. "Rillet’s AI-native ERP, replacing NetSuite or QuickBooks for scaling SaaS companies in 45 days"; "Run a continuous close with every entry traceable to the source"; "Apply ASC 606 automatically, directly from your contracts"; buyer fit stated as "Series A through pre-IPO SaaS companies with $5M–$200M+ ARR"; "Enterprise pricing — request a demo for a custom quote". Rillet product site, reviewed 2026-09-12

The testA close is governed when someone other than the preparer signs it off and the period can be locked afterwards. If a product cannot show you those two things, it is speeding up matching — which may be all you need, but it is not a control.

Sources for this decision · Reviewed Sep 18, 2026

Pull, matching, adjustment and sign-off behaviour read from each vendor’s own site on 2026-09-12. QuickBooks Online’s matching, automatic matching and period lock, and Xero’s JAX reconciliation, manual and repeating journals and lock dates, were read from their own help centres and product pages on 2026-09-13. Where a ledger documents both a person and a route without one at a step, the cell shows the route without one and the row names its conditions. Sign-off is recorded as verified only where a vendor documents a person accepting the work; neither ledger’s reviewed pages do, and this page will not infer a reviewer role from a plan comparison.

AI Accounting Software AI Data Analysis

Put it together

Four stacks worth considering — and when not to build them

Editorial buying patterns built only from the rows above. Each says what it leaves unsolved.

Native-first practice

One entity, one reviewer, clean feeds.

The stack: QuickBooks Online or Xero, and nothing else
It solves: Capture, coding, matching, bill pay and a period lock you already pay for.
It leaves open: A second-person sign-off neither ledger was shown to enforce, and approval before payment below Bill Pay Elite.
Don’t build it when: Client documents arrive on paper or by email, or approvals have to follow rules.

Document-heavy bookkeeping practice

Many clients, messy paper and emailed documents.

The stack: Your ledger plus Dext or Sage AutoEntry
It solves: Collecting, extracting and coding client documents before anything reaches the ledger.
It leaves open: Approval, payment and close review. Settle posting control too: AutoEntry can auto-publish supplier by supplier, and Dext’s was not verified.
Don’t build it when: The feed is clean and documents are the exception.

AP-control finance team

Many vendors, and approvals that follow rules.

The stack: Your ledger plus BILL or Ramp
It solves: Approver routing under policies you configure, and a payment rail with a trail behind it.
It leaves open: A guaranteed approval: BILL lets an administrator switch approvals off or pay an unapproved bill, and Ramp can approve by rule. Set the roles in writing.
Don’t build it when: One named approver is enough — on QuickBooks, Bill Pay Elite already sells that.

Governed close team

A named reviewer who must sign each close.

The stack: Your ledger or ERP plus FloQast
It solves: Drafted entries, a documented review and a sign-off — FloQast states nothing hits the books without human approval.
It leaves open: Matching you already have. A period lock on FloQast’s side was not verified.
Don’t build it when: You cannot name the reviewer today.

Before you connect it to a client file

Nine things to settle with the vendor in writing

Software procurement guidance, not legal or accounting advice, and no substitute for your own professional obligations.

Who can act4

Client and entity separation
Whether one client’s data can be reached from another client’s workspace, and how a staff member is scoped to one entity.
A firm holds books for businesses that compete with each other. Separation is the difference between a tool and an incident.
Role permissions
Whether preparer, reviewer, approver and payer are separate permissions that one person cannot hold at once.
Segregation of duties only exists if the software can enforce it. A single admin role quietly removes it.
Posting authority
Who or what can write to the ledger, whether posting can be held behind review, and whether that setting can be turned off.
This decides whether the product assists your books or writes them.
Payment authority
What can move money without a person, under which threshold, to which vendors, and who can change that list.
Payment authority is the only permission on this page whose failure mode is money leaving the account.

Where money and data can leak3

Vendor bank detail changes
How a change of vendor bank details is verified, who may approve it, and whether the change is logged.
It is the single most exploited step in accounts payable, and automation makes it faster in both directions.
Confidential financial data
Where the data is stored and processed, who at the vendor can read it, and what the sub-processor list looks like.
Client financial and identity data carries obligations that do not transfer to a vendor with the upload.
Model training
Whether client documents and transactions are used to train shared models, and whether that can be switched off for every client at once.
A default that is acceptable for your own books may not be acceptable for a client’s.

What survives the contract2

Retention and exit
How long documents are kept, what deletion actually removes, and what you can export on the day you leave.
Source documents are the evidence behind the numbers. A product that cannot hand them back has your working papers.
Audit evidence
Whether the trail keeps the original document, every coding change, the approver and the timestamp — and whether it exports.
A generated answer with no record of how it was produced is not evidence, however accurate it turns out to be.

Sources · Reviewed Sep 18, 2026

A procurement checklist written by ToolWorthy for this page, not a compliance framework and not a statement about any specific product. Answers have to come from the vendor in writing; nothing here has been tested by ToolWorthy against a live account.

Test before you buy

Six tests to run on your own books

A demo runs on the vendor’s cleanest month. Every test below puts one step of a control path under load, on your own books, before anything is connected to a client file.

Read
Messy intake
Use the worst documents you actually receive, not the ones a demo was built around.
Load it with · 5 cases
- A photographed receipt taken at an angle, in bad light, partly creased
- A multi-page supplier statement, and a bank statement page
- A foreign-currency invoice, and one in a second language
- A duplicate of a document already in the system
- The same document submitted twice by two different routes
Pass or failDid anything arrive silently wrong, and would you have noticed without opening the source document?
Code
Ambiguous coding
Pick the transactions your own staff argue about, not the ones with an obvious account.
Load it with · 4 cases
- A supplier you buy two different categories of thing from
- A payment that is part expense and part capital
- A transaction whose correct treatment depends on a contract the software cannot see
- A brand-new supplier with no history to learn from
Pass or failWhen it is unsure, does it say so and stop — or does it pick, and how would you find out that it picked?
Match
AP duplicate and mismatch
This is the test that costs money if it fails, so run it before any approval workflow is configured.
Load it with · 5 cases
- The same invoice submitted twice, once as a PDF and once as a photograph
- An invoice whose quantity does not match the receipt
- An invoice whose total does not match the purchase order
- A credit note against an invoice already paid
- An invoice from a supplier whose bank details differ from the one on file
Pass or failWas every mismatch surfaced as an exception a person has to clear, or did any of them pass through?
ApprovePay
Approval boundary
Test the authority you actually intend to grant. Do not enable payment release to complete a checklist.
Load it with · 5 cases
- Whether approval and payment can be held by two different people, and whether the software enforces it
- What happens at, just under, and just over an amount threshold
- Whether an administrator can approve their own item, and whether that is logged
- Who may add a vendor, and who may change a vendor’s bank details
- Whether a granted permission can be narrowed or revoked afterwards
Pass or failCan one person, acting alone, get a payment out? If the answer is yes, the control is a convention rather than a control.
MatchAdjust
Reconciliation mismatch
Reconcile a month you already closed, so you know what the right answer looks like before the software tells you.
Load it with · 5 cases
- A transaction that appears in the feed twice
- A payment that cleared in a different period from the invoice
- A partial payment against a larger invoice
- A balance the software cannot reconcile at all
- Whether an adjusting entry is drafted for review or simply made
Pass or failFor everything it could not match, did it hand you the exception — or did it close the difference for you?
PostAdjust
Correction and audit history
Break something on purpose, fix it, then try to reconstruct what happened from the record alone.
Load it with · 4 cases
- Whether the original document survives a correction
- Whether the previous coding, the person and the timestamp are all retained
- Whether a deleted or voided item is still traceable
- Whether the trail exports in a form an auditor can read without the vendor
Pass or failCould someone who was not there reconstruct the change from the record? If not, the trail is a log rather than evidence.

Two things to check while the trial is still connected

Revoke the integration and watch what happens: whether the connection can be narrowed rather than only removed, whether anything already written to the ledger is left behind, and whether data held at the vendor is deleted or merely disconnected. Then run the export you would need on the day you leave, with a real client file rather than a sample, and confirm the source documents come with it. Both answers are far cheaper to obtain during a trial than during a migration.

An editorial buying framework, not a claim about what any vendor’s trial includes. No accuracy percentage, time saving or ROI figure appears here, because none is evidenced — the output of each test is a yes or a no you observed yourself.

Where this page stops

Real software markets, none of them decided by where a person takes over a control path. What each is actually decided on is more useful than a shortlist we cannot stand behind.

PayrollJurisdiction coverage, who carries filing responsibility, and who is liable for a late or wrong filing.
Tax preparation and filingForm coverage, e-file authorisation and who signs the return. Regulatory questions, not procurement ones.
Managed bookkeeping engagementsScope, staffing and exit terms. You are buying capacity from people, so the authority question is answered by a contract rather than by a product.
Enterprise record-to-report programmesA multi-year controls transformation with implementation partners attached. A different purchase, a different budget line, and a different decision-maker.
Global payouts and contractor tax formsCountry coverage, worker classification and withholding. It looks like AP and is not: the risk is employment and tax status, not approval authority.
Professional judgementMateriality, going concern, revenue recognition and any position taken on a return remain the work of a licensed professional. Nothing on this page changes who is answerable.

Still open

Can AI post journal entries on its own?

Some products do, inside rules you set — which is why this page separates automatic from rule-bound. A threshold, a vendor list or a contract-driven revenue rule is a very different arrangement from a model deciding unaided. For several products here, posting authority is not documented publicly and the page records that rather than guessing. Before enabling automatic posting on a client file, establish whether it can be held behind review and how a wrong entry gets corrected.

Is approval authority the same as payment authority?

No, and conflating them is the most expensive mistake in this category. Approval clears a bill as correct and owed; payment releases the money. A product can document a strong approver chain and still let one administrator hold both permissions. Ask for them as separate roles in writing, with an amount threshold and a controlled vendor list, and ask specifically how a change of vendor bank details is verified.

Why does a product show "Not verified" when its site clearly describes the feature?

Because describing a capability is not the same as documenting who holds the permission. "Autonomous processing" tells you the software can act; it does not tell you whether a person must approve first. Where a first-party source did not separate the two, this page says so at the same weight as every other state. It is a fact about the evidence available to a buyer, and a reasonable thing to put to the vendor.

Should a small practice buy anything on this page?

Often not, and each decision says where its own "no" lives. If your feed is clean, intake needs nothing. If you cannot name the second person who signs off the close, a close-control layer buys the artefacts of control without the control. The one that most often does pay is intake, and only because client document collection is the step you do not control.

How this page decides

This is a buying guide, not a directory listing. Products are here because an editor put them here for the job, and they stay whether or not ToolWorthy happens to hold a record for them.

Selection and evidence

Products are here because an editor put them here for one of the three decisions, and they keep their place whether or not ToolWorthy holds a record for them.
Product facts come from first-party sources. A third-party review can point at a source; it cannot establish an authority or approval claim.
Documented capability and documented permission are recorded separately. "Supports approvals" does not establish that every write is human-approved.
Where a product documents a manual route and an automatic or rule-bound route through the same step, the cell records the furthest the software goes without a person, and the row names the plan, setting or rule it depends on. A checkpoint that a documented setting can route around is not drawn as a checkpoint.
A human step that a documented setting, plan or role can skip altogether keeps its state and is marked Can be skipped. Skipping an approval is not automating it, so it is never recorded as automatic, and never drawn as a human checkpoint.
A payment-workflow feature is never converted into a claim that software independently moves funds.
Where no first-party source established a step, it reads Not verified at the same visual weight as every other state. That describes the evidence, not the product.
Prices are the standing rate, checked at review. Promotional and first-period rates are named as such, and quote-based pricing stays quote-based.
Tier gates, implementation requirements, integration limits and country-specific packaging are treated as material comparison facts, not footnotes.
A vendor or customer statement is a source to check, never a substitute for checking.

Last reviewed Sep 18, 2026. Pricing and features change; the linked tool and category pages are the maintained record.

Keep going

Category directories are the maintained inventory for a capability, and the ranked guide is where accounting products are scored against each other. This page only decides where a product sits in your stack and how far it may act.

AI Accounting Software AI Bookkeeping Software Best AI accounting software, ranked

Start from what is actually hurting

What QuickBooks Online and Xero already cover

Do you need a preparation layer beyond the ledger you already run?

Checkpoint

Authority

Checkpoint

Authority

Plan and setting

Checkpoint

Authority

Checkpoint

Authority

Checkpoint

Authority

How far should software go from reading an invoice to moving the money?

Checkpoint

Authority

Plan and setting

Checkpoint

Authority

Checkpoint

Authority

Plan and setting

Checkpoint

Authority

Do you need faster matching, or a governed close?

Checkpoint

Authority

Plan and setting

Checkpoint

Authority

Checkpoint

Authority

Checkpoint

Authority

Four stacks worth considering — and when not to build them

Native-first practice

Document-heavy bookkeeping practice

AP-control finance team

Governed close team

Nine things to settle with the vendor in writing

Who can act4

Where money and data can leak3

What survives the contract2

Six tests to run on your own books

Messy intake

Ambiguous coding

AP duplicate and mismatch

Approval boundary

Reconciliation mismatch

Correction and audit history

Two things to check while the trial is still connected

Where this page stops

Still open

How this page decides

Keep going