In this article
Build a product-and-policy reference so that the help you follow matches your employer’s actual expense system.
A colleague says “Certify,” an email says “Emburse,” and the app on your phone carries another label. Before attempting a fix, establish which product your employer uses. The brand covers multiple systems. A sensible instruction for one system can describe a button, status or payment process that another does not have.
The current naming map
The official Emburse login directory identifies Certify as Emburse Professional and Chrome River as Emburse Enterprise. Product pages use the fuller names Emburse Expense Professional and Emburse Expense Enterprise. This is a naming relationship, not evidence that the two products have become the same application.
Emburse Spend is separately identified. Its individual-expense approach should not be confused with every report-oriented Professional instruction. Other products in the login directory also retain their own entries. The word “Emburse” alone therefore cannot tell you which help article to follow.
Make a reference without collecting secrets
Use an employer-approved note or internal bookmark to record five details. You can usually collect them from your established work instructions and the application you already use. Do not copy credentials or banking information into the note.
- Product: record the name shown in your employer’s current setup instructions.
- Entry point: save the existing work portal or employer-approved sign-in route.
- Interface: distinguish browser, mobile app and any travel-booking application.
- Policy owner: identify the team responsible for expense categories, evidence and approval routing.
- Payment owner: identify the team that can verify reimbursement release and payment records.
The last two roles may sit with the same team, but they answer different questions. An IT colleague may restore access without being able to approve an expense. A manager may approve the business purpose without having visibility into the payment batch. Our reimbursement route map explains why those boundaries matter.
Check a guide on four dimensions
Product match: does the page explicitly name the product in your reference? A historical Certify URL can legitimately host current Professional help; the page title and official provenance matter more than a familiar-looking hostname alone.
Role match: is the guide for an employee, approver or administrator? If it asks you to configure company policy, it may not describe a permission you have. Do not borrow someone else’s access or try to recreate missing administrative controls.
Interface match: a browser screenshot and a mobile screen may organize the same work differently. Treat a missing button as a question to investigate, rather than proof that your account is broken.
Configuration match: check whether the page assumes a payment service, optional integration, enabled review feature or particular workflow. Product capability is not proof of enrollment. Your organization’s policy also decides what is allowed; the presence of a category does not grant spending approval.
A fictional naming mix-up
Priya’s company historically called its expense tool Chrome River. She searches for a reimbursement delay and finds a Professional article describing report folders. None of the labels match her screen. Her next useful action is to confirm Enterprise in the employer’s instructions and ask the payment owner which payment route applies. Repeatedly hunting for the Professional folders would add confusion without moving the payment forward.
She records the actual report reference, the exact status shown and the date she checked it. Those are useful observations regardless of product. She does not translate an unfamiliar Enterprise status into a Professional label merely because they sound similar.
When two official pages disagree
Keep both links and describe the precise difference. Public documentation can describe different interfaces, configurations or stages of a rollout. The responsible administrator can reconcile those instructions with your actual account. Ask, “Which rule applies to our product and interface?” rather than selecting whichever page permits the action you prefer.
Use the approval handoff checklist once the product is established. If access itself is the problem, prepare a minimal case using our safe support guide. The finished reference should help you reach the right owner quickly, without containing anything that could unlock your account.