Rippling +

Emburse Certify

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.

What the Rippling +

Emburse Certify

 Integration Does

  • Automated user provisioning at hire: New hire events in Rippling create Emburse Certify accounts with the correct expense policy assignment, ensuring employees can submit expenses through the managed system from their first day.
  • Manager hierarchy-driven approval routing: Rippling's reporting structure drives Emburse Certify's expense approval chain, updating automatically when manager changes occur so reports always route to the correct current approver.
  • Department and cost center expense coding: Rippling department and cost center data maps to Certify's GL coding structure, pre-populating expense coding at submission and reducing manual coding errors.
  • Offboarding deprovisioning: Employee termination in Rippling deactivates the Emburse Certify account, preventing new expense submissions after departure with appropriate handling of outstanding reports.

What Mid-Market Teams Get Wrong

  • Not syncing Rippling's manager hierarchy to Emburse Certify's approval routing: Expense approval chains that route to former managers create bottlenecks and delayed reimbursements. Manager changes in Rippling must update Certify's approval routing automatically — not be manually corrected by finance after an employee reports their expense report is stuck.
  • Not mapping Rippling department and cost center data to Certify expense coding: Employees who manually select cost centers and GL codes when submitting expenses introduce coding errors that require finance correction at month-end. Rippling's department and cost center data should pre-populate expense coding at submission, reducing errors and accelerating close.
  • Not provisioning Emburse Certify at hire through Rippling: New employees without Certify access on their start date submit expenses via email or spreadsheet — creating unstructured expense records that aren't captured in the expense management system and complicate reimbursement processing for finance.
  • Not deactivating Certify accounts promptly at offboarding: Former employees with active Certify accounts can submit expense reports after departure. More commonly, stale accounts with unprocessed reports create month-end reconciliation issues when finance discovers unresolved expense reports from departed employees during close.

How thePeopleStack Configures This

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.

USA & Canadian Operations Note

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.

FAQs

What is Emburse Certify and how does it differ from other Emburse products in the Rippling integration?

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.

Does Rippling's manager hierarchy drive Emburse Certify's approval routing?

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.

Can Rippling department and cost center data drive Emburse Certify expense coding?

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.

How is Emburse Certify offboarding handled through Rippling?

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.

How long does the Rippling–Emburse Certify integration take to configure?

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.

Ready to Connect Rippling with

Emburse Certify

We implement and configure Rippling integrations for mid-market teams across North America. Most integration setups are completed within a single implementation engagement.

Book a Free Discovery Call