FerrataOrion

Integrations

Built on the systems you already run.

Orion reads the GL from your ERP, statement lines from your bank and each run from payroll, into the same foundation Atlas, Apex and Cortex use. Every connection is set up with your instance and checked on your own records before your first close runs on it.

Connections · set up with your instanceHalden FoodsAll checked
SourceWhat it brings
SAP S/4HANAGL, journals, entitiesChecked
Operating •••• 2210Bank feed, dailyChecked
Payroll registerEach run, by departmentChecked
Atlas Apex CortexIn the foundationRead in place
Journals go back only when a person posts them, and are read back to confirm

Your ERP

What Orion reads, and what goes back.

ERPOrion readsGoes back, when a person posts
SAP (Business One and S/4HANA)Chart of accounts, trial balance, journal entries, entitiesJournal entries
Oracle NetSuiteAccounts, trial balance, journals, subsidiariesJournal entries
Microsoft Dynamics 365Chart of accounts, trial balance, general journals, companiesGeneral journals
RilletConfigured with Rillet when your instance is set upConfigured with Rillet when your instance is set up

Bank and payroll

The records outside the ERP.

01

Bank feeds

Set up with your instance, account by account.

02

Statement files

CSV, OFX and BAI2, read into one shape.

03

Payroll

Your payroll system's register or your ERP's payroll journals.

04

Budgets

From your ERP's budget or a file your team loads.

Every connection

Set up and checked before it counts.

  1. 01

    Set up

    With your instance, by Ferrata's engineers and your IT team.

  2. 02

    Checked

    On your own records: last month's trial balance read and agreed.

  3. 03

    Mapped

    Accounts, entities and departments, with you.

  4. 04

    In use

    Your first close runs on it.

What Orion works out, and what is yours

Orion does the arithmetic. People sign.

Reading runs on its own once a connection is checked. Every journal that goes back is posted by a person.

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 the GL, bank and payroll on schedule
  • Keeps each record as it came
  • Reads every posting back before it counts

Always a person

  • Every journal posted
  • Adding or changing a connection
  • Account and entity mapping

FAQ

Integrations, run end to end.

Which ERPs does Orion work with?

SAP Business One and S/4HANA, Oracle NetSuite and Microsoft Dynamics 365, with Rillet listed. Each connection is set up with your instance and checked on your own records before your first close runs on it.

What does Orion write back to our ERP?

Only journal entries a person posts: adjustments, accruals, payroll and reclasses. Each is claimed once, checked against the ERP first and read back to confirm it landed.

How does Orion get our bank data?

From your bank's feed, set up with your instance, or from the CSV, OFX and BAI2 files your bank already sends.

Which payroll systems does Orion read?

Orion reads your payroll system's register or the payroll journals in your ERP. Which one is set up with you at onboarding and checked on your own runs.

Is Orion certified by our ERP vendor?

No. Orion is an independent product. It is not certified by, partnered with or affiliated with SAP, Oracle, Microsoft or Rillet.

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.