Quick Answer
Straight-through processing (STP) rate measures the share of invoices that complete the full AP cycle without manual intervention. Global AP automation vendors commonly cite 80% or higher STP as a benchmark. In Indian mid-market B2B, four compliance-specific exception categories create structural friction that standard automation does not resolve: GSTR-2B reconciliation failures, TDS category boundary errors, IRN validation gaps, and multi-GSTIN routing mismatches. Achievable STP in India is lower than global benchmarks, is category-dependent, and is primarily determined by vendor base compliance health, not automation tool capability alone.
Every AP automation demo includes the same claim: "Our customers achieve 80% or higher straight-through processing." For a CFO evaluating AP automation, the question is not whether that number is accurate. It is whether it applies to an Indian B2B company processing 2,000 invoices a month from a vendor base with varying GSTIN compliance, TDS categorisation complexity, and e-invoice obligations.
It does not.
What STP rate measures, and where the 80% benchmark was built
Straight-through processing rate is calculated as the number of invoices processed without manual intervention divided by total invoices received, expressed as a percentage.
First-time match rate is the precondition for STP. The invoice must match the purchase order and goods receipt note on the first attempt; any mismatch routes the invoice to an exception queue, removing it from the STP count.
The 80%+ benchmarks cited by global AP automation vendors come from deployment data in US and European markets, per publicly reported deployment data from global AP automation providers. Those environments share two characteristics that Indian mid-market B2B does not:
- Invoice compliance is largely binary. There is no equivalent of GSTR-2B reconciliation, IRN mandatory fields, or multi-rate TDS withholding.
- PO-backed invoices dominate. In Indian B2B manufacturing and logistics, a significant share of invoices arrive without a matching PO, particularly for service contracts, recurring vendor payments, and freight.
Applying the benchmark directly to an Indian deployment produces a misleading target.
Why Indian B2B compliance creates four exception categories that break STP
GSTR-2B mismatch
GSTR-2B is the auto-populated ITC statement generated by the GST portal on the 14th of each month, reflecting supplier filings. If a vendor files GSTR-1 late, incorrectly, or with a wrong GSTIN, the corresponding invoice does not appear in the buyer's GSTR-2B. Under GST Rule 36(4) as typically interpreted, ITC cannot be claimed on invoices absent from GSTR-2B beyond the permitted variance. The invoice must be held until the supplier corrects the filing or the ITC exposure is accepted and provisioned.
Standard AP automation treats this hold as a manual exception. A compliance-native architecture triggers the hold automatically at invoice receipt, keeping the invoice outside the exception queue until GSTR-2B confirmation arrives.
TDS category boundary errors
Mis-categorisation under sections 194C, 194J, and 194H of the Income-tax Act, 1961 generates three categories of financial exposure in Indian mid-market AP.
Under Section 40(a)(ia) of the ITA, 1961, if TDS is short-deducted by applying a lower rate (for example, 2% under 194C instead of 10% under 194J(b) for professional fees), 30% of the entire invoice value is disallowed as a business expense. Interest under Section 201(1A) accrues at 1% per month from the date of short-deduction. Correction requires a TDS Correction Statement on the TRACES portal, reversal of original entries, and reissue of Form 16A to the vendor.
Section 194C applies to routine execution using manual labour or material manipulation. Section 194J applies when the service requires intellectual input, custom engineering, or specialised technical expertise. A maintenance contract for standard facilities falls under 194C at 2%. An annual maintenance contract for ERP servers or diagnostic medical equipment falls under 194J at 2% (technical services). A production house creating a bespoke corporate film falls under 194J at 10% (royalty/professional fees). An explicit amendment to Section 194C states that any payment covered under Section 194J cannot be classified as work under 194C, drawing a strict legal line between routine execution and expert application.
Under the Income-tax Act, 2025 framework, these sections transition to Section 393 with specific numeric payment codes (194C: codes 1005/1006; 194J(a): code 1026; 194J(b): code 1027; 194H: codes 1014/1015). TDS returns filed with legacy section numbers for current payments trigger immediate portal validation errors.
For AP teams processing invoices from vendors who provide both contracted services and technical consultancy, the category determination cannot be automated without a classification rule set mapped to each vendor-service combination. Standard AP tools do not carry this rule set. For a detailed breakdown of TDS rates and withholding obligations in AP, see TDS in Accounts Payable: Automating Deduction and Compliance in India.
IRN validation gap
Under the GSTN Advisory dated 5 November 2024, e-invoices must be generated within 30 days of the invoice date. Invoices presented to the buyer after this window carry invalid or absent IRNs. Accepting them without flagging creates ITC risk; processing them requires manual review to determine whether the supplier can regenerate a valid IRN or whether the invoice must be rejected.
Standard AP automation does not validate IRN date windows at invoice receipt. Compliance-native architecture does, blocking or flagging the invoice before it enters the AP workflow. The interaction between vendor portal submissions and IRN compliance is covered in detail in Vendor Portals and E-Invoicing Compliance: The IRN Validation Gap.
Multi-GSTIN routing failures
Large vendors in manufacturing and logistics often operate under multiple GSTINs across states. An invoice issued from a vendor's Tamil Nadu GSTIN routed to a buyer entity registered in Maharashtra triggers a cross-GSTIN mismatch. The ITC claim is valid only if the GSTIN on the invoice matches the buyer entity to which the supply is made. Routing errors require manual correction before the invoice can be processed.
What a realistic India STP target looks like
STP rate in Indian mid-market B2B varies by invoice category:
- PO-backed invoices from GST-compliant vendors with clean IRN records: 75 to 85% STP is widely observed in Indian mid-market deployments with compliance-native AP automation. This varies with vendor base compliance health.
- Non-PO invoices covering service contracts, freight, and recurring payments: 50 to 65% is a more realistic target. These invoices are more likely to carry TDS categorisation complexity and arrive without a matching PO.
- First-time invoices from new vendors: STP is near zero until vendor master data (GSTIN, PAN, TDS category, bank details) is verified and mapped. Vendor onboarding quality is the primary STP determinant for this category.
The primary levers for improving STP in India are vendor base compliance health, TDS classification rule set completeness, and IRN validation at receipt, not tool selection. A compliance-native architecture addresses all three at the invoice receipt stage. Standard AP automation layered on an ERP does not. For context on what this looks like after go-live, see ERP Go-Live in AP: Why the Work Starts After the Switch.
To see how compliance-native validation works at invoice receipt, book a demo.
Key observations
- Global STP benchmarks of 80%+ are built on US and European deployment data and do not account for Indian compliance architecture.
- Four exception categories are structural in Indian mid-market B2B: GSTR-2B mismatch, TDS category boundary errors, IRN validation gaps, and multi-GSTIN routing failures.
- TDS mis-categorisation under 194C vs 194J carries a 30% expense disallowance risk under Section 40(a)(ia) of the ITA, 1961, and mandatory interest under Section 201(1A).
- Realistic India STP targets range from 50 to 65% for non-PO invoices to 75 to 85% for PO-backed invoices with compliant vendor bases. These are directional, not guaranteed.
- STP rate in India is primarily determined by vendor compliance health and TDS master data accuracy, not automation tool capability.