Sie sind auf Seite 1von 41

DMRC BI-MONTHLY

MEETING 2019
HELLO!
I am JM

2
TOPICS TO BE DISCUSSED
◉ DMRC ACCOUNT ASSIGMENT ◉ DMRC PROCESS
◉ DMRC FUNCTION  NEW PROCESS
 ADDITIONAL PROCESS
◉ VOCABULARY (commonly used terms)
 REVISED PROCESS
◉ RPAN/201 FILE VALIDATION
◉ WHITE BOARD
◉ RPAN/2O1 ENCODING
◉ EMPLOYEE KIT
◉ DMRC ADHOC TASK
◉ DMRC REPORTS

3
DMRC ASSIGNMENT
1
4
CLUSTER 1 & 8
• Assigned to Cluster 1 and 8Accounts
 PCH, BLK, MPTII, J&J, Happy Skin, Jake Bros, CCAC
 RPAN receiving & HRAN encoding
 Employee Kit releasing for the assigned account
• Contract, Rpan, Handbook Monitoring
• Gov’t Application receiving, releasing monitoring (AMII & SMSSI)

MA. MERCEDES “DITAS” CASIÑO


DMRC Staff

ditas.acabar@gmail.com

1
dpcasino@tnci.com.ph

DMRC ASSIGNMENT
Tel. no: 8446003 loc.152

5
CLUSTER 2
• Assigned to Cluster 2 account
 Wyeth, Fly Ace, Scan Asis, SCJohnson, Sunnywood
 RPAN receiving & RPAN encoding
 Employee Kit releasing for the assigned account
• Contract, Rpan, Handbook Monitoring
• R1A encoding and Report

FRANCIS ALDRIN “LICH” LEECHIU


DMRC Staff
fsleechiu@tnci.com.ph

1
Tel. no: 8446003 loc.152

DMRC ASSIGNMENT
6
CLUSTER 3
• Assigned to Cluster 3 account
 Coke, MFC, Zuellig, Firelfy, Scheider
 RPAN receiving & RPAN encoding
 Employee Kit releasing for the assigned account
• Contract, Rpan, Handbook Monitoring
• AD&D Encoding And Report

FRANCIS
MARK BENJAMIN “LICH” LEECHIU
ALDRIN “BENJ” ALDAYA
DMRC Staff
mbaldaya@tnci.com.ph

1
Tel. no: 8446003 loc.152

DMRC ASSIGNMENT
7
CLUSTER 4 & 5
• Assigned to Cluster 4 & 5 account
 Sepco, Multirich, Suncrest
 RPAN receiving & RPAN encoding
 Employee Kit releasing for the assigned account
• Contract, Rpan, Handbook Monitoring
• Tarpaulin Creation and Editing.
• Relasing of ID branch

JHUDEL
FRANCIS
MARK “JHUD”
ALDRIN
BENJAMIN “LICH”
“BENJ”OROLA
LEECHIU
ALDAYA
DMRC Staff
DMRC Staff
jsorola@tnci.com.ph

1
Tel. no: 8446003 loc.152

DMRC ASSIGNMENT
8
CLUSTER 5, 6 & 7
• Assigned to Cluster 4 & 5 account
 SMIS, SMBI, BCS, MDC, MCC, YPI, BEI
 RPAN receiving & RPAN encoding
 Employee Kit releasing for the assigned account
• Contract, Rpan, Handbook Monitoring
• R1A encoding and Report

MARK
FRANCIS
MARK ALDRIN
BENJAMIN “LICH”LIGPIT
“BENJ”
DEO“DEO” LEECHIU
ALDAYA
DMRC Staff
DMRC Staff
mfligpit@tnci.com.ph

1
Tel. no: 8446003 loc.152

DMRC ASSIGNMENT
9
CLUSTER 1
• Assigned to Cluster 1 account
 CDO
 RPAN receiving & RPAN encoding assigned account.
 Employee Kit releasing whole Stargate account
 PANform releasing whole Stargate Account.
 Releasing if ID for branch

MARK
ALFERDS
FRANCIS
MARK “FERDZ”
ALDRIN
BENJAMIN “LICH”
“BENJ”
DEO“DEO” LIGPIT
REBADULLA
LEECHIU
ALDAYA
DMRC Staff
DMRC Staff
Staff
agrebadulla@tnci.com.ph

1
Tel. no: 8446003 loc.152

DMRC ASSIGNMENT
10
CLUSTER 4
• Assigned to Cluster 4 account
 MARS
 RPAN receiving & RPAN encoding for the assigned
account.
• Contract Returned Monitoring
• PANform Returned Monitoring
• Handbook Returned Monitoring
• Performance Evaluation Monitoring
• R1A Encoding & Report
JERRY “JERRY” ORTEGO
DMRC Staff
jportego@tnci.com.ph

1
Tel. no: 8446003 loc.152

DMRC ASSIGNMENT
11
CLUSTER 2 & 3
• Assigned to Cluster 2 & 3 account
 KCPI, LAMCO, 3M, GSMI, SEPCO, LOREAL, ABBOTT
 RPAN receiving & RPAN encoding for the assigned
account.
• AD&D Encoding And Report

INNA PAULINE “INNA” AREVALO


DMRC Staff
Innaarevalo@gmail.com

1
Tel. no: 8446003 loc.152

DMRC ASSIGNMENT
12
DMRC FUNCTION
2
13
 RPAN receiving and employee’s data encoding
(i.e rate, area of assignment, date of employment, Accidental Death &
Dismemberment enrollment when applicable.)
 Employment Agreement creation, issuance and monitoring of return
 ID creation and issuance
 Updating of employee’s records in the system (Changes in rate, superior,
paygroup, employment status, etc.)
 Issuance of PAN form to employees whenever there is a change of
employee’s status i.e probi/regular, position, change of rate, promotions,
transfer

1
 PayCard number encoding for (GMA and Provincial)
DMRC FUNCTION
14
 R1A encoding and reporting
 Monitors the submission of performance evaluation(AMII & SMSSI).
 Assistance to all employment verification.
 Monitoring of employees tenure per account.
 Preparation of DOLE data report for all rationalizations, retrenchments
and completion of projects.
 Receiving and monitoring of Clearances.
 201 File filing and records keeping
 Maintaining accurate date on Jeonsoft and update necessary information
needed for the employee.
DMRC FUNCTION
1 15
2
VOCABULARY INTRODUCTION commonly
used terms/acronyms

16
1. Personal Information Sheet - application form that needs to be filled up by an applicant prior
to screening
2. RPAN - Request for Personnel Action Notice
◉ Form used to request for employment agreement / contract & ID
◉ Form used to register and update employee in the HRIS
3. Employment Agreement - Employee’s Contract
4. Job Description (JD)
◉ A document that outlines all his duties, responsibilities and key result areas particular to his job. This document also indicates
his immediate supervisor.
5. Non Disclosure Agreement (NDA) - a document that is issued together with Employment
Agreement which employees agree to keep confidential information about the company
6. ID – Identification Card
7. Katibayan (Katibayan ng Pagtanggap / Acknowledgement form) - A document that is issued
together with employee’s PayCard; acknowledgement form

2
Vocabulary
(Commonly Used Terms / Acronyms)

17
8. PayCard - a special payroll ATM card issued to all employees of the 3 companies
9. Personnel Action Notice (PAN) = A document that is issued to employee whenever
there is a change of employee’s status
i.e probi/regular, position, change of rate, promotions, transfer
10. 201 File
Personal record of an employee including:
◉Signed Employment Agreement
◉Government identification numbers (SSS, PHIC, HDMF, TIN)
◉Personal Information Sheet (Education attainment & previous work experience
◉COE from previous employers
◉NBI, Police clearance
◉Medical Records Vocabulary

2
◉All disciplinary related docs
◉Performance Appraisal (Commonly Used Terms / Acronyms)

18
• RPAN/201 FILE VALIDATION
3
19
DOCUMENT REMARKS
RPAN
Personal Information Sheet
SSS No. Minimum Requirements (DMRC can accept)

Latest / Updated NBI Clearance or Police

PhilHealth No.
Pag-Ibig No.
TIN

3
Red background for AMII
ID Picture (1pc. 2x2, 1pc. 1x1)
Blue background for SMSSI
Formal
Green for TNCI

RPAN/201 FILE VALIDATION

20
20
# Requirement What are acceptable?

• SSS ID
• Any SSS form that has a “Received” Stamp
1. SSS No.
• SSS E1 Form or SSS E4 Form
• UMID (as long as the CRN does not start with 0111)

2. NBI Clearance or • Must not be expired as of 1st day of employment


Police Clearance • O.R will be accepted as long as it has the “Claiming Date”

3. Philhealth No. • Philhealth ID (New or Old)


• PHIC MDR or PMRF
• Any Philhealth document has a “Received” Stamp

4. Pag-IBIG No. • Pag-IBIG Loyalty Card


• Old HDMF ID or Transaction Card
• MDF (For non-members)

3
• Any Pag-IBIG document that has a “Received” Stamp

5. TIN ID • TIN ID
• 3 copies of fully filled up BIR 1902 Form with employee’s Birth Certificate + Marriage
Contract, if Married + Dependent’s Birth Certificate, if applicable.
• Any BIR document that has a “Received” Stamp.

RPAN/201 FILE VALIDATION


21
21
Check if what company RPAN coming

Name of Account

Check if for additional, replacement or reliever


for replace and reliever DMRC shall encode name
on remarks tab name of employee he/she relieving
or replacing.

DMRC shall will check information and make sure all


tabs are fill up properly

DMRC will make sure if rate are aligned in MWE rate


sheet, if Above minimum DMRC will need approve
rate or ask billing for the aligned rate sheet.

3
Same with the allowances. (check if daily or monthly)

DMRC shall secure signature of account hedas (OM,


NAM or RAM)

RPAN/201 FILE VALIDATION


22
22
• RPAN/201 ENCODING
4
23
Regular Process
 Upon receiving of RPAN/201 file from OP, DMRC shall check and verify contents of RPAN and
attached documents.
• Deadline of receiving of files is 6PM. If OP submitted files beyond the given time. DMRC will still
accommodate the files but received date should be the following date)

 If OP submitted files that does not pass on our standard minimum requirements (RPAN, SSS, 201
Application and NBI or Police) DMRC shall flag concerned FOA regarding incomplete requirements. If
OP did not comply within the day, DMRC shall email list of employee for PULL OUT to (FOA, OM,
Heads, and OSD heads) and shall log names of the files with its reason in LOGBOOK

 Once all files has been check, DMRC shall start encoding received files
• Upon received date, DMRC shall encode the files not exceeding 3 DAYS

4
 DMRC will submit RPAN for posting to payroll
 DMRC shall email list of newly hire/encoded to O.P same day of submission of for posting to Payroll.
 Sending of newly hire/encoded – OP should see details of employee from (employee code, formal
name, rate, pms, date hired, etc)

RPAN/201 ENCODING
24
24
Regular Process
Submission
RPAN encoding as of TSS
to regular process

PAY OUT

`
DATES 10 11 12 13 14 15 16 17 18 19 26

Submission of
list Newly Hire
RPAN deadline of
Employee to OP

4
submission from OP
RPAN for
posting
Note: if date hired of Employee is within the submission
given date (between OP RPAN deadline to to Payroll
DMRC and DMRC RPAN for posting deadline

RPAN/201 ENCODING
to payroll) DMRC will receive and process
RPAN under regular process and will be tag as
ON TIME

25
25
Special Payroll/Process
 Files that didn’t make it on regular deadline submission are subject for Special Payroll/Process
• Employees that are hired not between (see illustration on next slide) OP RPAN deadline to DMRC to
DMRC RPAN for posting deadline to payroll. OP shall email request for a Special Payroll/Process.
• Employees that are hired between (see illustration on next slide) OP RPAN Deadline to DMRC to DMRC
RPAN for posting deadline to payroll. DMRC will acknowledge this and under go Regular process
and will be tag as ON TIME.
 DMRC will accept files for Special Payroll/Process and advice OP to make email
 Upon encoding DMRC will change Security Level to “Level 3” so once payroll submit TSS to OP those
who are subject for SP approval won’t be included on TSS.

4
 DMRC will wait for approval of heads (Ma’am Shee or Ma’am Elo) before submitting to payroll and
reverting security level back to “Level 1”
 Once approved DMRC shall submit RPAN for special payroll/process to payroll the same day of
approved date.by OSD heads.

RPAN/201 ENCODING
26
26
Special Payroll/Process
 Once submitted DMRC will change security level from Level 3 to Level 1 so payroll can view and submit
new TSS to OP. once requested.
• For bulk change security level you may email list to me for uploading.
• DMRC will never provided Employee Code to O.P for the purpose of S.P as this will violate Standard
Process
• OP should request for another set of TSS for those employee under S.P
 DMRC will reply e.g. “done encoding. request for another TSS” same email thread where OP requested
for S.P

RPAN/201 ENCODING
4
27
27
Special Payroll/Process
RPAN encoding as
to regular process

`
DATES 10 11 12 13 14 15 16 17 18 19

RPAN regular deadline RPAN that are NOTE: OP shall email


submitted after regular request for S.P with the list

4
of submission from OP
Regular RPAN for deadline will fall under of employee and reason why
posting submission to S.P they didn’t submit it on time.
Payroll

RPAN/201 ENCODING
28
28
EMPLOYEE KIT
5
29
 Employee Kit Includes:
EMPLOYEE KIT
• Employment Agreement (Employer and Employee Copy
• Non Disclosure Agreements
• ESS access Guidelines
• Ecare Guidelines
• Guidelines how to Sign contract & NDAproperly
• Employee Handbook
• Handbook Acknowledgment Receipt.
 DMRC will issue Employee Kit within 7 Days upon receipt of RPAN/201for posting.
 DMRC will issue Employee kit with Employee Handbook to those employee who are probationary, project
employee and reliever with more than 1 month tenure.
 DMRC will issue Employee kit without Employee Handbook for those project employee or reliever who

5
has less than 1 month tenure.
 For those employee who did not signed their Employee kit for the reason of Resigned, end of project, etc.
DMRC shall re-issue Employee Handbook to another employee.
 DMRC will email OP once Employee Kit is available and ready to claim.
EMPLOYEE KIT
30
30
DMRC ADHOC TASK
6
31
DMRC ADHOC TASK
 DITAS – Handling Cluster 1 and 8 Accounts.
• Receiving and Monitoring submitted Government Applications from OP for Acabar and Stargate
• Incharge in keeping track submitted application from OP to benefits and securing copy of files will be
given to OP and Insert to the 201 file folder of the said employee.
• TIN – 1902
• PAG IBIG New Application.
• PHILHEALTH New Application.
• LICH – Handling Cluster 2
• R1A – enrolling employee to sss under what company he/she is hired (acabar)
• Creation of PHILHEALTH application forms base on system and will submit to benefits for the purpose
of enrollment of employee
• Assisting training section

5
• BENJ – Handling Cluster 3 Accounts
• AD&D – Enrolling, Purging and Monitoring of employee for insurance.
• JHUDEL – Handling Cluster 4 and 5 (RBC Group) accounts.
• Creation and Releasing of ID for Branch.
• Tarpauling creation or any related request when it records to editing pictures or videos.

DMRC ADHOC TASK


32
32
DMRC ADHOC TASK
 DEO – Handling Cluster 6,7 and 5 (benby) account
• R1A – enrolling employee to sss under what company he/she is hired (acabar)

STARGATE TEAM
 JERRY – Handling Cluster 4 (Mars) Account.
• R1A – enrolling employee to sss under what company he/she is hired (stargate)
 FERDS – Handling Cluster 1 Account
• Creation and Releasing of ID for Branch.
 INNA – Hadling Cluster 2 and 3 account.
• AD&D – Enrolling, Purging and Monitoring of employee for insurance.

DMRC ADHOC TASK 5


33
33
DMRC REPORTS
6
34
DMRC REPORTS
 RPAN Newly Hire Monitoring – Monitoring that includes the details of submitted newly hire that tracks
Lag days of received, encode, submitted and release.
 DMRC shall update RPAN and Contract Monitoring twice a month (1st and 2nd period of the month)
 DMRC shall insure all inputted information are accurate.
 DMRC will send report to DMRC SUP. A week before MANCOM.
 Contract Monitoring.– Monitoring that includes details of released contracts to OP and tracks lag days of
contract created, released and returned.
• DMRC shall update monitoring in a day to day basis once he/she release contract to OP or Received
retuned contract from OP

6
• All received contract shall be updated on or before every Friday
• DMRC shall email Contract monitoring per cluster to OP every Saturday COB

DMRC REPORTS
35
35
DMRC PROCESS (NEW, REVISED, ADDITIONAL
6
36
DMRC PROCESS
 DO.174 Release Date and PANFORM for Regularization Tick Box. – This process is to help track and
improve monitoring and releasing of employee kit in the given 7 days timeline upon received of RPAN from
OP.
 Whenever DMRC release Employee Kit. DMRC should fill up “DO.174 Released Date” input date when
the employee kit email/release to OP and Tick Box when DMRC released PANform for regularization.
• DMRC will input email/release date of Employee Kit “DO.174 Released Date”
• DMRC will provide list to me for uploading of released employee kit with the date as to when it was
emailed/released to OP for bulk encoding only.
• If DMRC can manage to manual encode no need to email me.

 PANform Regularization – This process is to help track and improve monitoring and released

6
Regularization.
• DMRC will tick the box if panform regularization has been issued
• DMRC will provide list to me for uploading of released employee kit with the date as to when it was
emailed/released to OP for bulk encoding only.
• If DMRC can manage to manual encode no need to email me.

DMRC PROCESS (NEW, REVISED, ADDITIONAL


37
37
DMRC PROCESS
 RPAN CUT OFF – this process is to help track and improve report monitoring when entering the specific
cut off when the files was received from OP.
• DMRC will included what cut off falls or received files in a month + period basis all RPAN for encoding
received e.g June 1St Period or june 2nd period)
• This is only applicable on newly hire or re-hired employee.
• For Corporate adhoc DMRC will use tagging of e.g june 1st week up to june 5th week.
 RPAN Received Date – this process is to help track and monitor of 7 days timeline in issuing employee
kit.
• DMRC will input date only for those who are Newly hire or Re-Hired for the purpose of monitoring of
deadline which is incorporated to RPAN CUT OFF.
 RPAn UPDATE – This process is to keep track and monitor all changes/movement in rpan

6
• DMRC will input date all RPAN Changes (rate, position, pms, etc) e,g 06.20.2019 change
rate|06.22.2019 change PMS.

DMRC PROCESS (NEW, REVISED, ADDITIONAL


38
38
PMS incharge base on
RPAN
DMRC PROCESS
Name of DMRC
encoded.

6
Email/released date of employee kit Tick Box When for
If no NBI/Police DMRC will tag “HOLD” Regularization has been issued
until OP submitted lacking file to employee.
Date when the files where submitted to
DMRC for Newly hire and Re Hire Only. Date of movement of RPAN (rate, PMS,
Period when the files etc)
received from OP When the files where encoded.

DMRC PROCESS (NEW, REVISED, ADDITIONAL


39
39
DMRC GUIDELINES FOR SP
 Standard process for requesting special payroll/process
• OP to email list of employees under special payroll/process including reason and endorse it to OM
incharge of account
• OM to endorse email from OP to OSD heads
• OSD heads to approve encoding base on the list of deliverables availability of DMRC staff incharge
• Once approve DMRC shall encode files base on the list provided from the 1st email from OP.
• Once done encoding DMRC will inform OP if done.
• OP shall request separate TSS under special payroll/prcess, DMRC may advice OP.
 NOTE: for the longest time, Standard process for SP was overlooked. Now we are enforcing strict
compliance for all processes for DMRC staffs/

6
 There are no separate process for AMII and SMSSI all standard process are the same. for the both
company

DMRC PROCESS (NEW, REVISED, ADDITIONAL


40
40
DMRC COMMINICATION
 DMRC to OP proper communication
• DMRC shall not converse on an OTP (over the phone) conversation
• DMRC shall not converse or make basis using CHAT in any form of application.
• DMRC shall advise OP to email all related concerns and all CC heads.
• DMRC shall documents through email all OTP conversation.
• Do not use un authorize email addresses, use only what is given by the company.
• DMRC shall always includes DMRC HEAD, Sup and OSD heads on all emails.
• If there are request from op or people kindly advise to email 1st before acting 1st.

 NOTE: this is to avoid any issues or conflict. And to converse professionally in or out of the office

DMRC PROCESS (NEW, REVISED, ADDITIONAL 6


41
41

Das könnte Ihnen auch gefallen