1. The Invoice Number Discrepancy Dilemma
Under GST rules, an invoice number can be up to 16 characters long and contain alphanumeric characters, hyphens, and slashes. Because humans enter these numbers manually on both ends (supplier's billing clerk and buyer's accountant), variations are inevitable:
- Slash vs Dash: Supplier files
GST/24-25/101• You enteredGST-24-25-101. - Financial Year Prefix Omission: Supplier files
2024-25/892• You entered892. - Leading Zero Stripping: Supplier files
000541• You entered541. - Typos in Suffixes: Supplier writes
INV/B-12• You enteredINV/B12.
2. How GST-Hawk's Multi-Layer Normalization Works
GST-Hawk implements a 3-stage artificial intelligence matching pipeline:
- Stage 1 - Exact Match: Validates identical GSTIN + Invoice Number + Tax Amount.
- Stage 2 - Core Alphanumeric Normalization: Automatically removes special characters (
/,-,_), leading zeros, and standard financial year prefixes (23-24,2023-24,2425). If the alphanumeric core matches with identical tax, it is verified. - Stage 3 - Levenshtein Distance Calculation: Calculates the mathematical edit distance between remaining strings. If the supplier GSTIN and tax values match exactly and string edit distance is within safe tolerance, it is flagged as a "Probable Match with Invoice Typo" for instant approval.
Pro-Tip for CAs: With GST-Hawk's 19-sheet report, you get a dedicated tab titled "Probable Matches (Typo Detected)" where both the Portal invoice number and your Books invoice number are printed side-by-side for instant audit sign-off!
3. Frequently Asked Questions
Does fuzzy matching ever create false positive matches?
No. GST-Hawk strictly requires exact GSTIN equality and tax value equality before applying fuzzy string similarity. Two different suppliers or different tax amounts will never be incorrectly paired.
Can I configure the fuzzy matching tolerance level?
Yes. Under Settings in GST-Hawk, you can adjust tolerance rules between strict CA mode and relaxed matching.