ERPNext Accounting Consultant, Bahrain

Perpetual inventory and the accounts behind it

With perpetual inventory enabled, every stock movement in ERPNext posts to the general ledger as it happens. That is a strength for Bahraini traders and manufacturers, because the balance sheet always reflects the warehouse, but it means configuration errors flow straight into the accounts.

The accounts I set and test per company and warehouse:

• Stock in hand for each warehouse group, so the balance sheet can show stock by location or category if the auditor asks.
• Stock received but not billed, the clearing account between goods receipt and supplier invoice. A growing balance here usually means bills are not being matched to receipts.
• Stock adjustment for count differences and write-downs, kept separate from cost of sales so management can see shrinkage.
• Expenses included in valuation for freight and duty added through landed cost vouchers.

Valuation method matters too. Moving average suits most distributors; first in first out suits perishable or batch-tracked goods. Changing method after transactions exist is difficult, so I settle it with your accountant first.

Each month I run a stock and account value comparison and review the received-but-not-billed balance by supplier. Differences are investigated while the transactions are recent. The stock side of these businesses is covered further on ERP for inventory and warehousing.

Goods sold across the Causeway and beyond

Many Bahraini distributors sell into Saudi Arabia and other GCC markets as well as at home. How each of those sales is treated for VAT depends on where goods are delivered, who the customer is and what evidence you hold, and your advisor decides the rules. ERPNext's job is to apply those rules without relying on each salesperson's memory.

The configuration I use:

• Tax categories on customers, such as domestic, GCC business customer and outside GCC, set when the customer is created and reviewed periodically.
• Tax rules that select the right sales tax template from the customer's category and the shipping address, so a quotation is already coded correctly.
• Delivery links between the sales invoice, delivery note and shipping documents, giving the accountant a trail for zero-rated or out-of-scope sales.
• Required fields for the customer's tax number where your advisor says one is needed.

Returns and credit notes are linked to their original invoice so the reversal uses the same treatment. I test every route with sample transactions and review the result with your accountant before go-live. Where a sister company trades in Saudi Arabia under its own compliance rules, its setup is a separate design question, discussed at platform level on ERPNext in Bahrain.

Building and reviewing the NBR return

Bahrain's VAT return is filed with the National Bureau for Revenue, and its figures should come straight from posted ERPNext transactions. Standard reports get most of the way; the exact box layout usually calls for a purpose-built report or structured extract, which I specify with your accountant rather than leaving to spreadsheet adjustments.

The review the accountant and I run before the first live filing:

1. Sales figures by tax category agreed to the output VAT account.
2. Purchases agreed to input VAT, with non-recoverable amounts separated where your advisor says they apply.
3. Services bought from overseas suppliers checked for reverse charge: the purchase template adds output VAT and claims input VAT on the same bill, so both sides reach the return.
4. VAT paid on imports of goods traced to customs records and the clearing agent's invoices.
5. Credit notes confirmed against original invoices and the right period.

After filing, the accounting period is closed for that company so posted tax cannot shift. Over time the review becomes a short monthly routine your finance team runs, with the accountant checking exceptions. The treatment of each transaction remains your advisor's decision; my contribution is a system that applies it consistently. For the Odoo version of this work in Bahrain, see Odoo Accounting in Bahrain.

Banks, dated checks and supplier advances

Bahraini traders deal with a mix of bank transfers, card settlements and dated checks, and they frequently pay overseas suppliers in advance. ERPNext covers each, but the routines must be clear.

• Statement import: direct feeds for local banks are uncommon, so statements are imported as bank transactions using a fixed template per bank, then matched in the reconciliation tool to payment entries and journals.
• Dated checks: recorded as payment entries with the check's reference date, kept visible until the bank statement shows them, and listed by maturity for treasury planning.
• Returned checks: handled by cancelling the payment entry with a reason, reopening the invoice and posting the bank charge.
• Supplier advances: paid against purchase orders and allocated when the bill arrives, so the supplier balance and goods received but not billed both clear correctly.
• Foreign currency suppliers: held in their invoicing currency with month-end revaluation.

Because the dinar uses three decimals, sample statements from every bank are run through the import during testing, and each line is compared to the fils. Small differences tolerated early tend to hide bigger ones later. My finance automation page describes the general reconciliation approach.

Opening stock, opening balances and the first year-end

Bahraini companies move to ERPNext from Tally, QuickBooks, Zoho Books or older local packages. For goods-based businesses, the opening stock is as important as the trial balance, and the two must agree.

• Stock first: opening quantities and values per warehouse, batch or serial loaded through stock reconciliation, posted against a temporary opening account.
• Trial balance next: the remaining balances posted as an opening journal, with the stock account offset so the opening account clears to zero.
• Open documents: customer invoices and supplier bills created through the opening invoice tool with original dates and amounts.
• Checks and advances: dated checks and supplier advances loaded individually.

Every load is tied back to the legacy reports under my ERP data migration method. At the first year-end, a physical count is reconciled to ERPNext, adjustments are approved and posted, and a period closing voucher is entered once the auditor agrees the figures.

Product detail is on ERPNext Accounting. For how I work with Bahraini businesses more broadly, see the Bahrain hub and ERP consultant in Bahrain.