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

Ask in the Event Request how Fellows (or those they are supporting) will claim (e.g. expense, or invoice) #758

Open
OscarSeip opened this issue Feb 23, 2024 · 2 comments
Assignees

Comments

@OscarSeip
Copy link

OscarSeip commented Feb 23, 2024

Add a field to the funding request form which asks if the Fellow will hire someone else to do some work for them or if the SSI will be invoiced. If so, finance should be alerted so they can add them as a supplier.

@shoaibsufi
Copy link

At event request time check:

  1. How they plan to claim
    1. Expense
    2. Invoice
    3. A combination (and if so a breakdown of how much for each)
  2. If they are using their Fellowship to support others – how will the other(s) be claiming.
    1. Expense
    2. Invoice
    3. A combination

In the case whether it’s an invoice or a combination this should trigger an email to a designated email (e.g. could be SSI Finance or Fellow-Management) to take over the conversation around supplier registration and timescales.

@shoaibsufi shoaibsufi changed the title Add field to funding request Ask in the Event Request how Fellows (or those they are supporting) will claim (e.g. expense, or invoice) Feb 26, 2024
@Kvglass
Copy link

Kvglass commented Feb 27, 2024

We also need to ask about the type of "service" that is being paid for. If we are paying for someone's time, (3 hrs @ £30 p/hr) this requires the payee to provide certain information re HMRC (a Unique tax ref no (UTR)), but if we are paying an honorarium, this would ususally be paid as a one-off payment, so no PO is required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants