Skip to content
InsightsGet started

Case study

Ramp and Foundation Software, connected both ways

A construction company keeps Ramp's coding options in step with Foundation every day, and gets a month of approved card spend as a ready-to-import Foundation file.

Value to the client

Cost reduction
200hrs / yr
of month-end re-coding and import building
Our estimate
Risk mitigation
118
automated tests behind every release, so a change can’t quietly break month-end
By design

Our estimate assumes about 2 days a month of re-coding Ramp spend and building the Foundation import file by hand.

Josh Mullins

Managing Director

3 min read

Share

At a glance

Client
Not named
Industry
Construction
Services

Connected both ways

  • Foundation SoftwareJobs, GL accounts, and cost codes
  • RampCard spend and coding

Coding that matches Foundation, and a month-end file ready to import

Coding sync
Daily
Jobs, GL accounts, and cost codes
Import file
Monthly
Approved Ramp spend for month-end
Sync
2-way
Foundation to Ramp, Ramp to Foundation
Automated tests
118
Behind every release

Before

Coding options and month-end that ran on manual exports

  • Ramp's jobs, GL accounts, and cost codes had to be kept current by hand.

  • When the options fell behind, cardholders coded spend to the wrong place.

  • Month-end meant rebuilding approved card spend in Foundation's import format.

What we did

A daily coding sync and a monthly import file

  1. Map Foundation's data

    Jobs, GL accounts, cost codes, and purchase orders, with Foundation's formatting kept intact.

  2. Daily sync to Ramp

    Every morning, Ramp's coding options are updated to match Foundation.

  3. Monthly import file

    On the 1st, approved Ramp transactions become a Foundation import file for month-end.

  4. Run in production

    Live since May 2026, with error notices sent to the client's finance lead.

Related insights

Working through a similar problem?

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

Get started