We’ve integrated our Sales Invoices with FBR’s Digital Invoicing (DI) system. In addition to sales tax, we are required to collect Advance Income Tax on certain eligible sales (e.g., under sections 236G/236H) and reflect it in the invoice total (inclusive of GST and Further Tax).
Since this is income tax, it cannot be treated as a sales tax code and must be excluded from DI sales-tax fields to avoid incorrect reporting.
Suggested Feature:
Please consider adding a built-in invoice-level field—similar to the existing Withholding Tax feature—to handle Advance Income Tax as a separate charge.
Desired Behavior:
A document-level percentage and/or fixed amount field applied to a selectable base (e.g., “Total incl. GST & Further Tax”).
Posts to a user-selectable liability account (e.g., “Advance Income Tax – 236G/H (Payable)”).
Appears as a separate line item on the invoice and printed documents.
Excluded from DI sales-tax payload, ensuring it doesn’t interfere with DI rate validations.
Supports custom labels and notes (e.g., “Advance Income Tax u/s 236G” with filer/non-filer rate distinctions).
Current Workaround:
We currently add a manual line posting to a liability account, but this is error-prone and complicates DI-linked workflows. A dedicated field would streamline compliance and improve accuracy.
This reduces the chance of inputting the wrong value.
If you already use an integration to create the invoice, then you should be able to have the integration add a new line item that performs the same procedure.
The moment a tax code of the Passthrough tax type is selected, it should grey out the Item, Account, Qty, and Unit Price field and calculate a tax amount won’t increase any other tax basis. The user would copy the sales line, then apply the tax code to achieve this. This maintains the current workflow of treating the Passthrough Tax as a separate line item.
The invoice itself can include additional information to make this clear:
@Asif_Hussain , could you please share a practical case example for Advance Income Tax (e.g., s.236G/H)?
What kind of invoice layout do you expect (e.g., a dedicated invoice-level field for this tax)?
How should the accounting journal entries ideally look for such a transaction?
Since this is also related to Digital Invoicing, could you try creating an invoice manually in the portal and share the resulting JSON output? That would help clarify how the system should handle it.
Hi we have started using another Accounting software in parallel which link invoices to fbr with no issue, attaching its screenshot, As you can see Advance tax is calculated at the end separately and is not sent to fbr, only data in bold line has been sent to fbr
Cant see Advance tax 2.5% i.e 20.53 Rupees in your screenshot, and it is not just a note as this is the actual amount we receive from customer i.e 841.82 Rupees
Since Advance Tax will be received from the customer, we can create a separate transaction to record it. In the example below, we use a journal entry to record Advance Tax. To adjust how it appears on the invoice, we can customize it using custom themes or footer script.
<script>
// Script ini berjalan di dalam iframe
document.querySelectorAll('table tbody tr').forEach(row => {
// Ambil semua sel di baris
const cells = row.querySelectorAll('td');
if (cells.length === 0) return;
// Cari sel yang mengandung teks "Journal Entry"
cells.forEach(cell => {
const text = cell.textContent.trim();
if (/^journal entry/i.test(text)) {
cell.textContent = 'Advance Tax 2.5%';
}
});
});
</script>
Suggested Feature:
Desired Behavior:
Current Workaround:
