FerrataOrion

The platform

The close reads the records, not copies of them.

Every Ferrata product works on one foundation: your ERP's records kept as they came, and one model every product reads, in a database that belongs to your company alone. Atlas, Apex and Cortex already hold receivables, billing, revenue schedules, bills and payments there. Orion adds the GL, the bank and payroll, and runs the close on all of it.

Halden Foods · one foundationWhere Orion reads from
AtlasReceivables, receipts, promises
ApexBilling, revenue schedules
CortexBills, payments, accruals
  1. ReadsOne foundation, your own databaseEach record kept as it came, one model for every product, nothing copied
  2. FromYour ERP, bank and payrollGL, journals and entities · statement lines · each run
  3. ForOrionThe close, cash and the CFO’s view, on the same records

What Orion reads from each

Each product's records, where they already are.

SourceWhat it holdsWhat Orion uses it for
AtlasCustomers, invoices, payments, promises and disputesReceivables tied to the GL, DSO, receipts in the forecast
ApexContracts, billing, revenue schedules and journalsDeferred revenue tied to the GL, billing in the forecast, revenue in flux
CortexBills, purchase orders, receipts, payments and accrualsPayables and accruals tied, pay dates in the forecast, committed spend
Your ERPChart of accounts, trial balance, journals and entitiesThe GL side of every reconciliation, flux and the overview
Your bankStatement lines for every accountCash, matched and tied
PayrollEach run, by departmentThe payroll journal, the accrual and labor cost

Four layers

From the ERP to the CFO's view.

  1. 01

    Your systems

    The ERP, the bank and payroll, each connection checked on your own records.

  2. 02

    One foundation

    The records kept as they came, and one model every product reads.

  3. 03

    Atlas, Apex and Cortex

    Receivables, billing and revenue, payables: worked where they live.

  4. 04

    Orion

    The close and the whole view, on the same records.

Why one foundation

Add a product, and the data is already there.

01

Nothing copied

Orion reads Atlas's receivables where Atlas keeps them, not an export of them.

02

One figure

A balance is computed once, the same way, for every product that shows it.

03

Adding a product

A company that adds Orion later finds its records already in place.

04

The ERP stays the book

Orion reads from it, drafts journals for a person to post, and reads them back.

What Orion works out, and what is yours

Orion does the arithmetic. People sign.

The foundation keeps the records in step on its own. What is written back to your ERP is a person's call.

Orion matches, ties and calculates on its own, from the records already in your foundation. Every journal posted, every difference written off, every reconciliation signed off and every period locked is a person's decision, recorded with their name. Orion never moves money.

Orion works it out

  • Reads your ERP, bank and payroll into the foundation
  • Keeps each record as it came
  • Computes every balance one way, for every product

Always a person

  • Every journal posted to your ERP
  • Turning on any kind of write-back
  • Adding a connection

FAQ

One foundation, run end to end.

Does Orion copy data from Atlas, Apex and Cortex?

No. Every Ferrata product works on one foundation in your company's own database. Orion reads Atlas's receivables, Apex's schedules and Cortex's bills where they already are, so there is one figure for each, not two.

What does Orion read from our ERP?

The chart of accounts, the trial balance by period, journals and entities, and the budget where your ERP holds it. Each connection is set up and checked on your own instance when it is deployed.

Do we need Atlas, Apex and Cortex for Orion to work?

No. Orion reads your GL, bank and payroll on the same foundation. Where your company runs Atlas, Apex or Cortex, Orion reads what they hold as well, and each one's records become evidence in the close.

Does Orion write to our ERP?

Only journals a person posts. Orion drafts an adjusting, accrual or payroll journal with its support, a person with posting rights posts it, and Orion reads it back before it counts.

What happens when we add Orion after the other products?

Your records are already in the foundation, so Orion reads them from the first day. Only the close template, the bank, payroll and your thresholds are set up.

See Orion work on your own close.

Bring last month's close: the checklist, the reconciliations and the trial balance. We run it through Orion beside your team and show you where it would have tied, and give you an honest answer if the close is slow for a reason upstream that you should fix first.

Your close calendar, chart of accounts, thresholds, reviewers and sign-off order are yours, and they stay yours. Orion is configured to the way your team closes. You are not handing over a playbook or fitting into a template.