Skip to content
InsightsGet started

Case study

Costpoint projects and accounts in Ramp, as one two-level choice

A professional services firm lets employees pick a Costpoint project, then only the accounts that belong to it, when they code expenses in Ramp.

Value to the client

Cost reduction
150hrs / yr
of correcting expenses coded to the wrong project or account
Our estimate
Risk mitigation
0
invalid project and account pairs offered when coding, for clean project charging
By design

Our estimate assumes about 3 hours a week spent finding and correcting miscoded expenses before they post to Costpoint.

Josh Mullins

Managing Director

3 min read

Share

At a glance

Client
Not named
Industry
Professional services
Services

Systems connected

  • Deltek CostpointProjects and account codes
  • RampExpense coding

Expenses coded to valid project and account pairs

Dropdown
2-level
Project first, then its accounts
Codes only
Active
Closed codes drop out
Source of codes
1
Costpoint, synced on a schedule

Before

Expense coding that depended on lookups

  • Employees looked up project and account codes before coding an expense.

  • Any account could be picked for any project, so mismatches reached Costpoint.

  • Closed projects and accounts lingered in the list.

What we did

A scheduled sync that builds the choice from Costpoint

  1. Map the codes

    Agreed which projects and accounts count as active, and how each one reads.

  2. Sync to Ramp

    Active projects and accounts load into Ramp from Costpoint on a schedule.

  3. Link them

    Each project shows only its own accounts, in a two-level dropdown.

  4. Keep it current

    Codes that close in Costpoint drop out of Ramp on the next run.

Related insights

Working through a similar problem?

Talk through your operations with us and we'll agree where to start.

Get started