> For the complete documentation index, see [llms.txt](https://transactiontool.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://transactiontool.hedera.com/transactions/creating-a-transaction.md). # Creating a transaction In this guide, you'll learn how to create and sign a transaction within the application using your individual credentials. This flow is ideal for submitting transactions that require only your own signature (i.e., not part of a multi-signature organization workflow). {% hint style="info" %} **Note:** If you're creating a transaction on behalf of an organization, refer to the [Organization Transaction Guide](broken://pages/pDLX8zlNvEFKe4ZROAUy). {% endhint %} *** ### **Select Personal Mode** In the top-right dropdown menu, switch the mode from **Organization** to **Personal**.\ This ensures that the transaction will be created and signed only by you, outside of any multi-signature organization workflow. *** ### Navigate to the Transaction Tab * In the left-hand navigation menu, select on **Transaction**. *** ### Create a New Transaction * Select **Create New** from the main menu then Choose **Transaction.**

*** ### Choose a **Transaction Type** * For example, Choose **Account** and then select **Create Account**. * Each transaction type will display a different set of required fields.

*** ### **Fill in the Required Fields** Once you’ve selected the appropriate transaction type (in this case, **Account Create**), the form will display both **common** and **transaction-specific** fields. #### **Common Transaction Fields** These fields are available on every transaction type:

Field	Description	Required/Optional
Transaction Description	A text description of the transaction. Does not get published to the network Ledger and is private to you.	Optional
Nickname	A name for the transaction. Does not get published to the network Ledger and is private to you.	Optional
Payer ID	The ID of the account that will be charged the transaction fee for this transaction.	Required
Valid Start	The time the transaction should be executed by the selected network	Required
Transaction Memo	A short memo for the transaction that will be visible on the network ledger. Any information here is not private. 100 characters max.	Optional
Max Transaction Fee	The maximum amount of HBARs you're willing to pay for the transaction	Required

#### **Account Transaction Fields** These fields are specific to the **Account Create** transaction type. If you create a different transaction these fields may not apply.

Field	Description	Optional/Required
Key	The public key that will own this account and sign transactions for. This can be a simple key or complex key. This can be an ED25519 key and ECDSA key type. Learn how to create a complex key type <here>.	Required
Accept Staking Rewards	Whether or not this account should accept staking rewards if it were staked to a node.	Optional
Staking	The account can be staked to a node account ID or staking to another account. Select the method in which you would like to stake your account.	Optional
Receiver Signature Required	If enabled, this account would require to sign all transactions where this account is being transferred tokens.	Optional
Initial Balance	The starting balance of the account when it is created. The balance is transfererd from the transaction fee payer account into this account upon creation.	Optional
Max automatic token associations	Whether or not this account should recieve token airdrops. <Expand futher>	Optional
Account Memo	A text memo to attach to the account. 100 characters max. Warning: This information will be publicly available on a network explorer when the account is searched for by anyone.	Optional

### *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://transactiontool.hedera.com/transactions/creating-a-transaction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.