ERPNext Accounting Consultant, Kuwait

Roles, permissions and separation of duties

Kuwaiti finance teams are often small relative to the number of companies they serve, so the same accountant may handle purchases for one entity and payments for another. ERPNext can support that safely, but only if access is designed rather than inherited from the administrator's defaults.

I start with a task inventory: who raises supplier invoices, who records receipts, who prepares payments, who approves them, who posts manual journals and who reconciles each bank. From that I build a role matrix and translate it into ERPNext:

• Role profiles that grant the doctypes each job needs and nothing more.
• User permissions that restrict a person to particular companies, cost centers or branches, so a branch accountant sees only that branch.
• Separate roles for creating and submitting sensitive documents, so preparing and approving are different people.
• Restricted payroll accounts, so salary details are not visible in the general ledger to everyone with finance access.

The matrix becomes a short control document your auditor can review. When people change jobs, finance updates the matrix first and access second. This sounds bureaucratic, but in a family group where staff move between companies regularly, it is the simplest way to keep access aligned with responsibility. The platform-level view of Kuwaiti group structures sits on ERPNext in Kuwait.

Payment approvals before the bank portal

Most Kuwaiti companies release supplier and salary payments through their corporate banking portal, which has its own approval layers. The gap is usually upstream: a payment is keyed into the portal from an email or a spreadsheet, and ERPNext is updated afterward, if at all. The ledger then trails the bank and duplicates slip through.

I reverse the order so ERPNext is where a payment is decided:

1. The payables accountant prepares a payment entry against approved supplier invoices, or a batch of entries for a payment run.
2. A workflow sends it for review, where the reviewer sees the invoices being settled, the supplier's balance and any open advances.
3. An authorized approver submits it; only then is the payment keyed into, or exported toward, the bank portal.
4. When the bank statement arrives, the bank transaction is matched to the submitted entry in the reconciliation tool.

Manual journals follow a similar workflow, because they are the easiest way to move money between accounts without a supporting document. Thresholds can route larger amounts to a senior approver. Approval workflows across other documents are discussed on ERP approval workflows, and an Odoo perspective on Kuwaiti finance sits on Odoo Accounting in Kuwait.

Outlet cash, POS closing and daily deposits

Retail, food and service businesses in Kuwait often run many outlets, each handling cash, cards and KNET receipts every day. The accounting risk is not the sales themselves but the gap between what the till says, what reaches the bank and what finance records.

In ERPNext each outlet uses a point of sale profile with its own cash account and warehouse. The daily routine I set up:

• Opening entry with the float counted at the start of the shift.
• Closing entry at the end, where the cashier records the counted cash and card totals against what the system expects.
• Differences posted to a cash variance account per outlet, which the area manager reviews weekly.
• Deposits recorded as transfers from outlet cash to the bank, then matched to the bank statement.
• Card and KNET settlements matched to the day's card totals with fees posted separately.

Because the dinar uses three decimals, I check cash rounding rules at the till and confirm that small differences are posted consistently rather than absorbed into sales. Where outlets use a separate POS product, I define a daily summary import instead, with the same variance and deposit checks. The finance automation page covers the wider reconciliation method.

Audit trail, amendments and protected periods

ERPNext does not allow a submitted invoice or payment to be edited in place. It must be cancelled and amended, which creates a new version linked to the original. That is a strong control, and I make sure Kuwaiti finance teams use it as intended rather than looking for ways around it.

The supporting setup:

• Cancellation rights limited to a small group, with a reason captured on the amended document.
• Accounting periods closed per company after each month is reported, so postings into a closed month need a specific role.
• Attachments required on manual journals and supplier invoices above an agreed value.
• Document history reviewed monthly for cancellations and backdated entries, using standard reports.

Tax is light on the indirect side: I am not aware of any broad VAT operating in Kuwait today, though regional policy can shift and your advisor should confirm it. Some companies carry income tax on foreign-owned interests or profit-based contributions; I accrue each to its own liability using your advisor's figures, without computing them. At year end, once the auditor agrees adjustments, the year's profit is closed into retained earnings through a period closing voucher, and the year is locked.

Consolidated statements and opening books per company

ERPNext arranges companies in a tree: a parent with child companies beneath it. Consolidated financial statements can then be run for the parent, combining the children's results in the presentation currency. For a Kuwaiti group this gives the owners a combined view without a separate tool, provided two conditions hold.

1. Every company's chart maps cleanly to the parent's account structure, which I settle at design stage.
2. Intercompany balances agree and are eliminated in a way your auditor accepts. Elimination is often handled through agreed journals or a structured export, and I document the method rather than assume the report handles every case.

The opening position is built per company: trial balance at the cutover date, open customer and supplier documents, deposits and guarantees, staff advances and the indemnity provision, and stock per outlet or warehouse. Sources range from local accounting applications to QuickBooks and spreadsheets, and each load is reconciled before go-live using my ERP data migration method.

For product detail, see ERPNext Accounting. For how I work with Kuwaiti businesses in general, visit the Kuwait hub or ERP consultant in Kuwait.