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.

Sign up for GitHub

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

Jump to bottom

Expenses Policy #123

Open
nelsonic opened this issue Nov 26, 2016 · 5 comments
Open

Expenses Policy #123

nelsonic opened this issue Nov 26, 2016 · 5 comments
Assignees
@nelsonic
Labels
discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality finance help wanted If you can help make progress with this issue, please comment! priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished question A question needs to be answered before progress can be made on this issue

Comments

@nelsonic
Copy link
Member

nelsonic commented Nov 26, 2016 •
edited by ghost
Loading

As a company/team/organisation, we need to have a clear expenses policy
so that it's unambiguous what we can/can't spend "company" money on
and be 100% transparent with everyone (the community & HMRC...) 💸

This will require knowledge of what is an "allowable" expense for TAX purposes and clear categorisation of different types of expense.
@nelsonic nelsonic added discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! priority-1 Highest priority issue. This is costing us money every minute that passes. labels Nov 26, 2016
@nelsonic nelsonic mentioned this issue Nov 26, 2016
Open
5 tasks
@ghost ghost self-assigned this Feb 1, 2017
@ghost
Copy link

ghost commented Feb 1, 2017

Links to #192 and #125

@iteles iteles added priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished and removed priority-1 Highest priority issue. This is costing us money every minute that passes. labels Feb 12, 2017
@ghost
Copy link

ghost commented Feb 14, 2017

@iteles suggested using finance+expenses@dwyl.io for all company expense receipts in order to simplify email filtering. Agreed that this should be added to the policy.

@ghost
Copy link

ghost commented Feb 14, 2017

Mark to write up policy this week

@ghost ghost changed the title Expenses Policy? Expenses Policy Feb 14, 2017
@iteles iteles mentioned this issue May 15, 2017
Closed
@nelsonic
Copy link
Member Author

nelsonic commented Jun 5, 2017

https://github.com/danschultzer/receipt-scanner

@iteles iteles added priority-3 Third priority. Considered "Nice to Have". Not urgent. and removed priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished labels Jun 5, 2017
@ghost ghost mentioned this issue Sep 20, 2017
Closed
@ghost ghost added finance priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished and removed priority-3 Third priority. Considered "Nice to Have". Not urgent. labels Oct 26, 2017
@jammur jammur unassigned ghost Dec 14, 2017
@rub1e rub1e mentioned this issue Jan 30, 2019
Closed
4 tasks
@rub1e
Copy link
Member

rub1e commented Jan 30, 2019

I've added a couple of tasks to dwyl/process-handbook#126 to review & update the policy

Can this be closed in favour of that issue?

@iteles iteles added the question A question needs to be answered before progress can be made on this issue label Jan 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nelsonic nelsonic

Labels
discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality finance help wanted If you can help make progress with this issue, please comment! priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished question A question needs to be answered before progress can be made on this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nelsonic @iteles @rub1e