Thingies
This commit is contained in:
parent
0eb20d720d
commit
5505a8ecff
3 changed files with 147 additions and 34 deletions
|
|
@ -7,4 +7,49 @@ Everyone agrees on it, yet we still need to put a solution in place. The Data Te
|
|||
## Content index
|
||||
|
||||
- `FW Payments and Invoicing process.msg`: some contents sent by Elaine, including Excel sheets they use to merge and process data.
|
||||
-
|
||||
- `step_files`: the Excel sheets mentioned above.
|
||||
- Invoicing flow chart: a flow chart built by Ben C. with the different steps: https://miro.com/app/board/uXjVMirYfDg=/
|
||||
|
||||
|
||||
## My notes on the video
|
||||
|
||||
My notes when watching through the video Ben C. recorded with the Finance team.
|
||||
|
||||
- Jamie has the task of calculating the waivers (can this be divided into a subprocess?)
|
||||
- Data is exported out of PowerBI and Acquired and "validated". There are inconsistencies between both sources and the team manually fixes them.
|
||||
- What are in the inconsistencies? Why do they happen?
|
||||
- If Acquired is the source of truth, why bother export the PowerBI data?
|
||||
- Which PowerBI is it exactly? What exact table gets exported?
|
||||
- With this, waivers are calculated and payments are reconciled.
|
||||
- Some manual information needs to be obtained through the dashboard
|
||||
- Which?
|
||||
- How can we get it out of the backend without having to go through the UI? Can I make a nice query to fetch this out instead?
|
||||
- Info also gets manually searched for in Hubspot and the Acquired dashboard.
|
||||
- So, what's not really in PowerBI?
|
||||
- Manual refunds
|
||||
- Chargebacks
|
||||
- Errors 262 from Acquired (PowerBI considers it as paid even though it isn't)
|
||||
- Sometimes the payment is simply not in Dashboard at all, so it doesn't appear in PBI.
|
||||
- Manually convert the currencies (Can I lookup some small excel wizardry to make this simple for them???)
|
||||
- There are Payment Requests that get manually generated by the Customer Service team in Stripe and sent to customers out-of-process if Acquired fails.
|
||||
- Records in Stripe about who the host is, what the booking is, need to be checked manually from the UI
|
||||
- From Hubspot
|
||||
- Get the new clients and pricing structure there
|
||||
- Names in Hubspot and Dashboard are different
|
||||
|
||||
|
||||
Some random thoughts:
|
||||
- I feel a lot of negativity in the meeting. Everything is deemed hard and not doable. "We are doomed and that's it."
|
||||
- Would all of these PBI exports be simplified by having direct queries to the databases?
|
||||
- It feels like Dashboard is not 100% perfectly synced with the Payment Providers?
|
||||
|
||||
|
||||
|
||||
Fronts:
|
||||
- Quickish
|
||||
- Ease data export from dashboard with tailored queries
|
||||
- Formalize things and win spreadsheet agility by simply formalizing and documenting things
|
||||
- Longish
|
||||
- Remove manual payments from limbo. We need some degree of organization around there, even if the first version is just a well maintained shared spreadsheet.
|
||||
- Single payment processor
|
||||
- Integrate payment processor data into a database of ours. Dashboard backend if it makes sense, DWH if it doesn't
|
||||
Loading…
Add table
Add a link
Reference in a new issue