Accounting System Design & Procedure Setup

It means building the structure your bookkeeping runs on before — or instead of — just recording transactions into whatever chart of accounts happens to exist. That includes designing account codes that reflect how your business actually earns revenue and spends money, writing down the step-by-step procedure for recurring tasks like invoicing and payroll, defining who can approve what, and configuring your accounting software to match that design. The result is a system where correct numbers come out because the structure supports it, not because one experienced person is holding it together from memory.

Having software running and having a properly designed system are different things. Many UAE companies set up a chart of accounts by accepting the software's default template, or copying one from an unrelated business, and never revisit it. Symptoms that the underlying design — not the software itself — is the problem include: monthly reports requiring manual reclassification to be useful, recurring VAT categorisation errors, no documented procedure for who approves what, and an auditor repeatedly raising the same findings year after year. Software migration without addressing the design just moves the same structural problems into a new platform.

We tag account-level VAT treatment at the design stage — separating standard-rated, zero-rated, exempt, and out-of-scope supplies distinctly on the revenue side, and flagging input VAT recoverability restrictions (such as those applicable to entertainment expenses and certain motor vehicle costs) on the expense side — so that VAT categorisation is correct at the point a transaction is recorded, rather than being reconstructed or corrected at return-filing time. This materially reduces the VAT return preparation effort every period and reduces the risk of categorisation errors that can trigger an FTA query.

UAE Corporate Tax, applicable at 9% on taxable income above AED 375,000 (0% below that threshold, with a separate Qualifying Free Zone Person regime for eligible free zone entities), is computed from the company's financial statements — which are only as reliable as the underlying chart of accounts and transaction classification. We design expense categories that map cleanly to deductible and non-deductible classifications under Corporate Tax rules, structure related-party and connected-person transaction accounts separately to support transfer pricing documentation requirements, and — for free zone clients pursuing the 0% Qualifying Free Zone Person rate — separate qualifying from non-qualifying income streams from the outset.

The design itself — chart of accounts structure, procedures, and controls — is software-agnostic; we design it around your business first. We then configure it into whichever cloud accounting platform suits your scale and complexity — commonly Zoho Books, QuickBooks Online, or Xero for our UAE clients, all of which support UAE VAT-compliant invoicing and reporting. The choice of platform depends on transaction volume, whether multi-currency or multi-entity consolidation is needed, and integration requirements with any existing sales or POS system.

For a single UAE entity of moderate complexity, a realistic timeline is 6–8 weeks from initial discovery to a fully configured, trained, and operating system, including a post-implementation review at the one-month mark. Multi-branch or multi-entity groups, businesses with inventory and manufacturing costing requirements, or free zone companies with complex Qualifying Free Zone Person income-stream separation extend this timeline.

Both. New companies benefit from having the system designed correctly from the first transaction, avoiding the cost of a later clean-up. Established businesses commonly engage this when reporting quality has become a genuine operational problem, ahead of a first statutory audit, when switching accounting software, when scaling to multiple branches or product lines, or when repeated VAT categorisation errors or Corporate Tax computation uncertainty trace back to how the underlying system was built.

Written, step-by-step Standard Operating Procedures covering the recurring financial processes specific to your business — typically sales invoicing (including FTA tax invoice compliance requirements), purchase and expense approval, payroll and WPS processing, bank reconciliation, fixed asset capitalisation, and the month-end and year-end close checklist. Each procedure specifies what triggers the process, who is responsible for each step, what approval or review is required, and what evidence is retained.

An approval matrix documents who is authorised to approve transactions of what type and value — purchase orders, supplier invoice payments, expense reimbursements — before they are processed. Even a small company benefits from this because it removes ambiguity (and single points of failure) around who can commit company funds, and it is one of the first things an auditor or a bank conducting due diligence looks for as evidence of basic internal control. We design the matrix proportionate to the company's actual size, so a five-person start-up gets a simple, workable structure rather than a corporate-scale control framework it cannot realistically operate.

Training is a core part of the engagement, not an optional add-on. We run structured sessions with the actual staff who will operate the system — whether your in-house team, a PNPC outsourced bookkeeping team, or a hybrid arrangement — walking through each documented procedure hands-on within the configured software. A procedure document that no one has been trained on is functionally unused within a month.

For businesses carrying physical inventory, the design includes a stock control and costing procedure — typically FIFO (first-in, first-out) or weighted average costing, chosen based on the nature of the goods and how the business itself tracks stock movement — consistent with how VAT and Corporate Tax treat inventory movements, write-offs, and cost of goods sold. This is integrated with the fixed asset and general chart of accounts design so inventory valuation flows correctly into the financial statements each period.

Qualifying Free Zone Person status is not automatic — it depends on meeting specific conditions, including maintaining adequate substance in the UAE and deriving income that qualifies under the relevant Cabinet and Ministerial Decisions, and demonstrating this requires accounting records that clearly and separately track qualifying versus non-qualifying income streams. We build this separation into the chart of accounts from the design stage, so the company can substantiate its Qualifying Free Zone Person position if the FTA reviews it, rather than trying to reconstruct the split retroactively from commingled revenue accounts.

We deliberately design the chart of accounts and approval matrix to extend — adding a new cost centre, branch code, or authorisation tier — without requiring a full redesign. A system designed too rigidly around the business's exact current shape tends to require an expensive rebuild the first time the business changes meaningfully; we design for reasonable future growth from the outset based on what the client tells us about their expansion plans during discovery.

Yes, payroll and WPS are a specific component of the procedure documentation. This covers the monthly payroll processing procedure, WPS (Wage Protection System) salary transfer through an approved exchange house or bank as mandated by MoHRE, correct monthly accrual of end-of-service gratuity under UAE Labour Law (rather than only recognising it when an employee actually leaves), and — for DIFC-registered entities — DEWS (DIFC Employee Workplace Savings) contributions in place of standard gratuity treatment.

A properly designed chart of accounts and documented procedures give the external auditor a navigable, well-structured file to work from, which materially reduces fieldwork time, audit queries, and — often — the audit fee itself compared to an ad hoc system. We build the year-end close checklist specifically to feed into audit preparation: trial balance review, supporting schedules, fixed asset register, and bank reconciliations all structured to be handed to an auditor with minimal further work.

An experienced individual can absolutely design and run a good system — the risk is concentration: the system's quality depends entirely on that one person, and it typically exists undocumented in their working method rather than as something the company owns independently of them. PNPC's engagement produces a documented, transferable system — written procedures, a defined chart of accounts, a configured platform, and trained staff — that continues to function correctly even as personnel change, rather than depending on one individual's continued presence and memory.

Yes, and this is a common combination. Where a company has both a structural design problem and a historical backlog, we generally recommend closing the backlog first (or running the two in close parallel) so the newly designed system is not built on top of unreconciled prior-period figures. We scope this as a single coordinated engagement rather than two disconnected projects, so the reconstructed historical data flows directly into the new chart of accounts structure rather than needing to be remapped separately.

Fee is scoped based on business complexity — number of revenue streams, branches or entities, whether inventory or manufacturing costing is involved, headcount and payroll complexity, and whether software migration is included. We provide a written scope and fixed fee before work begins, based on the discovery-stage findings, rather than an open-ended hourly arrangement.

Most clients transition into an ongoing monthly or quarterly bookkeeping retainer that operates within the newly designed system once the design and implementation phase is complete — either with PNPC's own bookkeeping team, the client's in-house staff (whom we have trained), or a hybrid. We also recommend a periodic review — typically annually — to confirm procedures are still being followed as documented and to adjust the design incrementally as the business changes, rather than letting practice quietly drift from what is written down.

Yes — where related-party transactions exist with an Indian (or other overseas) entity, UAE Corporate Tax transfer pricing rules require these to be conducted and documented on an arm's-length basis, with specific documentation required above certain thresholds. We design separate, clearly identified related-party transaction accounts to support this documentation, and where the India-side entity is also relevant for Indian tax purposes, PNPC's Chennai, Bangalore, and Hyderabad offices coordinate directly with the Dubai team so both sides of the intercompany relationship are structured consistently.

Where headcount genuinely does not allow full segregation of duties — the classic small-business constraint where one or two people handle most financial functions — we design compensating controls: mandatory dual approval above defined value thresholds even with a small team, owner or director-level review of the bank reconciliation each month, and system-enforced access restrictions in the accounting platform so that, for example, the person recording a transaction is not also the sole person able to approve its payment. We size the control framework to what the business can realistically operate, not a template built for a much larger organisation.

Where a business regularly transacts in currencies other than AED — common for import/export and trading companies — we design the chart of accounts and platform configuration to correctly record foreign-currency transactions at the applicable exchange rate, track realised and unrealised foreign exchange gains and losses, and ensure VAT is calculated and reported in AED as required by the Federal Tax Authority regardless of the transaction's original currency.

The core methodology — discovery, chart of accounts design, procedure documentation, controls, configuration, and training — is the same regardless of licensing jurisdiction. What differs is the regulatory context layered on top: free zone entities may be pursuing Qualifying Free Zone Person status requiring qualifying/non-qualifying income separation, DIFC and ADGM entities have additional regulator-specific reporting considerations, and mainland companies licensed through the relevant Department of Economic Development may have different activity-specific record-keeping expectations depending on sector.

This is a common scenario — an outsourced bookkeeper can only be as effective as the chart of accounts and procedures they are working within. We frequently redesign the underlying system while the existing bookkeeping relationship continues, then hand over the improved structure for the bookkeeper (whether the existing provider or PNPC's own team) to operate going forward. The engagement is about fixing the foundation, not necessarily replacing whoever is currently doing the data entry.

The post-implementation review at roughly the one-month mark specifically checks whether the first live month-end close followed the documented procedures, and flags any gap between the design and actual practice while it is still small and easy to correct. Beyond that initial review, an ongoing bookkeeping retainer with periodic check-ins is the most effective way we have found to keep a system operating as designed rather than gradually drifting back to informal practice.

Yes. A well-designed system with clean segmented reporting, documented controls, and consistent historical categorisation is precisely what due diligence reviewers look for, and its absence is one of the most common sources of delay or renegotiation in a transaction. We design specifically with due diligence readiness in mind when a client tells us financing or a transaction is on the horizon — building the segmented reporting and control documentation an investor or lender's finance team will ask for, before they ask for it.

A software vendor or reseller is generally focused on getting the platform technically configured and functional — creating accounts, setting up modules — not on the underlying design judgement of how those accounts should be structured for your specific VAT treatment, Corporate Tax positioning, and management reporting needs. PNPC has been a practising Chartered Accountancy firm since 1986; our design work is reviewed by qualified accountants who understand how the structure will actually be used for tax compliance and financial decision-making, not just how to make the software run.

Both. A well-designed chart of accounts produces management-useful reporting as a byproduct of routine bookkeeping — branch-level performance, product-line profitability, or cost-centre spend — without requiring a separate manual reporting exercise each month. During discovery, we specifically ask what management currently cannot see from their existing reports that they would like to, and design the account structure and reporting templates to answer those questions directly from the general ledger.

Segregation of duties means no single individual controls an entire transaction cycle end to end — for example, the person who records a purchase invoice should not also be the sole person able to approve its payment, reducing both error and fraud risk. In a small company where full segregation is not staff-realistic, we design compensating controls instead — such as mandatory owner or director review of payments above a threshold, or system-enforced approval workflows within the accounting platform — so the control objective is still met without requiring headcount the business does not have.

Where a single legal entity operates from more than one physical location — a mainland branch plus a free zone branch, or operations across Dubai and Abu Dhabi — we design the chart of accounts with location or branch-level cost centres so performance and cost can be tracked by location, while keeping the entity's overall financial statements and VAT/Corporate Tax position correctly consolidated at the legal-entity level, since VAT and Corporate Tax are generally assessed on the legal entity as a whole rather than branch by branch.

We recommend the platform that fits the business's actual complexity and reporting needs — sometimes that means moving from a more expensive, over-specified platform to a simpler one that costs less and suits the business better; other times a growing business genuinely needs a platform with more robust multi-entity or multi-currency capability than its current low-cost tool provides. We are not tied to any single software vendor and do not receive referral commissions that would bias the recommendation.

This is common, particularly for newly incorporated companies without prior operating history to draw on. Where reporting needs are not yet clear, we design a chart of accounts with sensible, commonly useful segmentation (by product line or service type, where the business model suggests a natural split) and build in enough flexibility to add finer segmentation later without a full redesign, rather than either guessing at unnecessary complexity or defaulting to an overly generic structure.

Yes. The documented Standard Operating Procedures are delivered as a written manual — covering sales invoicing, purchasing, payroll/WPS, bank reconciliation, fixed assets, and month-end/year-end close — that the client retains as their own document. This is commonly shared with an external auditor at the start of a statutory audit engagement, and with a bank or investor during due diligence, as evidence of a properly controlled financial function.

In scope: chart of accounts design, documented SOPs for invoicing, purchasing, payroll/WPS, bank reconciliation and close, an approval matrix, fixed asset and inventory policy, software configuration, and team training. Out of scope, unless separately agreed: ongoing monthly bookkeeping execution (that becomes a retainer once the system is live), historical backlog reconstruction (a separate backlog accounting engagement), and formal tax return filing itself, which sits with our VAT and Corporate Tax service lines even though the system is built to feed them cleanly. We set out these boundaries in the engagement letter so the client knows precisely what is delivered and what happens next.

Weak source documentation changes the design work plan directly. Where invoices, contracts, or bank records are missing or disorganised, we first run a document-gap assessment during discovery and agree with the client how gaps will be closed — supplier re-issue requests, bank statement re-downloads, or a documented assumption where the original cannot be recovered. The chart of accounts and procedures are then designed to require the level of documentation the business can realistically produce going forward, while flagging where historical gaps mean an opening balance carries residual uncertainty that management should be aware of.

The engagement designs the accounting records so they support whatever is filed on EmaraTax — VAT returns, Corporate Tax returns, and tax-record amendments — but does not itself update your EmaraTax registration profile or file returns; that is handled through PNPC's VAT and Corporate Tax service lines, or by your existing tax advisor. This distinction matters because the FTA requires changes to key tax records — trade/legal name, principal place of business, and primary business activity — to be notified through EmaraTax within 20 business days of the change. So where discovery surfaces that the entity has moved office, changed its trade name, or added an activity but never updated EmaraTax, that is a live compliance exposure, not just untidy paperwork — we flag it immediately and can coordinate the amendment internally.

Corporate Tax record retention obligations mean the accounting system we design has to produce records that remain retrievable and evidentially sound for at least seven years, not just usable for this month's close. Practically, this shapes decisions like how supporting documents are filed and cross-referenced to ledger entries, whether scanned source documents are retained alongside the digital ledger, and how the chart of accounts and schedules are structured so a transaction from several years ago can still be traced back to its underlying evidence without reconstruction work.

During discovery we sample the client's actual sales and purchase invoices against the FTA's mandatory tax invoice content requirements, review how import documentation and customs declarations are currently captured, and check how credit notes are issued and linked back to the original invoice. Any recurring gaps — invoices missing required fields, import VAT not being correctly recorded for reverse-charge treatment, credit notes issued without proper linkage — are built into the new invoicing and purchase procedures as explicit checkpoints rather than left as a recurring manual correction.

The trial balance, the fixed asset register with depreciation schedules, the related-party transaction listing, and the deductible/non-deductible expense classification we build into the chart of accounts all feed directly into the annual Corporate Tax computation and return. We design the month-end and year-end close checklist specifically so these schedules are already reconciled and reviewed by the time the Corporate Tax return is prepared, rather than requiring a separate reconstruction exercise once a year at filing time.

Beyond the general QFZP income-separation point covered elsewhere, free zone status also affects which reporting the licensing free zone authority itself expects at renewal — some free zones require audited financial statements structured a particular way, and the substance requirements underlying QFZP status need to be evidenced in payroll, lease, and operational records, not just in the ledger's revenue split. We map these free-zone-authority-specific expectations during the entity and licensing review stage of discovery so the chart of accounts and supporting records satisfy both the FTA's QFZP conditions and the free zone authority's own renewal requirements.

Yes — a mainland trade licence's listed activities determine which revenue and cost categories the chart of accounts needs to separately track, particularly where the company holds multiple activities under one licence (trading plus services, for example) or where a specific activity carries sector-specific record-keeping expectations from its regulator. We review the trade licence and its listed activities during the entity and licensing review stage precisely so account groupings map to what the company is actually licensed and permitted to do, not a generic mainland template.

Where a business holds or regularly transacts through non-AED bank accounts, we configure the chart of accounts and platform to record each transaction at the applicable exchange rate at the transaction date, generate realised foreign exchange gain/loss entries on settlement, and revalue open foreign-currency balances at period end to capture unrealised gains and losses — all while ensuring VAT is calculated and reported in AED as the Federal Tax Authority requires, regardless of the invoice's original currency.

We create dedicated related-party and director/shareholder-loan account codes at the design stage, separate from ordinary trade debtors and creditors, so that intercompany and owner transactions are never commingled with arm's-length third-party balances. This separation is what makes Corporate Tax transfer pricing documentation and related-party disclosure requirements practical to satisfy — reconstructing which balances were genuinely related-party after a year of mixed postings is a materially harder exercise than tagging them correctly from the first entry.

An automated bank feed reduces manual data entry but does not eliminate the need for reconciliation — feeds can duplicate transactions, miss items during connectivity gaps, or misclassify a payment based on the counterparty name alone. We design a monthly reconciliation procedure that treats the bank feed as an input to be verified against the actual bank statement, not a substitute for review, with a documented sign-off evidencing that someone has actually confirmed the ledger balance agrees to the bank.

Before any go-live, we agree a documented opening trial balance with the client — reconciled bank balances, confirmed receivables and payables, an agreed fixed asset register with opening depreciation, and any related-party or loan balances confirmed against underlying agreements. This opening balance is signed off by management before the new chart of accounts starts recording live transactions, so there is a clean, agreed starting point rather than an assumed carry-forward from a previous, potentially flawed, system.

We design reporting templates during discovery around what management, a bank relationship manager, or an investor specifically needs to see — branch or product-line profitability, cash runway, debtor ageing, or covenant-relevant ratios — rather than a generic profit and loss and balance sheet. Because the chart of accounts is structured to capture this segmentation at the point of entry, these reports are produced directly from the ledger each month without a separate manual reporting exercise layered on top.

The year-end close checklist we build is designed with statutory audit fieldwork in mind: a reviewed trial balance, supporting schedules for each material balance sheet line (fixed assets, receivables, payables, related-party balances), bank reconciliations for every account, and a documented list of judgement areas and estimates the auditor will want explained. Handing an auditor this pack at the start of fieldwork, rather than a raw ledger export, is what materially reduces the number of audit queries and the time (and often the fee) the audit takes.

We design a dedicated director/shareholder current account in the chart of accounts specifically to capture drawings, personal expenses paid through the company account, and any repayments, keeping these entirely separate from operating expense accounts. This matters both for Corporate Tax purposes — personal expenses run through the company are generally not deductible business costs — and for basic financial statement integrity, since commingled personal and business transactions are one of the fastest ways to undermine an otherwise well-designed set of books.

Documented approval evidence — who authorised a purchase, at what value, against what supporting invoice — is what allows the business to demonstrate that expenses were genuinely incurred for business purposes, which matters directly for Corporate Tax deductibility and for surviving an auditor's or the FTA's scrutiny of a specific transaction. Without that evidence trail, even a legitimate business expense can become difficult to substantiate months or years later when someone asks for proof of why it was incurred and who approved it.

Yes — as part of the design and initial data-quality review, we request statements directly from major customers and suppliers and compare them against what the client's ledger shows as outstanding, which frequently surfaces invoices booked twice, payments applied to the wrong invoice, or balances that were simply never recorded. We build a periodic third-party statement reconciliation into the ongoing procedure for material accounts, rather than relying solely on internal records, which are only as reliable as what was actually entered.

The main drivers are the number of legal entities and bank accounts involved, whether the business carries inventory requiring a separate costing procedure, how many revenue streams and related-party relationships exist, the quality and completeness of existing source documents, and how quickly the client's team is available for the discovery interviews and training sessions. A single-entity, single-branch business with clean records and a responsive team routinely finishes at the faster end of the range; a multi-branch group with inventory and unresolved historical gaps extends it.

Fee is driven by the same complexity factors that drive timeline — number of entities, branches, and bank accounts, whether inventory costing is required, headcount and payroll complexity, and whether software migration is part of the scope — plus the condition of existing records, since reconstructing a chart of accounts on top of disorganised historical data takes longer than designing one from a clean slate. We confirm the fee in writing after the discovery stage establishes actual complexity, rather than quoting a flat number before we have seen the business.

The handover pack includes the designed chart of accounts, the written SOP manual covering every documented procedure, the approval matrix, the fixed asset and inventory policy, the fully configured accounting platform with live user access set up, and a signed-off opening trial balance — plus the post-implementation review conducted roughly one month after go-live. It is a working, operating system with trained staff, not a set of recommendations left for the client to implement independently.

Once live, the business (or PNPC's bookkeeping team, if the client transitions onto a retainer) is expected to follow the documented month-end close checklist — bank reconciliations, accruals, fixed asset updates, intercompany confirmations, and VAT return review — on the cadence the procedures specify, and to flag any process change (a new bank account, a new revenue stream, a new hire in a finance role) so the design can be extended rather than quietly bypassed. We recommend an annual check-in specifically to confirm this discipline is holding.

PNPC operates under standard professional confidentiality obligations as a practising Chartered Accountancy firm, and during the engagement we configure user access within the accounting platform itself so that only authorised client staff and the specific PNPC team members working on the engagement have visibility into the records — access is not left open by default. Once the engagement concludes, platform ownership and administrative control remain with the client, and PNPC's access is limited to whatever ongoing arrangement (if any) is separately agreed.

Beyond the related-party account structure covered elsewhere, PNPC's Chennai, Bangalore, and Hyderabad teams and the Dubai team coordinate directly on chart-of-accounts terminology, intercompany transaction dating, and currency translation conventions so that the UAE and Indian entities' books reconcile to the same intercompany figures rather than each side using an independently designed structure that has to be reconciled manually at group consolidation time.

Yes — banks assessing a facility application typically request several years of consistently prepared financial statements, current management accounts, and debtor/creditor ageing, and a business whose chart of accounts and procedures produce these consistently and promptly each month is materially faster to support through a bank's underwriting process than one reconstructing figures on request. We design the reporting templates with this kind of lender request explicitly in mind where a client tells us financing is a near-term goal.

Investors and their diligence teams look for consistent historical categorisation, clean segmented reporting by product or branch, and documented controls — precisely what a properly designed system produces as routine output rather than a one-off exercise assembled for the data room. We build the segmented reporting and control documentation an investor's finance team will request as part of the standard design deliverables when a client signals that a raise or transaction is likely within the next year or two.

Yes — because the chart of accounts and procedures are built so every VAT treatment, Corporate Tax classification, and material balance can be traced back to its source document and the review evidence recorded at the time, responding to an FTA query becomes a matter of retrieving the relevant close-pack schedule rather than reconstructing the underlying transaction from scratch. This traceability is one of the core design objectives, not an incidental benefit.

Where software migration is part of (or follows) the design engagement, we test that the new platform correctly replicates the designed VAT tax-code mapping, approval workflows, and user-access segregation before go-live, and we run a parallel reconciliation of a sample close period in both the old and new systems to confirm the migrated opening balances and transaction history are complete and accurate. Migrating software without this testing step risks silently carrying over data errors, losing historical audit trail detail, or misconfiguring VAT codes in the new platform.