We encode the spec. Your bank accepts the test.
We control encoding, field validation and preflight. Your bank controls its own test and approval cycle, so we do not claim a bank is supported until a real customer file has been accepted.
Payroll Copilot connects HRIS, time, payroll, approvals, and Philippine compliance so every cutoff is easier to review, explain, and release with confidence.
Every cutoff is organized around one question: can this payroll be safely approved and released?
Bring employee, time, leave and payroll inputs into one governed cutoff.
Run deterministic payroll and statutory calculations against a versioned ruleset.
Investigate material variance, attendance issues and missing information.
Record approval, build payment outputs and preserve release evidence.
Click a payroll amount and see the sources, deductions, premiums, statutory shares and ruleset that produced the result—without leaving the payroll run.
Open the interactive payrollPayroll Copilot focuses reviewers on the employees and inputs that actually need attention.
Keep statutory calculations and filing preparation inside the same payroll evidence chain.
Employee and employer shares stay attached to the payroll calculation and ruleset used.
Review contribution basis, employee share and employer share before the cutoff is released.
Calculate employee and employer contributions with transparent rule tracing.
Keep withholding tax calculations, annual context and filing preparation connected.
Preserve inputs and tax treatment used for 13th-month calculations and exemptions.
Approved payroll versions retain the ruleset ID needed to explain calculations later.
Make it clear who has reviewed the payroll and what still blocks payment.
Builds the cutoff and resolves source-data issues.
Investigates exceptions, variances and calculation evidence.
Approves the controlled payroll version for release.
Payment output and filing close follow the approved version.
Payroll evidence should survive handoffs, spreadsheet changes and future audits.
Ordinary payroll administrators see the exception and recommended action first. Finance, audit and compliance teams can drill deeper only when needed.
Start beside the current Excel process, compare employee-level results, then graduate to controlled production payroll.
Bring employee, salary, DTR and existing payroll registers from CSV or XLSX.
Calculate independently and focus on the employees and values that differ.
Keep resolved differences, approval history and cutoff proof before changing systems.
Philippine banks each have their own payroll file layout, and yours is in the pack your bank gave you when you set up corporate payroll. Send it to us — we'll build your file to that exact spec and support you through your bank's test upload. BDO, BPI, Metrobank, UnionBank, Security Bank, RCBC, Landbank or any other.
We control encoding, field validation and preflight. Your bank controls its own test and approval cycle, so we do not claim a bank is supported until a real customer file has been accepted.
Forward this to your relationship manager:
Keep access, auditability and privacy controls visible as operational requirements—not marketing decoration.
Separate employee, manager, payroll, finance and administrative permissions.
Track privileged actions, approvals and changes that affect payroll.
Protect employee identifiers, documents and payroll evidence by tenant and role.
Keep payment and statutory close behind explicit approval gates.
Start with payroll control and HRIS, then add deeper operations as the team grows.
For very small teams validating a payroll-first workflow.
The core operating system for Philippine payroll teams.
For teams that also need deeper HR operations.
We build to your bank's spec rather than guessing at it. Bank formats differ by bank and sometimes by product tier, and they change without notice — so we don't publish a list of “supported banks” we can't verify. Send us the payroll file specification from your bank onboarding pack and we'll encode it, validate it against your real cutoff, and walk your first test file through with you.
A named bank is only treated as validated after a real customer test file has been accepted. Until then, Payroll Copilot can prepare and preflight the customer-specific layout, but the bank's own validation remains the acceptance gate.
See payroll readiness, investigate material changes and understand every peso before release.