ERPNext Accounting in Jordan

A chart of accounts built for IFRS statements and management reporting

Jordanian companies generally prepare statements under IFRS, and groups with Gulf or foreign parents also report into a group chart. Your auditor confirms the framework; my part is making ERPNext produce what they need without reclassifying entries in a spreadsheet every quarter.

I start from the statements, notes and tax schedules, and work backwards:

• Account groups that roll up to each statement line, with account types set so receivables, payables, stock, tax and bank accounts behave correctly in ERPNext.
• Cost centers for departments or business units management tracks.
• Accounting dimensions for projects, clients or product lines, required on every posting where they apply.
• A group mapping report for a parent's chart, so no second ledger is needed.

For pharmaceutical and medical distributors, I add accounts and procedures for expired and damaged stock, so write-offs post with an approval trail and a batch reference rather than as unexplained adjustments. For technology firms, I separate revenue by stream, such as licenses, subscriptions, implementation and support, because those streams are recognized differently.

Dinar precision belongs in this stage too, and the ERPNext consultant Jordan page explains why. Standard features are described on the global ERPNext Accounting page.

Sales tax templates and JoFotara from the finance side

Jordan's general sales tax, special tax on certain goods and exempt or zero-rated supplies each need their own handling. In ERPNext, transaction templates set the default treatment, item-level templates override it for particular goods, and tax categories apply the right template from the customer or supplier record. Rates, scope and the treatment of exported services come from your tax advisor, and I test each case on real invoices before go-live.

The connection to JoFotara, the national e-invoicing system, usually comes from a community app or custom integration in ERPNext; planning it is covered on the parent ERPNext page. Finance still needs control once it runs:

• Customer data: the buyer's tax number or other identifier where required, captured before the first invoice.
• Status and reference fields on every invoice and credit note, with a report of failed or pending submissions.
• Correction rules so a rejected invoice is fixed by credit note or amendment in a consistent way.
• Print formats that show any code or reference the platform returns, if your advisor confirms it must appear.
• Monthly matching of invoice totals in ERPNext against the platform.

Which invoices are in scope, and from when, is for your advisor to confirm. If the app is weak, finance carries the risk, so the finance manager takes part in testing it, not only the developer. My testing method for connections like this sits under ERP integration.

Deferred revenue, projects and service contracts

Jordan's technology and services firms bill in ways that do not fit a simple invoice-equals-revenue model: yearly software subscriptions paid in advance, support contracts, retainers, milestone billing on implementation projects and recharges to Gulf affiliates. ERPNext supports deferred revenue at invoice item level. An item can be flagged for deferral, a service start and end date set, and the system posts recognition entries from a deferred revenue account over the service period. Deferred expenses work the same way on purchase invoices for prepaid licenses or insurance.

The design questions:

• which items are deferred and on what basis, as your auditor agrees;
• whether recognition runs automatically or is reviewed before posting;
• how contract changes, early termination and credit notes adjust the schedule;
• how projects carry costs, timesheets and billing so margin per project is visible.

ERPNext's project module links timesheets, expense claims and purchase costs to a project, and accounting dimensions can carry the project onto every ledger line. Combined with deferred revenue, finance can show recognized revenue, the deferred balance and cost by project. Contract accounting with many separate performance obligations may outgrow this, and I say so when it does. Recharges between Jordanian and Gulf companies use internal customers and suppliers, described on the multi-company ERP page.

Dinar banks, dollar receipts and post-dated checks

Post-dated checks remain part of commercial life in Jordan, alongside dinar and dollar bank accounts, especially in trading, pharmaceutical distribution and property. In ERPNext, a dinar account and a dollar account are simply bank accounts with different currencies; statement files are loaded with the bank statement import, and lines are matched to payments in the reconciliation screen. Automatic bank feeds for Jordanian banks are worth asking about, but plan on statement files until one has been shown working with your bank.

Post-dated checks need a deliberate design, since ERPNext treats a check as a payment reference rather than a document with its own life cycle. Options include:

• posting received checks to a checks-under-collection account and clearing them when the bank confirms;
• recording post-dated checks issued as payments with a future reference date, reported by due date for cash planning;
• a custom or community app for a full check register, including returns, replacements and bank charges.

The choice depends on check volume and how much control your finance manager needs. A register app is the more complete answer but adds something to maintain through upgrades. Dollar balances are revalued under your accountant's policy, with entries reviewed before posting. Currency structure in general is on the multi-currency ERP page, and the finance automation page covers automated matching.

Hosting, upgrades and who maintains the accounting code

An open-source license means no per-user software subscription, not no running cost. Hosting on Frappe Cloud or your own server, a support arrangement, developer time for custom apps and finance time for upgrade testing all need budgeting. With Jordan's software sector close at hand, in-house development is tempting; the risk is a ledger that depends on one developer's knowledge.

For the finance function, I set out:

• A custom app register: the JoFotara app, any check register, custom reports and print formats, each with a maintainer and a repository.
• An upgrade test pack: sample invoices, credit notes, deferred schedules, bank imports and tax reports rerun on a copy of live data before anyone approves the upgrade.
• Timing rules: no upgrades during a close or audit fieldwork.
• Backup and restore: a restore actually tested before year end, not assumed.

Support can come from Frappe, a Jordanian or regional partner, a freelancer or your own team; confirm scope and response directly with them. I hold no Frappe partnership and sell no hosting, support or licenses. A business that expects its software vendor to carry e-invoicing compliance should also look at Odoo Accounting in Jordan or a commercial product. See also the ERP consultant Jordan page and the Jordan overview.