Home About Shannon Services Industries San Diego Blog Tools & Resources Contact Book Now

Three things happened in six weeks. A payroll provider began pulling tax debits on its own schedule. An accounting platform started attaching uploaded receipts to transactions without anyone choosing the match. And a spend-management company launched a product that reads a contract, builds a revenue recognition schedule from it, and syncs that schedule into the accounting file.

None of these is a scandal. All three are sold as time savings, and in most cases that's exactly what they are. But together they describe something worth naming. Your books now contain entries that no person in your business authored.

The Difference Between Automation You Chose and Automation That Arrived

You can audit a rule you wrote. If a bank rule miscategorizes a vendor, you know what you intended, so you can see where the rule went wrong and fix it. The same is true of a chart of accounts you built or an automation you deliberately turned on. Your intent is the reference point.

The newer category works differently. The feature ships already switched on, or a tool someone else in the business bought starts writing into the accounting file, and the reasoning behind each entry lives in a vendor's system rather than in a decision anyone made. When you ask why a number is what it is, the honest answer becomes "the software decided," and that is not an answer you can give a lender, a CPA, or an auditor.

The test: For any entry in your books, can someone in your business explain why it's there? If the only available answer points at a vendor's model, that entry is unexplained, however correct it turns out to be.

Three Examples of Software-Originated Entries

Revenue Schedules Built From Contract Language

In September 2026, Ramp launched an accounts receivable product that, in its own words, "turns contract terms into revenue recognition schedules and keeps everything synced with the business's ERP," with QuickBooks Online and NetSuite supported at launch for US-based, single-entity businesses.

Revenue recognition is a judgment call about when you've earned money. If that judgment is produced from contract language by software and pushed into your file, deferred revenue starts moving on a basis nobody in your business can walk through. The product also matches incoming payments to open invoices automatically, which is the quieter risk. A payment applied to the wrong open invoice nets to the same cash, leaves two customer balances wrong, and surfaces months later as a dispute rather than as a reconciliation break.

Worth being fair about the collections piece, because secondary coverage overstated it. Ramp's own language is that the system drafts a message "for review," not that it sends one. Your customers are not about to start receiving automated dunning emails.

Documents Attaching Themselves to Transactions

Xero's September release renamed Files to Documents and added auto-matching, which in Xero's wording "attaches your uploaded documents to an already existing transaction," with a toggle you can switch on or off at any time. Where the match is right, that saves real time. Where it's wrong, the support sitting behind a reconciled transaction is the wrong support, and nobody discovers it until year-end or an audit. Xero's post doesn't say whether the setting defaults to on, which is the whole reason to go look rather than assume.

Debits Pulled on the Platform's Schedule

Payroll and accounting platforms increasingly pull tax payments automatically rather than when you approve them. The money is genuinely owed, so nothing is wrong in substance. What changes is that the timing is no longer yours, and a cash forecast built on the old timing quietly stops matching the bank.

Why This Belongs in Your Books and Not Just in IT

The practical damage isn't dramatic. It's that your books stop being a record of decisions and start being a record of outcomes.

That matters at three specific moments. When a lender asks about a line, the answer has to be explainable, not merely accurate. When your CPA reviews deferred revenue or prepaid balances at year-end, "the integration produced it" costs billable hours that a short explanation wouldn't have. And when something genuinely goes wrong, you can't tell the difference between an error and a feature if you were never sure what the software was doing in the first place.

There's a quieter cost too. Owners stop asking why a number moved, because the answer stopped being available. That habit is harder to rebuild than any individual setting is to change.

What to Do About It

This isn't an argument for turning everything off. Most of these features are worth having. It's an argument for knowing which ones are running.

Open the settings in your accounting platform and your payroll system and read what's enabled, specifically anything that creates, matches, or schedules something on its own. Where a feature is on, decide deliberately whether you want it on rather than inheriting the default.

Ask who else can write to your accounting file. A tool bought by someone outside the finance function can sync entries into the books, and that often surfaces as an unexplained balance long before anyone connects it to the purchase. This is the same reason an audit of the software line on your P&L is worth doing once a year.

Where software generates a schedule, keep the source. If a revenue recognition schedule is produced from a contract, the contract and the schedule belong together in a place your CPA can find them in January.

And add one line to your month-end routine. Ask whether anything posted this month that nobody here can explain. Our free Bookkeeping Health Score is a reasonable starting point if you're not sure how exposed you are.

The Bottom Line

Software that writes entries into your books isn't new, but software that decides what those entries should be is. The risk isn't that the machine is wrong more often than a person. It's that when it is wrong, nothing in your process catches it, because nobody expected to be checking.

At Salt & Sand Bookkeeping, part of keeping books clean is knowing which entries a person wrote and which ones the software wrote. We record what happened, and we keep your books explainable.

See how we approach clean, reviewed books: Our Bookkeeping Services

Questions about your books? Reach us at info@saltandsandbookkeeping.com or (619) 304-SALT (7258).

Not sure what your software is doing on its own? Let's take a look together.

Schedule a Free Consultation
← Back to all posts