Apex by Ferrata Labs
Quote to cash on your ERP. Worked by agents.
Apex prices quotes from your own price book, turns signed deals into sales orders, meters usage, bills and builds revenue schedules, all on the records already in SAP, NetSuite or Dynamics. Every invoice and journal lands in the ERP first. Agents draft and check. People approve.
Built to connect with SAP · NetSuite · Dynamics 365
- Quote
- Approve
- Sign
- Order
- Invoice
- Revenue
01 · Quote
Tooling set, 3 m × 3$48,576
Install and training$6,200
Service plan, 36 mo$41,400
Priced from the ERP price list $96,176
- Q-20401Northgate Freight$53,523.44 posted · schedule built
- Q-20409Ridgeback Civil$215,291.50 posted · schedule built
Illustrative deals. Not client data.
- 01Quote
- 02Approve
- 03Sign
- 04Order
- 05Bill
- 06Recognize
How a deal moves
One flow, one record, from the first quote to the last journal.
Apex reads what it needs from the ERP, does the work the ERP was never built for, and writes the result back as the ERP’s own documents. A person approves at the three points where money is committed.
Deal · Bill · Recognize
Every step of quote to cash, each one a place to start.
Each function stands on its own, and each one you add reads the records the last one brought down. The figures in these cards are illustrative.
CPQ on your price book
Items, price lists and customer terms come from the ERP. Ramps, options and usage commitments sit on top.
DealApprovals by rule
Discount, margin, term and clause rules send a quote to the person who owns that decision.
DealContracts, structured
A signed PDF becomes terms, phases and a schedule, each linked to its page.
BillUsage, from the ERP too
Deliveries, timesheets and equipment hours count as usage, beside events and warehouse imports.
BillInvoices posted to the ERP first
Calculated in Apex, checked against the customer PO, posted as an A/R invoice and read back.
RecognizeRevenue schedules
Built from your policy. Your accountant signs off each close before a journal posts.
RecognizeARR, MRR and NRR
Computed from the schedules themselves, so each number traces to a contract.
BillA portal for your customers
Invoices, usage, credits and contracts, behind a link for verified contacts.
Inside Apex
The screens your team works in.
A quote, an invoice and a revenue schedule from the same deal, as finance, sales operations and the controller see them.
Deal
A quote a rep edits, not starts
Lines from the price book, a ramp on the service plan, margin against the floor before it goes anywhere.
See how it worksBill
An invoice that has already met the PO
PO number, lines and remaining balance checked, tax code from the ERP, then posted and read back.
See how it works- PO 4500-8812 present
- Lines match PO, 3 of 3
- PO balance covers invoice
- Tax code from the ERP
Recognize
A schedule your controller can follow
The discount allocated by standalone selling price, each obligation with its method, the close locked when signed off.
See how it worksProcurement-led quoting
Quotes that survive a buyer’s process.
Manufacturers, distributors, contractors and carriers sell to procurement teams, not founders. A quote has to answer a tender, honor a price agreement and carry the freight. Each of these is a pricing model or a check on the same core, not a separate product.
Connects with
Built on the ERP you already run.
Apex reads from the ERP and writes back through one outbox: each write is claimed once, the ERP is read before anything is written, and the result is read back to confirm it. The ERP holds the posted record. Connections are configured to your own company codes when your instance is set up.
Apex is an independent product. It is not certified by, partnered with or affiliated with SAP, Oracle or Microsoft.
Agents propose, people approve
Eight agents that draft and check. None that post on their own.
Apex grows out of Ferrata’s Quill, which drafts quotes, and Swift, which turns purchase orders into sales orders. Rating, billing and revenue schedules are deterministic jobs with no model in them.
Contract intake
Reads a signed PDF or emailed contract and drafts the contract record and billing schedule, each field linked to its source page.
A person confirms the draft against the document before it bills.
Quote assistant
Drafts a quote from an inbound inquiry or a deal, priced from your book, and suggests ramps or options from the customer's history.
A rep reviews and sends it; discounts outside your rules go to the approver they name.
Invoice review
Checks each invoice draft for unusual lines, missing usage and prices that differ from the contract, and explains what it found.
Posting the invoice to the ERP waits for a person's release.
Usage anomaly
Flags spikes, drops and missing feeds in usage before a billing run, with the meter and period affected.
Held usage is billed only after a person accepts or corrects it.
Renewal
Drafts each renewal quote from the current contract, actual usage and your price changes, and states every change it made.
The account owner reviews and sends the renewal.
Email follow-up
Drafts short email reminders before and after an invoice's due date, written from the invoice's facts, and stops when it is paid.
Email only, on the schedule you set; anything beyond a reminder goes to a person.
Rev rec review
Explains why an amount was deferred or recognized and flags schedules that look wrong against the contract.
It never posts: journals wait for your accountant's sign-off.
PO matching
Matches the customer's purchase order (number, lines, remaining balance) against an invoice before it is sent or submitted to a portal.
A mismatch holds the invoice for a person to resolve.
Every agent stops at an approval gate until it has earned its way out of one. Nothing releases cash, commits spend or touches a customer without a person saying so.
Your dataModels that read your data run inside your environment, behind your firewall. No client data reaches a frontier lab.
Apex’s agents in detailIndustries
Built for how your industry actually prices.
Tenders, price agreements, rebates, retainage, per-shipment rates, fund fees. Apex starts from the industries Ferrata already serves, and from the ERPs they run.
One foundation
Start with one function. Everything after it is already in place.
Your company gets one Ferrata tenant: one model of your customers, items, contracts, invoices and payments, brought down from the ERP once. Start with quoting, usage billing, invoicing or revenue. Whatever you add next reads the same records, so nothing is re-implemented and nothing is reconciled between two systems.
How Ferrata’s foundation worksFAQ
Questions, answered plainly.
What is Apex?
Apex is quote-to-cash software built by Ferrata Labs. It quotes from your price book, routes approvals, turns signed deals into ERP sales orders, meters usage, calculates invoices and builds revenue schedules, all on the data already in SAP, NetSuite or Microsoft Dynamics 365.
Does Apex replace our ERP?
No. The ERP stays the system of record for customers, items, posted invoices, payments and the general ledger. Apex calculates what the ERP does not model well (ramps, usage, approvals, revenue schedules) and writes the results back: sales orders, A/R invoices, credit notes and journal entries.
Can we start with one function?
Yes, and most companies should. Start with quoting, usage billing, invoicing or revenue recognition alone. Apex brings your customers, items, invoices and payments down from the ERP into your Ferrata foundation once, and every function you add later reads the same records. Nothing is re-implemented.
What do the agents do, and what do they not do?
Apex's agents read contracts, draft quotes and renewals, review invoices, flag unusual usage, match customer POs and explain revenue schedules. They propose; a person approves in the Approval Queue. Calculations such as rating, billing and revenue schedules are deterministic jobs with no model in them.
Is Apex ASC 606 compliant?
Compliance is a judgment your accountant makes, not a property of software. Apex computes revenue schedules from the policy your accountant sets (obligations, standalone selling prices, methods), shows its working, and waits for sign-off on each close before a journal is posted to the ERP.
Where does our data go?
Your data stays in your Ferrata tenant and your ERP. Models that read it run inside your environment, behind your firewall. No client data reaches a frontier lab.
Does Apex take payments?
No. Apex does not process payments. Cash is applied in your ERP as it is today, and Apex reads the payments back so invoices, the portal and your metrics show what has been paid.
How long does it take to go live?
It depends on the function and the ERP, which is why the first conversation is about one workflow. Ferrata's standard engagement puts a first workflow on real transactions in under 90 days, behind an approval gate on every consequential action.
Related in Apex
- CPQConfigure, price and quote from the items and price lists already in your ERP.View
- Usage-based billingBill what customers used, rated at the price they signed, posted to your ERP.View
- InvoicingInvoices calculated in Apex, checked against the PO, posted to your ERP first.View
- Revenue recognitionRevenue schedules computed from your policy, journals posted to the ERP after review.View
- SAPQuotes, orders, invoices and journals on SAP Business One or S/4HANA.View
From Ferrata Labs
- Ferrata LabsThe firm that builds Apex, and builds AI agents into ERP-heavy businesses.
- How it worksAssess, Anchor, a first agent live in under 90 days, then your team.
- The platformThe Brain: retrieval, models and audit inside your own environment.
- Quill, the quoting agentReads every inquiry, prices it against your rules, drafts the quote.
- Swift, the order agentTurns customer purchase orders into clean sales orders.
Start with one function, or talk it through first.
Thirty minutes with Ferrata Labs on one workflow. You leave with a view of where Apex fits, and an honest answer if the sequencing is wrong and you should fix something else first.
Your pricing, approval and billing rules are your advantage, and they stay yours. Apex is configured to the way you sell and bill. You are not handing over a playbook or fitting into a template.