Your crew shoots receipts on their phones from the supplier's yard. Tally reads each one, codes it from what you did last time, splits it across jobs, and posts it into QuickBooks Desktop as a bill, card charge, check, or debit — with you approving every one before anything is written.
14 days free. No card to start. Nothing posts to your books without you pressing the button.
One tap on the phone, in the truck or the yard. No app store, no login for the crew to forget.
Vendor, date, total, tax and invoice number come back filled in — matched to the vendors already in your books.
Assign it across jobs and classes. The lines have to add up to the receipt before it can go anywhere.
QuickBooks is asked first, you see what it said, then the transactions are written.
Most receipt tools were designed for an office with one expense account. This one was designed for a load of materials that goes to three jobs.
Creased, angled, half in shadow, thermal paper going faint. It reads vendor, date, subtotal, tax, total and invoice number, and tells you plainly when it could not read something rather than inventing a number.
It reads the tender line at the bottom of the receipt. VISA ****4021 becomes a credit card charge; DEBIT becomes a check against the bank account; an invoice with terms becomes a bill.
That one line decides which of the four QuickBooks transaction types gets written, so nobody has to remember.
One receipt, as many lines as you need — each with its own account, class, customer:job and memo, marked billable or not.
A running tally shows what is still unassigned, and nothing can be approved until the lines balance to the receipt. QuickBooks would happily take a mismatched entry; finding that in March is a bad afternoon.
The second SiteOne receipt arrives already coded to the account and class you used on the first. And it tells you why: "you coded the last 6 SiteOne receipts this way."
Job assignment is never guessed. Which job the mulch went to is a fact about that day, not about the vendor.
Vendors, expense accounts, bank and card accounts, classes and customer:jobs are pulled straight out of your company file, so every picker only ever offers names QuickBooks already knows.
Press send and Tally asks QuickBooks whether it would accept the batch — without writing anything. You read the answer, then decide.
A job closed last week still looks fine in any cached list. Catching that before the write beats unpicking a half-posted batch after it.
QuickBooks Desktop has no internet API. It only talks to a program running on the same Windows machine. That is why most receipt apps quietly support QuickBooks Online only, and why the ones that claim Desktop support usually mean a CSV file you import by hand.
Tally ships a small companion program for the PC that already runs QuickBooks. It checks in with us every few seconds and does the writing locally.
Nothing connects in to that machine. No open port, no firewall exception, no VPN, no static IP. Your IT person does not need to be involved, because there is nothing for them to open.
Setup is one code, typed once, on one PC.
Everyone in the company included. No per-user fees, no contract.
per company · or $490 a year, two months free · cancel any time
No card to start. Go past 300 in a month and receipts still come in and still post — they just need filling in by hand until the 1st. If you stop paying, you keep reading and exporting everything you have already put in.
The things you would otherwise find out in week three.
No — and nothing can. The QuickBooks Desktop SDK has no way to write to its Doc Center. Tally keeps every image and links it to the transaction it created, so you can always pull up the photo behind an entry. But the attachment does not live inside QuickBooks itself. Anyone telling you otherwise is showing you QuickBooks Online.
Usually yes, and the PC has to be on. If you authorise the bridge for unattended access — a checkbox in the QuickBooks permission dialog — it can work with QuickBooks closed.
Those go to a person, deliberately. A scrawled project code read wrong is a cost on the wrong job, which is worse than typing it. The reading saves you the vendor, date and total; the job split is the part worth a human.
That receipt stays put and tells you what QuickBooks said, in its own words. The rest of the batch still goes in. Nothing is ever marked as posted unless QuickBooks confirmed the write.
They need a login, but not much else — the phone side is one button. Only owners and admins can approve receipts or send anything to QuickBooks.
Handled as any other receipt for reading and splitting, but cash has no clean equivalent in this flow, so it comes to you to decide how to record it.
You keep your account, your receipts and your images, and you can still read and export all of it. What stops is adding new receipts and posting to QuickBooks. Nobody should have to pay a ransom to look at their own paperwork, and some of it you are required to keep.
Set up a company, connect the office PC, and put the first receipt through in an afternoon.