Venmo, Zelle and the 1099-K

The number on a 1099-K is gross. The regulation says so in one sentence, and the list of things it disregards includes refunded amounts and fees.

Which is why a guide who took twenty thousand dollars through an app, refunded two trips and paid three per cent in processing can receive a form showing the whole twenty thousand. Nothing has gone wrong. The form is doing exactly what it is defined to do, and the reconciliation is the taxpayer's job. Beyond that, whether a particular service produces a form at all depends on a three-part statutory test that has nothing to do with how the app markets itself. Below, the test and the gross rule are read from the statute and the regulation. Reporting thresholds have been the subject of repeated transition guidance, so confirm the exact figures for the year in question with the agency. This is not tax advice. The running the business hub collects the adjacent pieces.

What does gross amount mean here?

The total, before everything.

Section 1.6050W-1 of Title 26 defines gross amount, for the purposes of the section, as the total dollar amount of aggregate reportable payment transactions for each participating payee without regard to any adjustments for credits, cash equivalents, discount amounts, fees, refunded amounts or any other amounts.

It then adds that the dollar amount of each transaction is determined on the date of the transaction.

Both halves matter. The first means the figure is not your revenue and was never intended to be. The second means a deposit taken in December for a trip in May counts in December.

So a guide comparing the form to their own books should expect a difference, and should expect to be able to explain it rather than to eliminate it.

The regulation is on the eCFR.

Why the books have to be able to produce that reconciliation is covered in the bookkeeping piece.

Castaway Anglers, NC

Who has to file the form?

A payment settlement entity, and there are two kinds.

Section 6050W(a) of Title 26 requires each payment settlement entity to make a return for each calendar year setting out the name, address and taxpayer identification number of each participating payee to whom payments in settlement of reportable payment transactions are made, and the gross amount of those transactions for each payee.

Subsection (b)(1) defines a payment settlement entity as the merchant acquiring entity in the case of a payment card transaction, and the third party settlement organization in the case of a third party network transaction.

Subsection (b)(2) defines the merchant acquiring entity as the bank or other organisation with the contractual obligation to make payment to participating payees in settlement of payment card transactions.

Subsection (b)(3) defines the third party settlement organisation as the central organisation with the contractual obligation to make payment to participating payees of third party network transactions.

Those are two different routes to the same form, and which one applies decides whether a threshold exists at all.

What the card side costs is covered in the card fees piece.

Feelin Fishy, WI

What is a third party payment network?

A three-part test, and the third part is an undertaking that providers get paid.

Section 6050W(d)(3) defines a third party payment network as any agreement or arrangement that satisfies three conditions.

First, it involves the establishment of accounts with a central organisation by a substantial number of persons who are unrelated to that organisation, who provide goods or services, and who have agreed to settle transactions for the provision of those goods or services under the arrangement.

Second, it provides for standards and mechanisms for settling those transactions.

Third, the arrangement must assure persons providing goods or services under it that they will be paid for providing them, which is the condition that separates a settlement network from a simple transfer service.

The subsection then excludes any agreement or arrangement that provides for the issuance of payment cards, which is how the card route and the network route are kept separate.

Whether a particular service satisfies that test is determined by the terms of its own arrangement, so the place to look is the operator's own tax reporting statements rather than any general account.

What the client agreement should say about payment is covered in the booking terms piece.

Is there a threshold?

The statute states one, and it applies only to the network route.

Section 6050W(e) provides that a third party settlement organisation is required to report with respect to the third party network transactions of a participating payee only if the amount that would otherwise be reported exceeds twenty thousand dollars and the aggregate number of those transactions exceeds two hundred.

Two features of that are worth holding onto. It is written as a conjunction, so on the statutory text both conditions have to be met.

And it appears only in the exception for third party settlement organisations, which means the card route carries no equivalent de minimis rule in this section.

That is the distinction most guides get wrong, because they assume a single threshold covers every way money arrives.

These figures have been the subject of repeated administrative transition guidance, so the operative numbers for a given year must be confirmed with the agency rather than taken from the statutory text or from here.

The statute is published by the Law Revision Counsel, and the agency's own page on the form is at the Internal Revenue Service.

How the quarterly obligation interacts with all of it is covered in the quarterly piece.

Are tips reported separately?

Yes, in the case of a third party settlement organisation.

Section 6050W(a)(3) requires the return, in the case of a third party settlement organisation, to set out the portion of reportable payment transactions that have been reasonably designated by payors as cash tips, together with the occupation of the person receiving them.

That is a specific and relatively recent feature of the reporting, and it matters directly to a trade where tipping is normal.

What it means in practice is that a tip added inside an app is capable of arriving on the form as an identified amount rather than being invisible inside a total.

Which is not a reason to change how tips are taken. It is a reason to record them, since a figure reported by somebody else and absent from your own books is the shape of an unnecessary problem.

Guides frequently treat cash and app tips as the same thing operationally, and the reporting treats them differently.

What the wage side of a tip involves is covered in the pay splits piece.

Who is a participating payee?

Defined by acceptance, not by agreement.

Section 6050W(d)(1)(A) defines a participating payee as, in the case of a payment card transaction, any person who accepts a payment card as payment, and in the case of a third party network transaction, any person who accepts payment from a third party settlement organisation in settlement of such a transaction.

The operative word in both limbs is accepts, which is a description of conduct rather than of paperwork.

Subparagraph (B) excludes persons with a foreign address, except as the Secretary provides otherwise, and adds that a person with only a foreign address is not treated as a participating payee merely because they receive payments in dollars.

Subparagraph (C) includes governmental units and their agencies and instrumentalities within the meaning of person.

For a guiding operation none of that is likely to bite, and it is worth knowing that the definition turns on acceptance because it explains why no election or registration is involved.

What accepting cards involves operationally is covered in the taking payments piece.

What is a payment card, for this purpose?

Defined by the arrangement behind it, not by the plastic.

Section 6050W(d)(2) defines a payment card as any card issued pursuant to an agreement or arrangement providing for one or more issuers of such cards, a network of persons unrelated to each other and to the issuer who agree to accept the cards as payment, and standards and mechanisms for settling transactions between merchant acquiring entities and those who accept them.

It then adds a sentence that closes off the obvious workaround: acceptance of any account number or other indicia associated with a payment card is treated the same as accepting the card itself.

So a keyed-in number, a stored card on file and a tap all land in the same place, which is the sensible outcome and worth knowing before anybody constructs a theory about it.

The regulation restates the same definition, so the two are consistent rather than layered.

That consistency is useful, because it means reading either one gives you the position.

Why a card on file changes the deposit conversation is covered in the deposit piece.

What happens with an intermediary?

The reporting obligation moves, and the rule is explicit.

Section 6050W(b)(4)(A) provides that where reportable payment transactions of more than one participating payee are settled through an intermediary, that intermediary is treated as the participating payee for determining the reporting obligations of the payment settlement entity, and is treated as the payment settlement entity with respect to settling those transactions with the actual payees.

Subparagraph (B) provides that where an electronic payment facilitator or other third party makes payments in settlement of reportable payment transactions on behalf of the payment settlement entity, the return is made by that facilitator or third party instead.

Those two rules explain why a guide working through a booking platform or a lodge may receive a form from a party they have no direct relationship with.

They also explain the opposite surprise, which is receiving nothing from a party you assumed would report, because the obligation had shifted.

Either way the answer is not to reason from who you think should have sent it, but to reconcile against your own records of what actually arrived.

How the platform layer works is covered in the direct bookings piece.

What must the payer send you?

A written statement, with a named contact.

Section 6050W(f) requires every person required to make a return to furnish a written statement to each person with respect to whom the return is required.

The statement must show the name, address and phone number of the information contact of the person required to make the return, along with the reportable amounts.

The phone number requirement is the useful part, because it means there is a defined route to query a figure you cannot reconcile rather than a general customer service queue.

Using it early is better than using it in April, since a corrected statement takes time and the deadline does not move for you.

Whether a figure is wrong or merely different from your books is a question to settle before contacting anybody, since the gross rule accounts for most apparent errors.

What a proper record of receipts looks like is covered in the numbers piece.

Does a personal transfer count?

The definitions turn on providing goods or services, which is the line.

The network definition requires accounts established by persons who provide goods or services and who have agreed to settle transactions for that provision under the arrangement.

A transfer between two people that is not settling a transaction for goods or services does not fit that description, which is why reimbursing a friend for fuel is a different thing from being paid for a trip.

The difficulty is not the rule but the evidence, because an app does not know what a payment was for beyond what the parties tell it.

Which is the practical argument for keeping business takings and personal transfers on different accounts, since it makes the distinction visible rather than arguable.

It also makes the reconciliation trivial, because a business account's total is supposed to match a business form.

What the account separation involves is covered in the accounts setup piece.

What about a chargeback in a later year?

The gross rule dates the transaction, and the reversal is its own event.

Because the dollar amount of each transaction is determined on the date of the transaction, a payment received in one year appears in that year's reported gross.

A reversal occurring afterwards does not reach back into a figure already determined, and the regulation's list of disregarded adjustments confirms that the reported number is not netted.

Which means a chargeback landing in January against a trip paid for in November is handled in your own records rather than by a change to last year's form.

That is a reconciliation problem rather than a reporting problem, and it is one more reason the record has to be kept by transaction and by date.

How a disputed charge actually proceeds is covered in the chargebacks piece.

Does the form create the tax?

No, and that is the most consequential misunderstanding.

Income from a trade or business is taxable whether or not any third party reports it, and the reporting rules in this section are information reporting rather than a charge to tax.

Which means a threshold not being met changes nothing about what is owed, and a guide who received no form still has the same obligation.

It also means the opposite: receiving a form for an amount larger than your revenue does not increase what is owed, because the reconciliation is done on the return.

Both errors run in the same direction, which is treating the form as the source of truth about the business rather than as one report about money movement.

Your own records are the source of truth, and they are also the only thing that lets you demonstrate it.

Why every figure has to be establishable is covered in the hobby loss piece.

Where do guides go wrong on this?

Five places, and the first is arithmetic.

Treating the reported gross as revenue, which overstates income by the fees, the refunds and any chargebacks in the same year.

Assuming a single threshold applies to every payment route, when the de minimis rule in this section sits only in the exception for third party settlement organisations.

Splitting takings across several apps in the belief that thresholds are the point, when the tax is owed regardless of whether any form is issued.

Failing to record app tips, so an amount reported by somebody else has no counterpart in the books.

And treating a deposit as next season's income when the transaction is dated in the year it happened, which produces a mismatch that looks like an error and is not.

How the deposit timing should be handled is covered in the cash flow piece.

What the refund side involves is covered in the refund policy piece.

What should a guide do about it?

Build the reconciliation once and reuse it every year.

Keep a record of gross takings by payment route, so each form can be matched to a route rather than to a guess.

Record refunds and processing fees separately, because those are precisely the items the reported gross disregards and precisely the items that explain the gap.

Record tips separately, especially where they arrive inside an app, since they may be reported as an identified amount.

Date each transaction when it happened rather than when the trip runs, which is how the reported figure is built and therefore how yours has to be to compare.

And take the return itself to somebody qualified, since the reconciliation is straightforward and the reporting rules for a given year are not.

What the payment mechanics look like on the water is covered in the deposit piece.