Attandess:
MII (bu Lidya and team), Hania, Edith, Andry, Ricko, Jessica P, Viani, Yudi

SF to query to pull data from EBP
1 ticket in SF = 1 Invoice to be followed up
Invoice breakdown is view only.
Download the detail via salesforce, in CSV format is a P1 requirement.
Salesforce to store to display P2 requirements - this means salesforce to store the data from CSV, and processing it.
Invoice status is pulled by salesforce regularly from BP
Collection status closing if invoice status paid is automated
Email status monitoring is a P1 requirement
Need to have capability to monitor email status, and trigger email resent if email bounces. MII needs to check first, and get back to us.
Customer ops can request changes of account data via Collection Platform. Collection platform will trigger task in MM (contracting/acquistion) salesforce to create task to update account to account owner (MM).
Reporting on collection and AR from salesforce. The AR reporting snapshot will be sent daily to traveloka finance email group
Data storing in SF:
P1 - invoice breakdown data is not stored in SF.
P2 - invoice breakdown data is stored in SF.
Account Contact and Account data field will be sent to Traveloka via quip for review by Bu Lidya, for traveloka to be reviewed.
Storage calculator will be sent by By Bu Lidya to estimate the storage size.

MII - Traveloka sync (21 Feb 2018):