Cross-Venue Prediction Market Accounting: Kalshi, Polymarket, and Multi-Venue Trading

Last Updated on August 23, 2026 by Patrick Camuso, CPA

Quick answer (read this first)

The short answer: A professional prediction-market firm generally cannot establish its accounting or tax reporting by adding together the profit and loss reported by Kalshi, Polymarket, and other venues. Each source environment first needs to be understood and reconciled according to the records it actually produces. The relevant activity can then be incorporated into a transaction-level subledger that reconciles to the entity’s general ledger and preserves the position-level facts needed for tax analysis.

What matters: Depending on the operation, the subledger may need to capture the relevant accounts and wallets, transaction history, position activity, settlements, transfers, fees, incentives, year-end open positions, and other material lifecycle events across several venues. Cash and positions also need to be reconciled separately because one does not establish the completeness of the other.

What does not follow automatically: Platform P&L does not determine federal taxable income. Positions that offset economically are not necessarily one position for accounting or federal tax purposes. Conversely, maintaining positions on different platforms does not, by itself, prevent them from becoming relevant to the same tax analysis.

Who this affects: These issues become most significant for market makers, proprietary trading firms, systematic traders, arbitrage operations, funds, family offices, and other professional participants trading through multiple prediction-market venues, brokers, accounts, or wallets.

A professional prediction-market operation may trade related exposure through Kalshi, Polymarket.com, Polymarket US, and other venues or access models while managing the activity as one economic book. That can be entirely appropriate for risk and performance reporting. For accounting and tax purposes, however, the firm still needs to establish what it owned, which taxpayer owned it, how the positions changed, how cash and collateral moved, what remained open at year-end, and how the resulting activity was recorded in the general ledger.

For a professional multi-venue operation, the accounting process generally moves from venue-specific source records to a reconciled transaction-level subledger and then to the entity’s general ledger. The subledger preserves the transaction and position detail that would ordinarily be lost if the operation relied only on summarized platform P&L or general-ledger entries. For some tax questions, the relevant inquiry also extends beyond the venue where an individual position appears. Economically related positions may need to be considered across the relevant taxpayer’s broader position population.

Our broader Prediction Market Accounting Guide addresses the overall accounting framework for prediction-market traders, funds, and institutions. The separate Prediction Market Tax Guide addresses the federal characterization issues that follow from the underlying contracts and taxpayer facts. This article focuses on the narrower cross-venue subledger and reconciliation problem.

The platform-specific discussion below reflects participant-facing public materials reviewed as of the date of this article. Platform APIs, account structures, contract mechanics, and reporting capabilities can change and should be reverified when relied upon for a particular accounting or tax matter. Nothing in this discussion assesses a venue’s internal systems or regulatory compliance or establishes the federal tax treatment of a particular contract or transaction.

Polymarket.com and Polymarket US Need to Be Distinguished

An accounting record should distinguish Polymarket.com from Polymarket US rather than treating all activity under the Polymarket name as one source environment. As of the date of this article, Polymarket’s public help materials identify Polymarket.com as the international product and Polymarket US as a separate U.S. product. The accounts are separate. Polymarket.com operates through a blockchain-based trading environment in which account-wallet information, outcome tokens, trading records, collateral activity, and on-chain transactions can each contribute different evidence to the accounting history. Its current documentation describes YES and NO outcome tokens on Polygon and identifies position events including split, trade, merge, and redemption. Polymarket.com positions and tokens documentation

Polymarket US presents a different participant-facing reporting environment. Its current institutional materials identify search and export functionality for orders, trades, and executions, including reporting described for end-of-day reconciliation. Polymarket US institutional reporting documentation. Accordingly, saying that a taxpayer “trades on Polymarket” is not sufficiently specific for a professional accounting engagement. The actual product, account structure, legal or beneficial owner, and source records need to be identified before the activity is incorporated into the subledger.

Why Different Prediction-Market Venues Cannot Simply Be Combined

Cross-venue accounting is sometimes treated as a file-normalization problem. Different exports have different columns, so the apparent solution is to convert them into one format and combine them. The accounting issue is broader because different source systems may describe different stages of a position’s lifecycle.

As of the date of this article, Kalshi’s public API documentation identifies participant records relating to fills, positions, settlements, deposits, withdrawals, balances, transfers, and subaccounts. Kalshi also separates certain older records from current portfolio data through its historical-data environment. A current Kalshi extraction can therefore contain significant information while still requiring additional records for a longer historical period or another accounting purpose.

Polymarket.com presents a different lifecycle. Positions may change through order-book trades, token creation, merges, transfers, redemption, and other supported mechanics. Those events should not be treated as interchangeable simply because each affects a position balance. Other prediction-market venues and access models can create their own variations. The customer-facing brand may also be different from the exchange, account, wallet, clearing, or other source that ultimately matters to the accounting.

The transaction-level subledger should be populated only after the source records and their material completeness have been sufficiently understood for the accounting purpose at issue.

Venue-Level Reconciliation Comes Before Subledger Consolidation

A multi-venue firm ultimately needs entity-level books, but combining venue records before each source environment can be explained can conceal accounting differences rather than resolve them.

For Kalshi, the relevant evidence may include fills, positions, settlements, cash activity, transfers, subaccounts, and historical records for the period under review. For Polymarket.com, the relevant evidence can extend beyond conventional trade history because wallet and token activity may explain position changes that are not fully represented by an order-book record alone. Other venues may provide trade confirmations, account statements, settlement files, tax statements, position reports, APIs, or other transaction histories.

Venue-level reconciliation establishes what the source records support before the activity is consolidated into the entity-level subledger. The subledger can then standardize the accounting attributes needed across venues while retaining the source identity of the venue, account, position, and relevant lifecycle event.

A Kalshi position should remain identifiable as a Kalshi position after it enters the subledger, and a Polymarket.com position should retain the facts needed to explain its wallet, token, trading, and settlement history.

Why the Transaction-Level Subledger Needs to Cover the Relevant Trading Population

At higher transaction volumes, a transaction-level subledger becomes the practical bridge between venue data and the general ledger. The important issue is not one particular software product or one prescribed subledger design. It is whether the subledger captures the population needed to support the entity’s books and tax analysis.

A professional firm’s trading activity can span multiple venues, accounts, subaccounts, wallets, entities, contract types, and tax years. The subledger needs to preserve the individual position histories while allowing the relevant taxpayer’s broader trading population to be analyzed together when necessary. Where several legal entities are involved, the subledger also needs to preserve those taxpayer boundaries. Positions should not be consolidated into the same taxpayer population merely because the entities share owners, employees, infrastructure, or a common commercial strategy.

This matters because a platform boundary does not necessarily define an accounting or tax boundary. One economic strategy may contain positions maintained on several prediction-market venues. An economically related position can also exist through another broker, wallet, or instrument outside the platform where the first position appears. A professional subledger therefore performs two related functions. It preserves the transaction-level history of the individual contracts and creates a comprehensive accounting population from which venue, account, entity, position, strategy, and tax-sensitive relationships can be evaluated.

The general ledger serves a different purpose. It records the summarized financial accounts of the entity. It should reconcile to the subledger without being expected to contain the complete transaction history itself.

Why Section 1092 Can Make the Broader Position Population Important

Cross-venue arbitrage illustrates why the tax analysis cannot always stop at individual platform accounts. A firm may maintain one position on Kalshi and an economically related position on Polymarket.com that reduces some or substantially all of the economic exposure associated with the first position. Management may appropriately view the legs as components of one trading strategy. The underlying contracts nevertheless retain separate acquisition histories, costs, fees, timing, contractual rights, and endpoints.

Section 1092 defines a straddle through offsetting positions with respect to personal property and looks, among other things, to whether another position substantially diminishes the taxpayer’s risk of loss. Section 1092 of the Internal Revenue Code Whether particular prediction-market contracts or a particular combination of positions falls within those rules remains a separate legal and tax question.

The venue on which a position appears does not, by itself, resolve that analysis. At the same time, economic correlation, a common referenced event, or management’s description of a strategy as an arbitrage does not establish that a statutory straddle exists. Where the straddle rules apply, separate timing consequences can follow, and Section 263(g) contains rules concerning certain interest and carrying charges allocable to property that is part of a straddle. Other cross-position rules may also require review depending on the contracts and surrounding facts.

The subledger needs to preserve enough position-level information to permit the legally relevant population to be evaluated across venues without treating every economically related trade as though a particular tax rule automatically applies. The actual identification, matching, grouping, and application of those provisions is a separate tax-analysis workstream and is outside the scope of this article.

Economic Closure Does Not Necessarily Mean the Positions Have Closed

A strategy can become economically neutral before its individual positions have ended. For example, positions maintained on different venues may substantially offset one another. Management may therefore regard the strategy as economically complete even though one or more underlying contracts remain open. Each position can still have its own acquisition cost, quantity, fees, timing, and legally relevant endpoint. One position may be transferred before resolution while another remains outstanding. Positions on different venues can also end in different tax years or through different contractual mechanics.

The transaction-level subledger should therefore preserve the individual legs even if a management report groups them into one arbitrage or market-making strategy. That distinction becomes important whenever recognition, character, loss limitations, basis, or other tax consequences depend on what actually happened to the individual positions rather than the net economic result of the strategy.

Our prediction-market loss deduction analysis discusses why characterization, recognition, deductibility, and loss utilization remain separate questions.

Cash Reconciliation and Position Reconciliation Are Separate Controls

A cash reconciliation does not establish the completeness or accuracy of the position subledger, just as a position reconciliation does not independently establish that every material cash movement has been captured. Cash reconciliation can help explain how beginning cash became ending cash after funding, withdrawals, trading activity, settlement proceeds, fees, incentives, transfers, and other adjustments. Position reconciliation addresses what contracts the firm owned and how those positions changed.

A venue cash balance can agree with the platform while an open position remains missing or carries incomplete acquisition-cost information. The position subledger can likewise reconcile while a withdrawal, rebate, funding movement, or other cash adjustment remains omitted or misclassified. Depending on the venue, available cash, collateral, amounts committed to orders, and economic exposure can also represent different concepts. Those amounts should not automatically be treated as interchangeable merely because they appear in the same account environment.

For a professional operation, both the cash reconciliation and the position reconciliation ultimately need to support the entity-level subledger and the balances posted to the general ledger.

Gross Transaction Data Should Remain in the Subledger

Management may appropriately evaluate a market-making or arbitrage strategy by its net economic result. The subledger generally needs to preserve more information than that management presentation. Gross positive and negative results, acquisition costs, proceeds or settlement amounts, fees, incentives, transfers, and open positions can matter separately under the accounting and tax rules applicable to the activity.

This becomes particularly important across venues. A profitable position on one platform can offset a loss elsewhere economically without establishing how either position is recognized, characterized, limited, or otherwise treated for federal tax purposes. The subledger should therefore retain sufficient transaction-level detail to reproduce the components of the consolidated result.

The general ledger can receive summarized journal entries. Those journal entries should reconcile back to the subledger rather than replace it.

Fees, Rebates, Rewards, and Liquidity Incentives Need Separate Subledger Treatment

Professional prediction-market firms can generate amounts outside the basic acquisition and settlement economics of the contracts. Market makers may incur transaction fees or receive maker rebates and liquidity incentives. Other participants may receive holding rewards, refunds, credits, or other platform payments. Those amounts may require different treatment depending on the governing arrangement, the economic function of the payment, and the applicable tax rules.

A platform label is relevant source information, but it does not independently determine federal tax treatment. The transaction-level subledger should therefore preserve material fees, rebates, rewards, and other platform adjustments separately enough that the ultimate accounting and tax treatment can be supported without attempting to reconstruct the amounts from net platform P&L.

Funding, Transfers, and Ownership Need to Be Reflected Correctly in the Subledger

Cross-venue operations may move funds among banks, venue accounts, subaccounts, wallets, and other controlled accounts. The direction of a movement does not determine its accounting treatment. Depending on the facts, an inflow or outflow may reflect funding, collateral movement, an internal transfer, a contribution or distribution, trading consideration, settlement proceeds, an asset conversion, or another event.

A transfer between two accounts legally and beneficially owned by the same entity can present a different accounting question from a movement between the entity and an owner, another entity, or a third party. If an internal transfer is recorded as revenue in one account and an expense in another, the entity-level subledger and consolidated P&L can be distorted even if both individual account balances appear correct.

This issue is particularly important where several members, partners, or related entities participate in the broader trading operation. The subledger needs to preserve taxpayer and entity boundaries even where the same commercial strategy spans several controlled accounts.

Account, Wallet, Subaccount, and Entity Identity Matter

A comprehensive subledger is only useful if the trading activity has been assigned to the correct taxpayer. A professional operation may use master accounts, subaccounts, trading wallets, funding wallets, owner-controlled wallets, and accounts associated with several legal entities. A wallet address should not be attributed to a taxpayer solely because somebody within the organization recognizes it. Likewise, operational access to an account does not necessarily establish legal or beneficial ownership.

Polymarket.com makes this issue particularly visible because its participant-facing account structure can distinguish signing credentials from account wallets. Other venues can present similar distinctions through master accounts, subaccounts, broker relationships, or controlled entities. The subledger should preserve enough account and ownership identity to determine which activity belongs in each entity’s books before the accounting is consolidated.

Missing Records and Exceptions Should Remain Visible in the Subledger

Historical data can have different coverage from current APIs. A transfer can initially lack an identifiable counterpart. A position may lack enough acquisition history to establish its cost. Settlement information may arrive separately from the transaction history. Platform corrections can also occur after an initial report has been generated. Material unresolved items should not disappear merely because assigning them to income or expense would make the general ledger tie.

The subledger should preserve material exceptions until the underlying facts can be established or an appropriate accounting or tax treatment is adopted. Similarly, an apparently expired contract should not be treated as having reached a particular endpoint solely because doing so produces a convenient position rollforward. The endpoint should be supported by relevant source evidence.

The objective is a subledger in which material exceptions remain identifiable rather than being concealed through normalization, netting, or consolidation.

Corrections and Other Lifecycle Events Need to Flow Through the Subledger

Depending on the venue, trading history can later be affected by corrections, voids, market cancellations, settlement adjustments, fee changes, refunds, or other post-trade events. Those items can matter even when the eventual cash balance appears correct.

A balance-level reconciliation that loses the correction history may leave the firm unable to explain why two reporting periods or two accounting runs produce different results. The subledger should therefore preserve enough transaction history to incorporate material corrections without losing the relationship to the source activity that preceded them.

Platform Changes Can Affect Historical Subledger Reconstruction

Prediction-market platforms continue to change account structures, APIs, collateral systems, contract mechanics, and reporting conventions. Historical activity should be interpreted using the source environment applicable to the period under review rather than automatically assuming that today’s platform architecture existed throughout the taxpayer’s trading history.

The same issue arises when API fields change, older records move into historical endpoints, fee presentation changes, or a new product introduces a different position lifecycle. A historical subledger may need to account for more than one version of a platform’s records across several tax years. Source provenance and period context become increasingly important as reconstruction extends further into a firm’s trading history.

Time, Ordering, Units, and Precision Can Affect the Subledger

At high transaction volumes, operational details that appear minor can alter the resulting position history.

A transaction around December 31 can fall into a different reporting period depending on the relevant timestamp and time-zone convention. When multiple transactions affect the same position in rapid succession, sequencing can influence the resulting open-position population. Platforms can also report prices, quantities, and fees at precision levels that do not map cleanly to conventional two-decimal general-ledger records.

The appropriate methodology depends on the source systems and reporting requirements. The accounting objective is reproducibility. The subledger should not produce different position histories merely because time-zone assumptions, ordering rules, units, or rounding conventions change without explanation. At institutional transaction volumes, seemingly small differences can compound into material reconciliation issues.

Year-End Requires an Open-Position Subledger

Annual P&L does not necessarily establish what the taxpayer held at the reporting cutoff. A position acquired late in the year may remain open on December 31 and terminate during the following year. A related position on another venue may end in a different period. Transfers or corrections can also remain unresolved around the cutoff date. Depending on the activity, year-end accounting may therefore require a point-in-time open-position subledger identifying material positions and unresolved items at the reporting cutoff.

That closing population becomes part of the opening position population for the following year. If the carryforward cannot be supported, a later disposition or settlement calculation can inherit a prior-year accounting gap even if the current year’s venue data is otherwise complete. Cross-year subledger continuity therefore matters independently of whether the annual platform P&L appears correct.

Platform Statements and Tax Forms Need to Reconcile to the Subledger

A platform P&L, annual statement, or information return can be important evidence without becoming the transaction-level subledger. If a platform-reported figure differs from the firm’s subledger, the difference should be understood before the platform number is automatically substituted for the books.

Timing, scope, acquisition-cost information, transaction definitions, fees, settlements, and reporting conventions can all create differences between platform statements and the entity’s accounting. The existence of a tax form likewise does not determine substantive federal tax character. Our Kalshi tax reporting analysis addresses the information available from Kalshi and what those records do not resolve. For Polymarket.com, our Polymarket tax reporting guide addresses the separate wallet, token, and self-reporting issues.

For a multi-venue firm, the accounting may therefore involve several reconciliations including source records to the transaction-level subledger, the subledger to platform statements or information returns, and the subledger to the general ledger. The applicable tax analysis is then applied to the relevant facts rather than inferred from any one reporting document.

How the General Ledger Fits Into Cross-Venue Prediction Market Accounting

QuickBooks, NetSuite, Xero, or another general ledger can remain an appropriate financial-accounting system for the reporting entity. The general ledger and the transaction-level subledger perform different functions.

The general ledger carries the entity’s summarized financial accounts, including cash, operating expenses, payroll, owner or partner accounts, and trading-related balances. The transaction-level subledger carries the detailed prediction-market activity needed to support those balances. Depending on the operation, that can include acquisition and position history, settlements, transfers, fees, incentives, wallet activity, open positions, and other lifecycle events. A professional prediction-market operation may generate too much transaction-level detail for the general ledger to serve both functions effectively.

The accounting structure can preserve detailed trading activity in the subledger and post approved summarized journal entries to the general ledger. Those journal entries should reconcile to the subledger, and the subledger should in turn remain traceable to the source records. Book accounting and tax analysis can use the same factual subledger without necessarily reaching identical classification, measurement, timing, or presentation conclusions.

What This Means in Practice

Kalshi and Polymarket.com make the cross-venue problem particularly visible because their participant-facing record environments differ materially, but the accounting issue extends to any professional operation trading through multiple prediction-market venues, brokers, accounts, or wallets. A professional firm needs more than several platform P&L statements.

Depending on the operation, it may need venue-level source reconciliation, a comprehensive transaction-level subledger, separate cash and position reconciliations, account and entity ownership controls, gross transaction detail, fee and incentive tracking, open-position continuity, exception management, and subledger-to-general-ledger reconciliation.

Where economically related positions exist across venues, the same subledger may also need to support analysis under Section 1092 and other applicable cross-position rules. Whether those provisions actually apply remains a separate tax conclusion. For professional market makers and multi-venue trading firms, the subledger becomes the accounting record that connects the underlying trading activity to the general ledger and, ultimately, to tax reporting.

How Camuso CPA Helps

Camuso CPA works with professional prediction-market traders, market makers, proprietary trading firms, funds, and other entities operating across Kalshi, Polymarket.com, Polymarket US, and other prediction-market environments.

For firms with material cross-venue activity, the work may extend beyond return preparation to evaluating source records, reconstructing historical trading activity where necessary, developing the transaction-level subledger, reconciling that subledger to the general ledger, and coordinating the resulting accounting with the tax analysis applicable to the firm’s positions.

Our Prediction Market Accounting services address these accounting and reconciliation issues for professional trading operations. At higher trading volumes, return preparation becomes the final stage of a larger classification, subledger accounting, reconciliation, and reporting process.

Request a Prediction Market Tax & Accounting Assessment

Frequently Asked Questions

Can I simply combine the P&L from Kalshi, Polymarket.com, and my other prediction-market venues?

The combined amount may be useful for management reporting, but it does not by itself establish reconciled books or a taxable result. Depending on the activity, the firm may need to reconcile each source environment, incorporate the relevant transactions into a transaction-level subledger, reconcile cash and positions, identify year-end open positions, and evaluate economically related positions across the taxpayer’s broader trading population.

What makes Kalshi and Polymarket accounting different?

Kalshi and Polymarket.com produce different participant-facing records and represent position activity differently. Kalshi’s public materials identify exchange and account records such as fills, positions, settlements, balances, transfers, and subaccounts. Polymarket.com also operates through a wallet- and token-based environment in which split, trade, merge, transfer, and redemption activity can affect the position history. Those differences need to be reconciled before the activity is consolidated into an entity-level subledger.

What is the difference between Polymarket.com and Polymarket US for accounting purposes?

Polymarket.com and Polymarket US are separate products with separate accounts and different participant-facing reporting environments. Polymarket.com operates through a blockchain-based wallet and outcome-token architecture, while Polymarket US provides a separate U.S. trading and reporting environment. The accounting and subledger reconstruction should be based on the actual product, account structure, ownership, and source records used by the taxpayer.

Does a professional prediction-market firm need a transaction-level subledger?

At higher transaction volumes, a transaction-level subledger can become necessary to maintain the position and transaction detail that a general ledger is not designed to carry. The appropriate structure depends on the trading operation, but the subledger may need to preserve venue, account, taxpayer, transaction, position, settlement, transfer, fee, and year-end information while reconciling to the entity’s general ledger.

Should all prediction-market venues be included in the same subledger?

The relevant trading activity generally needs to be reflected in a sufficiently comprehensive entity-level accounting population, while venue, account, wallet, and taxpayer distinctions remain preserved. Depending on the firm’s architecture, that may involve venue-specific components within a consolidated transaction-level subledger. The important point is that cross-venue positions can be analyzed together when applicable without losing their separate source histories.

Why is reconciling each prediction-market venue separately not always enough?

Venue-level reconciliation establishes what occurred within each source environment, but the entity’s general ledger ultimately needs to reflect the relevant activity across its accounts and venues. Transfers may cross platforms, positions can remain open across reporting periods, and economically related positions maintained in different places may become relevant to the same tax analysis. The transaction-level subledger provides the bridge between those venue records and the general ledger.

Can Section 1092 apply to positions maintained on different prediction-market venues?

Potentially, depending on the contracts and facts. The fact that positions appear on different platforms does not by itself determine whether Section 1092 applies. Economic correlation or a common referenced event also does not automatically create a statutory straddle. A sufficiently complete subledger helps preserve the position-level facts needed to perform the applicable analysis.

Do economically offsetting positions become one accounting position?

Not automatically. Management may appropriately evaluate several positions as one economic strategy while the underlying contracts retain separate acquisition costs, source records, timing, and endpoints. The subledger generally needs to preserve those individual positions even when they are aggregated for performance or risk reporting.

What changes for market makers trading across several prediction-market venues?

Market makers can generate high transaction volumes, economically related positions, transaction fees, rebates, incentives, and activity distributed across multiple accounts or venues. Those characteristics can increase the importance of a comprehensive transaction-level subledger, separate cash and position reconciliation, entity-level consolidation, and cross-position tax analysis. Market-maker status itself does not determine federal tax character.

Can QuickBooks handle multi-venue prediction-market accounting?

QuickBooks or another general ledger can remain part of the accounting system, but a high-volume prediction-market operation may require a transaction-level subledger to maintain the detailed trading record. General-ledger balances and summarized journal entries should reconcile to that subledger, and the subledger should remain traceable to the underlying venue, wallet, settlement, and cash records.

What should happen to prediction-market positions that remain open at year-end?

Depending on the accounting and tax issues involved, the year-end subledger may need to identify the positions that remain open at the reporting cutoff and carry the relevant transaction history into the following period. Annual platform P&L alone does not necessarily establish that point-in-time open-position population.

When should a professional trading firm address cross-venue reconciliation?

Addressing cross-venue reconciliation and subledger accounting before year-end and before tax preparation is underway generally reduces the amount of historical reconstruction required. As transaction volume and the number of venues increase, unresolved ownership questions, transfers, open positions, and data gaps can become substantially harder to resolve after the fact.