> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/create-a-transaction.md). # Create a Transaction To create a transaction for the multisig to act upon first derive a PDA for the transaction. The transaction PDA is used to reference the account created, and will store some basic information about the transaction. In addition to the PDA, creating a transaction also requires and authority index. A complete example to create a new Transaction with the expected `transactionIndex` 
// fetch the multisig
const multisigAccount = await squadsProgram.account.ms.fetch(multisig);

// get the next expected transactionIndex
const transactionIndex = new anchor.BN(multisigAccount.transactionIndex + 1);

// get the transaction PDA
const transaction = await anchor.web3.PublicKey.findProgramAddress(
    anchor.utils.bytes.utf8.encode("squad"),
    multisig.toBuffer(),
    transactionIndex.toBuffer("le", 4), // or .toArrayLike(Buffer, "le", 4) 
    anchor.utils.bytes.utf8.encode("transaction")
);

// get the public key of the payer/creator
const creator = wallet.publicKey;

await program.methods.createTransaction(1) //using authorityIndex of 1
   .accounts({
       multisig,    // the multisig PDA
       transaction, // the transaction PDA
       creator // the creator/payer of the transaction acccount
    })
    .rpc();
After being created, the transaction will remain in a `Draft` status, until it is activated by the member key that created it. Refer to the [Transaction PDA section](/main/squads-legacy/development/pdas/transaction.md) for more information about deriving the transaction PDA and [the Authority section](/main/squads-legacy/development/authorities.md) for information about how authorities function within Squads. --- # 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://docs.squads.so/main/squads-legacy/development/anchor-idl/transactions/create-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.