-
Notifications
You must be signed in to change notification settings - Fork 1
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
F&C Invoicing Update #272
Comments
@markwilliamfirth Are the dev invoices part of this or part of #229 ? |
A further requirement (not urgent but may impact how you record things for F&C) - I would love to run a report off to see how much we've paid in commission for each person back to F&C. This would give the developers an idea of how much they have contributed given that there is a suggested contribution. |
@iteles uploading to xero is part of this, but sending to me is part of 229 (have updated 229) |
This keeps getting pushed back, but Dan's been waiting on this a long time and I think we should make this a priority @iteles Dan's actually asked me about it 4 times, but each time my answer is that it hasn't been done yet as it isn't a priority |
It is a priority. There has literally been one thing that is higher priority than this for months, which is something we discussed as a key part of what was needed on 31st January: #321 That is still a higher priority. I also agree that seeing as this was opened as a priority 2 in March, we need to understand exactly why the priority of this wasn't respected and why it has taken us this long to get around to it. A time estimation would be a great start to understand where it can be fit in. |
@iteles because there are 63 priority 2 issues in HQ alone (ignoring other repos e.g. focus hub etc) The priority-2 label doesn't really mean much when there are so many. The only thing we can go by is the projects log and as you can see it keeps getting pushed back as more urgent things pop up and move in front of it I think we need to agree a deadline for when it should be done by and stick to it |
The deadline for this is after #321 is complete 👍 This might also be a good time to go through your |
@markwilliamfirth I need to meet with @sofer on this in the next 2 weeks, so the priority on this needs to rise. Is it realistic to please carry out step 1 of the checklist in the top comment of this issue (or any other methodology you see as more efficient over filling out that spreadsheet) by the end of this week so that we have an idea of roughly how much we need to settle and can also determine before I meet with Dan what actions are needed to guide the conversation that we have? |
I'm assuming the answer to my question directly above this was 'no', rather than what was implied by the labels which is that it was both doable and in progress? I am meeting with Dan early next week, so please let me know @markwilliamfirth . |
@iteles this is in progress - I've already discussed this with Dan separately. if there is a deadline for this completion please let me know |
I'm not sure I understand your comment @markwilliamfirth. My question above was what was a realistic timeline for to "carry out step 1 of the checklist in the top comment of this issue (or any other methodology you see as more efficient over filling out that spreadsheet)". |
We're not actually going to solve this via the old spreadsheet - this requires getting Xero completely in order (which I've almost done) and then doing some weird Xero magic and/or something with autocrat - the dependency is here because i'm currently in contact with Xero as our account balances don't match |
@markwilliamfirth Very excited to hear Xero is almost completely in order! Is this related to #383 ? |
Any luck with Xero? They seem slow on the resolving of issues 😕 |
Any questions, complaints, feedback, contributions? |
dwyl pays a commission of 10% of charged-out rates back to Founders & Coders to help keep the lights on.
Update F&C sheet for new payments
Mark devise new Xero system to inform Dan
Developer invoices
The text was updated successfully, but these errors were encountered: