DRAFT FOR REVIEW. NOT PUBLISHED. Pink dashed boxes are placeholders for open decisions. Art is illustrative and screens are examples.
Penny
A white-label bookkeeping agent for CPA firms

A bookkeeping assistant for every client, under your name.

It preps the books weekly in QuickBooks. When bank feeds launch, it checks them against the bank. Your client approves. You review at month-end. It never moves money.

It prepares. You approve. It never moves money.

Book a 20-minute call See how it works
Read-only QuickBooks Client approves every payment You review at month-end
Custom illustration, not a client: two colleagues at a desk in a CPA firm reviewing a multi-client screen. Some clients show a green check, some show hold.
Illustration · not a client
The weekly loop

Same loop, every client. Every week.

You already do this for the small businesses you serve. Each one has its own invoices, its own vendors, its own bank. The work repeats, and it lands on your people.

  1. Invoices arrive by email, by photo, by text.
  2. Someone codes each one.
  3. Someone checks the bank against the books.
  4. Someone builds the pay list, then reconciles.
Custom illustration, not a client: a small-shop owner at the counter with a tablet while invoices arrive by phone photo, email, and paper.
Illustration · not a client
Where it is used

Real small-business settings. A short list, a yes.

Your clients run shops, crews, and job sites. The assistant meets them where they are: on a phone, at the office, on site.

Illustrative stock photo, not a client: five colleagues gathered around a laptop in a bright office, reviewing something together.
Illustrative photo · not a client
Illustrative stock photo, not a client: a contractor in a safety vest crouching at a work site, holding a smartphone.
Illustrative photo · not a client
Illustrative stock photo, not a client: a site manager in a hard hat and safety vest looking at a tablet on a construction site.
Illustrative photo · not a client
How it works

It gets it ready. Your client says yes. You review.

Three steps. The amber step is a person. Nothing goes past it without a yes.

STEP 1

It gets it ready.

Reads each invoice, codes it, and flags what is missing.

match · code · flag
STEP 2 · A PERSON

Your client says yes.

A short list in their HQ: approve, fix, or hold. Only the client approves bills and payments.

approve · fix · hold
STEP 3

You review.

Your dashboard will show every client: holds, overdue, uncoded. You review at month-end.

Firm dashboard: Planned
Flow diagram of one invoice. Steps 1 to 4, done by the agent: the invoice arrives, is read, is coded, and is checked for completeness. If something is missing it goes on hold and the agent says why. If complete it is saved in a to-be-paid list. Step 6 is amber: the client approves, only the client can. After the yes, the client pays by check or digital, the agent notes it as paid as a draft, and the client sends the packet to the firm.
What connects

Five connections. Honest about each status.

We label what is in pilot, what is planned, and what is still being designed. No live claims we can't back.

Pilot

QuickBooks Online

Reads bills, invoices, and the books. Read-only to start.

Planned

Bank and card feeds (Plaid)

Connect the client's bank and cards so the agent can check what cleared. On the roadmap, not live.

Planned

Payments received (Stripe)

A read-only view of payouts and invoices the client was paid. On the roadmap, not live.

Pilot

Client HQ

A simple approve screen for each client, in your firm's colors.

In design

Invoice inbox

Bills and receipts by email or photo land in one place per client.

One thinking system Bank and payment feeds: Roadmap

Bank, payments, and books look through one brain.

Plaid and Stripe are only windows: read-only, and both on the roadmap. The decision engine is the single decision-maker looking through all of them. A person says yes. Then, and only then, a draft is prepared. Everything is logged.

SYSTEM 1 · THINKS

The decision engine

Answers fixed, typed questions about each item (what is this, does it match, should a person look) with a confidence and a reason. It cannot act, and it can still be wrong, so a person approves.

SYSTEM 2 · DOES THE WORK

The agent team

Language-model agents that do the multi-step work: fetch, read, file, and draft. They ask the decision engine and never decide alone. Everything they prepare waits for a yes.

AP · MONEY OUT

Approved on Friday, cleared on Monday, or not.

AR · MONEY IN

A deposit lands. The assistant suggests which invoice it belongs to. A person confirms.

BOOKKEEPING

Bank lines with no category get a suggested one, with a reason.

Interactive example · sample data · four views: the system, the Agentic OS around it, one transaction step by step, and honest status of every part. Open full screen

Interactive example · sample data · Plaid, Stripe, and the firm-wide flow are ROADMAP (planned). The decision step has been tried on sample support tickets, not on bookkeeping. RUNNING = running today, internally or for one pilot client · TESTED = sample or sandbox data only · ROADMAP = planned, not built.

NEVER, by anything in this system: move money, pay, transfer, charge, refund, or print checks. Plaid Auth and Transfer are out of scope.

Two Plaid products only, both planned: Transactions (what cleared) and Balance (cash on hand). Auth and Transfer, the parts that set up or move payments, are out of scope by design. Stripe is a read-only view of payments received, also planned. Bank coverage is checked per client, per bank, when bank feeds launch.

Custom illustration, not a client: a contractor in a hard hat on a job site holding a phone that shows a short list to approve.
Illustration · not a client
What your client sees

Your name and colors. A short list. Their yes.

Each client gets their own HQ with their own data. It shows only what needs a yes. Everything else is a one-line count.

See it in your firm's colors
[YOUR FIRM NAME] BooksFriday list · example

3 things need your yes

12 more are ready and need nothing from you.

Sample Lumber Co.
Coded to Materials · due Friday
$1,000 sample
ApproveFixHold
Sample Electric LLC
On hold: no W-9 on file
$500 sample
Ask for W-9Keep on hold
Sample Supply House
Looks like a repeat of an earlier bill
$250 sample
Not a repeatHold
Bookkeeping assistant by [Your firm], powered by PennyExample screen · sample data

Example screen · sample data · themes are illustrative and use no real firm's logo. Whether "powered by" shows is the firm's choice on a paid tier: [PLACEHOLDER: TBD]

Weekly reports

Reports your client actually reads.

Six short pieces. The rule: only what needs a yes; everything else is a one-line count.

Weekly report

Example, not client data. Payees and amounts are sample.

  • Bills to pay this FridayOnly the ones that need a yes3 need a yes
    9 ready
  • Needs codingThe agent suggests, with a reason2 items
  • Money owed to youOverdue and due soon1 overdue
    2 due soon
  • Cash after this week's paymentsNeeds bank feedsPlanned
  • What QuickBooks shows vs what was approvedGaps flagged, nothing changed1 gap
  • Month-end packetDrafted for your reviewDraft

Firm view: all clients

Example screen · sample data · Planned

ClientHoldsOverdueUncoded
Sample Builder Co.213
Sample Café LLC001
Sample Salon Inc.120

You review the exceptions. Your client makes the calls.

Pilot offer for firms

Start with one or two of your clients.

We run it in shadow mode first: it prepares, and the client works as usual. Then assist mode. We measure time and accuracy together.

  1. 1

    Set up

    Connect QuickBooks read-only. Name the client's one approver. Collect the chart of accounts and payee list.

  2. 2

    Shadow

    The agent prepares every week. The client works as usual. We compare the two.

  3. 3

    Assist

    The client reviews the agent's list instead of building it. You review at month-end.

Pilot terms

Price
[PLACEHOLDER: CPA pricing TBD]
Firms · clients · weeks
[PLACEHOLDER: pilot terms to be agreed]
Contract
[PLACEHOLDER: TBD]
Custom illustration, not the pilot client: a builder at a desk with building plans and a tablet showing an approve screen.
Illustration · not the pilot client

We are running the first pilot with a custom home builder.

It is set up the same way as everything on this page: the owner says yes, a person reviews every new rule before it is trusted, and nothing goes out without a yes.

Results will be shared when measured.

Plain answers

Questions a partner asks.

Does it post to QuickBooks?

Not in the first version. It reads. Any write would be a separate, opt-in feature with an approval step.

Can it pay bills?

No. Payment stays with your client.

What if it is wrong?

Nothing goes out without a yes. Every correction teaches it, and a person reviews any rule before it is trusted.

Who sees client data?

Each client has their own HQ and their own data. You see your own clients. [PLACEHOLDER: legal terms TBD]

Is my brand on it?

Yes. Clients see your name and colors. "Powered by" is a choice. [PLACEHOLDER: decision pending]

What is the decision engine?

The one decision-maker inside the system. It answers fixed questions about each item and gives a confidence and a reason. It cannot act, and a person approves every proposal. It has been tried on sample support tickets, not yet on bookkeeping.

Which banks work?

It depends on the bank. We check per client when bank feeds launch. Bank feeds through Plaid are planned, not live.

What does it cost?

Pilot terms are being set. Ask us. [PLACEHOLDER: pricing TBD]

Is it live?

QuickBooks reading is in pilot. Bank feeds (Plaid), payment views (Stripe), and the firm-wide dashboard are planned.

Next step

Book a 20-minute call.

Bring one or two clients in mind. We will show you the approve list and talk through a pilot.

Book a 20-minute call [PLACEHOLDER: CTA destination TBD. Calendar link or mailbox from MT. Nothing on this page sends mail.] [CONTACT EMAIL TBD by MT]

It prepares. You approve. It never moves money.