SuiteCrunch · Insights
Practical, documentation-grounded write-ups on how NetSuite and Ramp actually work — where finance and operations teams get tripped up, and what to do about it.
Ramp's PO sync is one-way — POs flow from Ramp into NetSuite, not the reverse. Custom transaction line fields on the Items sublist, including those sourced from the Item master, cannot be written back to Ramp. Here's why, and what your options are.
Read the article →Custom transaction line fields on the Items sublist aren't imported by Ramp and can't be coded in the platform. Here's why, how to verify your field configuration in NetSuite, and the options for fixing it.
Read the article →Ramp's permission model is additive — custom roles can only layer on top of the base Employee role, never subtract from it. Here's what that means for PO editing controls, why the Employee base role can't be removed, and what the platform actually supports today.
Read the article →Every Ramp card is locked to one legal entity at issuance, and cardholders can't recode their own spend across entities by default. Here's why Ramp built it that way, what to do instead, and the exact request that gets it turned on.
Read the article →NetSuite doesn't measure AI consumption in tokens — it counts successful AI actions against a monthly pool. Where to find your usage, what counts toward it, and how SuiteProjects Pro limits work differently.
Read the article →More notes on NetSuite, Ramp, and finance systems design coming soon.
SuiteCrunch
If a NetSuite or Ramp quirk is costing your team time at close, it's usually a sign the underlying structure needs a second look — not just a workaround.