How Bitcoin transactions work, for finance teams

A Bitcoin transaction is a signed instruction that spends bitcoin locked in earlier transactions and assigns it to new owners. Once it is included in a block and has enough blocks on top of it, it is final: there is no recall, no chargeback and no bank to call. For a finance team, understanding how Bitcoin transactions work is less about the technology and more about knowing where errors can happen and which controls stop them.

This article walks through a transaction from instruction to settlement, using terms a treasury team already knows.

How Bitcoin transactions work: the building blocks

A bank account is a single balance that goes up and down. Bitcoin does not work that way. Instead, the ledger records discrete pieces of value called unspent transaction outputs, or UTXOs.

Think of each UTXO as a banknote of an odd denomination. A wallet that "holds 12.4 BTC" may in fact control five separate outputs of different sizes. The balance a treasury dashboard shows is the sum of those pieces.

Every transaction has two sides:

• Inputs. The existing outputs being spent. Each must be spent in full.
• Outputs. The new pieces being created, each locked to an address.

Because inputs must be spent in full, most transactions create a change output that sends the remainder back to an address the sender controls. If a company spends a 10 BTC output to pay 3 BTC, the transaction creates a 3 BTC output to the recipient and roughly 7 BTC of change back to the company, less the fee.

The fee is not a separate line. It is the difference between total inputs and total outputs, and it goes to the miner who includes the transaction. We explain the pricing in how Bitcoin network fees work.

From instruction to signature

A transaction becomes valid when it is signed with the private key, or keys, that control each input. The signature proves authority without revealing the key itself. We cover the mechanics in public and private keys explained.

In a corporate setting, the signing step is where governance lives. A typical flow looks like this:

1. A treasury analyst prepares a transfer request with amount, destination and purpose.
2. The custody platform builds the unsigned transaction.
3. Approvers review and sign according to the agreed quorum.
4. The signed transaction is broadcast to the network.

Nothing in the network checks whether the payment was commercially sensible. If the signatures are valid and the inputs are unspent, the network accepts it.

Broadcast, mempool and confirmation

Once broadcast, the transaction travels between nodes and waits in each node's mempool, a holding area for valid but unconfirmed transactions. Miners choose which transactions to include in the next block, usually prioritising higher fees.

When a block containing the transaction is found, the transaction has one confirmation. Each further block adds another. Blocks arrive about every ten minutes on average, though the gap varies widely.

Confirmation thresholds are a policy decision. Many institutions treat six confirmations as final for large amounts, which takes about an hour on average.

What makes a Bitcoin transfer different from a wire

Finance teams used to payment systems should note four differences:

• Finality is absolute. A misdirected payment cannot be clawed back through the network. Recovery depends entirely on the recipient's goodwill or legal action against them.
• There is no name check. An address carries no beneficiary name. The network will pay any well-formed address.
• It runs 24/7. Transfers settle on weekends and holidays, which affects cut-offs and staffing. See 24/7 Bitcoin markets and treasury operations.
• The ledger is public. Anyone can see amounts and addresses, though not the legal owner. Privacy depends on address hygiene.

The controls that matter most

Most losses in corporate Bitcoin operations come from process failures, not from the network. The controls below address the common ones.

• Address whitelisting. Only pre-approved destination addresses can receive funds, and changes to the list require separate approval.
• Independent address verification. Confirm a new address through a second channel, such as a call-back to a known contact, not by email alone.
• Test transactions. Send a small amount first and confirm receipt before sending the balance.
• Character-by-character checks. Some malware swaps copied addresses. Check the full address, not only the first and last few characters.
• Confirmation policy. Define how many confirmations count as settled for receipts, by amount band.
• Reconciliation. Match on-chain transaction IDs to internal records and execution reports daily.

Before your first live transfer, write down who prepares, who approves and who verifies the destination, and require that these are three different people for any transfer above a set threshold.

Where transactions sit in the wider process

For a company buying Bitcoin through an OTC desk, the on-chain transaction is usually the final leg: the provider delivers bitcoin to the company's custody address after the cash leg is settled or simultaneously with it. How that sequencing works, and who bears risk in between, is covered in settlement and counterparty risk and pre-funding vs delivery versus payment.

The accounting follows the economic event. Network fees and the treatment of change outputs need to be reflected correctly in the ledger, which is why many teams agree the method with their auditors early. Companies should take their own accounting and tax advice on this.

How The Bitcoin World helps

We design the transaction workflow around your existing approval matrix: whitelisting, verification steps, confirmation thresholds and reconciliation. Execution, custody and settlement are carried out by licensed third-party institutions. Our role is to make sure the process is documented, tested and understood by everyone who signs. See our custody architecture work for more.