What is an accounts payable exception?

An AP exception occurs when an incoming supplier invoice does not match the purchase order (PO) or goods receipt note (GRN) in terms of price, quantity, tax calculations, or vendor details.

How does exception handling protect business tax compliance?

By flagging and placing mismatched invoices in a review queue, it prevents claiming incorrect Input Tax Credit (ITC) under Section 16(2) of the CGST Act and protects the business from tax disallowance under Section 43B(h).

Can we set up approval hierarchies in Tally Prime?

Tally Prime supports basic user roles and security controls (Tally Vault/User Security). However, advanced multi-level approval routing based on invoice values requires integrated enterprise workflows. While TrulyInvoice does not handle multi-level approvals, it automates the manual data entry of vendor bills directly into Tally.

What are the common tolerances for pricing exceptions?

Pricing exceptions generally carry a 0% tolerance. Any price change must be authorized via a formal purchase order amendment before the voucher can be posted.

How should we handle tax rate mismatches on supplier invoices?

Tax rate mismatches must be resolved by checking the statutory HSN/SAC rate database. If the vendor has charged an incorrect GST rate, they must issue a corrected invoice or credit note.

Exception Handling in Automated AP Workflows: ERP & Tax Controls

Automating accounts payable is essential for processing high invoice volumes, but automation is only as good as its exception management rules. When supplier invoices carry wrong pricing, short-shipped quantities, or incorrect GST rate splits, posting them automatically into your ERP creates ledger errors.

Establishing a robust **exception handling playbook** with clear maker-checker limits ensures that discrepant invoices are flagged and resolved, keeping books audit-compliant.

1. Types of AP Invoice Exceptions

Invoice discrepancies generally fall under four main categories:

Unit Price Discrepancies: The unit price charged on the invoice is higher than the agreed rate in the Purchase Order (PO). This requires procurement approval.
Quantity Discrepancies: The billed quantity exceeds the physical units received and accepted in the Goods Receipt Note (GRN).
Tax Classification Mismatches: Mismatches between the HSN/SAC code GST rates or state codes (e.g. CGST/SGST billed instead of IGST).
Vendor Master Discrepancies: Invoices containing mismatched supplier bank details, PAN numbers, or inactive GSTIN registrations.

2. Detailed Exception Resolution Matrix

When an exception occurs, the system must determine the correct action based on the variance type:

Variance Type	Tolerance Limit	Default Action	Tax Action
Price Increase	0% (Zero tolerance)	Route to Procurement for PO Amendment	Hold payment u/s 43B(h) until resolved
Quantity Shortage	Within ±2% (bulk only)	Auto-adjust and book to shortage ledger	Claim ITC only on actual quantity received
Tax Rate Mismatch	0% (Zero tolerance)	Block invoice and request Credit/Debit Note	Do not claim ITC until correct rate is filed u/s 34
Rounding Difference	Within ±₹10	Auto-approve and round off	None

3. Case Study Scenario: Acme Corp Dispute Management

To illustrate exception routing in practice, let's analyze how Acme Corp handles a typical pricing dispute:

A vendor delivers steel coils with a Purchase Order rate of ₹50,000/ton. However, the supplier invoice lists a rate of ₹52,000/ton due to sudden market rate increases.

The accountant flags the variance, blocks posting to Tally Prime, and routes a notification to the purchasing manager. The manager verifies the contract terms and determines the price increase was not pre-authorized.

The system sends an automated dispute email to the supplier with linked contract details. The vendor agrees to the error and issues a revised invoice, which matches the PO on the next run and is posted to Tally with zero manual journal adjustments.

4. Standardizing HSN/SAC Codes in Multi-State Entities

For companies operating across multiple Indian states, procuring services (such as nationwide IT support or maintenance) creates additional exception risks. The place of supply rules u/s 12 of the IGST Act determine whether CGST/SGST or IGST is applicable.

If a vendor bills IGST from their Karnataka office to your Maharashtra warehouse, but the PO was configured under local CGST/SGST parameters, standard accounting packages will throw tax validation exceptions. Automating exception handling requires maintaining centralized HSN/SAC master directories that dynamically reconcile state codes based on vendor GSTIN prefixes.

5. Setting Up Maker-Checker Approval Hierarchies

To prevent unauthorized payments and maintain clear audit trails, businesses implement maker-checker approval controls:

AP Maker (Clerk): Responsible for scanning incoming invoices, verifying metadata extraction via AI OCR, and running initial validations. Maker enters data but cannot post vouchers.
AP Checker (Supervisor): Reviews transactions, checks HSN configurations, verifies GSTR-2B matching results, and approves vouchers within designated limits.
Head of Finance (CFO): Approves high-value vouchers, authorizes PO rate amendments, and resolves unresolved supplier payment disputes.

6. Tax and Statutory Implications of Mismatches

Handling exceptions incorrectly exposes businesses to several tax liabilities:

CGST Section 16(2): Claiming ITC on short-shipped goods is illegal. Claiming credit on undelivered inventory triggers tax disallowances during assessments.
Income Tax Section 43B(h): Holding vendor payments past 45 days due to unresolved disputes results in expense disallowances if the supplier is a registered Micro/Small enterprise.
TRACES TDS Penalties: Misclassifying services u/s 194C instead of 194J results in short-deduction liabilities.

7. MCA Audit Trail (Edit Log) Compliance

The Ministry of Corporate Affairs (MCA) mandates that all companies using accounting software must maintain a built-in **Audit Trail (Edit Log)** feature. Every modification, deletion, or correction of an accounting entry must be logged with a timestamp and user ID.

Manual ledger classification processes result in frequent entry corrections, creating a long edit log of reclassifications at month-end. This attracts heavy scrutiny from statutory auditors who audit edit logs for potential window-dressing.

AI ledger mapping solves this by validating the ledger allocation **before** the entry is posted to Tally Prime. This ensures the first posting is accurate, keeping edit logs clean and audit-compliant.

8. Configuring Exception Rules in Tally Prime

To manage invoice exceptions in Tally Prime:

Debit Note & Purchase Return Setups:

If an invoice is booked but a quantity shortage is identified post-delivery, create a **Debit Note (Alt+F5)** in Tally. Select **Purchase Return** under the Nature of Transaction. Map it to the original purchase invoice to adjust the outstanding balance and reverse the excess Input Tax Credit.

Stop typing invoices manually into Tally: Skip the manual data entry. Just upload your purchase bill PDFs or images, review the extracted values, and sync them directly to Tally Prime in a few clicks with TrulyInvoice. Keep your books audit-ready without the typing.