Onfinity ERP Overview Core modules Productivity ERP for industries Editions

Onfinity ERP

Finance, operations and the factory floor. One system.

All of it on one data model: one set of masters, one chart of accounts, and every number tracing back to the transaction that made it. Sales, procurement and order-to-cash run on the same one.

Book a demo See what's inside

The transactional core

Six areas write to the ledger

This sets out what each area actually does, and shows the screen you would spend your day in. Everything else in Onfinity posts into these six.

Onfinity GL Journal: posted and unposted percentages, a pending action queue and recent journal entries with debit and credit totals — Financial Management · GL Journal

The financial core

Financial management

This is a full general ledger with accounting schemas, not a bookkeeping layer over a sales system. It is multi-company, multi-currency and multi-book from the first posting.

General ledger and journals
Accounts payable
Accounts receivable
Bank and cash management
Fixed assets and depreciation
Accounting schemas per book
Multi-currency revaluation
Consolidation across subsidiaries
Budgeting and commitments
IFRS and GAAP reporting
Statutory and tax reporting
Period close and audit trail

Onfinity product master: stock and availability showing on hand, reserved, on order and available to promise across warehouses — Inventory · Stock & availability

Supply chain and inventory

Available-to-promise is calculated from what is on hand, what is already reserved and what is confirmed inbound, so the date your sales team quotes is the date the warehouse can actually meet.

Multi-warehouse and locators
Lot and serial tracking
Available-to-promise
Replenishment and min/max
Landed cost allocation
Stock counts and adjustments
Internal transfers
Attribute sets and variants
Costing: standard, average, FIFO
Shipment and receipt confirmation

Onfinity goods receipt: lines received against a purchase order with quantities and locators — Procurement · Goods receipt

Procurement

Requisition to payment runs as one document chain. Three-way matching compares the order, the receipt and the invoice without anyone exporting a spreadsheet to do it.

Requisition and approval routing
Request for quotation
Purchase orders and releases
Goods receipt and returns
Three-way matching
Vendor master and terms
Blanket and contract purchasing
Receipt ageing and GRNI
Vendor performance
Multi-organisation buying

Onfinity accounts receivable invoice list with customer, status and amounts — Order to cash · Customer invoice

Order to cash

A single numbering chain runs from order to collection, so a question about an invoice leads straight back to the shipment and the order, with no lookup table in between.

Sales orders and quotations
Price lists and discount schemas
Fulfilment and shipping
Customer invoicing
Credit limits and holds
Collections and dunning
Cash application
Revenue recognition
Commissions
Returns and credit notes

Onfinity CRM opportunity record with pipeline stage, value and linked activity — Sales & CRM · Opportunity

Sales and CRM

The customer record that the invoice posts against is the same record the salesperson works in. The CRM is part of the ERP, so the two are always in step.

Leads and opportunities
Pipeline and forecasting
Quotations and contracts
Activities, calls and email
Campaigns
Service requests and SLAs
Customer portal
Territory and team assignment

Reads, in one run

Open sales orders
Demand forecast
Safety stock levels
Reorder policy per item

Writes, as drafts

Production orders
Purchase orders
Consolidated per supplier
Held for your approval

Diagram · one MRP run

Material requirements planning reads every source of demand in a single run rather than one at a time, then proposes what to make and what to buy. Every draft waits for your approval before it reaches the shop floor or a supplier.

Bills of material, multi-level
Routings and work centres
Production orders
Shop floor reporting
MRP: regenerative and net change
Lot-for-lot and consolidation
Capacity and planning horizon
Standard and actual costing
Work-in-progress valuation
Subcontracting

On the same ledger

Eight more modules post into the same ledger

A payroll run posts to the general ledger. A work order consumes the stock and books the labour. A project captures both. These are modules of one system sharing one set of masters, not separate applications bridged onto it.

HR and payrollRecruitment to payslip, attendance, leave, claims, performance Service and maintenanceRequests, work orders, scheduling, spares, contracts Asset managementAsset register, condition, depreciation, downtime ProjectsStructure, resources, time and expense, progress billing Point of saleTills, shifts, offline capture, stock at the counter Document managementCapture, versioning, retention, documents on the record DashboardsActionable widgets on the live tables, one click from the record CanvasNew windows, tables and processes without writing the underlying code

Why the numbers agree

Enter it once, and it updates everything

A goods receipt moves the stock, accrues the liability, closes the purchase commitment and lands in the payables ageing. That is one transaction, entered once.

1Goods receipt Warehouse confirms 44 of 44 against PO 800027

2Stock moves On hand goes up, on order goes down, and available-to-promise is recalculated

3Liability accrues The goods-received-not-invoiced account posts to the ledger at landed cost

4Payables sees it It appears in the payables ageing and in three-way matching the same second

Separate applications reach the same answer after a nightly sync and a reconciliation somebody maintains. On one ledger it happens inside the transaction itself.

Getting it live

Adopt the standard, keep what makes you different

Most of what a company does runs well on standard process, and that is where the improvement comes from. What genuinely sets you apart — numbering, approval routes, the fields your industry needs, the documents that have to be worded a particular way — stays configuration here, held in the application dictionary rather than in code. AURA drafts it from documents you already use, and your team approves every entry before it applies.

Step one

Describe how the company works

Bring the chart of accounts, a purchase order, an invoice layout and the approval rules as they stand today.

Your team does this, using documents you already have

Step two

AURA drafts the configuration

Document types, numbering, approval routing, fields, validation and print formats are all configuration entries. AURA drafts them and shows you each one it proposes.

AURA does this, and shows you every change before it is applied

Step three

Rehearse a real month

Post a month of your own transactions and reconcile them before anything goes live. The configuration that comes out of that month is the one you start on, running on the standard product.

Both teams do this together, on the standard product

Every change is a configuration entry that the next release still reads, so you stay on the standard product and your upgrades stay routine.

Before you shortlist

The questions that come after the feature list

Functionality is where an evaluation starts. These are what it usually turns on.

Where it runsAzure, Oracle Cloud, AWS, or your own servers. The same product either way. The source is openYou can read it, extend it and keep running it. Staying is a decision, not a requirement. Who stands behind itTÜV certified, 15,000+ people in the community, partners in Germany, Canada, India and Portugal. What it costsPer user, per month, with the editions and what each one includes set out in full.

See it running on your own data

We will spend thirty minutes on your figures and your processes, and you can ask the questions you would ask in a real evaluation.

Book a demo See what it costs