Sales & Purchase Ledger Bookkeeping (Domestic & Export/Import)

It covers the recording of every sales invoice issued and every purchase invoice received, coded with the correct VAT treatment, reconciled against bank statements and customer/supplier statements of account, and — for trading companies — cross-referenced against customs and shipping documentation. The output is a set of ledgers that support accurate VAT returns, Corporate Tax computation, and management reporting on receivables, payables, and margin.

A services company generally has one VAT treatment applying to most of its domestic sales and purchases. A trading company's sales ledger typically needs to distinguish standard-rated domestic sales, zero-rated exports, and sales to or from designated zones, while the purchase ledger needs to separately identify domestic purchases, imports subject to VAT at clearance or under the reverse-charge deferment mechanism, and purchases from other free zone or designated-zone entities that may fall outside the scope of VAT. Getting this categorisation right at the point of recording, rather than reconstructing it later, is the core value of a purpose-built ledger structure.

Under the UAE VAT Executive Regulations, a supply of goods can generally be zero-rated as a direct export where the supplier retains official and commercial evidence that the goods left the UAE (and, where relevant, the wider VAT implementing states) within the timeframe prescribed by the regulations. In practice this means a commercial invoice, a customs export declaration, and shipping documentation such as a bill of lading or airway bill. Without this documentation, the FTA can deny the zero-rating on audit and treat the supply as standard-rated, creating a retrospective VAT liability plus penalties.

Import VAT is generally payable at the point goods clear UAE Customs, though VAT-registered importers can apply to self-account for import VAT through their VAT return under the FTA's import VAT deferment (reverse charge) mechanism rather than paying it upfront at clearance, subject to the conditions the FTA sets for that scheme. Either way, the purchase ledger needs to record the import transaction with the correct VAT treatment tagged, cross-referenced to the customs declaration, so the VAT return correctly reflects the import VAT position for the period.

Yes, materially. Sales and purchases between two free zone or designated-zone entities, or transactions where goods remain within a designated zone and never enter UAE mainland circulation, can fall outside the scope of standard UAE VAT treatment under the designated zone rules. The ledger needs to distinguish these transactions clearly from standard-rated domestic sales and reverse-charge imports, both for VAT return accuracy and — separately — for the Corporate Tax Qualifying Free Zone Person qualifying-income analysis, which looks specifically at trading activity conducted with other free zone persons.

A Qualifying Free Zone Person is a free zone entity that meets specific conditions under UAE Corporate Tax law — including maintaining adequate substance in the UAE, deriving qualifying income, and not exceeding the de minimis threshold for non-qualifying income relative to total revenue — and is therefore eligible for the 0% Corporate Tax rate on its qualifying income, with the standard 9% rate applying above AED 375,000 of any non-qualifying income. Qualifying income for a trading business can include trading of goods with other free zone persons under specified conditions. Because this status depends on the composition of actual revenue, the sales ledger needs to be structured to identify and total qualifying versus non-qualifying income streams throughout the year, not just estimate the split at year end.

Every purchase that carries recoverable input VAT, or that is deductible for Corporate Tax purposes, needs to be recorded and supported by a valid tax invoice to be defensible under FTA rules — there is no materiality threshold below which the FTA disregards missing or incorrect documentation. In practice, we set up expense categorisation and, where volume is high, batch small routine purchases (such as minor office supplies) into manageable recording cycles rather than demanding invoice-by-invoice founder involvement, while still capturing the underlying documentation.

Monthly, at minimum, and more frequently for higher-volume trading businesses. A monthly cycle keeps the bank reconciliation, customer and supplier statement matching, and VAT categorisation current enough that errors are caught and corrected while the underlying documentation is still fresh and easy to trace, rather than discovered months later during VAT return preparation or an FTA query.

We work with cloud accounting platforms suited to UAE VAT compliance and the client's transaction volume and complexity — commonly Zoho Books, QuickBooks Online, or Xero, each of which supports UAE VAT tax coding, multi-currency invoicing, and bank feed integration. The right platform depends on transaction volume, whether multi-entity or multi-currency consolidation is needed, and integration requirements with any existing invoicing, POS, or inventory system the business already uses.

Yes. We begin with a review of the existing ledger against bank statements, customer and supplier statements, and available customs documentation to establish its actual state before taking over ongoing maintenance — rather than assuming the existing balances are correct and simply continuing from where the prior bookkeeper left off. Where material discrepancies are found, we flag them and scope a limited clean-up before transitioning to ongoing monthly bookkeeping.

Sales and purchase ledger bookkeeping is the ongoing, forward-looking discipline of recording and reconciling transactions as they occur. Backlog accounting is a fixed-scope project to reconstruct a period that was never properly recorded in the first place. Companies with a significant historical gap typically need a backlog engagement first to close that gap, and then transition into ongoing sales and purchase ledger bookkeeping so the gap does not reopen.

Invoices denominated in a foreign currency are recorded in the ledger at the exchange rate ruling on the date of supply, in line with UAE VAT and accounting requirements, with the AED-equivalent value used for the VAT return regardless of which currency the invoice is issued in. Where settlement happens on a different date at a different exchange rate, the resulting realised gain or loss is tracked separately and does not affect the original VAT-reported value of the transaction.

The invoice remains in the sales ledger and VAT return as issued unless a credit note is raised to formally cancel or adjust it — VAT is generally accounted for on supply, not on payment, under the UAE's standard VAT accounting basis. If the debt is genuinely uncollectible, UAE VAT law provides for bad debt relief allowing the previously accounted output VAT to be reclaimed, subject to specific conditions including that the debt has been outstanding for a prescribed period and written off in the accounts. We track disputed and ageing receivables specifically to flag when bad debt relief becomes available rather than letting uncollectible debts sit unresolved in the ledger indefinitely.

For trading companies with meaningful export or import volume, yes — we cross-reference sales and purchase ledger entries against the corresponding customs declarations where they are material to the VAT treatment applied, particularly for zero-rated exports (where the customs export declaration is part of the evidence trail) and for imports (where the bill of entry establishes the import VAT position). For lower-volume or domestic-only businesses, this level of customs cross-referencing is generally not necessary.

Where the business holds physical inventory rather than operating on a pure back-to-back or drop-ship model, we maintain opening and closing inventory records and build landed cost workings — incorporating freight, insurance, customs duty, and clearance charges — into the cost of goods sold calculation, so gross margin reporting reflects the true cost of imported goods rather than just the supplier invoice price. This feeds directly into both management reporting and the Corporate Tax taxable income computation.

Not a separate ledger, but distinct handling within the sales ledger. Marketplace settlement reports typically show net proceeds after platform fees and commissions are deducted, while the gross sale value (before fees) is what needs to be recorded as revenue for VAT and accounting purposes, with the platform fee recorded separately as an expense. Reconciling marketplace settlements against actual gross sales requires working from the platform's sales reports, not just the bank deposit amount.

Fee is scoped based on monthly transaction volume, the number of bank accounts and currencies involved, whether export/import documentation cross-referencing is needed, and whether Corporate Tax QFZP income segmentation is required. We provide a written, fixed monthly fee based on an initial review of actual transaction volume rather than a generic per-invoice rate that does not reflect the complexity of trading-company bookkeeping.

Yes. Where a group operates a mainland entity and a free zone entity together — a common structure for businesses that need mainland market access alongside free zone customs and tax advantages — we maintain both entities' ledgers with correct treatment of intercompany transactions between them, which themselves may carry specific VAT and transfer pricing considerations under UAE Corporate Tax's related-party rules.

For groups with both an Indian and a UAE entity trading with each other, we coordinate the UAE-side sales and purchase ledger with PNPC's India offices in Chennai, Bangalore, and Hyderabad, so intercompany invoices, transfer pricing positions, and DTAA-related withholding tax treatment are consistent on both sides of the relationship rather than reconciled independently and potentially inconsistently.

The same zero-rating evidence requirements apply regardless of export volume — the FTA does not apply a lower documentation standard to occasional exporters. We build the export documentation checklist into the sales recording process for every export sale, however infrequent, so an occasional exporter is not caught out at audit for a transaction that happened once and was not properly documented at the time.

Ledger bookkeeping produces the reconciled figures the VAT return is built from, and we review those figures specifically for VAT-return purposes before filing. Whether VAT return filing itself (submission on EmaraTax) is bundled into the same engagement or handled as a related but separately scoped service depends on how the engagement is structured — this is agreed and set out clearly in the written scope before work begins.

By building the ledger with the underlying evidence — export documentation, customs declarations, supplier and customer statements, bank reconciliation workpapers — retained and cross-referenced from the point of original recording, not assembled retrospectively when an audit notice arrives. An FTA audit typically requests supporting documentation for a sample of transactions across a period; a ledger built with documentation retained transaction by transaction responds to that request far faster and with far less risk than one where documentation has to be traced after the fact.

Revenue for accounting and Corporate Tax purposes is recorded net of VAT — VAT collected on a standard-rated sale is not company revenue, it is a liability owed to the FTA and must be shown separately in the ledger as output VAT payable, not blended into sales revenue. Recording sales gross of VAT overstates both revenue and, if not corrected, can distort the VAT return itself.

Yes — this is one of the most common uses of a well-maintained trading ledger beyond compliance. Banks assessing a letter of credit facility, invoice discounting, or a trade finance line typically want to see reconciled receivables and payables, evidence of consistent trading history, and clean documentation tying invoices to shipments. A ledger maintained to this standard on an ongoing basis is available on demand rather than requiring a scramble to assemble supporting documentation when a facility application arises.

Re-export transactions, particularly common for free zone trading companies acting as a regional distribution hub, are recorded with the import documentation on entry and the export documentation on exit, with the VAT treatment depending on whether the goods entered UAE mainland circulation at any point or remained within a designated zone throughout. This distinction materially affects whether import VAT was triggered on entry and whether zero-rating evidence is needed on exit, so the ledger structure needs to capture both legs of the transaction clearly linked to each other.

Standard monthly deliverables include reconciled sales and purchase ledgers, receivables and payables ageing reports, a VAT-ready summary of the period's transactions by category, and management accounts summarising sales, gross margin, and material variances from the prior period. Additional reporting — such as sales by product line, by customer, or by export destination — is configured based on what is actually useful for the founder's decision-making, not a generic template applied regardless of business type.

Onboarding for an active trading company with reasonably current records can typically begin within a few days of engagement, with the chart of accounts and platform setup completed within the first one to two weeks. Where a VAT filing deadline is imminent, we prioritise reviewing and reconciling the current period's transactions first to meet the deadline, and complete the broader onboarding and historical review in parallel rather than delaying the urgent filing.

Yes. The core bookkeeping discipline is the same regardless of whether the entity is licensed on the mainland through the relevant Department of Economic Development or in a free zone such as JAFZA, DMCC, RAK ICC, SHAMS, Ajman Free Zone, or others. What differs is the specific VAT and Corporate Tax QFZP treatment applicable to free zone entities, and the customs procedures specific to the free zone or designated zone the company operates in — both of which we account for in the ledger design for each client.

We flag this immediately rather than letting it sit unresolved in the ongoing ledger. Depending on the materiality of the discrepancy, this typically requires a Voluntary Disclosure to the FTA correcting the prior period's VAT position — filing proactively before the FTA identifies the issue itself is treated more favourably under the UAE's administrative penalties framework than being caught with unsupported zero-rating on audit.

A data-entry bookkeeper can record invoices and produce a trial balance. What a trading company's ledger genuinely requires beyond that is judgement — knowing when zero-rating evidence is sufficient to withstand an FTA audit, correctly applying the import VAT deferment mechanism, segmenting qualifying and non-qualifying income for Qualifying Free Zone Person status, and recognising when a discrepancy needs a voluntary disclosure rather than a silent adjustment. PNPC has been a practising Chartered Accountancy firm since 1986, and sales and purchase ledger engagements for trading companies are structured and reviewed by qualified accountants who understand these distinctions, not just data-entry staff working from a generic checklist.

In scope: recording and coding every sales and purchase invoice, credit and debit notes, bank and third-party statement reconciliation, export/import documentation cross-referencing, receivables and payables ageing, and the VAT-ready summary feeding EmaraTax. Out of scope by default (unless separately bundled): VAT return submission itself, Corporate Tax return filing, payroll and WPS processing, statutory audit, and forward-looking budgeting or cash flow forecasting — those sit with VAT/CT filing, payroll, audit, or virtual CFO engagements respectively. The written scope letter sets out exactly where the line falls for each client so nothing is assumed to be included that was never priced or resourced.

Where invoices, customs declarations, or bank statements are missing or illegible, we flag the gap immediately rather than estimating or assuming a treatment. For sales, a missing customs export declaration means we cannot safely apply zero-rating and will code the sale as standard-rated pending the document; for purchases, a missing tax invoice means the input VAT is treated as not recoverable until evidence is produced. If the gaps are extensive across a period, that signals the engagement needs a backlog accounting phase first rather than ongoing monthly bookkeeping layered on top of incomplete history.

Because each invoice is tagged with its VAT treatment — standard-rated domestic, zero-rated export, reverse-charge import, or out-of-scope designated-zone — at the point it is recorded, the totals needed for each box of the VAT return can be pulled directly from the ledger rather than manually re-sorted from a flat invoice list each period. We review the resulting return specifically for the export evidence trail and reverse-charge treatment before it is filed on EmaraTax, so preparation becomes a review-and-file step rather than a full reconstruction each tax period.

Taxable and exempt persons must retain the records supporting their Corporate Tax position for at least seven years after the end of the relevant tax period, so the FTA can verify taxable income or exemption status if it later reviews the period. This applies directly to sales and purchase ledger records, since they are the underlying evidence for both the VAT return and the Corporate Tax computation. We build retention into the handover pack — organised by financial year and cross-referenced to the return filed for that period — so a seven-year-old transaction can still be located and explained if the FTA asks.

We check that supplier tax invoices carry the supplier's Tax Registration Number, a clear description of the goods or services, the VAT amount shown separately from the value of supply, and an invoice date within the period being recorded — the baseline requirements for the input VAT to be recoverable. For import purchases we additionally check the invoice ties to a customs declaration and bill of entry reference. Purchases that fail this check are flagged rather than recorded with an assumed VAT treatment, since a defective tax invoice is one of the most common reasons the FTA disallows input tax recovery on audit.

The Corporate Tax taxable income computation starts from the accounting profit derived from the same sales and purchase ledger, adjusted for specific items the Corporate Tax law requires — such as certain non-deductible expenses, exempt income, and reliefs. Ministerial Decision No. 114 of 2023 sets the accounting standards and methods applicable for this computation, which is why we structure chart-of-accounts categories, revenue recognition, and cost allocation around what a defensible Corporate Tax schedule needs, not just what produces a plausible trial balance. For trading companies this includes correctly allocating landed costs to cost of goods sold, since margin distortion flows straight into taxable income.

For a free zone entity, the sales ledger needs an additional layer beyond VAT coding: separating qualifying income (including qualifying trading of goods with other free zone persons under the conditions the Corporate Tax law sets) from non-qualifying income, and tracking the de minimis threshold across the year, because this determines whether the entity retains the 0% Corporate Tax rate on qualifying income as a Qualifying Free Zone Person. A mainland entity's sales ledger does not carry this QFZP segmentation — its Corporate Tax exposure is simply 0% up to AED 375,000 of taxable income and 9% above that, without a qualifying/non-qualifying income split.

Each foreign-currency invoice is recorded at the exchange rate ruling on the date of supply for VAT and accounting purposes, converted to AED for the return regardless of invoice currency. Where the business holds foreign-currency bank accounts, receipts and payments in that currency are matched to the original invoice, and any difference between the invoice-date rate and the settlement-date rate is tracked as a realised foreign exchange gain or loss — kept separate from the VAT-reported transaction value so the original return figure is never retroactively distorted.

Intercompany invoices, shareholder loans, and owner-funded purchases are tagged separately from arm's-length third-party transactions as they are recorded, because UAE Corporate Tax's related-party and transfer pricing rules require these balances to be identifiable and, where material, supported by arm's-length pricing documentation. This matters particularly for groups running a mainland trading entity alongside a free zone entity, where intercompany sales between the two need a defensible pricing basis rather than being treated as routine trade invoices.

A bank feed pulls transaction lines automatically but does not know which sales invoice a receipt settles, whether a payment covers one purchase invoice or several, or whether a bank line is a genuine business transaction versus a bank fee, FX adjustment, or duplicate feed entry. Monthly reconciliation matches every feed line to the specific invoice it relates to, investigates unmatched or duplicate entries, and confirms the closing bank balance ties to the ledger — a step the feed itself does not perform.

Before recording a single new transaction, we agree the opening receivables, payables, and any related suspense balances against the prior provider's trial balance, outstanding customer and supplier statements, and the last filed VAT return, so the starting point is a documented, reconciled figure rather than an assumed carry-forward. Any discrepancy found at this stage is raised with the client and, where material, scoped as a limited clean-up before ongoing monthly bookkeeping begins.

We build the report around the decisions a trading-company owner actually needs to make each month — receivables ageing by customer to inform credit-limit decisions, payables ageing to manage supplier relationships and early-settlement discounts, gross margin by product line or export destination to spot which lines are compressing, and a short variance commentary flagging anything materially different from the prior period. This is configured per client rather than issued as a standard template, because a distribution business and a direct-export business need different breakdowns to be useful.

A structured file containing the reconciled sales and purchase ledgers for the audit period, receivables and payables ageing schedules, bank reconciliation workpapers, the export and import documentation cross-referenced to the relevant invoices, and a summary of any exception items or manual adjustments made during the year with the reasoning documented. Handing this over in an organised, indexed form — rather than raw ledger exports — is what minimises audit fieldwork time and reduces the volume of queries the auditor needs to raise.

Any payment or transfer identified as personal — director drawings, personal expenses paid from the business account, or shareholder loan movements — is recorded to a distinct drawings or related-party account rather than blended into ordinary purchase or expense categories. This matters for Corporate Tax purposes because personal expenditure is generally not a deductible business cost, and for VAT because input tax on personal expenses is not recoverable; miscoding it as a business purchase overstates deductible expenses and can overstate recoverable input VAT.

Ideally a documented approval trail showing who authorised the purchase order or invoice and who released the corresponding payment, separated so the same person is not requesting, approving, and paying without any check. Where a business has no formal approval workflow, we review a sample of purchases and payments to understand what actually happens in practice and recommend a minimum maker-checker split appropriate to the team size — this is a control observation, not just a tidiness preference, because unapproved payments are a common source of duplicate or fraudulent disbursements in growing trading companies.

We request statements of account directly from significant customers and suppliers and reconcile them against what the internal ledger shows, rather than relying solely on invoices entered by the business itself. This catches invoices the counterparty issued that were never recorded, duplicate entries, and timing differences — discrepancies that an internally-consistent ledger can hide entirely, since the ledger will appear to balance even when it is missing a transaction the other party has on record.

Speed depends mainly on: how current and complete the existing records are (a business with no historical gap onboards in one to two weeks; one with a backlog needs that closed first); how many bank accounts, currencies, and entities are involved; whether export/import documentation has been retained alongside invoices or needs to be traced separately; and whether the existing chart of accounts already distinguishes domestic, export, and import transaction types or needs to be rebuilt from a flat 'Sales'/'Purchases' structure.

Fee is scoped against actual monthly transaction volume, the number of bank accounts and currencies, whether export/import documentation cross-referencing is required, whether Corporate Tax QFZP income segmentation applies, and the condition of the records at handover — clean, current books cost less to maintain than ones requiring ongoing correction of a prior provider's miscoding. We confirm the fee in writing after reviewing actual volume rather than quoting a generic per-invoice rate that ignores trading-company complexity.

A completed chart of accounts mapped to VAT treatment categories, the cloud platform configured with bank feeds live, the first month's reconciled sales and purchase ledgers, a receivables and payables ageing report, a VAT-ready summary for the period, and a short process note explaining what PNPC needs from the client each month going forward (which invoices, statements, and bank records) to keep the cycle on schedule.

Timely provision of bank statements, outstanding sales and purchase invoices not yet captured in the cloud platform, credit/debit notes, and — for trading companies — customs and shipping documents for that month's exports and imports. The reconciliation cycle depends on receiving these within the agreed window after month end; delayed documentation is the most common reason a monthly close slips past its target date.

Access to the client's records within the cloud accounting platform and PNPC's internal working files is limited to the specific team members assigned to the engagement, with role-based permissions separating data entry from review and approval. Bank statements, invoices, and other sensitive documents are handled under PNPC's standard client confidentiality terms set out in the engagement letter, and platform access is removed at the end of the engagement or on request.

For groups trading between a UAE entity and an Indian entity, PNPC coordinates the UAE-side ledger with its India offices in Chennai, Bangalore, and Hyderabad so intercompany invoices, transfer pricing positions, and cross-border remittance and withholding tax treatment tie out consistently on both sides, rather than each side's books being reconciled independently and potentially inconsistently.

Banks assessing a letter of credit line, invoice discounting facility, or overdraft secured against receivables generally want reconciled receivables and payables ageing, evidence of a consistent trading history over several months, and documentation tying specific invoices to the underlying shipments they finance. We format the ageing and reconciliation reports specifically for bank submission for clients actively using or seeking trade finance, rather than producing reports designed only for internal management use.

Investor diligence typically tests whether reported revenue and margin can be traced to underlying invoices, whether receivables are genuinely collectible rather than aged and doubtful, and whether related-party transactions have been separately identified rather than blended into ordinary trading figures. A ledger maintained to the standard PNPC builds — VAT-coded at entry, reconciled monthly, related-party balances tagged — answers these questions from existing records rather than requiring a retrospective clean-up exercise once a term sheet is on the table.

Because the ledger is built with supporting documentation — export evidence, customs declarations, bank reconciliation workpapers, customer and supplier statements — cross-referenced to each transaction from the point of original recording, we can trace a queried balance or invoice back to its source documents directly from the retained file rather than reconstructing the trail after the fact. Response time depends on how far back the query reaches, but the documentation itself does not need to be rebuilt.

Before any migration, we verify that opening balances on the new platform match the closing reconciled balances on the old one, that VAT tax codes are correctly mapped to the same transaction categories (standard-rated, zero-rated export, reverse-charge import, out-of-scope designated-zone), that historical data needed for the current Corporate Tax retention period remains accessible, and that bank feed connections are re-established and tested with a live reconciliation before the old platform is retired.

Unresolved variances — an unmatched bank line, a missing invoice, an unusual payment, or a stock adjustment without clear support — are logged in an exception register with the issue, the amount, and what is needed to clear it, rather than being buried in a balancing journal entry. Material exceptions are raised with the client for a documented management decision before being cleared, so there is a recorded rationale rather than a silent adjustment that later looks unexplained.

Each month's reconciled ledger, ageing schedule, and management accounts roll forward into the year-end trial balance, so the annual financial statements are a consolidation of twelve already-reviewed months rather than a from-scratch reconstruction at year end. Where a statutory audit or Corporate Tax return is required, the closing schedules — receivables, payables, inventory, fixed assets where relevant — are already substantially prepared from the monthly cycle, reducing both the year-end workload and the risk of unexplained balances surfacing only at close.