See RPM In ActionYour ERP Knows What You Charged.RPM Shows You What You Kept.

RPM currently has live connectors for Acumatica, Business Central, NetSuite, and Microsoft GP. We are certified on the Acumatica and Business Central marketplaces. The API is open and documented; if your ERP isn’t on this list, your team or ours can build the connection. We typically prioritize new connectors when five or more customers are running on the same platform.

RPM uses a pricing tree, a hierarchy of rule sets applied in order. If RPM works through the entire tree and finds no valid price for a customer and item combination, it returns an explicit error rather than a silent zero or a wrong price. That error is visible to your pricing manager and flags that a rule needs to be created. You always know when something is missing. You are never guessing.

Every pricing rule in RPM can carry an effectivity date: a start date, an end date, or both. Rules outside their active date range are ignored automatically; no manual cleanup required. This means you can update pricing for new customers or new contracts while leaving existing legacy pricing in place for customers whose terms haven’t changed. Different customers can run under different pricing simultaneously, and each one transitions on its own schedule.

Rebates in RPM are configured as pricing calculations tied to the conditions that trigger them: vendor relationship, sales volume, customer performance, contract terms, or any combination. When a qualifying transaction occurs, the rebate is accrued in real time and can be mapped to a GL account for clean financial reconciliation. Your pricing manager sees rebate accruals as they build, not after the period closes. Rebate transparency is also visible at the line-item level, so reps and managers can see what’s accruing on any deal before it’s finalized.

RPM includes a catalog feature that generates a price list for any customer or group of customers based on the rules currently active for them. You select the customer, run the catalog, and RPM outputs every item and the price that would apply. That output can be exported to Excel or used internally for review before any pricing goes live in your ERP. Catalogs are a useful tool for validating rules before activating them – run a catalog, compare to your current pricing, confirm the output looks right, then activate.

RPM manages contract pricing – enforcing customer-specific contract terms automatically on every order – but it is not a contract lifecycle management system. If you have customer contracts with specific items, prices, and expiration dates, those can be loaded into RPM as a schedule. RPM will apply them to the right orders automatically and stop applying them when the contract expires. For full contract document management, redlining, and signature workflows, you would use a separate system alongside RPM.

RPM reads cost data from Acumatica via the API – including average cost, last cost, standard cost, or any other cost field your instance uses. You choose which cost field serves as the baseline for RPM’s calculations during implementation. When Acumatica’s average cost updates, RPM picks up the new value on the next pricing call and recalculates accordingly. This means your margin calculations stay current with your actual inventory cost without any manual intervention. The specific sync frequency and field mapping are configured during onboarding based on how your Acumatica instance is structured.