Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expense Flow Re-Design Project #2394

Open
piamancini opened this issue Sep 4, 2019 · 46 comments
Open

Expense Flow Re-Design Project #2394

piamancini opened this issue Sep 4, 2019 · 46 comments
Assignees
Labels

Comments

@piamancini
Copy link
Contributor

@piamancini piamancini commented Sep 4, 2019

Expense flow re-design

Project owner: @alanna (plus @piamancini )

Success metrics:

  • More expenses filed
  • Less support requests
  • Less host admin time spent
  • Way fewer issues with invoices (fewer expense comments)
  • Use of the new features (ex batch expenses)

Specs

Includes all issues tagged expenses and it closes #1326

Timeframe: ideally starting implementation by end of Oct

Roadmap

Current workflow

s_E48E182FD63A8A447F657D2745DC041586A26476C1F7A83221710910A27D1E66_1562194109646_Board+1

EPICS related user issues for context

@lindatalu @Memo-Es @cuiki

Batch uploads: #1324
Submit expense in expense currency: #101 and #477
Choose payout method: #1217
Generate the invoice when submitting the expense #1167
Update expense status and expense status metadata #1071 (comment)
and #705
Clarify privacy of attachment #1222

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Sep 17, 2019

We have created some Balsamiq mockups to show the improved submit expense flow.

view them here

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Sep 17, 2019

@lindatalu

This comment has been minimized.

Copy link

@lindatalu lindatalu commented Sep 26, 2019

Here under the expense flow for: core contributor, fiscal host and user submitting an expense:
@alanna would you mind to check them and give us feedback.
After the call the fiscal host flow has been updated
User submitting an expense.pdf
Core contribitor submitting an expense.pdf
Fiscal host submitting an expense.pdf

@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Sep 27, 2019

@lindatalu we are missing the create invoice and save template in the flow.

@lindatalu

This comment has been minimized.

Copy link

@lindatalu lindatalu commented Sep 27, 2019

@lindatalu we are missing the create invoice and save template in the flow.

@raulgrafico will update the flow on Monday, when he finished I will update the files

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Oct 11, 2019

This is the link to the documentation of the expense flow design:
http://bit.ly/ocd_expenseflow_docs

And the figma file that contains the wireframes:
http://bit.ly/ocd_expenseflow_wireframes

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Oct 12, 2019

@Memo-Es are you seeking feedback at this stage? For me the Figma is "view only" so I can't leave comments there. Should I wait until our next meeting?

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Oct 12, 2019

@alanna I linked where we are keeping our internal documentation.
We prefer to handle feedback here or inside the paper doc. Anyway, yes, the next step was scheduling a call with you to take a look at it and then talking with the dev team. Let's plan the meeting via Slack, ok?

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Oct 17, 2019

Hello folks,
I share with you the updates on the expense flow low-res wireframing process:

Link to the general flow prototype (navigation)

Link to the general navigation of the flow (canvas)

  • The form-filling flow is the first thing that we would like to focus on at this point, in the previous general flow appears in a "full" version; but I personally think that it should be more like small, condensed pieces of information to fill. I think it's a clever idea from @alanna to make it less heavy. Here is the link. (Just for the reimburse for the moment)

A couple of questions for the dev team start to arise at this point...

  1. How are we dealing with the "Save as template" feature? Can you save every different expense as a template? If is so... where do you "storage" them? And, how you decide which one to use when starting the flow?

  2. How are we going to incorporate taxes like VAT?

We will continue working on the flow today for a formal presentation of the V2 on Friday's demo.
@alanna @piamancini @Betree

@Betree

This comment has been minimized.

Copy link
Member

@Betree Betree commented Oct 17, 2019

How are we dealing with the "Save as template" feature?

We haven't wrote any specs for this feature yet.

Can you save every different expense as a template?

We could, tho I think that saving an expense as a template should be an opt-in. For example I don't need to save my train ticket to Madrid expense as a template. This is mostly useful for recurring expenses.

If is so... where do you "storage" them?

This will depend on what's designed, but it will probably be stored server-side in the user or collective settings.

And, how you decide which one to use when starting the flow?

We need a component to pick them, ideally on the same form so that you can easily switch between templates.

How are we going to incorporate taxes like VAT?

@xdamman may give a more complete answer but from what was specified in #1552 we would need:

  • A "tax picker", defaults to "No tax", would only have one option for now: VAT
  • If VAT is selected, amount should be without tax and we should add a "VAT amount" input

Feedback on general flow

  • One thing we learned from the existing flow is that users want to be redirected to their expense after it's created. Rather than showing a button See it in "Collective name" expense feed, I'd redirect to the page for this expense. See #2109

Feedback on the canvas

  • In Payout method options, we'll need to add more details (paypal email, IBAN number). Users may have multiple PayPal emails, or multiple bank accounts.

image

@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Oct 17, 2019

This is mostly useful for recurring expenses.

I think this would be useful for invoices as well as recurring expenses.

We need a component to pick them, ideally on the same form so that you can easily switch between templates.

We have something like it (it's not ideal because you can't easily move between templates) for events. Check it out --> create an event on staging

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Oct 17, 2019

I can't get figma to load; I just get this error face. @Memo-Es let's go over the details in our meeting today and then I can respond.

Screen Shot 2019-10-18 at 10 15 02 AM

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Oct 19, 2019

Wireframe update: Forms

Today we presented the low-resolution wireframes of the forms in the expense flow (Receipt and invoice), the intention of these prototypes is to collect all the details about what we need to consider in this phase and how is represented in a rough interface approach.

Receipt form: 👉 Prototype

Single expense → Batch mode → Select payout option → Expense summary →
Single expense Batch expense Select payout option Expense summary - Receipt

Invoice form 👉Prototype

Submit your invoice → Select payout option → Expense summary →
Expense summary - Invoice

During the feedback section, we talked about giving different treatment to the tax and privacy statements and working on the layout.

Quick update after feedback

Submit your invoice Upload receipt
Invoice submission Receipt upload

Next steps

We will take these form wireframes to the next detail level (High-res wireframes) and in a parallel way zooming into another part of the expense flow and design low-res wireframes, gathering feedback and information from the PO's and dev team

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Oct 21, 2019

Looking good! Some notes....

Receipt expense summary

  • How do notes work with batches? Will it add a copy of the note to each expense? I wonder if notes should be a per-expense thing instead of a per-batch thing.

Invoice expense summary

  • We decided there would be no batch option for invoices, so showing multiple expenses summarized here doesn't make sense.

Submit your invoice

  • Add 'payee name' to this screen. Often they need to specify their company name or their legal name here, which might be different to their profile name. The basic required data for an invoice is What it is for (description), amount to be paid, name of person or company to be paid (missing), and physical address.
@aunnop739

This comment was marked as off-topic.

Copy link

@aunnop739 aunnop739 commented Oct 21, 2019

@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Oct 21, 2019

We decided there would be no batch option for invoices, so showing multiple expenses summarized here doesn't make sense.

+1 @Memo-Es let us know if there are any questions here

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Oct 22, 2019

We decided there would be no batch option for invoices, so showing multiple expenses summarized here doesn't make sense.

Just updated in the comment
Yes, sorry. I uploaded the same image for both but it was considered 👍🏽

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Oct 24, 2019

Update:

👉Prototype

How do notes work with batches? Will it add a copy of the note to each expense? I wonder if notes should be a per-expense thing instead of a per-batch thing.

Batch summary → Expand detail → Add notes →
Expense form - Summary Expense form - Summary - Expanded Expense form - Summary - Notes
@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Oct 24, 2019

Thank you @Memo-Es! Great progress.

Page 9: We'll need to redesign that page so we can show all receipts in a batch as well as the private / public comments.

Page 10: Why do we have two sets of private and public comments?

Templates: Where in the create receipt process are we allowing people to choose from existing expense templates?

Where are we storing those templates? In the user settings?

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Oct 28, 2019

Update

This is the last update of the expense flow presented on Friday, October 24:

Submission to CC's - Receipts Submission to CC's - Invoices
Submission to CC's - Receipts Submission to CC's - Invoices

Next steps:

Forms

  • Solving the "Templates" design
  • Recurrent expenses

Approval rejection

  • Core contributors
  • Fiscal hosts
@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Oct 28, 2019

@Memo-Es it's looking great!
I saw the conversation you had about tags with Xavier. It's a fair point. Maybe we can do a view with tags per expense. Maybe smaller in size so we can fit them in?

I still think comments should be batch only.

Solving the "Templates" design
Recurrent expenses

Do you need something from us here?

@Betree

This comment has been minimized.

Copy link
Member

@Betree Betree commented Oct 30, 2019

Looking great! Maybe we should better surface the payout method on the confirmation page. It's a very important information that you want to encourage users to double/triple-check (because they can have a typo in their PayPal email for example).

image

@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Oct 30, 2019

@Betree, great idea

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Nov 1, 2019

Had a meeting with the designers today and discussed a couple issues.

  1. Where did the requirement for templates come from? It's not in the specs.

@piamancini I see you made a comment about including it above, but I don't really understand what the purpose is. When will Collectives use it? Do we have some examples of real life expenses where having a template will improve the experience? Personally I think we should leave templates out, because it's unnecessary complexity. Templates only are the description and the amount, which is such a small amount if info to put in. If someone has 10x similar receipts, they are likely to use the batch function instead.

  1. Recurring expenses. We made an explicit decision not to include this in V1. The designers have thought a bit about where it could fit in, but I reiterated to them that we don't want to design for that right now. We can take it on in a future iteration if there is a clear need.

I think it's important we stick to what's in the specs and not have scope creep for this project.

@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Nov 1, 2019

@alanna The templates are the invoices on the fly. It's how we save the information that hosts need contributors to add to the invoice. It's been in the specs from the beginning. See below a screenshot of the specs where it states this.

Screen Shot 2019-11-01 at 11 12 07 AM

Do we have some examples of real life expenses where having a template will improve the experience?

Templates are for invoices, not expenses. It's a separate path.

Recurring expenses. We made an explicit decision not to include this in V1

I think that if we are saving a template for the invoice, we are laying down the groundwork for saving the info for a recurring expense. Even if we don't build it now in figma, thinking about where it can go will save time in the future.

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Nov 4, 2019

Ah ok I think I see the confusion @piamancini - the designers were applying templates to receipts not invoices. This is why it didn't make sense to me.

@Memo-Es please see above clarification from @piamancini - we are removing templates from receipt expenses and only enabling saved information for invoices, as we've discussed.

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Nov 13, 2019

Update - Expense feed wireframes

@alanna

Expense feed Expense - Invoice Expense - Receipt
→ Latest expenses → Expense - invoice → Expense - receipt
@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Nov 14, 2019

Thanks @Memo-Es - we can discuss at the meeting tomorrow. For now, here's some notes.

  • Can you to filter expense feed by status (approved, paid, etc)?
  • If you click a tag will it filter by that tag?
  • I would like to visually seperate out status updates from comments. Right now status updates like "approved on [date]" are very hidden. They should be super obvious. This goes for "submitted by [person] on [date]" and "paid by [person] on [date]" etc.
  • I can see the approve button but where is the reject button? It's important to keep in mind all the possible actions that can appear: approve, reject, pay with paypal, pay manually, unapprove, unpay, etc.
  • What is an "expense follower"? The "follow" function is not in the spec so I think we should leave it out.
  • Admins should be able to add/edit tags but I don't see those options.
  • Having the "submit expense" button appear on a page where we are asking users to take actions on a specific expense could be confusing. Like instead of clicking "approve" could they click "submit expense" by mistake?
  • I can see the edit option for the individual receipt expenses, but I don't see how to edit the invoice expense, or how to edit the receipt batch as a whole.
  • Instead of saying "fiscal host" let's say "payer" (which goes with "payee" as the complement), and list the Collective name first, then the fiscal host name and info.
  • What happens if you click "request changes"? I assume it will basically just post a comment on the expense?
  • We should clarify clearly which data on this screen is public and which is private. For example, if someone has chosen a bank transfer, their bank details will show here under "payout details", but this will only be visible to them and the admins. We need to find a way to communicate and reassure people about that, because currently people get very concerned that this data is public.
@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Nov 14, 2019

Can you to filter expense feed by status (approved, paid, etc)?
We should be able to.

I think ready to pay should always be floated up first followed by pending. This will prevent us going down the feed to find old pending expenses.

Please remove the XX days ago, it's always very confusing. Let's always have the exact date of submission.

I would like to visually seperate out status updates from comments. Right now status updates like "approved on [date]" are very hidden. They should be super obvious. This goes for "submitted by [person] on [date]" and "paid by [person] on [date]" etc.

Where do you think are hidden? They are quite obvious on the feed, image 1. Is that what are are referring to?

I can see the approve button but where is the reject button?

+1

We should clarify clearly which data on this screen is public and which is private.

That is the lock item on the comments.

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Nov 14, 2019

I think ready to pay should always be floated up first followed by pending. This will prevent us going down the feed to find old pending expenses.

I think this depends on which view we're talking about. If it's the budget section on the Collective page, chronological probably makes sense. If it's the admin view of the expense feed, then yes unresolved (pending, approved) expenses should be on top.

Re: status updates hidden....

They are quite obvious on the feed, image 1. Is that what are are referring to?

This is the only reference I see the the expense being approved in the comment thread. It's tiny. It should be its own line in the feed and super obvious, not hidden within another comment. You should be able to 'read' the expense's history through these status updates. They are just as if not more important than comments.

Screen Shot 2019-11-15 at 11 00 01 AM

Privacy:

That is the lock item on the comments.

This might work for comments, but I'm talking about data like the user's address, paypal email, bank transfer info, etc.

Screen Shot 2019-11-15 at 11 02 25 AM

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Nov 22, 2019

To enable the designs that are being worked on, we need some specifications for the settings host admins can define for invoices and payouts.

@Memo-Es @piamancini I'm writing this here but let me know if I should make these seperate issues. Interested in your feedback about these topics. @alinamanko you might want to chime in too. FWIW my inclination is to go for the MVP+ options in both cases below.

Invoice details

Currently we have a field in settings for address and this is the natural place to draw the payer address details from to go on the invoice. However, to make sure we enable the correct info to show on invoices we might want to expand the options.

Option A: MVP

Keep the settings as is and just inform fiscal host admins that we will print whatever is in the address box under their organization name on invoices created by the system. If they want to include their tax number or other required details they can add it in this box.

Option B: MVP+

Add some extra boxes to the host settings info section to facilitate better data collection, such as tax ID number (required in some countries) and legal entity name (might be different than their host name). These would be optional because each host is a bit different.

Option C: Add invoice settings section

I think this would require implementing #2380 because host orgs really need seperate settings from sponsor orgs but currently we combine them. If we could have different settings specifically for hosts, we could add an "invoice details" section and move the billing details from the info section to there and expand the options.

Another aspect to this is how exporting system-created invoices for tax reporting will work. Currently hosts get a PDF that includes a list of expenses and their associated attachments. Going forward, there won't be a seperate attachment for system-created invoices, so we need to define what the report will contain. I will ask the accountants whether a spreadsheet with the required data is good enough or whether we need the system to output a one page documented formatted as an invoice for each expense. (This applies for invoices only - receipts will still be attachments and reporting for them will stay the same).

@xdamman it would be useful to understand what European hosts need in terms of the details exported with system-generated invoices.

Payout Methods

In the designs shown above, the user can select their desired payout method. These need to be defined by the fiscal host because it's the host who actually does the paying.

MVP

Keep the current options we have now, which are paypal and other. Paypal has an associated Paypal address and allows payment direct from the dashboard through the API. Other can mean anything but is generally used for bank transfers via ACH and Transferwise etc, and we expect users to give us those details in the private notes box.

I think we can do better than the status quo here. We especially want to save users' payout method details so they don't have to input them again for each expense they submit, and to do that we need to enable options. We also want to seperate out details specific to a payout method from the general notes boxes.

MVP+

Add a few more payout options that we know hosts use, with more specifically associated details, and allow host admins to toggle these on and off. Only ones they allow will show as options to expense submitters. I suggest these could be added to the "expenses" section in settings.

  • Paypal - payment email address
  • Bank Transfer - bank wire transfer details such as account number, SWIFT, IBAN, etc. I think this should be a free box because each country uses different details but everyone can understand "input your bank transfer instructions here".
  • Cheque - requires mailing address
  • Cash - for groups who meet up in person, etc.
  • Other - we could still enable this option with a free text box for details

Full control of options by admin

This would require more complexity but help host admins who currently spend time chasing expense submitters who request a payout method without meeting required criteria, or who want to use less common options and need to explain to user to choose "other" and what to put in the box.

This would mean host admins could define:

  • payment option name (could include local payment systems, Venmo, whatever they want)
  • required details (ex for ACH we need ABA and acct#, for EU they need IBAN, NZ only acct#, etc)
  • criteria - ex. bank transfers only available for expenses over a certain $ amount, etc
@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Nov 24, 2019

Update from accountants re: exporting system-generated invoices for tax reporting:

A spreadsheet with all the data for each expense be enough

So we don't need to generate formatted invoice documents for monthly reports. However, I assume we should still make these downloadable by the expense submitters?

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Nov 29, 2019

Update - Expense feed wireframes

@alanna

Expense feed Expense - Invoice Expense - Receipt Expense - Submitter view Expense - Outsider view
→ Latest expenses → Expense - invoice → Expense - receipt Submitter view Outsider view
@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Nov 29, 2019

Update - Admin view wireframes

@alanna

Latest expenses Expense - Invoice Expense - Receipt Reject with comment
→ Latest expenses → Expense - invoice → Expense - receipt Admin view - rejection comment
@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Nov 29, 2019

Thanks @Memo-Es!

Comments:

Expense - Invoice

How's the view before there are any attachment's added? Also for the URL (thank you for adding that btw), what's the view of the input field before there's anything?

Are we are missing the email views of the notifications?

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Dec 2, 2019

It's looking great @Memo-Es ! Getting really close now.

Privacy

I think we still need to improve how we're dealing with communicating and displaying confidential information.

  • Submitter view: There should be clear indication visually which data they see if private and which is public. Users are very concerned about posting their confidential info (understandable since it's bank details, email address, and private stuff). We get issues with this all the time. There should be visual separation between data that is public and data that's only visible because they are the submitter/admin and have permission to see it.
  • Outsider view: I think we can get rid of everything in the orange boxes, to really simplify it. Just have the payee, the Collective name, and the host name, along with the expense description and amount.

69842391-b7ceda00-1228-11ea-87bf-ec676a81813d

Expense - submitter view

  • add cancel option
    Right now 'reject' is often used when the submitter wants to cancel their expense because of an error or change of plans. Maybe we should show a "cancel" button to submitters where the "reject" button appears to admins? Sorry I should have put this in the spec earlier. We do need to offer submitters a way to cancel. It can follow the same functionality as 'reject' and offer them the option to put a reason comment.

Admin view

  • To clarify, the "admin view" wire frames are the fiscal host admin's view right? The Collective admin view will not include the payment action buttons.
  • We talked about the "other fees" box - what is this for? I have only ever put in payment processor fees in this context, but you were going to ask @xdamman if there was a reason for the other boxes. Unless there is a need for it, let's remove it.
  • Is it possible to reject an expense without typing in a comment?
@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Dec 10, 2019

@Memo-Es @raulgrafico Can you please post the latest wireframes here?
@Betree and @znarf have been looking at this for dev feedback and they aren't sure which one is the latest version.

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Dec 10, 2019

Interface update - Form / Receipts

@piamancini @alanna @Betree @znarf

Expense type → Expense info - Receipt → Upload receipt → 1st Batch upload → Upload receipt → 2nd Batch upload → Edit Receipt
00 → Expense type 01 → Expense info - Receipt 02 → Expense info - Upload receipt 02 → Expense info - Multiple receipts 02 → Expense info - Multiple receipts-1 03 → Expense receipt - Summary 03 → Expense receipt - Edit receipt
@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Dec 12, 2019

Figma isn't working for me, so I'm putting text changes here.

Screen Shot 2019-12-13 at 11 39 52 AM

1

Request payment from [Collective] for work you've done or to be reimbursed for purchases. Expenses will be processed for payment once approved by a Collective admin. Only the amount and description are public in the Collective's transparent budget—attachments, payment details, and other personal info is kept private.

2

Expense description

3

Upload receipt(s)
Get paid back for a purchase already made

4

Submit invoice
Charge for your time or get paid in advance

5

How do I get paid from a Collective?

Submit an expense and provide your payment information.

How are expenses approved?

Collective admins are notified when an expense is submitted and they can approve or reject it.

Is my private data made public?

No. Only the expense amount and description are public. Attachments, payment info, and other private data is only visible to you and the admins.

When will I get paid?

Payments are processed by the Collective's fiscal host, the organization that hold funds on their behalf. Many fiscal hosts pay expenses weekly, but each one is different.

More info

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Dec 12, 2019

Screen Shot 2019-12-13 at 12 30 17 PM

1

Upload receipt

2

Submit invoice

3

Tags

4

Upload one or multiple receipt(s)

5

Expenses will not be paid without a valid receipt

6

Amount

7

OR [ ] 100% of Collective balance ($x USD)

8

What does a valid receipt contain?

To be valid, a receipt must show: name of vendor, transaction date, description of goods or services, amount paid, and form of payment. Some countries also require a tax ID number or other info.

What if I don't have a receipt?

Expenses cannot be reimbursed without a receipt. If you don't have one, submit an invoice instead.

When will I be paid?

Once your expense has been approved by a Collective admin, it will be processed for payment by the fiscal host. Most pay expenses at least once a week.

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Dec 13, 2019

Screen Shot 2019-12-13 at 12 56 27 PM

1

Make it super clear that this section is private info

2

Total (tax inclusive)

Note: we are not adding any features for taxes as it's super complex. We're just saying if someone needs to include tax in their invoice total that's up to them.

3

Tags

4

Payout method

5

Remove this, it's not in the scope. If they want to add a URL they can do it as a comment.

6

Remove this - no attachment needed for invoice expenses. If they want to add an attachment they can do so in a comment.

7

Is my personal info public?

No, only you and the admins can see your address and payment info. Only the expense amount and description are public.

How can I save an invoice template?

If you'd like to save multiple payment templates for invoices (for example, paying you personally vs your company), enter the payee info and tick the 'save template' box. You'll be able to select from your saved templates next time you submit an invoice.

When will I be paid?

Once your expense has been approved by a Collective admin, it will be processed for payment by the fiscal host. Most pay expenses at least once a week.

Do I need to submit a tax form?

Some fiscal hosts require tax information from payees. If this is the case, you will receive communication from the fiscal host letting you know.

@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Dec 13, 2019

Screen Shot 2019-12-13 at 12 57 16 PM

Save your info for next time?
You can save your invoicing details as a template so you don't have to put them in every time. You can save multiple templates for different payees (e.g. yourself personally and your company).

[ ] Save as template Template name: [ e.g. Company XYZ or Firstname Lastname ]

Question: do templates save both payee details and payout method info, or are these treated separately? I thought they were seperate and you would choose your payee template for the name and address info, and the payout method for bank or paypal details.

@Memo-Es

This comment has been minimized.

Copy link

@Memo-Es Memo-Es commented Dec 14, 2019

Update - Forms prototype

This is the form prototype for receipts and invoices after the feedback round of today's demo. @alanna you can use this for the newsletter

Prototype in figma

Receipts

Expense type → Upload receipt → Single receipt → Batch 1 - Incomplete info → Batch 1 - complete info → Batch 2 - Edit → ← Batch 3 → Expense summary - Receipt
00 → Expense type 01 → Receipt upload 1st 02 → Receipt single 03 → Receipt batch 1 (Incomplete info) 03 → Receipt batch 1 (Complete info) 04 → Receipt batch 2 05 → Receipt batch (complete) 06 → Expense receipt - Summary (Receipt)

Invoices

Expense type → Invoice fill-out → Invoice details → Expense summary - Invoice
00 → Expense type 01 → Invoice 02 → Invoice 03 → Expense summary (Invoice)
@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Dec 15, 2019

Thanks @Memo-Es

A few comments...

  1. Please remove the "do you have an invoice already" thing. We don't need attachments for invoices anymore, and it will further complicate the design.

We are building this with the expectation that the user will put their details in the form, and we will need them to do so for exporting the data to accountants, etc, so uploading another invoice is redundant (even if they have generated one for their company or records already - that's their business and we do not need it). We can't have people putting essential info on invoice attachments when the host admins will be looking at the data in the payout info they put in the actual form, not on the attachment.

  1. Where has the save template functionality gone? I don't see it in these screenshots. Are we simplifying that to just save their previously entered info and basically just have one set of info per user instead of a list of saved templates? I am fine with that actually as most people do not need multiple templates, they just need the system to save the one version of their info.
@alanna

This comment has been minimized.

Copy link
Contributor

@alanna alanna commented Dec 15, 2019

I posted a seperate thread for user feedback that I'll link to from the newsletter: #2725

@piamancini

This comment has been minimized.

Copy link
Contributor Author

@piamancini piamancini commented Dec 16, 2019

@alanna

Please remove the "do you have an invoice already" thing. We don't need attachments for invoices anymore, and it will further complicate the design

We decided to still support this option, as there are people who will still want to send invoices they created. For example, Mexico has strict regulations of what their invoices need to have. So they will want to upload theirs.

It's like any vendor system, we create an invoice but still have our own that is uploaded, we our own accounting system that we want to make sure we keep.

Where has the save template functionality gone?

This is for now out of scope. This was designed for recurring expenses, but we are moving that to V2. There is no template to be saved. We'll just add the host information when we generate the invoice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.