Connect Rippling to Emburse Certify so expense management users are provisioned at hire, approval chains reflect your live manager hierarchy, and expense coding is driven automatically by Rippling's department and cost center data.
thePeopleStack configures the Rippling–Emburse Certify integration with manager hierarchy mapping that keeps approval chains accurate as the org evolves, and department and cost center data that automates expense GL coding at submission. We set up hire-triggered Certify account creation with the correct expense policy assignment, and configure offboarding to deactivate accounts at termination with appropriate handling of any outstanding expense reports.
For clients using Emburse Certify alongside a connected accounting system — NetSuite, Sage Intacct, or QuickBooks — we ensure Rippling's department and cost center structure is consistently mapped across both the expense management and accounting layers, preventing the GL coding discrepancies that require manual correction at month-end close.

Emburse Certify is deployed by thePeopleStack's Rippling clients primarily for US mid-market employee expense management, with expense policy enforcement, approval routing, and reimbursement processing configured around US org hierarchies and Rippling's US employee data.
Canadian and cross-border operations: Canadian employees submitting expenses through Emburse Certify are provisioned through the same Rippling sync. thePeopleStack ensures cross-border expense submissions account for Canadian currency, GST/HST treatment, and PIPEDA-relevant data handling for employee expense records processed through Certify.
Emburse Certify is Emburse's mid-market expense management product — distinct from Emburse Chrome River (enterprise) and the base Emburse platform. It provides receipt capture, mileage tracking, expense report creation, multi-level approval routing, and reimbursement processing. The Rippling integration provisions Certify users at hire with the correct policy and approval chain, and syncs expense data to connected accounting systems.
Yes. Rippling's manager hierarchy drives Emburse Certify's expense approval chain, ensuring expense reports route to the correct approver at each level based on the employee's actual reporting structure. When manager changes occur in Rippling, Certify's approval routing updates automatically so expense reports don't route to former managers or get stuck awaiting approval from someone who no longer manages the submitter.
Yes. Rippling department and cost center data maps to Emburse Certify's expense coding structure, ensuring submitted expenses are automatically coded to the correct GL account and cost center for accounting purposes. This reduces the manual expense coding step that slows reimbursement processing and creates accounting reconciliation work.
Employee termination in Rippling deactivates the Emburse Certify user account, preventing former employees from submitting new expense reports after departure. Any outstanding expense reports submitted before termination should be processed before the account is deactivated — thePeopleStack advises on final expense report handling as part of the offboarding configuration.
A standard configuration covering user provisioning, manager hierarchy approval routing, department and cost center mapping, and offboarding deprovisioning typically takes 3—5 hours. Certify deployments with multi-level approval chains, complex expense policy configurations by employee level, or direct accounting system integrations alongside Rippling may require additional scoping.