Tax withholding and currency applications

Receipt payment note and functional currency reconciliation with Pakistan examples

Use this guide when applying customer receipts, vendor payments or notes to open documents. Keep four amounts separate: invoice gross, withholding, cash applied in the invoice currency, and cash consumed in the bank-document currency. Then reconcile their functional-currency accounting.

The examples use a fictional Pakistan business with functional currency PKR. All rates are deliberately chosen training inputs, not current exchange quotes or prescribed Pakistan tax rates. A configured 18 percent chargeable tax and 5 percent withholding on the stated base illustrate the arithmetic only. The tax owner must determine the actual authority, rate, base, recoverability, recognition timing and effective date for each real supply.

Identify the three currencies

Foreign currency means a document differs from functional currency. Cross-currency application means the two linked documents have different currencies. Two USD documents in a PKR company are foreign-currency but same-currency to each other. Do not change a company's functional currency to make a settlement easier.

Check tax selection before saving the invoice

Review the resolved customer or vendor tax code on each actual transaction line. The two sides have separate partner/item defaults. Check chargeable and withholding components, active dates, percentage, rank, tax nature, account mapping and any Applied To dependencies. A displayed percentage alone does not establish the complete tax calculation.

An exclusive chargeable component is added to its applicable base. Inclusive tax, multiple ranks, tax-on-tax and withholding with selected chargeable taxes use different component calculations. Do not assume that a tax code name, a zero amount or an empty selection proves a legally zero-rated or exempt supply.

For inclusive pricing, agree an approved sample against the saved Base, Chargeable Tax and Total Incl. Tax before routine entry. The Inclusive setting affects the component formula; do not assume it automatically backs tax out of every entered unit price or that the entered price is the final payable total. If the saved result differs from the supplier/customer evidence, stop and resolve the configuration/calculation before issuing the document.

Distinguish chargeable tax from withholding

The WHT Recognition setting becomes locked when the tax code is used. If the approved recognition policy changes, maintain a new appropriate tax code through authorised setup; do not relabel historical tax details.

Work through an exclusive tax invoice

Assume a PKR1,000 taxable base, one exclusive chargeable component at 18 percent, no discount and no other dependencies. Chargeable tax is PKR180 and gross is PKR1,180. If there is no applicable withholding, an exact PKR1,180 cash application settles that invoice, subject to its saved state and processing.

For an ordinary customer invoice the illustrative relationship is receivable debit 1,180, revenue credit 1,000 and output-tax credit 180. For an ordinary vendor service invoice with fully recoverable input tax, it is expense debit 1,000, input-tax debit 180 and supplier liability credit 1,180. These are reconciliation relationships, not permission to assume every purchase tax is recoverable.

Apply cash when withholding was recognised on the invoice

Using the same base and chargeable tax, assume the approved withholding component is 5 percent of the PKR1,000 base: PKR50. Gross remains PKR1,180, but the invoice's net cash receivable/payable is PKR1,130 after invoice-timed withholding.

Do not deduct another PKR50 while applying the PKR1,130. Reconcile the invoice's recognised WHT separately from the bank cash and open balance. A cash receipt/payment saved for PKR1,180 would contain an extra PKR50 unless another valid purpose explains it; do not force that excess onto the invoice.

Apply cash when withholding is recognised at settlement

With settlement-timed WHT, the invoice initially retains the PKR1,180 gross open amount. The projected PKR50 withholding is reserved, so maximum cash is PKR1,130. Recognition follows the cash application, not just saving an unapplied receipt/payment.

After the first application, the residual PKR590 consists of PKR565 cash plus PKR25 projected withholding. Do not apply PKR590 as cash and withhold another PKR25. Review the saved application's Settlement WHT and linked protected transaction, the remaining invoice and the cash source.

Read the application lookup and amount controls

Labels vary between receipt, payment and note screens. Always read the currency attached to each amount; identical numbers are not proof of identical units.

Apply cash across different currencies

Assume a PKR company, a USD1,100 invoice at PKR280 per USD and a EUR100 receipt/payment at PKR310 per EUR. There is no tax, withholding, discount or prior revaluation in this example. The intended target settlement is USD110.

1. Save the cash document in its actual EUR bank currency and review the EUR100 unapplied balance and PKR31,000 functional value.
2. Select the intended USD invoice line in the eligible receipt/payment application screen. Review customer/supplier, location, type, number and remaining balance.
3. Enter USD110 in the target cash-applied field and EUR100 in Receipt Applied Amount or Payment Applied Amount. Review the derived rate: 100 divided by 110 = 0.909090909091 EUR per USD at the stored rate precision.
4. Check dates and available balances, then apply once. Reopen the target and source: invoice residual is USD990 and cash residual is EUR0 if there are no other applications.
5. Reconcile the target functional reduction of PKR30,800 with the cash-source carrying value of PKR31,000. The illustrative difference is a PKR200 customer-side gain or vendor-side loss. Inspect the actual linked journals and their posted state, not only a displayed FX number.

Use the two actual currency amounts as the primary check. If deriving an amount from a rate leaves a rounding residual, inspect the residual at company precision; do not force a hidden rounding adjustment or overwrite historical invoice rates. Bank fees are a separate supported event, not automatically an FX difference.

Combine foreign currency cash and settlement withholding

Assume the same fictional rates, but the target invoice is USD1,000 base plus USD180 tax, with USD50 settlement-timed withholding. Its gross open amount is USD1,180 and eligible cash is USD1,130. Apply USD565 cash using EUR500 from the bank document.

The withholding basis is the target invoice's approved tax design, not an arbitrary percentage of EUR cash. Reconcile cash, the protected withholding record and FX separately. Prior revaluation, different mappings, fees, rounding or other applications require their own actual reconciliation.

Apply foreign currency notes within the supported currency boundary

For customer notes, the ordinary application requires the same currency on credit and target. A USD100 credit at PKR285 applied to USD100 of an invoice at PKR280 uses cross rate 1, while its source and target functional values differ by PKR500. Reconcile the linked FX records as well as both USD residuals.

Vendor reducing notes have their own Apply controls; the normal lookup also filters the target currency when the source note is identified. The note Cross Currency Rate expresses target units per source-note unit, unlike the cash rate described above. Do not use the existence of rate columns to force a different-currency target that the supported lookup does not offer. The customer endpoint expressly rejects such a mismatch.

See customer notes and vendor notes. A ledger plug, artificial cash receipt or changed saved currency is not a supported note-application procedure.

Correct the originating application and inspect its effects

For an ordinary application error, use the supported application edit/remove action only where its dates, locks, document state, permissions and fiscal protections allow it. Reopen the invoice/note and cash-source balances afterwards. A removal restores availability; it does not cancel the original invoice, send money or automatically reverse a physical stock movement.

Settlement WHT creates protected linked records. Correct or unapply the originating receipt/payment application rather than deleting the system-managed WHT allocation. Recheck the resulting WHT generations, totals, history and journals before reapplying. If processing is uncertain, inspect saved identities/status before retrying; do not create a second payment or reuse the import as a reversal.

Separate realised FX from period revaluation

Cash and note application differences arise from settling linked balances at their respective functional bases. Period-end revaluation is a separate process for eligible open monetary balances. Do not run it merely to make two application fields agree, and do not post an additional manual FX journal for a difference already represented by linked system records.

Use Forex and GL setup and revaluation and close, with matching date cutoffs and review of any revaluation/reversal already posted. Refundable cash and non-monetary advance consideration can require different accounting judgments; do not infer classification solely from the name of an unapplied-control account. Refer to IAS 21 and the organisation's approved accounting policy.

Check the Pakistan fiscal and tax evidence

Confirm the applicable federal or provincial authority, customer/supplier registration, document classification, item/service, HS/UOM and required source reference before issuance or correction. A Pakistan address does not by itself determine the tax rate or mean that every service follows the federal goods-tax route.

Keep invoice accounting, FBR preparation/submission/acceptance, commercial note application and bank settlement as separate evidence. A customer credit/debit note must follow its permitted original-document reference and protection rules. Do not use vendor documents in the customer FBR route or assume that unapplying cash reverses a submitted fiscal document.

Use FBR's official digital-invoicing provisions and its user-manual entry point with the applicable current rules and approved country process. Never include production tokens, signing secrets or real tax identifiers in a shared training workbook or screenshot.

Reconcile the whole settlement before close

Compare invoice/note and cash source in their own currencies first. Reconcile open balances, source unapplied balances, withholding, application dates and linked accounting. Then compare the functional GL control, bank, recognised tax and FX accounts with the corresponding reports at the same cutoff. For goods, add stock and valuation reconciliation.

Continue with document and setup references

Customer invoices and notes, vendor invoices and notes, receipt fields, payment fields, tax-code setup, electronic invoicing, bank reconciliation, report parameters and bulk import safety.