Trading as a small business — costs, contracts and available cash
A profitable month does not mean you will have money for every bill when it falls due. Some funds may remain in the trading account, while an expected counterparty payment has not yet arrived. Plan costs, receipts and payments separately, then check how much cash will be available on each date. This lesson compares different trading-related activities and explains how to organise contracts, a budget and documents. Here, “small business” describes an approach to organising work; it does not determine whether business registration is required or how the activity is taxed. A delayed-payment example shows why receipt timing matters even when the reported result is positive.

A payment date and a period’s economic cost can differ
A trading-related activity may pay for access to a tool well before using all of it. Treating the whole payment as every month’s expense would duplicate it. Treating the unconsumed service as cash available for bills would create money that cannot be spent. Keep the cash payment and the chosen economic allocation in separate columns.
Our invented activity begins January with 1,500 PLN of operating cash and no other balances in this small worksheet. It pays 1,200 PLN at once for twelve equal months of tool access starting in January. For this exercise only, the economic usage cost is allocated evenly at 100 PLN per month. The contract is assumed non-refundable; unused access cannot be converted back into cash.
This is a management worksheet convention, not a determination of statutory accounting, tax deduction, VAT or business-registration duties. January’s service receipt of 500 PLN is earned and received in that month under the supplied facts. Cash operating costs are 200 PLN in January and 200 PLN in February. February has no receipt. No other cash flows, taxes or financing are modeled.
Reconcile January in the cash and economic columns
| Measure | Calculation | Result |
|---|---|---|
| Closing cash | 1,500 + 500 − 1,200 − 200 | 600 |
| Economic result for January | 500 − 100 − 200 | +200 |
| Unused service allocation after January | 1,200 − 100 | 1,100 |
Cash falls to 600 PLN because the annual payment happens now. January’s economic result is +200 PLN under the explicitly even allocation. The remaining 1,100 PLN describes service assigned to later periods; it is not another bank balance, receivable for a refund or money available to pay a supplier.
These two records reconcile: closing cash 600 plus unconsumed service allocation 1,100 equals 1,700 PLN in the worksheet, which is the initial 1,500 plus January’s 200 result. This arithmetic does not establish the resale value, legal ownership classification or recoverable value of a real software contract.
Carry the prepayment forward without paying it again
February starts with the actual 600 PLN cash. With no receipt and 200 PLN of cash operating costs, closing cash becomes 400 PLN. Another 100 PLN of service is consumed under our allocation, leaving 1,000 PLN for later periods. February’s economic result is 0 − 100 − 200 = −300 PLN.
Across both months, the economic result is 200 − 300 = −100 PLN. Cash can be checked directly as 1,500 + 500 − 1,200 − 200 − 200 = 400 PLN. Cash 400 plus remaining service allocation 1,000 equals 1,400 PLN, consistent with initial resources reduced by the 100 PLN combined economic loss.
Do not deduct the annual 1,200 PLN again in February’s cash ledger. Equally, do not forget the stated monthly usage when assessing economic costs. A repeated annual renewal later would be a new future payment to schedule; this exercise contains only the initial contract.
Use spendable cash for commitments and other evidence for classification
At February’s end, the next cash bill can use only the money actually available, subject to any other restrictions. The remaining service allocation cannot fund it under our non-refundable assumption. If an actual contract provides a refund or transfer right, record its conditions and confirmed cash timing separately rather than assuming immediate access to the face amount.
Keep the contract, payment confirmation, access period, allocation method and monthly usage record together. Show unknown taxes or contributions as items requiring determination, not as confirmed zero liabilities. Their omission from this narrow exercise is a scope limit, not a rule for a real activity.
The detailed lesson below compares own-account trading, services, companies and programme payments. This small prepayment case adds a practical bookkeeping distinction to that work: one cash payment, several periods of service use and no automatic source of money for the next bill. A transparent operating model can explain the difference without choosing a legal form or promising business profitability.
Three exercises with worked answers
The exercise data are hypothetical. Choose an answer, then check the calculation.
From a prepaid tool to the full operating model
Keep cash dates, economic allocation and legal or tax classification separate while reading the activity models and budget bridges below.
1. Start with the activity model
Write one sentence: what you do, whose funds you use, for whom, and on what basis you receive money. Only then can you list the documents, expenses and obligations. One person may have several streams; record each separately.
| Model | Possible source of money | Capital and dependency | Starting document |
|---|---|---|---|
| Trading your own account | Withdrawal of available broker-held funds, potentially including profit and returned capital | You risk your own money; access depends on positions, settlement and broker processing, among other factors | Account agreement, transaction history and withdrawal terms |
| Analytical, technical or educational service | Client payment for an agreed service | You fund delivery and the wait for payment, and owe obligations to the client | Service scope, acceptance, payment deadline and liability terms |
| Employment or contracting at an institution deploying its own capital | Contractual compensation and any variable component | The institution's mandate and limits; its P/L is not your pay | Contract, compensation rules, mandate and confidentiality obligations |
| Commercial prop programme | Operator reward after programme conditions are met | Fees and payout conditions; the account may be simulated | Agreement with a named entity and the rules version |
A simulated account's nominal limit is neither your asset nor a loan you can freely spend. Likewise, AUM—assets under management in the relevant model—is not the manager's revenue. Do not finance costs based solely on the displayed account size.
2. Your own account and layers of results
In Poland, PIT-38 covers specified capital income, including income from derivative financial instruments. It is not, however, a “trader's legal structure”. Article 30b(4) of the Polish Personal Income Tax Act excludes that article's regime where the specified transactions occur in the course of business. Do not classify activity solely by broker name, profit amount or trading frequency.[1]
First reconstruct performance in the account currency using 16.5. Track record. Then add activity costs absent from the statement: data, software, equipment or tax-filing support. These expenses exist economically even when not tax-deductible. Having no registered Polish sole proprietorship (JDG) does not mean operating without costs.
Depositing your own money transfers assets; it is not a trading cost. From the operating account's perspective, however, it is an outflow that reduces liquidity. Money transferred to a broker cannot simultaneously remain reserved for invoices. Likewise, an unrealised gain in equity is not money received in a bank account.
Taxable income requires separate rules for recognising revenue, costs and currency conversion. The Polish Ministry of Finance's 2025 PIT-38 brochure distinguishes the conversion of revenue, costs, expenditure and tax; one exchange rate applied to annual P/L cannot replace those rules.[2] Section 14 covers tax and record-keeping details.
3. Services and business registration
Selling a service requires defining what the client buys: a report, code, workshop or other deliverable. Describe the result, delivery date, acceptance process, revisions and termination terms. The economic assessment also includes preparation time, client communication and complaint handling.
A request for an invoice is not, by itself, a test of whether Polish JDG registration is required. The Ministry of Finance also describes invoicing for unregistered activity, available subject to separate conditions.[3] Applicable law and circumstances determine whether an activity constitutes a business; the absence of an invoice request does not remove a registration obligation that has arisen.
Do not choose tax treatment before identifying the activities, income source and permissible options. A Polish PKD code describes activity in a register; it does not itself classify the service or confirm a tax rate. A tax uncertainty can be submitted for an individual ruling with a precise statement of facts. This is neither mandatory for every programme nor a resolution of every legal obligation.[4]
Services also have a regulatory boundary. Making decisions in a client's account and giving personalised recommendations are not simply add-ons to selling educational material. Assess the activities before starting them; the label “education” and having a business do not replace required authorisations.[5]
4. Company finances and the owner's money
When considering a company, separate its finances from the owner's money. Company profit, cash in its bank account and the amount lawfully distributable to the owner are three different figures. Model the basis and date of each payment rather than assuming all profits can be taken monthly.
Compare structures for the same activity, period, costs and payout method. Do not compare profit from your own CFDs with service revenue and then declare a tax winner. Check formation and administration costs, reporting duties, specific individuals' liability, financing and closure costs. Not every amount paid when creating an entity is a definitive expense: contributed company capital is a separate category.
5. Co-owners and liability
With co-owners, add who supplies funds, bears losses, makes decisions and may request payment. Agree a co-owner's exit procedure and what happens to the activity during a dispute. These are real operating conditions that comparing tax rates alone cannot replace.
This article does not choose a Polish general partnership, limited partnership or company for an unknown ownership arrangement. Do not treat shares or a loan agreement as an automatic way around rules on other people's funds. Describe activities and responsibilities before analysing the appropriate structure.
6. Prop programmes: contract, document and payment
FTMO describes its accounts as simulated and the possibility of real rewards dependent on performance and programme terms.[6] This is one specific model, not every entity using “prop”. For your contract, establish whether transactions are real, who enters them and what the operator pays for.
Keep a payout register in four states: simulation result → expected amount → confirmed receivable → cash received. Do not jump between them because a “request payout” button exists. Record when conditions were met, acceptance, the due date and receipt. If further assessment is required, show it as a condition.
| Document | What to record | Why |
|---|---|---|
| Contract and rules | Entity, country, version, date, account type, fees and change provisions | Identify the relationship and applicable scope |
| Period report | Simulation or account result, included costs, participant's share | Separate the displayed result from the reward amount |
| Settlement confirmation | Accepted amount, outstanding conditions and deadline | Assess whether there is a receivable or only an expectation |
| Sales document, where appropriate | Description of the actual service and required details | Documentation suitable for the established relationship, not an automatic JDG invoice |
| Receipt confirmation | Date, currency, amount received, deductions and exchange rate | Reconcile cash with the operator's settlement |
The word “payout” alone does not determine the Polish tax category. A foreign contract cannot set Polish PIT or VAT rates or the basis of social insurance in place of Polish law. Do not apply someone else's ruling to a different contract. In filing instructions, separately record the service classification, revenue timing, documentation, currency, taxes and contributions; do not assume universal PIT-38, PIT-36 or lump-sum taxation for every programme.
If an invoice is appropriate, check record-keeping and issuance requirements, including current rules for Poland's KSeF e-invoicing system. For a cross-border relationship, establish the customer's status and place of supply. “Outside Polish VAT”, “exempt” and “zero-rated” are not interchangeable. This article does not assign a rate to an unspecified service.
These are uses of funds, not a requirement to open four bank accounts. A simulated programme limit is not your capital, and some models do not use every category.
7. Operating budget and the bridge to cash
Classify costs along three independent dimensions: fixed or variable, one-off or recurring, and cash or non-cash. An annual subscription may be allocated to successive months even though cash leaves on one date. Equipment use reduces the economic result but is not another transfer after the purchase was paid.
The register below is a template to complete, not a service price list or tax-deductibility table. Replace dates with your contractual terms. Keep the amount, currency, frequency, document and person responsible for review in every entry.
| Receipt / cost | Source / recipient | Timing | Nature | Dependency | Document | No receipt and response |
|---|---|---|---|---|---|---|
| Programme reward | Contracting operator | Due date and actual receipt date separately | Variable; receivable before receipt, then cash | Conditions assessment and payment by one operator | Contract, acceptance, transfer | Delay: do not plan spending dependent on unreceived money. |
| Tools, data, VPS | Providers | Subscription and notice periods | Fixed, recurring; cash expense on payment | Service availability and export capability | Contract, invoice | Cost continues; review need and a cheaper scope before renewal. |
| Programme fee | Operator | Before starting or renewing | Variable cash expense, even with zero performance | The same entity as the future payer | Purchase confirmation and refund terms | Set a spending limit beforehand; a new attempt is a new cost. |
| Accounting and filing support | Accountant / adviser | Contractual dates | Fixed or per assignment, cash | Data completeness and deadlines | Service scope and payment document | Include work still required when there are no receipts. |
| Equipment use | Internal calculation | Monthly | Non-cash economic cost | Assumed useful life | Calculation and purchase document | Do not deduct the purchase again from the month's cash flow. |
| Taxes and contributions | Relevant authority | Established obligation | Separate layer; amount and date require calculation | Legal model, income and other insurance grounds | Calculation, return, payment confirmation | No receipt does not automatically mean no liability. |
| Deposit with a broker | Your own account | Transfer date | Asset transfer, not cost; operating-account outflow | Availability of a return withdrawal | Transfer confirmation | Reduce the operating reserve by the actual transfer. |
A profitable month, but too little cash when payment is due
Synthetic example—not historical performance or a tax calculation. Assume a notional simulated programme settled in PLN (Polish złoty). March's +PLN 6,000 result is already after simulated transaction costs. The contract awards an 80% share, and all conditions were fulfilled and confirmed on 31 March: the receivable is PLN 4,800, due on 14 April. The 80% share and deadline are example assumptions, not a particular firm's offer.
PLN 900 was paid in March for tools and support. Previously purchased equipment is assigned an economic usage cost of PLN 300 monthly; we are not determining tax depreciation. Operating cash on 1 March is PLN 1,500. Separately, assume tax and contribution liabilities established at March-end: PLN 700 in contributions due on 20 April and PLN 500 in tax due the same day. In the model, they arise in March and are allocated to that month's result; their opening balance was zero. These are schedule parameters, not a tax rate applied to P/L. There are no other receivables, arrears, expenses or capital injections.
| March layer | Calculation | Result |
|---|---|---|
| Net simulation result | Programme report value | +PLN 6,000 |
| Participant's receivable | 6,000 × 80% | +PLN 4,800 |
| Activity result before taxes and contributions | 4,800 − 900 tools − 300 equipment use | +PLN 3,600 |
| Result after assumed contributions and tax | 3,600 − 700 − 500 | +PLN 2,400 |
| March cash flow | 2,400 + 300 non-cash cost − 4,800 receivables increase + 1,200 unpaid liabilities | −PLN 900 |
| Cash on 31 March | 1,500 − 900 | PLN 600 |
A second check gives the same answer: March receipts were PLN 0 and payments PLN 900, so cash fell by PLN 900. Transaction costs already included in the programme result were not deducted again. Only the PLN 4,800 share is recognised as the participant's economic revenue; the full PLN 6,000 is not their receivable.
| Date | Receipt on time | No receipt by 20 April |
|---|---|---|
| 31 March | PLN 600 cash | PLN 600 cash |
| 14 April | 600 + 4,800 = PLN 5,400 | 600 + 0 = PLN 600 |
| 20 April—700 + 500 due | 5,400 − 1,200 = PLN 4,200 after payment | PLN 1,200 needed, PLN 600 available: PLN 600 shortfall |
With timely payment, cash exceeds the initial PLN 1,500 by PLN 2,700: the PLN 2,400 result plus PLN 300 of non-cash equipment use. With delayed payment, a positive result cannot settle all liabilities. The model stops at the shortfall; we do not invent a negative account balance or an unassumed loan. Late receipt alone does not cancel the receivable or tax.
The operational decision from these data: before starting another paid cycle, cover the identified shortfall from a previously identified operating reserve or reduce cancellable future expenses. The model does not automatically fund essential obligations by increasing risk. In practice, add April's costs, other deadlines and a longer period without payouts; they are explicitly omitted here to illustrate one period's mechanism.
If payout conditions had not been met on 31 March, PLN 4,800 would remain an expectation, not a confirmed receivable. The economic result would also change: without it, with the same PLN 900 + PLN 300 costs, it would be −PLN 1,200 before taxes and contributions. Those liabilities must be reassessed for that separate situation; do not carry over the previous scenario's tax unchecked.
Synthetic model. PLN 4,800 is due on 14 April. Cash cost 900, equipment use 300 and liabilities 1,200 are separate; the liabilities are assumptions, not tax rates. Do not add these layers together.
8. Scheduling taxes and contributions
Schedule taxes under the applicable model and obligation dates, and contributions according to the grounds for insurance. Business revenue may be due before payment; statutory rules also provide exceptions and special methods. A delayed transfer does not automatically postpone recognition.[1] Do not label a result “net spendable cash” if its classification or a known liability is missing.
Polish contributions do not depend solely on the label “JDG”. Other insurance grounds, employment, relief eligibility and periods of activity may matter. ZUS, Poland's social insurance institution, explains overlapping insurance grounds separately. For example, with an employment contract guaranteeing at least the minimum wage, mandatory social insurance in the described overlap arises from employment. This is not automatic exemption from every charge, including health insurance.[7]
Each obligation needs four spreadsheet fields: basis of calculation, amount, due date and funding source. Enter “to be established”, not zero, for an unknown amount. A reserve for a future payment is not an already paid expense. Once payment occurs, reduce the reserve; do not deduct the same amount again from free cash.
Two versions of the same example, excluding other April costs and borrowing. In the delayed-payment case, the model stops before payment, not after a hypothetical negative bank balance.
9. Dependencies, switching and exit costs
Check what happens if one provider is lost: the payout operator, broker, data provider, hosting service or sales channel. Multiple accounts with entities relying on the same supplier may not diversify risk. A second paid programme creates another cost and does not guarantee a receipt on the same date.
For each dependency, record export options, notice periods, refund rules and replacement costs. Where a counterparty can change terms, establish which changes the contract permits and when they take effect; do not assume unlimited unilateral changes. A dated copy of the rules helps establish the relationship's terms but does not resolve a dispute by itself.
When comparing a change of structure or a foreign arrangement, request a calculation from profit to funds actually available to the owner after costs and all applicable charges. Residence, operating location, distribution method and closure are analytical inputs. A foreign address or lower nominal rate alone does not determine savings. Without these data, do not quote a capital threshold above which a structure supposedly pays.
Exit costs include remaining contractual fees, settlements, archiving and work to close obligations. Ending sales or stopping trading does not automatically cancel earlier receivables and payments. Legal and tax procedures depend on the specific structure.
10. Reviewing the model and the next decision
Review before renewing a material contract and after receipt conditions change. A monthly review is a useful organisational rhythm, not a professional standard. Liquidity depends on liability dates, so action may be needed sooner.
| Observation | What to check | Possible decision |
|---|---|---|
| Positive result, no cash | Receivables, payout conditions and upcoming deadlines | Pause new discretionary spending; recalculate the schedule |
| Receipts do not cover costs | Trial period, full cost and remaining budget limit | Reduce scope, choose cheaper tools or end the model |
| Performance exists only in simulation | Whether and when reward entitlement arises | Do not fund obligations from an expectation alone |
| A counterparty requests a different document | Legal relationship and actual documentation obligation | Establish the correct procedure, rather than automatically changing structure |
| The plan requires using household reserves | Whether the operating budget has its own funding | Reduce scale or pause; reassess household finances separately |
Write your criterion before the next expense, for example: “I will not renew the programme if, after reserving known payments and closure costs, insufficient money remains for the new fee.” This is a budget rule under assumed data, not a profitability guarantee. Fees already paid are not a reason to buy another attempt.
Now complete the register for one model and check the next payment deadline assuming zero receipts. Use amounts from contracts, confirmations and your budget; neither increased risk nor business registration is needed to do the calculation. Calculate the household budget and employment-change scenarios separately in 16.8.
Frequently asked questions
Does profitable trading require registering a Polish sole proprietorship?
Does every invoice require entry in Poland's CEIDG business register?
Why does positive P/L not cover the bills?
Can I deduct all tools for tax purposes?
Are all prop-programme payouts taxed the same way?
Can the operating reserve also be trading capital?
Sources and scope of use
- Polish Personal Income Tax Act—consolidated text, Journal of Laws 2026, item 592, Articles 14 and 30b(4). Scope: revenue due and exclusion from the Article 30b regime for specified business transactions. Reflects the legal position on 1 April 2026; does not determine the reader's particular contract.
- Polish Ministry of Finance—2025 PIT-38 brochure: return scope and foreign-currency conversion. A 2025 filing document, not a forecast of future liabilities.
- Polish Ministry of Finance—Unregistered activity, updated 26 May 2026. Scope: its separate eligibility conditions and invoicing duties.
- Gov.pl—Obtain an individual tax ruling. Scope: applying about a described factual situation or future event.
- UKNF—Provision of investment advisory services by investment firms. Scope: distinguishing advice, recommendations and information.
- FTMO—How It Works. Scope: simulated environments and rewards under programme terms. The 80% model and example dates are separate editorial assumptions.
- ZUS—Overlapping grounds for social insurance. Scope: other insurance grounds, including employment guaranteeing the minimum wage.
Sources accessed on 8 September 2026; Polish legal sources are in Polish. Examples are operating models with disclosed assumptions, not records of actual income or personalised tax calculations.