> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/expenses-and-getting-paid/submitting-expenses/nviting-a-third-party-to-submit-an-expense.md). # Inviting a third-party to submit an Expense {% hint style="info" %} Please note if an invitation isn't accepted within a month, it will expire. You will need to submit a new expense and invite the third party again. {% endhint %} It is also possible to draft an expense and send it to a third party to edit and submit an expense. You can send a drafted expense to an existing user of the platform or to someone else that is not on the platform yet. Inviting a third-party user or organization to submit an expense automatically creates a draft of the expense and emails the user so they can finalise any final details and submit it to the collective. Notice, although the invited user will pick who's going to be paid for the expense, the created expense will display you as the user who requested it: ![Jean-François requested an expense to Pia who submitted it in the name of Open Collective Inc, one of her organizations.](https://2931279126-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWSZizTt4ZC1UNDV89f%2F-MMHIQKAD1q0FsXxkz_1%2F-MMIEQTwSoSzZOD2rCQC%2Fimage.png?alt=media\&token=1afc611b-9178-4efc-b5bd-073ff83fa3ed) ### Inviting an existing user To invite an existing user, search for an existing user in the payee selection dropdown. After selecting the user, you'll be able to add a title to the expense, optional items, and a note to the recipient that will be sent in the email. ![](https://2931279126-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWSZizTt4ZC1UNDV89f%2F-MMHIQKAD1q0FsXxkz_1%2F-MMHX-AhyrrpMDljrAo4%2Fdeepin-screen-recorder_Select%20area_20201116162535.gif?alt=media\&token=a4d958cb-e07e-47c4-b0a4-27389f283ce6) The invited user will receive a notification by email containing a link with a key that will allow them to finish editing and submit the expense. ### Inviting a new user It is also possible to invite a user that does not have an account on the platform to submit an expense. To do that, simply select the option *Invite someone to submit an expense.* ![](https://2931279126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LWSZizTt4ZC1UNDV89f%2Fuploads%2FogbqIH9WMIiCNfDXF1I9%2FExpenses_SubmittingExpenses_Invitingnewuser_2022-05-28.png?alt=media\&token=a8f04667-d727-4a40-b793-fa0e390b00ef) Select either Personal Account or Organization Account (this will result in an Organisation profile in which that individual is the admin). Fill in their name and email address and Organisational information. ![](https://2931279126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LWSZizTt4ZC1UNDV89f%2Fuploads%2FCdtgEHVX3ANuA5OtjN9I%2FExpenses_Submittingexpenses_Personal%3Aorganisation_2022-05-28.gif?alt=media\&token=bdcaffb1-83f5-4b88-a94e-f3ae960ee3f1) Click next to get to the invoice details screen. You are now able to *add additional information about the expense.* Pre-fill whatever info you already have, then invite the payee to fill in the rest and confirm. This can make the whole process a lot easier! ![](https://2931279126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LWSZizTt4ZC1UNDV89f%2Fuploads%2FkuiXxLJTkdoLu2r7iOQg%2FExpenses_Submittingexpenses_invoicedetails_2022-05-28.png?alt=media\&token=b6d9aca8-5432-43d3-ace0-9ac30c5a7d0e) Click Send Invite. The payee will get an email saying "'Collective' wants to pay you" and they will be guided to put in their bank details and confirm the expense When the payee finishes editing the expense, the summary of the expense is displayed and they will be able to create their account and submit the expense in a single action. ![](https://2931279126-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWSZizTt4ZC1UNDV89f%2F-MMIF-GSEnl2mxRQPMD8%2F-MMIKNtQ6wg-HUlKLpkn%2Fimage.png?alt=media\&token=0408507e-5fd7-479e-95d8-2eb6a06ff5cd) After joining and submitting the edited expense, the expense now is saved in the platform and marked as *unverified* until the payee validates their email. After the payee validates their email, the expense is marked as pending and is displayed on the expenses page for the Collective's admins to approve (and you will get an email notification). ![](https://2931279126-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LWSZizTt4ZC1UNDV89f%2F-MMIF-GSEnl2mxRQPMD8%2F-MMILYi7AR6hCCO9MRGO%2Fimage.png?alt=media\&token=5c0b158d-3bf8-47be-9f28-dd0af737906c) Once the expense is there on the list, click "approve" on it --- # 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.opencollective.com/help/expenses-and-getting-paid/submitting-expenses/nviting-a-third-party-to-submit-an-expense.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.