Three-Way Matching Software for Indian Manufacturing

The multi-tax-code problem

Most Indian manufacturers raise POs at a pre-GST base value: ₹100,000 for 500 units of a forged component at ₹200 each. The vendor's tax invoice arrives at ₹118,000 — base value plus 18% GST split across CGST and SGST (or IGST for inter-state supply). A naive line-amount comparison treats every taxable purchase as a value mismatch. Worse, the GSTIN on the invoice must reconcile back to GSTR-2B before input tax credit can be claimed under Section 17(5) of the CGST Act, which means the AP control needs to verify three things simultaneously: PO match, GRN match, and GSTR-2B presence.

Layer on TDS at source. Under Section 393(1)(a) of the Income Tax Act (payment code 1002), contractor and sub-contractor payments attract TDS at 1% (individual/HUF) or 2% (other). Section 393(1)(k) (payment code 1012) requires TDS at 0.1% on the purchase of goods above the threshold of ₹50 lakh per vendor per year. Works contracts governed by Section 143 of the CGST Act add another layer where principal-to-job-worker material movement must be documented separately from the invoice match.

The partial-delivery problem

Manufacturing supply rarely arrives in a single shipment matching the PO exactly. A 5,000-unit PO for forgings to an auto-component plant typically fulfils across three to five GRNs over two to six weeks, with rejected lots returned via debit notes and replenished against the same PO. Quality holds at incoming inspection further fragment the GRN trail — a GRN may be booked at 4,800 units accepted out of 5,000 received, with 200 units pending QC clearance for several days. The vendor's invoice may arrive against any of these GRN states.

The reconciliation challenge is that one PO line links to multiple GRN lines, which in turn link to one or many invoice lines — a three-way many-to-many relationship that breaks the simple PO=GRN=Invoice matching logic baked into most ERPs. Without an exception management layer that tracks PO ageing, residual quantity, GRN-to-invoice mapping, and return-debit reversals, AP teams resort to spreadsheets and manual telephone calls to vendors — the well-documented source of the 60-75% exception rate in Indian manufacturing AP exception management.

PO ingestion from any ERP

Purchase order headers and lines are pulled from SAP MM (ME21N output), Oracle Fusion Procurement, Tally Prime, Dynamics 365, Sage, Odoo, Zoho Books, or Busy via BAPI, IDoc, API, or daily file drop. The PO master is the anchor for matching — every GRN and every invoice traces back to a PO line and its open residual quantity.

GRN matching with partial-delivery support

One PO line to many GRNs; one GRN to many invoices. TransactIG handles the many-to-many mapping, tracks open residual PO quantity after each GRN, applies QC hold and rejection states, and links return debit notes back to the originating GRN.

Vendor invoice classification

Every invoice line is classified as GST-inclusive or GST-exclusive on ingestion. Taxable value is compared against the PO line; CGST, SGST, IGST, and CESS are reconciled as separate columns. The vendor GSTIN is cross-referenced against GSTR-2B for the period to validate input tax credit eligibility under Section 17(5).

Configurable tolerance band framework

Price, quantity, GST, vendor PAN, and rate tolerances are configured per material category, per vendor tier, and per plant. Critical and batch-controlled materials get tight bands (0% quantity); commodity items get broader bands (±2% price). Tolerance rules are versioned with effective dates for audit.

TDS at source — Section 393(1)(a) and (k)

Contractor and works-contract invoices are tagged for TDS under Section 393(1)(a) with payment code 1002. Goods purchases crossing the ₹50 lakh annual threshold per vendor are tagged under Section 393(1)(k) with payment code 1012. The deduction is computed before payment release, eliminating the post-facto recovery problem.

Audit-ready evidence file

Every matched line and every exception carries a fingerprint trail: PO reference, GRN reference, invoice reference, tolerance rule applied, variance code, maker-checker decision, and timestamp. The evidence file maps directly to internal audit, statutory audit (CARO 2020), tax audit (3CD), and ICFR control testing requirements.

Ingest PO, GRN, and invoice from ERP

Connectors to SAP MM-FI, Oracle Fusion, Tally Prime, Dynamics 365, Sage, Odoo, Zoho Books, and Busy pull purchase orders, goods receipt notes, and vendor tax invoices on a daily schedule. Vendor master, material master, GSTIN file, and rate contract file are loaded as reference data. Historical PO-GRN-invoice tuples are used to tune tolerance bands during implementation.

Match with configurable tolerance bands

The matching engine compares PO, GRN, and invoice on five dimensions — price, quantity, GST, vendor PAN/GSTIN, rate — with bands configured per material category and vendor tier. Many-to-many GRN-to-invoice relationships are handled natively. GSTR-2B cross-reference is applied for ITC eligibility under Section 17(5). TDS rules under Section 393(1)(a) and (k) tag the invoice for at-source deduction.

Exception queue with variance codes, ageing, maker-checker

Unmatched lines route to a structured exception queue tagged by variance code, with ageing buckets at 30, 60, and 90+ days. Maker-checker workflow enforces separation between AP analyst (maker) and AP manager (checker) for any release outside tolerance. The full evidence trail is exported to internal audit, statutory audit, and ICFR review files.

Project-mode capital goods POs

Long-cycle POs with stage payments, milestone billing, and price-escalation clauses linked to commodity indices. The match must handle milestone advance, against-shipment billing, and price-variation invoices against the same PO. Sub-contracted machining attracts Section 393(1)(a) TDS at source.

JIT supply and partial GRN

Daily JIT call-off against a quarterly blanket PO. Each PO line splits across 60+ GRNs in a quarter; invoices arrive weekly or fortnightly. Forging and casting sub-contracting attract Section 143 CGST works-contract treatment. PAN-vendor consolidation matters because tier-2 suppliers often share PANs across registrations.

Batch-controlled receipts

Zero quantity tolerance on batch-controlled APIs and excipients. QC hold and quarantine states fragment the GRN further. Vendor invoices must match GRN exactly post-QC release — and any rejection requires the debit note linked back to the original GRN for GST credit reversal.

Bulk receipts and weighbridge variance

Tanker and bulk receipts subject to weighbridge tolerance, density adjustment, and contamination deductions. Invoice quantity rarely equals PO quantity exactly. Tolerance bands of ±1% to ±2% on quantity with absolute caps in tonnes are standard. Hazmat freight invoices add a separate match dimension.