Skip to content

What OnERP doesn't do yet

OnERP runs the order-to-cash path: partners, products, prices, orders, invoices, stock, fulfillment and tax. This page is everything a business might reasonably expect of an ERP that is not here.

It is the only page that lists absences. Nothing elsewhere in this manual apologises for a missing feature.

Area Status
Purchasing No purchase orders, no goods receipts against them, no supplier invoices. Suppliers exist as business partners, but nothing buys from them.
Accounting and general ledger No chart of accounts, no journal, no postings. Invoices carry tax and totals; nothing books them.
Payments Nothing records that an invoice was paid. No bank import, no reconciliation, no dunning, no open-item list.
Stock counting No physical inventory count, and no reconciliation of a counted figure against the recorded one.
Customer returns Undoing a warehouse pick is not a returns process. There is no return document, and nothing ties a correction crediting the goods to the movement bringing them back into stock.
Shipping and packing No delivery note, no packing list, no carrier integration, no tracking number. Shipping methods are a label on the order, with no rules behind them.
Currency conversion Prices apply only in the document’s exact currency. Nothing converts between currencies anywhere.
File attachments Nothing can be attached to a record.
Manufacturing, projects, HR, CRM Out of scope.

The assistant. Present and usable, and still moving. It has to be switched on by whoever runs OnERP. See The assistant.

Service accounts. API keys work and can be scoped by role. The surrounding tooling — usage history, rotation — is not there. See Service accounts.

  • Two draft invoices against the same order line each carry the full remaining quantity. Releasing both bills the line twice, and nothing prevents it.
  • Removing an order line an invoice already points at is rejected with an unclear message.
  • A correction issued after a VAT rate change credits at the new rate, not the rate the line was billed at, so the two documents do not net out. Nothing warns about it.
  • A sale from a country with no seeded VAT rates comes out untaxed rather than refused.

Two in particular cause lasting damage:

  • Do not book a count difference as an ordinary receipt or issue. It enters the ledger as a real movement with no explanation, and nothing distinguishes it later.
  • Do not edit or delete a movement to correct it. Post the opposing movement so both the error and the correction stay on the record.

Suggestions and gaps belong with whoever runs your instance. This page is kept current with what is actually built, not with what is planned.