1099-K & Gross Receipts Tie-Out

$39.00

For the person who currently opens three 1099-Ks, adds them up by month in a pivot table, and compares them to the general ledger by eye.

Local-firstNo telemetry — nothing phones homeNo lock-inNo migration

Give it the processors’ 1099-K figures and the booked gross receipts and it sums both by month.

It subtracts the fees and refunds, then flags every month whose variance is over a dollar.

$39 a month for the firm. Every client, every processor. Cancel any day.

The IRS has three numbers and your books have one

Stripe sent a 1099-K. So did Square. So did PayPal, for the eleven transactions the client took that way in 2023 and forgot about entirely.

The IRS now has a gross figure for the client that the client has never seen and does not agree with, because 1099-K gross is *gross*, before the processor’s fee came out, before the refunds, before the chargeback in October. The books show net. The forms show gross. And the difference is not an error, it’s arithmetic, but you have to be able to show the arithmetic.

If you can’t tie those out, the client gets a notice, and the notice arrives eighteen months later when nobody remembers anything.

It sums by month, then flags the gaps

  1. It parses the three files. FORMS_CSV (processor, month, gross amount), BOOKED_CSV (month, booked receipts), and optionally ADJUSTMENTS_CSV (month, type, amount). The parser handles quoted fields and embedded commas, so nothing shifts a column.
  2. It sums by month. The forms file can carry one row per processor per month, so Stripe, Square and PayPal all land in the same monthly total without you pre-aggregating anything.
  3. It computes the variance. For each month: 1099-K gross total, minus booked receipts, minus adjustments. Any month whose absolute variance clears TOLERANCE (default one dollar) gets flagged.

What comes out

  • VARIANCES.md: only the months that don’t tie, with likely causes listed next to them. This is the file that turns a three-hour investigation into a twenty-minute one, because it tells you *which month* to go looking in.
  • TIE_OUT.md: the full schedule with totals. Staple it to the workpapers and the tie-out is documented, which is the actual deliverable when a notice arrives.
  • tieout.csv and tieout.json for whatever comes next.
  • TOLERANCE is a dollar by default, and you’ll want that. A penny of rounding across twelve months of Stripe fees is not a variance worth anyone’s Tuesday.

Who needs this

A bookkeeping or tax firm with clients who take card payments. Restaurants, retail, ecommerce, any service business on Square. If a client of yours has ever said “that 1099-K number is wrong,” this is the tool that lets you say “no, it’s right, here’s why,” which is a much better sentence.

Not for you if your clients don’t take card payments, obviously. And not for you if you’re hoping it will *find* the reconciling items. It computes the variance and points at the month. Working out that the $4,180 gap in October was a chargeback plus a refund is still a human job.

What it replaces

A pivot table.

Excel is genuinely fine at this. Anyone competent can build the monthly sums and the variance column in twenty minutes, and Excel will let you slice it in ways this tool won’t.

What Excel won’t do is run itself the same way for the next eleven clients, or write the schedule out as a document you can attach to a workpaper, or remember what TOLERANCE you used last year. And the pivot table gets rebuilt from scratch every January, by someone slightly different, with a slightly different definition of what counts as an adjustment.

That inconsistency is the actual cost, and it’s invisible until an examiner asks how you tied it out.

Where the payment data sits

On your machine. Every CSV is read from disk, the schedule is written to disk, and nothing goes anywhere else. There’s no cloud in this product and no processor API to authorise, which means you’re never handing a vendor read access to a client’s Stripe account.

The schedule lands under OUTPUT_FOLDER at 0600, and every write path is checked with assertWithinRoot.

$39 a month, and about six minutes

Set FORMS_CSV, BOOKED_CSV and OUTPUT_FOLDER. Add ADJUSTMENTS_CSV if you have the fees and refunds broken out, and you should, because without it every month will show a variance equal to the processor’s fees and the report will be noise.

Run --validate first. It checks the config and reads nothing, which is the right way to point a new tool at a live client file.

Security and privacy

Handles client financial exports (1099-K processor gross amounts, booked gross receipts, fee/refund adjustments). Security is designed in.

Principles
Local-first. FORMS_CSV/BOOKED_CSV/ADJUSTMENTS_CSV are read from disk and never transmitted anywhere; nothing in this tool touches the network. Nothing is uploaded, no telemetry, no cloud dependency.
Non-destructive. Source CSVs are only read, never modified or deleted.
Least privilege. Reads FORMS_CSV/BOOKED_CSV/ADJUSTMENTS_CSV, writes only under OUTPUT_FOLDER.

Protections implemented (v0.1.0)
Path-traversal defense — every output filename is sanitized (safeSegment) and every write is checked with assertWithinRoot(), so the schedule can’t be written outside OUTPUT_FOLDER.
Fail-fast config validation — clear errors for missing/invalid FORMS_CSV/BOOKED_CSV/OUTPUT_FOLDER/TOLERANCE before any file is touched. --validate runs this check alone.
Restrictive permissions — the generated schedule (TIE_OUT.md, VARIANCES.md, tieout.csv, tieout.json) is written 0600.
Defensive parsing — the CSV parser and currency parser never throw on malformed input (missing fields default to empty string, unparseable amounts default to 0); a bad row degrades the tie-out rather than crashing it.
Secrets discipline.env and generated TieOuts/ output are git-ignored; no secrets or client data in the repo.

Distribution / AV trust

Known limitations / roadmap
– Monthly totals only in v0.1.0 — a processor misreporting one month and overreporting the next (net-zero across the year) will not be flagged if each individual month stays within TOLERANCE. Reviewers should also sanity-check the annual totals.
TOLERANCE is a flat $ amount, not a percentage — high-volume months may need a higher tolerance than low-volume ones; percentage-based tolerance is on the roadmap.
ADJUSTMENTS_CSV nets all adjustment types together by month; it does not currently break out fees vs. refunds vs. chargebacks in the schedule itself (the raw CSV retains the type column for manual review).

Reporting
Report suspected vulnerabilities privately to the maintainer before public disclosure.

Frequently asked questions about 1099-K & Gross Receipts Tie-Out

What does the 1099-K & gross receipts tie-out software do, and how does the tie-out work?

The 1099-K & gross receipts tie-out software solves one narrow problem and solves it well. It takes the total reported on a client’s Form 1099-K and the gross receipts booked in their accounting file, two numbers that almost never agree, and it explains the gap between them line by line. You import the 1099-K and a sales export, map the columns one time, and the tool returns a tie-out schedule with a month-by-month variance report. The firms that reach for it are the ones the catalog names plainly, firms whose clients get 1099-Ks that never match the books.

To see why the two figures diverge, it helps to know what the form reports. The IRS explains on its page, Understanding your Form 1099-K, that the form is a report of the payments a client received for goods or services through payment cards and third-party networks during the year. That gross figure includes amounts later refunded, processor fees taken before the deposit, sales tax collected, and sometimes personal charges run through a business account. Booked receipts are recorded on a different basis, so the totals drift apart for reasons that are all explainable once you set them side by side.

The workflow is short on purpose. First you import the 1099-K and a sales export from the client’s books. Then you map the columns so the tool knows which field is the gross amount, which is the month, and which is the transaction count. After that it builds the tie-out and the variance report. Nothing is filed anywhere and nothing is transmitted to the government. The tool does the matching math and the human keeps the judgment.

What comes out is a schedule that compares 1099-K totals against booked receipts by month, then names the reconciling items that account for the difference, refunds, fees, timing, and personal charges. Instead of a single unexplained variance at year end, you get a per-month picture that shows where the gap opened and what caused it. That is the difference between guessing and knowing when a client asks why their form is higher than their recorded sales.

Why this matters is the IRS matching program. When a filed return’s gross receipts sit below the 1099-K the agency also received, that mismatch can trigger a notice. A clean tie-out schedule is the answer to that notice prepared in advance, sitting in the workpapers before anyone asks for it. The 1099-K & gross receipts tie-out software exists so the number on the return can be defended with a document rather than a memory.

For a firm running many client books, the value is that the same short workflow repeats identically on every engagement. You are not rebuilding a reconciliation spreadsheet from scratch for each client. You feed the form and the sales export, map once, and read the result. You can see how it fits a tax practice on the product page, and it does the one job, the tie-out, the same way every time. That sameness is what makes the output something you can hand to a reviewer without a second look, and what makes the tie-out software worth running on every client who ever swiped a card.

How does a 1099-K tie-out help a client’s gross receipts survive an IRS matching notice?

A matching notice starts when the gross receipts on a filed return come in under the Form 1099-K the IRS received from a client’s payment processors. The agency compares the two figures, and a shortfall can produce a letter asking the taxpayer to explain or pay. The tie-out schedule this tool builds is that explanation, written down before the letter arrives. It shows, month by month, that the return’s lower number is correct and that the difference is made of refunds, fees, timing, and non-business charges rather than hidden income.

The reason a schedule beats a spoken answer is recordkeeping. IRS Publication 583, Starting a Business and Keeping Records, states that supporting documents include the sales slips, invoices, receipts, and deposit slips that back up what ends up on a return, and that a business should keep them in an orderly fashion. A tie-out that maps processor totals to booked sales is exactly that kind of orderly supporting document. It connects the third-party form to the ledger the return was built from, in one page a reviewer can read.

Because the 1099-K & gross receipts tie-out software produces an IRS-ready tie-out schedule as a by-product of the reconciliation, the record exists the moment the work is done, not scrambled together under notice pressure months later. The preparer imports the 1099-K and the sales export, maps the columns, and the schedule is generated with the variance already itemized. If the client is ever questioned, the firm opens the workpaper and reads the answer straight off the page.

The month-by-month layout is what makes the schedule persuasive. A single annual variance invites suspicion because it looks like a plug. A per-month tie-out that shows refunds in one month, a batch of processor fees in another, and a timing difference at the year boundary reads like what it is, ordinary business activity. Each reconciling item is labeled, so the reviewer at the firm and the examiner at the agency are looking at the same story.

None of this changes what the client owes. The tool does not file the return and does not move money. It documents the bridge between two numbers so the correct gross receipts figure can stand. The judgment about what belongs in income stays with the preparer, who now has a schedule to point at instead of a recollection to defend.

Run across a full client base, the 1099-K & gross receipts tie-out software makes a documented tie-out the routine outcome rather than the lucky one. Every card-accepting client ends the year with a matching schedule already sitting in the workpapers, so a notice on any one of them becomes a document lookup instead of a research project that starts from a cold spreadsheet.

For a firm that prepares returns for many card-accepting clients, this is the record that turns a stressful notice into a five-minute reply. You keep your own workpaper structure and your own review habits. The tie-out software simply produces the one document the matching program is most likely to ask for. You can see the rest of the SortTax lineup on the accounting and tax page, where the tie-out sits alongside the other tools a tax practice runs each season, and each one is built to leave a record you can defend rather than a number you have to explain from memory.

Is client payment data safe, and where does the 1099-K tie-out keep the files it reads?

The honest answer a firm wants first is where the data goes. The tie-out reads a client’s Form 1099-K and a sales export, which together describe every card and network payment a business took in a year. That is sensitive financial data, and the tool is built to work with it in place rather than shipping it off to a third party. You import the files, the reconciliation runs against them, and the tie-out schedule comes back, all within the firm’s own workflow.

Protecting that kind of data is not optional for a tax practice. The Federal Trade Commission treats professional tax preparers as financial institutions under its rule, and its guidance, FTC Safeguards Rule: What Your Business Needs to Know, tells firms to develop, implement, and maintain an information security program with administrative, technical, and physical safeguards designed to protect customer information. A tool that reads 1099-K totals and booked sales sits squarely inside the scope of information a firm must protect under that program.

The 1099-K & gross receipts tie-out software fits that obligation by keeping the work close to the firm. Client payment records are handled as part of the reconciliation and the resulting tie-out schedule stays with the firm’s own files. There is no requirement to hand a full year of a client’s processor data to an outside platform in order to answer a simple matching question. The narrower the path the data travels, the smaller the surface a firm has to secure.

It is worth being plain about what the tool is and is not. It does the matching math between two imported numbers and writes a schedule. It does not advertise itself as antivirus and it does not replace the firm’s own security program. What it does is avoid adding a new place where a client’s payment history lives, which is one fewer copy to account for when the firm writes down its safeguards.

A firm’s security program also has to cover the everyday habits around a tool like this, who can open the imported files, where the exported schedule is stored, and how old copies are disposed of. The tie-out software supports those habits by keeping its inputs and outputs where the firm already applies its controls, rather than scattering them across an outside service the firm does not run.

Put plainly, the 1099-K & gross receipts tie-out software is designed to reduce the number of places a client’s payment history has to live, not add to it. A firm that already keeps a written program can bring the tool inside that program without redrawing the map of where sensitive data sits, because the form and the export are read where the firm already applies its controls.

For the buyer, a small CPA or bookkeeping firm, this is the difference between adopting a tool and adopting a liability. You get the reconciliation you needed without widening the circle of systems that touch client money. You can read how the tie-out fits a practice on the product page, and decide for yourself how it slots into the written safeguards you already keep. The tool earns its place by staying inside the fence you have already built, not by asking you to build a new one around somebody else’s cloud.

How is the 1099-K tie-out different from doing the reconciliation in a spreadsheet by hand?

Most firms already do this reconciliation. They do it in a spreadsheet, from scratch, every time a client’s Form 1099-K lands higher than the sales on the books. The 1099-K & gross receipts tie-out software replaces that blank-page ritual with a repeatable one. You import the form and a sales export, map the columns once, and get a tie-out and variance report. The manual version and the tool reach the same kind of answer, but only one of them behaves identically on the hundredth client.

The catalog is direct about what it replaces, spreadsheets and manual reconciliation. The difference is not that a spreadsheet cannot subtract. It is that a hand-built spreadsheet carries a preparer’s one-off formulas, a preparer’s column choices, and a preparer’s chance of a broken cell reference. When the person who built it leaves, the next person relearns it. The tool gives every engagement the same structure, so a reviewer opening one client’s tie-out already knows how to read the next.

Retention is the quieter difference. The IRS page, How long should I keep records?, states that a business generally keeps records for three years, keeps employment tax records for at least four years, and keeps records indefinitely if no return is filed. A tie-out is one of those supporting records. A schedule produced by the tool is labeled and consistent, which makes it far easier to retain and retrieve than a spreadsheet named after whatever the preparer typed that afternoon.

Speed matters too, but not the way people expect. The tool does not just run faster. It removes the part of the job where mistakes hide, the manual mapping of a processor’s columns to a client’s ledger. You map once, and the reconciling items, refunds, fees, timing, and personal charges, come back itemized rather than buried in a formula you have to trust.

There is a fair limit to state. The tool is not a full accounting package and it does not rebuild the books. It reconciles what you import against the 1099-K and explains the gap. If the underlying sales export is wrong, the tie-out will be wrong in the same way, and a preparer still has to know the client’s business. What changes is that the mechanical work is consistent and the output is defensible.

The plainer way to say it is that the 1099-K & gross receipts tie-out software takes a task you already perform and makes it behave the same on client one and client fifty. A hand-built spreadsheet rewards the person who wrote it and punishes the person who inherits it, and that trade stops being acceptable once the volume of card-accepting clients climbs into the dozens.

For a firm juggling many client books in a compressed season, that consistency is the whole argument. A spreadsheet is fine for one client. It becomes a risk at fifty. The tie-out software turns a task that scaled badly into one that scales the same every time. You can see how it sits next to the other SortTax tools on the accounting and tax page, and judge whether trading your spreadsheet for a repeatable schedule is worth it for the volume of matching notices your clients actually attract each year.

Can the tie-out explain reconciling items like refunds and processor fees on a client’s 1099-K?

This is the capability the tool is built around. A Form 1099-K reports a gross number, and gross is almost never what a business recorded as sales. The 1099-K & gross receipts tie-out software takes that gross figure apart and names the reconciling items that stand between it and the booked receipts, refunds, processor fees, timing differences at the year boundary, and personal charges that ran through a business account. Each item is itemized in the variance report rather than lumped into one number.

The reason those items exist is in how the form is defined. The IRS page, Understanding your Form 1099-K, describes the form as a report of the payments received for goods or services during the year, which is a gross measure taken before any of the usual subtractions. Refunds issued to customers are still in that gross total. Fees the processor kept were never deposited but still counted. Sales tax collected for the state passed through. The tool exists because the form and the ledger measure different things.

Mechanically, the reconciliation runs month by month. You import the 1099-K and a sales export, map the columns, and the tool compares 1099-K totals against booked receipts for each period. Where the two disagree, it surfaces the difference and lets the preparer attach the reason. Over a year, the pattern becomes obvious, fees are steady, refunds cluster around returns, and timing differences show up right at the December and January boundary.

Naming the items is what makes the schedule useful under scrutiny. An unexplained variance looks like a problem. A variance broken into refunds, fees, timing, and personal charges looks like ordinary business, because that is what it is. The tie-out software gives the preparer a labeled line for each cause, so the client’s gross receipts can be defended item by item rather than as a single leap of faith.

The output stays with the firm as a workpaper. It is the IRS-ready tie-out schedule the catalog describes, produced as a by-product of the reconciliation rather than as a separate write-up. If a matching notice ever arrives, the reconciling items are already documented and dated, sitting in the file the moment the return was prepared.

Because it names each cause on its own line, the 1099-K & gross receipts tie-out software also makes the review inside the firm faster. A second preparer can read the schedule and follow the logic without asking the first how a number was reached, which is what keeps a busy season from turning every client’s tie-out into a separate conversation at the reviewer’s desk.

There is a boundary worth naming. The tool identifies and organizes the reconciling items, but the preparer decides how each one is treated on the return. A personal charge run through a business account is a judgment call, not a math result. The tie-out surfaces it so the human can make that call with the number in front of them. You can read more about how the reconciliation fits a tax practice on the product page, where the tie-out is described as one focused job done the same way on every client who takes card and network payments through a processor that issues a 1099-K.

Attributes Value
Deployment

Cloud

Platform

Web

License Type

Subscription

Billing Period

Monthly

Target Customer

Accounting & CPA Firms

Free Trial

Yes

Reviews

Be the first to review “1099-K & Gross Receipts Tie-Out”

Your email address will not be published. Required fields are marked *