|
| 1 | +--- |
| 2 | +title: Filing process |
| 3 | +sidebar_position: 3 |
| 4 | +--- |
| 5 | + |
| 6 | +If you do not yet have access to expensify, please complete the |
| 7 | +[application process](/crowdfund/application) first. |
| 8 | + |
| 9 | +## Terminology |
| 10 | + |
| 11 | +### Report |
| 12 | + |
| 13 | +**A "report" is a claim for refund.** |
| 14 | + |
| 15 | +For a single event (e.g. a Local, a Conference, etc), exactly **ONE REPORT** |
| 16 | +should be filed. The report should be itemized - each individual expense should |
| 17 | +be entered as **separate receipts** within the **same report**. |
| 18 | + |
| 19 | +> [!DANGER] Do NOT combine multiple receipts into a single PDF - keep them |
| 20 | +> separate. |
| 21 | +
|
| 22 | +### Receipts |
| 23 | + |
| 24 | +**A "receipt" is a single scanned document from a vendor showing an amount paid |
| 25 | +related to a report.** |
| 26 | + |
| 27 | +Each report may have more than one receipt. |
| 28 | + |
| 29 | +The amounts in each receipt must match exactly the amount entered. |
| 30 | + |
| 31 | +An expense cannot be claimed without a receipt. |
| 32 | + |
| 33 | +## Creating a report |
| 34 | + |
| 35 | +Log in to Expensify. |
| 36 | + |
| 37 | +Create a basic report: |
| 38 | + |
| 39 | +- **Department**: LFX |
| 40 | + |
| 41 | +Then move on to adding expenses: |
| 42 | + |
| 43 | +## Adding expenses |
| 44 | + |
| 45 | +Each receipt should have its own expense entry (on the **same** report). |
| 46 | + |
| 47 | +Here's some guidance on the inputs: |
| 48 | + |
| 49 | +- **Currency**: match the currency of the receipt. |
| 50 | +- **Description**: The descriptions will be rendered publicly, but are |
| 51 | + truncated, thus please prefix them with the most important info, e.g.: |
| 52 | + - Report name: `(London) April 26 GraphQL Local` |
| 53 | + - Receipt name: `(London) Pizzas` |
| 54 | + - Receipt name: `(London) Drinks` |
| 55 | + - Receipt name: `(London) Stickers` |
| 56 | + - Report name: `(Ambassador) Amsterdam GraphQL Day` |
| 57 | + - Receipt name: `(Ambassador) Outbound travel` |
| 58 | + - Receipt name: `(Ambassador) 2 nights hotel stay` |
| 59 | + - Receipt name: `(Ambassador) Return travel` |
| 60 | + - Receipt name: `(Ambassador) Stickers` |
| 61 | +- **Project**: "graphql" (**NOT** "GraphiQL") |
| 62 | +- **Category**: whatever seems right to you. For flyers/stickers/swag use |
| 63 | + "Marketing". For GraphQL Locals if in doubt use "Meetups". |
| 64 | + |
| 65 | +## Submitting your request |
| 66 | + |
| 67 | +1. Go to Settings > Account > Wallet and make sure you have linked a bank |
| 68 | + account. |
| 69 | +2. Submit the report to LFX: |
| 70 | + - **CC**: be sure to include the list of email addresses you were given to CC |
| 71 | + during the application process, or request that list if you do not have it. |
| 72 | + - **Memo**: Same as description (e.g. "(Ambassador) Amsterdam GraphQL Day") |
| 73 | + |
| 74 | +## Getting paid |
| 75 | + |
| 76 | +Once a report is submitted, it will be validated by a member of the Linux |
| 77 | +Foundation team. Unless added to the CC explicitly, the GraphQL Foundation |
| 78 | +currently have no visibility into this process. |
| 79 | + |
| 80 | +Allow 30 days for payment to clear, longer in certain territories. If after 35 |
| 81 | +days still no updates, applicant should use the "support" feature (modal?) |
| 82 | +available from the report they have created through Expensify; this message will |
| 83 | +then route to an admin to figure out why it went wrong. The GraphQL Foundation |
| 84 | +can only offer limited help here, feel free to keep us in the loop but your |
| 85 | +support requests should go through expensify. |
0 commit comments