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

Spiff bounties process - Payment #1579

Open
calexh-sar opened this issue May 21, 2024 · 5 comments
Open

Spiff bounties process - Payment #1579

calexh-sar opened this issue May 21, 2024 · 5 comments
Assignees
Labels
enhancement New feature or request process Process model updates
Milestone

Comments

@calexh-sar
Copy link
Contributor

calexh-sar commented May 21, 2024

Complete proposed process model to allow for bounty payment.

Bounty payment will require creation of a Iplicit PO, which involve adding the bounty supplier account in Iplicit with at least this data:

  • contact group ID: 3P for credit suppliers, CARD for any suppliers who will be paid by debit card. I have created a group BOUNTY for bounty recipients
  • department ID: Yes this is very important so that the supplier invoices are allocated to the correct department
  • paymentmethod ID: DBT for all suppliers who will be paid by card, including subscriptions and adhoc payments. CRY is Crypto if the supplier will receive crypto payments and BC for BACS payments.
  • payterm ID: We will use 30 days as standard for all 3rd party suppliers unless we specifically are told that the supplier has different terms.
  • address: Yes, mandatory
    Also...
  • For bounties, the default account will be bounties.
  • We will still need tax authority and tax band, but I have set them as a default tax authority of Singapore and tax band as Not applicable as a default, the same as we have for CCs
@calexh-sar calexh-sar self-assigned this May 21, 2024
@calexh-sar calexh-sar added this to the Bounties MVP milestone May 21, 2024
@calexh-sar
Copy link
Contributor Author

@harmeet-status issue for bounty payment for your prioritization. Are the details on the Iplicit PO process still pending?

@harmeet-status
Copy link
Collaborator

harmeet-status commented May 21, 2024

No @sashayar13 will not be ready in time, so we can just put a manual step here for Finance to create a purchase order (PO) in Iplicit.

@sashayar13
Copy link
Collaborator

@calexh-sar there is a PO process in place which you can incorporate into the Bounty process. @MarD0607 is the one who will be able to assist you with this

@calexh-sar
Copy link
Contributor Author

Thx, @sashayar13. @MarD0607, would you please point me to a process or processes which are examples of the PO process.

@calexh-sar
Copy link
Contributor Author

From @MarD0607 via Discord:
For the bounty data store, we will need to generate codes for suppliers just like we do with vendors. You can use https://dev.app.spiff.status.im/process-models/manage-procurement:vendor-lifecycle-management:metadata-synch:current-list-of-iplicit-codes to get the current list of codes from Iplicit, and I have a Generate supplier code script task in the MI in https://dev.app.spiff.status.im/editor/process-models/manage-procurement:vendor-lifecycle-management:metadata-synch:bbhr-man-new-cc-to-iplicit/files/bbhr-synch-with-vendor-md.bpmn, which based on the full name and the list of current codes from Iplicit, will create the new code

@harmeet-status harmeet-status added enhancement New feature or request process Process model updates labels Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request process Process model updates
Projects
Status: Backlog
Development

No branches or pull requests

3 participants