Automation for the work that repeats

What this actually is

Not a product, and not a platform you log into. It is custom work built against a specific business's chart of accounts, vendors, and workflow — because that is the part generic software cannot do. Off-the-shelf tools make you reshape your process to fit them. Building on top of your own system means the process stays as it is and the repetitive parts of it stop needing a person.

It sits on top of an existing bookkeeping relationship. Someone has to know what the books are supposed to look like before it is worth automating anything that touches them, which is why this is offered to clients rather than as a standalone service.

What can be built

• Document intake. Invoices, receipts, and statements pulled from email or a shared drive, read, and filed against the transaction they belong to — instead of a monthly hunt through an inbox.
• Recurring coding. Vendors and transaction patterns that always code the same way, applied consistently, with anything unfamiliar held back for a person to look at.
• Exception flagging. Transactions that do not match any expected pattern surfaced early — a duplicate payment, a charge that doubled, a vendor that has never appeared before.
• Cross-system reconciliation. One system's records checked against another's on a schedule: a payroll provider's reports against the ledger, a back-office system against the accounting file, a rent roll against deposits.
• Reporting. The same monthly package assembled from the same accounts every time, delivered on a fixed date rather than when someone gets to it.
• Internal tools. Small applications for the things a business does constantly and awkwardly — a form that produces a correctly coded entry, a lookup that answers a question staff currently ask the bookkeeper.

What does not get automated

This matters more than the list above, because the failure mode of automation is not being wrong occasionally — it is being confidently wrong at scale, in a system of record, without anyone noticing for months.

• Judgment calls. Whether an ambiguous expense belongs in one account or another, whether a cost is a repair or a capital improvement, how an unusual transaction should be treated.
• Anything carrying professional responsibility. Trust and escrow reconciliations get signed off by a person. So does the monthly close.
• Anything a regulator or a CPA will rely on without a person having checked it first.

Every automation is built so a person reviews what it did before it becomes the record. The books stay the bookkeeper's responsibility, not the software's — automation changes how long the work takes, not who is answerable for it.

How QuickBooks integration works

QuickBooks Online publishes an API that lets an authorized application read and write transactions, bills, invoices, vendors, and reports. Access is granted by the account owner, scoped to what the tool actually needs, and can be revoked at any time from inside QuickBooks. Nothing is installed on your machines and no passwords are shared — the connection is authorized the same way any approved QuickBooks app is.

Where a business runs something other than QuickBooks — a brokerage back-office platform, a point of sale, a club or property management system — what is possible depends on what that system exposes. That is the first thing to establish, and it is a short conversation.

How an engagement runs

1. Start from a bottleneck, not a technology. Something specific that takes hours every month and shouldn't.
2. Scope and fixed price. Quoted and contracted by Signal Solutions as its own project, separate from the monthly bookkeeping retainer, so it is a decision you make once rather than an open meter.
3. Built, then run alongside the manual process until it demonstrably agrees with it.
4. Handover. You own what is built and it keeps working if the engagement ends. No hostage software.

Where your data goes

Nowhere it doesn't already live. This is the part most worth being specific about, so:

• Client financial data is not sent to any third-party AI service. Automation runs against the systems you already control — your accounting file, your storage, your accounts.
• Nothing is used to train any model. Not ours, not anyone's.
• Access is scoped and revocable. A connection is authorized by you, limited to what the tool actually needs, and can be switched off from inside your own software without anyone's help.
• No new copies of your books. Automation reads and writes where the records already are rather than creating a second system holding your financials.
• Anything unusual is agreed in writing first. If a specific project ever needed a different arrangement, it would be described and agreed before it was built — never discovered afterwards.

These are commitments about other people's money, so they are stated plainly rather than buried. A law firm's trust ledger or a brokerage's escrow account is not somewhere to find out later.

Who builds it

This work is led by Tom Bastianelli, Vice President of KMB Financial, and is built and contracted through Signal Solutions — the IT and telecommunications firm he founded in 2016, which has spent a decade on managed IT, cybersecurity, network and telecom work for Rhode Island businesses, law firms and accounting practices among them.

That matters more than it might sound. A decade of keeping other people's systems running and secure is not a background that encourages plugging a system of record into something experimental. It is a background that asks what happens when it fails, who can switch it off, and where the data actually sits — which is why those questions are answered above rather than left to the fine print.

The engagement is deliberately separate from your bookkeeping: its own scope, its own price, its own agreement with Signal Solutions. Responsibility for the books does not move — Korissa remains the person who signs off on what becomes the record. Automation changes how long the work takes, not who is answerable for it. More about both of us.