{
  "source": "https://www.terra-insight.com",
  "description": "Machine-readable FAQ corpus for Terra Insight. Covers TransactIG (reconciliation infrastructure — TDS, GST, NACH, bank reconciliation, platform settlements), TransactIQ (bank statement analysis for NBFC credit underwriting — OCR, forensics, risk word signals), and surrounding CA firm, audit/assurance, retail/D2C, and ERP integration practitioner content.",
  "totalFaqs": 1741,
  "clusters": {
    "bsa-risk-signals": {
      "label": "Bank Statement Risk Word Signals",
      "faqs": [
        {
          "q": "Why is adult entertainment a separate risk category in bank statement analysis?",
          "a": "Adult entertainment is a distinct credit risk category for two reasons. First, subscription-based spending in this category creates a recurring outflow that contributes to the total discretionary spend share — relevant to FOIR and affordability calculations. Second, transactions to platforms operating outside Indian regulatory frameworks may indicate financial behaviour inconsistent with declared income or occupation. The category is flagged for human review, not treated as an automatic rejection criterion.",
          "article": "Adult Entertainment Transactions in Bank Statements: A Credit Risk Category Explained",
          "url": "https://www.terra-insight.com/insights/adult-entertainment-detection-bank-statements"
        },
        {
          "q": "How do adult entertainment transactions appear in Indian bank statements?",
          "a": "They appear primarily as international card transactions, UPI payments to payment aggregators, or IMPS/NEFT credits to entities with non-descriptive merchant names. Domestic subscription platforms occasionally appear with the platform name in the narration. International platforms often appear as foreign currency card debits with the platform's legal entity name, which may differ from its consumer-facing brand. Automated detection requires matching against both brand names and associated payment entity names.",
          "article": "Adult Entertainment Transactions in Bank Statements: A Credit Risk Category Explained",
          "url": "https://www.terra-insight.com/insights/adult-entertainment-detection-bank-statements"
        },
        {
          "q": "How should a credit officer interpret adult entertainment spending in a loan application?",
          "a": "The interpretation depends on context: frequency and value relative to income, whether the applicant declared a particular income level or occupation that is inconsistent with the spending pattern, and whether the transactions appear alongside other risk signals (gambling, predatory lending, financial distress). An isolated low-value subscription is materially different from high-frequency high-value transactions. The risk word report surfaces the data; the credit officer applies the judgement.",
          "article": "Adult Entertainment Transactions in Bank Statements: A Credit Risk Category Explained",
          "url": "https://www.terra-insight.com/insights/adult-entertainment-detection-bank-statements"
        },
        {
          "q": "Do Indian regulatory guidelines specifically address this risk category?",
          "a": "RBI's Digital Lending Guidelines and KYC Master Direction require regulated entities to conduct adequate due diligence on borrowers' financial profiles, which includes assessing income allocation and spending patterns. There is no specific RBI circular naming adult entertainment as a prohibited category. The classification exists in bank statement analysis frameworks because it is a standard discretionary spend category used by NBFC credit teams when assessing repayment capacity.",
          "article": "Adult Entertainment Transactions in Bank Statements: A Credit Risk Category Explained",
          "url": "https://www.terra-insight.com/insights/adult-entertainment-detection-bank-statements"
        },
        {
          "q": "Is automated detection of this category reliable given indirect payment methods?",
          "a": "Detection reliability is moderate. Domestic subscription platforms that include their name in narration strings are reliably identified. International platforms that route through payment processors with generic entity names are harder to detect by name alone — these may be captured by pattern analysis (recurring international card debits of similar amounts) rather than keyword matching. For credit underwriting at Indian NBFCs, direct platform-name matches cover the most commonly encountered cases.",
          "article": "Adult Entertainment Transactions in Bank Statements: A Credit Risk Category Explained",
          "url": "https://www.terra-insight.com/insights/adult-entertainment-detection-bank-statements"
        },
        {
          "q": "How does alcohol spending appear in an Indian bank statement?",
          "a": "Alcohol purchases appear through several channels: direct point-of-sale card swipes at liquor stores, beverage corporation outlets, bars, and restaurants; UPI payments to retail outlets with the outlet name in the narration; app-based home delivery platforms (Swiggy Instamart, Zomato, or dedicated alcohol delivery apps like HipBar) where the narration may show the delivery platform name; and online retailers like Wine Shop India or Beverage Delivery. Premium brands and hotel bars appear in narrations when full establishment names are included.",
          "article": "Alcohol Spending in Bank Statements: A Discretionary Expense Signal for Lenders",
          "url": "https://www.terra-insight.com/insights/alcohol-spending-detection-bank-statements"
        },
        {
          "q": "Which state alcohol retail entities are covered in bank statement risk word lists?",
          "a": "State-run alcohol retailers are a significant component: TASMAC (Tamil Nadu), Kerala Beverages Corporation (Bevco), Karnataka State Beverages Corporation (KSBCL), Maharashtra State Beverages Corporation (MSBC), Delhi DSIIDC outlets, AP Beverages Corporation, and Telangana State Beverages Corporation are recognised. These names appear in UPI and card transaction narrations when customers transact at government-operated outlets. Coverage of state names and abbreviations is important for accurate detection in South and West India where government retail is dominant.",
          "article": "Alcohol Spending in Bank Statements: A Discretionary Expense Signal for Lenders",
          "url": "https://www.terra-insight.com/insights/alcohol-spending-detection-bank-statements"
        },
        {
          "q": "What threshold of alcohol spending relative to income is considered a credit risk signal?",
          "a": "There is no universal threshold — lender policy governs the cutoff. A common internal benchmark used by NBFC credit teams is that alcohol-related debits exceeding 3 to 5% of average monthly income consistently over 3 months warrant manual review. The context matters: a one-time high-value transaction at a premium establishment differs from daily small-value entries suggesting habitual high-frequency spending. The credit officer reviews both the share and the pattern.",
          "article": "Alcohol Spending in Bank Statements: A Discretionary Expense Signal for Lenders",
          "url": "https://www.terra-insight.com/insights/alcohol-spending-detection-bank-statements"
        },
        {
          "q": "Does alcohol spending detection rely only on brand names?",
          "a": "No. Detection covers multiple signal types: global brand names (Johnnie Walker, Chivas, Jack Daniel's, Heineken, Kingfisher, Royal Challenge), state corporation outlet names (TASMAC, Bevco, KSBCL), bar and restaurant names where alcohol is the primary category, home delivery platforms with alcohol categories, and generic retail terms associated with liquor stores. Pattern-based detection supplements keyword matching for transactions where specific names are absent but the merchant category code or narration pattern is indicative.",
          "article": "Alcohol Spending in Bank Statements: A Discretionary Expense Signal for Lenders",
          "url": "https://www.terra-insight.com/insights/alcohol-spending-detection-bank-statements"
        },
        {
          "q": "How does the ICAI guidance on financial statement analysis apply to alcohol spending detection in credit underwriting?",
          "a": "ICAI's auditing and review standards require practitioners assessing financial positions to evaluate expense categories against income. When CAs assist NBFCs in credit assessment or when statutory auditors review NBFC portfolios, the principle of expense-income consistency applies to all major discretionary categories including alcohol. For credit underwriting, this means that alcohol spending is assessed in the same framework as any other expense category — as a proportion of income, in the context of total obligations.",
          "article": "Alcohol Spending in Bank Statements: A Discretionary Expense Signal for Lenders",
          "url": "https://www.terra-insight.com/insights/alcohol-spending-detection-bank-statements"
        },
        {
          "q": "What is the current regulatory status of cryptocurrency transactions in India?",
          "a": "As of April 2026, cryptocurrency is a legal asset class in India under the Virtual Digital Asset (VDA) framework introduced in the Finance Act 2022. Transfers of VDAs attract 30% tax on gains with no loss set-off permitted, and a 1% TDS applies under Section 194S on transfers above ₹50,000 per year (₹10,000 for non-specified persons). Exchanges operating in India must register with FIU-IND under PMLA. RBI's banking ban on crypto was lifted by Supreme Court order in March 2020. Lenders must apply standard AML due diligence to customers with crypto activity.",
          "article": "Cryptocurrency Transactions in Bank Statements: What Indian Lenders Flag and Why",
          "url": "https://www.terra-insight.com/insights/crypto-transaction-patterns-bank-statements"
        },
        {
          "q": "Which Indian cryptocurrency exchanges appear most often in bank statement analysis?",
          "a": "CoinDCX, WazirX, CoinSwitch Kuber, Unocoin, and ZebPay are the primary Indian exchanges and appear directly in bank statement narrations. Binance India (now exited the Indian market) and its successor entities appear in older statements. International exchanges accessed via Indian bank accounts appear as foreign currency card debits or IMPS transfers to intermediary payment entities. P2P crypto transactions routed through UPI may appear as transfers to individuals rather than exchange names.",
          "article": "Cryptocurrency Transactions in Bank Statements: What Indian Lenders Flag and Why",
          "url": "https://www.terra-insight.com/insights/crypto-transaction-patterns-bank-statements"
        },
        {
          "q": "How does crypto activity affect FOIR calculations in NBFC underwriting?",
          "a": "Crypto activity complicates FOIR in two ways. On the income side, large crypto sale credits may be treated as one-time non-recurring income rather than stable income, reducing the income base for FOIR. On the obligation side, active crypto investment requiring regular funded top-ups represents a capital allocation that, while not a fixed obligation, reduces discretionary income available for debt servicing. NBFC credit policies vary on how they treat crypto sale proceeds — some exclude them entirely from income calculations.",
          "article": "Cryptocurrency Transactions in Bank Statements: What Indian Lenders Flag and Why",
          "url": "https://www.terra-insight.com/insights/crypto-transaction-patterns-bank-statements"
        },
        {
          "q": "What PMLA obligations apply to NBFCs when a borrower shows crypto exchange transactions?",
          "a": "Under PMLA 2002 and the 2023 notification bringing VDA service providers under PMLA, regulated entities including NBFCs are required to apply enhanced due diligence to customers whose transactions indicate exposure to Virtual Asset Service Providers. If the transaction volumes or patterns are inconsistent with the customer's declared income and risk profile, a Suspicious Transaction Report (STR) obligation may arise under Section 12 of PMLA. FIU-IND is the nodal authority for STR filings.",
          "article": "Cryptocurrency Transactions in Bank Statements: What Indian Lenders Flag and Why",
          "url": "https://www.terra-insight.com/insights/crypto-transaction-patterns-bank-statements"
        },
        {
          "q": "Is crypto investment a disqualifying factor for loan applications at Indian NBFCs?",
          "a": "No universal policy applies across Indian NBFCs. Some lenders treat active crypto investment as a risk factor that increases scrutiny; others treat it as an asset class like equities. The credit risk concern is primarily about income volatility — an applicant who has made large crypto investments from their bank account and then shows significant crypto sale proceeds as income is being assessed on income that may not recur at the same level. The detection layer surfaces the activity; the lender's credit policy governs the treatment.",
          "article": "Cryptocurrency Transactions in Bank Statements: What Indian Lenders Flag and Why",
          "url": "https://www.terra-insight.com/insights/crypto-transaction-patterns-bank-statements"
        },
        {
          "q": "Does gambling activity in a bank statement automatically disqualify a loan applicant in India?",
          "a": "No. Gambling transactions are a risk signal, not an automatic disqualifier. The credit officer reviews the transaction count, total value, and frequency relative to income. A single ₹500 fantasy sports entry on Dream11 carries very different weight than recurring high-value deposits to offshore betting platforms. The decision remains with the lender.",
          "article": "Detecting Gambling Transactions in Bank Statements: A Credit Risk Signal for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/detecting-gambling-transactions-bank-statements"
        },
        {
          "q": "Which gambling platforms appear most often in Indian bank statement analysis?",
          "a": "Fantasy sports platforms dominate Indian bank statements: Dream11, MPL (Mobile Premier League), My11Circle, and Gamezy are the most common. Rummy platforms — Rummy Circle, Classic Rummy, Adda52 — appear frequently in South India in particular. Offshore sports betting apps accessed via UPI aggregators or international card transactions also appear, though narration strings vary by payment method.",
          "article": "Detecting Gambling Transactions in Bank Statements: A Credit Risk Signal for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/detecting-gambling-transactions-bank-statements"
        },
        {
          "q": "How does TransactIQ detect gambling transactions across 130+ platforms?",
          "a": "TransactIQ scans every transaction description against a curated list of 130+ gambling and betting platform names, including name variants, abbreviations, and payment gateway references used by these platforms. For each match, the report records transaction count, total debit, total credit, and the top five matched terms — giving the credit officer a complete picture without manual keyword searching.",
          "article": "Detecting Gambling Transactions in Bank Statements: A Credit Risk Signal for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/detecting-gambling-transactions-bank-statements"
        },
        {
          "q": "What is the RBI's position on gambling apps in the digital lending context?",
          "a": "RBI's digital lending guidelines and its directions to payment aggregators have progressively tightened restrictions on processing payments for offshore gambling. Several payment aggregators were directed to discontinue merchant onboarding for betting apps in 2023. Lenders are expected to account for cash outflows to restricted platforms as part of their due diligence under RBI's KYC Master Direction.",
          "article": "Detecting Gambling Transactions in Bank Statements: A Credit Risk Signal for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/detecting-gambling-transactions-bank-statements"
        },
        {
          "q": "How should a credit officer interpret a high total debit to gambling platforms relative to declared income?",
          "a": "A useful benchmark is the share of total monthly debits attributable to gambling. If gambling-related outflows exceed 5% of average monthly income consistently over 3 or more months, that warrants manual review. The pattern matters as much as the total: escalating frequency, post-salary gambling entries within 48 hours of credit, and a mix of both domestic and offshore platforms together constitute a stronger signal than a single isolated high-value entry.",
          "article": "Detecting Gambling Transactions in Bank Statements: A Credit Risk Signal for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/detecting-gambling-transactions-bank-statements"
        },
        {
          "q": "What narration patterns indicate a NACH bounce charge in an Indian bank statement?",
          "a": "Common NACH bounce charge narrations across Indian banks include: 'NACH RTN CHG', 'ECS RTN CHRG', 'ACH RETURN CHRG', 'NACH BOUNCE FEE', 'AUTOPAY RTN CHG', and similar abbreviated forms. The specific pattern varies by bank — HDFC uses formats like 'NACH RTN CHRG' while SBI uses 'NACH/ENACH BOUNCE'. The charge typically debits within 1 to 3 days of the failed NACH presentation date. Multiple NACH bounce charges in a single month indicate more than one failed mandate — a strong repayment stress signal.",
          "article": "Financial Distress Signals in Bank Statements: Bounce Charges, Penalties, and NPA Indicators",
          "url": "https://www.terra-insight.com/insights/financial-distress-signals-bank-statements"
        },
        {
          "q": "How does a minimum balance penalty signal financial distress?",
          "a": "Minimum balance penalties appear as recurring debits when an account falls below the bank-required balance threshold. Common narration patterns include 'MAB CHRG', 'AVG BAL CHGS', 'MIN BAL PEN', 'NON MAINT CHGS', and similar. The credit relevance is twofold: first, it confirms that the account was regularly insufficient even to meet the bank's base requirement; second, it indicates the account holder was not managing the account proactively. For salary accounts where minimum balance waivers are standard, the presence of these charges may indicate the account type has changed or salary credits have stopped.",
          "article": "Financial Distress Signals in Bank Statements: Bounce Charges, Penalties, and NPA Indicators",
          "url": "https://www.terra-insight.com/insights/financial-distress-signals-bank-statements"
        },
        {
          "q": "What is the difference between a NACH bounce charge and a cheque return charge as a credit signal?",
          "a": "Both indicate payment failure, but with different implications. A NACH bounce reflects an automated debit instruction — typically an EMI, insurance premium, or utility payment — that the account could not honour. It is a direct repayment failure indicator. A cheque return charge (narration: 'CHQ RETURN CHGS', 'CTS RETURN', 'CHQ DISHONOUR') indicates an issued cheque was returned unpaid, which may reflect insufficient funds or a stop-payment instruction. Multiple cheque returns alongside NACH bounces are a compound distress signal — the account is failing across multiple payment instruments.",
          "article": "Financial Distress Signals in Bank Statements: Bounce Charges, Penalties, and NPA Indicators",
          "url": "https://www.terra-insight.com/insights/financial-distress-signals-bank-statements"
        },
        {
          "q": "Do loan restructuring entries appear in bank statements?",
          "a": "Loan restructuring entries may appear as specific narration strings from the lender: 'LOAN RESCHD', 'EMI HOLIDAY', 'MORATORIUM', or through a change in the standard EMI debit pattern (a gap month followed by a different amount). These are less reliably detectable by keyword matching than bounce charges, but the EMI continuity tracking module in bank statement analysis identifies cases where a recurring EMI that was active for 6+ months suddenly disappears or changes amount — which covers the pattern if not always the explicit label.",
          "article": "Financial Distress Signals in Bank Statements: Bounce Charges, Penalties, and NPA Indicators",
          "url": "https://www.terra-insight.com/insights/financial-distress-signals-bank-statements"
        },
        {
          "q": "How many NACH bounce charges in a 12-month statement are a red flag?",
          "a": "One or two NACH bounces in a 12-month period are within the range seen in otherwise creditworthy borrowers — occasional timing mismatches between salary credit and mandate presentation are common. Three or more NACH bounces in a 12-month period, particularly if concentrated in recent months or involving the same obligation, indicate a pattern of payment failure rather than an isolated event. A borrower with 5+ NACH bounces in the most recent 6 months has a repayment track record that warrants specific attention regardless of their current account balance.",
          "article": "Financial Distress Signals in Bank Statements: Bounce Charges, Penalties, and NPA Indicators",
          "url": "https://www.terra-insight.com/insights/financial-distress-signals-bank-statements"
        },
        {
          "q": "What does a lifestyle-income gap mean in the context of bank statement credit analysis?",
          "a": "A lifestyle-income gap is a discrepancy between the income an applicant declares and the spending pattern their bank statement reveals. An applicant declaring a monthly income of ₹60,000 but showing regular transactions at five-star hotels, luxury fashion brands, and premium jewellery stores is presenting an inconsistency. This inconsistency raises two possibilities: the income is understated (informal income not disclosed), or the applicant is living beyond declared means through informal borrowing or savings drawdown. Both scenarios are material to a credit decision.",
          "article": "Luxury Overspending in Bank Statements: 45+ Brand Signals for Credit Teams",
          "url": "https://www.terra-insight.com/insights/luxury-overspending-detection-bank-statements"
        },
        {
          "q": "Which Indian luxury brands and retailers appear in bank statement detection?",
          "a": "India-specific luxury markers include Tanishq, Kalyan Jewellers, Malabar Gold, and Joyalukkas for jewellery; Shoppers Stop, Westside, and lifestyle department stores; five-star hotel chains (Taj, Oberoi, ITC Hotels, Marriott, Hyatt) for hospitality; premium cosmetics and beauty retailers including Nykaa luxury brands and MAC; and electronics premium retail including Apple Store transactions and premium camera brands. International fashion brands (Gucci, Louis Vuitton, Prada, Burberry, Armani) with Indian retail presence are also covered.",
          "article": "Luxury Overspending in Bank Statements: 45+ Brand Signals for Credit Teams",
          "url": "https://www.terra-insight.com/insights/luxury-overspending-detection-bank-statements"
        },
        {
          "q": "How should a credit officer interpret luxury spending from a high-income applicant?",
          "a": "Context governs interpretation. For a borrower with monthly income of ₹5 lakh, a ₹30,000 jewellery purchase is within a normal range and warrants no special attention. The same purchase for a borrower declaring ₹40,000 monthly income — representing 75% of declared monthly income — is a significant flag. The detection threshold is income-relative, not absolute. Credit officers are expected to consider the proportion, the frequency, and whether multiple luxury categories are active simultaneously.",
          "article": "Luxury Overspending in Bank Statements: 45+ Brand Signals for Credit Teams",
          "url": "https://www.terra-insight.com/insights/luxury-overspending-detection-bank-statements"
        },
        {
          "q": "Does business travel and hospitality spending trigger the luxury flag?",
          "a": "Potentially, yes — and this is a context the credit officer must resolve. A salesperson or business owner with frequent five-star hotel stays may be recording legitimate business expenses that route through their personal account. In these cases, the credit officer would typically look for offsetting business income credits from the same period, or request clarification. Automated detection flags the transactions; distinguishing personal luxury from business expense is a human review task.",
          "article": "Luxury Overspending in Bank Statements: 45+ Brand Signals for Credit Teams",
          "url": "https://www.terra-insight.com/insights/luxury-overspending-detection-bank-statements"
        },
        {
          "q": "How is luxury spending detection different from general discretionary expense analysis?",
          "a": "General discretionary expense analysis categorises all non-essential spending. Luxury detection is a targeted sub-set focused on brand-specific spending at the premium end — transactions that are individually significant in value and collectively indicate a lifestyle level that should be consistent with declared income. The specific signal is the brand name match, not just the expense category. A ₹5,000 restaurant bill at an Oberoi property signals differently than a ₹5,000 grocery bill, even though both are food spending.",
          "article": "Luxury Overspending in Bank Statements: 45+ Brand Signals for Credit Teams",
          "url": "https://www.terra-insight.com/insights/luxury-overspending-detection-bank-statements"
        },
        {
          "q": "Why does FOIR from bureau data understate true leverage in Indian borrowers?",
          "a": "FOIR calculated from bureau data captures only obligations reported to credit bureaus — CIBIL, CRIF, Experian, and Equifax. Many Indian borrowers carry obligations that are not bureau-reported: BNPL platforms that do not report to all bureaus, predatory lending apps operating without NBFC registration, family or informal borrowing reflected in the account as IMPS transfers, and employer salary advances. Bank statement analysis surfaces all of these through the actual debit entries, regardless of bureau reporting status. The gap between bureau-derived FOIR and statement-derived FOIR can be 20 to 40 percentage points in high-leverage borrower profiles.",
          "article": "Over-Leverage Detection in Bank Statements: EMI, BNPL, and Debt Consolidation Signals",
          "url": "https://www.terra-insight.com/insights/over-leverage-detection-bank-statements"
        },
        {
          "q": "How do BNPL obligations appear in an Indian bank statement?",
          "a": "BNPL charges appear as recurring NACH or UPI debits from the platform — typically monthly or fortnightly. Common narration patterns: 'LAZYPAY EMI', 'SIMPL REPAYMENT', 'ZESTMONEY EMI', 'SLICE EMI', 'MONEYVIEW BNPL'. For BNPL platforms that process through an NBFC partner, the NBFC name may appear instead of the consumer-facing brand. Unlike a bank EMI, BNPL obligations often have variable amounts as the balance reduces — a pattern that the obligation tracking module recognises by looking for consistent counterparty names with decreasing amounts over 3+ months.",
          "article": "Over-Leverage Detection in Bank Statements: EMI, BNPL, and Debt Consolidation Signals",
          "url": "https://www.terra-insight.com/insights/over-leverage-detection-bank-statements"
        },
        {
          "q": "What is debt consolidation loan detection in bank statement analysis?",
          "a": "A debt consolidation loan appears as a large single inward credit followed — within 1 to 15 days — by multiple outward transfers to other lenders or loan app accounts. The pattern indicates the borrower took a new loan specifically to repay existing obligations. While this may reduce the number of active debits, it does not reduce total indebtedness. Detection cross-references large inward credits with outward transfers in the same period to identify likely consolidation events.",
          "article": "Over-Leverage Detection in Bank Statements: EMI, BNPL, and Debt Consolidation Signals",
          "url": "https://www.terra-insight.com/insights/over-leverage-detection-bank-statements"
        },
        {
          "q": "How are credit card minimum payments detected in bank statements?",
          "a": "Credit card minimum payments appear as outward transfers to card-issuing banks with narration patterns like 'CC MIN PAY', 'CRDT CARD PMT MIN', or simply the card issuer name. A borrower making only minimum payments on one or more credit cards has undisclosed revolving debt that FOIR does not capture — the minimum payment is not the actual obligation. Detection flags minimum payment narrations (as distinct from full payment narrations) and counts them as an indicator of revolving credit stress.",
          "article": "Over-Leverage Detection in Bank Statements: EMI, BNPL, and Debt Consolidation Signals",
          "url": "https://www.terra-insight.com/insights/over-leverage-detection-bank-statements"
        },
        {
          "q": "Which BNPL platforms are covered in Indian bank statement over-leverage detection?",
          "a": "India-specific BNPL coverage includes: LazyPay, Simpl, ZestMoney, Slice, MoneyView, KreditBee, PaySense, StashFin, CASHe, and EarlySalary. BNPL features embedded within larger platforms — Amazon Pay Later, Flipkart Pay Later, Ola Money Postpaid — also appear in statement narrations and are covered. For platforms where the BNPL obligation routes through a partner NBFC, the NBFC name is cross-referenced to the platform.",
          "article": "Over-Leverage Detection in Bank Statements: EMI, BNPL, and Debt Consolidation Signals",
          "url": "https://www.terra-insight.com/insights/over-leverage-detection-bank-statements"
        },
        {
          "q": "How does a predatory lending app appear in an Indian bank statement?",
          "a": "Predatory lending app transactions typically appear as inward IMPS or UPI credits (the loan disbursal) followed by outward UPI or NACH debits (repayments or renewal fees). The platform name appears in the narration alongside a reference ID. For apps that have been banned and re-launched under alternate names, the new entity name appears instead — which is why automated detection requires ongoing list maintenance rather than a fixed keyword set.",
          "article": "Predatory Lending App Detection in Bank Statements: What Indian Lenders Check",
          "url": "https://www.terra-insight.com/insights/predatory-lending-app-detection-india"
        },
        {
          "q": "Do predatory lending app transactions affect a borrower's CIBIL score?",
          "a": "Many predatory and informal lending apps do not report to credit bureaus. This means a borrower could have 5 to 10 active informal loan obligations that are completely invisible to a CIBIL pull. Bank statement analysis surfaces these obligations directly from the transaction history — repayment debits appear regardless of whether the lender is bureau-registered. This is one of the key reasons bank statement analysis is used alongside bureau pulls in NBFC underwriting.",
          "article": "Predatory Lending App Detection in Bank Statements: What Indian Lenders Check",
          "url": "https://www.terra-insight.com/insights/predatory-lending-app-detection-india"
        },
        {
          "q": "What was RBI's 2022–2023 crackdown on digital lending apps?",
          "a": "In August 2022, RBI issued Digital Lending Guidelines that prohibited loan disbursals and repayments from flowing through third-party pass-through accounts. In 2023, RBI and the Ministry of Electronics and IT directed app stores to remove several hundred non-compliant loan apps. The banned apps list included entities offering loans at annualised rates exceeding 100%, apps using coercive recovery tactics, and apps not registered as NBFCs or bank partners. Many of these entities re-launched under different names — which is why the detection list requires active maintenance.",
          "article": "Predatory Lending App Detection in Bank Statements: What Indian Lenders Check",
          "url": "https://www.terra-insight.com/insights/predatory-lending-app-detection-india"
        },
        {
          "q": "What is the credit risk implication of multiple predatory app transactions in a statement?",
          "a": "Multiple predatory app inflows followed by rapid repayments — the classic debt-cycling pattern — indicate a borrower managing a cash shortfall through successive short-tenure high-cost loans. For an NBFC assessing an additional loan application, this pattern suggests the borrower's effective debt burden is materially higher than bureau records show, that discretionary income is already committed to high-cost repayments, and that adding another obligation increases default risk significantly.",
          "article": "Predatory Lending App Detection in Bank Statements: What Indian Lenders Check",
          "url": "https://www.terra-insight.com/insights/predatory-lending-app-detection-india"
        },
        {
          "q": "Are all high-interest digital lending apps predatory by definition?",
          "a": "No. The classification used in bank statement risk analysis is based on regulatory status and known enforcement actions, not interest rate alone. Apps that operated without NBFC registration, apps that were formally banned by RBI or removed under the 2023 directive, and apps associated with coercive recovery practices are flagged. Licensed NBFCs and bank-partner apps operating within regulatory guidelines are not flagged even if their rates are above average.",
          "article": "Predatory Lending App Detection in Bank Statements: What Indian Lenders Check",
          "url": "https://www.terra-insight.com/insights/predatory-lending-app-detection-india"
        },
        {
          "q": "What PMLA obligations do Indian NBFCs have when suspicious counterparty patterns appear in a loan applicant's bank statement?",
          "a": "Under PMLA 2002 and the Prevention of Money Laundering (Maintenance of Records) Rules 2005, all NBFCs registered with RBI are reporting entities. When a loan officer encounters bank statement transactions that indicate potential money laundering — including hawala-associated patterns, structured transactions, or unusual round-trip activity — the entity must file a Suspicious Transaction Report (STR) with FIU-IND within 7 days of forming suspicion. The obligation to file exists regardless of whether the loan is ultimately approved or declined.",
          "article": "Suspicious Counterparty Patterns in Bank Statements: AML Signals for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/suspicious-counterparty-patterns-bank-statements"
        },
        {
          "q": "What is structuring in the context of Indian bank statement analysis?",
          "a": "Structuring is the practice of conducting multiple transactions just below a reporting or monitoring threshold to avoid triggering oversight. In India, RBI and FIU-IND have identified thresholds at ₹50,000 for cash transactions and ₹10 lakh for aggregate monthly cash movements as points of heightened scrutiny. A bank statement showing multiple cash withdrawals of ₹49,000 to ₹49,500 over a short period, or multiple IMPS transfers of similar amounts fractionally below a round threshold, may indicate deliberate structuring. Detection counts sub-threshold clusters and flags their frequency.",
          "article": "Suspicious Counterparty Patterns in Bank Statements: AML Signals for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/suspicious-counterparty-patterns-bank-statements"
        },
        {
          "q": "How are hawala-associated transactions identifiable in a bank statement?",
          "a": "Hawala transactions are informal cross-border or domestic remittances that bypass the formal banking system, but they often use the banking system as a component. Indicators in bank statements include: beneficiary names or narrations associated with known informal remittance operators, repeated transfers to a single counterparty with no apparent commercial relationship, large cash withdrawals followed by foreign currency inflows of similar amounts through informal channels, and transfers described with vague narrations like 'settlement' or 'payment against agreement' to unrecognised counterparties. These are indicators, not proof — STR obligations require reasonable suspicion, not certainty.",
          "article": "Suspicious Counterparty Patterns in Bank Statements: AML Signals for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/suspicious-counterparty-patterns-bank-statements"
        },
        {
          "q": "What does round-trip transaction detection look at in a bank statement?",
          "a": "Round-trip detection identifies credit-debit pairs involving the same or related counterparty at similar amounts within a short time window — typically 3 to 30 days. A genuine business relationship would not normally show money leaving and returning through the same counterparty at the same amount repeatedly. Round-trip patterns can indicate circular fund movement designed to inflate apparent turnover, simulate business activity, or route funds between related parties. The report lists matched pairs with counterparty name, credit amount, debit amount, and days between the transactions.",
          "article": "Suspicious Counterparty Patterns in Bank Statements: AML Signals for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/suspicious-counterparty-patterns-bank-statements"
        },
        {
          "q": "Can legitimate businesses show patterns that resemble suspicious counterparty activity?",
          "a": "Yes. A trading company with regular buy-sell cycles with the same counterparty can show credit-debit pairs at similar amounts. An MSME that both borrows from and supplies to a related entity may show circular movements that are commercially justified. These false-positive scenarios are why suspicious pattern detection produces a flag for human review rather than an automated decision. The credit officer or compliance team reviews the flagged transactions against the customer's declared business activity and requests clarification where the pattern cannot be explained by the business model.",
          "article": "Suspicious Counterparty Patterns in Bank Statements: AML Signals for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/suspicious-counterparty-patterns-bank-statements"
        },
        {
          "q": "How does tobacco spending appear as a credit risk category in NBFC underwriting?",
          "a": "Tobacco spending is a credit risk category for two reasons. First, it is a discretionary expense that competes with debt servicing. For borrowers with limited disposable income, regular tobacco spending — whether on cigarettes, beedi, chewing tobacco, or similar products — reduces the effective income available for EMI payments. Second, health risk proxies are an input in some lender actuarial models for product pricing, though credit decisions based solely on tobacco use may face regulatory scrutiny. The primary use is income allocation assessment, not health scoring.",
          "article": "Tobacco and Controlled Substance Transactions in Bank Statements: How Lenders Categorise Them",
          "url": "https://www.terra-insight.com/insights/tobacco-controlled-substances-bank-statements"
        },
        {
          "q": "What specific tobacco products and brands appear in Indian bank statement detection?",
          "a": "Detection covers cigarette brands (Gold Flake, Classic, Navy Cut, Wills, Marlboro, Four Square, Bristol), beedi brands and regional tobacco suppliers, pan masala and chewing tobacco brands, hookah lounge transactions (which appear as restaurant or entertainment point-of-sale entries), and tobacco retail outlets with recognisable naming patterns. Premium cigar retailers and duty-free tobacco transactions also appear in statements for higher-income profiles. State-operated tobacco retail entities (in states that maintain them) are included.",
          "article": "Tobacco and Controlled Substance Transactions in Bank Statements: How Lenders Categorise Them",
          "url": "https://www.terra-insight.com/insights/tobacco-controlled-substances-bank-statements"
        },
        {
          "q": "How is a prescription medicine distinguished from a controlled substance in bank statement analysis?",
          "a": "Prescription medicines — even those classified as controlled substances in other contexts — purchased from licensed Indian pharmacies (Apollo Pharmacy, MedPlus, 1mg, Netmeds, PharmEasy) are treated as healthcare spending, not as controlled substance risk flags. Detection in this category focuses on transactions to entities associated with unlicensed or non-pharmaceutical supply of controlled substances. The practical implementation is that pharmacy names are whitelisted from the controlled substance detection module, so legitimate healthcare spending does not trigger risk flags.",
          "article": "Tobacco and Controlled Substance Transactions in Bank Statements: How Lenders Categorise Them",
          "url": "https://www.terra-insight.com/insights/tobacco-controlled-substances-bank-statements"
        },
        {
          "q": "What is the income allocation threshold at which tobacco spending becomes a credit signal?",
          "a": "No universal threshold applies across lenders — credit policy governs the treatment. A common internal benchmark is that tobacco-related debits exceeding 2 to 3% of average monthly income consistently over 3 or more months warrant inclusion in the discretionary spend review. The aggregate picture matters more than a single category: tobacco at 2%, alcohol at 4%, and gambling at 5% combined represent a meaningful share of income that the FOIR calculation does not capture.",
          "article": "Tobacco and Controlled Substance Transactions in Bank Statements: How Lenders Categorise Them",
          "url": "https://www.terra-insight.com/insights/tobacco-controlled-substances-bank-statements"
        },
        {
          "q": "Does the controlled substance detection category flag prescription drug purchases at pharmacies?",
          "a": "No. Licensed pharmacy transactions are explicitly excluded from the controlled substance risk category and classified under healthcare spending. The controlled substance detection module focuses on transactions that indicate procurement through non-pharmaceutical channels — transactions to entities that are not licensed pharmacies and whose narration patterns are associated with controlled substance supply. This distinction is important for credit officers to understand: a borrower with high healthcare spending at pharmacy chains is showing a different signal than one showing transactions to unlicensed channels.",
          "article": "Tobacco and Controlled Substance Transactions in Bank Statements: How Lenders Categorise Them",
          "url": "https://www.terra-insight.com/insights/tobacco-controlled-substances-bank-statements"
        }
      ]
    },
    "tds-sections": {
      "label": "TDS Reconciliation",
      "faqs": [
        {
          "q": "Should TDS on advertising agency invoices be 194J or 194H?",
          "a": "Advertising services attract 10% TDS under Section 194J when the invoice includes creative work, content production, campaign strategy, or branded content. Section 194H at 2% applies only to pure commission on media buying — for example, a 15% agency commission retained from a media vendor payout. The Income Tax Act 2025 classifies advertising as a professional service under Section 402(28), confirming the 194J treatment for the full creative invoice.",
          "article": "Advertising TDS: Why Creative Services Fall Under 194J, Not 194H",
          "url": "https://www.terra-insight.com/insights/advertising-tds-194j-vs-194h-india"
        },
        {
          "q": "What is the difference between media buying commission and creative advertising services?",
          "a": "Pure media buying commission arises when an agency earns a percentage from a media owner for placing ads — typically 2% to 15% of the media spend. This is 194H at 2%. Creative advertising services cover strategy, copy, artwork, film production, digital campaign build, and branded content. These are 194J at 10%. A single agency invoice often bundles both, which is the root cause of misclassification.",
          "article": "Advertising TDS: Why Creative Services Fall Under 194J, Not 194H",
          "url": "https://www.terra-insight.com/insights/advertising-tds-194j-vs-194h-india"
        },
        {
          "q": "If an invoice bundles creative and media placement, what TDS rate applies?",
          "a": "The conservative practice is to deduct 10% under 194J on the full creative and production component and 2% under 194H on the separately identified commission line. If the invoice does not split the lines, most Indian deductors apply 194J at 10% on the full amount, because under-deduction risk is higher than over-deduction risk. Agencies benefit from invoicing creative and commission as separate line items with distinct SAC codes.",
          "article": "Advertising TDS: Why Creative Services Fall Under 194J, Not 194H",
          "url": "https://www.terra-insight.com/insights/advertising-tds-194j-vs-194h-india"
        },
        {
          "q": "Does 194J apply to digital marketing and performance agencies?",
          "a": "Yes. Digital marketing agencies — running Google Ads, Meta Ads, SEO, content marketing, or performance campaigns — typically fall under 194J at 10% because the service involves strategy, creative, and analytics work, not pure commission. Pure ad-spend passthrough with a separate management fee is the only portion that may arguably be technical services under 194J at 2% or commission at 194H; the agency's own fee is 10% professional services in almost all engagement structures.",
          "article": "Advertising TDS: Why Creative Services Fall Under 194J, Not 194H",
          "url": "https://www.terra-insight.com/insights/advertising-tds-194j-vs-194h-india"
        },
        {
          "q": "How do advertising vendors reconcile 194J over-deductions against 194H expectations?",
          "a": "Media agencies that historically billed under 194H often continue to post TDS receivable at 2% in their ledger. When clients correctly deduct at 10% under 194J, Form 26AS shows excess credit against the ledger. Reconciliation requires reclassifying the expected rate in the ledger to 10%, matching against Form 26AS entries under section 194J, and clearing the 8% ledger gap. For an agency with ₹8 crore annual billing, this gap is ₹64 lakh in TDS receivable timing that shifts between quarters.",
          "article": "Advertising TDS: Why Creative Services Fall Under 194J, Not 194H",
          "url": "https://www.terra-insight.com/insights/advertising-tds-194j-vs-194h-india"
        },
        {
          "q": "Do I need to reconcile both AIS and Form 26AS before filing ITR?",
          "a": "Yes, but with different priorities. AIS is now the primary statement and drives Section 143(1) intimation processing. Form 26AS is now supplementary but still contains TDS entries that feed into AIS Part B. The reconciliation sequence should be: first reconcile AIS against your books, then cross-check any TDS entries in 26AS against the corresponding AIS Part B entries. If the same TDS entry appears in both but with a discrepancy, the AIS figure is what the tax department will use in automated processing.",
          "article": "AIS and TIS Reconciliation: How to Reconcile Annual Information Statement Before Filing ITR",
          "url": "https://www.terra-insight.com/insights/ais-tis-reconciliation-india"
        },
        {
          "q": "What if AIS shows income I did not earn?",
          "a": "Use the Feedback mechanism in the AIS portal on the income tax e-filing portal (www.incometax.gov.in). Against the specific AIS entry, select the feedback type — options include 'Income is not mine', 'Income is already included in ITR', 'Income is partially correct', or 'Duplicate entry'. After submitting feedback, the information source (bank, deductor, or reporting entity) has 15 days to confirm or deny the correction. The TIS processed value updates once feedback is accepted, which changes the ITR prefill values.",
          "article": "AIS and TIS Reconciliation: How to Reconcile Annual Information Statement Before Filing ITR",
          "url": "https://www.terra-insight.com/insights/ais-tis-reconciliation-india"
        },
        {
          "q": "How long does AIS feedback take to process?",
          "a": "After a taxpayer submits feedback on an AIS entry, the information source is notified and has 15 days to respond. If the source confirms the correction, the AIS entry is updated and the TIS processed value changes within a few days. If the source does not respond within 15 days, the feedback is deemed accepted by default. In practice, banks and large financial institutions tend to respond faster; individual deductors may take the full 15 days. File the ITR with TIS processed values after feedback is submitted — do not wait for the source response if the ITR deadline is approaching.",
          "article": "AIS and TIS Reconciliation: How to Reconcile Annual Information Statement Before Filing ITR",
          "url": "https://www.terra-insight.com/insights/ais-tis-reconciliation-india"
        },
        {
          "q": "Can AIS mismatches result in a notice even after filing a correct ITR?",
          "a": "Yes. If your ITR reports income lower than the AIS reported figure for any category, the centralised processing system at CPC Bengaluru will issue a Section 143(1)(a) intimation flagging the discrepancy. Even if your ITR is factually correct and the AIS entry is wrong, the notice still issues. The resolution process requires submitting a response to the 143(1) notice with supporting documentation — such as the AIS feedback trail, books of account, or bank statements — explaining the variance. Early AIS reconciliation and feedback submission before filing reduces this risk significantly.",
          "article": "AIS and TIS Reconciliation: How to Reconcile Annual Information Statement Before Filing ITR",
          "url": "https://www.terra-insight.com/insights/ais-tis-reconciliation-india"
        },
        {
          "q": "Is AIS data final for tax purposes?",
          "a": "AIS data is not automatically final — it is the tax department's consolidated view based on information reported by third parties (banks, deductors, exchanges, registrars). A taxpayer can dispute AIS entries through the Feedback mechanism, and after the resolution cycle, the TIS processed value is used for ITR prefill. However, if a taxpayer files an ITR that conflicts with AIS without submitting feedback, the CPC uses the AIS figure in the 143(1) comparison. The practical implication: always reconcile AIS against your books before filing, and submit feedback on any inaccurate entries.",
          "article": "AIS and TIS Reconciliation: How to Reconcile Annual Information Statement Before Filing ITR",
          "url": "https://www.terra-insight.com/insights/ais-tis-reconciliation-india"
        },
        {
          "q": "What is the TDS reconciliation process step by step in India?",
          "a": "The process has five steps: (1) Download Form 26AS from TRACES for each PAN — or obtain the consolidated 26AS data via the TRACES API. (2) Export the TDS receivable ledger from the ERP (Tally, SAP, Oracle) showing TDS amounts by deductor TAN, section, and quarter. (3) Match each Form 26AS entry to the corresponding ledger entry on three dimensions: TAN, TDS section, and quarter. (4) Classify mismatches by type — short deduction, wrong section, wrong quarter, PAN error, or challan delay. (5) Raise deduction correction requests with clients for short-deduction or wrong-section mismatches, and track pending entries for the next quarter's Form 26AS update.",
          "article": "Automating TDS Reconciliation: What the Process Looks Like End-to-End",
          "url": "https://www.terra-insight.com/insights/automating-tds-reconciliation-india"
        },
        {
          "q": "What causes TDS mismatches in Form 26AS for Indian companies?",
          "a": "The five most common mismatch causes are: (1) Short deduction — the deductor applied a lower rate than required, often because the vendor has a lower-deduction certificate under Section 197 that the accounts team did not receive. (2) Wrong section — the deductor filed TDS under 194C instead of 194J or vice versa. (3) Cross-quarter credit — TDS deducted in Q3 but deposited after the Q3 cutoff date, appearing in Q4 in Form 26AS. (4) PAN error — deductor filed against an incorrect PAN, so the credit does not appear in the correct vendor's Form 26AS. (5) Challan delay — the deductor deposited TDS but TRACES has not yet reflected it due to bank processing lag.",
          "article": "Automating TDS Reconciliation: What the Process Looks Like End-to-End",
          "url": "https://www.terra-insight.com/insights/automating-tds-reconciliation-india"
        },
        {
          "q": "How do you reconcile TDS when a single client deducts from multiple TANs?",
          "a": "This is common for large clients with multiple GST registrations or state-level operations. Each TAN appears as a separate entry in Form 26AS. The reconciliation must map each TAN to the specific invoices it relates to — typically by matching the TDS amount and section to invoice records by state or business unit. Automation handles this by maintaining a TAN-to-client master table that maps multiple TANs to a single client entity, aggregating TDS credits at the client level while preserving TAN-level audit detail.",
          "article": "Automating TDS Reconciliation: What the Process Looks Like End-to-End",
          "url": "https://www.terra-insight.com/insights/automating-tds-reconciliation-india"
        },
        {
          "q": "What TDS reconciliation software integrates with TRACES for automated matching in India?",
          "a": "TRACES does not provide a real-time API for third-party tools. The integration is typically through structured file uploads: the finance team downloads the 26AS XML or the TDS certificate file from TRACES and uploads it to the reconciliation platform. The platform then maps deductor TANs, matches at section and quarter level, and produces an exception report. TransactIG's TDS reconciliation module handles net-of-TDS receipt matching natively — linking the bank receipt (net of TDS) with the Form 26AS entry and the original invoice in a single match.",
          "article": "Automating TDS Reconciliation: What the Process Looks Like End-to-End",
          "url": "https://www.terra-insight.com/insights/automating-tds-reconciliation-india"
        },
        {
          "q": "How long does TDS reconciliation take with automation versus manual in India?",
          "a": "Manual TDS reconciliation for an organisation with 60 to 80 active deductors across multiple sections typically takes 3 to 5 staff days per quarter, and 2 to 3 weeks for year-end March closing. The time is spent downloading data, cleaning format mismatches, and resolving ambiguous entries. With automated matching, the structured ingestion and match run complete in hours. Finance teams shift from row-by-row matching to reviewing a pre-classified exception list — typically reducing active reconciliation time to 2 to 4 hours for the same deductor volume.",
          "article": "Automating TDS Reconciliation: What the Process Looks Like End-to-End",
          "url": "https://www.terra-insight.com/insights/automating-tds-reconciliation-india"
        },
        {
          "q": "Can I claim TDS credit in my ITR based on Form 16 if Form 26AS shows a lower amount?",
          "a": "No. The Income Tax Department's return processing system validates TDS credit claims against Form 26AS, not against Form 16. If Form 16 shows ₹80,000 TDS but Form 26AS shows ₹60,000, and you claim ₹80,000 in your ITR, the system will generate a demand notice under Section 143(1) for the ₹20,000 difference. Claim only what appears in Form 26AS. If the employer's figure is correct, the resolution path is to ask the employer to file a correction return so Form 26AS updates before you file the ITR.",
          "article": "Form 16 vs Form 26AS: What to Do When They Don't Match",
          "url": "https://www.terra-insight.com/insights/form-16-vs-form-26as-reconciliation"
        },
        {
          "q": "What should I do if my employer's Form 16 shows TDS that isn't in Form 26AS?",
          "a": "Contact the HR or payroll department and ask them to verify: (1) that the quarterly TDS return was filed on time for the relevant quarter; (2) that the challan BSR code and serial number in the return match the actual bank challan; and (3) that the PAN entered for you in the TDS return is correct. If any of these is wrong, the employer must file a correction return on TRACES. Provide them with the specific quarter and amount in question, and track the correction return status through TRACES.",
          "article": "Form 16 vs Form 26AS: What to Do When They Don't Match",
          "url": "https://www.terra-insight.com/insights/form-16-vs-form-26as-reconciliation"
        },
        {
          "q": "How long after an employer files a TDS correction does Form 26AS update?",
          "a": "Form 26AS typically updates within 3–7 business days after the correction return is processed by the TDS CPC. Check Form 26AS after 7 business days. If unchanged, ask the employer to confirm the correction return status on TRACES. You should verify Form 26AS is fully updated before filing your ITR — do not rely on the employer's timeline estimate alone.",
          "article": "Form 16 vs Form 26AS: What to Do When They Don't Match",
          "url": "https://www.terra-insight.com/insights/form-16-vs-form-26as-reconciliation"
        },
        {
          "q": "Is Form 26AS or Form 16 more authoritative for income tax purposes?",
          "a": "Form 26AS is the government's authoritative record of TDS credits linked to a PAN. Form 16 is the employer's certificate of TDS deducted and deposited — a useful document, but secondary to Form 26AS for ITR purposes. When the two conflict, the Income Tax Department treats Form 26AS as the primary source. If Form 16 shows higher TDS than Form 26AS, the resolution must come from the employer correcting the underlying TDS return and challan data, not from accepting Form 16 at face value.",
          "article": "Form 16 vs Form 26AS: What to Do When They Don't Match",
          "url": "https://www.terra-insight.com/insights/form-16-vs-form-26as-reconciliation"
        },
        {
          "q": "What is AIS and how does it differ from Form 26AS?",
          "a": "AIS (Annual Information Statement), accessible from the Income Tax e-filing portal at incometax.gov.in, provides transaction-level data reported by financial institutions: interest income from banks, dividend receipts, securities transactions, mutual fund activity, and foreign remittances. Form 26AS aggregates TDS by deductor TAN at quarterly level. For TDS reconciliation — specifically verifying whether employer TDS is credited — Form 26AS remains the relevant document. AIS is more useful for verifying completeness of income disclosure across all sources.",
          "article": "Form 16 vs Form 26AS: What to Do When They Don't Match",
          "url": "https://www.terra-insight.com/insights/form-16-vs-form-26as-reconciliation"
        },
        {
          "q": "What is Form 16A and who issues it?",
          "a": "Form 16A is a TDS certificate issued by the deductor—the party that deducted tax at source—to the deductee for non-salary payments. It is generated from the TRACES portal and covers deductions under sections such as 194J (professional fees at 10%), 194I (rent at 10% or 2%), 194C (contractor payments at 1% or 2%), 194A (interest at 10%), and 194H (commission at 5%). A manually prepared Form 16A is not valid for ITR purposes.",
          "article": "Form 16A TDS Certificate: Reconciling Non-Salary TDS Deductions with Your Books",
          "url": "https://www.terra-insight.com/insights/form-16a-tds-certificate-reconciliation"
        },
        {
          "q": "When must deductors issue Form 16A to the deductee?",
          "a": "Form 16A must be issued within 15 days from the due date of filing the quarterly TDS return. For Q1 (April–June), the return is due 31 July and Form 16A is due by 15 August. For Q4 (January–March), the return is due 31 May and Form 16A is due by 15 June. Failure to issue Form 16A within the due date can attract a penalty of ₹100 per day under Section 272A.",
          "article": "Form 16A TDS Certificate: Reconciling Non-Salary TDS Deductions with Your Books",
          "url": "https://www.terra-insight.com/insights/form-16a-tds-certificate-reconciliation"
        },
        {
          "q": "Why might a Form 16A amount differ from the Form 26AS entry for the same quarter?",
          "a": "Differences arise from three causes: (1) the deductor filed the TDS return under the wrong section code—for example, 194C instead of 194J—causing 26AS to show a different section than Form 16A; (2) the deductor's challan was not mapped correctly to the deductee's PAN in the TDS return; or (3) the deductor filed a partial return and the balance deduction is shown in a subsequent quarter's return. Each case requires a different remediation path.",
          "article": "Form 16A TDS Certificate: Reconciling Non-Salary TDS Deductions with Your Books",
          "url": "https://www.terra-insight.com/insights/form-16a-tds-certificate-reconciliation"
        },
        {
          "q": "What should a service provider do if a deductor has not issued Form 16A despite deducting TDS?",
          "a": "The deductee should first check Form 26AS to confirm whether the deductor has deposited and filed the challan. If the TDS appears in 26AS but Form 16A has not been issued, the deductee can request the certificate directly from the deductor—referencing the TRACES-generated unique certificate number. If the TDS does not appear in 26AS, the deductor has likely not filed the quarterly return, in which case the deductee can only claim the credit by establishing the deduction through other documentation.",
          "article": "Form 16A TDS Certificate: Reconciling Non-Salary TDS Deductions with Your Books",
          "url": "https://www.terra-insight.com/insights/form-16a-tds-certificate-reconciliation"
        },
        {
          "q": "Can a deductee claim TDS credit in the ITR if the Form 16A has a wrong PAN?",
          "a": "If the PAN on Form 16A does not match the deductee's actual PAN, the corresponding entry will not appear in the deductee's Form 26AS—making the credit unclaimed without correction. The deductee must request the deductor to file a TDS correction return via TRACES to correct the PAN. This must be done before the ITR is filed; credit cannot be claimed on the basis of a physical Form 16A with an incorrect PAN.",
          "article": "Form 16A TDS Certificate: Reconciling Non-Salary TDS Deductions with Your Books",
          "url": "https://www.terra-insight.com/insights/form-16a-tds-certificate-reconciliation"
        },
        {
          "q": "Is manpower supply TDS deducted under 194C or 194J?",
          "a": "Manpower supply and staffing services fall under Section 194C, not 194J. CBDT's long-standing position treats the supply of warm bodies to work under the client's supervision as a work contract. The rate is 1% for individual or HUF vendors and 2% for companies, firms, and LLPs. The Income Tax Act 2025, effective 1 April 2026, codifies this by explicitly including manpower supply in the definition of work under Section 402(47).",
          "article": "Manpower Supply TDS: Why It Falls Under 194C, Not 194J",
          "url": "https://www.terra-insight.com/insights/manpower-supply-tds-194c-vs-194j-india"
        },
        {
          "q": "Why do so many clients deduct 10% under 194J for staffing invoices?",
          "a": "The common misapplication traces to ERP vendor masters that tag any service invoice as professional fees. A ₹10,00,000 staffing invoice deducted at 10% instead of 2% creates an ₹80,000 over-deduction. The vendor must then either recover via a correction return on TRACES or claim the excess through the ITR refund cycle, which takes 6 to 14 months after financial year close.",
          "article": "Manpower Supply TDS: Why It Falls Under 194C, Not 194J",
          "url": "https://www.terra-insight.com/insights/manpower-supply-tds-194c-vs-194j-india"
        },
        {
          "q": "What test distinguishes 194C manpower supply from 194J technical services?",
          "a": "The practical test is three-part: does the vendor supply named individuals under a Statement of Work with hourly or monthly bill rates, does the client direct and supervise the work, and does the vendor charge a markup over salary cost rather than a fixed project deliverable fee. If all three are yes, the contract is 194C manpower supply. If the vendor owns the outcome, carries delivery risk, and bills milestones, 194J may apply.",
          "article": "Manpower Supply TDS: Why It Falls Under 194C, Not 194J",
          "url": "https://www.terra-insight.com/insights/manpower-supply-tds-194c-vs-194j-india"
        },
        {
          "q": "How do I recover over-deducted TDS when a client applied 10% instead of 2%?",
          "a": "First, request the client to file a correction statement on TRACES changing the section from 194J to 194C and refiling with the correct rate. Processing takes 7 to 15 working days. If the correction is refused, the vendor can claim the full deducted amount in the ITR — the higher credit will match Form 26AS, and any refund is released once the return is processed, typically within 30 to 90 days of filing.",
          "article": "Manpower Supply TDS: Why It Falls Under 194C, Not 194J",
          "url": "https://www.terra-insight.com/insights/manpower-supply-tds-194c-vs-194j-india"
        },
        {
          "q": "Does GST apply differently when the same invoice is classified as 194C versus 194J?",
          "a": "GST classification is independent of TDS section. Manpower supply attracts GST at 18% under SAC code 998513 regardless of whether the client deducts TDS under 194C or 194J. However, a 194J misclassification often signals that the client has recorded the expense under professional fees in the ledger, which can affect ITC eligibility checks and internal expense approval limits.",
          "article": "Manpower Supply TDS: Why It Falls Under 194C, Not 194J",
          "url": "https://www.terra-insight.com/insights/manpower-supply-tds-194c-vs-194j-india"
        },
        {
          "q": "Do old TDS section codes still work on TRACES after April 1, 2026?",
          "a": "TRACES will maintain backward compatibility for historical returns (FY 2025-26 and earlier), which will retain old section codes. New transactions filed from April 1, 2026 onwards must use the new section codes under the Income Tax Act 2025. Attempting to file a Q1 FY 2026-27 return with old section codes (194C, 194J, etc.) is expected to generate validation errors on the updated TRACES portal.",
          "article": "New Income Tax Act 2025: Complete TDS Section Mapping for Finance Teams",
          "url": "https://www.terra-insight.com/insights/new-income-tax-act-2025-tds-section-mapping"
        },
        {
          "q": "When does the new Income Tax Act 2025 take effect?",
          "a": "The Income Tax Bill 2025 (Bill No. 11 of 2025), introduced in Lok Sabha on February 13, 2025, is scheduled to take effect from April 1, 2026, applying to FY 2026-27 and onwards. The Finance Act 2025 confirmed this implementation date. All TDS deductions, challan deposits, TDS certificates, and quarterly returns for transactions from April 1, 2026 must reference the new section numbering.",
          "article": "New Income Tax Act 2025: Complete TDS Section Mapping for Finance Teams",
          "url": "https://www.terra-insight.com/insights/new-income-tax-act-2025-tds-section-mapping"
        },
        {
          "q": "Will Form 26AS show new or old section codes after April 1, 2026?",
          "a": "Form 26AS and the Annual Information Statement (AIS) will show the new section codes for transactions deducted on or after April 1, 2026. Historical entries (deductions up to March 31, 2026) will retain the old section codes. This means any cross-year reconciliation between FY 2025-26 receivables and FY 2026-27 Form 26AS entries will involve both code sets simultaneously.",
          "article": "New Income Tax Act 2025: Complete TDS Section Mapping for Finance Teams",
          "url": "https://www.terra-insight.com/insights/new-income-tax-act-2025-tds-section-mapping"
        },
        {
          "q": "Do we need to refile old TDS returns under the new section numbers?",
          "a": "No. TDS returns for FY 2025-26 and earlier remain valid under the old section numbers. There is no requirement to refile historical returns using new section codes. The new numbering applies only to transactions deducted on or after April 1, 2026. However, correction statements for FY 2018-19 through FY 2022-23 must be filed before March 31, 2026, as those years become time-barred after that date.",
          "article": "New Income Tax Act 2025: Complete TDS Section Mapping for Finance Teams",
          "url": "https://www.terra-insight.com/insights/new-income-tax-act-2025-tds-section-mapping"
        },
        {
          "q": "Does the Income Tax Act 2025 change TDS rates or thresholds?",
          "a": "The Income Tax Bill 2025 is primarily a restructuring and consolidation exercise. TDS rates and thresholds are expected to carry over from the 1961 Act. For example, Section 393(1)(a) (replacing 194C) is expected to retain the 1%/2% rate and the ₹30,000 per-transaction and ₹1,00,000 aggregate thresholds. Confirm final rates at the Income Tax India e-filing portal once the Act is formally notified.",
          "article": "New Income Tax Act 2025: Complete TDS Section Mapping for Finance Teams",
          "url": "https://www.terra-insight.com/insights/new-income-tax-act-2025-tds-section-mapping"
        },
        {
          "q": "What is the TDS rate under Section 194T?",
          "a": "Section 194T mandates TDS at 10% on salary, remuneration, commission, bonus, and interest paid by a firm to its partners. The threshold is ₹20,000 in aggregate during a financial year. If the partner does not furnish a PAN, the rate escalates to 20% under Section 206AA.",
          "article": "Section 194T: The New TDS Obligation on Partner Remuneration, Interest, and Bonus",
          "url": "https://www.terra-insight.com/insights/section-194t-partner-firm-tds"
        },
        {
          "q": "When does Section 194T come into effect?",
          "a": "Section 194T is effective from April 1, 2026, applying to all payments made to partners from Tax Year 2026-27 onwards. Under the Income Tax Act 2025, it maps to Section 393(3), Table Serial No. 7, with Payment Code 1067. Firms must begin deducting from the first payment that causes the aggregate to cross ₹20,000.",
          "article": "Section 194T: The New TDS Obligation on Partner Remuneration, Interest, and Bonus",
          "url": "https://www.terra-insight.com/insights/section-194t-partner-firm-tds"
        },
        {
          "q": "Does Section 194T apply to LLPs?",
          "a": "Yes. Section 194T applies to every firm as defined under the Indian Partnership Act, 1932, and to every Limited Liability Partnership under the LLP Act, 2008. Both traditional partnership firms and LLPs must deduct TDS on partner salary, remuneration, interest, commission, and bonus exceeding the ₹20,000 annual threshold.",
          "article": "Section 194T: The New TDS Obligation on Partner Remuneration, Interest, and Bonus",
          "url": "https://www.terra-insight.com/insights/section-194t-partner-firm-tds"
        },
        {
          "q": "What happens if a firm does not deduct TDS under Section 194T?",
          "a": "The firm becomes an assessee-in-default under Section 201(1), liable to pay the TDS amount from its own funds plus 1% interest per month from the date the TDS was deductible. Additionally, the entire partner remuneration or interest expense is disallowed under Section 40(a)(ia) at 30% of the payment amount, increasing the firm's taxable income.",
          "article": "Section 194T: The New TDS Obligation on Partner Remuneration, Interest, and Bonus",
          "url": "https://www.terra-insight.com/insights/section-194t-partner-firm-tds"
        },
        {
          "q": "Which TDS return form covers Section 194T deductions?",
          "a": "Under the Income Tax Act 2025, Section 194T deductions are reported in Form 140, which replaces the earlier Form 26Q. The TDS certificate issued to partners shifts from Form 16A to Form 131. Quarterly filing deadlines remain unchanged: 31 July, 31 October, 31 January, and 31 May for the respective quarters.",
          "article": "Section 194T: The New TDS Obligation on Partner Remuneration, Interest, and Bonus",
          "url": "https://www.terra-insight.com/insights/section-194t-partner-firm-tds"
        },
        {
          "q": "Is Section 194C replaced by Section 393 of the new Income Tax Act?",
          "a": "Yes. Section 194C of the Income Tax Act 1961 — which governs TDS on contractor and sub-contractor payments — is replaced by Section 393(1)(a) of the Income Tax Act 2025, effective April 1, 2026. The rates (1% for individuals/HUF, 2% for companies/firms) and thresholds (₹30,000 per transaction or ₹1,00,000 aggregate per year) are expected to remain the same. However, all challans, Form 16A certificates, and quarterly returns (26Q) for deductions made from April 1, 2026 must reference Section 393(1)(a), not Section 194C.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "Do I need two separate mapping tables for reconciliation after April 1, 2026?",
          "a": "Effectively yes. From April 1, 2026, your reconciliation system must maintain a dual-code reference: old section codes for any transaction deducted up to March 31, 2026 (which will continue to appear in Form 26AS and TDS certificates for those periods), and new Section 393 sub-clause codes for all transactions from April 1, 2026 onwards. For any cross-year reconciliation — comparing FY 2025-26 receivables against FY 2026-27 credits — both code sets will appear in the same matching run.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "Will banks update NEFT narrations to show new section codes?",
          "a": "Bank NEFT narrations for TDS challan payments — which typically read 'OLTAS TDS 194J' or 'TDS ON PROF FEES 194J' — are not standardised and depend on the originating ERP or payment system. Banks do not automatically update narration formats when legislation changes. After April 1, 2026, narrations may continue to show old section codes if the originating system has not been updated, or may show the new codes if it has. This makes bank narration an unreliable source for section code identification post-transition — reconciliation systems should rely on the TRACES return data rather than bank narrations for section classification.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "What happens to TDS reconciliation for FY 2025-26 returns filed after April 1, 2026?",
          "a": "Q4 FY 2025-26 (January–March 2026) TDS returns have a filing deadline of May 31, 2026 for Form 26Q and 27Q. These returns cover deductions made up to March 31, 2026 and must use old section codes (194C, 194J, etc.) because they relate to transactions under the old Act. Even though they are filed after April 1, 2026, they retain old section numbering. The new Section 393 codes apply only to deductions made on or after April 1, 2026.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "How does Section 393 affect reconciliation for organisations that receive TDS across multiple sections?",
          "a": "For organisations that receive TDS under multiple sections — common for IT services companies receiving TDS under both 194C (project work) and 194J (consulting) — the reconciliation change is significant. Before April 1, 2026, the TDS receivable ledger categorises credits by 194C and 194J. After April 1, new credits will arrive categorised under 393(1)(a) and 393(1)(b). A ledger that cannot store both code sets simultaneously will show reconciliation gaps even when the underlying credits are correct. The mapping table must be maintained at the ledger level, not just in the return filing system.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "Which Section 393 sub-clause maps to TDS on rent of land, building, plant, and machinery?",
          "a": "Section 194I of the 1961 Act — TDS on rent — maps to Section 393(1)(e) of the 2025 Act. The rate structure is preserved: 10% for rent of land, building, or furniture; 2% for rent of plant, machinery, or equipment. The annual threshold of ₹2,40,000 also continues. From April 1, 2026, lessors should expect their Form 26AS rent credits to show '393(1)(e)' in place of '194I'. For real estate-heavy organisations and large landlords, this also affects the rent-roll reconciliation against tenant-side deductor returns.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "Does Section 206AB (higher TDS for non-filers of return) survive under the new Income Tax Act 2025?",
          "a": "The principle of higher TDS for specified non-filers — at twice the applicable rate or 5%, whichever is higher — is retained in the 2025 Act, but it sits within a different section number. Reconciliation systems that maintain a 'specified person' flag against the deductee master should keep the flag intact across the transition, because the underlying compliance check (TRACES Compliance Check API) remains the same lookup. The rate-doubling logic must continue to apply on top of whichever Section 393 sub-clause is the base rate.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "What about Section 195 TDS on payments to non-residents — does that also become Section 393?",
          "a": "No. Section 195 of the 1961 Act, which governs TDS on payments to non-residents (royalty, fees for technical services, interest, dividends), maps to a separate section in the 2025 Act — typically referenced as Section 413 — not Section 393. This is because non-resident TDS depends on Double Taxation Avoidance Agreement (DTAA) treaty rates and PE/withholding-certificate logic that are structurally different from the resident TDS framework. Reconciliation systems should maintain Section 195 / Section 413 as a parallel track to the Section 393 framework, not collapse them into one.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "How should TRACES Form 26AS data be ingested across the transition for cross-year reconciliation?",
          "a": "Pull Form 26AS as separate financial-year files: one for FY 2025-26 (which will continue to carry old section codes for that year's entries even when downloaded after April 1, 2026), and one for FY 2026-27 (which carries the new Section 393 sub-clauses). Tag each row with the deduction date and let your matching engine route on date, not on code. A single combined-year pull can mix old and new codes in the same dataset and confuse rate validation if the matching engine assumes one code set.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "Does the Section 393 change require a re-issue of TDS certificates for FY 2025-26?",
          "a": "No. Form 16A certificates for FY 2025-26 are issued based on Q4 FY 2025-26 quarterly returns (filed by May 31, 2026 with old section codes) and continue to reflect old section codes — 194C, 194J, 194I, etc. — because the underlying deduction event was governed by the 1961 Act. Deductors do not need to re-issue or re-stamp historical certificates. The new Section 393 codes apply only to certificates for deductions made on or after April 1, 2026.",
          "article": "Section 393 Under the New Income Tax Act 2025: What It Means for TDS Reconciliation",
          "url": "https://www.terra-insight.com/insights/section-393-tds-new-income-tax-act-reconciliation"
        },
        {
          "q": "What is the TCS rate on overseas tour packages under Section 206C(1G)?",
          "a": "Tour operators must collect TCS at 5% on overseas tour packages for amounts up to ₹7 lakh per individual per financial year. Above ₹7 lakh, the rate increases to 20%. Effective April 2025, the Finance Act 2025 raised the higher slab threshold to ₹10 lakh for tour packages, with 20% applying above that amount. TCS must be deposited by the 7th of the following month.",
          "article": "TCS on LRS and Overseas Tour Packages: Reconciliation for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tcs-lrs-overseas-tour-reconciliation-india"
        },
        {
          "q": "What is the RBI LRS limit for foreign remittances?",
          "a": "The Reserve Bank of India permits individuals to remit up to USD 250,000 per financial year under the Liberalised Remittance Scheme. This covers education, medical treatment, overseas investments, gifts, and general remittances. The TCS obligation under Section 206C(1G) applies on top of the LRS limit — banks and forex dealers must collect TCS at applicable rates regardless of whether the individual has exhausted their LRS quota.",
          "article": "TCS on LRS and Overseas Tour Packages: Reconciliation for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tcs-lrs-overseas-tour-reconciliation-india"
        },
        {
          "q": "How does a forex dealer track cumulative TCS thresholds per PAN?",
          "a": "The forex dealer must maintain a running total of remittances per PAN per financial year. The first ₹7 lakh in remittances is exempt from TCS for most categories. Once cumulative remittances cross ₹7 lakh, TCS at the applicable rate (0.5%, 5%, or 20% depending on purpose) must be collected on amounts above the threshold. This requires a PAN-indexed ledger updated with every transaction, which becomes unmanageable beyond 200-300 active remitters without a system.",
          "article": "TCS on LRS and Overseas Tour Packages: Reconciliation for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tcs-lrs-overseas-tour-reconciliation-india"
        },
        {
          "q": "Can a buyer claim TCS credit collected on LRS remittances?",
          "a": "Yes. TCS collected under Section 206C(1G) appears in the buyer's Form 26AS and Annual Information Statement (AIS). The buyer claims credit against their total income tax liability when filing their ITR. If the TCS exceeds the tax liability, the excess is refundable. The credit is available only if the collector has deposited the TCS and filed Form 27EQ correctly with the buyer's PAN.",
          "article": "TCS on LRS and Overseas Tour Packages: Reconciliation for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tcs-lrs-overseas-tour-reconciliation-india"
        },
        {
          "q": "What penalty applies if a tour operator does not collect TCS on overseas packages?",
          "a": "The tour operator faces interest at 1% per month under Section 206C(7) from the date TCS should have been collected to the date of actual deposit. Additionally, non-collection can trigger prosecution under Section 276BB. The penalty for late filing of Form 27EQ is ₹200 per day under Section 234E, capped at the total TCS amount for the quarter.",
          "article": "TCS on LRS and Overseas Tour Packages: Reconciliation for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tcs-lrs-overseas-tour-reconciliation-india"
        },
        {
          "q": "What is the TCS rate on motor vehicles under Section 206C(1F)?",
          "a": "Section 206C(1F) requires sellers to collect TCS at 1% on the sale of motor vehicles where the value exceeds ₹10 lakh. This applies to every qualifying sale — there is no aggregate annual threshold. The seller must deposit the TCS with the government by the 7th of the month following collection and report it in Form 27EQ for the relevant quarter.",
          "article": "TCS on Luxury Goods Reconciliation in India: Section 206C Matching",
          "url": "https://www.terra-insight.com/insights/tcs-luxury-goods-reconciliation-india"
        },
        {
          "q": "Is Section 206C(1H) still applicable for TCS on goods above ₹50 lakh?",
          "a": "Section 206C(1H) was abolished effective April 1, 2025 by the Finance Act 2025. It has been replaced by expanded TDS provisions under Section 194Q. However, transactions that occurred before April 2025 still require reconciliation, and any TCS collected under 206C(1H) for prior periods must be matched against Form 27EQ filings and buyer credits in Form 26AS.",
          "article": "TCS on Luxury Goods Reconciliation in India: Section 206C Matching",
          "url": "https://www.terra-insight.com/insights/tcs-luxury-goods-reconciliation-india"
        },
        {
          "q": "What happens if a seller fails to collect TCS under Section 206C?",
          "a": "If a seller fails to collect TCS, the buyer is not absolved of the tax liability. However, the seller faces prosecution under Section 276BB of the Income Tax Act for non-collection. Additionally, interest at 1% per month is levied from the date the TCS should have been collected to the date of actual deposit under Section 206C(7).",
          "article": "TCS on Luxury Goods Reconciliation in India: Section 206C Matching",
          "url": "https://www.terra-insight.com/insights/tcs-luxury-goods-reconciliation-india"
        },
        {
          "q": "How do I reconcile TCS collected with Form 27EQ for a motor vehicle dealership?",
          "a": "Match each vehicle sale above ₹10 lakh against three data points: the TCS amount collected from the buyer at the time of sale, the challan deposit confirming remittance to the government, and the corresponding entry in Form 27EQ. Common mismatches include wrong buyer PAN, incorrect section code (206C(1F) vs 206C(1H)), and late challan deposits that shift the credit to the next quarter.",
          "article": "TCS on Luxury Goods Reconciliation in India: Section 206C Matching",
          "url": "https://www.terra-insight.com/insights/tcs-luxury-goods-reconciliation-india"
        },
        {
          "q": "What is the quarterly filing deadline for Form 27EQ?",
          "a": "Form 27EQ follows the same quarterly deadlines as TDS returns: Q1 (April–June) by July 31, Q2 (July–September) by October 31, Q3 (October–December) by January 31, and Q4 (January–March) by May 31. Late filing attracts a fee of ₹200 per day under Section 234E, capped at the total TCS amount.",
          "article": "TCS on Luxury Goods Reconciliation in India: Section 206C Matching",
          "url": "https://www.terra-insight.com/insights/tcs-luxury-goods-reconciliation-india"
        },
        {
          "q": "When is Form 15CB mandatory before filing Form 15CA?",
          "a": "Form 15CB is mandatory when the remittance is taxable in India and exceeds ₹5 lakh in aggregate in a financial year under a single remittance purpose code, or where a treaty benefit is being claimed. The CA certifying Form 15CB must assess the nature of income, the applicable DTAA rate, and whether TDS has been correctly computed. Form 15CB must be uploaded on the income tax portal before Part C of Form 15CA is filed.",
          "article": "Form 15CA and 15CB: Reconciling TDS on Foreign Remittances for Indian Companies",
          "url": "https://www.terra-insight.com/insights/tds-15ca-15cb-foreign-remittance-reconciliation"
        },
        {
          "q": "What is the TDS rate under Section 195 for payments to non-residents for software subscriptions?",
          "a": "Payments for use of software — classified as royalty under Section 9(1)(vi) — are subject to TDS under Section 195 at 10% plus surcharge and cess (effective rate approximately 10.92% for corporate non-residents in many cases). However, if the applicable DTAA between India and the payee's country provides a lower rate, and the payee submits a Tax Residency Certificate and Form 10F, the treaty rate applies. Some DTAA articles define software payments as business profits rather than royalties, which may eliminate withholding entirely.",
          "article": "Form 15CA and 15CB: Reconciling TDS on Foreign Remittances for Indian Companies",
          "url": "https://www.terra-insight.com/insights/tds-15ca-15cb-foreign-remittance-reconciliation"
        },
        {
          "q": "Which TDS return form covers payments to non-residents under Section 195?",
          "a": "Section 195 payments must be reported in Form 27Q, which is the quarterly TDS return for payments other than salaries made to non-residents. Form 27Q is filed quarterly with due dates of 31 July, 31 October, 31 January, and 31 May. This is separate from Form 26Q (resident payments) and Form 24Q (salaries). The 15CA acknowledgement number must be referenced in the Form 27Q filing.",
          "article": "Form 15CA and 15CB: Reconciling TDS on Foreign Remittances for Indian Companies",
          "url": "https://www.terra-insight.com/insights/tds-15ca-15cb-foreign-remittance-reconciliation"
        },
        {
          "q": "What happens if a company remits funds to a non-resident without filing Form 15CA?",
          "a": "Under Rule 37BB, the authorised dealer bank (AD bank) is required to receive the 15CA acknowledgement number before processing any covered foreign remittance. Remittances made without Form 15CA — where it is required — expose the remitter to prosecution under Section 276B for failure to comply with TDS provisions, as well as potential demand for TDS not deducted and interest under Section 201(1A) at 1.5% per month.",
          "article": "Form 15CA and 15CB: Reconciling TDS on Foreign Remittances for Indian Companies",
          "url": "https://www.terra-insight.com/insights/tds-15ca-15cb-foreign-remittance-reconciliation"
        },
        {
          "q": "How long must a company retain Form 15CA and 15CB records?",
          "a": "There is no specific retention period prescribed solely for 15CA/15CB records, but since they relate to TDS compliance under Section 195, the standard 7-year retention period applicable to financial records under the Companies Act 2013 and the Income Tax Act applies. The records must be available for production during any scrutiny assessment or TDS survey, which can be initiated up to 6 years after the relevant assessment year.",
          "article": "Form 15CA and 15CB: Reconciling TDS on Foreign Remittances for Indian Companies",
          "url": "https://www.terra-insight.com/insights/tds-15ca-15cb-foreign-remittance-reconciliation"
        },
        {
          "q": "How do I know if a TDS challan mismatch is causing my Form 26AS not to update?",
          "a": "Download Form 26AS from TRACES or the Income Tax e-filing portal and compare each entry against your TDS receivable ledger. If an expected credit is absent or shows a different amount, ask your deductor to log into TRACES and verify the challan BSR code, serial number, and deposit date against the OLTAS record. A mismatch between the TDS return entry and the OLTAS challan record is confirmed when the challan status on TRACES shows 'unmatched'.",
          "article": "TDS Challan Mismatch: How to Identify and Resolve Errors",
          "url": "https://www.terra-insight.com/insights/tds-challan-mismatch-resolution"
        },
        {
          "q": "How long does it take for Form 26AS to reflect after a TDS correction return?",
          "a": "After the deductor files a C2 correction return on TRACES and it is accepted, Form 26AS typically updates within 3–7 business days. The exact timing depends on TRACES processing load, which is higher near quarterly filing deadlines. Check Form 26AS after 7 business days and, if unchanged, verify on TRACES that the correction return status shows 'processed'.",
          "article": "TDS Challan Mismatch: How to Identify and Resolve Errors",
          "url": "https://www.terra-insight.com/insights/tds-challan-mismatch-resolution"
        },
        {
          "q": "Can I claim TDS credit in my ITR even if it doesn't appear in Form 26AS yet?",
          "a": "Claiming TDS credit that is absent from Form 26AS is inadvisable. The Income Tax Department's processing system validates ITR claims against Form 26AS data, and a discrepancy will generate a demand notice under Section 143(1). The safer approach is to wait for Form 26AS to update after the deductor files the correction return, or to write to the jurisdictional Assessing Officer with supporting evidence — deductor's challan, TDS certificate, and bank confirmation — before filing the ITR.",
          "article": "TDS Challan Mismatch: How to Identify and Resolve Errors",
          "url": "https://www.terra-insight.com/insights/tds-challan-mismatch-resolution"
        },
        {
          "q": "What is a C2 correction return and when is it required?",
          "a": "A C2 correction return is filed on TRACES by the deductor to correct challan details in an already-filed TDS return. It is required when the BSR code (the 6-digit branch code of the bank where TDS was deposited) or the challan serial number was entered incorrectly in the original return. The C2 correction links the TDS return entry to the correct challan record in OLTAS, allowing Form 26AS to update for the affected deductees.",
          "article": "TDS Challan Mismatch: How to Identify and Resolve Errors",
          "url": "https://www.terra-insight.com/insights/tds-challan-mismatch-resolution"
        },
        {
          "q": "Who is responsible for filing a TDS correction return — the deductor or the deductee?",
          "a": "The deductor is solely responsible for filing the correction return on TRACES. The deductee cannot access or modify the deductor's TDS return. The deductee's role is limited to identifying the mismatch through Form 26AS, notifying the deductor with specific details (expected amount, TAN, quarter, section), and following up until TRACES shows the correction return as processed. Documenting all communication is recommended if the deductor is unresponsive.",
          "article": "TDS Challan Mismatch: How to Identify and Resolve Errors",
          "url": "https://www.terra-insight.com/insights/tds-challan-mismatch-resolution"
        },
        {
          "q": "How do I file a TDS correction return for a wrong PAN?",
          "a": "Log into TRACES (https://www.tdscpc.gov.in) with the deductor's TAN credentials. Download the original accepted TDS return in FVU format from the 'Download Conso File' section. Open the file in NSDL's RPU (Return Preparation Utility), locate the incorrect PAN row, and correct the PAN. Validate the file using the FVU tool, which generates a corrected .fvu file. Upload this file on TRACES as a C1 correction. After submission, TRACES will process the correction within 3–7 business days. Form 26AS for the deductee with the corrected PAN will update once processing is complete.",
          "article": "TDS Correction Return: How to Fix Errors After Filing",
          "url": "https://www.terra-insight.com/insights/tds-correction-return-process"
        },
        {
          "q": "Can I file a correction return after the original return has been processed and Form 26AS updated?",
          "a": "Yes. There is no time limit that prevents filing a correction return after the original has been processed. Even if Form 26AS has already updated with the original return data, a correction return can be filed to fix the error. After the correction is processed (3–7 business days), Form 26AS will update to reflect the corrected information — crediting the correct PAN and removing the credit from the incorrect one in the case of a C1 correction.",
          "article": "TDS Correction Return: How to Fix Errors After Filing",
          "url": "https://www.terra-insight.com/insights/tds-correction-return-process"
        },
        {
          "q": "How many corrections can I make to a single TDS return?",
          "a": "There is no statutory limit on the number of correction returns that can be filed for a single original TDS return. Each correction return builds on the most recently processed version (not on the original). If a C1 correction has been processed, the next correction must be filed against the C1 version, not the original. This means each correction must be filed and processed sequentially — two corrections cannot be uploaded simultaneously and processed in parallel.",
          "article": "TDS Correction Return: How to Fix Errors After Filing",
          "url": "https://www.terra-insight.com/insights/tds-correction-return-process"
        },
        {
          "q": "Does filing a TDS correction return attract any penalty?",
          "a": "Filing a correction return itself does not attract a penalty. If the original TDS return was filed on time, no late-filing fee under Section 234E applies to the correction. However, if the original return was filed late, the ₹200/day Section 234E penalty applied from that point and is not reversed by the subsequent correction. The correction addresses the data errors in the return but does not affect penalties already assessed for the original late filing.",
          "article": "TDS Correction Return: How to Fix Errors After Filing",
          "url": "https://www.terra-insight.com/insights/tds-correction-return-process"
        },
        {
          "q": "What is the NSDL RPU tool and how is it used for TDS correction returns?",
          "a": "NSDL RPU (Return Preparation Utility) is a Java-based tool provided by NSDL TIN for preparing and validating TDS returns and correction returns. It is downloaded from the TRACES portal or the NSDL TIN website. To prepare a correction, download the consolidated statement file (Conso file) from TRACES for the quarter to be corrected, open it in RPU, make the required changes, and then validate the output using the FVU (File Validation Utility) tool. The FVU produces a .fvu file that is then uploaded to TRACES for submission.",
          "article": "TDS Correction Return: How to Fix Errors After Filing",
          "url": "https://www.terra-insight.com/insights/tds-correction-return-process"
        },
        {
          "q": "Can I correct TDS after March 31, 2026 for FY 2018-19?",
          "a": "No. TDS correction statements for FY 2018-19 through FY 2022-23 become permanently time-barred after March 31, 2026 under the limitation period applicable to Section 200 of the Income Tax Act 1961. After this date, the TRACES portal will not permit correction statement filing for these years. Any challan mismatches, PAN errors, or amount discrepancies for these years that are not corrected by March 31, 2026 become irrecoverable from a TDS compliance standpoint.",
          "article": "TDS Correction Statement Deadline: March 31, 2026 Time-Bar for FY 2018–23",
          "url": "https://www.terra-insight.com/insights/tds-correction-statement-march-2026-deadline"
        },
        {
          "q": "What is the penalty for uncorrected TDS mismatches that remain after the March 31 deadline?",
          "a": "Uncorrected TDS mismatches for time-barred years can result in demand notices under Section 200A for short deduction, interest under Section 201(1A) at 1.5% per month from the date of deduction to the date of payment, and disallowance of the underlying expense under Section 40(a)(ia) for contractor/professional fee payments. For amounts that were deducted but not deposited or deposited with incorrect PAN, the deductee may also be unable to claim the TDS credit in their income tax return.",
          "article": "TDS Correction Statement Deadline: March 31, 2026 Time-Bar for FY 2018–23",
          "url": "https://www.terra-insight.com/insights/tds-correction-statement-march-2026-deadline"
        },
        {
          "q": "How do I know if my Form 26AS has pending TDS mismatches?",
          "a": "Download your Form 26AS or Annual Information Statement (AIS) from the Income Tax e-filing portal or TRACES. Compare the TDS entries against your TDS receivable ledger for each financial year. Entries that appear in your ledger but not in 26AS, or where amounts differ, indicate a potential mismatch requiring a correction statement from the deductor. For FY 2018-19 through 2022-23, any deductor-side correction must be filed before March 31, 2026.",
          "article": "TDS Correction Statement Deadline: March 31, 2026 Time-Bar for FY 2018–23",
          "url": "https://www.terra-insight.com/insights/tds-correction-statement-march-2026-deadline"
        },
        {
          "q": "Which financial years remain open for TDS correction after March 31, 2026?",
          "a": "FY 2023-24 and FY 2024-25 correction windows remain open after March 31, 2026. You can file correction statements for these years through TRACES subject to the applicable limitation period. Q4 FY 2025-26 returns and correction statements will also be available. Only the five years from FY 2018-19 through FY 2022-23 are closing on March 31, 2026.",
          "article": "TDS Correction Statement Deadline: March 31, 2026 Time-Bar for FY 2018–23",
          "url": "https://www.terra-insight.com/insights/tds-correction-statement-march-2026-deadline"
        },
        {
          "q": "Can a deductee force the deductor to file a TDS correction statement?",
          "a": "A deductee cannot directly file a correction statement — only the deductor (the party that deducted and deposited the TDS) can do so through TRACES. However, the deductee can raise a grievance on the income tax e-filing portal under the 'TDS Mismatch' category, which can trigger a communication to the deductor. For FY 2018-19 through 2022-23, the deductee should contact the deductor immediately given the March 31, 2026 deadline.",
          "article": "TDS Correction Statement Deadline: March 31, 2026 Time-Bar for FY 2018–23",
          "url": "https://www.terra-insight.com/insights/tds-correction-statement-march-2026-deadline"
        },
        {
          "q": "What is the last date to deposit TDS for March 2026?",
          "a": "TDS deducted during March must be deposited by 30 April 2026. This is an exception to the standard rule — for all other months (April through February), TDS must be deposited by the 7th of the following month. The extended deadline for March applies to both government and non-government deductors.",
          "article": "TDS Compliance Calendar: Filing Deadlines, Reconciliation Windows, and Penalty Dates for FY 2025-26",
          "url": "https://www.terra-insight.com/insights/tds-compliance-calendar-india"
        },
        {
          "q": "What is the penalty for late filing of a TDS return under Section 234E?",
          "a": "Section 234E imposes a fee of ₹200 per day for each day the TDS return is filed after the due date. The fee is capped at the total TDS amount for that quarter — so it cannot exceed what was deducted. For a quarterly return with ₹5 lakh TDS and a 30-day delay, the Section 234E fee would be ₹6,000 (30 days x ₹200). This is in addition to any interest payable under Section 201(1A).",
          "article": "TDS Compliance Calendar: Filing Deadlines, Reconciliation Windows, and Penalty Dates for FY 2025-26",
          "url": "https://www.terra-insight.com/insights/tds-compliance-calendar-india"
        },
        {
          "q": "By when must Form 16A be issued for non-salary TDS deductions?",
          "a": "Form 16A must be issued within 15 days of the due date for filing the TDS return for that quarter. For Q1 (April-June), the return is due 31 July, so Form 16A must be issued by 15 August. For Q4 (January-March), the return is due 31 May, so Form 16A must be issued by 15 June. Form 16 for salary TDS has a different deadline — 15 June following the end of the financial year.",
          "article": "TDS Compliance Calendar: Filing Deadlines, Reconciliation Windows, and Penalty Dates for FY 2025-26",
          "url": "https://www.terra-insight.com/insights/tds-compliance-calendar-india"
        },
        {
          "q": "What interest applies if TDS is deducted but deposited late?",
          "a": "Section 201(1A) charges interest at 1.5% per month (or part of a month) from the date TDS was deducted to the date it is actually deposited. If TDS of ₹1 lakh deducted on 15 April is deposited on 20 June — a delay of two months and a part month — interest would be 1.5% x 3 months = 4.5%, i.e., ₹4,500. This is separate from Section 234E penalties for late return filing.",
          "article": "TDS Compliance Calendar: Filing Deadlines, Reconciliation Windows, and Penalty Dates for FY 2025-26",
          "url": "https://www.terra-insight.com/insights/tds-compliance-calendar-india"
        },
        {
          "q": "When should reconciliation of TDS receivable against Form 26AS be performed?",
          "a": "There are three structured reconciliation windows in the TDS compliance calendar: (1) after each quarterly return — compare Form 26AS entries for the quarter against the TDS receivable ledger; (2) after Form 16A issuance — confirm deductee certificates match your books; (3) March year-end close — reconcile full-year TDS receivable against Form 26AS and AIS before finalising the balance sheet. Reconciling only at year-end leaves discrepancies unresolved past the deductor's quarterly correction deadline.",
          "article": "TDS Compliance Calendar: Filing Deadlines, Reconciliation Windows, and Penalty Dates for FY 2025-26",
          "url": "https://www.terra-insight.com/insights/tds-compliance-calendar-india"
        },
        {
          "q": "What is the time limit for filing a Section 154 rectification for TDS credit mismatch?",
          "a": "Section 154 rectification can be filed within 4 years from the end of the financial year in which the original assessment order was passed. For example, an assessment order for AY 2023-24 passed on March 31, 2024 can be rectified until March 31, 2028. The rectification must involve a mistake apparent from the record, meaning the AO should be able to verify the TDS credit from Form 26AS or the deductor's TDS return without further inquiry.",
          "article": "TDS Credit Recovery: Every Mechanism Available When Form 26AS Doesn't Match",
          "url": "https://www.terra-insight.com/insights/tds-credit-recovery-mechanisms-india"
        },
        {
          "q": "How does CBDT Instruction No. 5/2013 help recover TDS credit not reflected in Form 26AS?",
          "a": "CBDT Instruction No. 5/2013 directs Assessing Officers to verify TDS credit by examining the deductor's TDS return, the challan payment details, and the deductee's bank statement showing the net-of-TDS receipt. If the AO is satisfied that TDS was genuinely deducted, credit must be granted even if Form 26AS does not show it. This instruction operationalises the Section 205 bar, which prohibits the department from recovering the same tax from the deductee when the deductor has already deducted it.",
          "article": "TDS Credit Recovery: Every Mechanism Available When Form 26AS Doesn't Match",
          "url": "https://www.terra-insight.com/insights/tds-credit-recovery-mechanisms-india"
        },
        {
          "q": "What additional tax is payable when filing an updated return under Section 139(8A)?",
          "a": "An updated return filed within 12 months of the end of the relevant assessment year attracts an additional tax of 25% on the aggregate of tax and interest payable. If filed between 12 and 24 months, the additional tax rises to 50%. For example, an updated return for AY 2024-25 filed by March 31, 2026 attracts 25% additional tax, while one filed by March 31, 2027 attracts 50%. An ITR-U cannot be filed if the total tax liability decreases.",
          "article": "TDS Credit Recovery: Every Mechanism Available When Form 26AS Doesn't Match",
          "url": "https://www.terra-insight.com/insights/tds-credit-recovery-mechanisms-india"
        },
        {
          "q": "Can TDS credit be claimed if the deductor has not deposited the TDS with the government?",
          "a": "Yes. Section 205 of the Income Tax Act bars the department from demanding the same tax from the deductee if TDS was deducted by the deductor. The obligation to deposit lies solely with the deductor, and the deductee cannot be penalised for the deductor's default. CBDT Instruction No. 5/2013 reinforces this by directing AOs to verify and grant credit based on documentary evidence including bank statements and invoices.",
          "article": "TDS Credit Recovery: Every Mechanism Available When Form 26AS Doesn't Match",
          "url": "https://www.terra-insight.com/insights/tds-credit-recovery-mechanisms-india"
        },
        {
          "q": "What is the deadline to respond to a Section 143(1) demand notice for TDS credit mismatch?",
          "a": "A demand notice issued under Section 143(1) for disallowed TDS credit must be responded to within 30 days from the date of service. The response is filed on the Income Tax e-filing portal under the 'Response to Outstanding Demand' section. If the demand is not addressed within 30 days, interest under Sections 234B and 234C begins to accrue on the outstanding amount, and the AO may initiate recovery proceedings.",
          "article": "TDS Credit Recovery: Every Mechanism Available When Form 26AS Doesn't Match",
          "url": "https://www.terra-insight.com/insights/tds-credit-recovery-mechanisms-india"
        },
        {
          "q": "What triggers a Section 200A TDS demand notice?",
          "a": "Section 200A empowers the Income Tax Department to process a TDS return and send an intimation raising a demand for short deduction, interest under Section 201(1A) at 1% per month from deduction date to deposit date (or 1.5% per month from deposit date to payment date), late filing fees under Section 234E at ₹200 per day, or adjustments for PAN or challan mismatches.",
          "article": "TDS Demand Notice Under Section 200A: How to Reconcile and Respond",
          "url": "https://www.terra-insight.com/insights/tds-demand-notice-reconciliation-india"
        },
        {
          "q": "What is the interest rate for late TDS deposit under Section 201(1A)?",
          "a": "Section 201(1A) prescribes interest at 1% per month (or part of a month) from the date TDS was deductible to the date it was actually deducted, and 1.5% per month from the date TDS was deducted to the date it was deposited. Both components accumulate separately and are shown as distinct line items in the Section 200A intimation.",
          "article": "TDS Demand Notice Under Section 200A: How to Reconcile and Respond",
          "url": "https://www.terra-insight.com/insights/tds-demand-notice-reconciliation-india"
        },
        {
          "q": "What is the late filing fee under Section 234E for TDS returns?",
          "a": "Section 234E imposes a fee of ₹200 per day for each day of delay in filing the TDS return, subject to a maximum equal to the TDS amount itself. The fee accrues from the due date of the quarterly TDS return — typically 31 July, 31 October, 31 January, and 31 May for the respective quarters.",
          "article": "TDS Demand Notice Under Section 200A: How to Reconcile and Respond",
          "url": "https://www.terra-insight.com/insights/tds-demand-notice-reconciliation-india"
        },
        {
          "q": "How do I rectify a challan mismatch shown in a Section 200A demand?",
          "a": "A challan mismatch arises when challan details entered in the TDS return — BSR code, challan serial number, deposit date, or amount — do not match OLTAS records. Rectification requires filing a correction statement through TRACES. After the correction is processed, typically within 3–7 working days, the mismatch is resolved and the demand is revised.",
          "article": "TDS Demand Notice Under Section 200A: How to Reconcile and Respond",
          "url": "https://www.terra-insight.com/insights/tds-demand-notice-reconciliation-india"
        },
        {
          "q": "Can a Section 200A demand be contested if the TDS records are correct?",
          "a": "Yes. Where TRACES records show correct deduction and deposit but the intimation is erroneous, the deductor may file a rectification application under Section 154 on the income tax portal. The rectification must be filed within 4 years from the end of the financial year in which the intimation was issued.",
          "article": "TDS Demand Notice Under Section 200A: How to Reconcile and Respond",
          "url": "https://www.terra-insight.com/insights/tds-demand-notice-reconciliation-india"
        },
        {
          "q": "When is TDS deducted on ESOPs in India — at grant, vesting, or sale?",
          "a": "TDS is deducted at the time of exercise (vesting and exercise are often contemporaneous in Indian ESOP structures). Under Section 17(2) read with Section 192, the perquisite arises when the employee exercises the option and acquires shares. TDS is not deducted at grant (since no benefit has transferred) or at sale (capital gains tax applies at that stage, not TDS). The taxable perquisite value is (FMV on date of exercise minus grant price) multiplied by the number of shares.",
          "article": "TDS on ESOP Perquisites Under Section 192: Reconciliation Challenges",
          "url": "https://www.terra-insight.com/insights/tds-esop-section-192-india"
        },
        {
          "q": "How is FMV determined for ESOP TDS calculation for an unlisted company in India?",
          "a": "For shares of unlisted companies, the Income Tax Rules require that FMV be determined by a registered merchant banker as on the date of exercise. The merchant banker issues a valuation certificate using SEBI-recognised methods (typically discounted cash flow or comparable company multiples). The valuation certificate date must be within 180 days of the exercise date. For listed companies, FMV is the average of the opening and closing price on NSE or BSE on the exercise date.",
          "article": "TDS on ESOP Perquisites Under Section 192: Reconciliation Challenges",
          "url": "https://www.terra-insight.com/insights/tds-esop-section-192-india"
        },
        {
          "q": "What happens to TDS if an employee leaves before exercising vested ESOPs?",
          "a": "If an employee has vested ESOPs but leaves without exercising them, the unvested options lapse and there is no TDS obligation. For vested but unexercised options, the treatment depends on the ESOP plan: most plans lapse unvested and unexercised options within 30 to 90 days of resignation. If the employee exercised options before resignation, the TDS would already have been deducted and deposited at the time of exercise. The employer's TDS liability ends at the point of departure.",
          "article": "TDS on ESOP Perquisites Under Section 192: Reconciliation Challenges",
          "url": "https://www.terra-insight.com/insights/tds-esop-section-192-india"
        },
        {
          "q": "How should ESOP perquisite value appear in Form 16?",
          "a": "Form 16 Part B must show the ESOP perquisite value under the head 'Value of perquisites under Section 17(2)'. The perquisite value is added to gross salary for the purpose of computing the employee's total income and TDS. Employers must ensure the perquisite value is reflected in both the TDS return (Form 24Q) for the relevant quarter and in Form 16 Part B issued at year-end. Omitting ESOP perquisite from Form 24Q creates a mismatch when the employee files their ITR.",
          "article": "TDS on ESOP Perquisites Under Section 192: Reconciliation Challenges",
          "url": "https://www.terra-insight.com/insights/tds-esop-section-192-india"
        },
        {
          "q": "For ESOPs granted by a foreign parent company to an Indian employee, who deducts TDS?",
          "a": "When a foreign parent company grants ESOPs to employees of its Indian subsidiary, the TDS obligation falls on the Indian employer under Section 192. The Indian entity is treated as having derived a benefit from the parent (the share issuance), and it must include the perquisite value in the employee's salary and deduct TDS accordingly. If the Indian entity does not have a formal arrangement with the parent for cost reimbursement, the tax department may still hold the Indian entity liable for TDS on the perquisite.",
          "article": "TDS on ESOP Perquisites Under Section 192: Reconciliation Challenges",
          "url": "https://www.terra-insight.com/insights/tds-esop-section-192-india"
        },
        {
          "q": "How do I apply for a lower TDS deduction certificate in India?",
          "a": "Applications are filed online through the TRACES portal (https://www.tdscpc.gov.in) using Form 13. The applicant submits projected income, estimated total tax liability, existing TDS and advance tax payments, and the TDS sections for which a lower rate is sought. The application is reviewed by the Assessing Officer (AO) of the applicant's jurisdictional income tax office. If satisfied, the AO issues the certificate specifying the lower rate and the sections to which it applies. The certificate is valid for the financial year stated in it—not beyond.",
          "article": "TDS Lower Deduction Certificate Under Section 197: Process and Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-lower-deduction-certificate-197"
        },
        {
          "q": "How long does it take to receive a lower deduction certificate under Section 197?",
          "a": "The statutory deadline for the AO to respond is 30 days from the date of application. In practice, processing takes 4–8 weeks, particularly at peak periods before April and October when filings are highest. Applications submitted in February or March for the next financial year face longer queues. Applicants expecting a new-year certificate should apply by January to allow processing time.",
          "article": "TDS Lower Deduction Certificate Under Section 197: Process and Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-lower-deduction-certificate-197"
        },
        {
          "q": "Can a deductor apply a lower rate without seeing the Section 197 certificate?",
          "a": "No. A deductor who applies a lower TDS rate without a valid Section 197 certificate on file remains liable for the difference between the standard rate and the lower rate applied, plus interest under Section 201. The deductor must verify the certificate on TRACES before the first payment at the reduced rate, and should retain a copy of the certificate with the date of TRACES verification. If the certificate is later found to be invalid, the deductor bears the shortfall risk.",
          "article": "TDS Lower Deduction Certificate Under Section 197: Process and Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-lower-deduction-certificate-197"
        },
        {
          "q": "How does a lower deduction certificate affect TDS reconciliation in Form 26AS?",
          "a": "Form 26AS reflects the rate actually deducted, which will be the lower certificate rate rather than the standard section rate. A recipient holding a 194J certificate at 2% (instead of the standard 10%) will see 2% entries in Form 26AS Part A. The TDS receivable ledger in the recipient's books must be updated to record the expected TDS at the lower rate—failing to do this creates a phantom shortfall in the ledger that takes time to investigate and write off.",
          "article": "TDS Lower Deduction Certificate Under Section 197: Process and Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-lower-deduction-certificate-197"
        },
        {
          "q": "Is a lower deduction certificate valid across all deductors?",
          "a": "Yes. The certificate issued by the AO is presented by the recipient to each deductor separately. Each deductor independently verifies the certificate on TRACES using the certificate number before applying the lower rate. There is no limit on the number of deductors to whom the same certificate can be furnished, provided the certificate's aggregate amount limit is not exceeded across all deductors in the financial year.",
          "article": "TDS Lower Deduction Certificate Under Section 197: Process and Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-lower-deduction-certificate-197"
        },
        {
          "q": "Which TDS section applies when a client deducts TDS on professional fees — Section 194J or 194C?",
          "a": "Section 194J applies to professional fees and technical services at 10% (or 2% for technical services). Section 194C applies to contracts and sub-contracts at 1% for individuals/HUFs and 2% for others. The correct section depends on the nature of engagement. A professional service engagement — legal, consulting, medical, architectural — falls under 194J. If a client misclassifies and deducts under 194C, the rate difference creates a mismatch between TDS deducted and TDS expected in the recipient's books.",
          "article": "Multiple Deductors, One PAN: Reconciling TDS from Multiple Sources in India",
          "url": "https://www.terra-insight.com/insights/tds-multi-deductor-reconciliation-india"
        },
        {
          "q": "What happens if a deductor files their TDS return late and the entry does not appear in Form 26AS?",
          "a": "If a deductor files their quarterly TDS return after the due date, the TDS entry will appear in the recipient's Form 26AS only after the return is processed. This means the recipient's 26AS may be incomplete at the time of advance tax computation or ITR filing. The recipient can claim the TDS credit in the ITR even if 26AS is not yet updated, but the refund or tax payable amount will be subject to verification against the deductor's filing.",
          "article": "Multiple Deductors, One PAN: Reconciling TDS from Multiple Sources in India",
          "url": "https://www.terra-insight.com/insights/tds-multi-deductor-reconciliation-india"
        },
        {
          "q": "How does a company with a multi-employer salary scenario avoid short TDS deduction?",
          "a": "An employee who joins a new employer mid-year must disclose previous salary and TDS deducted by the former employer by submitting Form 12B to the new employer. The new employer aggregates the total income for the year and deducts TDS under Section 192 on the balance. Without Form 12B disclosure, the new employer deducts TDS only on their portion, resulting in total annual TDS that is less than required, and the employee faces a demand when the ITR is processed.",
          "article": "Multiple Deductors, One PAN: Reconciling TDS from Multiple Sources in India",
          "url": "https://www.terra-insight.com/insights/tds-multi-deductor-reconciliation-india"
        },
        {
          "q": "Can a recipient of TDS claim credit for TDS that appears in 26AS but has no matching invoice in their books?",
          "a": "No. A 26AS entry with no matching income in the recipient's books typically indicates a deductor error — they may have entered the wrong PAN and the TDS belongs to a different entity. The recipient should not claim this credit and should report the discrepancy to the deductor for correction through a TRACES correction statement. Claiming credit for TDS on income not recorded in books can trigger scrutiny during ITR processing.",
          "article": "Multiple Deductors, One PAN: Reconciling TDS from Multiple Sources in India",
          "url": "https://www.terra-insight.com/insights/tds-multi-deductor-reconciliation-india"
        },
        {
          "q": "What is the deadline to reconcile Form 26AS against books before filing an ITR?",
          "a": "There is no regulatory deadline for internal reconciliation, but practical reconciliation must be complete before the ITR due date — 31 July for non-audit cases and 31 October for audit cases. For companies, the audit ITR deadline is 31 October. Reconciliation performed after ITR filing cannot change the filed return without a revised return, which must be filed before 31 December of the assessment year.",
          "article": "Multiple Deductors, One PAN: Reconciling TDS from Multiple Sources in India",
          "url": "https://www.terra-insight.com/insights/tds-multi-deductor-reconciliation-india"
        },
        {
          "q": "Is TDS deductible on the GST portion of an invoice in India?",
          "a": "No. CBDT Circular No. 23/2017 clarifies that TDS under Chapter XVII-B of the Income Tax Act is not deductible on the GST component of an invoice. TDS must be computed only on the base value (the amount before GST). This applies to all TDS sections including 194C, 194J, 194H, and 194I.",
          "article": "TDS on GST Component: How to Handle GST-Inclusive Invoices Correctly",
          "url": "https://www.terra-insight.com/insights/tds-on-gst-component-india"
        },
        {
          "q": "What happens if TDS is deducted on the full invoice amount including GST?",
          "a": "The excess TDS gets deposited against the vendor's PAN and appears in their Form 26AS. However, the excess amount represents tax deducted on the GST portion — which the vendor already pays to the government separately. The vendor cannot claim the excess TDS as a credit against income tax, making it an erroneous entry that requires a correction return from the deductor.",
          "article": "TDS on GST Component: How to Handle GST-Inclusive Invoices Correctly",
          "url": "https://www.terra-insight.com/insights/tds-on-gst-component-india"
        },
        {
          "q": "How do I correct TDS deducted wrongly on a GST-inclusive amount?",
          "a": "File a correction return (Form 26Q or 27Q as applicable) through TRACES. In the correction, revise the TDS amount to reflect deduction on the base value only. If the excess TDS has already been deposited, you can adjust the excess in a subsequent challan or claim a refund through TRACES. The vendor's Form 26AS will update once the correction is processed — typically within 7 to 10 working days.",
          "article": "TDS on GST Component: How to Handle GST-Inclusive Invoices Correctly",
          "url": "https://www.terra-insight.com/insights/tds-on-gst-component-india"
        },
        {
          "q": "Does the GST component change when a buyer pays GST under reverse charge mechanism (RCM)?",
          "a": "Under RCM, the buyer pays GST directly to the government rather than to the vendor. The vendor receives the full base invoice amount without a GST charge on the invoice. TDS is still computed on the base invoice value only. Even if the buyer is paying GST separately under RCM, the TDS computation does not change — it remains on the contractual service value.",
          "article": "TDS on GST Component: How to Handle GST-Inclusive Invoices Correctly",
          "url": "https://www.terra-insight.com/insights/tds-on-gst-component-india"
        },
        {
          "q": "If a vendor does not show GST separately on the invoice, how should TDS be computed?",
          "a": "The deductor should ask the vendor to issue a revised invoice that separately discloses the base value and the GST component. If the vendor cannot provide a breakup, the deductor should compute TDS on the estimated base value (total divided by 1 plus the applicable GST rate). For an 18% GST invoice of ₹1,18,000, the base value is ₹1,00,000 and TDS should be deducted on ₹1,00,000.",
          "article": "TDS on GST Component: How to Handle GST-Inclusive Invoices Correctly",
          "url": "https://www.terra-insight.com/insights/tds-on-gst-component-india"
        },
        {
          "q": "What TDS rate applies when a vendor does not provide a valid PAN?",
          "a": "Under Section 206AA, if a deductee fails to furnish a valid PAN, TDS must be deducted at the highest of three rates: the rate specified in the relevant section (e.g., 2% under 194C or 10% under 194J), the rate in force under the Finance Act, or 20%. For most vendor payments, the 20% floor applies. This rate applies per transaction — there is no threshold below which 206AA can be ignored.",
          "article": "TDS PAN Validation Failures: How PAN Mismatches Trigger Higher Deduction Rates",
          "url": "https://www.terra-insight.com/insights/tds-pan-validation-mismatch-india"
        },
        {
          "q": "What happens if a vendor's PAN is linked to Aadhaar after TDS was already deducted at 20%?",
          "a": "If a vendor's PAN becomes operative after Aadhaar linking and TDS was already deducted at 20% under Section 206AA, the deductor cannot reverse the deduction retroactively for past payments. Going forward, once the PAN is operative and validated on TRACES, the correct section rate applies. The vendor can claim the excess TDS as a refund when filing their income tax return, provided the deductor has quoted the PAN correctly in the filed TDS return.",
          "article": "TDS PAN Validation Failures: How PAN Mismatches Trigger Higher Deduction Rates",
          "url": "https://www.terra-insight.com/insights/tds-pan-validation-mismatch-india"
        },
        {
          "q": "How do I validate PAN in bulk before filing a 24Q return?",
          "a": "TRACES provides a 'PAN Verification' facility under the 'Statements/Payments' section. Upload a CSV file with the vendor PANs you want to verify, and TRACES returns a status for each: valid, invalid, inoperative, or not found. Run this check before each quarterly return filing — not just before year-end. An inoperative PAN status confirmed before filing allows you to deduct at 20% and document the TRACES output as the audit evidence.",
          "article": "TDS PAN Validation Failures: How PAN Mismatches Trigger Higher Deduction Rates",
          "url": "https://www.terra-insight.com/insights/tds-pan-validation-mismatch-india"
        },
        {
          "q": "Does Section 206AA apply to foreign vendors with no Indian PAN?",
          "a": "Yes. For non-resident vendors without an Indian PAN, Section 206AA requires TDS at 20% or the applicable treaty rate plus applicable surcharge and cess, whichever is higher. An exception exists under Rule 37BC: if a non-resident provides details including name, address, email, and country of residence, and no PAN is available, the 20% rate under 206AA does not apply — provided the payment is under a treaty and Form 10F is furnished.",
          "article": "TDS PAN Validation Failures: How PAN Mismatches Trigger Higher Deduction Rates",
          "url": "https://www.terra-insight.com/insights/tds-pan-validation-mismatch-india"
        },
        {
          "q": "What is the difference between an invalid PAN and an inoperative PAN for TDS purposes?",
          "a": "An invalid PAN does not exist in the Income Tax Department's database — it may be a fabricated or incorrectly quoted number. An inoperative PAN exists but has been deactivated because it was not linked to Aadhaar by 31 May 2024. Both are treated identically for TDS purposes under the Finance Act 2023: deductions must be made at the Section 206AA higher rate. TRACES PAN verification will return 'inoperative' for the latter, giving the deductor a clear audit record.",
          "article": "TDS PAN Validation Failures: How PAN Mismatches Trigger Higher Deduction Rates",
          "url": "https://www.terra-insight.com/insights/tds-pan-validation-mismatch-india"
        },
        {
          "q": "What is the interest rate for late deposit of TDS?",
          "a": "Late deposit of TDS attracts interest at 1.5% per month under Section 201(1A), calculated from the date of deduction to the date of actual deposit. The interest is computed on a per-month basis — even a one-day delay counts as a full month. For ₹1 crore in monthly TDS, a systematic one-day delay generates ₹1.5 lakh per month or ₹18 lakh annually in interest.",
          "article": "TDS Penalty and Interest: The Complete Multi-Layered Consequence Framework",
          "url": "https://www.terra-insight.com/insights/tds-penalty-interest-regime-india"
        },
        {
          "q": "What is the penalty for not deducting TDS at all?",
          "a": "Non-deduction triggers three concurrent consequences: the deductor becomes an assessee-in-default under Section 201(1) and must pay the TDS from own funds, interest accrues at 1% per month from the date TDS was deductible, and 30% of the payment amount is disallowed as a business expenditure under Section 40(a)(ia). For a ₹10 lakh professional fee payment where TDS was not deducted, the combined exposure is approximately ₹1.87 lakh in the first year.",
          "article": "TDS Penalty and Interest: The Complete Multi-Layered Consequence Framework",
          "url": "https://www.terra-insight.com/insights/tds-penalty-interest-regime-india"
        },
        {
          "q": "Can the Assessing Officer impose a penalty for delayed TDS deposit under Section 271C?",
          "a": "No. The Supreme Court in Hindustan Coca-Cola Beverages Pvt. Ltd. v. CIT (2007) and the more recent US Technologies International v. CIT (April 2023) held that Section 271C penalty applies only to failure to deduct TDS, not to delayed deposit after deduction. Late deposit consequences are limited to Section 201(1A) interest and potential prosecution under Section 276B.",
          "article": "TDS Penalty and Interest: The Complete Multi-Layered Consequence Framework",
          "url": "https://www.terra-insight.com/insights/tds-penalty-interest-regime-india"
        },
        {
          "q": "What is the late filing fee under Section 234E for TDS returns?",
          "a": "Section 234E imposes a fee of ₹200 per day for every day the TDS return remains unfiled after the due date. The fee is capped at the total TDS amount reported in the return. Additionally, Section 271H allows the Assessing Officer to levy a penalty between ₹10,000 and ₹1,00,000 if the return is not filed within one year of the due date or contains incorrect information.",
          "article": "TDS Penalty and Interest: The Complete Multi-Layered Consequence Framework",
          "url": "https://www.terra-insight.com/insights/tds-penalty-interest-regime-india"
        },
        {
          "q": "Can directors be personally prosecuted for TDS defaults?",
          "a": "Yes. Under Section 278B of the Income Tax Act, when a company commits an offence under Section 276B (failure to deposit TDS), every person who was in charge of and responsible for the conduct of the company's business at the time of the offence is deemed guilty. This includes managing directors and finance directors. The Supreme Court upheld director-level prosecution in Sasi Enterprises v. ACIT (2014) 5 SCC 139, confirming imprisonment of 3 months to 7 years with rigorous imprisonment and fine.",
          "article": "TDS Penalty and Interest: The Complete Multi-Layered Consequence Framework",
          "url": "https://www.terra-insight.com/insights/tds-penalty-interest-regime-india"
        },
        {
          "q": "What is the deadline for filing a TDS return for Q4 (January–March)?",
          "a": "The Q4 TDS return (Form 26Q or 27Q for non-salary; Form 24Q for salary) is due on 31 May. Other quarters: Q1 (April–June) is due 31 July; Q2 (July–September) is due 31 October; Q3 (October–December) is due 31 January. These deadlines apply to the return filing, not the challan deposit. TDS must be deposited by the 7th of the following month (30 April for the March deductions).",
          "article": "TDS Quarterly Return Reconciliation: Process and Common Errors",
          "url": "https://www.terra-insight.com/insights/tds-quarterly-filing-reconciliation"
        },
        {
          "q": "How many days before the filing deadline should I start TDS return reconciliation?",
          "a": "Start at least 10–15 working days before the deadline. The most common error in quarterly filing is rushing data validation in the final 2–3 days: deductee PANs are unverified, challan serial numbers are copied from the previous quarter, and section codes are incorrectly assigned. Starting early allows time to resolve PAN invalidation errors (which NSDL's FVU rejects) and to verify challan deposits against OLTAS before the return file is prepared.",
          "article": "TDS Quarterly Return Reconciliation: Process and Common Errors",
          "url": "https://www.terra-insight.com/insights/tds-quarterly-filing-reconciliation"
        },
        {
          "q": "What happens if TDS is deducted but the quarterly return is not filed on time?",
          "a": "A late filing fee of ₹200 per day applies under Section 234E, from the day after the due date until the return is filed, subject to a maximum of the total TDS amount for that quarter. This is a mandatory fee, not a penalty that can be waived — it is calculated automatically and reflected in the TRACES demand. In addition, Form 26AS for all deductees in that return will not update until the return is filed and processed, delaying their credit claims.",
          "article": "TDS Quarterly Return Reconciliation: Process and Common Errors",
          "url": "https://www.terra-insight.com/insights/tds-quarterly-filing-reconciliation"
        },
        {
          "q": "Can I revise a TDS return after filing if I find errors?",
          "a": "Yes. Correction returns are filed on TRACES. The type depends on the error: C1 corrects deductee PAN, C2 corrects challan BSR code or serial number, C3 corrects salary/deduction details in Form 24Q. Multiple corrections can be filed, each building on the previous corrected version. There is no limit on the number of corrections, but each correction takes 3–7 business days to process, so catching errors before filing is significantly more efficient.",
          "article": "TDS Quarterly Return Reconciliation: Process and Common Errors",
          "url": "https://www.terra-insight.com/insights/tds-quarterly-filing-reconciliation"
        },
        {
          "q": "How do I verify that my TDS return has been accepted and processed by the department?",
          "a": "Log into the TRACES portal (https://www.tdscpc.gov.in) with the deductor TAN and check the return filing status. A processed return will show the status as 'processed' with a statement token number. Additionally, after processing, Form 26AS for the listed deductees will begin updating — you can verify this by checking one or two deductee PANs. If status shows 'pending' after 10 business days, contact TRACES helpdesk for the specific statement token.",
          "article": "TDS Quarterly Return Reconciliation: Process and Common Errors",
          "url": "https://www.terra-insight.com/insights/tds-quarterly-filing-reconciliation"
        },
        {
          "q": "When should TDS receivable be recorded in the books — on invoice date or receipt date?",
          "a": "Under the accrual basis of accounting, the invoice is recorded gross (including the TDS component) on the invoice date. The TDS receivable is recognised as a separate asset at this point, representing the expected tax credit. However, the TDS credit can only be claimed in the ITR when it appears in Form 26AS — which depends on the deductor depositing the challan and filing the quarterly return. The accounting entry and the claimable credit are therefore on different timelines, making reconciliation between the TDS receivable ledger and Form 26AS essential.",
          "article": "TDS Receivable Ledger Reconciliation: Matching Books to Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-receivable-ledger-reconciliation"
        },
        {
          "q": "How do I handle TDS receivable that hasn't appeared in Form 26AS after 3 months?",
          "a": "After 3 months without a Form 26AS credit, initiate a structured follow-up: (1) Contact the deductor and request the TDS certificate (Form 16A) and challan details for the relevant payment. (2) Ask the deductor to verify on TRACES that the quarterly return for that period has been filed and processed. (3) Check whether the deductor's TDS return shows your PAN correctly — an invalid or incorrect PAN is a frequent cause of missing credits. If the deductor confirms the return is filed but the credit is still absent, escalate to verify the challan BSR code and serial number.",
          "article": "TDS Receivable Ledger Reconciliation: Matching Books to Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-receivable-ledger-reconciliation"
        },
        {
          "q": "Can I claim TDS credit in ITR if it's in my TDS receivable ledger but not in Form 26AS?",
          "a": "No. The Income Tax Department's return processing system validates TDS credit claims directly against Form 26AS data. A claim that exceeds Form 26AS will generate a demand notice under Section 143(1). The TDS receivable ledger is an internal accounting document; it has no standing as evidence for credit claims. If a credit is in the ledger but not in Form 26AS, the resolution path is to obtain the correction from the deductor — not to claim the amount and explain it later.",
          "article": "TDS Receivable Ledger Reconciliation: Matching Books to Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-receivable-ledger-reconciliation"
        },
        {
          "q": "How do I reconcile TDS receivable when the same client deducts from 3 different branch TANs?",
          "a": "Aggregate the expected TDS by client PAN first to get the total credit expected from that client. Then split the Form 26AS entries by each of the three TANs to verify that the combined credit equals the ledger total. Form 26AS displays TDS by deductor TAN, so each branch will appear as a separate entry. At the invoice level, record the expected TAN alongside each receivable entry — this enables TAN-level matching when Form 26AS is downloaded, and identifies which specific branch's return has a problem when a credit is missing.",
          "article": "TDS Receivable Ledger Reconciliation: Matching Books to Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-receivable-ledger-reconciliation"
        },
        {
          "q": "What is the best ERP configuration to make TDS receivable reconciliation easier?",
          "a": "Capture the deductor's TAN at the invoice or purchase order level, not just at the vendor master level. Tag the applicable TDS section code on each invoice (since the same vendor may be subject to different sections for different service types). Configure the export report to group TDS receivable by TAN and quarter — this mirrors the structure of Form 26AS and eliminates a manual restructuring step when running the reconciliation. If the ERP allows, store the Form 16A certificate reference number against the corresponding ledger entry when the certificate is received.",
          "article": "TDS Receivable Ledger Reconciliation: Matching Books to Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-receivable-ledger-reconciliation"
        },
        {
          "q": "Which TDS section applies to IT services companies in India?",
          "a": "IT services companies are primarily subject to Section 194J. Professional services (consulting, advisory, software customisation) attract 10% TDS. Technical services (standard software maintenance, data processing) attract 2% following the CBDT amendment effective April 2020. If a client misclassifies services as a works contract under Section 194C (2%), the vendor must raise a correction request because the Form 26AS credit will be lower than expected.",
          "article": "TDS Reconciliation for IT Services Companies: 194J at Scale",
          "url": "https://www.terra-insight.com/insights/tds-reconciliation-it-services-india"
        },
        {
          "q": "How should an IT company handle a client deducting TDS under 194C instead of 194J?",
          "a": "First, review the client's purchase order and service agreement to confirm whether the engagement is professional services (194J at 10%) or technical services (194J at 2%). If 194C is incorrect, issue a formal written clarification to the client citing the nature of services. The client must file a correction return for the relevant quarter to revise the section code. Until corrected, the lower TDS credit in Form 26AS creates a receivable shortfall that must be disclosed at ITR time.",
          "article": "TDS Reconciliation for IT Services Companies: 194J at Scale",
          "url": "https://www.terra-insight.com/insights/tds-reconciliation-it-services-india"
        },
        {
          "q": "What should an IT company do when Form 26AS shows lower TDS credit than expected?",
          "a": "Download the Form 26AS for the relevant financial year from the Income Tax portal and reconcile each entry against your invoice register and TDS receivable ledger. Common causes: client has not yet deposited the deducted amount (timing lag), client filed under the wrong section, or the client's TAN is incorrect. Contact the client with the specific invoice and quarter details, request their TDS return acknowledgement, and if the gap persists, escalate to a correction return before your ITR filing deadline.",
          "article": "TDS Reconciliation for IT Services Companies: 194J at Scale",
          "url": "https://www.terra-insight.com/insights/tds-reconciliation-it-services-india"
        },
        {
          "q": "How can IT companies efficiently reconcile TDS across 50 or more clients?",
          "a": "Automated reconciliation software that ingests Form 26AS data via the TRACES API and matches entries to the invoice register using TAN, amount, and period reduces 3-week manual cycles to under a day. The matching engine must handle net-of-TDS amounts — linking a ₹90,000 bank credit to a ₹1,00,000 invoice and a ₹10,000 TDS entry as a single transaction. Exceptions (section mismatches, missing credits) are surfaced as work items rather than buried in spreadsheet columns.",
          "article": "TDS Reconciliation for IT Services Companies: 194J at Scale",
          "url": "https://www.terra-insight.com/insights/tds-reconciliation-it-services-india"
        },
        {
          "q": "How long does a TDS refund typically take to credit after ITR filing?",
          "a": "After the ITR is processed under Section 143(1) and a refund is determined, CPC Bengaluru typically issues the refund within 20–45 days of the intimation date for electronically verified returns. Refunds are credited directly to the bank account registered and pre-validated on the income tax portal. Processing times can extend where the return is selected for scrutiny or where there is an outstanding demand in any prior year that the department applies the refund against under Section 245.",
          "article": "TDS Refund Reconciliation: Claiming and Tracking Excess TDS Deducted in India",
          "url": "https://www.terra-insight.com/insights/tds-refund-reconciliation-india"
        },
        {
          "q": "What is Section 245 and how does it affect a TDS refund?",
          "a": "Section 245 empowers the Income Tax Department to adjust a refund due for one year against an outstanding tax demand for any other year before issuing the refund. The taxpayer receives a notice under Section 245 before the adjustment is made and has 30 days to respond. If the outstanding demand is disputed, the taxpayer should respond within the notice period with evidence of the dispute or payment. Failure to respond results in automatic adjustment of the refund.",
          "article": "TDS Refund Reconciliation: Claiming and Tracking Excess TDS Deducted in India",
          "url": "https://www.terra-insight.com/insights/tds-refund-reconciliation-india"
        },
        {
          "q": "Can a company claim TDS credit in the ITR if the deductor has not yet filed the quarterly return and the credit does not appear in Form 26AS?",
          "a": "Yes. A taxpayer can claim TDS credit in the ITR even if the entry does not yet appear in Form 26AS, provided the income corresponding to that TDS has been declared in the return. However, the refund or tax credit will be granted only after verification — which requires the deductor's TDS return to be on record. If the deductor has not filed, the taxpayer's refund may be held or reduced until the deductor's filing is complete.",
          "article": "TDS Refund Reconciliation: Claiming and Tracking Excess TDS Deducted in India",
          "url": "https://www.terra-insight.com/insights/tds-refund-reconciliation-india"
        },
        {
          "q": "What happens to a TDS refund if the bank account registered on the income tax portal is incorrect?",
          "a": "CPC Bengaluru attempts to credit the refund to the bank account pre-validated on the income tax portal. If the account details are incorrect or the account is closed, the credit will fail. The taxpayer must update and pre-validate the correct bank account on the portal and request a refund reissue through the grievance or refund reissue module. This process can add 30–60 days to the refund timeline.",
          "article": "TDS Refund Reconciliation: Claiming and Tracking Excess TDS Deducted in India",
          "url": "https://www.terra-insight.com/insights/tds-refund-reconciliation-india"
        },
        {
          "q": "How does a Section 197 lower deduction certificate affect TDS refund reconciliation?",
          "a": "Section 197 allows a taxpayer to apply for a certificate from the Assessing Officer directing deductors to apply a lower or nil TDS rate. If the certificate is obtained but not submitted to the deductor in time — and TDS is deducted at the full rate — the excess TDS becomes part of the refund claimed in the ITR. The Section 197 certificate number, validity period, and applicable rate must be tracked separately and reconciled against the actual TDS deducted by each deductor.",
          "article": "TDS Refund Reconciliation: Claiming and Tracking Excess TDS Deducted in India",
          "url": "https://www.terra-insight.com/insights/tds-refund-reconciliation-india"
        },
        {
          "q": "What is the TDS rate under Section 192 for salary?",
          "a": "Section 192 does not prescribe a fixed rate. The employer calculates the employee's estimated annual tax liability based on their income slab under the applicable tax regime (old or new), then divides this equally across the remaining months of the financial year. Rates effectively range from nil for income below ₹3 lakh (new regime) to 30% for income above ₹15 lakh, plus applicable surcharge and health and education cess at 4%.",
          "article": "Section 192: Reconciling Salary TDS Deductions with Form 16 and Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-section-192-salary-reconciliation-india"
        },
        {
          "q": "When must the employer deposit salary TDS under Section 192?",
          "a": "For government employers, TDS must be deposited on the same day of deduction. For non-government employers, TDS deducted during any month of April through February must be deposited by the 7th of the following month. TDS deducted in March must be deposited by 30 April.",
          "article": "Section 192: Reconciling Salary TDS Deductions with Form 16 and Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-section-192-salary-reconciliation-india"
        },
        {
          "q": "What is Form 24Q and how often must it be filed?",
          "a": "Form 24Q is the quarterly TDS return filed by employers for salary payments under Section 192. It is due on 31 July (Q1), 31 October (Q2), 31 January (Q3), and 31 May (Q4). Annex II of the Q4 Form 24Q is particularly critical—it contains the full year salary details used to generate Form 16 Part A from TRACES.",
          "article": "Section 192: Reconciling Salary TDS Deductions with Form 16 and Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-section-192-salary-reconciliation-india"
        },
        {
          "q": "Why does Q4 salary TDS deduction spike compared to earlier quarters?",
          "a": "The employer re-estimates the employee's annual tax liability in January–March after accounting for actual bonus, arrears, perquisites (ESOP, car), and any LTA or HRA claims declared via Form 12BB. If the re-estimate exceeds the cumulative deductions made in Q1–Q3, the shortfall is recovered in Q4 months, causing a visible spike in March payslip TDS.",
          "article": "Section 192: Reconciling Salary TDS Deductions with Form 16 and Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-section-192-salary-reconciliation-india"
        },
        {
          "q": "What is the penalty for late deposit of salary TDS under Section 192?",
          "a": "Interest under Section 201(1A) accrues at 1.5% per month or part thereof from the date of deduction to the date of actual deposit. Additionally, late filing of Form 24Q attracts a penalty of ₹200 per day under Section 234E, subject to a maximum of the TDS amount involved.",
          "article": "Section 192: Reconciling Salary TDS Deductions with Form 16 and Form 26AS",
          "url": "https://www.terra-insight.com/insights/tds-section-192-salary-reconciliation-india"
        },
        {
          "q": "What is the TDS rate under Section 194 for dividends paid to resident shareholders?",
          "a": "Section 194 requires TDS at 10% on dividends paid to resident individuals and Hindu Undivided Families where the aggregate dividend in a financial year exceeds ₹5,000 per shareholder. If the shareholder does not furnish a PAN, Section 206AA requires TDS at 20%.",
          "article": "Section 194: Reconciling TDS on Dividends for Indian Shareholders and Companies",
          "url": "https://www.terra-insight.com/insights/tds-section-194-dividend-reconciliation-india"
        },
        {
          "q": "Does Section 194 apply to dividends declared before 1 April 2020?",
          "a": "No. Before 1 April 2020, dividends were covered by the Dividend Distribution Tax (DDT) regime and were exempt in the hands of shareholders. Section 194 TDS applies only to dividends declared or paid on or after 1 April 2020, following the abolition of DDT under the Finance Act 2020.",
          "article": "Section 194: Reconciling TDS on Dividends for Indian Shareholders and Companies",
          "url": "https://www.terra-insight.com/insights/tds-section-194-dividend-reconciliation-india"
        },
        {
          "q": "Which form does a company use to file TDS returns for Section 194 dividend payments?",
          "a": "A company paying dividends to resident shareholders files TDS returns in Form 26Q on a quarterly basis. For dividends paid to non-resident shareholders under Section 195, the relevant form is Form 27Q. Form 16A is issued to shareholders as the TDS certificate.",
          "article": "Section 194: Reconciling TDS on Dividends for Indian Shareholders and Companies",
          "url": "https://www.terra-insight.com/insights/tds-section-194-dividend-reconciliation-india"
        },
        {
          "q": "What TDS rate applies to dividends paid to non-resident shareholders?",
          "a": "Under Section 195, TDS on dividends to non-residents is 20% plus applicable surcharge and cess, resulting in an effective rate of up to 23.296% for non-corporate non-residents. If the shareholder's country has a DTAA with India and provides a lower rate, that treaty rate applies, provided the shareholder submits Form 10F and a Tax Residency Certificate.",
          "article": "Section 194: Reconciling TDS on Dividends for Indian Shareholders and Companies",
          "url": "https://www.terra-insight.com/insights/tds-section-194-dividend-reconciliation-india"
        },
        {
          "q": "How does a receiving company reconcile dividend TDS in its accounts?",
          "a": "The receiving company should match dividend income recorded in the profit and loss account against dividend warrants or bank credits, then verify the TDS amount against Form 26AS or the Annual Information Statement (AIS). The TDS credit must appear in 26AS before it can be claimed in the advance tax computation or ITR filing.",
          "article": "Section 194: Reconciling TDS on Dividends for Indian Shareholders and Companies",
          "url": "https://www.terra-insight.com/insights/tds-section-194-dividend-reconciliation-india"
        },
        {
          "q": "Does TDS apply under 194A on interest paid on an FD with an NBFC?",
          "a": "Yes. Interest paid on a fixed deposit with a Non-Banking Financial Company (NBFC) is subject to TDS at 10% under Section 194A when the annual interest exceeds ₹5,000. This is materially different from interest on bank FDs, where the TDS threshold is ₹40,000 per year (₹50,000 for senior citizens). A company earning ₹20,000 interest on an NBFC FD will have TDS deducted at ₹2,000, whereas the same amount from a scheduled bank would not attract TDS.",
          "article": "TDS Under Section 194A: Interest Income Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194a-interest-tds"
        },
        {
          "q": "How do I reconcile 194A TDS when interest is accrued but not yet paid?",
          "a": "TDS under 194A is triggered on credit (accrual) or payment, whichever is earlier. Many banks and NBFCs credit interest quarterly to the account and deduct TDS at that point, even if the depositor does not withdraw. In Form 26AS, the TDS entry appears in the quarter when the interest was credited. In the depositor's books, the interest income may be recognised on an accrual basis that does not align with the quarterly credit schedule. Reconciliation requires mapping Form 26AS quarter-by-quarter entries to the accrual schedule in the books.",
          "article": "TDS Under Section 194A: Interest Income Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194a-interest-tds"
        },
        {
          "q": "Is TDS required under 194A on interest on a security deposit held by a landlord?",
          "a": "Yes, if the landlord pays interest on the security deposit. Some commercial lease agreements provide for the landlord to pay interest on the security deposit at a specified rate (for example, 6% per annum). If this interest exceeds ₹5,000 in a financial year, the tenant-turned-interest-recipient does not deduct TDS — rather, the landlord as payer must deduct TDS at 10% under Section 194A before paying the interest. This scenario is common in large commercial property leases with multi-crore security deposits.",
          "article": "TDS Under Section 194A: Interest Income Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194a-interest-tds"
        },
        {
          "q": "What is the TDS threshold for interest income under 194A for a company?",
          "a": "For a company receiving interest from a non-bank source (NBFC, cooperative society, inter-company loan, builder's deposit), the TDS threshold is ₹5,000 per year per payer. For interest from a scheduled bank or cooperative bank on a fixed deposit or recurring deposit, the threshold is ₹40,000 per year (₹50,000 for senior citizens aged 60 and above). Savings account interest is excluded from 194A entirely and is instead reported under Section 194A(3)(i) exemptions.",
          "article": "TDS Under Section 194A: Interest Income Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194a-interest-tds"
        },
        {
          "q": "How does 194A TDS reconciliation differ from 194J reconciliation?",
          "a": "Section 194A TDS appears in the income source's books (lender deducts from interest paid to borrower), whereas 194J appears in the service provider's books (client deducts from fees paid). The volume and matching pattern also differ: 194A entries are typically low-volume (one or two entries per quarter per lender) with exact amounts, while 194J may involve 30–100 entries per quarter from multiple clients with partial payments and rate disputes. For inter-company loans in a conglomerate, 194A entries may appear in both the subsidiary (paying interest, which is the deductor) and the parent (receiving interest, which sees the credit in Form 26AS).",
          "article": "TDS Under Section 194A: Interest Income Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194a-interest-tds"
        },
        {
          "q": "Does TDS apply on insurance agent commission under 194H?",
          "a": "Yes. Insurance companies deduct TDS at 5% on commission paid to agents under Section 194H when the aggregate commission in a financial year exceeds ₹15,000. For a life insurance agent earning ₹80,000 commission annually, the TDS deducted is ₹4,000. Insurance companies typically consolidate monthly commission payments and deposit a single monthly TDS challan, which appears in Form 26AS with the insurer's TAN.",
          "article": "TDS Under Section 194H: Commission and Brokerage Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194h-commission-brokerage"
        },
        {
          "q": "What is the difference between 194H and 194J for agency payments?",
          "a": "Section 194H applies when the payment is commission or brokerage — that is, a fee for arranging or facilitating a transaction, typically calculated as a percentage of deal value. Section 194J applies when the payment is for professional services rendered — fees for expertise, not transaction facilitation. A travel agent earning commission from an airline is covered by 194H at 5%. A travel consultant charging a fixed professional fee for itinerary design may fall under 194J at 10%.",
          "article": "TDS Under Section 194H: Commission and Brokerage Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194h-commission-brokerage"
        },
        {
          "q": "How do I reconcile 194H TDS when commission is paid as a percentage of each transaction?",
          "a": "Variable commission creates a different amount each month, making amount-based one-to-one matching unreliable. The correct approach is to reconcile at the quarter level: sum all commission invoices for the quarter, calculate expected TDS at 5%, and match the total against the single quarterly entry in Form 26AS. Certificate numbers in Form 16A (downloadable from TRACES) confirm the deductor TAN and quarter, serving as the authoritative match key.",
          "article": "TDS Under Section 194H: Commission and Brokerage Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194h-commission-brokerage"
        },
        {
          "q": "Is platform commission charged by e-commerce operators subject to 194H?",
          "a": "No. Platform commissions charged by e-commerce operators (Flipkart, Amazon, Meesho, and similar marketplaces) to sellers are covered by a distinct set of provisions — Section 194O for TDS on e-commerce payouts and GST TCS under Section 52 of the CGST Act. Section 194H does not apply to marketplace platform fees. Misclassifying marketplace deductions as 194H is a common error in seller reconciliation that leads to incorrect ledger entries.",
          "article": "TDS Under Section 194H: Commission and Brokerage Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194h-commission-brokerage"
        },
        {
          "q": "What is the TDS rate on real estate brokerage payments?",
          "a": "Real estate brokerage payments to channel partners (property dealers, DSAs) attract TDS at 5% under Section 194H when aggregate payments exceed ₹15,000 in a financial year. A developer paying ₹3,00,000 brokerage on a ₹60,00,000 property deal must deduct ₹15,000 TDS. The TDS must be deposited by the 7th of the following month and reported in the quarterly TDS return (Form 26Q).",
          "article": "TDS Under Section 194H: Commission and Brokerage Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194h-commission-brokerage"
        },
        {
          "q": "What is the TDS rate under Section 194C for a private limited company?",
          "a": "Payments to a company or firm attract TDS at 2% under Section 194C. The threshold is ₹30,000 per single payment or ₹1,00,000 in aggregate during the financial year. TDS must be deposited by the 7th of the following month (30 April for March deductions).",
          "article": "TDS Under Section 194C: Contractor Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194c-contractor-payments"
        },
        {
          "q": "Why does Form 26AS show a different TDS amount than expected under 194C?",
          "a": "The most frequent cause is rate misinterpretation: a deductor applies 1% (the individual/HUF rate) to a company contractor, or vice versa. Other causes include a wrong TAN being quoted, the deductor mapping the transaction to Section 194J instead of 194C, or a challan deposit being delayed beyond the 7th of the month so it does not appear in the same quarter's Form 26AS.",
          "article": "TDS Under Section 194C: Contractor Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194c-contractor-payments"
        },
        {
          "q": "How long does it take to resolve a Section 194C correction return?",
          "a": "A correction statement filed on TRACES (https://www.tdscpc.gov.in) is typically processed within 5–7 working days for structural corrections (wrong TAN, wrong section) and up to 15 working days if the underlying challan itself needs to be corrected. The corrected credit appears in Form 26AS within 3–7 days of processing.",
          "article": "TDS Under Section 194C: Contractor Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194c-contractor-payments"
        },
        {
          "q": "What is the difference between TDS under 194C and 194J?",
          "a": "Section 194C applies to work contracts — manufacturing, construction, transport, catering, labour supply. Section 194J applies to professional or technical services. The rates differ: 194C is 1% or 2% depending on payee type, while 194J is 10% for professional services and 2% for technical services. Misclassifying a software development contract from 194J to 194C results in an 8% shortfall in deduction, which the deductor is liable to make good.",
          "article": "TDS Under Section 194C: Contractor Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194c-contractor-payments"
        },
        {
          "q": "How do I reconcile 194C TDS when a client deducts from multiple branches?",
          "a": "Large enterprises often register separate TANs for each branch, state, or legal entity. Form 26AS aggregates credit by PAN but lists each deductor TAN separately. To reconcile, extract all TAN-level rows from Form 26AS for the financial year, then map each row to the corresponding invoice or purchase order. An organisation with 8 active client branches may see 8 separate 194C deductor entries for a single project.",
          "article": "TDS Under Section 194C: Contractor Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194c-contractor-payments"
        },
        {
          "q": "What is the TDS rate on office rent under Section 194I?",
          "a": "TDS on office rent (land, building, furniture, and fittings) is 10% under Section 194I. For plant, machinery, or equipment hire, the rate is 2%. The threshold in both cases is ₹2,40,000 per year per landlord, which means any monthly rent above ₹20,000 triggers the TDS obligation. TDS is deducted at the time of credit to the landlord's account or actual payment, whichever is earlier.",
          "article": "TDS Under Section 194I: Rent Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194i-rent-reconciliation"
        },
        {
          "q": "Does TDS apply to co-working space rent under 194I?",
          "a": "In most interpretations, co-working space charges are treated as service charges rather than rent, making Section 194J (technical services, 2%) more applicable than Section 194I. The distinction is whether the arrangement grants exclusive possession of a defined space (rent, 194I) or access to shared facilities with additional services such as internet, housekeeping, and reception (service, 194J). Most co-working providers structure their agreements as service contracts specifically to avoid the 194I classification.",
          "article": "TDS Under Section 194I: Rent Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194i-rent-reconciliation"
        },
        {
          "q": "How do I reconcile 194I TDS when the landlord has multiple TANs for different properties?",
          "a": "Large institutional landlords — real estate investment trusts, commercial property companies — often maintain separate TANs for each property or state registration. As the tenant, your books show one rent expense account but Form 26AS (if you are the deductor) shows one entry per TAN. Reconciliation requires mapping each monthly rent payment to the correct TAN before matching. If you are the landlord receiving rent, each corporate tenant has a unique TAN and Form 26AS shows a separate row per tenant.",
          "article": "TDS Under Section 194I: Rent Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194i-rent-reconciliation"
        },
        {
          "q": "Is TDS deducted on the security deposit paid with the first month's rent?",
          "a": "No. TDS under Section 194I applies only to rent — periodic payments for use of property. Security deposits are refundable amounts held as collateral and do not constitute rent. Deducting TDS on a security deposit is an error. If a deductor incorrectly deducts TDS on the deposit, the landlord must request a correction return from the deductor to remove the erroneous entry from Form 26AS, since the deposit amount will never appear as rental income in the landlord's ITR.",
          "article": "TDS Under Section 194I: Rent Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194i-rent-reconciliation"
        },
        {
          "q": "What happens when rent increases mid-year — does TDS need to be adjusted?",
          "a": "Yes. If rent increases from ₹30,000/month to ₹35,000/month from July onwards, the TDS calculation for each month changes. April–June TDS is ₹3,000/month (10% of ₹30,000) and July–March TDS is ₹3,500/month (10% of ₹35,000). The annual total against which the ₹2,40,000 threshold is checked is the revised aggregate: 3×₹30,000 + 9×₹35,000 = ₹4,05,000, which exceeds the threshold, so TDS applies from the first payment.",
          "article": "TDS Under Section 194I: Rent Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194i-rent-reconciliation"
        },
        {
          "q": "What is the TDS rate for IT consulting services under Section 194J?",
          "a": "IT consulting services are taxed at 2% under Section 194J if they qualify as technical services, following the Finance Act 2020 amendment effective from 1 April 2020. If the engagement involves professional advisory — strategy, legal opinion, or domain expertise — the rate is 10%. The ₹30,000/year threshold applies in both cases. Clients who were deducting at 10% on software services before FY 2020-21 must now confirm reclassification in their ERP.",
          "article": "TDS Under Section 194J: Professional Services Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194j-professional-services"
        },
        {
          "q": "Can a client deduct TDS at 2% on software development services under 194J?",
          "a": "Yes, software development services generally qualify as technical services and attract 2% TDS under Section 194J. However, if the engagement includes significant professional advisory, design authority, or intellectual property creation (for example, custom algorithm development billed as consultancy), a client may argue 10% applies. Disputes on this boundary are the most common 194J reconciliation issues for Indian IT exporters receiving domestic contracts.",
          "article": "TDS Under Section 194J: Professional Services Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194j-professional-services"
        },
        {
          "q": "How do I reconcile 194J TDS when deducted quarterly vs monthly invoicing?",
          "a": "Many large deductors consolidate 194J payments and deposit a single quarterly TDS challan rather than monthly. Form 26AS shows the deduction at the quarter level — for example, Q1 shows a single entry even if three monthly invoices were raised. To reconcile, sum the TDS amounts from all invoices in the quarter and match that total against the Form 26AS quarterly entry. Certificate numbers in Form 16A, downloadable from TRACES, link the challan back to individual deductee records.",
          "article": "TDS Under Section 194J: Professional Services Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194j-professional-services"
        },
        {
          "q": "What happens if a deductor misclassifies my service under 194C instead of 194J?",
          "a": "If a deductor applies 194C (2% for company) instead of 194J (10% professional or 2% technical), the TDS credit in Form 26AS will be tagged with the wrong section code. Even if the amount matches, the section mismatch may cause issues at ITR processing if the income is declared under the correct head. The correct remedy is to ask the deductor to file a correction return on TRACES changing the section from 194C to 194J. The corrected credit typically reflects in Form 26AS within 7–10 working days.",
          "article": "TDS Under Section 194J: Professional Services Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194j-professional-services"
        },
        {
          "q": "How many invoices does a typical IT services company need to reconcile for 194J per quarter?",
          "a": "A mid-size IT services company with 30–50 active domestic clients will typically process 90–150 invoices per quarter attracting 194J TDS. If each client deducts quarterly instead of monthly, Form 26AS shows 30–50 entries against 90–150 invoice rows in the accounts receivable ledger. The 3:1 ratio between ledger rows and Form 26AS rows is the primary reason quarterly 194J reconciliation takes 3–4 working days without automation.",
          "article": "TDS Under Section 194J: Professional Services Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194j-professional-services"
        },
        {
          "q": "What is the TDS rate under Section 194A for NBFCs?",
          "a": "NBFCs deduct TDS on interest payments to resident depositors at 10% if the depositor furnishes a valid PAN. If PAN is not furnished, the rate increases to 20% under Section 206AA. For interest payments to non-residents, Section 195 applies instead of 194A — the withholding rate depends on the applicable Double Taxation Avoidance Agreement (DTAA) or the Income Tax Act rate, whichever is beneficial. The threshold for mandatory TDS deduction under 194A for NBFCs is above ₹5,000 per annum per depositor.",
          "article": "TDS Reconciliation for NBFCs: Managing Section 194A at Scale",
          "url": "https://www.terra-insight.com/insights/tds-reconciliation-nbfc-india"
        },
        {
          "q": "How do NBFCs handle Form 15G and 15H submissions to avoid excess TDS deduction?",
          "a": "Depositors below the basic exemption limit (Form 15G for those below 60 years) or senior citizens (Form 15H) submit declarations to the NBFC requesting nil TDS deduction. The NBFC must log the submission date, validate that the depositor's declared income is within the eligible limit, and ensure the TDS system excludes those accounts from deduction for the applicable financial year. NBFCs are required to submit these declarations electronically on the TRACES portal each quarter. A reconciliation gap occurs when a depositor submits the form mid-year after TDS has already been deducted — the NBFC cannot reverse the deduction but must issue a revised Form 16A reflecting the corrected position.",
          "article": "TDS Reconciliation for NBFCs: Managing Section 194A at Scale",
          "url": "https://www.terra-insight.com/insights/tds-reconciliation-nbfc-india"
        },
        {
          "q": "What happens when TDS is deducted at 20% due to a missing PAN?",
          "a": "When a depositor fails to furnish a valid PAN, Section 206AA requires TDS at 20%, double the standard rate. If the depositor later furnishes PAN in the same financial year, the NBFC must file a correction return for the relevant quarter on TRACES to revise the deduction from 20% to 10%. A revised Form 16A is then issued to the depositor. If the correction return is not filed, the depositor cannot claim the excess TDS credit in their ITR — creating a compliance liability for both parties. Automating PAN validation at account opening and at each interest payout cycle reduces the frequency of 20% deductions at source.",
          "article": "TDS Reconciliation for NBFCs: Managing Section 194A at Scale",
          "url": "https://www.terra-insight.com/insights/tds-reconciliation-nbfc-india"
        },
        {
          "q": "How should NBFCs reconcile TDS for co-lending partnerships?",
          "a": "In a co-lending arrangement, an NBFC and a bank jointly disburse a loan. When the borrower repays interest, the allocation between the bank and NBFC must be tracked separately. If the bank is the primary lender on record, the bank may deduct TDS under 194A on the NBFC's share of interest income received. The NBFC must reconcile this TDS deduction (appearing in Form 26AS under the bank's TAN) against its interest income ledger for each co-lending partner. NBFCs with five or more co-lending partners face a multi-TAN reconciliation exercise each quarter that requires systematic TAN-to-partner mapping to avoid misattribution.",
          "article": "TDS Reconciliation for NBFCs: Managing Section 194A at Scale",
          "url": "https://www.terra-insight.com/insights/tds-reconciliation-nbfc-india"
        },
        {
          "q": "Is the ₹1 crore threshold for 194N calculated per bank account or per bank?",
          "a": "Per bank. All accounts held at the same bank—current, savings, cash credit, overdraft—are aggregated when computing the ₹1 crore annual threshold. A business with three current accounts at the same bank has all three accounts' withdrawals pooled. If the same business has accounts at two separate banks, each bank tracks its own ₹1 crore limit independently.",
          "article": "TDS Under Section 194N: Cash Withdrawal Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194n-cash-withdrawal"
        },
        {
          "q": "Does TDS under 194N apply to withdrawals from current accounts of businesses?",
          "a": "Yes. Section 194N applies to all account types including business current accounts, savings accounts, cash credit accounts, and overdraft accounts. The section does not distinguish between individual and business account holders; it applies based on withdrawal volume alone.",
          "article": "TDS Under Section 194N: Cash Withdrawal Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194n-cash-withdrawal"
        },
        {
          "q": "How do I see 194N TDS deducted by my bank in Form 26AS?",
          "a": "194N TDS appears in Form 26AS Part A1. The deductor is the bank branch, identified by the bank's TAN (not your company's TAN). The section code is 194N. You can download Form 26AS from TRACES at https://www.tdscpc.gov.in after the bank files its quarterly TDS return. The update typically appears 3–7 days after the return is processed.",
          "article": "TDS Under Section 194N: Cash Withdrawal Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194n-cash-withdrawal"
        },
        {
          "q": "Can I claim a refund of 194N TDS when filing income tax return?",
          "a": "Yes. TDS deducted under 194N is treated as advance tax. When you file your income tax return for the year, the 194N TDS credit from Form 26AS is set off against your total tax liability. If TDS deducted exceeds your tax due, the surplus is refunded by the Income Tax Department, typically within 30–60 days of return processing.",
          "article": "TDS Under Section 194N: Cash Withdrawal Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194n-cash-withdrawal"
        },
        {
          "q": "Does the 5% enhanced rate for 194N apply to all previous 3 years or only the current year?",
          "a": "The 5% rate applies when the account holder has not filed income tax returns for all three preceding financial years for which the ITR filing deadline has passed. It is not applied retroactively; it takes effect from the date the bank determines that the ITR non-filing condition is met, and continues for the remainder of that financial year.",
          "article": "TDS Under Section 194N: Cash Withdrawal Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194n-cash-withdrawal"
        },
        {
          "q": "What is the TDS rate under Section 194O for e-commerce sellers?",
          "a": "The rate is 1% on the gross amount paid or credited to the seller by the e-commerce operator. For individual and HUF sellers with PAN on record, the rate is 1%. Without PAN, TDS is deducted at 5% under Section 206AA.",
          "article": "Section 194O TDS: Reconciling E-Commerce Operator Deductions for Indian Sellers",
          "url": "https://www.terra-insight.com/insights/tds-section-194o-ecommerce-reconciliation"
        },
        {
          "q": "Does Section 194O apply to all sellers on Amazon and Flipkart?",
          "a": "For individual and HUF sellers, the section applies only when aggregate payments in the financial year exceed ₹5 lakh. There is no threshold for companies and firms—TDS applies from the first rupee of credit or payment by the e-commerce operator.",
          "article": "Section 194O TDS: Reconciling E-Commerce Operator Deductions for Indian Sellers",
          "url": "https://www.terra-insight.com/insights/tds-section-194o-ecommerce-reconciliation"
        },
        {
          "q": "Which form does the e-commerce operator use to file Section 194O TDS?",
          "a": "The e-commerce operator reports TDS under Section 194O in Form 26QE, filed quarterly with the Income Tax Department. The seller sees the deduction in Form 26AS under the relevant part and can verify it through the AIS on the income tax portal.",
          "article": "Section 194O TDS: Reconciling E-Commerce Operator Deductions for Indian Sellers",
          "url": "https://www.terra-insight.com/insights/tds-section-194o-ecommerce-reconciliation"
        },
        {
          "q": "Why does the TDS figure on a marketplace seller dashboard differ from Form 26AS?",
          "a": "The operator deducts TDS on the gross payment including GST components of fees or commissions, while the seller books revenue and fees net of GST. This creates a structural difference. Additionally, 26AS reflects deductions only after the operator files Form 26QE, which can lag the actual deduction by 30–60 days.",
          "article": "Section 194O TDS: Reconciling E-Commerce Operator Deductions for Indian Sellers",
          "url": "https://www.terra-insight.com/insights/tds-section-194o-ecommerce-reconciliation"
        },
        {
          "q": "How should a multi-platform seller reconcile 194O TDS from Amazon, Flipkart, and Meesho?",
          "a": "Each operator files and deducts separately. The seller must download Form 26AS or AIS and split entries by deductor TAN—Amazon's TAN, Flipkart's TAN, and Meesho's TAN are each distinct. Each platform's cumulative deduction must be matched independently against that platform's settlement statements for the quarter.",
          "article": "Section 194O TDS: Reconciling E-Commerce Operator Deductions for Indian Sellers",
          "url": "https://www.terra-insight.com/insights/tds-section-194o-ecommerce-reconciliation"
        },
        {
          "q": "Does TDS apply under 194Q if my company's turnover is ₹8 crore?",
          "a": "No. Section 194Q applies only when the buyer's gross turnover in the preceding financial year exceeds ₹10 crore. A buyer with ₹8 crore turnover does not deduct TDS under 194Q, regardless of purchase volume from any single seller.",
          "article": "TDS Under Section 194Q: Purchase Reconciliation for Large Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-194q-purchase-reconciliation"
        },
        {
          "q": "What happens when both 194Q TDS and 206C TCS apply to the same purchase?",
          "a": "When both could apply, Section 194Q takes precedence. The buyer deducts TDS at 0.1% and the seller does not collect TCS. If the buyer is not liable under 194Q (for example, turnover below ₹10 crore), the seller may then collect TCS under Section 206C(1H). Both cannot apply simultaneously to the same transaction.",
          "article": "TDS Under Section 194Q: Purchase Reconciliation for Large Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-194q-purchase-reconciliation"
        },
        {
          "q": "How do I track the ₹50 lakh per-seller threshold for 194Q compliance?",
          "a": "Cumulative purchase value must be tracked per seller PAN across the financial year. Most buyers configure an alert in their ERP or accounts payable system to flag when purchases from a single vendor approach ₹48–49 lakh. Once cumulative purchases cross ₹50 lakh, TDS at 0.1% applies on every subsequent payment to that seller for the remainder of the financial year.",
          "article": "TDS Under Section 194Q: Purchase Reconciliation for Large Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-194q-purchase-reconciliation"
        },
        {
          "q": "Is TDS under 194Q deducted on GST-inclusive or GST-exclusive amounts?",
          "a": "TDS under 194Q is deducted on the invoice value exclusive of GST. CBDT's FAQ circular clarified that where GST is shown separately on the invoice, TDS should be calculated only on the taxable value, not on the GST component.",
          "article": "TDS Under Section 194Q: Purchase Reconciliation for Large Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-194q-purchase-reconciliation"
        },
        {
          "q": "How does 194Q TDS appear in Form 26AS for the seller?",
          "a": "The seller sees the TDS in Form 26AS Part A1, with the buyer's TAN appearing as the deductor. The section code is 194Q. Sellers—particularly smaller manufacturers—should verify Part A1 each quarter, since many receive payments net of 0.1% TDS without prior notice from buyers who crossed the threshold mid-year.",
          "article": "TDS Under Section 194Q: Purchase Reconciliation for Large Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-194q-purchase-reconciliation"
        },
        {
          "q": "Does 194R TDS apply on product samples given to distributors?",
          "a": "Yes, if the fair market value of product samples given to a single distributor exceeds ₹20,000 in a financial year. CBDT clarified that samples whose aggregate value stays within ₹20,000 per recipient per year are below the threshold and attract no TDS. Above ₹20,000, TDS at 10% applies on the full value, not just the excess.",
          "article": "TDS Under Section 194R: Benefit and Perquisite Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194r-benefit-perquisite"
        },
        {
          "q": "How is TDS deducted under 194R when the benefit is a non-cash gift?",
          "a": "The deductor must use the grossing-up mechanism. Since TDS cannot be recovered from a physical gift, the company providing the benefit must deposit the TDS from its own funds. For a ₹50,000 gift, the tax at 10% is ₹5,000—the company deposits ₹5,000 as TDS and the full gift of ₹50,000 is given to the recipient. The TDS cost becomes an additional business expenditure for the deductor.",
          "article": "TDS Under Section 194R: Benefit and Perquisite Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194r-benefit-perquisite"
        },
        {
          "q": "How does 194R TDS appear in Form 26AS for the recipient?",
          "a": "The TDS appears in the recipient's Form 26AS Part A1, with the benefit-provider as deductor and the section code 194R. Since the recipient received a non-cash benefit, they must recognise the benefit value as business income and claim the Form 26AS TDS credit against their tax liability. The reconciliation task is to match the Form 26AS entry to the specific benefit received in the books.",
          "article": "TDS Under Section 194R: Benefit and Perquisite Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194r-benefit-perquisite"
        },
        {
          "q": "Is conference sponsorship for a channel partner subject to 194R?",
          "a": "Yes. If a company sponsors a dealer or distributor to attend a conference—paying for flights, accommodation, and registration—and the cost exceeds ₹20,000 for that dealer in the year, TDS at 10% applies under 194R. The deductor is the sponsoring company. CBDT has specifically cited sponsored travel as within the scope of Section 194R.",
          "article": "TDS Under Section 194R: Benefit and Perquisite Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194r-benefit-perquisite"
        },
        {
          "q": "Can a company claim input credit for the 194R TDS it deducts and deposits?",
          "a": "No. The company depositing 194R TDS on a non-cash benefit receives no input credit. The TDS paid is a cost to the deductor. The benefit of the credit goes entirely to the recipient, who claims it in Form 26AS as advance tax paid on the benefit income they must declare in their income tax return.",
          "article": "TDS Under Section 194R: Benefit and Perquisite Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-194r-benefit-perquisite"
        },
        {
          "q": "What is the TDS rate under Section 194S on VDA transfers?",
          "a": "The rate is 1% on the consideration paid for the transfer of any virtual digital asset. For specified persons—individuals or HUFs with business turnover below ₹1 crore or professional receipts below ₹50 lakh in the preceding year—TDS applies only when aggregate VDA consideration in the financial year exceeds ₹50,000. For all other taxpayers, the threshold is ₹10,000.",
          "article": "Section 194S: Reconciling TDS on Virtual Digital Asset Transfers in India",
          "url": "https://www.terra-insight.com/insights/tds-section-194s-vda-reconciliation-india"
        },
        {
          "q": "Which form is used to file TDS returns under Section 194S?",
          "a": "Crypto exchanges file TDS returns in Form 26QF on a quarterly basis. Other deductors—such as corporate buyers or P2P platform operators—file in Form 26Q under Section 194S. The deductee sees the TDS credit in Form 26AS and the Annual Information Statement (AIS) on the income tax portal.",
          "article": "Section 194S: Reconciling TDS on Virtual Digital Asset Transfers in India",
          "url": "https://www.terra-insight.com/insights/tds-section-194s-vda-reconciliation-india"
        },
        {
          "q": "Can a VDA trader claim TDS credit even if they made a loss on the trade?",
          "a": "Yes. TDS credit under Section 194S can be claimed in the ITR regardless of whether the VDA transaction resulted in a profit or loss. Section 115BBH prohibits offsetting VDA losses against other income, but it does not restrict the TDS credit claim. The credit reduces overall tax liability, even if the underlying VDA income is taxed separately at 30%.",
          "article": "Section 194S: Reconciling TDS on Virtual Digital Asset Transfers in India",
          "url": "https://www.terra-insight.com/insights/tds-section-194s-vda-reconciliation-india"
        },
        {
          "q": "Who deducts TDS in a peer-to-peer VDA transaction under Section 194S?",
          "a": "In a peer-to-peer transfer facilitated by a P2P exchange platform, the platform itself is responsible for deducting TDS if it acts as the facilitator. In a direct off-platform P2P trade, the buyer is the deductor. The buyer must have a TAN, deposit the TDS, and file a return in Form 26Q. Failure to deduct makes the buyer a defaulter under Section 201.",
          "article": "Section 194S: Reconciling TDS on Virtual Digital Asset Transfers in India",
          "url": "https://www.terra-insight.com/insights/tds-section-194s-vda-reconciliation-india"
        },
        {
          "q": "How is TDS calculated when VDA consideration includes both crypto and fiat components?",
          "a": "TDS under Section 194S is calculated on the full consideration paid for the VDA transfer, regardless of whether it is in cash, crypto, or a combination. If the consideration is in kind (e.g., one cryptocurrency exchanged for another), the fair market value of the VDA received is used as the base. The deductor must convert this to INR at the applicable rate on the date of transfer.",
          "article": "Section 194S: Reconciling TDS on Virtual Digital Asset Transfers in India",
          "url": "https://www.terra-insight.com/insights/tds-section-194s-vda-reconciliation-india"
        },
        {
          "q": "Is Form 15CA mandatory for all payments to non-residents under Section 195?",
          "a": "Not for every payment. Payments below ₹5 lakh per financial year, and certain specified categories listed in Rule 37BB (such as imports, airline tickets, and shipping freight), are exempt from Form 15CA/15CB. For all other remittances, Form 15CA must be filed online and Form 15CB (CA certificate) must be obtained before the bank processes the transfer.",
          "article": "TDS Under Section 195: Non-Resident Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-195-non-resident-payments"
        },
        {
          "q": "What TDS rate applies when India has a DTAA with the recipient's country?",
          "a": "The lower of the DTAA rate or the domestic Section 195 rate applies. For example, India's DTAA with Singapore specifies 15% on royalties, whereas the domestic rate is 20%—so 15% is applied. If the non-resident has a Permanent Establishment in India, the business income may instead be taxed as Indian-sourced income, potentially at a higher rate.",
          "article": "TDS Under Section 195: Non-Resident Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-195-non-resident-payments"
        },
        {
          "q": "How do I reconcile Section 195 TDS when the foreign company claims treaty exemption?",
          "a": "The non-resident must furnish a Tax Residency Certificate (TRC) from their home country's tax authority and a self-declaration in Form 10F. Once these are provided to the Indian payer, the DTAA rate or nil rate applies. For reconciliation, maintain a file linking each payment to the TRC/Form 10F on record, and verify that Form 26AS Part A reflects the reduced rate actually deducted.",
          "article": "TDS Under Section 195: Non-Resident Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-195-non-resident-payments"
        },
        {
          "q": "Does Section 195 apply to SaaS subscription payments made to US companies?",
          "a": "It depends on characterisation. If the subscription grants a right to use software (the user cannot access or reproduce the underlying code), Indian courts and CBDT circulars have held it is business income, not royalty—TDS may not apply if the US company has no Permanent Establishment in India. If the arrangement grants a licence to the underlying IP, it may be taxed as royalty at 15% under the India-US DTAA. Each contract must be reviewed individually.",
          "article": "TDS Under Section 195: Non-Resident Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-195-non-resident-payments"
        },
        {
          "q": "How is Form 26AS updated for Section 195 TDS payments?",
          "a": "The Indian payer (deductor) deposits the TDS using their own TAN and files a TDS return for Section 195. The entry appears in the non-resident's Form 26AS Part A, identified by the deductor's TAN, PAN of the non-resident (if they have one), section code 195, and quarter. The update lag is typically 3–7 days after the quarterly return is processed on TRACES.",
          "article": "TDS Under Section 195: Non-Resident Payment Reconciliation",
          "url": "https://www.terra-insight.com/insights/tds-section-195-non-resident-payments"
        },
        {
          "q": "What are the conditions that make a vendor a 'specified person' under Section 206AB?",
          "a": "A vendor is a specified person under Section 206AB if two conditions are both met: first, they have not filed income tax returns for both of the two financial years immediately preceding the current year (for which the return filing due date under Section 139(1) has passed); and second, the aggregate TDS and TCS in their account was ₹50,000 or more in each of those two years. Both conditions must be satisfied — a vendor who missed filing for only one of the two years, or whose TDS was below ₹50,000 in either year, is not a specified person.",
          "article": "Section 206AB and 206CCA: Identifying Non-Filers and Reconciling Higher TDS Rates",
          "url": "https://www.terra-insight.com/insights/tds-section-206ab-206cca-india"
        },
        {
          "q": "What TDS rate applies to a specified person under Section 206AB?",
          "a": "The rate for a specified person is the highest of three: twice the rate specified in the relevant TDS section, twice the rate in force under the Finance Act, or 5%. For Section 194J (professional fees at 10%), twice the rate is 20%, which is higher than 5%, so 20% applies. For Section 194C (contractor payments at 1–2%), twice the rate is 2–4%, which is below 5%, so 5% applies. Always compare the doubled rate against 5% and apply the higher figure.",
          "article": "Section 206AB and 206CCA: Identifying Non-Filers and Reconciling Higher TDS Rates",
          "url": "https://www.terra-insight.com/insights/tds-section-206ab-206cca-india"
        },
        {
          "q": "How often should the TRACES Compliance Check for Section 206AB be run?",
          "a": "TRACES recommends running the Compliance Check before each payment cycle for vendors above the relevant threshold. In practice, a vendor's specified person status can change between financial years — a vendor who was non-compliant in FY 2022-23 and FY 2023-24 may have filed returns by the time FY 2025-26 payments are processed, which would remove their specified person status. Running the check annually is insufficient; it should be part of the payment authorisation workflow for each vendor where TDS applies.",
          "article": "Section 206AB and 206CCA: Identifying Non-Filers and Reconciling Higher TDS Rates",
          "url": "https://www.terra-insight.com/insights/tds-section-206ab-206cca-india"
        },
        {
          "q": "What is Section 206CCA and how does it differ from 206AB?",
          "a": "Section 206CCA applies the same higher-rate principle to Tax Collected at Source (TCS) rather than TDS. It applies to sellers who are required to collect TCS but are dealing with buyers who are specified persons. The threshold conditions are identical to 206AB: two preceding years of non-filing and TDS/TCS of ₹50,000 or more in each year. The higher rate for 206CCA is twice the applicable TCS rate or 5%, whichever is higher.",
          "article": "Section 206AB and 206CCA: Identifying Non-Filers and Reconciling Higher TDS Rates",
          "url": "https://www.terra-insight.com/insights/tds-section-206ab-206cca-india"
        },
        {
          "q": "What happens if a deductor fails to apply the Section 206AB higher rate?",
          "a": "If the deductor applies the standard section rate to a vendor who is a specified person, the shortfall is treated as short deduction under Section 201. The deductor is treated as an assessee in default and is liable for interest under Section 201(1A) at 1% per month on the shortfall from the date it should have been deducted, plus penalty under Section 271C equivalent to the amount of the short deduction. The TRACES Compliance Check output serves as the primary defence — it documents that the deductor took reasonable steps to verify status before payment.",
          "article": "Section 206AB and 206CCA: Identifying Non-Filers and Reconciling Higher TDS Rates",
          "url": "https://www.terra-insight.com/insights/tds-section-206ab-206cca-india"
        },
        {
          "q": "What is the TCS rate on scrap under Section 206C?",
          "a": "The TCS rate on scrap under Section 206C(1) is 1% of the sale consideration. This applies when any person sells scrap to a buyer. There is no minimum threshold for scrap—TCS applies from the first rupee of the transaction value.",
          "article": "Section 206C: Reconciling TCS Collected at Source for Indian Sellers and Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-206c-tcs-reconciliation-india"
        },
        {
          "q": "When did the TCS rate on LRS overseas remittances increase to 20%?",
          "a": "The Finance Act 2023 increased the TCS rate on remittances under the Liberalised Remittance Scheme (LRS) to 20% effective 1 October 2023, for purposes other than medical treatment and education. Remittances for medical treatment and education remain at 5%. Overseas tour packages are taxed at 20% regardless of purpose.",
          "article": "Section 206C: Reconciling TCS Collected at Source for Indian Sellers and Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-206c-tcs-reconciliation-india"
        },
        {
          "q": "Which form is used to file quarterly TCS returns under Section 206C?",
          "a": "TCS collectors file quarterly returns in Form 27EQ. The filing deadlines are 15 July (Q1), 15 October (Q2), 15 January (Q3), and 15 May (Q4). The TCS certificate issued to the buyer is Form 27D, which must be generated from TRACES.",
          "article": "Section 206C: Reconciling TCS Collected at Source for Indian Sellers and Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-206c-tcs-reconciliation-india"
        },
        {
          "q": "How does a buyer claim TCS credit from Section 206C in their ITR?",
          "a": "The buyer can claim the TCS deducted by the seller as a credit against their income tax liability, similar to TDS. The credit appears in Form 26AS Part C. The buyer must match the TCS amount, the collector's PAN/TAN, and the section code in Form 26AS against the purchase invoice and Form 27D certificate before filing.",
          "article": "Section 206C: Reconciling TCS Collected at Source for Indian Sellers and Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-206c-tcs-reconciliation-india"
        },
        {
          "q": "What happens if a seller collects TCS but the buyer is also liable to deduct TDS under Section 194Q?",
          "a": "When both Section 194Q (TDS by buyer) and Section 206C(1H) (TCS by seller) could apply to the same goods transaction, Section 194Q takes precedence. The buyer deducts 0.1% TDS and the seller does not collect TCS on that transaction. Sellers must verify whether the buyer's turnover exceeds ₹10 crore to determine which section governs.",
          "article": "Section 206C: Reconciling TCS Collected at Source for Indian Sellers and Buyers",
          "url": "https://www.terra-insight.com/insights/tds-section-206c-tcs-reconciliation-india"
        },
        {
          "q": "What is the difference between Form 26AS and AIS on TRACES?",
          "a": "Form 26AS is the Tax Credit Statement — it shows TDS deducted by each deductor (identified by TAN), the amount deposited to the government, and the credit available against the deductee's tax liability. AIS (Annual Information Statement) is a broader document that includes Form 26AS data plus information from Statement of Financial Transactions (SFT) sources, such as bank interest, mutual fund redemptions, and high-value transactions. For TDS reconciliation, Form 26AS is the primary document; AIS is used to cross-check completeness and to catch cases where TDS appears in AIS before the deductor's return has updated Form 26AS.",
          "article": "TRACES Portal: How to Download and Reconcile TDS Data for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-traces-portal-reconciliation-india"
        },
        {
          "q": "How do I download Form 26AS from TRACES for reconciliation?",
          "a": "Log into TRACES as a deductee (using PAN credentials). Navigate to 'My Account' and select 'View Form 26AS'. Choose the relevant financial year and the file format (PDF for review, XML for structured data extraction). For bulk reconciliation, the XML format is preferable — it can be parsed into columns by section, TAN, quarter, and amount, matching directly against the TDS receivable ledger in your ERP. The PDF version is password-protected with the date of birth of the PAN holder.",
          "article": "TRACES Portal: How to Download and Reconcile TDS Data for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-traces-portal-reconciliation-india"
        },
        {
          "q": "Can a deductor verify challan status on TRACES before filing the quarterly return?",
          "a": "Yes. Deductors should verify challan status on TRACES before filing each quarterly TDS return. Log into TRACES as a deductor (TAN credentials), go to 'Statements/Payments', and select 'Challan Status'. Enter the BSR code and challan serial number, or the challan date range, to confirm whether each deposit is reflecting in OLTAS. If a challan shows 'unmatched', the BSR code or serial number in the return entry must be corrected before filing — otherwise the return will contain mismatches that require a C2 correction later.",
          "article": "TRACES Portal: How to Download and Reconcile TDS Data for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-traces-portal-reconciliation-india"
        },
        {
          "q": "How long does it take for a TDS return to appear on TRACES after filing?",
          "a": "After a TDS return is accepted by the TRACES processing system, the data typically becomes available for download (Form 16A, challan status, 26AS updates) within 3–5 business days. During peak periods — around quarterly return deadlines (31 July, 31 October, 31 January, 31 May) — processing may take up to 7 business days. For deductees, Form 26AS reflects the deductor's quarterly return data after TRACES processes the return, not at the time of challan deposit.",
          "article": "TRACES Portal: How to Download and Reconcile TDS Data for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-traces-portal-reconciliation-india"
        },
        {
          "q": "What is the TRACES Compliance Check and when should it be run?",
          "a": "The TRACES Compliance Check for Section 206AB/206CCA allows deductors to upload a list of vendor PANs and receive a status for each: compliant or specified person (non-filer triggering higher TDS). It should be run before each payment cycle for vendors above the relevant section threshold, not just at the start of the financial year. A vendor's ITR filing status can change during the year, and the check date and result must be retained as audit evidence for the rate applied at each payment.",
          "article": "TRACES Portal: How to Download and Reconcile TDS Data for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-traces-portal-reconciliation-india"
        },
        {
          "q": "When is the last date to deposit TDS for March 2026?",
          "a": "TDS deducted during March 2026 must be deposited by 30 April 2026. This is the only month where the deposit deadline extends beyond the standard 7th-of-the-following-month rule. The Q4 TDS return (January–March) is then due by 31 May 2026.",
          "article": "TDS Year-End Reconciliation: March 31 Close Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-year-end-march-close-india"
        },
        {
          "q": "What is Section 40(a)(ia) and how does it affect year-end TDS reconciliation?",
          "a": "Section 40(a)(ia) disallows 30% of any expense where TDS was required to be deducted or deposited but was not. The disallowance applies for the year in which the expense was booked. During year-end reconciliation, finance teams must confirm that every expense above the TDS threshold — contractor fees, professional fees, rent, interest — has TDS either deducted or covered by a lower deduction certificate under Section 197. Any gap at 31 March creates a 30% disallowance risk on that expense.",
          "article": "TDS Year-End Reconciliation: March 31 Close Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-year-end-march-close-india"
        },
        {
          "q": "Can TDS receivable as at March 31 be claimed if it is not yet reflected in Form 26AS?",
          "a": "Yes, but with a reconciling item. Form 26AS reflects TDS only after the deductor files the quarterly return — which is due 31 May for Q4. At 31 March, TDS deducted in Q4 by counterparties will not yet appear in Form 26AS. Finance teams should book the receivable based on supporting evidence (TDS certificates, payment advice, agreements) and create a reconciling item noting that TRACES reflection is pending. AIS and Form 26AS should be reviewed again after 31 May to confirm the credit appears.",
          "article": "TDS Year-End Reconciliation: March 31 Close Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-year-end-march-close-india"
        },
        {
          "q": "What should be done about March 31 payments where TDS was deducted but not yet deposited?",
          "a": "TDS deducted on 31 March must be deposited by 30 April. At the March 31 balance sheet date, this amount sits as TDS payable — a current liability. Confirm the challan was deposited before 30 April and that OLTAS reflects the deposit. If the deposit is delayed past 30 April, interest under Section 201(1A) at 1.5% per month accrues from 31 March, and this should be provisioned in the year-end accounts.",
          "article": "TDS Year-End Reconciliation: March 31 Close Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-year-end-march-close-india"
        },
        {
          "q": "How should advance payments with TDS in Q4 be handled in year-end reconciliation?",
          "a": "Advance payments made in Q4 where TDS was deducted create a timing issue: the TDS deduction is recorded in the Q4 return, but the expense may be capitalised or carried as an advance in the balance sheet rather than recognised as an expense in FY 2025-26. In this case, TDS payable is correctly accounted for in Q4, but the corresponding expense deduction under Section 40(a)(ia) applies only when the expense is recognised. Document the advance nature and the TDS deduction separately to avoid incorrect disallowance treatment.",
          "article": "TDS Year-End Reconciliation: March 31 Close Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tds-year-end-march-close-india"
        }
      ]
    },
    "nach-statutory": {
      "label": "NACH and Statutory Payments",
      "faqs": [
        {
          "q": "What are the advance tax instalment deadlines for Indian companies?",
          "a": "Indian companies must pay advance tax in four instalments: 15% of estimated tax liability by 15 June, 45% by 15 September, 75% by 15 December, and 100% by 15 March. These percentages are cumulative — by 15 September, the total advance tax paid should be at least 45% of the full-year liability, not 45% of the remaining amount. If any instalment date falls on a bank holiday, payment is due on the next working day. The assessment year for FY 2025-26 is AY 2026-27, and all Challan 280 payments must specify AY 2026-27 correctly.",
          "article": "Advance Tax Reconciliation in India: Challan 280 Matching, CIN Tracking, and Form 26AS",
          "url": "https://www.terra-insight.com/insights/advance-tax-reconciliation-india"
        },
        {
          "q": "What is the CIN (Challan Identification Number) and how is it used to verify advance tax payment?",
          "a": "The CIN (Challan Identification Number) is the three-part identifier printed on the counterfoil of Challan 280 after payment: BSR code of the bank branch (7 digits) + date of deposit (DDMMYYYY) + challan serial number (5 digits). The CIN is the match key that links the Challan 280 payment to the advance tax credit in Form 26AS. During reconciliation, the CIN from the bank challan counterfoil or bank statement must match the CIN appearing in Form 26AS Part F (Details of Tax Deducted at Source / Tax Collected at Source / Advance Tax). If the CIN does not appear in Form 26AS, the payment has not been credited to the PAN.",
          "article": "Advance Tax Reconciliation in India: Challan 280 Matching, CIN Tracking, and Form 26AS",
          "url": "https://www.terra-insight.com/insights/advance-tax-reconciliation-india"
        },
        {
          "q": "How long after a Challan 280 payment does the credit appear in Form 26AS?",
          "a": "After a Challan 280 payment is made online or at a bank branch, the credit typically appears in Form 26AS within 3 to 7 working days. For NEFT-based payments through netbanking, the update is usually faster (3–4 days). For physical challan payments at bank branches, the branch must upload the data, which can take 5–7 working days. Reconciliation run immediately after payment will show the bank debit but not the Form 26AS credit — this is a timing difference that should be tagged and reviewed 7 days after payment.",
          "article": "Advance Tax Reconciliation in India: Challan 280 Matching, CIN Tracking, and Form 26AS",
          "url": "https://www.terra-insight.com/insights/advance-tax-reconciliation-india"
        },
        {
          "q": "What interest rate applies under Section 234C for missing an advance tax instalment?",
          "a": "Section 234C interest applies when the cumulative advance tax paid by any instalment date is less than the prescribed percentage. The interest rate is 1% per month (12% per annum) on the shortfall amount, calculated for a period of 3 months (for June and September instalments) or 1 month (for December and March instalments). For example, if the September instalment requires 45% of ₹10,00,000 tax = ₹4,50,000, and only ₹3,00,000 was paid, Section 234C interest applies on ₹1,50,000 at 1% per month for 3 months = ₹4,500.",
          "article": "Advance Tax Reconciliation in India: Challan 280 Matching, CIN Tracking, and Form 26AS",
          "url": "https://www.terra-insight.com/insights/advance-tax-reconciliation-india"
        },
        {
          "q": "What happens if advance tax is paid under the wrong PAN or wrong assessment year?",
          "a": "If Challan 280 is paid under the wrong PAN, the credit will appear in Form 26AS of the wrong taxpayer, not in the company's Form 26AS. The company will show a shortfall, and Section 234B/234C interest will accrue. Correction requires submitting a challan correction request through the bank that accepted the payment, or through the Assessing Officer's office, which can take 30–90 days. If paid under the correct PAN but wrong assessment year, the credit appears under the wrong year and the same correction process applies. Both errors must be corrected before the return filing date to avoid demand notices.",
          "article": "Advance Tax Reconciliation in India: Challan 280 Matching, CIN Tracking, and Form 26AS",
          "url": "https://www.terra-insight.com/insights/advance-tax-reconciliation-india"
        },
        {
          "q": "What is the primary difference between ECS and NACH for reconciliation?",
          "a": "The primary reconciliation difference is the match key. Legacy ECS used the MICR code and bank account number as the mandate identifier — a combination that was not unique across banks and did not support end-to-end tracking from originator to destination bank. NACH replaced this with the UMRN (Unique Mandate Reference Number), a 20-character alphanumeric identifier assigned by NPCI at mandate registration. The UMRN appears in every NACH file — the batch submission, the settlement confirmation, and the return file — making mandate-level traceability possible in a way that ECS never supported.",
          "article": "ECS to NACH Migration Reconciliation: Handling Dual-Running Periods and Mandate Transfer",
          "url": "https://www.terra-insight.com/insights/ecs-nach-migration-reconciliation"
        },
        {
          "q": "What was the key match identifier in legacy ECS, and how does NACH's UMRN differ?",
          "a": "Legacy ECS mandates were identified using the MICR code of the destination bank branch plus the account number. This combination was not globally unique — two accounts at different banks could share the same MICR+account pattern in edge cases — and the MICR code changed when a bank branch relocated or was absorbed in a merger. NACH's UMRN is a 20-character alphanumeric code assigned by NPCI centrally at mandate registration. The UMRN never changes for the life of the mandate and is unique across all banks, making it a reliable primary key for reconciliation.",
          "article": "ECS to NACH Migration Reconciliation: Handling Dual-Running Periods and Mandate Transfer",
          "url": "https://www.terra-insight.com/insights/ecs-nach-migration-reconciliation"
        },
        {
          "q": "What is the risk of double debit during ECS to NACH migration?",
          "a": "Double debit occurs when an ECS mandate and a NACH mandate for the same borrower and the same EMI due date are both active and both presented in the same billing cycle. Since ECS and NACH run on separate rails and separate bank processing queues, the destination bank processes both independently and may honour both — debiting the borrower's account twice for the same EMI. The lender receives two credits for the same loan account. Preventing this requires maintaining a deduplication flag in the mandate register: once a NACH mandate is registered and active for a borrower, the corresponding ECS mandate must be cancelled before the next ECS batch submission.",
          "article": "ECS to NACH Migration Reconciliation: Handling Dual-Running Periods and Mandate Transfer",
          "url": "https://www.terra-insight.com/insights/ecs-nach-migration-reconciliation"
        },
        {
          "q": "How should finance teams reconcile collections during the dual-running period when both ECS and NACH are active?",
          "a": "During the dual-running period, the reconciliation system must maintain two parallel mandate registers: one for active ECS mandates with MICR+account as match key, and one for active NACH mandates with UMRN as match key. Each bank credit must be tagged to its originating channel — ECS or NACH — based on the transaction reference format. Once tagged, the credit is matched to the borrower's loan record using the appropriate match key. A deduplication check must run before each batch submission to ensure no borrower has both an ECS and a NACH mandate active for the same due date.",
          "article": "ECS to NACH Migration Reconciliation: Handling Dual-Running Periods and Mandate Transfer",
          "url": "https://www.terra-insight.com/insights/ecs-nach-migration-reconciliation"
        },
        {
          "q": "Has RBI fully phased out ECS in favour of NACH?",
          "a": "RBI mandated the migration from ECS to NACH and directed banks to transition mandate volumes to the NACH platform. NACH is now the active platform managed by NPCI for bulk debit and credit mandates. Legacy ECS infrastructure has been wound down at most major banks. However, some organisations that completed the technical migration early still carry residual ECS references in their internal systems for historical mandate records predating the migration. For active mandate books, NACH is the only operating channel.",
          "article": "ECS to NACH Migration Reconciliation: Handling Dual-Running Periods and Mandate Transfer",
          "url": "https://www.terra-insight.com/insights/ecs-nach-migration-reconciliation"
        },
        {
          "q": "What is the ESI employer contribution rate and employee contribution rate?",
          "a": "The employer ESI contribution rate is 3.25% of gross salary. The employee ESI contribution rate is 0.75% of gross salary. Both contributions are calculated on gross salary (including basic, DA, HRA, and all allowances except overtime wages and certain excluded payments). The combined ESI contribution rate is 4% of gross salary for covered employees. For employees earning up to ₹137 per day, the employee contribution is waived — the employer still contributes 3.25%.",
          "article": "ESI Contribution Reconciliation in India: ESIC Challan Matching and Wage Month Verification",
          "url": "https://www.terra-insight.com/insights/esi-contribution-reconciliation-india"
        },
        {
          "q": "Which employees are covered under ESI and what is the wage ceiling?",
          "a": "ESI coverage applies to employees earning ₹21,000 per month or less in gross salary (₹25,000 per month for persons with disability). Coverage is determined at the start of each contribution period — April 1 or October 1 — based on wages in the preceding period. An employee who earns ₹18,000 per month in October gets covered from October 1 regardless of whether their salary rises above ₹21,000 during the six-month period ending March 31. Coverage ends only at the next contribution period boundary.",
          "article": "ESI Contribution Reconciliation in India: ESIC Challan Matching and Wage Month Verification",
          "url": "https://www.terra-insight.com/insights/esi-contribution-reconciliation-india"
        },
        {
          "q": "What is an IP number in ESI and how is it used in contribution reconciliation?",
          "a": "An IP (Insurance Policy) number is the unique identifier assigned to each covered employee by ESIC when they are registered on the ESIC portal. The IP number is used to match contribution data at the employee level: the employer's monthly return lists contributions by IP number, and ESIC's records are maintained at the IP number level. During ESI reconciliation, the count of active IP numbers in the ESIC portal for the wage month should match the count of covered employees in the payroll register. IP number mismatches occur when new employees are not registered promptly or when exited employees remain active in the ESIC portal.",
          "article": "ESI Contribution Reconciliation in India: ESIC Challan Matching and Wage Month Verification",
          "url": "https://www.terra-insight.com/insights/esi-contribution-reconciliation-india"
        },
        {
          "q": "What is the deadline for paying the monthly ESI challan?",
          "a": "The monthly ESI challan must be paid by the 15th of the month following the wage month. For wages paid in January, the ESI challan payment deadline is 15 February. The employer must file the monthly contribution return on the ESIC portal and pay the challan within this deadline. Late payment attracts interest at 12% per annum under the ESI Act. If the 15th falls on a bank holiday, the payment is due on the next working day.",
          "article": "ESI Contribution Reconciliation in India: ESIC Challan Matching and Wage Month Verification",
          "url": "https://www.terra-insight.com/insights/esi-contribution-reconciliation-india"
        },
        {
          "q": "How does the 6-month eligibility period in ESI create reconciliation complexity for companies with frequent salary revisions?",
          "a": "ESI contribution periods run April–September and October–March. Coverage for each period is determined by wages in the immediately preceding period. An employee earning ₹19,000 per month during April–September will be covered during October–March — even if their salary is revised to ₹24,000 in November. The ESI challan for November must include this employee at the new gross salary of ₹24,000 (contributions at 4% of ₹24,000), even though the employee is above the ₹21,000 ceiling. Companies with bi-annual salary revision cycles see systematic headcount and contribution mismatches at each contribution period boundary, requiring a reconciliation run specifically for the transition months of April and October.",
          "article": "ESI Contribution Reconciliation in India: ESIC Challan Matching and Wage Month Verification",
          "url": "https://www.terra-insight.com/insights/esi-contribution-reconciliation-india"
        },
        {
          "q": "Should I apply the 15-day or 45-day rule if I am not sure whether a written agreement exists?",
          "a": "Apply the 15-day rule as a conservative default. If no written agreement is documented in your records, Section 15 of the MSMED Act treats the relationship as having no agreed payment period, which triggers the 15-day window. Retroactively claiming that an informal understanding constitutes a written agreement is not accepted under the Act. The safer approach is to formalise all MSME vendor agreements in writing and retain the documents, which then permits the 45-day window.",
          "article": "MSME 45-Day Payment Tracker: How to Reconcile Vendor Payables Under Section 43B(h)",
          "url": "https://www.terra-insight.com/insights/msme-45-day-payment-compliance-tracker"
        },
        {
          "q": "What if a payment to an MSME vendor is partial?",
          "a": "Partial payment does not reset the clock on the remaining outstanding amount. If ₹5 lakh is due to an MSME and ₹2 lakh is paid within 15 days, the remaining ₹3 lakh continues to age from the original acceptance date. If the ₹3 lakh is not paid within the applicable window (15 or 45 days from acceptance), only that amount is disallowed under Section 43B(h). Track each invoice balance separately — do not aggregate across invoices from the same vendor.",
          "article": "MSME 45-Day Payment Tracker: How to Reconcile Vendor Payables Under Section 43B(h)",
          "url": "https://www.terra-insight.com/insights/msme-45-day-payment-compliance-tracker"
        },
        {
          "q": "Does NEFT/RTGS transfer date or the date it credits to the MSME account count as the payment date?",
          "a": "For Section 43B purposes, the relevant date is when the payment leaves the buyer's account — that is, the bank debit date on the NEFT/RTGS transaction. NEFT settles in hourly batches and RTGS is real-time during business hours, so the credit at the MSME's end normally happens the same day. The UTR generated at the time of NEFT/RTGS initiation is the documentary evidence of payment date. Retain UTR records for all MSME vendor payments as part of the compliance trail.",
          "article": "MSME 45-Day Payment Tracker: How to Reconcile Vendor Payables Under Section 43B(h)",
          "url": "https://www.terra-insight.com/insights/msme-45-day-payment-compliance-tracker"
        },
        {
          "q": "How often should I run the MSME payment age analysis?",
          "a": "Monthly at minimum, but for companies with high MSME vendor volumes, a weekly review is more protective. The 15-day window in particular requires near-real-time monitoring — by the time a monthly review catches a breach, it is already too late for that payment. Set system alerts when MSME payables reach 10 days outstanding (for the 15-day rule) and 35 days outstanding (for the 45-day rule), giving the AP team a working window to clear before breach.",
          "article": "MSME 45-Day Payment Tracker: How to Reconcile Vendor Payables Under Section 43B(h)",
          "url": "https://www.terra-insight.com/insights/msme-45-day-payment-compliance-tracker"
        },
        {
          "q": "What is a UMRN and how is it used in NACH mandate reconciliation?",
          "a": "UMRN stands for Unique Mandate Reference Number — a 20-character alphanumeric identifier assigned by NPCI when a NACH mandate is successfully registered. In mandate reconciliation, the UMRN is the primary key used to match the internal mandate register entry against NPCI's mandate database. If a UMRN appears in the internal register with status Active but NPCI shows it as Cancelled, the next NACH debit presentation using that UMRN will return with code 25 (Mandate Cancelled). Regular UMRN-level reconciliation against NPCI's portal prevents these avoidable returns.",
          "article": "NACH Mandate Management and Reconciliation: Active Mandates, Amendments, and Cancellations",
          "url": "https://www.terra-insight.com/insights/nach-mandate-management-reconciliation"
        },
        {
          "q": "What happens when a borrower cancels their NACH mandate directly with their bank?",
          "a": "When a borrower submits a cancellation request to their bank, the bank processes the cancellation through NPCI's NACH mandate management system. NPCI updates the mandate status to Cancelled and the UMRN becomes inactive. The originator (NBFC or lender) is not automatically notified — the cancellation appears only in the return file when the next debit presentation fails with return code 25. This notification gap is why proactive mandate register reconciliation matters: without a weekly check against NPCI's mandate status data, the lender discovers the cancellation only after a failed debit.",
          "article": "NACH Mandate Management and Reconciliation: Active Mandates, Amendments, and Cancellations",
          "url": "https://www.terra-insight.com/insights/nach-mandate-management-reconciliation"
        },
        {
          "q": "How often should an NBFC reconcile its internal mandate register against NPCI's records?",
          "a": "For NBFCs with active NACH debit batches, a weekly mandate register reconciliation is the minimum acceptable frequency. High-volume lenders (above 50,000 active mandates) should run reconciliation at least twice per month, with an additional check 48 hours before each major batch submission. The pre-batch check catches cancellations and expired mandates that would otherwise generate avoidable returns. Some lenders with API access to their bank's NACH portal run daily mandate status checks for mandates flagged as at-risk (previous code 01 returns or recent stop payment history).",
          "article": "NACH Mandate Management and Reconciliation: Active Mandates, Amendments, and Cancellations",
          "url": "https://www.terra-insight.com/insights/nach-mandate-management-reconciliation"
        },
        {
          "q": "What is the process for amending a NACH mandate when a borrower changes their bank account?",
          "a": "A NACH mandate amendment for a bank account change requires the originator to submit a cancellation request for the existing UMRN and register a fresh NACH mandate on the new bank account. NACH does not support mid-mandate account number changes in place — the amendment is a cancel-and-reregister process. The new mandate registration typically takes 5–7 working days to be activated by NPCI. During this window, the EMI cannot be collected via NACH; the lender must arrange an alternative collection method (UPI AutoPay or post-dated cheques) to avoid a DPD gap.",
          "article": "NACH Mandate Management and Reconciliation: Active Mandates, Amendments, and Cancellations",
          "url": "https://www.terra-insight.com/insights/nach-mandate-management-reconciliation"
        },
        {
          "q": "How long does a new NACH mandate registration take to become active for the first EMI debit?",
          "a": "A new NACH mandate registration submitted to NPCI through the presenting bank takes 5–7 working days to be processed and activated. The mandate becomes available for debit presentations only after NPCI assigns a UMRN and marks the mandate as Active. First-time debit presentations can be submitted only after this activation. If a batch is submitted with a UMRN that has not yet been activated, the presentation will return with an error code. Lenders typically build a 10-day buffer between mandate registration and the first EMI due date to account for processing delays.",
          "article": "NACH Mandate Management and Reconciliation: Active Mandates, Amendments, and Cancellations",
          "url": "https://www.terra-insight.com/insights/nach-mandate-management-reconciliation"
        },
        {
          "q": "How quickly should an NBFC update the LMS after receiving a NACH return file?",
          "a": "RBI's prudential norms require that DPD counting begins from the contractual due date, not from the date the NBFC processes the return. In practice, this means the LMS must be updated within the same business day the return file is received — typically T+1 or T+2 from presentation date. An NBFC that processes returns only during weekly reconciliation runs will systematically understate DPD for 5–6 days on every failed debit, which affects NPA provisioning accuracy for the period.",
          "article": "NACH Reconciliation for NBFCs and Lenders: EMI Collection Matching and LMS Updates",
          "url": "https://www.terra-insight.com/insights/nach-nbfc-lender-reconciliation"
        },
        {
          "q": "What is the impact of a delayed NACH reconciliation on DPD reporting for an NBFC?",
          "a": "Under RBI IRACP norms, a loan account becomes a Non-Performing Asset (NPA) when it remains overdue for more than 90 days. If the NACH return is posted to the LMS 5–7 days late in each billing cycle, the effective DPD count is understated by those days. Over three billing cycles, this can delay NPA classification by 15–21 days relative to the correct timeline — directly affecting provisioning requirements and regulatory reporting accuracy.",
          "article": "NACH Reconciliation for NBFCs and Lenders: EMI Collection Matching and LMS Updates",
          "url": "https://www.terra-insight.com/insights/nach-nbfc-lender-reconciliation"
        },
        {
          "q": "How does an NBFC handle a partial NACH settlement where the bank debits less than the full EMI amount?",
          "a": "Partial NACH settlements are uncommon but occur when a bank applies a partial debit due to account-level restrictions. The reconciliation system receives a settlement amount lower than the presented amount. The correct LMS update is to post the actual amount collected as a partial payment, mark the balance as outstanding, and begin DPD counting on the unpaid portion from the original due date. For detailed handling, the partial payment reconciliation India process applies the same net-settled logic used in payment gateway contexts.",
          "article": "NACH Reconciliation for NBFCs and Lenders: EMI Collection Matching and LMS Updates",
          "url": "https://www.terra-insight.com/insights/nach-nbfc-lender-reconciliation"
        },
        {
          "q": "Can an NBFC retry a NACH debit that returned with code 01 (Insufficient Funds)?",
          "a": "Yes. Return code 01 (Insufficient Funds) is a retriable return under NPCI's NACH framework. The originator can submit a fresh NACH presentation using the same UMRN. Most NBFCs allow a maximum of 2 retries per billing cycle. The retry window is typically 3–5 business days from the original return date. Each retry resets the presentation date but does not reset the DPD counter — the DPD counter runs from the original contractual due date regardless of retry attempts.",
          "article": "NACH Reconciliation for NBFCs and Lenders: EMI Collection Matching and LMS Updates",
          "url": "https://www.terra-insight.com/insights/nach-nbfc-lender-reconciliation"
        },
        {
          "q": "What is the RBI reporting requirement for NBFCs regarding NACH return rates?",
          "a": "RBI does not publish a specific NACH return rate threshold in isolation, but NACH return rates feed directly into the NBFC's portfolio-at-risk (PAR) metrics, which form part of the Supervisory Return (NBS-7 and NBS-9) submitted to RBI. An NBFC with high unreconciled NACH return rates may show understated PAR figures in regulatory returns, which can attract scrutiny during inspections. Accurate NACH reconciliation is therefore both an operational and a compliance requirement.",
          "article": "NACH Reconciliation for NBFCs and Lenders: EMI Collection Matching and LMS Updates",
          "url": "https://www.terra-insight.com/insights/nach-nbfc-lender-reconciliation"
        },
        {
          "q": "What does NACH return code 01 mean and can the mandate be retried?",
          "a": "NACH return code 01 means Insufficient Funds — the borrower's account did not have enough balance on the presentation date. This is a retriable return. Most lenders allow up to 2 retry attempts within the same billing cycle. The retry must be submitted as a new NACH batch with the same UMRN. Each retry attempt resets the presentation date for DPD calculation purposes, so lenders typically retry within 3–5 business days of the original return.",
          "article": "NACH Return Codes in India: Full Reference and Resolution Guide for Finance Teams",
          "url": "https://www.terra-insight.com/insights/nach-return-codes-india"
        },
        {
          "q": "What is the difference between NACH return code 20 (Account Closed) and 25 (Mandate Cancelled)?",
          "a": "Code 20 (Account Closed) means the destination bank account no longer exists. Code 25 (Mandate Cancelled by Account Holder) means the account is active but the borrower has specifically withdrawn the NACH mandate authorization. Both are non-retriable returns, but the resolution differs: code 20 requires the borrower to register a new mandate on a different bank account, while code 25 requires mandate re-registration on the same or a different account — and may indicate intentional non-payment, which triggers a separate collections workflow.",
          "article": "NACH Return Codes in India: Full Reference and Resolution Guide for Finance Teams",
          "url": "https://www.terra-insight.com/insights/nach-return-codes-india"
        },
        {
          "q": "How does a NACH return code 27 (Stop Payment) differ from an insufficient funds return?",
          "a": "Code 27 (Stop Payment) means the account holder has placed a specific instruction with their bank to stop the NACH debit. Unlike code 01 (Insufficient Funds), code 27 is a deliberate borrower action and is classified as a dispute return, not a liquidity failure. Retrying a code 27 return without resolving the underlying dispute will result in a repeated code 27. The correct workflow is to initiate a borrower contact and dispute resolution process — not a standard retry.",
          "article": "NACH Return Codes in India: Full Reference and Resolution Guide for Finance Teams",
          "url": "https://www.terra-insight.com/insights/nach-return-codes-india"
        },
        {
          "q": "How quickly does an NBFC receive the NACH return file after a failed debit?",
          "a": "Under the NPCI NACH framework, the destination bank returns rejected mandates to NPCI, and the return file is made available to the presenting bank (and through it, to the originator) within T+1 or T+2 business days from the presentation date. In practice, most NBFCs configure their bank's API integration to receive the return file by T+1 morning. A 48-hour processing window is the maximum accepted delay before DPD reporting is considered understated.",
          "article": "NACH Return Codes in India: Full Reference and Resolution Guide for Finance Teams",
          "url": "https://www.terra-insight.com/insights/nach-return-codes-india"
        },
        {
          "q": "What is the UMRN and how is it used to match a NACH return to a specific borrower account?",
          "a": "UMRN stands for Unique Mandate Reference Number — a 20-character alphanumeric identifier assigned by NPCI at the time of mandate registration. Every NACH debit presentation carries the UMRN, and every return file entry includes the UMRN of the failed mandate. The reconciliation system uses the UMRN as the primary match key to link each return code back to the specific borrower, loan account, and scheduled EMI amount in the loan management system (LMS).",
          "article": "NACH Return Codes in India: Full Reference and Resolution Guide for Finance Teams",
          "url": "https://www.terra-insight.com/insights/nach-return-codes-india"
        },
        {
          "q": "What is the PF ECR and what does it contain?",
          "a": "The ECR (Electronic Challan cum Return) is the single monthly filing submitted by employers on the EPFO portal that combines both the challan (payment instruction) and the return (employee-level contribution data). It contains each employee's UAN, wage month, gross wages, EPF wages, employer EPF contribution (3.67%), employer EPS contribution (8.33%, capped at ₹15,000 basic), employee EPF contribution (12%), and EDLI contribution (0.5%). Filing and payment must happen together — the ECR generates the TRRN once the challan amount is confirmed.",
          "article": "PF ECR Reconciliation in India: Matching EPFO Challan Returns to Books and Bank",
          "url": "https://www.terra-insight.com/insights/pf-ecr-reconciliation-india"
        },
        {
          "q": "What is the TRRN and how is it used in PF bank reconciliation?",
          "a": "The TRRN (Transaction Reference Number) is a unique number generated by the EPFO portal when the employer raises a PF challan. It appears in the bank narration as 'EPFO TRRN [number] PF CONTRIBUTION [MONTH]' when the challan amount is debited. The TRRN is the primary match key linking the ECR filing on the EPFO portal, the bank debit on the bank statement, and the PF expense ledger entry in the books. Without the TRRN, PF bank reconciliation relies on amount matching alone, which fails when multiple challans of similar amounts are filed in the same period.",
          "article": "PF ECR Reconciliation in India: Matching EPFO Challan Returns to Books and Bank",
          "url": "https://www.terra-insight.com/insights/pf-ecr-reconciliation-india"
        },
        {
          "q": "What is the deadline for filing the PF ECR and paying the challan?",
          "a": "The ECR must be filed and the corresponding PF challan must be paid by the 15th of the month following the wage month. For wages paid in January, the ECR filing and challan payment deadline is 15 February. The deadline applies to all establishments covered under the EPF and MP Act, 1952. Late payment attracts interest under Section 7Q at the rate of 12% per annum from the due date to the actual date of payment.",
          "article": "PF ECR Reconciliation in India: Matching EPFO Challan Returns to Books and Bank",
          "url": "https://www.terra-insight.com/insights/pf-ecr-reconciliation-india"
        },
        {
          "q": "How are PF contributions calculated for employees earning more than ₹15,000 basic salary?",
          "a": "For employees with basic salary above ₹15,000, the employer's EPS (Employees' Pension Scheme) contribution is capped at 8.33% of ₹15,000 = ₹1,250 per month. The employer's EPF contribution for such employees is 12% of actual basic minus ₹1,250. The employee's own EPF contribution remains 12% of actual basic with no cap. In the ECR, the 'EPF wages' column shows the actual basic; the EPS calculation is automatically capped by the portal. Misapplying the cap — either in payroll or during ECR reconciliation — is a common source of ECR-to-payroll mismatch.",
          "article": "PF ECR Reconciliation in India: Matching EPFO Challan Returns to Books and Bank",
          "url": "https://www.terra-insight.com/insights/pf-ecr-reconciliation-india"
        },
        {
          "q": "What interest rate applies if PF challan payment is delayed past the 15th of the month?",
          "a": "Late PF challan payment attracts interest under Section 7Q of the EPF and MP Act at 12% per annum (1% per month). The interest accrues from the due date (15th of the following month) to the actual date of payment. If a company has 100 employees with an average monthly PF contribution of ₹3,000 per employee, a single month's delay on a ₹3,00,000 challan accrues ₹3,000 in interest. Interest payments must be separately accounted for and are not deductible as business expense.",
          "article": "PF ECR Reconciliation in India: Matching EPFO Challan Returns to Books and Bank",
          "url": "https://www.terra-insight.com/insights/pf-ecr-reconciliation-india"
        },
        {
          "q": "Does Section 43B(h) apply to Medium enterprises?",
          "a": "No. Section 43B(h) covers only Micro and Small enterprises as defined under the MSMED Act 2006 (revised 2020). Micro enterprises have investment below ₹1 crore and turnover below ₹5 crore. Small enterprises have investment below ₹10 crore and turnover below ₹50 crore. Payments due to Medium enterprises (investment below ₹50 crore, turnover below ₹250 crore) are not subject to the 15/45-day disallowance rule.",
          "article": "Section 43B(h): MSME Payment Reconciliation and Tax Disallowance Risk",
          "url": "https://www.terra-insight.com/insights/section-43b-h-msme-payment-reconciliation"
        },
        {
          "q": "What if the MSME supplier does not have Udyam registration?",
          "a": "If a supplier has not obtained Udyam Registration from the government portal (udyamregistration.gov.in), they cannot legally claim MSME status. Section 43B(h) applies only to registered Micro and Small enterprises. However, the tax department may scrutinise situations where payments are delayed to suppliers who later obtain Udyam registration retroactively. Best practice is to collect Udyam certificates at the time of onboarding every new vendor.",
          "article": "Section 43B(h): MSME Payment Reconciliation and Tax Disallowance Risk",
          "url": "https://www.terra-insight.com/insights/section-43b-h-msme-payment-reconciliation"
        },
        {
          "q": "Can a written agreement extend the payment period beyond 45 days?",
          "a": "No. Section 15 of the MSMED Act sets a hard cap of 45 days regardless of the contract terms. A buyer and MSME supplier can agree to any timeline in writing, but the maximum enforceable period is 45 days from the date of delivery or acceptance. Any contractual clause exceeding 45 days is void in relation to the MSMED Act. The 15-day rule applies where no written agreement exists.",
          "article": "Section 43B(h): MSME Payment Reconciliation and Tax Disallowance Risk",
          "url": "https://www.terra-insight.com/insights/section-43b-h-msme-payment-reconciliation"
        },
        {
          "q": "Is there a penalty beyond tax disallowance under 43B(h)?",
          "a": "Yes. Beyond income tax disallowance, the MSMED Act provides for compound interest on overdue payments at three times the bank rate notified by RBI. This civil remedy is separate from the tax consequence. Additionally, CARO 2020 requires company auditors to specifically disclose amounts due to MSMEs outstanding for more than 45 days in the audit report, creating reputational and regulatory exposure beyond the tax risk alone.",
          "article": "Section 43B(h): MSME Payment Reconciliation and Tax Disallowance Risk",
          "url": "https://www.terra-insight.com/insights/section-43b-h-msme-payment-reconciliation"
        },
        {
          "q": "In which year is the disallowed amount eventually claimed as a deduction?",
          "a": "The disallowed amount is deductible only in the financial year in which actual payment is made to the MSME supplier. If ₹10 lakh due to an MSME was not paid in FY 2024-25, it is disallowed in AY 2025-26. When the payment is made in FY 2025-26, the ₹10 lakh becomes deductible in AY 2026-27. There is no retrospective relief — the timing of actual payment determines the year of deduction.",
          "article": "Section 43B(h): MSME Payment Reconciliation and Tax Disallowance Risk",
          "url": "https://www.terra-insight.com/insights/section-43b-h-msme-payment-reconciliation"
        },
        {
          "q": "What are the statutory payment deadlines that Indian companies must track each month?",
          "a": "Indian companies must track the following recurring statutory payment deadlines: TDS challan (Challan 281) — 7th of the following month (30 April for March); GST PMT-06 / monthly challan — 20th of the following month for GSTR-3B filers; PF ECR filing and challan payment — 15th of the following month; ESI challan — 15th of the following month; professional tax — varies by state, typically 15th–20th. Advance tax instalments are quarterly: 15 June, 15 September, 15 December, and 15 March. A single statutory payment register tracking all six obligation types with their due dates prevents deadline misses that arise when different teams manage different portals.",
          "article": "Statutory Payment Reconciliation in India: Managing TDS, GST, PF, and ESI in One View",
          "url": "https://www.terra-insight.com/insights/statutory-payment-reconciliation-india"
        },
        {
          "q": "What is a CPIN in GST payments and how is it used in reconciliation?",
          "a": "CPIN (Common Portal Identification Number) is the 14-digit number generated by the GST portal when a taxpayer creates a GST challan (PMT-06) for payment of CGST, SGST, IGST, or cess. The CPIN is valid for 15 days from generation. Once payment is made, the bank transmits the CPIN to the GST portal, which updates the electronic cash ledger. The CPIN is the primary match key in GST payment reconciliation — it links the GST challan in the GST portal to the bank debit. The bank narration for GST payments follows: 'NEFT CR GSTN CPIN [14-digit number] CGST SGST IGST'. Any GST portal challan without a CPIN confirmation is an open item in the statutory payment register.",
          "article": "Statutory Payment Reconciliation in India: Managing TDS, GST, PF, and ESI in One View",
          "url": "https://www.terra-insight.com/insights/statutory-payment-reconciliation-india"
        },
        {
          "q": "How should a company reconcile a statutory challan payment that was debited from the bank but has not yet appeared on the respective government portal?",
          "a": "This is a timing difference, not an error, in most cases. The standard resolution path is: (1) confirm the bank debit by locating the narration with the match key (TRRN, CPIN, CIN, or BSR+date+serial); (2) check the government portal status for the challan — most portals (TRACES, GST, EPFO, ESIC, OLTAS) have a challan status lookup by match key; (3) if the portal shows the challan as pending, allow 2–3 working days for confirmation; (4) if the portal shows no record after 5 working days, file an inquiry with the bank — the payment data may not have been transmitted. Tag the item in the statutory payment register as 'bank debit confirmed — portal pending' with the expected resolution date.",
          "article": "Statutory Payment Reconciliation in India: Managing TDS, GST, PF, and ESI in One View",
          "url": "https://www.terra-insight.com/insights/statutory-payment-reconciliation-india"
        },
        {
          "q": "What is the interest rate for late TDS deposit, and how is it calculated?",
          "a": "Interest for late TDS deposit is charged at 1.5% per month (18% per annum) under Section 201(1A) of the Income Tax Act for the period from the date on which TDS was deducted to the date of actual deposit. For TDS not deducted, the interest rate is 1% per month from the date on which TDS was deductible. Even a single day's delay triggers a full month's interest — a TDS challan due on 7 February and paid on 8 February incurs 1.5% interest for the full period. For a company with a monthly TDS liability of ₹5,00,000, a one-month delay costs ₹7,500 in interest.",
          "article": "Statutory Payment Reconciliation in India: Managing TDS, GST, PF, and ESI in One View",
          "url": "https://www.terra-insight.com/insights/statutory-payment-reconciliation-india"
        },
        {
          "q": "How many different portals does an Indian company typically log into to verify statutory payment compliance each month?",
          "a": "An Indian company with a workforce and multiple tax registrations typically logs into 5–6 separate portals every month to verify statutory payment compliance: (1) TRACES / Income Tax portal — for TDS challan confirmation and Form 26AS; (2) GST portal — for CPIN confirmation and electronic cash ledger; (3) EPFO portal — for TRRN confirmation and ECR filing status; (4) ESIC portal — for ESI challan confirmation and IP number count; (5) OLTAS portal — for advance tax CIN status; (6) state professional tax portal (if applicable). Each portal uses a different match key, a different login credential, and provides confirmation in a different format — making manual monthly verification a significant time sink without a consolidated statutory payment register.",
          "article": "Statutory Payment Reconciliation in India: Managing TDS, GST, PF, and ESI in One View",
          "url": "https://www.terra-insight.com/insights/statutory-payment-reconciliation-india"
        }
      ]
    },
    "retail-d2c": {
      "label": "Retail and D2C Reconciliation",
      "faqs": [
        {
          "q": "What fulfilment models do Ajio and Myntra offer to fashion sellers?",
          "a": "Ajio operates two primary models — Ajio Own Inventory (Ajio purchases stock from the brand, handles all fulfilment) and Ajio Sell On (the brand stocks in its own warehouse, Ajio facilitates the marketplace sale). Myntra offers Myntra Flex (vendor-managed inventory with Myntra's logistics) and Myntra FBF (Fulfilled by Flipkart, with stock held at Flipkart warehouses). Each model carries a different commission band, fulfilment fee structure, and tax treatment under Section 52 and Section 194O.",
          "article": "Ajio and Myntra Seller Settlement Reconciliation: Fulfilment Models, Returns, TDS 194O",
          "url": "https://www.terra-insight.com/insights/ajio-seller-settlement-reconciliation-india"
        },
        {
          "q": "What are the typical commission tiers for Ajio and Myntra sellers?",
          "a": "Myntra commission tiers typically range from 15 to 28 percent depending on category and brand tier — premium and private-label brands see higher commission than standard. Ajio Sell On commission ranges from 12 to 25 percent, with Ajio Own Inventory operating on a wholesale margin structure (35 to 50 percent off MRP) rather than a commission. Fulfilment fees add ₹35 to ₹70 per shipment on top of commission for platform-fulfilled orders. Reverse-logistics fees on returns add another ₹40 to ₹80 per returned unit.",
          "article": "Ajio and Myntra Seller Settlement Reconciliation: Fulfilment Models, Returns, TDS 194O",
          "url": "https://www.terra-insight.com/insights/ajio-seller-settlement-reconciliation-india"
        },
        {
          "q": "How does TDS Section 194O apply to Ajio and Myntra sellers?",
          "a": "Both Ajio and Myntra, as e-commerce operators, deduct TDS at 1% under Section 194O on the gross sale value (excluding GST) of each seller's supplies once annual payouts exceed ₹5 lakh per individual seller. Below the threshold, no deduction applies. The 1% is deducted from each payout after crossing the threshold for the financial year. The seller sees the deduction in Form 26AS Part A and can claim it against income tax liability. For seller entities (non-individual), the threshold does not apply and 194O is deducted from the first rupee of payout.",
          "article": "Ajio and Myntra Seller Settlement Reconciliation: Fulfilment Models, Returns, TDS 194O",
          "url": "https://www.terra-insight.com/insights/ajio-seller-settlement-reconciliation-india"
        },
        {
          "q": "How are fashion return rates netted in the Ajio and Myntra settlement?",
          "a": "Fashion categories on Ajio and Myntra experience return rates of 25 to 40 percent. Return netting works as follows: the platform's weekly settlement credits the seller for all orders where delivery was confirmed in the window and the return window has lapsed (7 to 15 days depending on category). Orders still in the return window are held as pending. When a return happens, the platform reverses revenue recognition, returns stock to the seller (for vendor-managed models) or to the platform warehouse (for FBF), and nets the reversal against the next settlement. TCS under Section 52 is also reversed via a revised GSTR-8 in the platform's next filing.",
          "article": "Ajio and Myntra Seller Settlement Reconciliation: Fulfilment Models, Returns, TDS 194O",
          "url": "https://www.terra-insight.com/insights/ajio-seller-settlement-reconciliation-india"
        },
        {
          "q": "What is the settlement cycle for Ajio and Myntra?",
          "a": "Myntra settles weekly for vendor-managed Flex orders, typically on a T+10 to T+15 cycle from delivery confirmation to allow for the return window. Ajio Sell On follows a similar T+10 to T+14 cycle. For Ajio Own Inventory and Myntra FBF (which use platform-owned stock), the payment cycle is the wholesale B2B cycle — 30 to 60 days from invoice depending on the brand's contract. Finance teams must track each fulfilment model's cycle independently; consolidating them produces receivable aging that mixes B2C settlement and B2B trade receivables incorrectly.",
          "article": "Ajio and Myntra Seller Settlement Reconciliation: Fulfilment Models, Returns, TDS 194O",
          "url": "https://www.terra-insight.com/insights/ajio-seller-settlement-reconciliation-india"
        },
        {
          "q": "What is Amazon SPN and how does it relate to seller GST filing?",
          "a": "Amazon SPN (Service Provider Network) is Amazon's network of tax consultants, chartered accountants, and service providers authorised to support sellers with GST registration, filing, reconciliation, and accounting. SPN partners use Amazon's seller data exports (orders, payments, TCS) to prepare GSTR-1 and GSTR-3B filings for their seller clients. The key data sources are the Amazon Business Reports (order-level data) and MTR (Merchant Tax Report) which gives GSTIN-level and invoice-level GST detail for filing.",
          "article": "Amazon SPN Seller GST Reconciliation: Easy Ship, FBA, and Returns Impact on GSTR-1",
          "url": "https://www.terra-insight.com/insights/amazon-spn-gst-reconciliation-india"
        },
        {
          "q": "How do Easy Ship and FBA differ for GST reconciliation?",
          "a": "Under Easy Ship, the seller retains inventory at their own warehouse and Amazon picks up each order for delivery. The seller is the supplier of record, issues the tax invoice, and ships from the warehouse state. Under FBA (Fulfilled by Amazon), the seller transfers inventory to Amazon fulfilment centres in multiple states, which means the seller must register for GST in each state where FBA inventory is held. Each FBA fulfilment centre state generates its own place-of-supply under Section 10 of the IGST Act, changing the SGST versus IGST split per order based on which FC fulfilled the shipment.",
          "article": "Amazon SPN Seller GST Reconciliation: Easy Ship, FBA, and Returns Impact on GSTR-1",
          "url": "https://www.terra-insight.com/insights/amazon-spn-gst-reconciliation-india"
        },
        {
          "q": "How does Amazon's MTR template map to GSTR-1?",
          "a": "The MTR (Merchant Tax Report) is downloadable monthly from Amazon Seller Central under the Reports section. It provides each invoice with invoice number, invoice date, supplier GSTIN, buyer GSTIN (for B2B orders), place of supply, HSN code, taxable value, and the split of CGST, SGST, and IGST. The reconciliation process maps B2B orders to GSTR-1 Table 4A (invoice-wise), intra-state B2C below ₹2.5 lakh to Table 7A (rate-wise aggregate), and inter-state B2C below ₹2.5 lakh to Table 7B (state and rate-wise aggregate). Inter-state B2C above ₹2.5 lakh goes to Table 5A invoice-wise.",
          "article": "Amazon SPN Seller GST Reconciliation: Easy Ship, FBA, and Returns Impact on GSTR-1",
          "url": "https://www.terra-insight.com/insights/amazon-spn-gst-reconciliation-india"
        },
        {
          "q": "How are returns treated for GST purposes on Easy Ship versus FBA?",
          "a": "For Easy Ship, a return flows back to the seller's warehouse. The seller issues a GST credit note to the buyer, reverses output tax in the period the credit note is issued, and reports the credit note in GSTR-1 Table 9B. For FBA, the return goes to Amazon's FC, Amazon raises a settlement adjustment, and the seller still issues the GST credit note to the buyer. The credit note period is the period Amazon confirms the return, not the period of the original sale. A return straddling two months creates a timing difference between output tax reversed in GSTR-3B and the Section 52 TCS reversal that Amazon files in its revised GSTR-8.",
          "article": "Amazon SPN Seller GST Reconciliation: Easy Ship, FBA, and Returns Impact on GSTR-1",
          "url": "https://www.terra-insight.com/insights/amazon-spn-gst-reconciliation-india"
        },
        {
          "q": "What is the Amazon Section 52 TCS treatment for SPN-supported sellers?",
          "a": "Amazon deducts TCS at 1% on the net taxable value of each supply facilitated through its marketplace. For intra-state orders, the split is 0.5% CGST + 0.5% SGST; for inter-state, it is 1% IGST. Amazon files GSTR-8 by the 10th of the following month, populating the seller's GSTR-2B under Amazon's operator GSTIN. The seller claims the TCS in GSTR-3B by adjusting it against output tax liability. Where returns cause a TCS reversal, it appears in a subsequent GSTR-8 and GSTR-2B — the seller must track the reversal to avoid claiming TCS that has been reversed by Amazon.",
          "article": "Amazon SPN Seller GST Reconciliation: Easy Ship, FBA, and Returns Impact on GSTR-1",
          "url": "https://www.terra-insight.com/insights/amazon-spn-gst-reconciliation-india"
        },
        {
          "q": "How does a 3PL like Delhivery or Shadowfax remit COD cash to a D2C brand?",
          "a": "3PL partners collect cash on delivery from the customer and remit the aggregate collection to the brand's bank account on a weekly or bi-weekly cycle depending on the contract. The remittance is net of COD handling charges (typically ₹25 to ₹60 per shipment) and RTO reverse-logistics charges for any returned orders. The remittance advice from the 3PL carries AWB-level detail that must be matched against the brand's order management system. Cycle times commonly run T+5 to T+10 from delivery.",
          "article": "D2C COD vs Prepaid Settlement Reconciliation: 3PL Remittance and Gateway Payouts",
          "url": "https://www.terra-insight.com/insights/d2c-cod-vs-prepaid-settlement-reconciliation-india"
        },
        {
          "q": "What deductions apply on a COD remittance from a 3PL versus a prepaid gateway payout?",
          "a": "COD remittance deductions include forward COD handling fees (₹25 to ₹60 per shipment), RTO reverse-logistics fees (₹40 to ₹80 per undelivered shipment), GST at 18% on both fee lines, and any damage or loss claims raised in the period. Prepaid gateway payout deductions include MDR (1.75% to 2.5% for cards, 0 to 0.4% for UPI), GST on MDR at 18%, and any refunds processed in the cycle. The two flows are accounted against different expense heads and have different ITC implications.",
          "article": "D2C COD vs Prepaid Settlement Reconciliation: 3PL Remittance and Gateway Payouts",
          "url": "https://www.terra-insight.com/insights/d2c-cod-vs-prepaid-settlement-reconciliation-india"
        },
        {
          "q": "How do I reconcile RTO orders in a COD settlement cycle?",
          "a": "An RTO (return to origin) shipment means the customer refused delivery or the 3PL could not deliver. The brand pays forward logistics, reverse logistics, and often COD attempt fees even though no revenue was collected. The 3PL remittance statement deducts both charges against the brand's remittance balance. Reconciliation requires matching each AWB marked RTO to the original order in the OMS, reversing any provisional revenue recognition, booking the logistics loss, and tracking the returned inventory back into stock. RTO rates of 20 to 30 percent are common in COD-heavy apparel categories.",
          "article": "D2C COD vs Prepaid Settlement Reconciliation: 3PL Remittance and Gateway Payouts",
          "url": "https://www.terra-insight.com/insights/d2c-cod-vs-prepaid-settlement-reconciliation-india"
        },
        {
          "q": "What is the typical settlement lag between order placement and cash in bank for D2C COD versus prepaid?",
          "a": "Prepaid orders on Razorpay or PayU settle at T+1 to T+2 from transaction success, so cash lands within 2 to 3 days of the order being placed. COD orders depend first on delivery (usually 2 to 7 days from order), then on the 3PL's remittance cycle (T+5 to T+10 from delivery confirmation). End-to-end, COD cash can lag 10 to 17 days behind order placement. Working capital implications are material for brands with 60 percent or higher COD share.",
          "article": "D2C COD vs Prepaid Settlement Reconciliation: 3PL Remittance and Gateway Payouts",
          "url": "https://www.terra-insight.com/insights/d2c-cod-vs-prepaid-settlement-reconciliation-india"
        },
        {
          "q": "Which accounts does a D2C brand use to separate COD and prepaid revenue?",
          "a": "Standard practice is to maintain separate receivable sub-ledgers — a gateway receivable for prepaid orders that settles against Razorpay or PayU payouts, and a 3PL receivable for COD orders that settles against Delhivery, Shadowfax, or Shiprocket remittance. Each sub-ledger matches independently. Combining them produces aggregate totals that match bank credits in total but leave specific RTO leakage, commission errors, or unremitted cash invisible. Each revenue line also carries different GST treatment on the deduction side.",
          "article": "D2C COD vs Prepaid Settlement Reconciliation: 3PL Remittance and Gateway Payouts",
          "url": "https://www.terra-insight.com/insights/d2c-cod-vs-prepaid-settlement-reconciliation-india"
        },
        {
          "q": "Which payment gateways integrate natively with Magento for India?",
          "a": "Magento 2 and Adobe Commerce support PayU, Razorpay, CCAvenue, and Cashfree through official extensions. PayU's Magento 2 module handles both hosted checkout and seamless integration. Razorpay's Magento extension supports UPI, cards, netbanking, and EMI with standard MDR of 2% for cards, 0 to 0.4% for UPI. Cashfree offers a similar extension with T+1 settlement as the default. For multi-vendor stores running Mirasvit or Webkul marketplace extensions, split settlement requires additional configuration in Razorpay Route or PayU SplitPay.",
          "article": "Magento India Payment Gateway Reconciliation: PayU, Razorpay, Cashfree for Multi-Vendor Stores",
          "url": "https://www.terra-insight.com/insights/magento-payment-gateway-reconciliation-india"
        },
        {
          "q": "How does a marketplace split settlement work on a Magento multi-vendor store?",
          "a": "Razorpay Route and PayU SplitPay allow a single customer transaction to be automatically split across multiple beneficiary accounts at settlement time. The merchant configures each vendor as a linked account with its own bank details and GSTIN. The gateway deducts MDR from the gross amount, then splits the net by commission rule (typically 8 to 20 percent to the marketplace, balance to the vendor). Reconciliation requires matching each payout to the original Magento sub-order line and verifying commission was deducted correctly per the vendor contract tier.",
          "article": "Magento India Payment Gateway Reconciliation: PayU, Razorpay, Cashfree for Multi-Vendor Stores",
          "url": "https://www.terra-insight.com/insights/magento-payment-gateway-reconciliation-india"
        },
        {
          "q": "How is TDS Section 194O applied in a Magento marketplace setup?",
          "a": "If the Magento store operates as an e-commerce operator facilitating sales on behalf of third-party vendors, TDS under Section 194O applies at 1% of the gross sale value (excluding GST) on payments to each vendor, subject to the annual threshold of ₹5 lakh per individual seller. The marketplace operator deducts TDS before releasing the vendor's share and files the deducted amount via quarterly TDS returns. Each vendor then claims the 194O credit in Form 26AS against their tax liability.",
          "article": "Magento India Payment Gateway Reconciliation: PayU, Razorpay, Cashfree for Multi-Vendor Stores",
          "url": "https://www.terra-insight.com/insights/magento-payment-gateway-reconciliation-india"
        },
        {
          "q": "What is the typical settlement cycle for Razorpay and PayU on Magento India?",
          "a": "Razorpay defaults to T+2 for card transactions and T+1 for UPI, with early settlement (T+0) available for an additional fee. PayU operates on T+1 to T+2 depending on merchant category and risk profile. Cashfree's default is T+1. For marketplace split settlements via Razorpay Route, the split occurs at the same T+2 cycle — each vendor receives their share net of commission in a separate settlement batch identifiable by the linked account ID.",
          "article": "Magento India Payment Gateway Reconciliation: PayU, Razorpay, Cashfree for Multi-Vendor Stores",
          "url": "https://www.terra-insight.com/insights/magento-payment-gateway-reconciliation-india"
        },
        {
          "q": "What common errors occur in Magento payment gateway reconciliation?",
          "a": "The three common errors are: matching gateway payout totals at batch level without unpacking to the Magento order line (hides per-order MDR variance), treating refunds as expense in the refund period instead of as revenue reversal against the original sale period (distorts monthly revenue), and missing commission splits for multi-vendor orders where Magento's sub-order IDs do not carry through to the gateway's settlement report (requires mapping via the parent order ID).",
          "article": "Magento India Payment Gateway Reconciliation: PayU, Razorpay, Cashfree for Multi-Vendor Stores",
          "url": "https://www.terra-insight.com/insights/magento-payment-gateway-reconciliation-india"
        },
        {
          "q": "How does Blinkit, Zepto, or Swiggy Instamart settle payments to FMCG brands?",
          "a": "Quick-commerce platforms operate on a wholesale inventory model — the platform purchases goods from the brand at a negotiated margin off MRP (typically 18 to 30 percent below MRP depending on category), stocks them at dark stores, and sells at MRP to end customers. The brand issues a tax invoice to the platform at the wholesale price, the platform pays on a settlement cycle (typically T+15 to T+30 from PO receipt), and the platform handles its own customer settlements independently. Brands reconcile against the platform's purchase orders and payment advices, not against consumer-level orders.",
          "article": "Quick Commerce Seller Reconciliation for Blinkit, Zepto, and Swiggy Instamart",
          "url": "https://www.terra-insight.com/insights/quick-commerce-seller-reconciliation-blinkit-zepto-india"
        },
        {
          "q": "What deductions appear in a quick-commerce platform's payment to an FMCG brand?",
          "a": "The primary deductions from a brand's invoice value are: trade promotion spend netted at source (scheme discounts agreed with the platform buyer), damage or short-receipt deductions reported at the dark-store receiving bay, return deductions for products near expiry pulled from shelves, TDS at 0.1% under Section 194Q if the platform's annual purchases from the brand exceed ₹50 lakh, and any penalty charges for late delivery or fill-rate misses. Each deduction is documented in the platform's payment advice and must be reconciled to the brand's credit-note ledger.",
          "article": "Quick Commerce Seller Reconciliation for Blinkit, Zepto, and Swiggy Instamart",
          "url": "https://www.terra-insight.com/insights/quick-commerce-seller-reconciliation-blinkit-zepto-india"
        },
        {
          "q": "Does TCS Section 52 apply to quick-commerce platforms?",
          "a": "TCS under Section 52 of the CGST Act applies when the platform acts as an e-commerce operator facilitating the supply of goods between a third-party seller and the end customer. In the wholesale inventory model used by Blinkit, Zepto, and Swiggy Instamart for their direct-buy categories, the platform is the seller of record to the customer — Section 52 TCS does not apply to that leg. For categories where the platform operates as a marketplace (less common for FMCG but present for specialty SKUs), TCS at 1% on the net taxable value applies and appears in the brand's GSTR-2B via the operator's GSTR-8.",
          "article": "Quick Commerce Seller Reconciliation for Blinkit, Zepto, and Swiggy Instamart",
          "url": "https://www.terra-insight.com/insights/quick-commerce-seller-reconciliation-blinkit-zepto-india"
        },
        {
          "q": "What is the typical commission or margin structure across quick-commerce platforms in India?",
          "a": "Margin expectations from quick-commerce platforms vary by category: staples and commodities typically run 15 to 22 percent off MRP, personal care and home care 22 to 30 percent, and impulse or premium SKUs 25 to 35 percent. Payment terms are usually 30 to 45 days from invoice for FMCG brands. Brands must track these margins per SKU per platform in the reconciliation layer — a 2 percent margin error on a fast-moving SKU across 200 dark stores compounds to material receivable variance within a quarter.",
          "article": "Quick Commerce Seller Reconciliation for Blinkit, Zepto, and Swiggy Instamart",
          "url": "https://www.terra-insight.com/insights/quick-commerce-seller-reconciliation-blinkit-zepto-india"
        },
        {
          "q": "How do I reconcile damage and short-receipt deductions on a quick-commerce platform?",
          "a": "Damage and short-receipt deductions are raised by the platform at the dark-store receiving dock when goods arrive damaged, under-quantity, or past the accepted shelf-life buffer. Each deduction is linked to a specific PO and invoice line and appears as a credit note or payment advice adjustment. Reconciliation requires matching each deduction to the original PO, validating the damage quantity against the dispatch manifest, and booking an inventory write-off or insurance claim entry. Brands routinely see 0.5 to 2 percent of GMV absorbed as damage deductions across quick-commerce platforms.",
          "article": "Quick Commerce Seller Reconciliation for Blinkit, Zepto, and Swiggy Instamart",
          "url": "https://www.terra-insight.com/insights/quick-commerce-seller-reconciliation-blinkit-zepto-india"
        },
        {
          "q": "How is SGST versus IGST determined on a Shopify storefront order in India?",
          "a": "Under Section 10 of the IGST Act, the tax split is determined by the ship-to state on the order. If the customer's shipping address is in the same state as the seller's registered place of business, the order carries 9% CGST + 9% SGST (for 18% GST goods). If the ship-to state is different, the full 18% is collected as IGST. Shopify's tax engine computes this at checkout, but the Shopify order export does not always label the split clearly — finance teams must derive SGST versus IGST from the ship-to state field before filing GSTR-1.",
          "article": "Shopify India GST Reconciliation: SGST, IGST, and Gateway Payout Matching",
          "url": "https://www.terra-insight.com/insights/shopify-india-gst-reconciliation"
        },
        {
          "q": "How is GST applied to shipping charges on a Shopify order?",
          "a": "GST on shipping follows the composite supply rule under Section 8 of the CGST Act. If the order contains goods taxed at 18%, the shipping charge is also taxed at 18% as part of the same composite supply. For mixed-rate carts, Shopify applies the highest rate to the shipping line by default. The SGST versus IGST split on the shipping GST follows the same ship-to state rule as the goods themselves.",
          "article": "Shopify India GST Reconciliation: SGST, IGST, and Gateway Payout Matching",
          "url": "https://www.terra-insight.com/insights/shopify-india-gst-reconciliation"
        },
        {
          "q": "How do I reconcile a Razorpay or PayU payout against Shopify orders?",
          "a": "Each gateway payout is a net figure — gross order value minus MDR (typically 1.75% to 2.5% for cards, 0% to 0.4% for UPI), platform fees, and any refunds processed in the cycle. Reconciliation requires matching each payout transaction in the gateway report to the corresponding Shopify order ID, reconstructing gross revenue, and booking the MDR as an expense with 18% GST claimable as ITC. The gateway's GST invoice for MDR is the source document for that ITC claim.",
          "article": "Shopify India GST Reconciliation: SGST, IGST, and Gateway Payout Matching",
          "url": "https://www.terra-insight.com/insights/shopify-india-gst-reconciliation"
        },
        {
          "q": "What is the settlement cycle for Razorpay and PayU on Shopify stores?",
          "a": "Razorpay's default settlement cycle is T+2 for card payments and T+1 for UPI, with early settlement available at an additional fee. PayU operates on T+1 to T+2 depending on the merchant category code and risk profile. Cashfree's default is T+1. Each cycle includes all successful transactions in the preceding window net of refunds processed in the same period. The bank credit reference narration typically carries the gateway's merchant ID and settlement batch reference.",
          "article": "Shopify India GST Reconciliation: SGST, IGST, and Gateway Payout Matching",
          "url": "https://www.terra-insight.com/insights/shopify-india-gst-reconciliation"
        },
        {
          "q": "What are the most common GST reconciliation errors for Shopify India sellers?",
          "a": "The three recurring errors are: applying a single tax rate across all orders without deriving SGST versus IGST by ship-to state (produces GSTR-1 place-of-supply mismatches), treating the gateway net payout as revenue instead of grossing up for MDR and GST (understates output tax and ITC claimable), and missing refund-period reversals when a Q1 order is refunded in Q2 (leaves output tax overstated). Each error compounds monthly if the reconciliation is done on net payouts rather than order-level data.",
          "article": "Shopify India GST Reconciliation: SGST, IGST, and Gateway Payout Matching",
          "url": "https://www.terra-insight.com/insights/shopify-india-gst-reconciliation"
        }
      ]
    },
    "payment-gateway": {
      "label": "Payment Gateway and Platform Settlements",
      "faqs": [
        {
          "q": "What is TCS in Amazon marketplace settlement and how is it reconciled?",
          "a": "Amazon deducts TCS (Tax Collected at Source) at 1% of the net taxable value of each transaction from marketplace seller payouts under Section 52 of the CGST Act (0.5% CGST + 0.5% SGST for intra-state transactions, or 1% IGST for inter-state). Amazon files GSTR-8 by the 10th of the following month, and this data auto-populates in the seller's GSTR-2B. Sellers must reconcile TCS shown in the Amazon settlement report against GSTR-2B Part II (TCS amounts) and Form 26AS Part F each quarter. Any mismatch must be resolved before crediting TCS against output liability.",
          "article": "Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts",
          "url": "https://www.terra-insight.com/insights/amazon-pay-settlement-reconciliation"
        },
        {
          "q": "What is Amazon Pay's settlement cycle for marketplace sellers in India?",
          "a": "Amazon India marketplace settlements for sellers follow a weekly cycle, typically 7 days after the order shipment confirmation date, subject to Amazon's payment hold policies for new sellers. The settlement includes sales proceeds minus Amazon's referral fee, fulfilment fees (for FBA sellers), advertising charges, return adjustments, and 1% TCS. Settlement timing differs from pure payment gateway products like Razorpay (T+2) due to the marketplace's additional deduction structure.",
          "article": "Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts",
          "url": "https://www.terra-insight.com/insights/amazon-pay-settlement-reconciliation"
        },
        {
          "q": "How does Amazon Pay as a payment method on external websites differ from marketplace settlement?",
          "a": "When Amazon Pay is used as a checkout option on a non-Amazon website (Amazon Pay for external merchants), it operates as a standard payment gateway: T+2 settlement, MDR deducted, GST on MDR charged at 18%, settlement report available in the Amazon Pay dashboard. TCS under Section 52 does not apply because the external merchant is not selling through Amazon's marketplace platform. The reconciliation is structurally identical to Razorpay or PayU settlement reconciliation.",
          "article": "Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts",
          "url": "https://www.terra-insight.com/insights/amazon-pay-settlement-reconciliation"
        },
        {
          "q": "Where does Amazon TCS appear in GST returns and compliance filings?",
          "a": "TCS collected by Amazon under Section 52 appears in: (1) the seller's Amazon settlement report as a line item deduction, (2) the seller's GSTR-2B Part II after Amazon files GSTR-8 by the 10th of the following month, and (3) the seller's Form 26AS Part F. Sellers claim TCS as a credit against their GST output liability in GSTR-3B. The TCS amount in GSTR-3B must match GSTR-2B exactly — over-claiming based on the settlement report before GSTR-8 is filed is a compliance error.",
          "article": "Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts",
          "url": "https://www.terra-insight.com/insights/amazon-pay-settlement-reconciliation"
        },
        {
          "q": "What exceptions appear in Amazon marketplace settlement reconciliation?",
          "a": "Amazon marketplace settlement exceptions include: TAX_DEDUCTION when TCS in the settlement report differs from GSTR-2B (timing mismatch if GSTR-8 has not yet been filed), FEE_DEDUCTION when referral fee percentage applied differs from the category rate, PARTIAL_PAYMENT when a return adjustment reduces a settlement without a traceable order ID in the OMS, ROUNDING on sub-rupee fee calculations, and UNEXPLAINED when a settlement credit cannot be matched to any order in the seller's system.",
          "article": "Amazon Pay Settlement Reconciliation: Marketplace TCS, MDR, and Weekly Payouts",
          "url": "https://www.terra-insight.com/insights/amazon-pay-settlement-reconciliation"
        },
        {
          "q": "Does Cashfree Payments offer T+1 settlement as standard?",
          "a": "Yes. Cashfree offers T+1 settlement — settlement initiated one working day after payment capture — as a standard feature for eligible merchants, without additional fees. This differs from Razorpay and PayU, where T+1 is typically available on request or for established merchants only. T+2 is available as a fallback. Merchant eligibility for T+1 depends on Cashfree's risk assessment.",
          "article": "Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling",
          "url": "https://www.terra-insight.com/insights/cashfree-settlement-reconciliation"
        },
        {
          "q": "What is the settlement_id in Cashfree and how does it work in reconciliation?",
          "a": "Cashfree assigns a settlement_id to each settlement batch, visible in the Cashfree Dashboard under the Settlements section. The settlement report CSV contains the settlement_id, settlement date, and net amount alongside individual transaction rows. The settlement_id is used to match the Cashfree settlement batch to the corresponding NEFT credit in the bank statement. The bank narration will typically show a Cashfree nodal account reference with a UTR.",
          "article": "Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling",
          "url": "https://www.terra-insight.com/insights/cashfree-settlement-reconciliation"
        },
        {
          "q": "How is MDR GST handled in Cashfree settlement reconciliation?",
          "a": "Cashfree charges MDR on transactions (0% for UPI, approximately 1.5–2% for cards depending on plan) and applies 18% GST on the MDR. Cashfree issues a monthly GST invoice to the merchant's registered GSTIN. The GST on MDR amount in the settlement report should match the invoice total for the corresponding period. GST-registered merchants can claim ITC on this amount after matching the invoice in GSTR-2B.",
          "article": "Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling",
          "url": "https://www.terra-insight.com/insights/cashfree-settlement-reconciliation"
        },
        {
          "q": "What is Cashfree Payouts and does it need separate reconciliation?",
          "a": "Cashfree Payouts is a separate product for bulk disbursements — vendor payments, refunds, salary transfers, and similar outgoing transactions. It is distinct from Cashfree Payments (the collection/gateway product). Payouts reconciliation matches outgoing transfer records in the Cashfree Payouts dashboard to debit entries in the merchant's bank account and to the corresponding liability or expense in the ERP. These two reconciliation tracks should not be combined.",
          "article": "Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling",
          "url": "https://www.terra-insight.com/insights/cashfree-settlement-reconciliation"
        },
        {
          "q": "What are the most common exceptions in Cashfree settlement reconciliation?",
          "a": "Common exceptions in Cashfree settlement reconciliation: FEE_DEDUCTION when the MDR applied differs from the agreed rate by instrument; TAX_DEDUCTION when the GST on MDR in the settlement report does not match the monthly invoice; PARTIAL_PAYMENT when a refund processed through Cashfree reduces the gross-to-net bridge but the originating Order ID falls in a different accounting period; and UNEXPLAINED when a transaction in the settlement report has no match in the OMS, which may indicate a test-mode payment that was not filtered.",
          "article": "Cashfree Settlement Reconciliation: T+1 Payouts and Exception Handling",
          "url": "https://www.terra-insight.com/insights/cashfree-settlement-reconciliation"
        },
        {
          "q": "How long does a merchant have to respond to a chargeback in India?",
          "a": "The dispute window given by the acquiring bank or payment gateway is typically 5–10 business days from the date of chargeback notification. The underlying card network rules (Visa and Mastercard) allow cardholders to raise chargebacks within 120 days of the original transaction date.",
          "article": "Chargeback reconciliation in India — matching disputes, deductions, and representment",
          "url": "https://www.terra-insight.com/insights/chargeback-reconciliation-india"
        },
        {
          "q": "What is the difference between a chargeback and a refund in a settlement report?",
          "a": "A refund is initiated by the merchant and appears as a negative line item labelled with the original payment_id or order_id. A chargeback is initiated by the cardholder's issuing bank and appears as a separate deduction — often without a direct reference to the original order — requiring manual matching to identify the source transaction.",
          "article": "Chargeback reconciliation in India — matching disputes, deductions, and representment",
          "url": "https://www.terra-insight.com/insights/chargeback-reconciliation-india"
        },
        {
          "q": "What happens if a merchant loses a chargeback dispute in India?",
          "a": "If the merchant's representment (counter-dispute with evidence) is rejected, the chargeback amount is permanently debited from the merchant's settlement account. There is no further appeal through the gateway — the loss is final and must be written off in the books.",
          "article": "Chargeback reconciliation in India — matching disputes, deductions, and representment",
          "url": "https://www.terra-insight.com/insights/chargeback-reconciliation-india"
        },
        {
          "q": "Does a chargeback trigger a GST credit note obligation?",
          "a": "Not automatically. A chargeback is a forced reversal of payment, not a return of goods. Whether a credit note is required depends on whether the underlying supply was reversed. If the goods were returned or the service was not rendered, a credit note under Section 34 of the CGST Act is required. If the chargeback was fraudulent and the merchant disputes it, no credit note is issued.",
          "article": "Chargeback reconciliation in India — matching disputes, deductions, and representment",
          "url": "https://www.terra-insight.com/insights/chargeback-reconciliation-india"
        },
        {
          "q": "How many settlement reports should a merchant reconcile for chargebacks?",
          "a": "A merchant using a single payment gateway receives one settlement file per settlement cycle (typically daily or T+2). Multi-gateway merchants — for example, running Razorpay for UPI and PayU for credit cards — must reconcile chargeback deductions across both files separately, since chargebacks appear only in the gateway that processed the original transaction.",
          "article": "Chargeback reconciliation in India — matching disputes, deductions, and representment",
          "url": "https://www.terra-insight.com/insights/chargeback-reconciliation-india"
        },
        {
          "q": "What deductions does Flipkart make before releasing a seller's weekly settlement?",
          "a": "Flipkart deducts marketplace commission (which varies by category — typically 5–20%), TCS at 1% under GST Section 52, return adjustments for orders reversed in the settlement period, and shipping charges where applicable. The bank credit is the net amount after all four deductions. A seller must reconstruct gross sales from this net figure before filing GSTR-3B.",
          "article": "Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns",
          "url": "https://www.terra-insight.com/insights/flipkart-seller-settlement-reconciliation"
        },
        {
          "q": "What is the TCS rate Flipkart deducts and where does the credit appear?",
          "a": "Flipkart deducts TCS at 1% of the net taxable value of supplies. For intra-state orders it is 0.5% CGST + 0.5% SGST; for inter-state orders it is 1% IGST. Flipkart files GSTR-8 by the 10th of the following month, which auto-populates the seller's GSTR-2B. The credit also appears in Form 26AS Part F under the seller's PAN.",
          "article": "Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns",
          "url": "https://www.terra-insight.com/insights/flipkart-seller-settlement-reconciliation"
        },
        {
          "q": "What is Flipkart's standard settlement cycle for sellers?",
          "a": "Flipkart's standard settlement cycle is T+7 — seven days from delivery confirmation in standard categories. The seller receives a weekly bank credit covering all orders confirmed delivered in that window. Settlement reports are downloadable from Flipkart Seller Hub with order-level detail including each deduction line.",
          "article": "Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns",
          "url": "https://www.terra-insight.com/insights/flipkart-seller-settlement-reconciliation"
        },
        {
          "q": "How do I reconcile return deductions in a Flipkart settlement?",
          "a": "Return deductions appear when customers return items during a settlement cycle. Flipkart nets the return credit against forward sales in the same settlement period. To reconcile correctly, the seller must match each return order ID in the settlement report to the original forward sale in their ERP, reverse the revenue recognition, and check whether TCS was already credited to GSTR-2B for the original transaction — if so, that TCS must also be reversed via GSTR-3B in the period the return credit appears.",
          "article": "Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns",
          "url": "https://www.terra-insight.com/insights/flipkart-seller-settlement-reconciliation"
        },
        {
          "q": "What is a variance taxonomy for Flipkart settlement reconciliation?",
          "a": "The three standard variance types in Flipkart reconciliation are: FEE_DEDUCTION (marketplace commission and shipping charges that differ from the fee schedule), TAX_DEDUCTION (TCS amount that does not match gross taxable value at 1%), and ROUNDING (sub-rupee differences created by per-order rounding in Flipkart's payout calculation). Each type requires a different resolution path — fee disputes go to Seller Hub, tax mismatches go to GSTR-8 correction, and rounding is written off below a materiality threshold.",
          "article": "Flipkart Seller Settlement Reconciliation: TCS, Fees, and Returns",
          "url": "https://www.terra-insight.com/insights/flipkart-seller-settlement-reconciliation"
        },
        {
          "q": "How much revenue do sellers typically lose to marketplace fee errors?",
          "a": "Industry analysis indicates sellers lose 2-3% of gross payment volume to fee-related errors. For a seller with ₹5 crore monthly GMV, this translates to ₹10-15 lakh annually. The most common sources are commission category misclassification, volumetric weight overcharges, and incomplete fee reversals on returned orders.",
          "article": "Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports",
          "url": "https://www.terra-insight.com/insights/marketplace-fee-audit-reconciliation-india"
        },
        {
          "q": "How do I file a SAFE-T claim on Amazon India?",
          "a": "SAFE-T claims must be filed within 90 days of the disputed transaction through Seller Central. Amazon sends information requests with a 3-day response window. If the claim is denied, sellers have one appeal within 7 days. Note that an active A-to-Z guarantee claim on the same order blocks SAFE-T filing until the A-to-Z claim is resolved.",
          "article": "Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports",
          "url": "https://www.terra-insight.com/insights/marketplace-fee-audit-reconciliation-india"
        },
        {
          "q": "What is the settlement cycle for Flipkart sellers?",
          "a": "Flipkart settlement cycles depend on the seller tier: Platinum sellers receive settlements at T+5, Gold at T+7, Silver at T+10, and Bronze at T+15 business days. Following the 2025 pricing update, Flipkart determines the final selling price in certain categories, which means the commission structure is applied to a marketplace-determined base rather than the seller's listed MRP.",
          "article": "Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports",
          "url": "https://www.terra-insight.com/insights/marketplace-fee-audit-reconciliation-india"
        },
        {
          "q": "How should TCS on marketplace settlements be verified?",
          "a": "TCS under Section 52 of the CGST Act must be computed on the net value of taxable supplies, excluding GST. Sellers should verify that TCS is not being computed on the gross settlement amount including GST. Additionally, the intra-state and inter-state split must match actual delivery addresses, not the seller's registered address. Cross-reference TCS credits in Form 26AS against the marketplace TCS certificate quarterly.",
          "article": "Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports",
          "url": "https://www.terra-insight.com/insights/marketplace-fee-audit-reconciliation-india"
        },
        {
          "q": "Why do manual VLOOKUP audits miss marketplace fee errors?",
          "a": "Manual VLOOKUP matching against settlement reports achieves approximately 51% match rate because marketplace settlements arrive as lump-sum bank credits covering thousands of orders, with deductions for commission, shipping, TCS, and returns netted at the line-item level. Order-level matching requires unpacking each settlement row into its constituent fee components and matching against the original order, which VLOOKUP cannot do without extensive preprocessing.",
          "article": "Marketplace Fee Audit: Identifying Revenue Leakage in E-Commerce Settlement Reports",
          "url": "https://www.terra-insight.com/insights/marketplace-fee-audit-reconciliation-india"
        },
        {
          "q": "What is MDR in payment gateway settlement, and how is it calculated?",
          "a": "MDR (Merchant Discount Rate) is the fee charged by the payment gateway for processing each transaction. It is calculated as a percentage of the transaction value for card transactions (typically 1.5%–2.5% for credit cards, varying for debit cards) or as a flat fee for net banking (typically ₹10–₹25 per transaction). The MDR is deducted from the settlement amount before the net proceeds are credited to the merchant.",
          "article": "MDR fee reconciliation — verifying gateway charges against contracted rates",
          "url": "https://www.terra-insight.com/insights/mdr-fee-reconciliation"
        },
        {
          "q": "Is GST charged on MDR in India, and can merchants claim ITC on it?",
          "a": "Yes. GST at 18% is charged on MDR, making the effective cost MDR × 1.18. For example, a 2% MDR on a transaction becomes an effective charge of 2.36% including GST. Merchants registered under GST can claim the 18% GST component as Input Tax Credit (ITC) on their GSTR-3B, provided the gateway issues a valid GST invoice or tax deduction statement.",
          "article": "MDR fee reconciliation — verifying gateway charges against contracted rates",
          "url": "https://www.terra-insight.com/insights/mdr-fee-reconciliation"
        },
        {
          "q": "What is the MDR rate for UPI transactions in India?",
          "a": "As per RBI guidelines, UPI P2M (person-to-merchant) transactions up to ₹2,000 attract 0% MDR. For higher UPI transaction amounts, MDR may apply depending on the gateway and the merchant's plan. Merchants should verify their specific MDR schedule for UPI in their gateway contract, as rates above the zero-MDR threshold vary by provider.",
          "article": "MDR fee reconciliation — verifying gateway charges against contracted rates",
          "url": "https://www.terra-insight.com/insights/mdr-fee-reconciliation"
        },
        {
          "q": "What is the variance type FEE_DEDUCTION in MDR reconciliation?",
          "a": "FEE_DEDUCTION is the exception type raised when the actual MDR deducted in the settlement does not match the expected MDR calculated from the contracted rate and transaction type. The most common cause is a transaction being billed at the credit card rate (1.5%–2.5%) when it was processed using a debit card (which may have a different contracted rate). FEE_DEDUCTION exceptions require verification with the gateway and, if confirmed, a fee adjustment credit.",
          "article": "MDR fee reconciliation — verifying gateway charges against contracted rates",
          "url": "https://www.terra-insight.com/insights/mdr-fee-reconciliation"
        },
        {
          "q": "How should a merchant verify MDR billing for international card transactions?",
          "a": "International card transactions are billed at a higher MDR than domestic cards — typically 2.5%–3.5% depending on the gateway and card type. The reconciliation must identify each international card transaction in the settlement report (usually flagged by card country code or network identifier) and verify that the MDR applied matches the international rate in the merchant's gateway agreement, not the domestic card rate.",
          "article": "MDR fee reconciliation — verifying gateway charges against contracted rates",
          "url": "https://www.terra-insight.com/insights/mdr-fee-reconciliation"
        },
        {
          "q": "What deductions does Meesho make from a seller's weekly settlement?",
          "a": "Meesho's advertised commission rate is 0%, but sellers incur logistics charges (typically ₹30–80 per shipment depending on weight and zone), return shipping charges, and TCS at 1% under GST Section 52. In high-return-rate categories, return logistics charges can exceed forward logistics charges in a given week, resulting in a net negative settlement that Meesho carries forward as a debit against the next week's payout.",
          "article": "Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions",
          "url": "https://www.terra-insight.com/insights/meesho-seller-reconciliation"
        },
        {
          "q": "How does TCS work on returned orders for Meesho sellers?",
          "a": "TCS is deducted on the original forward sale at the time of settlement, not on the net amount after returns. If a seller sells ₹50,000 worth of goods in a week and ₹20,000 worth are returned, TCS of ₹500 (1% on ₹50,000) was already deducted and appears in GSTR-2B. Meesho issues a TCS reversal for the returned ₹20,000 in a subsequent settlement cycle and files a revised GSTR-8, which then generates a correcting entry in GSTR-2B.",
          "article": "Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions",
          "url": "https://www.terra-insight.com/insights/meesho-seller-reconciliation"
        },
        {
          "q": "What is a negative settlement on Meesho and how should it be accounted for?",
          "a": "A negative Meesho settlement occurs when return deductions, return logistics charges, and penalties in a given week exceed forward sales for that same period. The negative balance does not result in a debit to the seller's bank account — Meesho carries it forward and deducts it from the next positive settlement. The seller must record this as a receivable reduction in their books and not recognise the deferred deduction as current-period expense until it is actually netted in the subsequent settlement.",
          "article": "Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions",
          "url": "https://www.terra-insight.com/insights/meesho-seller-reconciliation"
        },
        {
          "q": "Where does Meesho TCS credit appear and how is it claimed?",
          "a": "Meesho files GSTR-8 by the 10th of the following month, which auto-populates the seller's GSTR-2B with the TCS credit under Meesho's operator GSTIN. The seller claims the credit in GSTR-3B by adjusting it against output tax liability for the period. For intra-state supplies, the credit splits as 0.5% CGST + 0.5% SGST; for inter-state, it is 1% IGST. The credit also appears in Form 26AS Part F.",
          "article": "Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions",
          "url": "https://www.terra-insight.com/insights/meesho-seller-reconciliation"
        },
        {
          "q": "What is the variance taxonomy for Meesho seller reconciliation?",
          "a": "The three variance types that recur in Meesho reconciliation are: FEE_DEDUCTION (logistics charges that differ from Meesho's published rate card — typically due to weight discrepancy disputes), TAX_DEDUCTION (TCS amount in GSTR-2B that does not match calculated TCS on gross forward sales net of accepted returns), and ROUNDING (sub-rupee differences in per-order payout calculations). Each variance type is resolved through a different process: rate disputes via Meesho seller support, TCS discrepancies via GSTR-8 revision request, and rounding via materiality write-off.",
          "article": "Meesho Seller Reconciliation: Handling High Return Rates and TCS Deductions",
          "url": "https://www.terra-insight.com/insights/meesho-seller-reconciliation"
        },
        {
          "q": "What is PayU's settlement cycle for Indian merchants?",
          "a": "PayU India's standard settlement cycle is T+2 working days from the payment capture date. Settlement timelines may vary by merchant category and risk profile. For HDFC SmartGateway and other bank-powered checkout solutions that use PayU's underlying infrastructure, the settlement timeline is governed by the bank's agreement with the merchant, which typically mirrors T+2.",
          "article": "PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts",
          "url": "https://www.terra-insight.com/insights/payu-settlement-reconciliation"
        },
        {
          "q": "How do I find the settlement_id in PayU reconciliation?",
          "a": "The PayU Dashboard (PayU Biz portal) includes a Settlements section where you can download settlement reports by date range. Each report includes a settlement_id field, the settlement date, the net amount credited, and transaction-level details including Payment ID, Order ID, gross amount, MDR, and GST on MDR. The settlement_id is the key for matching the downloaded report to the NEFT credit in the bank statement.",
          "article": "PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts",
          "url": "https://www.terra-insight.com/insights/payu-settlement-reconciliation"
        },
        {
          "q": "What MDR rates does PayU charge on different payment instruments?",
          "a": "PayU MDR rates vary by instrument: UPI transactions carry 0% MDR (government mandate for person-to-merchant UPI); domestic debit cards are typically 0.4–0.9% depending on the merchant's plan; domestic credit cards range from 1.5–2.5%; and international cards may attract up to 3.5%. Each instrument's MDR is applied separately, and GST at 18% is charged on each MDR amount.",
          "article": "PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts",
          "url": "https://www.terra-insight.com/insights/payu-settlement-reconciliation"
        },
        {
          "q": "Does PayU handle BNPL through LazyPay and how does it affect settlement reconciliation?",
          "a": "LazyPay, PayU's BNPL product, processes transactions where the customer's obligation is deferred. From a merchant settlement perspective, the PayU settlement credit arrives on the same T+2 cycle as card payments — LazyPay absorbs the deferred risk, not the merchant. In the settlement report, LazyPay transactions are identifiable by instrument type. Reconciliation logic should classify these separately to correctly attribute fee structures.",
          "article": "PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts",
          "url": "https://www.terra-insight.com/insights/payu-settlement-reconciliation"
        },
        {
          "q": "What causes a mismatch in PayU settlement reconciliation?",
          "a": "Common mismatches in PayU settlement reconciliation include: MDR rate applied differing from the contracted rate (FEE_DEDUCTION), GST on MDR variance between settlement file and PayU's tax invoice (TAX_DEDUCTION), refund deductions where the original Order ID is not in the current system scope (PARTIAL_PAYMENT), and sub-rupee fee rounding (ROUNDING). A PayU settlement credit appearing in the bank with no matching settlement_id in the report typically indicates a date boundary issue in the report export range.",
          "article": "PayU Settlement Reconciliation: Matching Nodal Bank Credits to Transaction-Level Payouts",
          "url": "https://www.terra-insight.com/insights/payu-settlement-reconciliation"
        },
        {
          "q": "What is the Razorpay settlement cycle in India?",
          "a": "Razorpay's standard settlement cycle is T+2 working days from the payment capture date. Merchants with a strong transaction history and low chargeback rates may request T+1 settlement. Settlements are initiated at a fixed cut-off time each business day; payments captured after the cut-off are included in the next day's batch.",
          "article": "Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders",
          "url": "https://www.terra-insight.com/insights/razorpay-settlement-reconciliation"
        },
        {
          "q": "What is the settlement_id in Razorpay and how is it used in reconciliation?",
          "a": "The settlement_id is a unique identifier Razorpay assigns to each settlement batch. It appears in the Razorpay Dashboard settlement report and is the primary match key for linking individual transaction rows in the report to the corresponding NEFT credit in the bank statement. Without matching on settlement_id, a finance team cannot reliably link a bank credit to its component orders.",
          "article": "Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders",
          "url": "https://www.terra-insight.com/insights/razorpay-settlement-reconciliation"
        },
        {
          "q": "How does MDR GST work in Razorpay settlements?",
          "a": "Razorpay charges MDR — typically 2% for standard card transactions — and applies 18% GST on that MDR amount. On a ₹10,000 transaction: MDR = ₹200, GST on MDR = ₹36, net settlement = ₹9,764. Razorpay issues a monthly GST invoice for the MDR charged. GST-registered merchants can claim ITC on the GST on MDR component.",
          "article": "Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders",
          "url": "https://www.terra-insight.com/insights/razorpay-settlement-reconciliation"
        },
        {
          "q": "What exception codes appear in Razorpay settlement reconciliation?",
          "a": "Common exceptions in Razorpay settlement reconciliation include: FEE_DEDUCTION (MDR difference between expected rate and actual rate charged), TAX_DEDUCTION (GST on MDR variance), ROUNDING (sub-rupee rounding in fee calculation), PARTIAL_PAYMENT (refund adjustments reducing the gross-to-net bridge), and UNEXPLAINED (settlement reference present in the bank credit but not found in the order system).",
          "article": "Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders",
          "url": "https://www.terra-insight.com/insights/razorpay-settlement-reconciliation"
        },
        {
          "q": "How do refunds appear in Razorpay settlement reports?",
          "a": "Refunds processed through Razorpay are deducted from future settlement batches rather than paid out as a separate debit. In the settlement report, a refund appears as a negative amount against the original Order ID. The net settlement transferred to the bank account is the gross batch amount minus total MDR, GST on MDR, and refund deductions. Refund timing varies: the deduction from settlement typically occurs within 5–7 working days of the refund initiation.",
          "article": "Razorpay Settlement Reconciliation: Unpacking Net Payouts to Individual Orders",
          "url": "https://www.terra-insight.com/insights/razorpay-settlement-reconciliation"
        },
        {
          "q": "How long does a payment gateway refund take to reach the customer in India?",
          "a": "The standard refund timeline for Razorpay, PayU, and Cashfree is 5–7 business days from the date the merchant initiates the refund. The refund first appears as a deduction in the merchant's next settlement cycle, then reaches the customer's bank within the 5–7 day window. UPI refunds may process faster — typically 2–3 business days.",
          "article": "Refund reconciliation for payment gateways — matching deductions to credit notes",
          "url": "https://www.terra-insight.com/insights/refund-reconciliation-payment-gateway"
        },
        {
          "q": "Is a credit note mandatory for every payment gateway refund under GST?",
          "a": "Yes, where the original supply was GST-inclusive. Section 34 of the CGST Act requires a credit note when a registered supplier reduces the value of a supply already invoiced. The credit note must be issued by 30 November of the financial year following the year of the original supply, or the date of filing the annual return (GSTR-9), whichever is earlier.",
          "article": "Refund reconciliation for payment gateways — matching deductions to credit notes",
          "url": "https://www.terra-insight.com/insights/refund-reconciliation-payment-gateway"
        },
        {
          "q": "What ITC reversal is required when a GST-inclusive sale is refunded?",
          "a": "The ITC claimed on the inputs attributable to that supply must be reversed proportionally to the refund amount. For a full refund, the entire ITC on that transaction is reversed. For a partial refund — for example, a single item return from a multi-item order — only the ITC attributable to the returned items is reversed. The reversal is reported in Table 4B(2) of GSTR-3B.",
          "article": "Refund reconciliation for payment gateways — matching deductions to credit notes",
          "url": "https://www.terra-insight.com/insights/refund-reconciliation-payment-gateway"
        },
        {
          "q": "How should partial refunds be matched in the settlement report?",
          "a": "Partial refunds appear in the settlement report as negative adjustments linked to the original payment_id or order_id, with the partial amount. The reconciliation must split the original order line: the refunded portion is matched to the credit note and ITC reversal, while the retained portion remains as revenue with the original ITC intact. Many ERP systems require a manual line split at this step.",
          "article": "Refund reconciliation for payment gateways — matching deductions to credit notes",
          "url": "https://www.terra-insight.com/insights/refund-reconciliation-payment-gateway"
        },
        {
          "q": "What happens if a gateway initiates a refund without merchant approval?",
          "a": "Gateway-initiated refunds occur for failed transactions — where payment was captured but the order was not fulfilled due to a technical failure. These appear as automatic deductions in the settlement. The merchant must still issue a credit note for GST purposes if a tax invoice was raised, even if the refund was not merchant-initiated. GSTR-3B must reflect the ITC reversal in the same return period.",
          "article": "Refund reconciliation for payment gateways — matching deductions to credit notes",
          "url": "https://www.terra-insight.com/insights/refund-reconciliation-payment-gateway"
        },
        {
          "q": "How do Indian businesses match a Stripe payout to their bank statement?",
          "a": "The primary match key is the Stripe payout_id, which appears in the Stripe dashboard payout detail and in the bank statement narration for SWIFT credits, typically in the payment reference or remittance information field. Standard settlement cycles from Stripe to Indian bank accounts are T+2 to T+7 depending on the payout schedule. For NEFT credits, the UTR number in the bank statement provides a secondary match key once the payout_id is located.",
          "article": "Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching",
          "url": "https://www.terra-insight.com/insights/stripe-india-settlement-reconciliation"
        },
        {
          "q": "Why does a forex rate difference arise in Stripe India settlements?",
          "a": "Indian businesses invoicing international customers in USD or EUR record the receivable at the exchange rate on the invoice date. Stripe settles the payout to the Indian bank account at Stripe's prevailing conversion rate on the settlement date, which differs from both the invoice date rate and the RBI reference rate. The difference between the booked receivable and the INR amount actually credited is a foreign exchange gain or loss that must be classified and accounted for — it is not a fee or error.",
          "article": "Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching",
          "url": "https://www.terra-insight.com/insights/stripe-india-settlement-reconciliation"
        },
        {
          "q": "What is FIRC and why does Stripe India settlement require it?",
          "a": "A Foreign Inward Remittance Certificate (FIRC) is issued by the receiving bank and serves as documentary proof of inward remittance under FEMA. Indian businesses that export services — SaaS subscriptions, consulting, software development — are required to repatriate export proceeds within the prescribed RBI timeline and maintain FIRC documentation. Without FIRC, the inward remittance from Stripe cannot be confirmed as export proceeds, which creates compliance risk during GST refund claims on zero-rated exports and FEMA scrutiny.",
          "article": "Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching",
          "url": "https://www.terra-insight.com/insights/stripe-india-settlement-reconciliation"
        },
        {
          "q": "Does TDS Section 195 apply to Stripe settlements received by Indian businesses?",
          "a": "Section 195 applies to payments made to non-residents, not to payments received by Indian businesses. However, if an Indian business makes payments to Stripe — for example, for platform fees charged in USD — Section 195 may apply to those outward payments depending on the applicable DTAA rate between India and the country where Stripe's taxable presence is established. For inbound Stripe settlements to Indian accounts, TDS does not apply to the receipt itself; the Indian recipient's income is recognised in India and taxed under domestic rules.",
          "article": "Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching",
          "url": "https://www.terra-insight.com/insights/stripe-india-settlement-reconciliation"
        },
        {
          "q": "What is the variance taxonomy for Stripe India settlement reconciliation?",
          "a": "Three variance types consistently arise in Stripe India reconciliation: FEE_DEDUCTION (Stripe's processing fee, typically 2–3% of the transaction value plus a fixed component, which is deducted before payout), TAX_DEDUCTION (any Stripe-collected taxes applicable in the originating jurisdiction), and ROUNDING — specifically the forex rate conversion difference between the invoice date rate and Stripe's settlement rate, which must be classified as a forex gain or loss in the books rather than a reconciling difference.",
          "article": "Stripe India Settlement Reconciliation: Forex, FIRC, and Inward Remittance Matching",
          "url": "https://www.terra-insight.com/insights/stripe-india-settlement-reconciliation"
        },
        {
          "q": "What is the TCS rate for e-commerce sellers in India under Section 52 of the CGST Act?",
          "a": "The TCS rate under Section 52 of the CGST Act is 1% of the net value of taxable supplies made through the e-commerce operator. For intra-state transactions, this is split as 0.5% CGST and 0.5% SGST. For inter-state transactions, it is 1% IGST. The rate applies to the net taxable value — after returns but before GST — of supplies facilitated by the operator.",
          "article": "TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B",
          "url": "https://www.terra-insight.com/insights/tcs-ecommerce-operator-reconciliation"
        },
        {
          "q": "By what date does an e-commerce operator file GSTR-8 in India?",
          "a": "GSTR-8 must be filed by the e-commerce operator by the 10th of the month following the calendar month in which TCS was collected. For example, TCS collected in January must be reflected in GSTR-8 filed by 10 February. Sellers should check GSTR-2B after the 14th of the following month, when auto-population from operator GSTR-8 filings is typically complete.",
          "article": "TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B",
          "url": "https://www.terra-insight.com/insights/tcs-ecommerce-operator-reconciliation"
        },
        {
          "q": "What should a seller do if the TCS in the settlement report does not match the GSTR-2B amount?",
          "a": "A mismatch between the settlement TCS and the GSTR-2B credit means the operator has either filed GSTR-8 with a different value or has not yet filed. The seller cannot claim the unmatched TCS in GSTR-3B — claiming more than what appears in GSTR-2B creates a discrepancy that will be flagged in GST scrutiny. The seller must contact the operator's seller support to request a GSTR-8 correction or confirmation of the correct value.",
          "article": "TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B",
          "url": "https://www.terra-insight.com/insights/tcs-ecommerce-operator-reconciliation"
        },
        {
          "q": "Where does TCS from e-commerce operators appear in Form 26AS?",
          "a": "TCS deducted by e-commerce operators under Section 52 of the CGST Act appears in Part F of Form 26AS (Tax Collected at Source), which is the income tax Annual Information Statement. This is separate from the GST TCS credit that appears in GSTR-2B. Sellers should reconcile both: the GSTR-2B credit for GST purposes and the Form 26AS entry for income tax purposes.",
          "article": "TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B",
          "url": "https://www.terra-insight.com/insights/tcs-ecommerce-operator-reconciliation"
        },
        {
          "q": "Can a seller on Meesho or Swiggy claim TCS credit against their output GST liability?",
          "a": "Yes. TCS credit appearing in GSTR-2B — auto-populated from the operator's GSTR-8 — can be claimed by the seller in GSTR-3B to offset their output GST liability for that month. There is no separate application; the credit is applied directly in the GSTR-3B return. The seller's obligation is to ensure the GSTR-2B credit matches the settlement deduction before claiming, and to carry forward any unmatched credit to the month when the GSTR-8 correction is filed.",
          "article": "TCS reconciliation for e-commerce sellers — GSTR-8 to GSTR-2B to GSTR-3B",
          "url": "https://www.terra-insight.com/insights/tcs-ecommerce-operator-reconciliation"
        },
        {
          "q": "What is the UPI Reference ID and how does it differ from UTR?",
          "a": "The UPI Reference ID is a 12-digit numeric identifier generated by the NPCI for each UPI transaction. It is distinct from the UTR (Unique Transaction Reference), which is a bank-generated identifier for NEFT, RTGS, and IMPS transactions. For UPI P2M transactions, the UPI Reference ID is the correct match key. The bank narration for a UPI credit typically reads: UPI/P2M/[12-digit UPI Ref ID]/[VPA or merchant name]. Using UTR to match UPI credits does not work because UTR is not generated for all UPI transaction types.",
          "article": "UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books",
          "url": "https://www.terra-insight.com/insights/upi-settlement-reconciliation"
        },
        {
          "q": "How does UPI settlement work for merchants — T+0 or T+1?",
          "a": "UPI P2M (Person to Merchant) transactions settle on a T+0 basis — the merchant's account is credited on the same day the transaction is authorised. This is different from card transactions, which typically settle T+1 or later. For merchants using payment aggregators like Razorpay or PayU, UPI transactions are first collected into the aggregator's nodal account and then settled to the merchant in batches — usually T+1 — based on the aggregator's settlement schedule. The T+0 settlement refers to the NPCI-to-nodal bank leg, not necessarily the aggregator-to-merchant leg.",
          "article": "UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books",
          "url": "https://www.terra-insight.com/insights/upi-settlement-reconciliation"
        },
        {
          "q": "What is the MDR rate for UPI P2M transactions in India?",
          "a": "For UPI P2M (Person to Merchant) transactions below ₹2,000, MDR is 0% per the RBI circular that waived MDR on small-value UPI payments. For transactions above ₹2,000 and for certain merchant categories, MDR may apply at rates set by the acquiring bank or payment aggregator. Merchants should verify the applicable MDR tier in their payment aggregator agreement. For reconciliation purposes, a zero-MDR transaction means the bank credit equals the gross transaction amount — there is no fee deduction to account for in the matching calculation.",
          "article": "UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books",
          "url": "https://www.terra-insight.com/insights/upi-settlement-reconciliation"
        },
        {
          "q": "How does reconciliation differ when UPI is processed through a payment aggregator vs. direct?",
          "a": "When UPI is processed directly via a bank's merchant UPI integration, each transaction generates a separate bank credit with its UPI Reference ID. Reconciliation involves matching each bank credit to the corresponding order in the POS or e-commerce system using the UPI Reference ID. When UPI is processed through an aggregator like Razorpay or PayU, transactions are pooled in the aggregator's nodal account and settled to the merchant as a batch credit (typically daily). Reconciliation then requires a two-step process: match the aggregator settlement report to the batch bank credit, then reconcile individual UPI transactions within the aggregator report to order-level records using the UPI Reference ID.",
          "article": "UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books",
          "url": "https://www.terra-insight.com/insights/upi-settlement-reconciliation"
        },
        {
          "q": "What is the variance taxonomy for UPI settlement reconciliation?",
          "a": "Three variance types arise in UPI reconciliation: FEE_DEDUCTION (aggregator charges and MDR where applicable, which reduce the batch settlement amount from gross transaction total), TAX_DEDUCTION (18% GST on MDR where MDR applies — typically on transactions above ₹2,000 in categories where MDR is charged), and ROUNDING (sub-rupee differences in per-transaction fee calculations that accumulate in batch settlements). For direct UPI with 0% MDR transactions below ₹2,000, FEE_DEDUCTION and TAX_DEDUCTION variances are zero, and only ROUNDING applies.",
          "article": "UPI Settlement Reconciliation — Matching High-Volume T+0 Transactions to Books",
          "url": "https://www.terra-insight.com/insights/upi-settlement-reconciliation"
        }
      ]
    },
    "manufacturing": {
      "label": "Manufacturing Reconciliation",
      "faqs": [
        {
          "q": "What is APMC and why does mandi cess vary by state?",
          "a": "An Agricultural Produce Market Committee (APMC) is a statutory body constituted under each state's APMC Act to regulate trade in notified agricultural commodities within a defined market area. Mandi cess, market fee, rural development cess and auction fee are levies imposed by state APMCs under powers granted by the state APMC Act — and because each state legislates separately, the combined rate varies from approximately 1% (Maharashtra, post 2018 reform) to 6.5% (Punjab, including 3% market fee plus 3% rural development cess plus an auction fee) and points in between. Tamil Nadu, Andhra Pradesh, Karnataka, Madhya Pradesh and Uttar Pradesh each carry their own combined load and revise rates from time to time.",
          "article": "APMC and Mandi Cess Reconciliation Across Indian States",
          "url": "https://www.terra-insight.com/insights/apmc-mandi-cess-reconciliation-india"
        },
        {
          "q": "Is APMC mandi cess GST-creditable?",
          "a": "No. APMC mandi cess, rural development cess and state market fee are state-level levies outside the GST framework — they are not GST and therefore not creditable in the buyer's electronic credit ledger. From a reconciliation standpoint this matters: the cess line on a mandi invoice is a pure cost-of-goods item, not a recoverable input tax. The processor must hold the cess in its commodity cost base for inventory valuation. Where the processor sells the value-added finished goods under GST, the cess that came in at procurement does not flow as ITC.",
          "article": "APMC and Mandi Cess Reconciliation Across Indian States",
          "url": "https://www.terra-insight.com/insights/apmc-mandi-cess-reconciliation-india"
        },
        {
          "q": "What changed under the Model APMC Act 2017 and the now-repealed farm laws?",
          "a": "The Model APMC Act 2017 (Agricultural Produce and Livestock Marketing Act) recommended by the central government allowed states to permit private wholesale markets, direct marketing from farm to buyer, and a single unified market fee. States adopted parts of the model differently — Maharashtra implemented direct marketing and a lower combined cess; Punjab and Haryana retained the higher legacy structure. The three central farm laws of 2020 (which would have extended direct marketing nationally) were repealed in 2021. The result is the current patchwork: state-by-state APMC regimes with material variance in cess rates and direct-procurement permissions.",
          "article": "APMC and Mandi Cess Reconciliation Across Indian States",
          "url": "https://www.terra-insight.com/insights/apmc-mandi-cess-reconciliation-india"
        },
        {
          "q": "What TDS applies to labour and handling contractors at the mandi?",
          "a": "Labour, loading, unloading and handling contractors engaged at the mandi gate (separate from the arhatiya commission agent) attract Section 393(1)(a) of the Income Tax Act 2025, payment code 1002 (which replaced legacy Section 194C). TDS is deductible at 1% (individual/HUF) or 2% (firm/company) above the per-transaction threshold of ₹30,000 and the aggregate annual threshold of ₹1 lakh. A processor procuring 2,000 MT per month across multiple mandis typically engages 3-8 handling contractors and must hold a vendor-master tag plus monthly challan reconciliation under code 1002.",
          "article": "APMC and Mandi Cess Reconciliation Across Indian States",
          "url": "https://www.terra-insight.com/insights/apmc-mandi-cess-reconciliation-india"
        },
        {
          "q": "How should a multi-state procurement footprint be reconciled?",
          "a": "A processor sourcing from mandis in 3+ states must configure each state's cess regime separately in the procurement system — Punjab 6.5%, Haryana 4%, Maharashtra 1%, Karnataka 1.5%, others variable. Each mandi invoice is reconciled with a state-specific split: commodity value, arhatiya commission, market fee, mandi cess, rural development cess, auction fee, weighment charge. The combined load can differ by ₹500-1,200 per MT between states for the same commodity, which materially affects sourcing economics. Monthly close ties the procurement ledger to mandi receipt slips per state and surfaces variances against the configured cess matrix.",
          "article": "APMC and Mandi Cess Reconciliation Across Indian States",
          "url": "https://www.terra-insight.com/insights/apmc-mandi-cess-reconciliation-india"
        },
        {
          "q": "What schemes does APEDA administer for food product exporters?",
          "a": "APEDA (Agricultural and Processed Food Products Export Development Authority) administers several export promotion schemes under its umbrella: Transport and Marketing Assistance (TMA) which subsidises international freight cost for eligible agricultural and processed food product exports; Market Development Assistance which supports market entry, brand promotion and trade fair participation; Quality Development Scheme covering certifications, testing facilities and packaging upgrades; Infrastructure Development Scheme for cold storage, pack-houses and integrated post-harvest facilities. Each scheme has separate eligibility, documentation and claim cycles, and a multi-product exporter must reconcile against each scheme independently.",
          "article": "APEDA Export Incentive Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/apeda-export-incentive-reconciliation-india"
        },
        {
          "q": "How does RoDTEP differ from the earlier MEIS scheme?",
          "a": "MEIS (Merchandise Exports from India Scheme) was withdrawn for most products from 1 January 2021 and replaced by RoDTEP — Remission of Duties and Taxes on Exported Products. RoDTEP is structured to refund embedded taxes and duties not currently refunded under any other mechanism — including state levies, fuel duties and other indirect costs. Disbursement is through electronic credit scrips issued on the ICEGATE portal against the shipping bill. The scrip can be used to pay basic customs duty on imports or transferred to another entity. Reconciliation ties each RoDTEP scrip to its underlying shipping bill, the eligible value, the rate notification and the scrip-use ledger.",
          "article": "APEDA Export Incentive Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/apeda-export-incentive-reconciliation-india"
        },
        {
          "q": "How is FIRC reconciliation done for food exports?",
          "a": "FIRC (Foreign Inward Remittance Certificate) is the bank-issued confirmation that an exporter has received foreign currency against an export shipment. RBI rules require export realisation within 9 months of the shipping bill date for most categories. Reconciliation runs at the shipping-bill-to-FIRC level: shipping bill number, invoice number, invoice value in foreign currency, bank realisation reference, INR equivalent at the realisation date exchange rate, any deductions for bank charges or foreign-agent commission. A shipping bill without a matched FIRC within the 9-month window triggers RBI Caution List exposure for the exporter.",
          "article": "APEDA Export Incentive Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/apeda-export-incentive-reconciliation-india"
        },
        {
          "q": "What is the IGST refund mechanism on zero-rated exports?",
          "a": "Under Section 16 of the IGST Act, exports are treated as zero-rated supplies. The exporter has two options: (a) export under bond or Letter of Undertaking (LUT) without payment of IGST, then claim refund of accumulated input ITC under Section 54 of the CGST Act, or (b) export on payment of IGST and claim refund of the IGST paid. Most large food exporters operate under LUT to preserve working capital. Reconciliation ties the export shipping bill to the LUT registration, the input ITC accumulation, the GSTR-1 export table, the GSTR-3B reverse charge entries where applicable, and the bank receipt when the refund is sanctioned by the GST portal.",
          "article": "APEDA Export Incentive Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/apeda-export-incentive-reconciliation-india"
        },
        {
          "q": "What TDS applies to foreign agent commission for export sales?",
          "a": "Commission paid to a non-resident agent for facilitating export sales attracts Section 413 of the Income Tax Act 2025, payment code 1062 (which replaced legacy Section 195). The rate is determined by the applicable DTAA between India and the agent's resident country plus the Indian rate where DTAA is silent, and a Form 15CA / 15CB certificate accompanies each outward remittance. Where the foreign agent has no permanent establishment (PE) in India and provides services entirely outside India, the position on chargeability has been contested historically but is typically resolved with reference to source rules and DTAA business-income articles. Reconciliation must hold the agent vendor master, the remittance register and the Section 413 challan deposit by the 7th of the following month.",
          "article": "APEDA Export Incentive Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/apeda-export-incentive-reconciliation-india"
        },
        {
          "q": "What is BOM cost reconciliation in a manufacturing context?",
          "a": "Bill of materials (BOM) cost reconciliation is the discipline of tying the standard cost roll-up of a finished good to its actual production cost, identifying and allocating each variance to a defined category, and posting the residual to cost of goods sold (COGS) or work-in-progress (WIP). The standard cost is computed by exploding the BOM structure — parent finished good, sub-assemblies, components, raw materials — at standard rates fixed at the start of the financial year or quarter. The actual cost is the sum of materials issued from inventory at actual issue cost plus labour and overhead absorbed. The variance between standard and actual must be analytically split into four buckets — Price (PPV), Usage, Yield, and Substitution — before it can be meaningfully attributed and managed.",
          "article": "Bill of Materials (BOM) Cost Reconciliation: Standard vs Actual Variance Allocation",
          "url": "https://www.terra-insight.com/insights/bill-of-materials-bom-cost-reconciliation"
        },
        {
          "q": "What are the four main BOM variance categories?",
          "a": "The four classical variance categories in BOM cost reconciliation are: (1) Purchase Price Variance (PPV) — the difference between standard rate and actual rate per unit of raw material, isolating procurement performance; (2) Usage or Quantity Variance — the difference between standard quantity per finished good and actual quantity issued, isolating shop-floor consumption; (3) Yield Variance — the difference between expected output and actual output for a given input, isolating process loss or gain; (4) Substitution or Material Mix Variance — the difference attributable to substituting one material for another (different grade, supplier, or specification) versus the BOM-defined material. Each variance routes to a different owner: PPV to procurement, Usage to shop-floor, Yield to process engineering, Substitution to planning.",
          "article": "Bill of Materials (BOM) Cost Reconciliation: Standard vs Actual Variance Allocation",
          "url": "https://www.terra-insight.com/insights/bill-of-materials-bom-cost-reconciliation"
        },
        {
          "q": "How does BOM cost reconciliation connect to PO-GRN-invoice three-way matching?",
          "a": "Three-way matching reconciles individual procurement transactions — PO, GRN, invoice — at the unit-rate and quantity level. BOM cost reconciliation rolls that up to the finished-good level by aggregating all material issues against the production order. A price tolerance breach surfacing as a Rate Variance in three-way matching directly feeds the Purchase Price Variance (PPV) bucket in BOM reconciliation. A partial GRN drift that delays material booking shows up as a usage variance when the production order is closed before the late GRN is recognised. The two reconciliations are different time horizons of the same data: three-way matching is transactional, BOM reconciliation is the closing month or quarter view that explains why standard cost did not equal actual.",
          "article": "Bill of Materials (BOM) Cost Reconciliation: Standard vs Actual Variance Allocation",
          "url": "https://www.terra-insight.com/insights/bill-of-materials-bom-cost-reconciliation"
        },
        {
          "q": "Where do BOM variances post in the general ledger?",
          "a": "Standard practice under Indian Accounting Standards aligned with Ind AS 2 (Inventories) is to value inventory at cost — which, in a standard costing system, means standard cost adjusted for variances allocated to inventory. Favourable variances reduce inventory carrying value and reduce COGS; adverse variances increase COGS. The four variance buckets typically post as: PPV to a 'Purchase Price Variance' GL account, with monthly absorption to COGS or WIP based on consumption pattern; Usage Variance to a 'Material Usage Variance' GL that closes to COGS; Yield Variance to a 'Process Yield Variance' GL; Substitution Variance to a 'Material Mix Variance' GL. The aggregate of these variance GLs ties back to the standard-versus-actual gap at month-end.",
          "article": "Bill of Materials (BOM) Cost Reconciliation: Standard vs Actual Variance Allocation",
          "url": "https://www.terra-insight.com/insights/bill-of-materials-bom-cost-reconciliation"
        },
        {
          "q": "How is BOM cost reconciliation different in process versus discrete manufacturing?",
          "a": "In discrete manufacturing — say automotive components, electronics, machinery — the BOM is a tree of countable items (one chassis, four wheels, one engine). Variances are calculated per production order and per finished good unit. In process manufacturing — chemicals, pharma, food, metals — the BOM is a recipe with continuous quantities (per batch or per kilogram of output), and yield variance dominates because the conversion of raw input to saleable output is rarely exactly the standard. Process manufacturing also has by-products and co-products with their own valuation rules, which complicate the substitution and yield variance computation. The reconciliation logic is the same — standard versus actual, four variance buckets — but the data structures and dominant variance categories differ.",
          "article": "Bill of Materials (BOM) Cost Reconciliation: Standard vs Actual Variance Allocation",
          "url": "https://www.terra-insight.com/insights/bill-of-materials-bom-cost-reconciliation"
        },
        {
          "q": "Is electricity generated and consumed by a captive power plant subject to GST?",
          "a": "No. Electricity is exempt from GST — it sits as a non-taxable supply under entry 1 of Notification 2/2017 (Central Tax Rate), HSN 2716. Captive consumption of power generated by a CPP for the manufacturer's own use does not attract output GST, both because of the exempt classification and because under Schedule III of the CGST Act self-supply within a single registered entity is not a supply. However, electricity duty, cross-subsidy surcharge and other state-level levies still apply, and the input ITC on coal, capex and consumables used in the CPP is impacted by the exempt-supply rule under Section 17(2) of the CGST Act.",
          "article": "Captive Power Plant Reconciliation for Indian Steel and Metal Manufacturing",
          "url": "https://www.terra-insight.com/insights/captive-power-plant-reconciliation-india"
        },
        {
          "q": "How does Section 17(2) of the CGST Act apply to a captive power plant?",
          "a": "Section 17(2) of the CGST Act requires that where inputs are used partly for taxable supplies (including zero-rated) and partly for exempt supplies, the ITC must be restricted to the proportion attributable to taxable supplies. For a CPP, electricity is exempt, so prima facie all coal and capex ITC could be denied. However, where the CPP feeds power into a manufacturing unit producing taxable goods (steel, sponge iron, aluminium), the law and the CBIC clarifications treat the coal and capex as inputs to the eventual taxable output. The reconciliation must track CPP output kWh allocated to (a) own taxable manufacturing (ITC retained), (b) exempt supply such as grid export under a captive arrangement (ITC reversed) and (c) inter-unit transfer to a separate GST registration (taxable supply at open-market value).",
          "article": "Captive Power Plant Reconciliation for Indian Steel and Metal Manufacturing",
          "url": "https://www.terra-insight.com/insights/captive-power-plant-reconciliation-india"
        },
        {
          "q": "What is the GST treatment of coal procurement for a captive power plant?",
          "a": "Coal attracts 5% GST plus a GST Compensation Cess of ₹400 per tonne where applicable. ITC on coal used in a CPP that feeds a taxable manufacturing unit is generally available, subject to the Section 17(2) apportionment if some power is exported to the grid or supplied to a separate entity. Coking coal imported attracts IGST plus Basic Customs Duty plus the Social Welfare Surcharge — the IGST is claimable as ITC subject to the same apportionment. The reconciliation control ties coal GRN to coal invoice to GSTR-2B entry to the CPP fuel ledger and finally to the per-kWh fuel cost allocated downstream.",
          "article": "Captive Power Plant Reconciliation for Indian Steel and Metal Manufacturing",
          "url": "https://www.terra-insight.com/insights/captive-power-plant-reconciliation-india"
        },
        {
          "q": "How is cross-subsidy surcharge handled for a CPP exporting to the grid?",
          "a": "Where a CPP exports surplus power to the state grid or wheels power to a third party using the grid, the state electricity regulator (SERC) levies a cross-subsidy surcharge — a per-unit charge meant to compensate the state distribution licensee for the loss of its high-paying industrial customer. Cross-subsidy surcharge, additional surcharge, wheeling charges and electricity duty are all separately invoiced by the state DISCOM or transmission company. These are outside GST (electricity itself is non-GST), but they sit in the CPP operating cost. The reconciliation control: per-month export-to-grid kWh, applicable surcharge tariff per the latest SERC tariff order, total surcharge payable, and the DISCOM invoice match.",
          "article": "Captive Power Plant Reconciliation for Indian Steel and Metal Manufacturing",
          "url": "https://www.terra-insight.com/insights/captive-power-plant-reconciliation-india"
        },
        {
          "q": "How is captive consumption transfer pricing between a CPP and the downstream manufacturing unit handled?",
          "a": "Where the CPP and the downstream manufacturing unit are part of the same legal entity and same GST registration, the inter-unit transfer is not a supply under Schedule III of the CGST Act and no GST is leviable. The transfer pricing is an internal cost allocation only — the CPP cost per kWh (coal, manpower, depreciation, allocated overhead) is allocated to consuming units on a metered basis and rolls up into the finished steel cost. Where the CPP and downstream unit are separate GST registrations of the same PAN (different states) or separate entities, the inter-unit transfer is a deemed supply at open market value under Schedule I of the CGST Act, with the CPP recognising taxable supply (though electricity itself is exempt, so the supply is exempt and Section 17(2) bites). MERC/SERC tariff orders provide the benchmark open-market price for the captive arrangement.",
          "article": "Captive Power Plant Reconciliation for Indian Steel and Metal Manufacturing",
          "url": "https://www.terra-insight.com/insights/captive-power-plant-reconciliation-india"
        },
        {
          "q": "What triggers an SCN in electronics imports?",
          "a": "Show Cause Notices on electronics imports cluster around four common triggers. First, valuation disputes on related-party imports where the customs SVB (Special Valuation Branch) suspects transfer pricing below arm's length — relevant for any EMS importing from a brand customer's group entity. Second, HS classification challenges where customs argues a different heading (8536 vs 8537 vs 8542 for switchgear, control panels and integrated circuits, or 8517 vs 8525 for telecom equipment vs broadcasting apparatus). Third, exemption notification misuse claims where customs argues an exemption was incorrectly invoked. Fourth, additional duty short-paid arguments — anti-dumping duty, safeguard duty, social welfare surcharge, IGST. Each triggers a different documentary defence.",
          "article": "Customs Duty SCN Matching for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/customs-duty-scn-matching-electronics-india"
        },
        {
          "q": "What is the SVB and how does it affect related-party imports?",
          "a": "The Special Valuation Branch (SVB) is a unit of customs that examines related-party imports to ensure the declared value reflects arm's-length pricing under Customs Valuation Rules 2007. When an importer is related to the foreign supplier — common for EMS importing from a brand customer's group affiliate — the bill of entry is assessed provisionally, with finalisation pending SVB investigation that can take 18-36 months. During the provisional assessment, the importer pays an Extra Duty Deposit (EDD) typically at 1% of assessable value. On finalisation, the EDD is either refunded under Section 27 of the Customs Act or the importer pays differential duty. Reconciliation must track every provisional bill of entry, the EDD paid, the SVB case reference, and the finalisation outcome.",
          "article": "Customs Duty SCN Matching for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/customs-duty-scn-matching-electronics-india"
        },
        {
          "q": "How is HS classification dispute reconciliation done?",
          "a": "HS misclassification disputes in electronics often cluster around closely-related sub-headings — 8536 (apparatus for switching/protecting electrical circuits) vs 8537 (boards/panels for electric control) vs 8542 (electronic integrated circuits). The duty rate differential between adjacent headings can be 5-15 percentage points and the SCN can demand the differential plus interest plus penalty going back to historical bills of entry. Reconciliation runs a parallel ledger keyed by part number, declared HS, contested HS (where applicable), differential duty exposure, and the technical specification document supporting the declared classification. The technical defence is product-specific — circuit diagrams, function descriptions, end-use evidence.",
          "article": "Customs Duty SCN Matching for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/customs-duty-scn-matching-electronics-india"
        },
        {
          "q": "What is the refund mechanism under Section 27 of the Customs Act?",
          "a": "Section 27 of the Customs Act 1962 governs refund of customs duty paid in excess. When an SCN is dropped (the demand is found unsustainable on adjudication or appeal) or when provisional assessment is finalised in the importer's favour, the importer can claim refund of the excess duty paid. Refund is paid with interest under Section 27A if delayed beyond three months from the refund order. Reconciliation ties each refund claim to the original bill of entry, the duty payment challan (TR-6 or electronic equivalent), the adjudication / appellate order dropping the SCN or finalising the provisional assessment, and the bank receipt when refund is sanctioned. Unjust enrichment doctrine applies — the importer must establish that the duty cost was not passed on to the customer.",
          "article": "Customs Duty SCN Matching for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/customs-duty-scn-matching-electronics-india"
        },
        {
          "q": "What is the typical lifecycle of an SCN at an EMS importer?",
          "a": "An SCN at an EMS importer typically runs: customs issues the SCN within the time limit under Section 28 of the Customs Act (5 years for suppression of facts cases, 2 years for normal cases). The importer files reply within the period stipulated in the SCN. Personal hearing follows. Order-in-Original is issued by the Adjudicating Authority. Appeal lies to the Commissioner (Appeals), then CESTAT, then High Court / Supreme Court on questions of law. Total lifecycle can run 3-7 years. Reconciliation must hold the SCN provision in books appropriately (contingent liability vs provision depending on advice from counsel), track legal cost burden, and reconcile any deposit-against-appeal made under Section 129E.",
          "article": "Customs Duty SCN Matching for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/customs-duty-scn-matching-electronics-india"
        },
        {
          "q": "What is the DAP-2020 offset clause and when does it apply?",
          "a": "Defence Acquisition Procedure 2020 requires that on capital procurement contracts above ₹2,000 crore in the Buy (Global) or Buy and Make categories, the foreign defence vendor (OEM) must discharge offset obligations equal to at least 30% of the contract value. The discharge is fulfilled through purchase of eligible products/services from Indian Defence Public Sector Undertakings (DPSUs), MSMEs and other Indian industry, transfer of technology to DRDO or Indian production agencies, training of Indian personnel, or investment in eligible defence and aerospace infrastructure. The offset clause is contractually binding and tracked through the discharge period (typically aligned to or extending beyond the main contract execution).",
          "article": "DAP-2020 Offset Clause Reconciliation for Indian Defence Manufacturing: 30% Discharge, DOMW Audit, Multipliers",
          "url": "https://www.terra-insight.com/insights/dap-2020-offset-clause-reconciliation-india"
        },
        {
          "q": "How does offset banking work?",
          "a": "DAP-2020 allows foreign vendors to bank offset credits in advance of contract award. A foreign OEM expecting future Indian contracts can pre-discharge through purchases from Indian industry and bank the credits with the Defence Offset Management Wing (DOMW). When a contract above ₹2,000 crore is subsequently awarded, the banked credits can be drawn down against the new contract's offset obligation. Banked credits typically have a validity window (commonly seven years from earning); credits not drawn within the window lapse. Reconciliation at the Indian recipient and at the foreign OEM must maintain matched ledgers of offset credit earned, banked, and drawn against specific contracts.",
          "article": "DAP-2020 Offset Clause Reconciliation for Indian Defence Manufacturing: 30% Discharge, DOMW Audit, Multipliers",
          "url": "https://www.terra-insight.com/insights/dap-2020-offset-clause-reconciliation-india"
        },
        {
          "q": "What are the multiplier rules for offset discharge?",
          "a": "DAP-2020 prescribes multipliers that increase the offset discharge value of certain categories of transactions: direct purchases from Indian industry typically count at 1x face value; purchases from Indian MSMEs typically count at 1.5x to encourage MSME participation; transfer of critical technology to DRDO or Indian production agencies can count at 1.5x to 3x depending on the technology category; investment in eligible defence infrastructure and joint ventures has its own multiplier framework. Reconciliation must apply the correct multiplier per transaction line and the cumulative discharge value is the sum of multiplier-adjusted values, which can be materially higher than the gross rupee outflow.",
          "article": "DAP-2020 Offset Clause Reconciliation for Indian Defence Manufacturing: 30% Discharge, DOMW Audit, Multipliers",
          "url": "https://www.terra-insight.com/insights/dap-2020-offset-clause-reconciliation-india"
        },
        {
          "q": "How does DOMW audit and the annual offset performance return work?",
          "a": "DOMW — the Defence Offset Management Wing under MoD — is the implementing agency for DAP-2020 offset policy. The foreign OEM files an annual offset performance return detailing discharge transactions in the year with documentation per transaction (purchase orders, invoices, bank remittance proof, MSME-status certification where claimed, technology transfer agreements where claimed). DOMW reviews the return, may seek clarifications, conducts audit visits at Indian recipients, and issues an acceptance of discharge to the cumulative obligation. Disallowed discharge lines must be made good in subsequent years; persistent shortfall against the discharge schedule triggers penalty under the contract.",
          "article": "DAP-2020 Offset Clause Reconciliation for Indian Defence Manufacturing: 30% Discharge, DOMW Audit, Multipliers",
          "url": "https://www.terra-insight.com/insights/dap-2020-offset-clause-reconciliation-india"
        },
        {
          "q": "What is the reconciliation obligation at the Indian recipient of offset-attributed purchases?",
          "a": "An Indian DPSU, MSME or industry recipient receiving purchase orders attributed to a foreign OEM's offset discharge must maintain documentation supporting the offset claim — purchase order with offset reference, invoice with appropriate description, bank receipt of remittance, MSME-status certificate if multiplier is claimed, and any technology-transfer documentation. DOMW audit may require the Indian recipient to produce this documentation independently of the foreign OEM. Reconciliation at the Indian recipient must therefore mirror-track offset-attributed transactions in a dedicated sub-ledger separate from regular commercial transactions, with full audit trail.",
          "article": "DAP-2020 Offset Clause Reconciliation for Indian Defence Manufacturing: 30% Discharge, DOMW Audit, Multipliers",
          "url": "https://www.terra-insight.com/insights/dap-2020-offset-clause-reconciliation-india"
        },
        {
          "q": "What are the five DAP-2020 procurement categories and how do they differ on cash-flow?",
          "a": "Defence Acquisition Procedure 2020 organises capital procurement into Buy (Indian-IDDM) where the platform is indigenously designed, developed and manufactured with at least 50% indigenous content, Buy (Indian) with at least 50% indigenous content but not necessarily indigenously designed, Buy and Make (Indian) where licensed manufacture by an Indian vendor follows an initial Buy phase, Buy (Global) with global vendors, and Buy and Make where foreign OEM transfers technology to an Indian production agency. Cash-flow profile differs sharply: Buy (Indian-IDDM) typically has the longest payment cycle with deeper milestone gates; Buy (Global) often involves USD payments and Section 413 withholding considerations. Reconciliation must encode the category against each contract because milestone definitions and PBG requirements vary by category.",
          "article": "Defence Manufacturing Reconciliation in India: DAP Procurement, Offsets, PBG, Milestone Payments",
          "url": "https://www.terra-insight.com/insights/defence-manufacturing-reconciliation-india"
        },
        {
          "q": "How does offset-clause reconciliation work for a contract above ₹2,000 crore?",
          "a": "DAP-2020 requires that on contracts above ₹2,000 crore, the foreign OEM discharge offsets equal to at least 30% of the contract value, fulfilled through purchases from Indian DPSUs, MSMEs, or technology transfer to Indian entities over a defined discharge period (typically aligned to contract execution). Reconciliation runs at two levels: at the foreign OEM (tracking each offset discharge transaction against the cumulative obligation) and at the Indian recipient (tracking offset-attributed purchases received from the foreign OEM, which carry specific documentation requirements for Defence Offset Management Wing audits). Multipliers apply to certain offset categories (MSME purchases, critical technology) that change the discharge value.",
          "article": "Defence Manufacturing Reconciliation in India: DAP Procurement, Offsets, PBG, Milestone Payments",
          "url": "https://www.terra-insight.com/insights/defence-manufacturing-reconciliation-india"
        },
        {
          "q": "What is the MoD vendor code and how does it sit alongside PAN?",
          "a": "MoD maintains a vendor master keyed by a MoD vendor code — a non-PAN identifier issued at vendor registration with the Directorate General of Quality Assurance, the relevant SHQ acquisition wing, or the DPSU contracting authority. PAN is captured separately for TDS and statutory purposes. Reconciliation at a defence vendor must maintain both identifiers and cross-reference them on every invoice — the MoD payment release runs against the MoD vendor code while the TDS deposit runs against PAN. A mismatch (correct MoD code, wrong PAN on the same invoice) is a common reconciliation exception in the first few months after vendor onboarding.",
          "article": "Defence Manufacturing Reconciliation in India: DAP Procurement, Offsets, PBG, Milestone Payments",
          "url": "https://www.terra-insight.com/insights/defence-manufacturing-reconciliation-india"
        },
        {
          "q": "How is a Performance Bank Guarantee (PBG) tracked through the contract life?",
          "a": "PBG is typically 5% to 10% of contract value submitted by the vendor at contract signing, held by MoD or the buying agency through the warranty period (often 24 to 36 months post final acceptance) and released at warranty expiry if no claim has been invoked. Reconciliation maintains a PBG register per contract with bank name, instrument number, face value, validity period, auto-extension clauses, and expiry alerts at 90/60/30 days. A lapsed PBG that should have been extended is a covenant breach and a material reconciliation exception.",
          "article": "Defence Manufacturing Reconciliation in India: DAP Procurement, Offsets, PBG, Milestone Payments",
          "url": "https://www.terra-insight.com/insights/defence-manufacturing-reconciliation-india"
        },
        {
          "q": "What does the retention money pattern look like on a defence contract?",
          "a": "Defence contracts typically structure payments as 10% advance against bank guarantee, milestone payments (60-80% across delivery stages — design freeze, first article, type approval, bulk production, FAT, SAT, deployment), and a retention of 5% to 10% held until final acceptance and warranty expiry. Retention amounts can sit on the buyer's books for 24 to 36 months past physical delivery. Reconciliation must age each retention by contract milestone, link to the corresponding PBG, and trigger a release request workflow at warranty expiry. The retention money pattern is covered in detail at /patterns/retention-money-reconciliation/.",
          "article": "Defence Manufacturing Reconciliation in India: DAP Procurement, Offsets, PBG, Milestone Payments",
          "url": "https://www.terra-insight.com/insights/defence-manufacturing-reconciliation-india"
        },
        {
          "q": "What are the typical milestone stages in a defence contract?",
          "a": "Defence contracts under DAP-2020 are structured around payment stages tied to physical/technical deliverables. A typical 4-year programme includes: 10-15% advance against advance bank guarantee, payment at design freeze (5-10%), payment on prototype/first article delivery (10-15%), payment on type approval or FAT (factory acceptance test) (15-25%), payment on bulk production batches (typically 30-40% across multiple batches), payment on SAT (site acceptance test) and final acceptance (10-15%), and retention release after the 24-36 month warranty expires. Each milestone has a defined deliverable, a buying agency review/acceptance step, and a payment trigger. Reconciliation must encode the milestone schedule per contract and tie each invoice and payment to its milestone.",
          "article": "Defence Contract Milestone Payment Reconciliation in India: MoD Vendor Code, Payment Stages, GST Time-of-Supply",
          "url": "https://www.terra-insight.com/insights/defence-milestone-payment-reconciliation-india"
        },
        {
          "q": "What is the MoD vendor code and how is it different from PAN?",
          "a": "MoD maintains a separate vendor master keyed by a MoD vendor code — a non-PAN identifier issued at vendor registration with the Directorate General of Quality Assurance (DGQA), the relevant Service HQ acquisition wing (Army, Navy, Air Force, Coast Guard), or the DPSU contracting authority. PAN is captured separately for TDS and statutory tax purposes. Reconciliation at a defence vendor must maintain both identifiers and cross-reference them on every invoice — the MoD payment release routes against the MoD vendor code while the TDS deposit by the buyer (where applicable on subcontracted services) routes against PAN. A mismatch (correct MoD code, wrong PAN on the same invoice) is a common reconciliation exception in the first few months of vendor onboarding.",
          "article": "Defence Contract Milestone Payment Reconciliation in India: MoD Vendor Code, Payment Stages, GST Time-of-Supply",
          "url": "https://www.terra-insight.com/insights/defence-milestone-payment-reconciliation-india"
        },
        {
          "q": "How does GST time-of-supply work on a multi-year defence contract?",
          "a": "Under Section 13 of the CGST Act, time of supply for goods is the earlier of invoice or payment, but Notification 66/2017 excludes goods-supply advance from immediate GST charge — GST triggers at invoice/dispatch for goods. For services, time of supply triggers on advance receipt. Defence contracts typically structure each milestone payment against a defined deliverable — when the deliverable is goods (drone units, sub-systems delivered) the GST triggers on the milestone invoice; when the deliverable is service (design package, engineering services, training) the GST triggers on the milestone advance receipt. A composite contract must split each milestone between its goods and service consideration so the time-of-supply treatment per leg is correct.",
          "article": "Defence Contract Milestone Payment Reconciliation in India: MoD Vendor Code, Payment Stages, GST Time-of-Supply",
          "url": "https://www.terra-insight.com/insights/defence-milestone-payment-reconciliation-india"
        },
        {
          "q": "How is the advance bank guarantee tracked against the 10% advance?",
          "a": "The 10-15% contract advance is paid only against an advance bank guarantee from the vendor's bank for the full advance amount. The advance bank guarantee is in addition to the Performance Bank Guarantee — it covers the buyer for recovery of the advance if the vendor fails to perform. The advance is recovered by the buyer through a recovery schedule applied to subsequent milestone payments (e.g. recovered pro-rata over the first 6-8 milestones, or recovered fully against the FAT milestone). The advance bank guarantee value reduces as recovery happens or is released when the advance is fully recovered. Reconciliation maintains an advance-recovery schedule per contract and tracks the advance bank guarantee status separately from the PBG.",
          "article": "Defence Contract Milestone Payment Reconciliation in India: MoD Vendor Code, Payment Stages, GST Time-of-Supply",
          "url": "https://www.terra-insight.com/insights/defence-milestone-payment-reconciliation-india"
        },
        {
          "q": "What TDS code applies on subcontracting under a defence contract?",
          "a": "Subcontracting payments by the principal defence vendor to Tier 2 vendors (manufacturing, testing, engineering services, integration support, sub-assembly) attract Section 393(1)(a) TDS at payment code 1002 — the successor to legacy Section 194C from 1 April 2026. Rate is 1% for individual/HUF and 2% for company/firm with thresholds of ₹30,000 per transaction and ₹1 lakh aggregate per FY. Professional service subcontracts (design consultancy, certification engineering) attract Section 393(1)(b) at code 1003 at 10% (legacy 194J). Purchase of components above ₹50 lakh aggregate per FY per vendor PAN attracts Section 393(1)(k) at code 1012 at 0.1% (legacy 194Q). Reconciliation maintains the vendor-rate matrix with code defaults.",
          "article": "Defence Contract Milestone Payment Reconciliation in India: MoD Vendor Code, Payment Stages, GST Time-of-Supply",
          "url": "https://www.terra-insight.com/insights/defence-milestone-payment-reconciliation-india"
        },
        {
          "q": "What is a Performance Bank Guarantee in a defence contract?",
          "a": "A Performance Bank Guarantee (PBG) is a bank-issued guarantee, typically 5% to 10% of contract value, submitted by the vendor at contract signing as security against the vendor's performance of contractual obligations. The PBG is held by MoD or the buying agency through the contract execution period plus a warranty period (often 24 to 36 months post final acceptance) and released on warranty expiry if no claim has been invoked. PBGs are typically issued by scheduled commercial banks, with explicit auto-extension clauses requiring the issuing bank to extend validity unless instructed otherwise by the beneficiary. The PBG is in addition to retention money — both run in parallel.",
          "article": "Performance Bank Guarantee (PBG) and Retention Money Tracking for Indian Defence Contracts",
          "url": "https://www.terra-insight.com/insights/defence-pbg-retention-tracking-india"
        },
        {
          "q": "How is retention money different from PBG?",
          "a": "Retention money is cash withheld by the buyer from each progress payment to the vendor — typically 5% to 10% of each milestone payment — held by the buyer until release triggers (final acceptance, warranty expiry, no claim). Retention sits on the buyer's books as cash actually retained. PBG is a bank guarantee — no cash sits with the buyer, the vendor's bank guarantees performance and the buyer can invoke the PBG to receive cash from the bank if the vendor defaults. Defence contracts typically use both — retention covers near-term performance risk through delivery and acceptance, PBG covers warranty-period risk after final acceptance.",
          "article": "Performance Bank Guarantee (PBG) and Retention Money Tracking for Indian Defence Contracts",
          "url": "https://www.terra-insight.com/insights/defence-pbg-retention-tracking-india"
        },
        {
          "q": "What are PBG renewal cycles and how are they tracked?",
          "a": "Defence PBGs typically have a 6-month or 12-month validity with an auto-extension clause requiring the issuing bank to extend validity until the beneficiary releases the guarantee. The auto-extension is conditional on the bank's continued willingness to extend, the vendor's continued banking relationship, and the absence of any restriction notice. In practice the bank requires the vendor to pay quarterly PBG charges (typically 0.5% to 1% per quarter on face value) and presents the PBG for extension at each cycle. Reconciliation must maintain a PBG register with bank name, instrument number, face value, current validity, next renewal date, and 90/60/30-day expiry alerts. A lapsed PBG that should have been auto-extended is a covenant breach.",
          "article": "Performance Bank Guarantee (PBG) and Retention Money Tracking for Indian Defence Contracts",
          "url": "https://www.terra-insight.com/insights/defence-pbg-retention-tracking-india"
        },
        {
          "q": "Are PBG bank charges eligible for GST input credit?",
          "a": "Bank charges on PBG attract GST 18% on the charge amount (issuance fee, quarterly renewal fee, amendment fee). The GST is invoiced by the bank to the vendor and is generally eligible for input tax credit at the vendor when the PBG relates to taxable business use — which a defence supply contract typically is. ITC is claimed against the bank's GSTIN-aligned invoice in GSTR-2B and utilised against output GST liability. Reconciliation must capture the bank-charge GST per PBG with the contract reference, so audit-trail tying ITC claimed to PBG to contract is intact for assessment.",
          "article": "Performance Bank Guarantee (PBG) and Retention Money Tracking for Indian Defence Contracts",
          "url": "https://www.terra-insight.com/insights/defence-pbg-retention-tracking-india"
        },
        {
          "q": "What is the ARC/RPC release certificate process?",
          "a": "MoD release of retention and PBG follows a documented certificate process. The Acceptance and Release Certificate (ARC) — sometimes Receipt-cum-Release Certificate (RPC) depending on the procurement document — is issued by the buying agency confirming acceptance of the delivered system, completion of warranty, no outstanding claims, and authorisation to release retention and discharge PBG. The vendor must submit a release request to the buying agency citing the contract reference, retention amount, PBG instrument number, and supporting documentation (warranty period expiry, customer satisfaction notes, no-claim certification). Issuance of the ARC by MoD can take 30-180 days post warranty expiry depending on the buying agency's process. Reconciliation tracks the release-request lifecycle from submission to ARC issuance to bank-credit receipt.",
          "article": "Performance Bank Guarantee (PBG) and Retention Money Tracking for Indian Defence Contracts",
          "url": "https://www.terra-insight.com/insights/defence-pbg-retention-tracking-india"
        },
        {
          "q": "When does Section 413 withholding apply to a drone component import?",
          "a": "Section 413 of the Income Tax Act 2025, payment code 1062 (which replaced legacy Section 195 from 1 April 2026), applies to any sum paid or credited to a non-resident which is chargeable to income tax in India. Pure goods import — buying motors, sensors, propellers from a foreign supplier with no permanent establishment in India — is generally not chargeable as business income in India and therefore not subject to Section 413 withholding. The classification turns on whether the payment is for goods (business profits, generally outside Section 413), royalty (chargeable), fees for technical services / FTS (chargeable), or interest (chargeable). Mixed invoices must be split component-by-component.",
          "article": "Drone Component Import Withholding Under Section 413: DTAA Rates, Form 15CA/15CB, and Royalty vs FTS Classification",
          "url": "https://www.terra-insight.com/insights/drone-component-import-section-413-withholding-india"
        },
        {
          "q": "How is the DTAA rate determined for a Chinese drone component supplier?",
          "a": "The India-China DTAA prescribes specific rates for royalty (10% typically) and fees for technical services (10% typically) and the Act's residual rate is 20% under the Income Tax Act 2025. Section 90 (carried forward) allows the taxpayer to claim the lower of DTAA rate or Act rate, conditional on furnishing of a tax-residency certificate (TRC) from the supplier's home tax authority, plus self-declaration (Form 10F or equivalent under the 2025 Act framework) and absence of permanent establishment in India. Without TRC and Form 10F, the Act 20% rate applies even if DTAA would have given a lower rate.",
          "article": "Drone Component Import Withholding Under Section 413: DTAA Rates, Form 15CA/15CB, and Royalty vs FTS Classification",
          "url": "https://www.terra-insight.com/insights/drone-component-import-section-413-withholding-india"
        },
        {
          "q": "What documentation is required for each foreign remittance?",
          "a": "Form 15CA (online declaration by the remitter, filed before remittance, with Part A/B/C/D depending on amount and chargeability) and, for chargeable remittances above the specified threshold, Form 15CB (Chartered Accountant certificate certifying the chargeability, withholding rate and computation). The supplier's TRC and Form 10F (or post-2025 equivalent) must be on file before applying any DTAA-reduced rate. Bank documentation for the remittance (SWIFT advice, foreign-currency outward remittance form) must reference the Form 15CA acknowledgement number.",
          "article": "Drone Component Import Withholding Under Section 413: DTAA Rates, Form 15CA/15CB, and Royalty vs FTS Classification",
          "url": "https://www.terra-insight.com/insights/drone-component-import-section-413-withholding-india"
        },
        {
          "q": "How does royalty vs FTS classification work for drone software components?",
          "a": "Autopilot firmware, ground control station software, mission planning licences and flight-controller embedded software involve payments that may be classified as royalty (consideration for the right to use a copyright or process) or FTS (consideration for technical, managerial or consultancy services). The classification is fact-specific — a standalone software licence with no provision of services is typically royalty; embedded software bundled with hardware where title to a physical good passes may be treated as part of the goods price (no separate royalty) per applicable jurisprudence. The DTAA-defined royalty article and Section 9(1)(vi) of the legacy Act / its 2025 successor framework govern the classification. Misclassification creates withholding exposure on assessment.",
          "article": "Drone Component Import Withholding Under Section 413: DTAA Rates, Form 15CA/15CB, and Royalty vs FTS Classification",
          "url": "https://www.terra-insight.com/insights/drone-component-import-section-413-withholding-india"
        },
        {
          "q": "What is the cross-era position for invoices in transit at 1 April 2026?",
          "a": "Foreign-supplier invoices and remittances initiated under the legacy Income Tax Act 1961 (Section 195, Form 15CA/15CB references in old notations) before 1 April 2026 continue to be governed by the legacy provisions. From 1 April 2026 onwards, Section 413 of the Income Tax Act 2025 with payment code 1062 applies. Form 15CB certifications dated in the cross-era window typically reference both sections. Reconciliation must maintain cross-era cross-reference in the foreign-vendor master so 26AS/AIS data for FY 2025-26 (legacy code) and FY 2026-27 (new code 1062) reconcile correctly.",
          "article": "Drone Component Import Withholding Under Section 413: DTAA Rates, Form 15CA/15CB, and Royalty vs FTS Classification",
          "url": "https://www.terra-insight.com/insights/drone-component-import-section-413-withholding-india"
        },
        {
          "q": "When does GST become payable on a customer advance for a drone supply?",
          "a": "Under Section 13 of the CGST Act, time of supply for goods is the earlier of date of invoice or date of receipt of payment. However, CBIC Notification 66/2017 (current law) exempts taxpayers other than composition dealers from paying GST at the time of receipt of advance for supply of goods — GST is payable only at invoice/dispatch. For services, the position is different: GST is payable on advance receipt as time of supply triggers on payment. A drone OEM supplying a drone (goods) takes the advance with no immediate GST liability; if the same order included a separate component for pilot training or service support (services), advance against that service component would attract GST at receipt.",
          "article": "Customer Advance and Pre-Order Deposit Reconciliation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-customer-advance-deposit-reconciliation-india"
        },
        {
          "q": "What is an advance receipt voucher and when is it issued?",
          "a": "Rule 50 of the CGST Rules requires a registered person receiving an advance towards any supply (goods or services) to issue an advance receipt voucher (ARV) at the time of receipt. The ARV captures the advance amount, supplier and customer details, GSTIN where applicable, description of the proposed supply, and the rate of tax. For drone OEMs taking advances on goods supply (currently not GST-chargeable at receipt per Notification 66/2017), the ARV is still required as a documentation step. On final dispatch the tax invoice supersedes the ARV and any GST liability triggers on the invoice amount.",
          "article": "Customer Advance and Pre-Order Deposit Reconciliation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-customer-advance-deposit-reconciliation-india"
        },
        {
          "q": "How is the customer deposit booked in the accounting ledger?",
          "a": "The advance/deposit is a liability on the OEM's balance sheet — not revenue. The accounting entry on receipt is debit Bank, credit Customer Advance (current liability). Revenue recognition under Ind AS 115 happens only on transfer of control to the customer (typically at dispatch for goods, with appropriate revenue-recognition trigger). On dispatch the entries reverse: debit Customer Advance against the invoice value, credit Revenue (for the goods portion) and credit Output GST (on the invoice). Reconciliation must age the customer advance liability by customer and pre-order date — long-tenor deposits sitting above 12 months attract scrutiny under audit and possibly under tax assessment for revenue-recognition disputes.",
          "article": "Customer Advance and Pre-Order Deposit Reconciliation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-customer-advance-deposit-reconciliation-india"
        },
        {
          "q": "What happens if a drone order is cancelled and the advance has to be refunded?",
          "a": "When an order is cancelled before dispatch, the OEM must refund the advance to the customer. Since GST was not collected at receipt (goods advance under Notification 66/2017), there is no output GST reversal on the OEM's books. The advance liability is simply extinguished against the bank outflow. If GST had been collected (services advance) and refunded, the OEM claims the refund under Section 54 of the CGST Act for tax paid on supply of services not provided. The advance receipt voucher must be referenced in the refund voucher (Rule 51) and the GSTR-1 / GSTR-3B return adjusted in the next filing.",
          "article": "Customer Advance and Pre-Order Deposit Reconciliation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-customer-advance-deposit-reconciliation-india"
        },
        {
          "q": "How does Section 13 time-of-supply interact with milestone production stages?",
          "a": "For drone supplies typically structured as advance-on-order plus balance-on-dispatch, the goods-supply rules apply at dispatch — GST triggers on the full invoice value at dispatch with the advance adjusted against the invoice. For larger fleet orders structured with milestone payments (advance, design freeze, first article, bulk production, delivery), if the contract is for goods supply the time of supply remains at each dispatch event with no GST at any earlier milestone. If the contract is structured as a composite supply with explicit service components (training, integration, maintenance), the service portions trigger GST at payment receipt and the goods portions at dispatch. Reconciliation must split each milestone payment between goods and service consideration where applicable.",
          "article": "Customer Advance and Pre-Order Deposit Reconciliation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-customer-advance-deposit-reconciliation-india"
        },
        {
          "q": "What is the PLI Drones scheme and how is it claimed?",
          "a": "The PLI Drones scheme was notified with a ₹120 crore base outlay for a three-year tenure covering FY 2022-23 to FY 2024-25 and has been extended in subsequent budgets. Eligibility is anchored on minimum annual sales of drones and drone components above defined thresholds with a value-add criterion of at least 40%. The incentive rate is up to 20% of value-add for eligible manufacturers. Claims are filed annually with the implementation agency under the Ministry of Civil Aviation; reconciliation ties audited eligible value-add to claim filed to sanction letter to bank credit, with disbursements typically lagging the financial year close by six to nine months.",
          "article": "Drone Manufacturing Reconciliation in India: PLI, DGCA Type-Certification, Customer Deposits",
          "url": "https://www.terra-insight.com/insights/drone-manufacturing-reconciliation-india"
        },
        {
          "q": "How does DGCA type-certification cost reconcile against manufacturing P&L?",
          "a": "DGCA's Drone Rules 2021 require type-certification before a drone model can be operated commercially in India. Type-certification cost per model — including airworthiness testing, conformance to type-certificate schedule, and quality management system audit — typically runs into the tens of lakhs and is incurred once per model. Reconciliation treats type-certification as an intangible asset under Ind AS 38, amortised over the expected commercial life of the model (commonly three to five years), with a periodic test for impairment if the model is withdrawn or a successor certified. The R3 (small), R4 (medium) and R5 (large) DGCA categories have different testing depths and therefore different cost bases.",
          "article": "Drone Manufacturing Reconciliation in India: PLI, DGCA Type-Certification, Customer Deposits",
          "url": "https://www.terra-insight.com/insights/drone-manufacturing-reconciliation-india"
        },
        {
          "q": "How does a drone OEM book a customer pre-order deposit for GST?",
          "a": "Under GST time-of-supply rules, advance received for the supply of goods is generally not chargeable to GST at the time of receipt (the position post the October 2017 notification) — GST is payable only when the supply is made (typically at invoice/delivery). However, advances for services do attract GST at receipt. Drone OEMs taking customer deposits for unit pre-orders book the deposit as a liability against the customer with no GST impact at receipt; on dispatch the deposit is applied against the invoice and GST 18% (current rate on drones in the standard category) is reckoned on the gross invoice value. Reconciliation ties the deposit liability ledger by customer to the eventual dispatch and revenue recognition under Ind AS 115.",
          "article": "Drone Manufacturing Reconciliation in India: PLI, DGCA Type-Certification, Customer Deposits",
          "url": "https://www.terra-insight.com/insights/drone-manufacturing-reconciliation-india"
        },
        {
          "q": "When does Section 393(1)(j) e-commerce participant TDS apply to a drone OEM?",
          "a": "Section 393(1)(j) of the Income Tax Act 2025, payment code 1010 (which replaced legacy Section 194O), applies when a manufacturer sells through an e-commerce operator and the operator deducts 1% TDS on the gross sale value at the time of crediting the participant or making payment, whichever is earlier. A drone OEM listing on Amazon, Flipkart or a sector-specific drone marketplace will see the marketplace deduct 1% under code 1010 on every shipped order. Reconciliation must tie the marketplace's TDS deduction statement, the participant's Form 26AS reflection, and the gross sale value in the OEM's books — the three should agree to the rupee.",
          "article": "Drone Manufacturing Reconciliation in India: PLI, DGCA Type-Certification, Customer Deposits",
          "url": "https://www.terra-insight.com/insights/drone-manufacturing-reconciliation-india"
        },
        {
          "q": "What is the Section 413 withholding obligation on foreign component imports?",
          "a": "Section 413 of the Income Tax Act 2025, payment code 1062 (which replaced legacy Section 195), governs TDS on payments to non-residents. A drone OEM importing motors from Germany, flight controllers from Switzerland or LiDAR sensors from the United States must withhold tax at the rate prescribed under the relevant DTAA, typically with a tax-residency certificate from the supplier on file and Form 15CA/15CB filed for each remittance. Goods purchase from a non-resident generally does not attract Section 413 withholding (business profits without PE), but service-component payments (firmware licence fees, software royalties, technical support fees) do. Reconciliation must split each foreign invoice into its goods and service components and apply withholding only to the relevant component.",
          "article": "Drone Manufacturing Reconciliation in India: PLI, DGCA Type-Certification, Customer Deposits",
          "url": "https://www.terra-insight.com/insights/drone-manufacturing-reconciliation-india"
        },
        {
          "q": "What does the DGCA Type Certification Scheme require for an Indian drone model?",
          "a": "DGCA's Drone Rules 2021 require type-certification before a drone model can be operated commercially in India. The Type Certificate is issued against a Type Certificate Data Sheet (TCDS) listing the model's airworthiness configuration. The applicant must undergo airworthiness testing (flight performance, structural integrity, electromagnetic compatibility, software validation), conformance to type-certificate schedule (every produced unit must match the certified configuration), and a Quality Management System audit at the manufacturer's plant. Testing depth and therefore cost varies sharply by category — R3 (small, 2-25 kg) is lighter, R4 (medium, 25-150 kg) and R5 (large, above 150 kg) require deeper test campaigns.",
          "article": "DGCA Type-Certification Cost Amortisation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-type-certification-cost-amortisation-india"
        },
        {
          "q": "How is type-certification cost capitalised under Indian accounting?",
          "a": "Type-certification cost meets the Ind AS 38 definition of an intangible asset — identifiable, controlled by the enterprise, expected to generate future economic benefits, and reliably measurable. Direct costs (test fees paid to designated testing agencies, certification authority charges, conformance audit fees, externally engaged design assurance support, in-house engineering time directly attributable) are capitalised. Indirect overheads, training costs and post-certification marketing costs are expensed. The capitalised asset is amortised over the model's expected commercial life with a periodic test for impairment if commercial success differs materially from the original assumption.",
          "article": "DGCA Type-Certification Cost Amortisation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-type-certification-cost-amortisation-india"
        },
        {
          "q": "What is the typical amortisation life for a drone type certificate?",
          "a": "Useful life depends on the technology generation cycle. For agricultural and survey drones in the R3 category, a 3-5 year commercial life is typical before a successor model. For larger industrial and defence drones in R4/R5, 5-7 years is common because the underlying airframe and propulsion are slower-moving. Ind AS 38 permits amortisation over expected useful life with the units-of-production method also available when the asset's economic benefit is consumed in proportion to output — increasingly common for drone OEMs where the per-unit cost recovery is contractually defined against a committed manufacturing run.",
          "article": "DGCA Type-Certification Cost Amortisation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-type-certification-cost-amortisation-india"
        },
        {
          "q": "How is a failed certification attempt treated?",
          "a": "Costs incurred on a failed certification attempt cannot remain capitalised once the failure is determined. Under Ind AS 38, the carrying amount must be written down to recoverable amount, with any excess recognised as an impairment loss in the P&L. If a fresh certification attempt is launched (revised design, repeat testing), only the new attempt's directly attributable costs are capitalised against the new TCDS — costs from the failed attempt cannot be transferred. Reconciliation must maintain attempt-level accounting on every model under certification to ensure failed-attempt costs are correctly expensed and audit-trailed.",
          "article": "DGCA Type-Certification Cost Amortisation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-type-certification-cost-amortisation-india"
        },
        {
          "q": "When does a design change trigger recertification cost?",
          "a": "Drone Rules 2021 require that any change affecting the airworthiness configuration listed in the TCDS — propulsion system change, structural change, flight controller change, airframe geometry change, battery configuration change — must be either approved as a Minor Change (lower regulatory burden, limited recertification cost) or processed as a Major Change requiring revised TCDS and partial or full recertification. Major changes typically run 30-60% of the original certification cost depending on scope. Reconciliation must capitalise the design-change cost as an addition to the existing intangible asset (Minor) or recognise a new intangible asset for the revised configuration (Major), with the original asset's remaining carrying amount tested for impairment.",
          "article": "DGCA Type-Certification Cost Amortisation for Indian Drone Manufacturers",
          "url": "https://www.terra-insight.com/insights/drone-type-certification-cost-amortisation-india"
        },
        {
          "q": "What is the PLI Large-Scale Electronics Manufacturing scheme and how does it affect reconciliation at an EMS company?",
          "a": "The Production Linked Incentive (PLI) Large-Scale Electronics Manufacturing scheme was launched in April 2020 by MeitY with a total outlay of ₹38,601 crore over five years. It provides a 4-6% incentive on incremental sales of mobile phones and specified electronic components above a base year value, subject to threshold investment commitments. From a reconciliation standpoint, EMS companies must tie every claim to a specific invoice, ensure the customer GSTIN and HSN code map to the eligible product list, and reconcile the incentive disbursement received from MeitY against the claim file submitted quarterly. A mismatch between booked incentive income and approved disbursement is one of the most common audit findings in this scheme.",
          "article": "Electronics Manufacturing Services (EMS) Reconciliation in India: PLI Large-Scale, SPECS, Customs Duty",
          "url": "https://www.terra-insight.com/insights/electronics-manufacturing-services-ems-reconciliation-india"
        },
        {
          "q": "How does the SPECS scheme differ from PLI for component manufacturers?",
          "a": "SPECS — the Scheme for Promotion of Manufacturing of Electronic Components and Semiconductors — provides a 25% capital subsidy on capex incurred for specified electronic components, semiconductor wafers, ATMP units, and certain capital goods. Unlike PLI, which is paid on incremental output, SPECS is paid on plant and machinery capex. Reconciliation runs against fixed asset registers rather than sales ledgers: every machine eligible under SPECS must be tagged with its invoice, bill of entry (if imported), GST ITC trail under Section 17(5), and the SPECS reimbursement claim file. A capex item booked twice or claimed under both SPECS and MSIPS is a disqualification trigger.",
          "article": "Electronics Manufacturing Services (EMS) Reconciliation in India: PLI Large-Scale, SPECS, Customs Duty",
          "url": "https://www.terra-insight.com/insights/electronics-manufacturing-services-ems-reconciliation-india"
        },
        {
          "q": "How are free-issue materials from brand customers reconciled in EMS contract manufacturing?",
          "a": "In the Foxconn/Wistron/Pegatron/Dixon contract manufacturing model, the brand customer often supplies certain bill-of-materials (BOM) items free of charge — chipsets, display modules, branded packaging. These move under a Section 143 CGST job-work dispatch from the brand to the EMS, and the EMS must reconcile inbound free-issue receipts against the GRN, the BOM consumption per finished unit, and the return of unconsumed material or scrap. Free-issue material does not enter EMS revenue or COGS but must show as a no-value receipt with full statutory audit trail. Mis-classification as purchased inventory inflates COGS and creates a GST liability if the return clock is missed.",
          "article": "Electronics Manufacturing Services (EMS) Reconciliation in India: PLI Large-Scale, SPECS, Customs Duty",
          "url": "https://www.terra-insight.com/insights/electronics-manufacturing-services-ems-reconciliation-india"
        },
        {
          "q": "What is the IGST refund mechanism on inverted duty structure for electronics goods?",
          "a": "Several finished electronics goods attract a lower GST rate (12% or 18%) than some of their inputs (which can attract 18% or 28%). Section 54(3) of the CGST Act permits a refund of accumulated ITC on this inverted duty structure. EMS companies file refund applications periodically with documentary proof of input GST paid, output GST charged, and the resulting accumulated credit. Reconciliation must tie each refund claim line to the underlying invoice, the GSTR-2B entry confirming vendor filing, and the bank receipt when refund is sanctioned. Refund claims rejected for documentary gaps are a working-capital drag of 6 to 12 months.",
          "article": "Electronics Manufacturing Services (EMS) Reconciliation in India: PLI Large-Scale, SPECS, Customs Duty",
          "url": "https://www.terra-insight.com/insights/electronics-manufacturing-services-ems-reconciliation-india"
        },
        {
          "q": "Which Section 393 TDS codes apply to EMS purchases and royalty payments?",
          "a": "Three Section 393 codes dominate EMS finance. Section 393(1)(k) (payment code 1012, replaces 194Q) applies at 0.1% on resident-vendor purchases above ₹50 lakh aggregate per PAN per financial year, where buyer turnover exceeds ₹10 crore in the preceding year — relevant for component vendors and packaging suppliers. Section 393(1)(a) (code 1002, replaces 194C) applies on contract manufacturing job-work charges. Section 413 (code 1062, replaces 195) applies on foreign-IP royalty payments — common when an EMS licenses brand IP or pays per-unit royalty to a foreign technology partner. Each requires a separate monthly challan deposit by the 7th of the following month and reconciliation against the quarterly TDS return.",
          "article": "Electronics Manufacturing Services (EMS) Reconciliation in India: PLI Large-Scale, SPECS, Customs Duty",
          "url": "https://www.terra-insight.com/insights/electronics-manufacturing-services-ems-reconciliation-india"
        },
        {
          "q": "What is the typical milestone billing structure in an engineering EPC contract?",
          "a": "A standard Indian EPC engineering contract for a capital goods supply typically structures payment across six phases: 10% on order acceptance as advance, 20% on design freeze and drawings approval, 20% on raw-material procurement evidenced by major component invoices, 25% on dispatch from the manufacturer's works, 15% on installation and commissioning at the customer site, and 10% as retention released after the warranty period (usually 12-18 months from commissioning). Reconciliation tracks each milestone against (a) the contractual evidence (signed design freeze, dispatch documents, commissioning certificate), (b) the invoice raised, (c) the GST liability triggered, (d) the customer payment received, and (e) the warranty-clock start for the retention release. A milestone invoiced without the supporting evidence creates a revenue-recognition reversal at audit.",
          "article": "Engineering and Capital Goods Reconciliation in India: Milestone Billing, Retention, PBG, Advance Receipts",
          "url": "https://www.terra-insight.com/insights/engineering-capital-goods-reconciliation-india"
        },
        {
          "q": "How is retention money reconciled and when is it released?",
          "a": "Retention money is typically 5-10% of the contract value, held by the customer against final acceptance and warranty performance. It is released after the warranty period — usually 12-18 months from commissioning, sometimes extending to 24 months for high-value capital equipment. Reconciliation maintains a retention ledger per contract with: the original retention amount, the GST treatment (GST is payable at the time of original invoice, not at retention release, under Section 13 time-of-supply), the warranty start and end dates, any warranty claims or deductions made by the customer against the retention, and the eventual release receipt. Where the customer deducts a portion of retention against warranty issues, the deducted amount may need a credit-note treatment under Section 34 of the CGST Act with proportionate output tax reversal. See the related cluster pattern at /patterns/retention-money-reconciliation/.",
          "article": "Engineering and Capital Goods Reconciliation in India: Milestone Billing, Retention, PBG, Advance Receipts",
          "url": "https://www.terra-insight.com/insights/engineering-capital-goods-reconciliation-india"
        },
        {
          "q": "What is a Performance Bank Guarantee and how is it separate from retention?",
          "a": "A Performance Bank Guarantee (PBG) is a bank-issued instrument — typically 5-10% of contract value — that the customer holds as security for the contractor's performance through the contract period and often through the warranty. Unlike retention, which is cash held back by the customer, a PBG is an off-balance-sheet contingent liability for the contractor (the bank's commitment to pay the customer if the contractor defaults). Reconciliation must track every active PBG by: bank name and instrument number, beneficiary, expiry date, amount, contract reference, and renewal status. PBGs that expire un-renewed against an active warranty obligation create customer-default risk and trigger contract penalties. The bank charges a quarterly commission (typically 0.5-1% per annum) which sits in finance cost and is itself a reconciliation line.",
          "article": "Engineering and Capital Goods Reconciliation in India: Milestone Billing, Retention, PBG, Advance Receipts",
          "url": "https://www.terra-insight.com/insights/engineering-capital-goods-reconciliation-india"
        },
        {
          "q": "How does GST time-of-supply work on advance receipts for an EPC contract?",
          "a": "Under Section 13 of the CGST Act, time of supply for services is the earliest of (a) invoice date if issued within the prescribed period, (b) date of payment, or (c) where invoice is not issued in time, the completion date. For an EPC contract receiving a 10% advance at order acceptance, the advance triggers GST liability at the time of receipt — the contractor must issue a receipt voucher under Section 31(3) of the CGST Act and pay GST on the advance in the GSTR-3B of that month. When the corresponding milestone invoice is later raised, the GST already paid on the advance is adjusted. Reconciliation must tie each advance receipt voucher to its eventual milestone invoice, ensuring no double GST liability and no missed liability. Advances on pure goods supply may have different time-of-supply treatment under Section 12 (where GST on advances on goods was historically suspended).",
          "article": "Engineering and Capital Goods Reconciliation in India: Milestone Billing, Retention, PBG, Advance Receipts",
          "url": "https://www.terra-insight.com/insights/engineering-capital-goods-reconciliation-india"
        },
        {
          "q": "Which Section 393 TDS codes apply to engineering and capital goods contractors?",
          "a": "Two Section 393 codes dominate the engineering and capital-goods rail. Section 393(1)(a) (payment code 1002, replaces 194C) applies at 1% (individual/HUF) or 2% (company/firm) on contractor payments — civil works contractors, fabrication contractors, installation and commissioning subcontractors, transport contractors. Section 393(1)(b) (payment code 1003, replaces 194J) applies at 10% on professional and technical service fees — design engineers, consulting engineers, project management consultants, third-party inspection agencies. A composite contract that bundles design with execution requires careful classification at PO stage: if the design fee is separately invoiced and identifiable, it sits under 393(1)(b); if bundled into a turnkey contractor invoice, it follows the 393(1)(a) treatment on the whole. Mis-classification is a routine TDS audit finding.",
          "article": "Engineering and Capital Goods Reconciliation in India: Milestone Billing, Retention, PBG, Advance Receipts",
          "url": "https://www.terra-insight.com/insights/engineering-capital-goods-reconciliation-india"
        },
        {
          "q": "What is the MEGA Food Park scheme and how does it affect reconciliation?",
          "a": "The MEGA Food Park scheme is a sub-scheme of the Pradhan Mantri Kisan Sampada Yojana (PMKSY) of the Ministry of Food Processing Industries that funds the creation of food-park clusters with common processing facilities — primary processing centres, collection centres, cold chain infrastructure, warehousing and quality testing labs — usable by individual food-processing units operating in the cluster. Reconciliation for a tenant unit must split its own production-line costs from the common-facility usage charges billed by the park's Special Purpose Vehicle (SPV), each carrying its own GST treatment and Section 393(1)(a) implications where the SPV is treated as a contractor for shared services.",
          "article": "Food Processing Reconciliation in India: MEGA Food Park, FSSAI, Mandi-APMC, GST Multi-Rate",
          "url": "https://www.terra-insight.com/insights/food-processing-reconciliation-india"
        },
        {
          "q": "How does mandi/APMC procurement reconcile across different state cess regimes?",
          "a": "Each state Agricultural Produce Market Committee (APMC) sets its own mandi cess, market fee, and aarthiya commission structure — Punjab and Haryana traditionally have higher market fees than southern states, while Maharashtra has reformed APMC rules differently. Procurement of a commodity through a regulated mandi attracts the mandi cess on top of the commodity price, paid by the buyer to the mandi committee. Reconciliation must split the invoice line: commodity value, aarthiya commission, mandi cess, GST where applicable. The eNAM (electronic National Agriculture Market) integration adds another data source where transactions are settled centrally.",
          "article": "Food Processing Reconciliation in India: MEGA Food Park, FSSAI, Mandi-APMC, GST Multi-Rate",
          "url": "https://www.terra-insight.com/insights/food-processing-reconciliation-india"
        },
        {
          "q": "How are MSP-linked farmer payments reconciled?",
          "a": "MSP-linked procurement for wheat, paddy, pulses and oilseeds is operated by state procurement agencies and FCI on behalf of the Government of India. A food processor procuring under MSP — or against an MSP-floor price in private trade — must reconcile the per-quintal price paid to each farmer against the declared MSP for the relevant rabi or kharif season, route the payment via DBT (Direct Benefit Transfer) to the farmer's bank account where mandated, and maintain farmer-master records with Aadhaar and land-record linkage. The farmer payment reconciliation is sensitive — public scrutiny is high and any under-payment against MSP can trigger regulatory action.",
          "article": "Food Processing Reconciliation in India: MEGA Food Park, FSSAI, Mandi-APMC, GST Multi-Rate",
          "url": "https://www.terra-insight.com/insights/food-processing-reconciliation-india"
        },
        {
          "q": "How does the multi-rate GST output structure work for a food processor?",
          "a": "GST rates on food products vary by category: 0% on fresh produce, milk, eggs and unprocessed grain; 5% on packaged food, branded grain, milk products like paneer; 12% on frozen products, processed dairy, certain fruit juices; 18% on chocolates, beverages, cocoa products, ice cream; 28% on aerated waters and certain luxury food categories. A food processor with a diversified portfolio (fresh produce, branded grain, frozen products, chocolates) raises invoices across multiple GST rates, and reconciliation must tie each SKU to its correct HS code and GST rate. GSTR-1 outward supply reconciliation breaks down by rate slab. GST law is unchanged by the Income Tax Act 2025; the rate structure and Section 17(5) blocked-credit list remain as before.",
          "article": "Food Processing Reconciliation in India: MEGA Food Park, FSSAI, Mandi-APMC, GST Multi-Rate",
          "url": "https://www.terra-insight.com/insights/food-processing-reconciliation-india"
        },
        {
          "q": "What TDS applies to contract-farming payments?",
          "a": "Contract-farming arrangements where a food processor engages farmers (or farmer-producer organisations) for cultivation of a specific commodity under defined terms attract Section 393(1)(a) of the Income Tax Act 2025, payment code 1002 (which replaced legacy Section 194C). The payment to the contracted farmer or FPO is treated as a contractor payment and TDS at 1% (individual/HUF) or 2% (company/firm/FPO) is deductible above the ₹30,000 per-transaction and ₹1 lakh aggregate annual thresholds. The reconciliation must distinguish contract-farming payments from open-market procurement (where no contract exists and TDS does not apply on commodity purchase from agriculturists).",
          "article": "Food Processing Reconciliation in India: MEGA Food Park, FSSAI, Mandi-APMC, GST Multi-Rate",
          "url": "https://www.terra-insight.com/insights/food-processing-reconciliation-india"
        },
        {
          "q": "What is free-issue material in EMS contract manufacturing?",
          "a": "Free-issue (FI) material is bill-of-materials inventory that the brand customer supplies free of charge to the contract manufacturer (EMS). Common examples in mobile and consumer electronics include the application processor / SoC supplied by the brand directly under the brand's volume contract with the chip vendor, display modules procured by the brand from panel manufacturers, camera modules, batteries from approved cells, and branded packaging that carries the brand's IP. The EMS receives these items, consumes them in the production process, ships finished goods carrying the FI components back to the brand, and returns any unconsumed FI material or scrap. FI material does not enter EMS revenue or COGS — only memorandum accounting at no value.",
          "article": "Free-Issue and Customer-Supplied Material Reconciliation for Indian EMS",
          "url": "https://www.terra-insight.com/insights/free-issue-material-reconciliation-ems-india"
        },
        {
          "q": "What is the GST treatment of free-issue material under Section 143 CGST?",
          "a": "Section 143 of the CGST Act governs job-work — the movement of goods from a principal to a job-worker for processing. The principal (brand customer) sends inputs under a delivery challan to the job-worker (EMS) without payment of GST. The EMS processes the inputs and returns the finished goods (or sends them directly to a customer-nominated destination) within 1 year for inputs and 3 years for capital goods. If the inputs are not returned within 1 year, the goods are deemed to be supplied on the day they were originally sent — and the GST liability shifts to the principal at that point. The EMS must reconcile every FI receipt against the consumption and return trail to ensure the 1-year clock is not breached on any line.",
          "article": "Free-Issue and Customer-Supplied Material Reconciliation for Indian EMS",
          "url": "https://www.terra-insight.com/insights/free-issue-material-reconciliation-ems-india"
        },
        {
          "q": "How is free-issue accounted in the EMS books?",
          "a": "FI material is held in a parallel no-value ledger — sometimes called a memorandum inventory ledger or a consignment ledger. It does not enter the EMS's purchases, inventory at value, or COGS. The dual control is that physical inventory must reconcile to the FI ledger quantity-wise, and the FI ledger must reconcile to the brand's outbound dispatch records. Mis-classification as purchased inventory is a recurring audit finding — if the FI is booked as purchase, it inflates COGS by the FI value, creates a phantom output GST liability when the finished goods ship back to the brand at the agreed contract manufacturing price, and breaks the Section 143 reconciliation.",
          "article": "Free-Issue and Customer-Supplied Material Reconciliation for Indian EMS",
          "url": "https://www.terra-insight.com/insights/free-issue-material-reconciliation-ems-india"
        },
        {
          "q": "What is the classification of free-issue handling under Schedule II?",
          "a": "Schedule II of the CGST Act lists activities or transactions to be treated as supply of goods or supply of services. Job-work appears in Schedule II as a supply of services. The EMS charges its contract manufacturing fee to the brand customer (per-unit assembly charge, testing charge, packaging service) as a supply of services under the relevant HSN/SAC. This service supply attracts GST at the applicable rate (typically 18%) on the conversion charge, not on the FI material value. The FI material flow is parallel and tax-neutral as long as Section 143 conditions are met.",
          "article": "Free-Issue and Customer-Supplied Material Reconciliation for Indian EMS",
          "url": "https://www.terra-insight.com/insights/free-issue-material-reconciliation-ems-india"
        },
        {
          "q": "Who bears insurance and shortage risk on FI material?",
          "a": "Insurance and shortage risk on FI material is typically governed by the contract manufacturing agreement between the brand and the EMS. Common patterns: the brand insures FI material in transit to the EMS gate; the EMS insures FI material from the gate inwards until consumption or return; shortage tolerance is defined at agreed percentages (often 0.1-0.3% of FI receipts) with the EMS bearing cost for shortages above the tolerance. Reconciliation must hold the FI receipt quantity, the production line consumption, the certified scrap return, and the in-process inventory snapshot — any unreconciled gap above the tolerance is a charge-back to the EMS at the FI value declared on the brand's outbound.",
          "article": "Free-Issue and Customer-Supplied Material Reconciliation for Indian EMS",
          "url": "https://www.terra-insight.com/insights/free-issue-material-reconciliation-ems-india"
        },
        {
          "q": "What is a goods receipt note (GRN) and why does it need reconciliation?",
          "a": "A goods receipt note is the document a factory raises when material arrives at the gate, capturing what was physically received against what the purchase order specified — quantity, item code, batch, lot, and quality status. GRN reconciliation matters because the GRN status (received-pending-QC, accepted, rejected, partial, on-hold) determines whether the vendor invoice can be processed for payment. A GRN raised in haste, before quality check is complete, creates downstream three-way match exceptions and disputed payments.",
          "article": "Goods Receipt Note (GRN) Reconciliation in India: Partial Deliveries, Rejections, and Quality Holds",
          "url": "https://www.terra-insight.com/insights/goods-receipt-note-grn-reconciliation-india"
        },
        {
          "q": "How are partial deliveries handled on GRN in Indian manufacturing?",
          "a": "A PO for 1,000 kg dispatched in two lots of 500 kg each creates two separate GRNs — GRN-1 for the first lot, GRN-2 for the second. The PO remains open until quantity received equals or exceeds quantity ordered (within tolerance). Each GRN matches against a partial invoice from the vendor, or against one invoice that covers both lots once both are received. The reconciliation control is to keep PO open-quantity, GRN total-received, and invoiced-quantity in three columns and ensure they tie at PO close.",
          "article": "Goods Receipt Note (GRN) Reconciliation in India: Partial Deliveries, Rejections, and Quality Holds",
          "url": "https://www.terra-insight.com/insights/goods-receipt-note-grn-reconciliation-india"
        },
        {
          "q": "What is a quality hold (Q-hold) and how long does it typically last?",
          "a": "A quality hold is a status applied to received material that is awaiting inspection by the Quality department before it can be accepted into bonded stores. Typical Q-hold periods at Indian manufacturers run from 24 hours (routine commodity items) to 7-15 days (incoming engineered components requiring detailed inspection) to 30+ days (sample-and-test programmes for critical items). The vendor invoice cannot be cleared for payment while the material is in Q-hold, because the accepted quantity is not yet final.",
          "article": "Goods Receipt Note (GRN) Reconciliation in India: Partial Deliveries, Rejections, and Quality Holds",
          "url": "https://www.terra-insight.com/insights/goods-receipt-note-grn-reconciliation-india"
        },
        {
          "q": "When should a GRN be reversed, and how is it reconciled?",
          "a": "A GRN is reversed when material is rejected after acceptance — typically when defects are found in production or when a third-party inspection downgrades the lot. The reversal entry reduces the inventory ledger and creates a debit note to the vendor for the rejected quantity. Reconciliation must tie the reversal GRN to the original GRN by reference, the debit note to the vendor ledger, and the physical return movement to an outbound delivery challan with e-way bill where applicable.",
          "article": "Goods Receipt Note (GRN) Reconciliation in India: Partial Deliveries, Rejections, and Quality Holds",
          "url": "https://www.terra-insight.com/insights/goods-receipt-note-grn-reconciliation-india"
        },
        {
          "q": "What is the typical matching window between GRN and vendor invoice?",
          "a": "Indian manufacturers commonly run a 7-15 day matching window between GRN creation and vendor invoice receipt, allowing for quality check completion and document movement. Beyond 15 days, the invoice is typically held in an exception queue under PARTIAL_QTY or AWAITING_GRN until the GRN closes. Beyond 30 days, the invoice routes to an aged-exception escalation. The window should be configured per vendor category — capital equipment may need 60+ days, FMCG raw materials 5-7 days.",
          "article": "Goods Receipt Note (GRN) Reconciliation in India: Partial Deliveries, Rejections, and Quality Holds",
          "url": "https://www.terra-insight.com/insights/goods-receipt-note-grn-reconciliation-india"
        },
        {
          "q": "When does a transporter qualify as a Goods Transport Agency (GTA) under GST?",
          "a": "A transporter qualifies as a Goods Transport Agency (GTA) under the CGST Act only when it issues a Consignment Note (CN) — a document with specific particulars (consignor, consignee, goods description, value, route, vehicle number, freight payable). A transporter that does not issue a Consignment Note is a goods-transport operator and its services are exempt from GST under entry 18 of Notification 12/2017. Only a GTA (which does issue a CN) attracts GST — and even then, under Notification 13/2017, the GST is payable by the recipient (manufacturer) under reverse charge rather than by the GTA itself, unless the GTA has opted for forward charge through the Annexure V declaration. The CN is therefore the documentary trigger that brings the freight into the RCM rail.",
          "article": "GTA Freight RCM Reconciliation for Steel and Manufacturing Inward Logistics",
          "url": "https://www.terra-insight.com/insights/gta-freight-rcm-reconciliation-india"
        },
        {
          "q": "What is the difference between 5% RCM and 12% forward charge on GTA freight?",
          "a": "A GTA has two GST options under the current regime. Under reverse charge (the default under Section 9(3) of the CGST Act and Notification 13/2017), the recipient pays GST at 5% on the freight invoice value; the GTA itself does not collect or pay GST and cannot claim any ITC on its own inputs (fuel, tyres, vehicle maintenance) — the 5% is a clean recipient-side liability. Under forward charge (the GTA opts in by filing Annexure V before 15 March for the next financial year), the GTA collects 12% GST from the recipient as part of the freight invoice, pays it to government and is eligible to claim ITC on its own inputs. The recipient receives an invoice that includes 12% GST and claims ITC on it as a normal inward supply. From the manufacturer's perspective, 5% RCM and 12% forward charge are economically similar in the long run, but the cash-flow timing and the reconciliation trail are different.",
          "article": "GTA Freight RCM Reconciliation for Steel and Manufacturing Inward Logistics",
          "url": "https://www.terra-insight.com/insights/gta-freight-rcm-reconciliation-india"
        },
        {
          "q": "When can a manufacturer claim ITC on GTA-RCM freight?",
          "a": "Under Section 16 of the CGST Act read with Rule 36 of the CGST Rules, ITC on GST paid under reverse charge is available in the same month in which the RCM tax is paid through GSTR-3B 3.1(d), provided the recipient holds the GTA invoice, the underlying Consignment Note, has issued an RCM self-invoice under Section 31(3)(f) of the CGST Act, and the underlying freight is used in the course of business. The ITC claim moves through GSTR-3B Table 4(A)(3) in the same month — so for a manufacturer the RCM is cash-neutral within the month, leaving only the working-capital impact of the small cash outflow on the 20th followed by the ITC offset in the same return.",
          "article": "GTA Freight RCM Reconciliation for Steel and Manufacturing Inward Logistics",
          "url": "https://www.terra-insight.com/insights/gta-freight-rcm-reconciliation-india"
        },
        {
          "q": "What does the reconciliation trail for GTA freight look like end-to-end?",
          "a": "The full GTA freight reconciliation trail has six links. First, the underlying inbound movement document — the purchase order or stock transfer — establishes the consignor and consignee GSTINs and the goods value. Second, the Lorry Receipt (LR) issued by the transporter at pick-up records the vehicle, driver and route. Third, the e-way bill generated on the GSTN system carries the same goods value, consignor and consignee GSTIN and vehicle number. Fourth, the Consignment Note issued by the GTA confirms its GTA status and the freight value. Fifth, the GTA invoice raised on the recipient is the trigger for RCM liability. Sixth, the RCM self-invoice issued by the recipient under Section 31(3)(f) is the document on which 5% RCM is computed, paid through GSTR-3B 3.1(d), and claimed as ITC in Table 4(A)(3). A mismatch on consignor / consignee GSTIN between e-way bill and freight invoice is the most common audit query.",
          "article": "GTA Freight RCM Reconciliation for Steel and Manufacturing Inward Logistics",
          "url": "https://www.terra-insight.com/insights/gta-freight-rcm-reconciliation-india"
        },
        {
          "q": "Which GTA invoices are exempt from RCM and how is that reconciled?",
          "a": "Notification 12/2017 (and subsequent amendments) carve out several GTA freight situations from GST altogether: (a) freight on agricultural produce, (b) freight on milk, salt and food grain, (c) freight on organic manure and registered newspapers, (d) freight where the consideration on a single carriage does not exceed ₹1,500 or where the consideration for transportation for a single consignee does not exceed ₹750, (e) freight relating to defence or military equipment. For a steel manufacturer, none of these routinely apply — the freight on iron ore, coal, fluxes, ferro-alloys and finished steel all attracts GTA RCM. The reconciliation control: every GTA invoice is screened against the exemption notification list at posting; only the small-consignment threshold and any agricultural produce flag are routinely relevant; everything else hits the RCM rail.",
          "article": "GTA Freight RCM Reconciliation for Steel and Manufacturing Inward Logistics",
          "url": "https://www.terra-insight.com/insights/gta-freight-rcm-reconciliation-india"
        },
        {
          "q": "What is inverted duty structure in electronics manufacturing?",
          "a": "Inverted duty structure arises when the GST rate on inputs is higher than the GST rate on the finished output. In electronics this is common — many input components (PCB assemblies, semiconductors at certain stages, specific raw materials) attract 18% GST while several finished electronic goods attract 12% or even 5% GST under specific notifications. Television sets above certain screen sizes, certain consumer electronics, and several IT hardware categories have had inverted structures historically. The accumulated unutilised input tax credit (ITC) that builds up because output tax is lower than input tax can be refunded under Section 54(3)(ii) of the CGST Act.",
          "article": "Inverted Duty Structure IGST Refund for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/inverted-duty-refund-electronics-india"
        },
        {
          "q": "What does Rule 89(5) say about the refund formula?",
          "a": "Rule 89(5) of the CGST Rules provides the formula for refund of unutilised ITC arising from inverted duty structure: Maximum Refund = (Turnover of inverted-rated supply of goods × Net ITC ÷ Adjusted Total Turnover) − Tax payable on such inverted-rated supply of goods. Net ITC is defined as ITC availed on inputs during the relevant period — and following the two amendments (in 2018 and 2022), 'inputs' for the purposes of this rule means goods other than capital goods and input services. The exclusion of input services and capital goods from Net ITC was contested in the VKC Footsteps Supreme Court judgment, which upheld the formula as constitutionally valid.",
          "article": "Inverted Duty Structure IGST Refund for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/inverted-duty-refund-electronics-india"
        },
        {
          "q": "What was the impact of the two Rule 89(5) amendments?",
          "a": "Rule 89(5) was amended in 2018 to restrict the refund to ITC on inputs only — excluding input services and capital goods. This was challenged in multiple High Courts with conflicting outcomes — Gujarat HC initially struck down the restriction, Madras HC upheld it. The Supreme Court in VKC Footsteps (2021) ultimately upheld the restriction, finding the legislative classification within Article 14. A further amendment in 2022 refined the formula computation. For an electronics manufacturer, this means input services (testing, calibration, freight, professional fees) and capital goods (manufacturing equipment) do not contribute to the inverted duty refund pool, even though their GST is real input tax that has been paid.",
          "article": "Inverted Duty Structure IGST Refund for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/inverted-duty-refund-electronics-india"
        },
        {
          "q": "What is the time limit for filing an inverted duty refund?",
          "a": "Section 54 of the CGST Act prescribes a 2-year time limit from the end of the financial year in which the refund claim arises. For inverted duty refund, the relevant date is interpreted as the due date for furnishing GSTR-3B for the period in which the refund arose. A claim filed beyond the 2-year window is time-barred. For a TV manufacturer accumulating ITC monthly, the typical practice is monthly or quarterly filing of FORM GST RFD-01 to keep the claim window short and the working-capital cycle compressed. Refunds filed monthly with complete documentation typically receive provisional refund (90%) within 7 days under Section 54(6) and final sanction subsequently.",
          "article": "Inverted Duty Structure IGST Refund for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/inverted-duty-refund-electronics-india"
        },
        {
          "q": "What documentation supports a Section 54 inverted duty refund?",
          "a": "FORM GST RFD-01 is the refund application. Supporting documents include the Annexure-B statement listing all input invoices with GSTIN of supplier, invoice number, date, taxable value, IGST/CGST/SGST claimed; GSTR-2B confirmation that the supplier has filed and the ITC is reflected; GSTR-3B for the period showing the output tax paid on inverted-rated supplies and the closing ITC balance; a certificate from a Chartered Accountant or Cost Accountant for refunds exceeding ₹2 lakh; and the bank account particulars for refund disbursement. Reconciliation must tie each refund claim line to its GSTR-2B entry to avoid the most common rejection ground (claimed ITC not appearing in GSTR-2B).",
          "article": "Inverted Duty Structure IGST Refund for Indian Electronics Manufacturing",
          "url": "https://www.terra-insight.com/insights/inverted-duty-refund-electronics-india"
        },
        {
          "q": "Which Section of the Income Tax Act 2025 applies to iron ore and coking coal purchase TDS, and at what rate?",
          "a": "Section 393(1)(k) of the Income Tax Act 2025 (payment code 1012, replacing legacy Section 194Q) applies at 0.1% on resident-vendor purchases above ₹50 lakh aggregate per vendor PAN per financial year, where the buyer's turnover crossed ₹10 crore in the immediately preceding year. For an integrated steel manufacturer, this universally engages on iron ore (whether bought from NMDC, state mining corporations like OMC, or merchant mines), coking coal (domestic from CIL subsidiaries or imported), and ferro-alloys. The ₹50 lakh threshold is per vendor PAN per year and resets on 1 April. The 0.1% deduction applies on the value net of GST, on the portion above the ₹50 lakh threshold.",
          "article": "Iron Ore and Coking Coal Procurement TDS Reconciliation for Indian Steel",
          "url": "https://www.terra-insight.com/insights/iron-ore-coking-coal-procurement-reconciliation-india"
        },
        {
          "q": "How does Section 393(1)(k) interact with Section 394 (the new TCS on sale of goods) on iron ore?",
          "a": "Section 394 of the Income Tax Act 2025 (payment code 1073 replacing 206C(1H)) requires a seller with prior-year turnover above ₹10 crore to collect 0.1% TCS on sale-of-goods receipts from a buyer where aggregate sales to that buyer crossed ₹50 lakh in the year. For iron ore — typically supplied by NMDC, OMC, MOIL or large merchant miners whose turnover easily crosses ₹10 crore — both Section 393(1)(k) (on the steel buyer) and Section 394 (on the miner seller) would prima facie engage. The law gives precedence to the buyer-side TDS: Section 393(1)(k) applies, Section 394 does not. The steel manufacturer must deduct 0.1% TDS, the miner must not collect 0.1% TCS. The miner records this through a self-declaration mechanism confirming the buyer is deducting.",
          "article": "Iron Ore and Coking Coal Procurement TDS Reconciliation for Indian Steel",
          "url": "https://www.terra-insight.com/insights/iron-ore-coking-coal-procurement-reconciliation-india"
        },
        {
          "q": "What is the GST treatment of iron ore and coking coal and how does the inverted-duty refund work?",
          "a": "Iron ore attracts 5% GST. Coking coal attracts 5% GST plus, where applicable, a GST Compensation Cess of ₹400 per tonne. Imported coking coal additionally attracts Basic Customs Duty and Social Welfare Surcharge with IGST on the assessable value plus duties. Finished steel (HR coil, CR coil, bars, sections) attracts 18% GST. This creates an inverted-duty position — input GST at 5% accumulates faster than output GST at 18% can absorb it, particularly for coal-heavy integrated steel plants in early operating quarters or after a major capex round. Section 54(3) of the CGST Act permits refund of the accumulated ITC under inverted duty, claimed periodically (typically quarterly) with documentary support tying every input invoice to its GSTR-2B entry and the resulting accumulated credit ledger. Rule 89(5) sets out the formula for the refund amount.",
          "article": "Iron Ore and Coking Coal Procurement TDS Reconciliation for Indian Steel",
          "url": "https://www.terra-insight.com/insights/iron-ore-coking-coal-procurement-reconciliation-india"
        },
        {
          "q": "What is the export duty position on iron ore and how is it reconciled?",
          "a": "The Government of India levies export duty on iron ore — currently 30% on Fe-content-above-58% iron ore lumps and fines, and varying lower rates on lower-Fe grades and on iron ore concentrates and pellets (which sit at a much lower or nil rate to encourage value addition). The grade classification is per the Indian Bureau of Mines (IBM) grading framework, which the customs authorities adopt. A steel plant exporting iron ore or pellets must reconcile the shipping bill to (a) the IBM grade classification certificate establishing Fe content, (b) the export duty computation at the applicable rate, (c) the customs duty payment challan, (d) the export invoice and (e) the foreign remittance receipt within nine months under FEMA. Royalty on the underlying mineral (state revenue) is separate and is paid by the miner, not the manufacturer.",
          "article": "Iron Ore and Coking Coal Procurement TDS Reconciliation for Indian Steel",
          "url": "https://www.terra-insight.com/insights/iron-ore-coking-coal-procurement-reconciliation-india"
        },
        {
          "q": "How are FY 2025-26 deductions under legacy 194Q reconciled in the new regime?",
          "a": "Deductions on iron ore and coking coal made under legacy Section 194Q during FY 2025-26 continue to carry the legacy 194Q tag on the original TDS challan and TDS return (Form 26Q). Those deductions appear in the seller's Form 26AS / AIS under the legacy 194Q label, and the seller's ITR for AY 2026-27 claims credit against the 194Q tag. From 1 April 2026, all new deductions on the same vendors carry payment code 1012 against Section 393(1)(k). Cross-era reconciliation against Form 168 (buyer view) must be able to match both labels — legacy 194Q for transactions up to 31 March 2026 and the new 1012 for transactions from 1 April 2026. Correction challans for FY 2025-26 raised after April 2026 still go under 194Q. For the full Section 393(1)(k) operating mechanics, see /insights/manufacturing-393-1-k-purchase-goods-reconciliation/.",
          "article": "Iron Ore and Coking Coal Procurement TDS Reconciliation for Indian Steel",
          "url": "https://www.terra-insight.com/insights/iron-ore-coking-coal-procurement-reconciliation-india"
        },
        {
          "q": "Which legacy section does Section 393(1)(k) replace and from when?",
          "a": "Section 393(1)(k) of the Income Tax Act 2025 replaces legacy Section 194Q of the Income Tax Act 1961, effective from 1 April 2026. The mechanics carry over largely unchanged — a buyer whose aggregate turnover, gross receipts or sales in the immediately preceding financial year exceed ₹10 crore must deduct 0.1% TDS on purchases from any resident seller where the aggregate purchase value crosses ₹50 lakh in a financial year, applied on the amount above ₹50 lakh. The TDS payment code is 1012, replacing the legacy 194Q tag. Form 168 (buyer view) and Form 26AS/AIS (seller view) carry the new code from FY 2026-27 onwards.",
          "article": "Section 393(1)(k) Purchase TDS for Manufacturing: Payment Code 1012, Section 206C(1H) Overlap (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-393-1-k-purchase-goods-reconciliation"
        },
        {
          "q": "How does Section 393(1)(k) interact with Section 394 (the new TCS on sale of goods)?",
          "a": "Section 394 of the Income Tax Act 2025 replaces legacy Section 206C(1H), payment code 1073, and requires a seller with prior-year turnover above ₹10 crore to collect 0.1% TCS on sale-of-goods receipts from a buyer where aggregate sale value to that buyer crosses ₹50 lakh in a financial year. When both buyer and seller cross their respective thresholds — buyer turnover > ₹10 crore and seller turnover > ₹10 crore and the transaction crosses ₹50 lakh — the law gives precedence to the buyer-side TDS. Section 393(1)(k) applies; Section 394 does not. The buyer must deduct, the seller must not collect. The seller still has a self-declaration mechanism to confirm the buyer is deducting.",
          "article": "Section 393(1)(k) Purchase TDS for Manufacturing: Payment Code 1012, Section 206C(1H) Overlap (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-393-1-k-purchase-goods-reconciliation"
        },
        {
          "q": "On what value is 0.1% TDS computed under Section 393(1)(k)?",
          "a": "Section 393(1)(k) requires the buyer to deduct 0.1% on the amount of purchase consideration paid or credited to the seller, but only on the portion exceeding ₹50 lakh in the financial year. So if a buyer has crossed ₹50 lakh of cumulative purchases from a vendor PAN by 1 August and books another ₹15 lakh invoice on 5 August, the entire ₹15 lakh attracts the 0.1% deduction. The ₹50 lakh threshold applies once per seller PAN per financial year and resets at the start of the next financial year. The deduction is computed on the value net of GST where GST is shown separately on the invoice.",
          "article": "Section 393(1)(k) Purchase TDS for Manufacturing: Payment Code 1012, Section 206C(1H) Overlap (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-393-1-k-purchase-goods-reconciliation"
        },
        {
          "q": "What is the cross-era impact on FY 2025-26 deductions filed before April 2026?",
          "a": "Deductions made under legacy Section 194Q during FY 2025-26 continue to carry the legacy 194Q section tag on the original TDS challan and TDS return (Form 26Q). Those deductions appear in the seller's Form 26AS and AIS under the legacy 194Q label, and the seller's ITR for AY 2026-27 will claim the credit against the 194Q tag. From 1 April 2026, all new deductions must carry payment code 1012 against Section 393(1)(k). Reconciliation against Form 168 (buyer view) for cross-era cases must be able to match both labels — the legacy 194Q for transactions up to 31 March 2026 and the new 1012 for transactions from 1 April 2026 — including correction challans for FY 2025-26 raised after April 2026 (which still go under 194Q).",
          "article": "Section 393(1)(k) Purchase TDS for Manufacturing: Payment Code 1012, Section 206C(1H) Overlap (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-393-1-k-purchase-goods-reconciliation"
        },
        {
          "q": "How should a manufacturer build a year-to-date purchase tracker per vendor for Section 393(1)(k)?",
          "a": "The tracker is keyed on vendor PAN (not vendor code or vendor name — a vendor may operate multiple legal entity codes under one PAN), accumulates net-of-GST invoice value across the financial year, and triggers a deduction flag from the invoice that takes the cumulative purchase above ₹50 lakh. The trigger must read invoice-by-invoice in posting sequence — the deduction does not apply on the invoice that crosses the threshold cumulatively at midnight on a calendar boundary, it applies on each subsequent invoice from that point until 31 March. Reconciliation against Form 168 monthly closes the loop, and ageing of deduction-flagged invoices against the 7th-of-following-month payment deadline catches missed deposits before they attract interest.",
          "article": "Section 393(1)(k) Purchase TDS for Manufacturing: Payment Code 1012, Section 206C(1H) Overlap (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-393-1-k-purchase-goods-reconciliation"
        },
        {
          "q": "What is the typical ageing distribution of an AP exception queue at an Indian manufacturer?",
          "a": "At a mid-size Indian manufacturer running three-way matching on spreadsheets, a typical exception queue at month-end shows roughly 40-50% of exceptions in the 0-30 day bucket, 25-30% in the 31-60 day bucket, 15-20% in the 61-90 day bucket, and 10-15% beyond 90 days. The 90+ day bucket is the most damaging — these are usually disputes that have lost vendor traction, MSME 43B(h) breaches, and ITC claims that may now be time-barred under Section 16(4) of the CGST Act (the September following the financial year). Driving the 90+ bucket toward zero is the highest-impact control.",
          "article": "AP Exception Management for Indian Manufacturing: From 70% Exceptions to Under 15%",
          "url": "https://www.terra-insight.com/insights/manufacturing-ap-exception-management-india"
        },
        {
          "q": "How should AP exceptions be prioritised when the queue is too large to clear daily?",
          "a": "Practical priority routing uses three tiers. Critical: MSME vendors approaching the 45-day Section 43B(h) window, invoices above ₹10 lakh per line, ITC claims at risk of crossing the Section 16(4) deadline. High: invoices in the 31-60 day bucket from any vendor, OVER_INVOICED exceptions above tolerance, VENDOR_PAN_MISMATCH cases. Medium: the standard 0-30 day RATE_VARIANCE and PARTIAL_QTY queue. Critical tickets must clear in 48 hours, High in 5 working days, Medium in the standard 15-day window.",
          "article": "AP Exception Management for Indian Manufacturing: From 70% Exceptions to Under 15%",
          "url": "https://www.terra-insight.com/insights/manufacturing-ap-exception-management-india"
        },
        {
          "q": "What is maker-checker and why does it matter for AP exception resolution?",
          "a": "Maker-checker is the segregation-of-duties control where the AP clerk who classifies and proposes resolution for an exception (the maker) is different from the person who approves and posts the resolution (the checker). For Indian manufacturers, the checker should be at AP manager level for exceptions up to ₹2 lakh, finance head level for ₹2 lakh to ₹10 lakh, and CFO sign-off above ₹10 lakh. The control is critical because exception resolution often involves writing off small variances, raising debit notes, or approving rate variances that have audit and tax implications under Section 393 and ICAI Standards on Auditing.",
          "article": "AP Exception Management for Indian Manufacturing: From 70% Exceptions to Under 15%",
          "url": "https://www.terra-insight.com/insights/manufacturing-ap-exception-management-india"
        },
        {
          "q": "When should an AP exception variance be written off rather than pursued?",
          "a": "Common write-off thresholds at Indian manufacturers are: rate variances below ₹500 per invoice line on commodity items where the index has moved, quantity variances below 0.5% on bulk material weighed at gate, GST rounding-off differences within ₹10 per invoice, and aged exceptions beyond 180 days where the vendor has not responded after three documented follow-ups. The write-off must be approved by the checker, posted to a specific GL (typically 'Procurement variance — within tolerance'), and tracked monthly for trend analysis.",
          "article": "AP Exception Management for Indian Manufacturing: From 70% Exceptions to Under 15%",
          "url": "https://www.terra-insight.com/insights/manufacturing-ap-exception-management-india"
        },
        {
          "q": "How quickly can an Indian manufacturer move from a 70% exception rate to under 15%?",
          "a": "Published implementation timelines for purpose-built three-way matching tools indicate that exception rates move from the 60-75% baseline to under 25% within 30 days of go-live (after vendor master cleanup and tolerance band configuration), to under 20% by day 60, and to under 15% by day 90 with the residual being genuine commercial dispute and quality-hold cases. Build is typically 2-4 weeks on AWS Mumbai infrastructure (ISO 27001:2022) once the ERP exports a structured PO, GRN, invoice and vendor master extract.",
          "article": "AP Exception Management for Indian Manufacturing: From 70% Exceptions to Under 15%",
          "url": "https://www.terra-insight.com/insights/manufacturing-ap-exception-management-india"
        },
        {
          "q": "What qualifies as capital goods under the CGST Act for ITC purposes?",
          "a": "Section 2(19) of the CGST Act defines capital goods as goods, the value of which is capitalised in the books of account of the person claiming ITC, and which are used or intended to be used in the course or furtherance of business. This is a books-driven definition — anything the company capitalises and depreciates under Ind AS 16 or AS 10 is capital goods for GST. Plant and machinery, factory equipment, computers, office furniture above the capitalisation threshold, and certain motor vehicles (subject to Section 17(5)) all fall in scope. Items expensed in the year of purchase are treated as inputs, not capital goods.",
          "article": "Capital Goods ITC Reconciliation for Indian Manufacturing: 5-Year Amortisation, Section 17(5), and CWIP Tracking",
          "url": "https://www.terra-insight.com/insights/manufacturing-gst-itc-capital-goods-reconciliation"
        },
        {
          "q": "Can a manufacturer claim full ITC on capital goods in the year of receipt?",
          "a": "Yes — Section 16 of the CGST Act permits a registered person to claim full ITC on capital goods in the year of receipt, subject to the standard conditions (possession of tax invoice, receipt of goods, supplier has paid the tax, invoice appears in GSTR-2B, no Section 17(5) block). There is no requirement to spread the ITC over the useful life or over five years on initial claim. The five-year clock becomes relevant only when the capital asset is later sold, disposed, or used for exempt or non-business purposes — at which point Section 18(6) and Rule 44 require a partial reversal of the originally claimed ITC.",
          "article": "Capital Goods ITC Reconciliation for Indian Manufacturing: 5-Year Amortisation, Section 17(5), and CWIP Tracking",
          "url": "https://www.terra-insight.com/insights/manufacturing-gst-itc-capital-goods-reconciliation"
        },
        {
          "q": "What is the 60-month reversal rule on sale of capital goods?",
          "a": "Under Section 18(6) read with Rule 44 of the CGST Rules, when a capital asset on which ITC was claimed is later sold, the manufacturer must reverse a portion of the originally claimed ITC. The reversal is computed as the original ITC reduced by five percentage points for every quarter (or part thereof) of use, treating a useful life of 60 months. If the GST on the sale price of the asset exceeds the reversal amount, the higher of the two becomes the GST liability on the disposal. This is why the disposal date of every capital asset must tie back to the original GSTR-2B entry that supported the ITC claim.",
          "article": "Capital Goods ITC Reconciliation for Indian Manufacturing: 5-Year Amortisation, Section 17(5), and CWIP Tracking",
          "url": "https://www.terra-insight.com/insights/manufacturing-gst-itc-capital-goods-reconciliation"
        },
        {
          "q": "Which capital goods fall under Section 17(5) blocked credits?",
          "a": "Section 17(5) of the CGST Act blocks ITC on specified categories regardless of business use. The most common manufacturing-relevant blocks are motor vehicles for transport of persons with seating capacity up to 13 (unless used for specified business purposes such as further supply, transport of passengers, or driving training), vessels and aircraft (with similar exceptions), works contract services for construction of immovable property other than plant and machinery, goods or services used for personal consumption, club and gym memberships, life insurance and health insurance (except where statutorily mandated), and goods lost, stolen, destroyed or written off. ITC claimed on a blocked credit and not reversed by September of the following year attracts 18% interest under Section 50.",
          "article": "Capital Goods ITC Reconciliation for Indian Manufacturing: 5-Year Amortisation, Section 17(5), and CWIP Tracking",
          "url": "https://www.terra-insight.com/insights/manufacturing-gst-itc-capital-goods-reconciliation"
        },
        {
          "q": "How does the CWIP to capital asset transition affect ITC reconciliation?",
          "a": "Vendor invoices for capital projects often arrive over 18-36 months as the project moves through procurement, fabrication, erection and commissioning. The GST on those invoices is claimable as ITC in the month the invoice appears in GSTR-2B and the goods or services are received — there is no need to wait for the asset to be commissioned. In the books, the related cost sits in CWIP and transfers to the fixed asset register only on commissioning. The reconciliation must therefore tie three things: the GSTR-2B inward CG entries (claimed monthly), the CWIP ledger (accumulating until commissioning), and the fixed asset register (populated on commissioning). A drift between any two surfaces as an audit finding.",
          "article": "Capital Goods ITC Reconciliation for Indian Manufacturing: 5-Year Amortisation, Section 17(5), and CWIP Tracking",
          "url": "https://www.terra-insight.com/insights/manufacturing-gst-itc-capital-goods-reconciliation"
        },
        {
          "q": "What is Section 394 of the Income Tax Act 2025?",
          "a": "Section 394 of the Income Tax Act 2025 governs Tax Collection at Source (TCS) on specified categories — replacing legacy Section 206C(1) from the previous Income Tax Act, 1961. For manufacturing, the most common application is scrap sales: ferrous and non-ferrous waste, mill scale, turnings, borings, dross and similar production waste. The TCS rate on scrap is 1% of the sale value, collected by the seller from the buyer at the time of debiting the buyer's account or receipt, whichever is earlier. The payment code on the monthly challan from FY 2026-27 onwards is 1071. Other categories under Section 394 (timber, forest produce, certain minerals, alcohol licence) carry their own rates.",
          "article": "Section 394 Scrap TCS Reconciliation for Manufacturing: Payment Code 1071 (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-scrap-tcs-reconciliation-section-394"
        },
        {
          "q": "Who collects scrap TCS — the manufacturer or the scrap buyer?",
          "a": "The seller of scrap collects TCS from the buyer. For a manufacturer disposing production waste, the manufacturer is the seller and the scrap dealer (or any other buyer) pays the TCS amount over and above the scrap sale value. The manufacturer remits the collected TCS to the government through the monthly TCS challan using payment code 1071, files the quarterly Form 27EQ return showing every buyer's PAN and the TCS collected, and issues Form 27D to each buyer. The buyer then claims the TCS credit against their own income tax liability through Form 26AS / AIS. Reconciliation must close all four legs — scrap sale ledger, TCS collected ledger, Form 27EQ filed, bank credit from the buyer.",
          "article": "Section 394 Scrap TCS Reconciliation for Manufacturing: Payment Code 1071 (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-scrap-tcs-reconciliation-section-394"
        },
        {
          "q": "What is the cross-era issue between Section 206C(1) and Section 394?",
          "a": "Section 394 takes effect from 1 April 2026 (FY 2026-27 onwards). Scrap sales made up to 31 March 2026 were under Section 206C(1) of the Income Tax Act 1961, with the corresponding payment code on the legacy challan. The cross-era problem hits when Form 27D for an FY 2025-26 scrap sale is downloaded by the buyer in FY 2026-27 — the form still references Section 206C(1) because the underlying collection was under the old Act. The buyer's reconciliation engine must map the legacy 206C reference to the buyer's own ledger entry, and the seller must keep both code histories visible until the final FY 2025-26 returns are accepted by CPC-TDS.",
          "article": "Section 394 Scrap TCS Reconciliation for Manufacturing: Payment Code 1071 (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-scrap-tcs-reconciliation-section-394"
        },
        {
          "q": "Form 27EQ versus Form 27D — what is the difference?",
          "a": "Form 27EQ is the quarterly TCS return filed by the seller (the manufacturer) on the income tax e-filing portal — analogous to Form 26Q on the TDS side. It lists every buyer's PAN, the gross scrap sale value, the TCS rate, the TCS collected, the challan reference, and the period. Form 27D is the TCS certificate issued by the seller to each buyer — analogous to Form 16A — which the buyer uses to claim TCS credit against their own tax. Form 27D is generated by the seller from the TRACES portal after the quarterly 27EQ is processed. Reconciliation ties the seller's scrap sale ledger to the 27EQ return, and the buyer reconciles their Form 27D against their purchase ledger and bank debit.",
          "article": "Section 394 Scrap TCS Reconciliation for Manufacturing: Payment Code 1071 (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-scrap-tcs-reconciliation-section-394"
        },
        {
          "q": "Does GSTR-2B show scrap TCS, and how does it interact with GST on scrap?",
          "a": "Scrap sales attract GST in addition to TCS. The seller (manufacturer) charges GST at the applicable rate (18% on most ferrous scrap, varying for non-ferrous waste, mill scale and specified categories) on the scrap sale invoice, and reports the outward supply in GSTR-1. The buyer's GSTR-2B reflects this as inward supply with GST ITC available, subject to Section 17(5) eligibility rules. The TCS leg sits entirely on the income tax side — Section 394, Form 27EQ, Form 27D, Form 26AS — and does not appear on the GST side. Reconciliation runs two parallel rails: GST (GSTR-1 outward at the seller versus GSTR-2B inward at the buyer) and Income Tax TCS (Form 27EQ at the seller versus Form 26AS at the buyer).",
          "article": "Section 394 Scrap TCS Reconciliation for Manufacturing: Payment Code 1071 (FY 2026-27)",
          "url": "https://www.terra-insight.com/insights/manufacturing-scrap-tcs-reconciliation-section-394"
        },
        {
          "q": "What is the typical AP exception rate at an Indian manufacturing company without structured reconciliation?",
          "a": "Documented exception rates in published industry surveys and CFO commentary at mid-size Indian manufacturers run between 60% and 75% of incoming vendor invoices when three-way matching is done on spreadsheets. The main drivers are price-tolerance mismatches against the purchase order, partial-delivery GRN drift, GST-inclusion variance between PO and invoice, and vendor-master PAN/GSTIN errors. Post implementation of a structured matching engine, the same teams typically reduce exception rates to under 15%, with the residual being genuine commercial disputes that need human resolution.",
          "article": "Manufacturing Reconciliation in India: The Complete Guide to PO-GRN-Invoice, Tax, and Bank Matching",
          "url": "https://www.terra-insight.com/insights/manufacturing-reconciliation-india"
        },
        {
          "q": "Which TDS section applies to contractor payments at an Indian manufacturer under the Income Tax Act 2025?",
          "a": "Contractor payments — including job-work charges, civil contractors, transport contractors, and AMC vendors — fall under Section 393(1)(a) of the Income Tax Act 2025, which replaced legacy Section 194C from the previous Act. The TDS payment code used while depositing the tax is 1002. Rates remain 1% for individual/HUF contractors and 2% for company/firm contractors, with the per-transaction threshold of ₹30,000 and aggregate threshold of ₹1 lakh unchanged. Reconciling 393(1)(a) deductions monthly against the contractor's PAN and quarterly against Form 26AS/AIS is the standard control.",
          "article": "Manufacturing Reconciliation in India: The Complete Guide to PO-GRN-Invoice, Tax, and Bank Matching",
          "url": "https://www.terra-insight.com/insights/manufacturing-reconciliation-india"
        },
        {
          "q": "What is Section 393(1)(k) and how does it affect manufacturers buying raw materials?",
          "a": "Section 393(1)(k) of the Income Tax Act 2025 replaces legacy Section 194Q. It requires a buyer whose turnover exceeds ₹10 crore in the preceding financial year to deduct 0.1% TDS on purchases from any resident seller where aggregate purchase value crosses ₹50 lakh in a financial year, beyond the ₹50 lakh threshold. The TDS payment code is 1012. Manufacturers must build a year-to-date purchase tracker per vendor PAN to know precisely when the ₹50 lakh threshold is crossed and start deducting from the next invoice.",
          "article": "Manufacturing Reconciliation in India: The Complete Guide to PO-GRN-Invoice, Tax, and Bank Matching",
          "url": "https://www.terra-insight.com/insights/manufacturing-reconciliation-india"
        },
        {
          "q": "How is scrap sale TCS handled in Indian manufacturing under the new Act?",
          "a": "Scrap sales attract TCS under Section 394 of the Income Tax Act 2025 (replacing legacy Section 206C(1)) at 1% on the sale value, payment code 1071, collected by the seller (the manufacturer) from the buyer at the time of debiting the buyer's account or receipt, whichever is earlier. The TCS is reported in the quarterly TCS return and reflected in the buyer's Form 26AS/AIS. Reconciliation must tie the scrap sale ledger, the TCS collected ledger, the quarterly return, and the bank receipt from the scrap buyer — a four-leg match per scrap invoice.",
          "article": "Manufacturing Reconciliation in India: The Complete Guide to PO-GRN-Invoice, Tax, and Bank Matching",
          "url": "https://www.terra-insight.com/insights/manufacturing-reconciliation-india"
        },
        {
          "q": "Why is GRN reconciliation a separate problem from invoice matching at a factory?",
          "a": "Goods received at the factory gate go through Stores → Quality check → Bonded stores → Issue, with each handoff producing a status change on the GRN (received-pending-QC, accepted, rejected, partial, on-hold). Vendor invoices often arrive before the GRN reaches accepted status, especially for items in quality hold for 5 to 15 days. Matching the invoice to the PO without waiting for GRN closure overstates payables; matching only at GRN closure delays vendor payment. A structured GRN reconciliation tracks both states separately and releases invoices into the AP exception queue only when the GRN status permits.",
          "article": "Manufacturing Reconciliation in India: The Complete Guide to PO-GRN-Invoice, Tax, and Bank Matching",
          "url": "https://www.terra-insight.com/insights/manufacturing-reconciliation-india"
        },
        {
          "q": "How does Ind AS 115 percentage-of-completion revenue recognition apply to an EPC contract?",
          "a": "Under Ind AS 115 (Revenue from Contracts with Customers), revenue from a long-cycle construction or EPC contract is recognised over time where the customer simultaneously receives and consumes the benefit, or the contractor's performance creates or enhances an asset the customer controls, or the performance does not create an asset with alternative use and the contractor has an enforceable right to payment for performance completed. Most onshore EPC contracts in India satisfy these conditions and follow over-time recognition, typically using a cost-incurred input method or a milestone output method. The percentage-of-completion as at month-end drives the cumulative revenue recognised; the period revenue is the change from prior month. RA bill invoicing is the cash-flow event, but it does not directly drive revenue recognition — these are separate.",
          "article": "Milestone Billing and Percentage-of-Completion Reconciliation for Indian EPC Contracts",
          "url": "https://www.terra-insight.com/insights/milestone-billing-percentage-completion-reconciliation-india"
        },
        {
          "q": "What is the RA (Running Account) bill mechanism in an Indian EPC contract?",
          "a": "A Running Account bill is a partial invoice raised by the contractor against work executed and certified up to a cut-off date during the project. A typical EPC contract has 8-15 RA bills over its duration, raised monthly or against pre-defined milestones. Each RA bill follows a standard structure: gross value of work done up to date, less previous cumulative bills, less mobilisation advance recovery for the period (typically pro-rated or front-loaded), less retention (typically 5-10%), less applicable TDS under Section 393(1)(a), plus applicable GST under Section 13 of the CGST Act. The net amount is what the customer actually pays. The final bill at project completion reconciles all RA bills, releases the balance retention (typically deferred to warranty expiry) and closes the contract.",
          "article": "Milestone Billing and Percentage-of-Completion Reconciliation for Indian EPC Contracts",
          "url": "https://www.terra-insight.com/insights/milestone-billing-percentage-completion-reconciliation-india"
        },
        {
          "q": "When does GST liability arise on an RA bill under Section 13 of the CGST Act?",
          "a": "Under Section 13 of the CGST Act, time of supply for services is the earliest of (a) date of invoice if issued within the prescribed period (30 days from supply), (b) date of payment, or (c) where invoice is not issued in time, the completion date. For an RA bill, the invoice date is the GST trigger — the contractor must record output GST in the GSTR-3B of the month of the RA bill date. Where the customer pays an advance before the RA bill (mobilisation advance, milestone advance), GST liability arises on the advance receipt under Section 31(3) receipt voucher mechanism. The reconciliation control: every RA bill date triggers GST liability in that month; every advance receipt triggers GST liability in the month of receipt; the RA bill is then issued net of advance recovery with the GST already paid on advance adjusted.",
          "article": "Milestone Billing and Percentage-of-Completion Reconciliation for Indian EPC Contracts",
          "url": "https://www.terra-insight.com/insights/milestone-billing-percentage-completion-reconciliation-india"
        },
        {
          "q": "What is the difference between certified and uncertified value of work done?",
          "a": "Certified value of work done is the value that the customer's project engineer or independent consultant has measured, verified and signed off against the contract bill of quantities and rates. Uncertified value is work the contractor has actually executed but for which the customer's certification is pending — typical lag of 30-60 days. RA bills are raised on certified value only. Revenue under Ind AS 115 percentage-of-completion may be recognised on uncertified work too (since the performance obligation has been satisfied), creating a balance-sheet line for unbilled revenue. The reconciliation control: monthly bridge between (a) certified value cumulative, (b) uncertified value cumulative, (c) cumulative revenue recognised, (d) cumulative RA bills raised, (e) cumulative customer receipts — with unbilled revenue and trade receivables as separate balance-sheet lines.",
          "article": "Milestone Billing and Percentage-of-Completion Reconciliation for Indian EPC Contracts",
          "url": "https://www.terra-insight.com/insights/milestone-billing-percentage-completion-reconciliation-india"
        },
        {
          "q": "Which Section 393 TDS code applies to RA bill payments under EPC contracts?",
          "a": "Section 393(1)(a) of the Income Tax Act 2025 (payment code 1002, replaces Section 194C) applies at 1% (individual/HUF contractors) or 2% (company/firm contractors) on RA bill payments. The customer (the project owner) deducts TDS on the gross RA bill value net of any service tax (now GST) at the time of credit or payment, whichever is earlier. The per-transaction threshold of ₹30,000 and aggregate threshold of ₹1 lakh trigger the deduction — virtually every RA bill in an EPC project crosses these. Cross-era reconciliation against Form 26AS data filed before 1 April 2026 needs the legacy 194C reference. For the full Section 393 code map see /insights/section-393-tds-new-income-tax-act-reconciliation/ and /insights/tds-payment-codes-1001-1092-india/.",
          "article": "Milestone Billing and Percentage-of-Completion Reconciliation for Indian EPC Contracts",
          "url": "https://www.terra-insight.com/insights/milestone-billing-percentage-completion-reconciliation-india"
        },
        {
          "q": "What is mobilisation advance in an EPC contract and how is it sized?",
          "a": "Mobilisation advance is an upfront payment by the customer to the contractor at the start of the project — typically 10-20% of the contract value — to fund early-stage activities like site mobilisation, design and engineering effort, advance procurement of long-lead items, and initial working capital. The customer secures this advance against an advance bank guarantee issued by the contractor's bank to the customer, equal to (or slightly greater than) the advance amount. Higher mobilisation advances (15-20%) are common on infrastructure and capital-goods contracts with long lead-times on critical equipment; lower (5-10%) on shorter-cycle contracts. The advance is recovered through deduction on each subsequent RA (Running Account) bill — either proportionally across all bills or front-loaded into early bills.",
          "article": "Mobilisation Advance Recovery Reconciliation for Indian EPC and Engineering",
          "url": "https://www.terra-insight.com/insights/mobilisation-advance-recovery-reconciliation-india"
        },
        {
          "q": "How is GST liability triggered on a mobilisation advance under Section 13 of the CGST Act?",
          "a": "Under Section 13 of the CGST Act, time of supply for services is the earliest of (a) date of invoice if issued within the prescribed period (30 days from supply), (b) date of payment, or (c) where invoice is not issued in time, the completion date. A mobilisation advance is a payment received before any invoice is raised — the date of receipt is therefore the time of supply, and GST liability arises in the month of receipt. The contractor must issue a receipt voucher under Section 31(3) of the CGST Act, record the GST at 18% (for a composite works contract) in the GSTR-3B of that month, and pay it to government. When subsequent RA bills are raised, the GST already paid on the corresponding advance portion is adjusted on the RA bill — no double GST liability. For pure goods supply (not works contract), Section 12 historically suspended GST on advances on goods, but a composite contract bundling design / engineering / installation services with goods supply follows Section 13.",
          "article": "Mobilisation Advance Recovery Reconciliation for Indian EPC and Engineering",
          "url": "https://www.terra-insight.com/insights/mobilisation-advance-recovery-reconciliation-india"
        },
        {
          "q": "Can the customer claim ITC on the GST paid on the mobilisation advance?",
          "a": "Yes. The contractor's receipt voucher under Section 31(3) of the CGST Act is the document on which the customer claims input tax credit, subject to Section 16 of the CGST Act (the underlying supply must be for business use, and the eventual invoice must follow). The ITC is available in the month of the receipt voucher. Where the underlying contract is for works contract on the customer's own immovable property and Section 17(5)(c)/(d) blocks ITC on works contract for own-property construction (other than plant and machinery), the ITC on the advance is similarly blocked. A common reconciliation issue: contractors issue receipt vouchers late or with incomplete details, blocking the customer's ITC claim and creating a relationship friction; the discipline is same-month receipt voucher issuance keyed to the bank credit date.",
          "article": "Mobilisation Advance Recovery Reconciliation for Indian EPC and Engineering",
          "url": "https://www.terra-insight.com/insights/mobilisation-advance-recovery-reconciliation-india"
        },
        {
          "q": "How does mobilisation advance recovery work on RA bills and how is the ledger reconciled?",
          "a": "Mobilisation advance is recovered through deduction on each RA bill — either pro-rated (equal recovery across all RA bills) or front-loaded (higher recovery in early bills to derisk the customer). For a ₹50 crore project with 15% mobilisation advance (₹7.5 crore) and 10 RA bills, pro-rated recovery is ₹75 lakh per RA bill. The reconciliation rail maintains an advance ledger per contract showing original advance, cumulative recovery through each RA bill, balance outstanding, and the cumulative GST already paid on the advance (matched against the RA bill GST adjustment). The bank guarantee remains live until balance is nil. A common reconciliation error: the advance recovery on a particular RA bill is missed (RA bill issued at gross value without advance deduction), creating an over-payment to the contractor that has to be clawed back at the next bill or through a credit note.",
          "article": "Mobilisation Advance Recovery Reconciliation for Indian EPC and Engineering",
          "url": "https://www.terra-insight.com/insights/mobilisation-advance-recovery-reconciliation-india"
        },
        {
          "q": "What happens to the mobilisation advance if the contract is terminated mid-way?",
          "a": "On termination of an EPC contract before completion, the unrecovered portion of the mobilisation advance becomes refundable to the customer. The customer typically invokes the advance bank guarantee for the unrecovered balance. The contractor records the refund as a reversal of the advance liability on its books. The GST already paid on the advance receipt is refundable to the contractor under Section 34 of the CGST Act through a credit note — provided the credit note conditions are met (recipient has not claimed the related ITC, or has reversed it). The reconciliation control: on termination, immediately compute unrecovered advance balance, freeze the advance ledger, prepare the GST credit note, coordinate with the customer to reverse their corresponding ITC, and process the refund and BG release. The bank-guarantee invocation by the customer for an uncooperative contractor is a separate legal recourse outside the GST framework.",
          "article": "Mobilisation Advance Recovery Reconciliation for Indian EPC and Engineering",
          "url": "https://www.terra-insight.com/insights/mobilisation-advance-recovery-reconciliation-india"
        },
        {
          "q": "What is MSP and which commodities does it cover?",
          "a": "Minimum Support Price (MSP) is the floor price declared by the Government of India through the Cabinet Committee on Economic Affairs (CCEA) on the recommendation of the Commission for Agricultural Costs and Prices (CACP). MSP is currently notified for 23 commodities — 7 cereals (paddy, wheat, maize, bajra, jowar, ragi, barley), 5 pulses (tur/arhar, moong, urad, chana, masur), 7 oilseeds (groundnut, mustard, soybean, sunflower, sesamum, niger, safflower), and 4 commercial crops (cotton, jute, sugarcane fair-and-remunerative price, copra). Procurement is operated by FCI for wheat and paddy, NAFED and NCCF for pulses and oilseeds under the Price Support Scheme (PSS), state procurement agencies, and cotton through the Cotton Corporation of India.",
          "article": "MSP-Linked Procurement Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/msp-procurement-reconciliation-india"
        },
        {
          "q": "How are MSP-linked farmer payments reconciled when paid via DBT?",
          "a": "Direct Benefit Transfer (DBT) routes the per-quintal MSP payment directly to the farmer's bank account linked to Aadhaar and the land record. Reconciliation runs at farmer-quintal grain: declared MSP for the season, actual price paid, quality deduction or premium, weighbridge slip number, mandi gate-pass, DBT bank credit confirmation. A processor procuring under PSS or directly under MSP-linked private trade must hold farmer-master accuracy (Aadhaar, IFSC, account number, land record number) — any DBT failure suspends payment and the farmer-master correction loop adds 4-7 days per failed record.",
          "article": "MSP-Linked Procurement Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/msp-procurement-reconciliation-india"
        },
        {
          "q": "What is the MSP gap subsidy and when does it apply?",
          "a": "Under schemes like Bhavantar Bhugtan Yojana (Madhya Pradesh) and the Price Deficiency Payment Scheme (PDPS) component of PM-AASHA, where the market price for oilseeds and pulses falls below the notified MSP, the state directly compensates the registered farmer for the difference. The processor pays the prevailing market price; the gap is paid separately by the state agency to the farmer. Reconciliation must hold the spot price per mandi day, the MSP for the season, and the farmer-level registration under the scheme — the processor is not the disbursing entity for the gap, but the buyer ledger feeds the state agency's gap-calculation pipeline.",
          "article": "MSP-Linked Procurement Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/msp-procurement-reconciliation-india"
        },
        {
          "q": "What is the TDS treatment on arhatiya (commission-agent) payments at the mandi?",
          "a": "Commission paid to an arhatiya for procurement facilitation at the APMC mandi attracts Section 393(1)(a) of the Income Tax Act 2025, payment code 1002 (which replaced legacy Section 194C). TDS is deductible at 1% (individual/HUF arhatiya) or 2% (firm/company arhatiya) above the per-transaction threshold of ₹30,000 and the aggregate annual threshold of ₹1 lakh. Important: payments to agriculturists for the commodity itself — where the farmer sells directly — generally do not attract TDS under the agriculture-income exemption, but the arhatiya commission line is a clear contractor payment and must be deducted at source.",
          "article": "MSP-Linked Procurement Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/msp-procurement-reconciliation-india"
        },
        {
          "q": "How does e-NAM differ from the traditional APMC mandi for reconciliation?",
          "a": "e-NAM (electronic National Agriculture Market) is a pan-India electronic trading portal that integrates participating APMC mandis. A bid placed on e-NAM is settled through a centralised payment route, and the buyer receives a single transaction record covering commodity value, mandi cess, market fee, and arhatiya commission (if routed through an agent). Reconciliation of e-NAM transactions is structurally simpler than traditional mandi handling because the platform produces a settlement file per trading day. The processor still needs to hold the underlying weighbridge slip and the quality assay record from the participating mandi as primary evidence.",
          "article": "MSP-Linked Procurement Reconciliation for Indian Food Processing",
          "url": "https://www.terra-insight.com/insights/msp-procurement-reconciliation-india"
        },
        {
          "q": "What is NPPA and how does DPCO 2013 work?",
          "a": "The National Pharmaceutical Pricing Authority (NPPA) is the regulator that administers the Drug Price Control Order (DPCO) 2013 under the Essential Commodities Act. DPCO 2013 brings 'scheduled formulations' — drugs listed in Schedule I of the order, derived from the National List of Essential Medicines (NLEM) — under direct price control. For every scheduled formulation, NPPA fixes a ceiling price per unit (per tablet, per ml, per gm depending on dosage form). The manufacturer's MRP for any pack size of a scheduled formulation cannot exceed (ceiling price × number of units in the pack) plus permitted local taxes — currently GST. Overcharging triggers recovery of the differential plus interest into the Drugs Prices Equalisation Account.",
          "article": "NPPA Price Ceiling and MRP Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/nppa-price-ceiling-mrp-reconciliation-india"
        },
        {
          "q": "How are ceiling prices revised annually?",
          "a": "Ceiling prices for scheduled formulations are revised annually by NPPA on the basis of the Wholesale Price Index (WPI) for the preceding calendar year, typically announced before 1 April each year. The revision applies to the ceiling price per unit and flows through to the MRP a manufacturer can charge across all pack sizes of the scheduled formulation. From a reconciliation standpoint, this means the SKU master must be updated annually with the new ceiling and the system must re-verify MRP compliance across all pack sizes of all scheduled formulations at the cutover date. A pack that was compliant at the previous ceiling may need an MRP reduction or stay flat — never an automatic increase beyond the WPI-allowed band.",
          "article": "NPPA Price Ceiling and MRP Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/nppa-price-ceiling-mrp-reconciliation-india"
        },
        {
          "q": "What is the 10% annual MRP-increase cap for non-scheduled formulations?",
          "a": "For non-scheduled formulations — drugs not listed in Schedule I of DPCO 2013 — there is no per-unit ceiling price. However, the manufacturer cannot increase the MRP by more than 10% in any preceding 12-month period. This cap is monitored by NPPA and any breach triggers recovery proceedings. Reconciliation must hold the SKU master with the MRP-as-on-date-1 and the MRP-as-on-each-revision, and the dashboard must surface any non-scheduled SKU where the year-on-year MRP increase has crossed or is approaching the 10% threshold. The 10% cap applies to the per-pack MRP, not to the per-unit equivalent — so a change in pack size can affect the calculation.",
          "article": "NPPA Price Ceiling and MRP Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/nppa-price-ceiling-mrp-reconciliation-india"
        },
        {
          "q": "How does trade margin work between manufacturer, stockist and retailer?",
          "a": "Pharma distribution traditionally runs through a three-tier channel: manufacturer (or its CFA — Carrying and Forwarding Agent) → stockist (distributor) → retailer (chemist). Trade margin between MRP and the price-to-stockist (PTS) is the combined channel margin. For scheduled formulations, NPPA prescribes maximum permitted trade margins — historically 16% for retailer and 8% for stockist, with variations under specific notifications. For certain notified drugs (cardiac stents, knee implants, several cancer / rare-disease drugs under Trade Margin Rationalisation), NPPA has capped the retailer margin at 30% on the first-point-of-sale price. The manufacturer's invoice to the stockist must be back-calculated from the MRP through the permitted margin structure to ensure each SKU stays inside the trade margin envelope.",
          "article": "NPPA Price Ceiling and MRP Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/nppa-price-ceiling-mrp-reconciliation-india"
        },
        {
          "q": "What is the Form V overcharging certificate?",
          "a": "When NPPA finds a manufacturer has charged a price exceeding the notified ceiling for a scheduled formulation, it issues a demand notice for the differential amount plus interest. The manufacturer's response includes a Form V overcharging certificate that quantifies the overcharged amount across SKUs, pack sizes and time periods. The certified amount, with interest computed under Section 7A of the Essential Commodities Act, is deposited into the Drugs Prices Equalisation Account (DPEA). Reconciliation must hold the per-SKU ceiling-vs-MRP variance over time, surface any breach for early correction, and feed the Form V certification process if NPPA initiates an overcharging inquiry.",
          "article": "NPPA Price Ceiling and MRP Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/nppa-price-ceiling-mrp-reconciliation-india"
        },
        {
          "q": "What is a Performance Bank Guarantee and how does it differ from retention?",
          "a": "A Performance Bank Guarantee (PBG) is a bank-issued instrument — typically 5-10% of the contract value — that the customer holds as security for the contractor's performance through the contract execution period and often through the warranty. The bank commits to pay the customer up to the PBG value if the contractor fails to perform. The PBG is an off-balance-sheet contingent liability for the contractor (the bank is the primary obligor; the contractor has a back-to-back indemnity to the bank). Retention, by contrast, is cash withheld by the customer from the contractor's RA bill payments — it sits on the contractor's books as a recognised receivable. Most large EPC contracts have both: 5-10% retention deducted across RA bills plus a 5-10% PBG issued at order acceptance. The two together secure the customer at typically 10-20% of contract value through the warranty period.",
          "article": "Performance Bank Guarantee (PBG) Ledger Reconciliation for Indian Engineering",
          "url": "https://www.terra-insight.com/insights/performance-bank-guarantee-pbg-ledger-reconciliation-india"
        },
        {
          "q": "What is the typical validity period of a PBG and when does it release?",
          "a": "A typical PBG is valid through the contract execution period plus the warranty period — so for a 14-month execution project with 18-month warranty, the PBG runs for 32 months from order acceptance. The PBG releases on the trigger event specified in the underlying contract — usually the warranty expiry date or a 'no-claim certificate' from the customer at warranty end. For high-value capital equipment contracts, the warranty period can extend to 24-36 months, and the PBG validity matches. PBGs that expire un-renewed against an active warranty obligation create a customer-default risk — the customer can call the unrenewed PBG and trigger contract penalties even where there is no actual performance failure. The reconciliation control: PBG expiry calendar with 60 / 30 / 7-day renewal alerts.",
          "article": "Performance Bank Guarantee (PBG) Ledger Reconciliation for Indian Engineering",
          "url": "https://www.terra-insight.com/insights/performance-bank-guarantee-pbg-ledger-reconciliation-india"
        },
        {
          "q": "How is the BG commission cost computed and is it claimable as ITC?",
          "a": "Bank guarantee commission is charged by the issuing bank — typically 0.5-1% per annum on the PBG face value, billed quarterly in advance. The commission is a financial service attracting 18% GST. For a contractor with a ₹400 crore active PBG portfolio at 0.75% annual rate, the annual BG commission is ₹3 crore plus ₹54 lakh GST. The GST on BG commission is eligible for ITC under Section 16 of the CGST Act, since BG is a service used in the course of the contractor's business of providing taxable EPC services. The reconciliation control: monthly bank statement BG commission entries tied to the per-PBG amortisation schedule, GST invoice from the bank tied to GSTR-2B, ITC claim in the period.",
          "article": "Performance Bank Guarantee (PBG) Ledger Reconciliation for Indian Engineering",
          "url": "https://www.terra-insight.com/insights/performance-bank-guarantee-pbg-ledger-reconciliation-india"
        },
        {
          "q": "What is the cost of a PBG extension on a programme delay?",
          "a": "Where a project is delayed and the original PBG expires before commissioning or warranty expiry, the PBG must be extended. The bank charges an extension fee — typically the prorated commission for the extension period — plus, depending on the bank's risk reassessment, sometimes a higher rate. For a ₹5 crore PBG extended by six months at 1% annual rate, the extension cost is ₹2.5 lakh plus 18% GST. The contractor may also need to deposit additional margin money with the bank, since BG extensions tighten the bank's exposure window. Where the delay is attributable to the customer (change orders, scope creep, site readiness issues), the contract typically allows the contractor to recover the extension cost; where attributable to the contractor, it's an absorbed cost. The reconciliation control: per-project programme variance against original baseline; trigger BG extension request 60 days before expiry; track extension cost as either pass-through or contractor cost.",
          "article": "Performance Bank Guarantee (PBG) Ledger Reconciliation for Indian Engineering",
          "url": "https://www.terra-insight.com/insights/performance-bank-guarantee-pbg-ledger-reconciliation-india"
        },
        {
          "q": "How does the issuing-bank statement reconcile to the PBG ledger?",
          "a": "The contractor's bank issues monthly statements listing all live PBGs along with face value, beneficiary, validity, expiry date and outstanding commission. The reconciliation rail ties this statement to the contractor's internal PBG ledger — which links each PBG to a specific contract, a contract milestone (typically order acceptance, mobilisation, commissioning), an underlying client requirement (per the contract clause), and a release trigger (commissioning certificate, warranty expiry, no-claim). Variances: bank-statement-listed PBGs not appearing in the contractor's ledger (typically dormant or already-released that the bank's records haven't updated); contractor-ledger PBGs not appearing on the bank statement (typically newly issued and not yet captured by the bank's reporting cycle). Monthly reconciliation closes both directions.",
          "article": "Performance Bank Guarantee (PBG) Ledger Reconciliation for Indian Engineering",
          "url": "https://www.terra-insight.com/insights/performance-bank-guarantee-pbg-ledger-reconciliation-india"
        },
        {
          "q": "What is Schedule M and what changed in 2023?",
          "a": "Schedule M of the Drugs and Cosmetics Rules 1945 prescribes Good Manufacturing Practice (GMP) requirements that every pharmaceutical formulation and API manufacturing plant in India must follow. The revised Schedule M was notified in 2023 with a phased compliance timeline running through December 2026 for different plant sizes — larger plants moved first, MSME-classified plants given a longer runway. The revision tightens batch-record requirements, mandates pharmaceutical quality system implementation, strengthens cross-contamination controls, and updates documentation requirements for sterile and non-sterile manufacturing. Reconciliation impact: every batch must now carry a more detailed audit trail from raw-material receipt through processing to dispatch, with electronic records preferred over paper-based logs.",
          "article": "Schedule M Batch Traceability Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/pharma-batch-traceability-reconciliation-india"
        },
        {
          "q": "What is the QR-code track-and-trace mandate for top 300 pharma brands?",
          "a": "Since 1 August 2023, the top 300 pharmaceutical brands in India (by Moving Annual Turnover, as notified by the Ministry of Chemicals and Fertilisers) are required to carry a QR code on the primary packaging that encodes traceability data — unique product identification code, manufacturer name, brand name, batch number, manufacturing date, expiry date and manufacturing licence number. The QR code enables end-to-end traceability from manufacturer through stockist to retailer to patient. Reconciliation impact: the batch-level data captured at packaging must reconcile to the dispatch register, the distributor receipt confirmation, and (where pull through to the patient is reported) the secondary-sales feed.",
          "article": "Schedule M Batch Traceability Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/pharma-batch-traceability-reconciliation-india"
        },
        {
          "q": "How does CDSCO PvPI integration affect batch reconciliation?",
          "a": "The Pharmacovigilance Programme of India (PvPI), run by CDSCO through the Indian Pharmacopoeia Commission, captures adverse drug reaction (ADR) reports from healthcare providers, patients and manufacturers. Manufacturers are required to monitor ADRs at batch level — an ADR cluster linked to a specific batch can trigger a recall. Reconciliation must hold the batch traceability such that an ADR signal at PvPI can be mapped back to the manufacturing batch, the BOM consumed, the QC release records, the dispatch trail to distributors and (where the QR-code track-and-trace applies) the further movement to retail. Failure to reconcile an ADR-flagged batch to its dispatch footprint delays recall execution and amplifies regulatory exposure.",
          "article": "Schedule M Batch Traceability Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/pharma-batch-traceability-reconciliation-india"
        },
        {
          "q": "What does a batch recall reconciliation involve?",
          "a": "A batch recall — voluntary by the manufacturer or directed by CDSCO — requires the manufacturer to recover every unit of the affected batch from the distribution chain. Reconciliation runs at the batch + distributor level: original dispatch quantity to each stockist, returns received against the recall notice, residual quantity unaccounted-for (still in retail / patient hands), credit notes issued for returned stock, destruction certificates for recovered stock, and the bank receipt reversal where the manufacturer refunds the distributor's payment. Where the QR-code track-and-trace data is available, the recall recovery rate can be measured at retail or patient level. Where it isn't, the recovery is measured at the distributor level only.",
          "article": "Schedule M Batch Traceability Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/pharma-batch-traceability-reconciliation-india"
        },
        {
          "q": "How is ITC reversal handled on a destroyed batch under recall?",
          "a": "When a batch is recalled and destroyed (rather than salvaged or reprocessed where regulatory permission allows), the ITC on the inputs that went into that batch must be reversed under Section 17(5)(h) of the CGST Act, which blocks ITC on goods destroyed. The reversal is computed proportionately: identify the destroyed batch quantity, trace it through the BOM to the API, excipients, primary and secondary packaging, calculate the original ITC on those inputs, reverse the proportionate ITC in GSTR-3B for the period of destruction. The destruction certificate, the batch traceability, and the reversal entry must all reconcile to the same physical event. GST law on this point is unchanged by the Income Tax Act 2025.",
          "article": "Schedule M Batch Traceability Reconciliation for Indian Pharmaceutical Manufacturing",
          "url": "https://www.terra-insight.com/insights/pharma-batch-traceability-reconciliation-india"
        },
        {
          "q": "What is the typical pharma distributor return policy?",
          "a": "Indian pharma manufacturers operate a standardised take-back policy with distributors and stockists, typically covering near-expiry stock (3-6 months from expiry date) for either credit note settlement against future purchases or physical replacement, and full-expiry / damaged / regulatory-recall stock for credit note + destruction. The specific terms — return window, return value (full MRP, PTS, manufacturer's invoice value, or net of channel margin), replacement vs credit — are governed by the manufacturer's distributor agreement and vary by therapeutic category and competitive positioning. The reconciliation operates at the SKU + batch + distributor level: original sale invoice, return note from distributor, credit note issued, destruction certificate or replacement dispatch.",
          "article": "Pharmaceutical Distributor and Expired Stock Return Reconciliation",
          "url": "https://www.terra-insight.com/insights/pharma-distributor-return-reconciliation-india"
        },
        {
          "q": "How does the GST credit note mechanism work under Section 34?",
          "a": "Section 34 of the CGST Act governs credit notes. When a manufacturer issues a credit note for returned goods or price reduction, the corresponding output GST liability reduces and the recipient's ITC reduces correspondingly. The credit note must contain particulars prescribed under Rule 53 of the CGST Rules — credit note number and date, original invoice reference, reason for issuance, taxable value adjustment, tax adjustment. Post-April-2024 amendment, credit notes can be issued up to 30 November of the following financial year (or the date of furnishing the annual return, whichever is earlier) — a tighter window than the previously open-ended position. Reconciliation must surface aged sale invoices approaching this window for proactive return processing.",
          "article": "Pharmaceutical Distributor and Expired Stock Return Reconciliation",
          "url": "https://www.terra-insight.com/insights/pharma-distributor-return-reconciliation-india"
        },
        {
          "q": "When does ITC reversal under Section 17 apply to expired stock?",
          "a": "Section 17(5)(h) of the CGST Act blocks ITC on goods lost, stolen, destroyed, written off or disposed of by way of gift or free sample. When a manufacturer takes back expired stock and destroys it (rather than recycling APIs into a new batch where permitted), the ITC on the inputs that went into that stock must be reversed. The reversal is computed proportionately based on the inputs traceable to the destroyed finished goods. Reconciliation must hold the destruction certificate, the batch traceability to the API and excipient inputs, the original input GST credit, and the reversal entry in GSTR-3B for the period of destruction. GST law on this point is unchanged by the Income Tax Act 2025.",
          "article": "Pharmaceutical Distributor and Expired Stock Return Reconciliation",
          "url": "https://www.terra-insight.com/insights/pharma-distributor-return-reconciliation-india"
        },
        {
          "q": "How is insurance claim handled on damaged stock?",
          "a": "Damaged stock — physical damage in transit, fire / flood / spoilage at distributor warehouse, regulatory recall destruction — is typically covered under the manufacturer's product liability or distribution insurance, with the distributor often holding parallel cover for in-warehouse damage. Insurance reconciliation runs at the claim level: damaged-stock manifest, distributor declaration, surveyor report, claim amount, GST treatment on claim receipt (insurance proceeds are generally outside GST), and ITC reversal under Section 17(5)(h) on the destroyed inputs. The accounting boundary matters — the claim receipt and the inventory destruction must reconcile to the same physical stock event without double-counting.",
          "article": "Pharmaceutical Distributor and Expired Stock Return Reconciliation",
          "url": "https://www.terra-insight.com/insights/pharma-distributor-return-reconciliation-india"
        },
        {
          "q": "What is the tax treatment of CSR-donated expired stock?",
          "a": "Some pharma manufacturers donate near-expiry stock to government hospitals, NGOs or registered charitable trusts under Section 135 of the Companies Act CSR framework — provided the stock has adequate remaining shelf life under regulatory norms (typically 6 months minimum for hospital use). The donation is treated as a free supply under GST — and Section 17(5)(h) blocks ITC on goods disposed of by gift. The Income Tax Act treatment of the donation as a CSR contribution allows deduction under Section 80G for eligible recipients, subject to the Section 80G limits and the CSR-eligibility test under Section 135. Reconciliation must hold the donation manifest, the recipient's 80G certificate where applicable, the ITC reversal entry, and the CSR ledger tagging for compliance with the 2% spend mandate.",
          "article": "Pharmaceutical Distributor and Expired Stock Return Reconciliation",
          "url": "https://www.terra-insight.com/insights/pharma-distributor-return-reconciliation-india"
        },
        {
          "q": "What is the role of NPPA and DPCO 2013 in pharmaceutical AP reconciliation?",
          "a": "The National Pharmaceutical Pricing Authority (NPPA) administers the Drug Price Control Order 2013 (DPCO 2013), which caps the ceiling price of scheduled formulations listed in the National List of Essential Medicines (NLEM). For any scheduled drug a manufacturer sells, the maximum retail price cannot exceed the NPPA-notified ceiling plus permitted local taxes. From an AP and reconciliation standpoint, the finance team must back-calculate margins by working from the NPPA ceiling backwards through trade discount, distributor margin, retailer margin, GST, and net realisation to ensure the invoice price to stockists is consistent with the NPPA ceiling. Overcharging is the single largest enforcement risk and triggers deposit of the overcharged amount plus interest into the Drugs Prices Equalisation Account.",
          "article": "Pharmaceutical Manufacturing Reconciliation in India: NPPA, DPCO, PLI Pharma, Batch Tracing",
          "url": "https://www.terra-insight.com/insights/pharmaceutical-manufacturing-reconciliation-india"
        },
        {
          "q": "What does the PLI Pharma scheme cover and how is reconciliation done?",
          "a": "PLI Pharma is a scheme launched by the Department of Pharmaceuticals with a total outlay of ₹15,000 crore, covering three product categories: Category 1 — biopharmaceuticals, complex generic drugs, patented drugs and orphan drugs; Category 2 — APIs, key starting materials and drug intermediates; Category 3 — in-vitro diagnostic devices and other drugs not covered in Categories 1 and 2. Incentives are disbursed annually on incremental sales above a base year, at rates that step down over the scheme period. Reconciliation builds an annual claim file tying invoice-level sales of eligible products to base-year sales, with HSN / product code mapping confirmed by the Project Management Agency. A separate reconciliation must tie the disbursement received from DoP against the approved claim — disbursements often arrive 6-12 months after claim filing, creating a long-running receivable to track.",
          "article": "Pharmaceutical Manufacturing Reconciliation in India: NPPA, DPCO, PLI Pharma, Batch Tracing",
          "url": "https://www.terra-insight.com/insights/pharmaceutical-manufacturing-reconciliation-india"
        },
        {
          "q": "How does Schedule M GMP affect reconciliation at a formulation plant?",
          "a": "Schedule M of the Drugs and Cosmetics Rules prescribes Good Manufacturing Practice (GMP) requirements that all formulation and API plants must follow. From a reconciliation standpoint, Schedule M mandates batch-level traceability — every batch of finished formulation must be traceable to its API lot, excipient lots, packaging components, and the QC release record. AP reconciliation extends this: each batch of finished goods must reconcile to the BOM consumption of APIs and excipients, the GRN and invoice of those input lots, and the QC pass/fail record. A batch released without a complete BOM-to-invoice trail is a Schedule M finding, not just an accounting gap.",
          "article": "Pharmaceutical Manufacturing Reconciliation in India: NPPA, DPCO, PLI Pharma, Batch Tracing",
          "url": "https://www.terra-insight.com/insights/pharmaceutical-manufacturing-reconciliation-india"
        },
        {
          "q": "How is R&D AP separated from production AP at an Indian pharma manufacturer?",
          "a": "R&D expenses are accounted under a separate cost centre and often qualify for weighted deduction under Section 35(2AB) of the Income Tax Act 2025 (transitioning from the legacy regime) for in-house R&D approved by DSIR. AP reconciliation must tag every invoice — clinical trial CRO fees, lab consumables, reference standards, animal studies, regulatory filing fees — to R&D or to production at the point of GRN. The GST ITC eligibility differs (R&D consumables generally claim ITC; clinical-trial CRO fees often follow Section 17(5) rules depending on the contract structure). Mis-tagging an R&D invoice as production inventory inflates COGS and understates the Section 35(2AB) weighted deduction claim — a permanent tax cost.",
          "article": "Pharmaceutical Manufacturing Reconciliation in India: NPPA, DPCO, PLI Pharma, Batch Tracing",
          "url": "https://www.terra-insight.com/insights/pharmaceutical-manufacturing-reconciliation-india"
        },
        {
          "q": "Which Section 393 TDS codes apply to pharma manufacturers?",
          "a": "Three Section 393 codes carry most of the pharma TDS exposure. Section 393(1)(b) (payment code 1003, replaces 194J) applies at 10% on technical or medical service fees — common for clinical trial principal investigator fees, medical advisory retainer payments, and certain CRO scopes. Section 393(1)(k) (code 1012, replaces 194Q) applies at 0.1% on resident-vendor purchases above ₹50 lakh aggregate per PAN per year — relevant for high-value API procurement from domestic suppliers. Section 393(1)(a) (code 1002, replaces 194C) applies on contract manufacturing and toll-blending arrangements at 1% (individual/HUF) or 2% (company/firm). Each code requires a separate monthly challan deposit by the 7th of the following month.",
          "article": "Pharmaceutical Manufacturing Reconciliation in India: NPPA, DPCO, PLI Pharma, Batch Tracing",
          "url": "https://www.terra-insight.com/insights/pharmaceutical-manufacturing-reconciliation-india"
        },
        {
          "q": "What is three-way matching in an Indian manufacturing context?",
          "a": "Three-way matching is the AP control where a vendor invoice is matched against the purchase order (the commercial agreement) and the goods receipt note (the physical receipt at the factory) before payment is released. In an Indian manufacturing context the match must also reconcile GST inclusive/exclusive treatment, Section 393(1)(k) TDS deduction on purchases above ₹50 lakh aggregate per PAN, and MSME 43B(h) payment-window flags. A clean match means PO quantity ≈ GRN quantity ≈ invoice quantity within tolerance, PO rate ≈ invoice rate within tolerance, vendor PAN/GSTIN matches the master, and GST is correctly inclusive or exclusive per PO terms.",
          "article": "PO-GRN-Invoice Three-Way Matching in India: The 60-75% AP Exception Problem",
          "url": "https://www.terra-insight.com/insights/po-grn-invoice-three-way-matching-india"
        },
        {
          "q": "Why are AP exception rates so high at Indian manufacturers — 60% or more?",
          "a": "Industry surveys and published CFO commentary at mid-size Indian manufacturers consistently report 60-75% of vendor invoices going into an exception queue at some stage when three-way matching is done on spreadsheets or with ERP-default tolerance settings. The four dominant drivers are: price tolerance breaches (vendor invoices ₹128/kg against PO of ₹125/kg with no documented tolerance band), partial-delivery GRN drift (invoice arrives before final GRN is closed), GST-inclusion confusion (PO drawn excluding GST, invoice raised inclusive at 18% or 12%), and vendor-master mismatches (PAN or GSTIN on invoice differs from what is on file). Structured matching engines that encode tolerance bands per item category typically reduce exceptions to under 15%.",
          "article": "PO-GRN-Invoice Three-Way Matching in India: The 60-75% AP Exception Problem",
          "url": "https://www.terra-insight.com/insights/po-grn-invoice-three-way-matching-india"
        },
        {
          "q": "What tolerance bands are typically used for three-way matching in India?",
          "a": "Common practice at Indian manufacturers is a price tolerance band of 0% to 5% (commonly 2-3% for raw materials, tighter for traded items), a quantity tolerance band of 0% to 3% (often zero for high-value capital items), and a 0% GST tolerance — any GST variance is a hard exception because it directly affects ITC claim and Section 17(5) exposure. Tolerance bands should be configured per item category, not globally, because a 5% price band that is acceptable on steel scrap is unacceptable on a precision-engineered component.",
          "article": "PO-GRN-Invoice Three-Way Matching in India: The 60-75% AP Exception Problem",
          "url": "https://www.terra-insight.com/insights/po-grn-invoice-three-way-matching-india"
        },
        {
          "q": "How does Section 393(1)(k) TDS affect three-way matching?",
          "a": "Section 393(1)(k) of the Income Tax Act 2025 (which replaced legacy Section 194Q) requires a buyer with turnover above ₹10 crore to deduct 0.1% TDS on purchases exceeding ₹50 lakh aggregate per resident seller in a financial year, using payment code 1012. This affects three-way matching because the invoice net payable must be reduced by the TDS amount, and a year-to-date purchase tracker per vendor PAN must flag the threshold crossing. Most exception queues miss this until the quarterly TDS return — and recovering excess paid is harder than deducting at source.",
          "article": "PO-GRN-Invoice Three-Way Matching in India: The 60-75% AP Exception Problem",
          "url": "https://www.terra-insight.com/insights/po-grn-invoice-three-way-matching-india"
        },
        {
          "q": "What is a realistic exception-rate target post-implementation of three-way matching software?",
          "a": "A realistic target after implementing structured three-way matching software at an Indian manufacturer is to push exceptions from the 60-75% industry norm to under 15% within 90 days of go-live. The residual 10-15% is typically genuine commercial dispute (rate negotiation in progress, partial-delivery legitimately split across cycles, quality holds awaiting QC sign-off) which requires human resolution. The customer outcomes published for purpose-built tools show match rates improving from 51% to 88% across the broader reconciliation surface.",
          "article": "PO-GRN-Invoice Three-Way Matching in India: The 60-75% AP Exception Problem",
          "url": "https://www.terra-insight.com/insights/po-grn-invoice-three-way-matching-india"
        },
        {
          "q": "What is SAP's standard 3-way match logic in MM-FI?",
          "a": "SAP runs three-way match through the GR/IR (Goods Received / Invoice Received) clearing account. When a purchase order is created in MM, no accounting entry is posted. When goods are received against the PO (transaction MIGO), the system debits inventory (or expense) and credits GR/IR clearing at the PO rate × GRN quantity. When the vendor invoice is posted (transaction MIRO), the system debits GR/IR clearing and credits the vendor account at the invoice rate × invoice quantity. If PO rate × GRN quantity equals invoice rate × invoice quantity, GR/IR clearing nets to zero — a clean three-way match. If there is a price or quantity mismatch, GR/IR carries an open balance that surfaces in the GR/IR balance report (transaction MB5S) for resolution.",
          "article": "SAP MM-FI Three-Way Match Reconciliation for Indian Manufacturing: Configuration and Common Gaps",
          "url": "https://www.terra-insight.com/insights/sap-mm-fi-three-way-match-reconciliation-india"
        },
        {
          "q": "What are the main India-specific configuration gaps in SAP standard 3-way match?",
          "a": "Five gaps dominate. First, GST inclusive versus exclusive treatment on the PO versus the invoice — SAP's standard tax procedure (TAXINN) handles this with tax codes but requires careful PO-line tax code defaults to avoid mismatches. Second, TDS posting timing — SAP can post withholding tax at invoice booking (typical for Section 393 contractor payments) or at payment, and the configuration must align to the manufacturer's Section 393 policy. Third, J1IGN and the India-specific transaction set for stock issues, capital goods transfers, and depot stock — these sit outside the standard MIGO/MIRO flow. Fourth, OBYC account determination for GR/IR — the wrong account assignment maps GR/IR to the incorrect GL by valuation class. Fifth, cross-GSTIN consolidation when one company code carries multiple plant GSTINs that file separate GST returns.",
          "article": "SAP MM-FI Three-Way Match Reconciliation for Indian Manufacturing: Configuration and Common Gaps",
          "url": "https://www.terra-insight.com/insights/sap-mm-fi-three-way-match-reconciliation-india"
        },
        {
          "q": "How does SAP handle GST on PO versus GST on invoice for Indian manufacturers?",
          "a": "SAP uses the TAXINN tax procedure for India with condition records that map vendor + plant + material + tax classification to a specific GST tax code. At PO creation, the buyer selects the tax code (IGST, CGST+SGST, or exempt) based on the supply combination. At MIRO invoice posting, the invoice tax code should match the PO tax code; if it does not, an exception is raised. The common gap is when the vendor's invoice carries a different tax code (for example IGST charged when the PO defaulted to CGST+SGST due to a plant master GSTIN mismatch) — SAP standard will let the user override at MIRO, but the override breaks the three-way match because the GR/IR posting was at the PO tax code. A separate India-localised reconciliation layer is usually required to catch this before payment release.",
          "article": "SAP MM-FI Three-Way Match Reconciliation for Indian Manufacturing: Configuration and Common Gaps",
          "url": "https://www.terra-insight.com/insights/sap-mm-fi-three-way-match-reconciliation-india"
        },
        {
          "q": "How is TDS under Section 393 handled in SAP for Indian manufacturers?",
          "a": "SAP's withholding tax functionality (configured per country in transaction OBWO and assigned per vendor master) handles TDS at either invoice booking or payment posting, depending on the withholding tax type configuration. For Section 393(1)(a) contractor payments (replacing 194C, payment code 1002), most manufacturers configure TDS at invoice booking — the vendor's payable line at MIRO is net of TDS, and the TDS payable line credits the income tax liability account. The post-cutover challenge from FY 2026-27 is the payment code remapping: the WHT types must be reconfigured from the old 194-series codes to the new Section 393 codes (1001-1092), and the Form 27Q quarterly return logic must point at the new section reference. Older transactions before 1 April 2026 keep the legacy 194-series code reference for cross-era Form 26AS matching.",
          "article": "SAP MM-FI Three-Way Match Reconciliation for Indian Manufacturing: Configuration and Common Gaps",
          "url": "https://www.terra-insight.com/insights/sap-mm-fi-three-way-match-reconciliation-india"
        },
        {
          "q": "Where does SAP standard three-way match fall short for Indian manufacturers, and what fills the gap?",
          "a": "SAP standard handles the rate-and-quantity three-way match cleanly through GR/IR. It does not natively handle: (1) GST inclusive versus exclusive consistency checks at PO-versus-invoice level; (2) cross-GSTIN consolidation when one company code spans multiple plant GSTINs; (3) Section 17(5) blocked credit flagging at MIRO (SAP knows the tax code but does not know the blocking rule by material type); (4) multi-EPN handling where a single invoice carries multiple e-invoice references; (5) J1IS challan numbering for India excise-era stock movement (still in use for some configurations); (6) retroactive TDS rate change handling for prior-period invoices; (7) cross-era Section 393 code mapping during the FY 2025-26 to FY 2026-27 cutover. A purpose-built reconciliation layer sitting alongside SAP MM-FI fills these gaps with India-specific rule sets, surfacing exceptions that SAP standard would let through.",
          "article": "SAP MM-FI Three-Way Match Reconciliation for Indian Manufacturing: Configuration and Common Gaps",
          "url": "https://www.terra-insight.com/insights/sap-mm-fi-three-way-match-reconciliation-india"
        },
        {
          "q": "Is GST applicable on stock transfers between two locations of the same company in India?",
          "a": "It depends on whether the two locations share a GSTIN. A stock transfer between two locations of the same company within the same state, operating under the same GSTIN, attracts no GST — the movement is treated as a delivery challan transaction, not a supply. A stock transfer between two locations of the same company operating under different GSTINs — whether inter-state or intra-state with separate registrations — is deemed a supply under Schedule I of the CGST Act, attracts IGST (inter-state) or CGST+SGST (intra-state with separate registrations), and must be invoiced as a stock-transfer invoice and reported in GSTR-1 of the sending GSTIN.",
          "article": "Stock Transfer Reconciliation in India: Intra-State, Inter-State, and Branch Transfer Mechanics",
          "url": "https://www.terra-insight.com/insights/stock-transfer-reconciliation-india"
        },
        {
          "q": "What is the e-way bill threshold for stock transfers in India?",
          "a": "An e-way bill is mandatory for any single consignment of goods with a value above ₹50,000 that moves on inter-state lines, and on intra-state lines in most states (a few states use ₹1 lakh for intra-state). The threshold is per consignment, not per day or per vendor. Stock transfers between plants of a multi-GSTIN manufacturer must generate an e-way bill before the truck leaves the sending plant gate, with the receiving plant's GSTIN as consignee. The e-way bill number must be retrievable later for reconciliation against the inbound GRN and the GSTR-1 outward entry.",
          "article": "Stock Transfer Reconciliation in India: Intra-State, Inter-State, and Branch Transfer Mechanics",
          "url": "https://www.terra-insight.com/insights/stock-transfer-reconciliation-india"
        },
        {
          "q": "How does Schedule I of the CGST Act treat stock transfers between distinct persons?",
          "a": "Schedule I lists activities treated as supply even when made without consideration. Entry 2 of Schedule I covers supply of goods or services between related persons or between distinct persons (as defined in Section 25), when made in the course or furtherance of business. A multi-GSTIN manufacturer is a single legal entity but each GSTIN is a 'distinct person' for GST purposes, so any movement of goods between two GSTINs of the same company is a deemed supply, requires a tax invoice and triggers IGST or CGST+SGST as applicable.",
          "article": "Stock Transfer Reconciliation in India: Intra-State, Inter-State, and Branch Transfer Mechanics",
          "url": "https://www.terra-insight.com/insights/stock-transfer-reconciliation-india"
        },
        {
          "q": "What is the difference between a delivery challan and a stock-transfer invoice?",
          "a": "A delivery challan under Rule 55 is used to move goods without an immediate supply event — for example, goods sent for job-work, goods sent on approval, goods moved within the same GSTIN. No GST is charged on the challan. A stock-transfer invoice is a full tax invoice raised when goods move between two distinct GSTINs of the same legal entity, with IGST or CGST+SGST charged at the applicable rate. The sending GSTIN reports the invoice in GSTR-1; the receiving GSTIN claims the ITC after the invoice flows into its GSTR-2B.",
          "article": "Stock Transfer Reconciliation in India: Intra-State, Inter-State, and Branch Transfer Mechanics",
          "url": "https://www.terra-insight.com/insights/stock-transfer-reconciliation-india"
        },
        {
          "q": "How do ITC implications differ when sending stock to a different GSTIN of the same company?",
          "a": "When a Maharashtra plant sends finished goods to a Karnataka plant of the same company under different GSTINs, the Maharashtra GSTIN charges IGST on the stock-transfer invoice and pays it via GSTR-3B; the Karnataka GSTIN claims that IGST as ITC after the invoice appears in its GSTR-2B. There is no net cash-flow loss at the entity level, but there is a working-capital lag of one filing cycle. If the receiving GSTIN cannot fully utilise the inbound ITC against its own outward supplies, accumulated ITC builds up and must be tracked for refund eligibility under Section 54 of the CGST Act.",
          "article": "Stock Transfer Reconciliation in India: Intra-State, Inter-State, and Branch Transfer Mechanics",
          "url": "https://www.terra-insight.com/insights/stock-transfer-reconciliation-india"
        },
        {
          "q": "How is captive power plant reconciliation done at an integrated steel manufacturer?",
          "a": "A captive power plant (CPP) at an integrated steel facility procures coal under a separate ledger from the steel manufacturing inputs. Coal attracts 5% GST plus the GST Compensation Cess of ₹400 per tonne (where applicable). CPP operating cost — coal, water, manpower, depreciation — is computed monthly and allocated to consuming units (sponge iron kiln, blast furnace, rolling mill) on a metered kWh basis. Reconciliation must tie: coal GRN to coal invoice and GSTR-2B entry; CPP cost build-up to the monthly allocation file; allocated cost to the finished steel costing ledger. Captive consumption of power generated does not attract GST under Schedule III treatment, but the input ITC on CPP capex and consumables follows the inverted-duty treatment because finished steel attracts 18% GST while some CPP inputs are at lower rates.",
          "article": "Steel and Metal Manufacturing Reconciliation in India: Captive Power, Freight In, GST, Scrap TCS",
          "url": "https://www.terra-insight.com/insights/steel-metal-manufacturing-reconciliation-india"
        },
        {
          "q": "How are rail and road freight-in reconciled at a steel plant?",
          "a": "Inbound freight at a steel plant flows through two channels. Rail freight moves on Railway Receipts (RR) and the new Freight Operations Information System (FOIS) records, with GST charged by Indian Railways at 5%. Road freight moves on transporter Lorry Receipts (LR) and e-way bills, with GST treatment depending on whether the GTA (Goods Transport Agency) has opted for 5% under reverse charge (RCM under Section 9(3) CGST) or 12% under forward charge. Reconciliation ties freight invoices to (a) the underlying purchase order or stock-transfer document, (b) the e-way bill in the GSTN system, (c) the GTA RCM self-invoice for reverse-charge cases, and (d) the GRN at the receiving plant. A mismatch between the e-way bill consignor / consignee GSTIN and the freight invoice party flags a fundamental tax-position error.",
          "article": "Steel and Metal Manufacturing Reconciliation in India: Captive Power, Freight In, GST, Scrap TCS",
          "url": "https://www.terra-insight.com/insights/steel-metal-manufacturing-reconciliation-india"
        },
        {
          "q": "How does the GST inverted duty structure work for steel manufacturers?",
          "a": "The GST rate stack in steel manufacturing is uneven. Coal sits at 5% GST plus a compensation cess on certain grades. Iron ore is at 5%. Sponge iron and pig iron move at 18%. Hot-rolled and cold-rolled steel attracts 18%. Coking coal imports attract IGST plus Basic Customs Duty plus social welfare surcharge. The inverted-duty position arises when input GST accumulates faster than output GST — most commonly on coal-heavy plants where the 5% coal credit and capex ITC on plant build-out exceed the 18% output liability for several quarters. Section 54(3) of the CGST Act permits refund of the accumulated ITC under inverted duty, claimed periodically with documentary support tying every input invoice to its GSTR-2B entry and the resulting accumulated credit ledger.",
          "article": "Steel and Metal Manufacturing Reconciliation in India: Captive Power, Freight In, GST, Scrap TCS",
          "url": "https://www.terra-insight.com/insights/steel-metal-manufacturing-reconciliation-india"
        },
        {
          "q": "How is scrap recovery TCS handled at a steel plant under Section 394?",
          "a": "Scrap recovery is a major revenue line at any integrated steel plant — steel turnings and borings, mill scale, slag, dross, runner-and-riser scrap. All these attract TCS under Section 394 of the Income Tax Act 2025 at 1% (payment code 1071), replacing legacy Section 206C(1). The seller (the steel manufacturer) collects the TCS from the buyer at the time of debiting the buyer's account or receipt, whichever is earlier. The four-leg reconciliation is: scrap sale ledger, TCS collected ledger, the quarterly TCS return, and the bank receipt from the scrap buyer. Where the buyer holds a declaration of further manufacturing under the original Section 206C(1A) framework (transitioned), the TCS may not be collected but the declaration must be on file before the sale invoice is raised.",
          "article": "Steel and Metal Manufacturing Reconciliation in India: Captive Power, Freight In, GST, Scrap TCS",
          "url": "https://www.terra-insight.com/insights/steel-metal-manufacturing-reconciliation-india"
        },
        {
          "q": "When does Section 393(1)(k) purchase TDS apply at a steel manufacturer?",
          "a": "Section 393(1)(k) of the Income Tax Act 2025 (payment code 1012, replaces 194Q) applies at 0.1% on resident-vendor purchases above ₹50 lakh aggregate per vendor PAN per year, where the buyer's turnover crossed ₹10 crore in the preceding year. For a steel manufacturer this typically engages on iron ore, coking coal (domestic procurement), limestone and dolomite fluxes, refractories, ferro-alloys, and oxygen / industrial gases. The control is a year-to-date purchase counter per vendor PAN with automatic deduction trigger at the ₹50 lakh crossing. A vendor under coverage of Section 394 TCS on the same product (sale of certain minerals by a seller to a buyer) takes precedence — the same transaction cannot have both TCS collected by seller and TDS deducted by buyer.",
          "article": "Steel and Metal Manufacturing Reconciliation in India: Captive Power, Freight In, GST, Scrap TCS",
          "url": "https://www.terra-insight.com/insights/steel-metal-manufacturing-reconciliation-india"
        },
        {
          "q": "What does Section 143 of the CGST Act allow a principal manufacturer to do?",
          "a": "Section 143 of the CGST Act allows a registered principal to send inputs or capital goods to a job-worker for further processing without paying GST on the dispatch, subject to two statutory windows — inputs must return (or be supplied from the job-worker's premises) within one year, capital goods within three years (jigs, fixtures, moulds and dies are exempt from the return clock). The dispatch moves on a delivery challan under Rule 45 of the CGST Rules with sender GSTIN, receiver job-worker details, description of goods and quantity. If the goods do not return within the statutory window, the original dispatch is deemed a supply on the date of original despatch and triggers GST liability with interest.",
          "article": "Sub-Contractor and Job Work Reconciliation Under Section 143 of CGST Act",
          "url": "https://www.terra-insight.com/insights/subcontractor-job-work-reconciliation-section-143"
        },
        {
          "q": "What is the ITC-04 return and when must it be filed?",
          "a": "ITC-04 is the statutory return that captures the movement of inputs and capital goods between the principal and the job-worker. It is filed on a quarterly basis for principals with aggregate turnover above ₹5 crore (annually for principals up to ₹5 crore). The return captures opening balance with job-worker, goods sent during the quarter, goods returned during the quarter, goods supplied from job-worker premises during the quarter, and closing balance with job-worker. The reconciliation between the principal's challan register and ITC-04 is the primary statutory control on the job-work rail.",
          "article": "Sub-Contractor and Job Work Reconciliation Under Section 143 of CGST Act",
          "url": "https://www.terra-insight.com/insights/subcontractor-job-work-reconciliation-section-143"
        },
        {
          "q": "What happens if inputs sent to a job-worker are not returned within one year?",
          "a": "Under Section 143(3) of the CGST Act, if inputs sent to a job-worker do not return to the principal (or are not supplied from the job-worker's premises) within one year of dispatch, the original dispatch is deemed to be a supply on the date the goods were originally sent. The principal must pay GST on the value of the deemed supply with interest under Section 50 from the original dispatch date. The 18% interest accrual makes early detection of approaching-window challans a high-value reconciliation control. The three-year window applies to capital goods under Section 143(4).",
          "article": "Sub-Contractor and Job Work Reconciliation Under Section 143 of CGST Act",
          "url": "https://www.terra-insight.com/insights/subcontractor-job-work-reconciliation-section-143"
        },
        {
          "q": "How does TDS apply to job-work charges paid to a sub-contractor?",
          "a": "Job-work charges paid to a sub-contractor fall under Section 393(1)(a) of the Income Tax Act 2025, which replaces legacy Section 194C. The TDS payment code is 1002. Rates are 1% for individual or HUF job-workers and 2% for company or firm job-workers, applied to the labour and processing charges (not on the value of inputs that are anyway owned by the principal). The per-transaction threshold is ₹30,000 and the aggregate threshold is ₹1 lakh per financial year. The deduction must be deposited to the central government by the 7th of the following month (30 April for March) and reflected in the job-worker's Form 26AS or AIS.",
          "article": "Sub-Contractor and Job Work Reconciliation Under Section 143 of CGST Act",
          "url": "https://www.terra-insight.com/insights/subcontractor-job-work-reconciliation-section-143"
        },
        {
          "q": "Can a job-worker supply finished goods directly from their premises to a customer?",
          "a": "Yes — Section 143(1)(b) of the CGST Act permits direct supply from the job-worker's premises, subject to two conditions. First, the job-worker must be a registered person, or the principal must declare the job-worker's premises as an additional place of business in the principal's GST registration. Second, the supply is treated as made by the principal — invoice raised by the principal, GST charged by the principal, reported in the principal's GSTR-1. The reconciliation must tie the job-worker's despatch document to the principal's outward invoice and the buyer's GRN, with the original challan from principal to job-worker matched against the supply event rather than a return movement.",
          "article": "Sub-Contractor and Job Work Reconciliation Under Section 143 of CGST Act",
          "url": "https://www.terra-insight.com/insights/subcontractor-job-work-reconciliation-section-143"
        },
        {
          "q": "What is a works contract under Indian GST law?",
          "a": "A works contract is defined under Section 2(119) of the CGST Act, 2017 as a contract for building, construction, fabrication, completion, erection, installation, fitting out, improvement, modification, repair, maintenance, renovation, alteration or commissioning of any immovable property wherein the transfer of property in goods (whether as goods or in some other form) is involved in the execution of such contract. The defining feature is that it applies only to immovable property and that it is a composite supply of both goods and services — taxed as a service under Schedule II of the CGST Act. Contracts involving movable property (such as fabrication of machinery delivered as goods) are not works contracts and follow normal goods or composite supply rules.",
          "article": "Works Contract Reconciliation in India: Composite Supply, GST 12% vs 18%, and AP Treatment",
          "url": "https://www.terra-insight.com/insights/works-contract-reconciliation-india"
        },
        {
          "q": "When does a works contract attract GST at 12% versus 18%?",
          "a": "The standard GST rate on works contract services is 18%. A concessional 12% rate applies to specified categories notified by the government — including affordable housing projects meeting the carpet area and price criteria, certain government infrastructure works (road, bridge, water supply, sewerage), historical monuments, and works contracts executed for specified entities such as government departments, local authorities or governmental authorities for non-commercial use. The contractor must apply the rate based on the project category certified in the contract; mis-classification (charging 12% where 18% applies, or vice versa) creates either an ITC reversal exposure for the manufacturer or a recovery dispute with the contractor. Reconciliation must verify the rate against the contract category before the AP team releases the running account bill.",
          "article": "Works Contract Reconciliation in India: Composite Supply, GST 12% vs 18%, and AP Treatment",
          "url": "https://www.terra-insight.com/insights/works-contract-reconciliation-india"
        },
        {
          "q": "Can a manufacturer claim ITC on works contract services?",
          "a": "Section 17(5)(c) and (d) of the CGST Act block input tax credit on works contract services and goods/services used for construction of an immovable property (other than plant and machinery) when consumed for own account. So a manufacturer doing a factory shed construction, office building expansion or warehouse renovation for own use cannot claim ITC on the contractor's GST — that GST becomes a cost. The exception is plant and machinery (foundation, structural support, capitalised as P&M under accounting standards), where ITC is allowed. The reconciliation flag must classify each works contract bill into either blocked (building/civil) or allowed (plant and machinery foundation) buckets, because mis-claimed ITC unwound after the September following the financial year attracts 18% interest.",
          "article": "Works Contract Reconciliation in India: Composite Supply, GST 12% vs 18%, and AP Treatment",
          "url": "https://www.terra-insight.com/insights/works-contract-reconciliation-india"
        },
        {
          "q": "Which TDS section applies to works contract bills paid by a manufacturer?",
          "a": "Works contract payments to a contractor fall under Section 393(1)(a) of the Income Tax Act 2025 (replacing legacy Section 194C), with TDS payment code 1002. The rate is 1% for individual or HUF contractors and 2% for company, firm, LLP or other non-individual contractors. Thresholds remain at ₹30,000 per single payment and ₹1 lakh aggregate per contractor per financial year. The TDS must be deducted on the bill value excluding GST (when GST is separately charged on the invoice) and deposited through the monthly challan by the 7th of the following month. Reconciliation ties the works contract ledger, the TDS deducted ledger, the contractor's PAN, and the quarterly Form 26Q return.",
          "article": "Works Contract Reconciliation in India: Composite Supply, GST 12% vs 18%, and AP Treatment",
          "url": "https://www.terra-insight.com/insights/works-contract-reconciliation-india"
        },
        {
          "q": "How do retention money and mobilisation advance complicate works contract reconciliation?",
          "a": "A typical works contract running account (RA) bill has three commercial adjustments before the net payable: retention deduction (commonly 5-10% of the bill value, held back as security until project completion or defect liability period expiry), mobilisation advance recovery (a percentage of the bill value adjusted against the upfront mobilisation advance the contractor received, until fully recovered), and any material supplied by the manufacturer (cement, steel) deducted at agreed rates. GST and TDS apply on the gross bill, not on the net payable — a frequent reconciliation error. Tracking each contract's running totals of retention held, mobilisation balance, and material recovery across multiple RA bills over 12-24 months is where most works contract AP queues fail. See our retention money pattern for the structured approach.",
          "article": "Works Contract Reconciliation in India: Composite Supply, GST 12% vs 18%, and AP Treatment",
          "url": "https://www.terra-insight.com/insights/works-contract-reconciliation-india"
        }
      ]
    },
    "automotive-components": {
      "label": "Automotive Component Reconciliation",
      "faqs": [
        {
          "q": "What is RoDTEP and how is the e-scrip reconciled by an auto component exporter?",
          "a": "RoDTEP — Remission of Duties and Taxes on Exported Products — remits embedded central, state and local duties and taxes that are not otherwise refunded, on exported goods. The benefit is granted as a transferable electronic scrip (e-scrip) credited to the exporter's ledger in the ICEGATE customs system, computed as a percentage of FOB value at a rate that varies by HS code (most auto-component HS lines fall in a low single-digit percentage band, subject to a per-unit value cap). Reconciliation ties three things: the RoDTEP entitlement claimed in the shipping bill (per HS code on FOB value), the e-scrip actually credited to the ledger, and the realisation of that scrip — either used to pay basic customs duty on imports or sold to another importer in the scrip market. A gap between claimed and credited scrip is the core RoDTEP control.",
          "article": "Auto Component Export Incentive Reconciliation: RoDTEP, EPCG, Advance Authorization, SEZ",
          "url": "https://www.terra-insight.com/insights/auto-component-export-incentive-reconciliation-india"
        },
        {
          "q": "How does EPCG export-obligation reconciliation work?",
          "a": "Under the Export Promotion Capital Goods (EPCG) scheme, an exporter imports capital goods — presses, CNC machines, moulds, testing equipment — at zero or concessional customs duty, against an export obligation (EO) equal to six times the duty saved, to be fulfilled over six years. Reconciliation tracks the EO in two layers: the total EO against the duty saved, and the block-wise milestones (typically 50% in the first block of four years and the balance in the next two years), plus an average-export-obligation maintenance requirement based on past exports. Each export shipment is tagged to the EPCG authorisation and counted toward the EO. Shortfall at a block boundary triggers proportionate duty plus interest, so the running EO-fulfilled-versus-EO-required position is the central reconciliation.",
          "article": "Auto Component Export Incentive Reconciliation: RoDTEP, EPCG, Advance Authorization, SEZ",
          "url": "https://www.terra-insight.com/insights/auto-component-export-incentive-reconciliation-india"
        },
        {
          "q": "What is Advance Authorization and how do SION norms enter the reconciliation?",
          "a": "Advance Authorization lets an exporter import inputs duty-free against an export obligation to use those inputs in exported products. The permitted input quantity is governed by Standard Input-Output Norms (SION) — published input-to-output ratios per product, or, where no SION exists, a self-declared or fixed norm. Reconciliation has to prove that the duty-free inputs imported under each authorisation were actually consumed in the exports against which the authorisation was issued, within the SION ratio — input consumed must not exceed the SION-permitted quantity for the exported output. Excess imports over SION, or under-export against the authorisation, create a duty-and-interest liability and block authorisation redemption. The SION input-output reconciliation per authorisation is the key control.",
          "article": "Auto Component Export Incentive Reconciliation: RoDTEP, EPCG, Advance Authorization, SEZ",
          "url": "https://www.terra-insight.com/insights/auto-component-export-incentive-reconciliation-india"
        },
        {
          "q": "How are supplies to an SEZ unit or EOU treated, and what refund applies?",
          "a": "A supply of goods to an SEZ unit or developer is a zero-rated supply under the IGST Act, and a supply to an Export Oriented Unit (EOU) is a deemed export under the Foreign Trade Policy. For zero-rated supplies the supplier can either export under bond/LUT without paying IGST and claim refund of accumulated input tax credit, or pay IGST and claim refund of the IGST paid — both routes under Section 16 of the IGST Act read with Section 54 of the CGST Act. Reconciliation ties the zero-rated outward supply (in GSTR-1, with the SEZ/EOU GSTIN and the LUT/bond reference), the IGST or ITC refund claim filed, and the refund actually sanctioned and credited. Refund lag between claim and sanction is the main working-capital control here.",
          "article": "Auto Component Export Incentive Reconciliation: RoDTEP, EPCG, Advance Authorization, SEZ",
          "url": "https://www.terra-insight.com/insights/auto-component-export-incentive-reconciliation-india"
        },
        {
          "q": "When does Section 413 code 1062 TDS apply to an auto component exporter?",
          "a": "Section 413 of the Income Tax Act 2025, payment code 1062, governs withholding on payments to non-residents — replacing legacy Section 195. For an auto component exporter, this commonly arises on commission paid to a foreign sales agent or buying house that sources orders abroad. The exporter must determine whether the commission is chargeable to tax in India (often it is not, where the agent operates wholly outside India with no business connection or permanent establishment, subject to the relevant DTAA and a tax-residency certificate), and withhold under Section 413 code 1062 where chargeable. The reconciliation ties the foreign agent commission booked, the withholding applied (or the no-PE / DTAA position documented with Form 15CA/15CB), the FIRC/BRC on the underlying export realisation, and the RBI A2 remittance for the commission payout.",
          "article": "Auto Component Export Incentive Reconciliation: RoDTEP, EPCG, Advance Authorization, SEZ",
          "url": "https://www.terra-insight.com/insights/auto-component-export-incentive-reconciliation-india"
        },
        {
          "q": "What is a line rejection and how does it become a quality debit note?",
          "a": "A line rejection happens when a supplied part is found defective at the OEM assembly line — it fails an inspection, does not fit, or causes a build fault — and is pulled out of production. The OEM logs the rejected quantity against the supplier with a rejection slip or quality notification number, and raises a quality debit note for the part value plus any associated cost (line-stop time, expediting, sorting). The debit is deducted from the supplier's running settlement. Reconciliation must match each quality debit to a rejection slip ID and then to the supplier's own internal rejection/return record, because the part value, the replacement obligation and the GST treatment all hang off whether the supplier accepts or contests the rejection.",
          "article": "Line Rejection and PPM Quality Debit Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/auto-line-rejection-ppm-quality-debit-reconciliation-india"
        },
        {
          "q": "How does a PPM penalty work and when is it charged?",
          "a": "PPM — parts per million — measures defect rate: defective parts found per million supplied. The contract sets a PPM threshold per part or per supplier (commonly tens of PPM for a mature programme). When the rolling defect rate breaches the threshold, the OEM applies a contractual PPM penalty, often a graduated charge that rises as the breach widens, sometimes alongside a supplier-rating downgrade that affects new-business allocation. The penalty is separate from the per-part value of the rejected pieces. Reconciliation must compute the supplier's own PPM from its rejection records, compare it to the OEM's asserted PPM, and validate the penalty calculation against the contractual band before accepting the debit.",
          "article": "Line Rejection and PPM Quality Debit Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/auto-line-rejection-ppm-quality-debit-reconciliation-india"
        },
        {
          "q": "What is an 8D and how does it relate to the quality debit?",
          "a": "An 8D (Eight Disciplines) is the structured corrective-action report the OEM demands when a quality problem occurs — it walks through containment, root cause, corrective action and prevention across eight defined steps. The 8D is the technical document; the quality debit note is the commercial document. They are linked by the same quality notification ID. The OEM may hold or escalate the financial debit until the 8D is closed, and a poorly closed 8D can lead to repeat rejections and a widening PPM breach. Reconciliation should cross-reference each open quality debit to its 8D status so that finance and quality are working the same claim ID rather than two disconnected lists.",
          "article": "Line Rejection and PPM Quality Debit Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/auto-line-rejection-ppm-quality-debit-reconciliation-india"
        },
        {
          "q": "How are sorting and rework back-charges reconciled?",
          "a": "When a defect is found, the OEM often deploys a resident supplier engineer or a third-party sorting agency to 100% inspect suspect stock at the line, and back-charges the supplier for the sorting hours, the agency fee and any rework or scrap. This sorting back-charge is separate from both the per-part value and the PPM penalty, and it can be large when a containment runs across multiple days and plants. Reconciliation must match the sorting back-charge to the sorting authorisation, the agency timesheet/invoice and the quantity sorted, and confirm it ties to the same quality notification as the rejection — otherwise a supplier can be charged sorting cost for an event it never authorised or that belongs to another supplier.",
          "article": "Line Rejection and PPM Quality Debit Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/auto-line-rejection-ppm-quality-debit-reconciliation-india"
        },
        {
          "q": "What is the GST treatment when rejected parts are returned and replaced?",
          "a": "When the OEM returns rejected parts, the correct GST mechanism is a supplier-issued credit note under Section 34 of the CGST Act for the value (and GST) of the returned goods, reducing the supplier's output liability provided it is issued within the window (until 30 November of the following financial year or the annual return, whichever is earlier) and the OEM reverses the matching ITC. The replacement dispatch is a fresh supply with its own tax invoice, e-invoice and e-way bill. A PPM penalty or a sorting back-charge, by contrast, is generally a commercial damages/service recovery rather than a price reduction on goods — its GST treatment depends on how the contract characterises it, and reconciliation must not net it against the goods credit note.",
          "article": "Line Rejection and PPM Quality Debit Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/auto-line-rejection-ppm-quality-debit-reconciliation-india"
        },
        {
          "q": "How does a Tier 2 auto-component supplier reconcile against an OEM short-pay routed through a Tier 1?",
          "a": "The Tier 2 invoices the Tier 1 directly — there is no privity of contract with the OEM. When the OEM short-pays the Tier 1 for a quality issue traced to the Tier 2's part, the Tier 1 issues a debit note against the Tier 2's account citing the back-charge code and the OEM's debit reference. Reconciliation must tie three documents — the OEM's debit note to the Tier 1, the Tier 1's debit note to the Tier 2, and the Tier 2's original invoice — by part number, vehicle programme and warranty claim ID. Without that three-way link the Tier 2 cannot dispute the back-charge or claim recovery from sub-tier suppliers.",
          "article": "Automotive Component Manufacturing Reconciliation in India: OEM Settlement, PLI Auto, JIT/Kanban Returns",
          "url": "https://www.terra-insight.com/insights/automotive-component-manufacturing-reconciliation-india"
        },
        {
          "q": "How is PLI Auto incentive disbursement reconciled at a component manufacturer?",
          "a": "The PLI Auto scheme, with a ₹26,058 crore outlay over a five-year tenure, releases incentive against incremental sales above a base year, weighted by value-add criteria. The disbursement comes as a single bank credit per quarter from MoHI's nominated agency after the value-add audit closes. Reconciliation ties the audited eligible sales figure to the incentive percentage band claimed (typically 8% to 18% based on value-add) to the actual bank credit, with the GST treatment booked as a subsidy not chargeable to GST in most interpretations. Any difference between claim and credit is logged as a PLI variance for the next quarter's appeal.",
          "article": "Automotive Component Manufacturing Reconciliation in India: OEM Settlement, PLI Auto, JIT/Kanban Returns",
          "url": "https://www.terra-insight.com/insights/automotive-component-manufacturing-reconciliation-india"
        },
        {
          "q": "What TDS code applies to job-work charges paid by an auto-component manufacturer to a heat-treatment vendor?",
          "a": "Job-work and sub-contracting charges paid to a heat-treatment, plating, machining or assembly vendor fall under Section 393(1)(a) of the Income Tax Act 2025, payment code 1002 (which replaced legacy Section 194C). Rate is 1% for individual/HUF vendors and 2% for company/firm vendors, with a per-transaction threshold of ₹30,000 and aggregate annual threshold of ₹1 lakh. The same vendor invoice will also carry GST on the job-work service, and the dispatch of inputs to the job-worker is governed separately by Section 143 of the CGST Act with a one-year return window.",
          "article": "Automotive Component Manufacturing Reconciliation in India: OEM Settlement, PLI Auto, JIT/Kanban Returns",
          "url": "https://www.terra-insight.com/insights/automotive-component-manufacturing-reconciliation-india"
        },
        {
          "q": "How does tooling amortisation reconciliation work?",
          "a": "An OEM typically pays one-time tooling cost upfront against a committed annual volume — say ₹40 lakh for a die expected to produce 80,000 parts over the programme life. Some OEMs treat tooling as their asset (the supplier holds custody and depreciates against the commitment); others let the supplier own it and recover via a per-part tooling amortisation line of ₹50 on each invoice. Reconciliation has to track cumulative tooling recovery against the contractual cap per programme — if actual volume runs ahead of forecast, the over-recovery sits as a credit due to the OEM; if volume falls short, the unamortised balance is at supplier risk at programme exit.",
          "article": "Automotive Component Manufacturing Reconciliation in India: OEM Settlement, PLI Auto, JIT/Kanban Returns",
          "url": "https://www.terra-insight.com/insights/automotive-component-manufacturing-reconciliation-india"
        },
        {
          "q": "What is FOMP and how does it reconcile against the Tier 1's monthly billing?",
          "a": "FOMP — Field-Originated Material Performance — is the OEM's back-charge regime for warranty claims traced back to a supplied part. Indian OEMs typically charge between 1% and 3% of monthly billing as a FOMP debit, sometimes structured as a rolling running account and sometimes as a per-claim debit. Reconciliation must split the FOMP debit by warranty claim ID, validate against the Tier 1's own warranty database, age unresolved disputes, and pursue recovery from the sub-tier supplier whose part caused the failure. Many Tier 1s carry 4-6% of revenue as a FOMP provision before reconciliation closes the actual exposure.",
          "article": "Automotive Component Manufacturing Reconciliation in India: OEM Settlement, PLI Auto, JIT/Kanban Returns",
          "url": "https://www.terra-insight.com/insights/automotive-component-manufacturing-reconciliation-india"
        },
        {
          "q": "When does GST liability arise on consignment stock held at an OEM plant under VMI?",
          "a": "GST liability arises on consumption or withdrawal by the OEM, not on the physical movement of goods to the OEM premises. Under a vendor-managed inventory or consignment model, the supplier retains ownership of the stock while it sits at the OEM line or warehouse — there is no supply, and therefore no GST, at the moment the goods move. The goods travel on a delivery challan under Rule 55 of the CGST Rules. Supply is treated as occurring when the OEM consumes the part (draws it onto the line) or withdraws it from the consignment store, and the tax invoice — frequently the OEM's self-billed invoice — must be raised at that point with GST charged.",
          "article": "Consignment Stock and VMI Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/consignment-stock-vmi-reconciliation-auto-india"
        },
        {
          "q": "What is a Rule 55 delivery challan and why is it used for VMI movement?",
          "a": "Rule 55 of the CGST Rules permits the movement of goods without a tax invoice in defined situations, including supply of goods on approval and movements where the supply is not determined at the time of removal — which covers consignment and VMI transfers to an OEM plant. The challan carries the consignor and consignee details, HSN, description, quantity and a declaration that it is not a tax invoice. The goods physically reach the OEM consignment location under this challan with no GST charged. The tax invoice (or the OEM's self-billed invoice) follows later, on consumption. The challan series and the e-way bill must reconcile to the eventual consumption-triggered invoice so the audit trail closes.",
          "article": "Consignment Stock and VMI Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/consignment-stock-vmi-reconciliation-auto-india"
        },
        {
          "q": "What is ERS or OEM self-billing in the auto VMI model?",
          "a": "ERS — Evaluated Receipt Settlement, also called self-billing or a Self-Billed Invoice — is the practice where the OEM generates the invoice on the supplier's behalf at the point of consumption, rather than waiting for the supplier to bill. The OEM's MRP or ERP system reads the consumption (or backflush from the bill of materials against vehicles built) and produces a settlement document at the agreed part price. The supplier must reconcile this OEM-generated self-billed invoice against its own consignment stock-out records and book the matching tax invoice for GST. The risk is that the OEM's consumption figure and the supplier's stock-out figure diverge, leaving revenue either over- or under-recognised.",
          "article": "Consignment Stock and VMI Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/consignment-stock-vmi-reconciliation-auto-india"
        },
        {
          "q": "How is min-max replenishment reconciled in a VMI auto relationship?",
          "a": "Under min-max VMI the supplier commits to keep the consignment stock at the OEM line between a floor (min) and ceiling (max) level per part number. The OEM's consumption draws the stock down; when it nears the min, the supplier replenishes up toward the max on a fresh Rule 55 challan. Reconciliation ties three quantities per part per period: opening consignment balance, replenishments dispatched (challan quantity), and OEM consumption (the billing trigger), with closing balance = opening + replenishment − consumption. A break in this identity points to a missed challan, an unrecorded consumption, line-side rejection, or shrinkage at the OEM store that the supplier owns the risk on.",
          "article": "Consignment Stock and VMI Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/consignment-stock-vmi-reconciliation-auto-india"
        },
        {
          "q": "What happens to ageing or obsolete consignment stock sitting at the OEM plant?",
          "a": "Because the supplier owns consignment stock until consumption, slow-moving or obsolete parts at the OEM location remain on the supplier's balance sheet and age there, often invisibly. When a vehicle programme ends or a part is engineering-changed, residual consignment stock that the OEM never consumes becomes the supplier's exposure — to be returned on a Rule 55 challan, scrapped (triggering Section 394 scrap TCS if sold), or negotiated into a buy-back. A consignment-stock ageing report by part number and consignment location is the core control: stock beyond an agreed ageing band signals provisioning need and a commercial conversation before programme exit crystallises the loss.",
          "article": "Consignment Stock and VMI Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/consignment-stock-vmi-reconciliation-auto-india"
        },
        {
          "q": "What is free-issue (FI) steel in auto stamping and how is it accounted?",
          "a": "Free-issue steel is steel coil that the OEM — or a steel major such as Tata Steel or JSW nominated by the OEM under a price-protected nomination — supplies to a stamping supplier at no charge, for the supplier to press into parts and return as finished components. The supplier never buys the steel and never records it in its purchase books; it is held memorandum-only, in a quantity ledger tracked in metric tonnes, because legal ownership of the FI material stays with the OEM throughout. The supplier bills only its conversion charge (the pressing labour, tooling amortisation and overhead), not the value of the steel. Reconciliation is therefore a quantity reconciliation — tonnes in, parts and scrap out — rather than a value reconciliation.",
          "article": "Free-Issue Steel and Skeleton Scrap Reconciliation for Indian Auto Stamping Suppliers",
          "url": "https://www.terra-insight.com/insights/free-issue-steel-skeleton-scrap-reconciliation-india"
        },
        {
          "q": "How is GST treated on free-issue material under the job-work rules?",
          "a": "Where an OEM supplies steel free-issue and the supplier presses it and returns the finished part, the arrangement is treated as job-work. Under Section 143 of the CGST Act the OEM (principal) can dispatch the FI steel to the stamping supplier (job-worker) on a delivery challan without GST, provided the inputs return within one year. The supplier charges GST only on its conversion/job-work charge, not on the value of the FI steel — because the steel is not the supplier's supply. Schedule II of the CGST Act classifies treatment or process applied to another person's goods as a supply of service, which is what the conversion charge represents. No GST attaches to the free-issue steel itself when it is processed and returned within the statutory window.",
          "article": "Free-Issue Steel and Skeleton Scrap Reconciliation for Indian Auto Stamping Suppliers",
          "url": "https://www.terra-insight.com/insights/free-issue-steel-skeleton-scrap-reconciliation-india"
        },
        {
          "q": "What is skeleton scrap and why must it be reconciled separately?",
          "a": "Skeleton scrap — also called engineering scrap or web scrap — is the perforated steel lattice left after blanks are stamped out of a coil or sheet. Stamping yields are typically 65-85%, meaning 15-35% of the FI steel by weight leaves as skeleton scrap depending on part geometry and nesting efficiency. Because the steel was free-issue and owned by the OEM, the skeleton scrap is also OEM-owned by default, so it cannot simply be treated as the supplier's own waste. It must be reconciled: returned to the OEM (on a delivery challan), or retained by the supplier and sold under an agreed scrap-credit arrangement — in which case the sale attracts Section 394 scrap TCS at 1% (payment code 1071) and the scrap credit is netted against the supplier's conversion charges.",
          "article": "Free-Issue Steel and Skeleton Scrap Reconciliation for Indian Auto Stamping Suppliers",
          "url": "https://www.terra-insight.com/insights/free-issue-steel-skeleton-scrap-reconciliation-india"
        },
        {
          "q": "How does scrap-credit netting against conversion charges work?",
          "a": "When the OEM allows the stamping supplier to retain and sell the skeleton scrap, the value of that scrap is usually credited back to the OEM rather than kept by the supplier — because the OEM owned the underlying steel. The mechanism is a scrap credit netted against the conversion-charge invoice: the supplier raises its conversion charge, computes the scrap recovery at the agreed scrap price per tonne on the actual scrap weight, and either deducts it from the conversion invoice or issues a separate scrap-credit note to the OEM. Reconciliation must tie the generated skeleton-scrap tonnage to the scrap-credit value, ensure the Section 394 TCS leg on any external scrap sale is closed, and confirm the net conversion charge ties to what the OEM pays.",
          "article": "Free-Issue Steel and Skeleton Scrap Reconciliation for Indian Auto Stamping Suppliers",
          "url": "https://www.terra-insight.com/insights/free-issue-steel-skeleton-scrap-reconciliation-india"
        },
        {
          "q": "What is a free-issue material audit and how often is it run?",
          "a": "A free-issue material audit is the periodic reconciliation of the memorandum FI quantity ledger against physical stock and against consumption. It closes the yield equation: opening FI steel balance + FI steel received − (finished parts dispatched + skeleton scrap returned-or-sold + permitted process loss) = closing FI balance, all in tonnes. Because the OEM owns the steel, any unexplained shortfall is the supplier's liability — the OEM will recover the value of missing free-issue material. OEMs commonly require a monthly or quarterly FI reconciliation statement, and a physical FI stock count at least annually. A persistent negative yield variance beyond the agreed process-loss tolerance is treated as a recoverable from the supplier.",
          "article": "Free-Issue Steel and Skeleton Scrap Reconciliation for Indian Auto Stamping Suppliers",
          "url": "https://www.terra-insight.com/insights/free-issue-steel-skeleton-scrap-reconciliation-india"
        },
        {
          "q": "What is the difference between EDI 830 and EDI 862 in an OEM delivery schedule?",
          "a": "The ANSI X12 830 is the planning schedule — a rolling forecast (typically a 12 to 26 week horizon) the OEM transmits to the supplier so capacity and raw material can be planned, but it is not a firm order. The ANSI X12 862 is the shipping schedule — the firm, short-horizon call-off (typically the next few days to two weeks) that authorises actual dispatch and is the document the supplier ships against. The discipline failure that breaks reconciliation is treating the 830 forecast as a commitment: the supplier may only invoice against quantity that was firmed on an 862 and physically received against an 856 ASN, never against the 830 planning number.",
          "article": "OEM Delivery Schedule and EDI/ASN Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/oem-delivery-schedule-edi-asn-reconciliation-india"
        },
        {
          "q": "What is CUM (cumulative quantity) accounting and why does it break reconciliation?",
          "a": "Auto EDI does not transmit discrete order quantities — it transmits running cumulatives. The 862 carries a CUM-required (total quantity the OEM expects received to date since a year-start or model-start reset), and the supplier's 856 ASN carries a CUM-shipped. The open delivery requirement is the difference: CUM-required minus CUM-received. The danger is that a single dropped or duplicated ASN permanently shifts the supplier's CUM-shipped out of step with the OEM's CUM-received, so every subsequent call-off is mis-stated until the two sides reconcile the CUM. Reconciliation must compare CUM-shipped on the supplier side against CUM-received on the OEM GRN, not just the last shipment quantity.",
          "article": "OEM Delivery Schedule and EDI/ASN Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/oem-delivery-schedule-edi-asn-reconciliation-india"
        },
        {
          "q": "Can a supplier raise a GST e-invoice and e-way bill against an ASN-driven JIT dispatch?",
          "a": "Yes, and they run in parallel. The 856 ASN is the logistics and line-feeding document that lets the OEM receive against the schedule; it is not a tax document. Each taxable dispatch above the e-invoice turnover threshold must still carry a GST e-invoice with an IRN, and movement above the e-way bill value threshold must carry an e-way bill. Many JIT suppliers invoice on a periodic (weekly or fortnightly) consolidated basis against the cumulative received quantity rather than per truck, so reconciliation has to map many ASNs to one tax invoice and validate that invoiced quantity equals OEM-confirmed received quantity for the period.",
          "article": "OEM Delivery Schedule and EDI/ASN Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/oem-delivery-schedule-edi-asn-reconciliation-india"
        },
        {
          "q": "What is the difference between ship-to-line and ship-to-store delivery?",
          "a": "Ship-to-line (or dock-to-line / JIS) means the supplier delivers directly to the assembly line-side in the exact sequence the OEM consumes parts, often in a 2 to 4 hour window with no OEM buffer stock — the ASN and sequence data feed the line directly. Ship-to-store means the supplier delivers to an OEM warehouse or store, the OEM books a GRN into stock, and consumption is decoupled from delivery. The reconciliation timing differs: ship-to-line confirmations arrive near real-time and short-pays surface fast, while ship-to-store delivery is reconciled against a periodic store GRN, so quantity disputes can lag by days.",
          "article": "OEM Delivery Schedule and EDI/ASN Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/oem-delivery-schedule-edi-asn-reconciliation-india"
        },
        {
          "q": "How does delivery tolerance affect ASN-to-GRN reconciliation?",
          "a": "Scheduling agreements usually allow an over-delivery and under-delivery tolerance (commonly a small percentage band, sometimes a fixed-quantity band) so minor batch rounding does not trigger an exception. Reconciliation must apply the tolerance per part before flagging a variance: an ASN-shipped quantity that lands inside the tolerance against the 862 firm call-off is treated as matched, while quantity outside the band is a genuine over- or under-delivery that may attract a return, a short-pay, or a premium-freight expedite charge. The tolerance band itself must be stored in the part master so the match is automated rather than judged line by line.",
          "article": "OEM Delivery Schedule and EDI/ASN Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/oem-delivery-schedule-edi-asn-reconciliation-india"
        },
        {
          "q": "How does a Maruti-style OEM auto-debit work mechanically?",
          "a": "An OEM such as Maruti Suzuki, Tata Motors, Mahindra & Mahindra or Hyundai runs an auto-debit on the supplier's running ledger — the supplier's invoice is taken on file, the OEM's payment is initiated for the invoice net of any deductions captured against the supplier during the billing period, and an auto-generated debit memo is shared electronically citing the reason code (FOMP, quality penalty, JIT shortage, line-stop charge, tooling adjustment, transport debit). The supplier has no opportunity to dispute the deduction before payment; reconciliation is post-facto and must match each debit memo to the underlying claim ID before the dispute window closes.",
          "article": "OEM-Tier 1 Settlement and Debit Note Reconciliation for Indian Automotive Components",
          "url": "https://www.terra-insight.com/insights/oem-tier1-settlement-debit-notes-reconciliation-india"
        },
        {
          "q": "When must a supplier issue a GST credit note against an OEM debit note?",
          "a": "Under Section 34 of the CGST Act, a credit note can be issued by the supplier (not the buyer) when goods are returned, found deficient, or the originally charged value or tax is reduced. The OEM's debit note is not itself a tax-effective document — it triggers the need for a supplier-issued GST credit note if the supplier accepts the underlying claim. The statutory window to issue a GST credit note runs until 30 November of the following financial year or filing of the annual return, whichever is earlier. A supplier disputing the debit beyond that window cannot reverse the GST liability through a credit note and is left with a commercial recovery only.",
          "article": "OEM-Tier 1 Settlement and Debit Note Reconciliation for Indian Automotive Components",
          "url": "https://www.terra-insight.com/insights/oem-tier1-settlement-debit-notes-reconciliation-india"
        },
        {
          "q": "When does Rule 37 ITC reversal hit on a delayed OEM settlement?",
          "a": "Rule 37 of the CGST Rules requires the recipient (the OEM, in this case) to reverse ITC if the supplier is not paid within 180 days of invoice date. For a Tier 1 whose Maruti invoice has been short-paid 12% with the residual sitting in dispute, the OEM faces Rule 37 reversal at day 180 on the unpaid 12%. OEMs typically force the issue at day 150-170 by either releasing the disputed amount or demanding a supplier-issued credit note. Reconciliation at the Tier 1 must age every short-pay against the 180-day Rule 37 clock and trigger settlement action well before it lapses.",
          "article": "OEM-Tier 1 Settlement and Debit Note Reconciliation for Indian Automotive Components",
          "url": "https://www.terra-insight.com/insights/oem-tier1-settlement-debit-notes-reconciliation-india"
        },
        {
          "q": "What TDS code applies when an OEM subcontracts heat treatment or machining back to a Tier 1?",
          "a": "Sub-contract service payments between OEM and Tier 1, or between Tier 1 and Tier 2 for heat treatment, plating, machining, assembly or surface treatment, are governed by Section 393(1)(a) of the Income Tax Act 2025, payment code 1002 — the successor to legacy Section 194C. Rate is 1% for individual/HUF payees and 2% for company/firm payees, with a per-transaction threshold of ₹30,000 and an aggregate annual threshold of ₹1 lakh. Reconciliation must split each composite invoice between goods and service components — TDS applies to the service portion only.",
          "article": "OEM-Tier 1 Settlement and Debit Note Reconciliation for Indian Automotive Components",
          "url": "https://www.terra-insight.com/insights/oem-tier1-settlement-debit-notes-reconciliation-india"
        },
        {
          "q": "What is a JIT shortage debit and how is it different from a quality back-charge?",
          "a": "A JIT (just-in-time) shortage debit is raised when the supplier's dispatched kanban quantity reaches the OEM line short of the called-off quantity, causing the OEM to either start the line short or pull from emergency reserve stock. The debit covers the shortage value plus any expediting cost (premium freight, line-stop charge). A quality back-charge — FOMP or technical service deduction — is raised when the dispatched part itself fails downstream, either at line rejection or in field warranty. The two are accounted differently: JIT shortages typically settle in the next billing cycle, while FOMP back-charges can age 6-18 months by warranty claim ID.",
          "article": "OEM-Tier 1 Settlement and Debit Note Reconciliation for Indian Automotive Components",
          "url": "https://www.terra-insight.com/insights/oem-tier1-settlement-debit-notes-reconciliation-india"
        },
        {
          "q": "What is the PLI Auto scheme and what does it cover?",
          "a": "The PLI Auto scheme — Production Linked Incentive for Automobile and Auto Components — was notified with a ₹25,938 crore outlay subsequently revised to ₹26,058 crore in budgetary allocations, for a five-year tenure covering FY 2023-24 to FY 2027-28. It targets two product categories: Advanced Automotive Technology (AAT) vehicles (electric, hydrogen fuel cell, advanced ICE) and Advanced Automotive Technology components (battery electronics, electric drivetrains, sensors, ADAS components, advanced safety, EV-specific hardware). Eligibility is anchored on committed investment, eligible-product certification, and minimum domestic value addition (DVA), with incentive percentages tiered by product category and value-add.",
          "article": "PLI Auto Claim Reconciliation: ₹26,058 Crore Scheme Incremental Sales Tracking for FY 2026-27",
          "url": "https://www.terra-insight.com/insights/pli-auto-claim-reconciliation-india"
        },
        {
          "q": "How is the FY 2019-20 base year used in incremental-sales calculation?",
          "a": "PLI Auto incentivises sales above the FY 2019-20 base. Each claim year's eligible sales are calculated as actual sales of AAT-certified products in the claim year minus the FY 2019-20 sales of the same product category. Only the incremental portion qualifies for incentive. For a Tier 1 with ₹100 crore FY 2019-20 AAT sales and ₹500 crore claim-year AAT sales, eligible incremental sales are ₹400 crore. Reconciliation must maintain a base-year ledger frozen at FY 2019-20 actuals per eligible product and audit-trail any product-category re-mappings.",
          "article": "PLI Auto Claim Reconciliation: ₹26,058 Crore Scheme Incremental Sales Tracking for FY 2026-27",
          "url": "https://www.terra-insight.com/insights/pli-auto-claim-reconciliation-india"
        },
        {
          "q": "What is domestic value addition (DVA) and who certifies it?",
          "a": "DVA is the percentage of value added domestically in the manufactured product — calculated as (sale value minus imported content) divided by sale value. Minimum DVA thresholds vary by product category, typically 50% for components and higher for AAT vehicles. DVA must be certified by a Chartered Engineer or a recognised independent agency, with documentation on bill-of-material level imported-content tracking, customs Bill of Entry references, and arm's-length transfer-pricing alignment for related-party imports. The DVA certificate is filed alongside the claim with the Project Monitoring Agency (PMA).",
          "article": "PLI Auto Claim Reconciliation: ₹26,058 Crore Scheme Incremental Sales Tracking for FY 2026-27",
          "url": "https://www.terra-insight.com/insights/pli-auto-claim-reconciliation-india"
        },
        {
          "q": "How does the PMA review and sanction workflow run?",
          "a": "Each quarter, the manufacturer files a claim with the PMA — currently IFCI Limited acting as the implementation agency under MoHI — comprising audited eligible sales, DVA certificate, eligible-product certification, committed-investment progress, and supporting financial statements. The PMA reviews documentation, may seek clarifications, conducts physical verification at the plant, and issues a sanction letter quantifying the disbursable incentive. Disbursement follows the sanction letter typically within 30-90 days as a single bank credit. Reconciliation must tie filed claim to sanction letter to bank credit, log any disallowance with reason, and queue disallowed lines for appeal in the next cycle.",
          "article": "PLI Auto Claim Reconciliation: ₹26,058 Crore Scheme Incremental Sales Tracking for FY 2026-27",
          "url": "https://www.terra-insight.com/insights/pli-auto-claim-reconciliation-india"
        },
        {
          "q": "What is the GST and Income Tax treatment of the PLI Auto incentive received?",
          "a": "GST: PLI incentive received from the government is generally treated as a capital subsidy not chargeable to GST under the current Section 15 framework — it is not a consideration for any supply made by the recipient to the government. Income Tax: post the Finance Act 2015 amendment to Section 2(24)(xviii) of the legacy Act (carried forward in the Income Tax Act 2025), government subsidies received in the nature of incentive are taxable as income unless specifically exempt or linked to a capital asset acquisition. Reconciliation must book PLI receipts to the correct ledger (income or capital reserve, depending on the legal opinion) and tie the disclosure to the corporate tax return for the year.",
          "article": "PLI Auto Claim Reconciliation: ₹26,058 Crore Scheme Incremental Sales Tracking for FY 2026-27",
          "url": "https://www.terra-insight.com/insights/pli-auto-claim-reconciliation-india"
        },
        {
          "q": "What is an RM price variation (RMPV) clause in an auto-component contract?",
          "a": "An RM price variation clause lets the component price float against the cost of the dominant raw material rather than staying fixed for the programme life. The contract defines a base price, a base index level, the material weight (kilograms of steel, aluminium, copper, zinc or polymer per part), and a reference index. At each revision date the new price is recomputed: the material portion moves with the index while the conversion/value-add portion stays fixed. The clause protects the supplier against a steel or LME spike it cannot absorb and protects the OEM by clawing the price back down when the index falls. Reconciliation is the recomputation of each claim against this formula and the matching of the resulting supplementary invoice or credit note.",
          "article": "Raw Material Price Escalation Clause Reconciliation for Indian Auto Components",
          "url": "https://www.terra-insight.com/insights/raw-material-price-escalation-clause-reconciliation-india"
        },
        {
          "q": "Which indices are referenced for auto-component RM escalation in India?",
          "a": "Steel-linked parts (stampings, forgings, fasteners) typically reference HR coil and CR coil prices, often via JPC (Joint Plant Committee) published prices or a named domestic mill price list. Aluminium, copper and zinc parts reference the LME (London Metal Exchange) settlement, adjusted for the rupee exchange rate and import/landing premiums. Plastic and rubber parts reference a polymer/resin index (polypropylene, ABS, EPDM grades). Precious-metal content (catalyst PGMs) references a bullion benchmark. The contract names the exact index, the averaging method and the lag, and reconciliation must apply that named index — not a proxy — to defend or contest a claim.",
          "article": "Raw Material Price Escalation Clause Reconciliation for Indian Auto Components",
          "url": "https://www.terra-insight.com/insights/raw-material-price-escalation-clause-reconciliation-india"
        },
        {
          "q": "How is a supplementary invoice for an RM price rise treated under GST?",
          "a": "When raw-material prices rise and the supplier becomes entitled to a higher price for goods already supplied, the supplier issues a supplementary (debit) invoice for the differential. Under the CGST Act this is a taxable upward revision: GST is charged on the price differential at the rate applicable to the component, and it flows into the supplier's GSTR-1 for the period of issue, with the OEM claiming the additional ITC. When prices fall and the OEM is entitled to a price reduction on goods already supplied, the supplier issues a GST credit note under Section 34, reducing its output liability subject to the buyer reversing the corresponding ITC. The debit/credit must be a supplier-issued document — a buyer's debit note is not by itself tax-effective.",
          "article": "Raw Material Price Escalation Clause Reconciliation for Indian Auto Components",
          "url": "https://www.terra-insight.com/insights/raw-material-price-escalation-clause-reconciliation-india"
        },
        {
          "q": "What is the time-of-supply issue on a retrospective RM price revision?",
          "a": "A retrospective price revision raises the question of when the additional tax is due. Under Section 13/Section 12 of the CGST Act read with the rules on time of supply, where the price of an already-supplied good is revised upward later, the supplementary invoice/debit note carries the GST and the liability is generally recognised in the tax period in which the revised price becomes determinable and the document is issued — not back-dated to the original supply. For a price reduction, the credit note can reduce liability only if issued within the Section 34 window (until 30 November of the following financial year or the annual return, whichever is earlier). Reconciliation must therefore tie each RMPV revision to the correct tax period and watch the credit-note cutoff.",
          "article": "Raw Material Price Escalation Clause Reconciliation for Indian Auto Components",
          "url": "https://www.terra-insight.com/insights/raw-material-price-escalation-clause-reconciliation-india"
        },
        {
          "q": "Why is there a lag between index publication and RMPV settlement?",
          "a": "The reference index for a quarter is only known after the quarter's price movements are published — a JPC steel price or an LME monthly average is finalised after the period closes, and the contract usually adds an averaging window and a settlement lag. So the Q1 RM revision is typically computed and settled in Q2, against goods already shipped in Q1. This lag means the supplier carries the RM exposure on its books before the supplementary invoice can be raised, and the OEM carries a potential clawback. Reconciliation must provision the expected RMPV claim at quarter-end based on observed index movement, then true it up when the index is published and the supplementary document is finally issued.",
          "article": "Raw Material Price Escalation Clause Reconciliation for Indian Auto Components",
          "url": "https://www.terra-insight.com/insights/raw-material-price-escalation-clause-reconciliation-india"
        },
        {
          "q": "Why do auto components move in returnable KLT bins instead of disposable packaging?",
          "a": "Auto assembly runs on standardised, stackable returnable containers — KLT (Kleinladungstraeger, small load carrier) bins, larger GLT bins, steel trolleys, pallets, dunnage and special-purpose containers — because they protect precision parts, present them at the line in a fixed pack quantity (the SNP, standard pack), stack and circulate cleanly, and avoid the cost and waste of disposable packaging at JIT volumes. The containers are usually owned by the OEM or by the supplier and are meant to cycle back empty after the parts are consumed. Because they are not being sold, their movement is not a supply — which is exactly why a returnable-packaging ledger and a Rule 55 challan are needed instead of a tax invoice.",
          "article": "Returnable Packaging and KLT Bin Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/returnable-packaging-klt-bin-reconciliation-india"
        },
        {
          "q": "What document covers returnable packaging movement under GST?",
          "a": "Goods sent for a reason other than supply — which includes returnable containers, and goods sent for job work or on approval — move on a delivery challan under Rule 55 of the CGST Rules, not on a tax invoice, because there is no supply and therefore no GST at dispatch. The delivery challan carries the description, quantity and the declared value of the containers, and an e-way bill is generated against the challan where the value crosses the threshold. The containers are expected to return on a corresponding inward challan. Reconciliation must tie each outward Rule 55 challan (bin-out) to an inward return challan or receipt (bin-in) so the float of containers in circulation is always accounted.",
          "article": "Returnable Packaging and KLT Bin Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/returnable-packaging-klt-bin-reconciliation-india"
        },
        {
          "q": "When does non-return of a KLT bin trigger a GST liability?",
          "a": "Returnable packaging moves without GST only because it is expected to come back. If containers are not returned within the agreed/contracted window, the position can shift to a deemed supply — the goods that left on a delivery challan are effectively retained by the recipient, and GST may become payable on the declared value of the unreturned containers, typically discharged by the supplier raising a tax invoice for the lost/retained bins. The exact trigger and timing depend on the contract and the facts, but the reconciliation principle is firm: an unreturned bin beyond its window is not just a logistics loss, it is a potential GST event that has to be quantified and either recovered from the recipient or settled.",
          "article": "Returnable Packaging and KLT Bin Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/returnable-packaging-klt-bin-reconciliation-india"
        },
        {
          "q": "How does a security deposit on returnable packaging work?",
          "a": "Where the OEM owns the bins it may hold no deposit but back-charge for losses; where the supplier owns the bins or where a pooled-container model is used, a security deposit is often taken against the float of containers in the counterparty's custody. The deposit sits on the balance sheet as a liability or receivable depending on direction, and is meant to be trued up against the actual bin balance. Reconciliation must tie the deposit ledger to the physical bin balance — deposit held should correspond to bins in circulation at the agreed per-bin value — so that a growing bin shortfall is matched by either a deposit drawdown or a recovery claim rather than sitting undetected.",
          "article": "Returnable Packaging and KLT Bin Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/returnable-packaging-klt-bin-reconciliation-india"
        },
        {
          "q": "How are empties returned in a milk-run, and why does it complicate reconciliation?",
          "a": "A milk-run is a consolidated logistics route where one vehicle visits several suppliers (or several OEM plants) on a fixed loop, dropping full bins and collecting empties in the same trip. It is efficient but it scrambles the one-dispatch-one-return mapping: empties collected on a milk-run may not correspond bin-for-bin to the full bins dropped, bins can be exchanged across plants, and the return challan may aggregate empties from multiple parts and dates. Reconciliation cannot assume a clean pairing — it has to net the bin-out and bin-in flows per bin type across the whole circulation, reconcile against the milk-run manifests, and locate where bins are physically parked when the cumulative out and in diverge.",
          "article": "Returnable Packaging and KLT Bin Reconciliation for Indian Auto Component Suppliers",
          "url": "https://www.terra-insight.com/insights/returnable-packaging-klt-bin-reconciliation-india"
        },
        {
          "q": "How does Section 143 of the CGST Act apply to a Tier-1 sending parts to a plater or heat-treater?",
          "a": "Section 143 of the CGST Act lets a registered principal — here the Tier-1 — send inputs to a job-worker (a plater, heat-treater, machinist, painter, anodiser or phosphater) for processing without paying GST on the dispatch, provided the goods return within one year (three years for capital goods). The inputs move on a delivery challan under Rule 45 with the principal's GSTIN, the job-worker's details, goods description and quantity. The Tier-1 retains ownership of the parts throughout; the job-worker bills only its conversion charge, which carries its own GST and TDS. If the part does not return within one year, the original dispatch is deemed a supply on the dispatch date and triggers GST with interest under Section 50.",
          "article": "Tier-2 Sub-Vendor Job-Work Reconciliation for Indian Auto Components (Section 143)",
          "url": "https://www.terra-insight.com/insights/tier2-subvendor-jobwork-reconciliation-auto-india"
        },
        {
          "q": "What is multi-hop job work and why does it complicate the Section 143 clock?",
          "a": "Multi-hop job work is where a part travels through more than one job-worker in sequence before returning to the Tier-1 — for example, a forged component goes to a machinist, then directly to a heat-treater, then to a plater, then back. Section 143 permits goods to be sent from one job-worker to another, but the one-year return clock runs from the original dispatch date by the principal, not from each hop. So the Tier-1 must track the part across every hop and ensure the full chain completes inside one year of the first dispatch. Each inter-job-worker movement is its own challan, and the ITC-04 must capture the whole chain. A part stuck at hop two as the year-end approaches is the same deemed-supply risk as one stuck at a single job-worker.",
          "article": "Tier-2 Sub-Vendor Job-Work Reconciliation for Indian Auto Components (Section 143)",
          "url": "https://www.terra-insight.com/insights/tier2-subvendor-jobwork-reconciliation-auto-india"
        },
        {
          "q": "How is ITC-04 reconciled for auto sub-vendor job work?",
          "a": "ITC-04 is the quarterly return (annual for principals with turnover up to ₹5 crore) that reports goods sent to and received back from job-workers. The reconciliation ties the challan-out register (parts dispatched to each job-worker), the challan-in register (parts returned), the inter-job-worker movement challans for multi-hop, and the open balance per job-worker — and rolls that into the ITC-04 line items: opening balance with job-worker, sent during the quarter, returned during the quarter, supplied from job-worker premises, and closing balance. A break between the Tier-1's challan registers and the ITC-04 is the primary statutory control; an open balance approaching the one-year window is the highest-priority alert.",
          "article": "Tier-2 Sub-Vendor Job-Work Reconciliation for Indian Auto Components (Section 143)",
          "url": "https://www.terra-insight.com/insights/tier2-subvendor-jobwork-reconciliation-auto-india"
        },
        {
          "q": "What TDS applies to the conversion charge paid to an auto job-worker?",
          "a": "The conversion charge — plating, heat-treatment, machining, painting, anodising or phosphating — is a service, so it attracts TDS under Section 393(1)(a) of the Income Tax Act 2025, payment code 1002 (which replaced legacy Section 194C). The rate is 1% for individual or HUF job-workers and 2% for company or firm job-workers, applied to the conversion/processing charge only — not to the value of the inputs, which the Tier-1 already owns. The per-transaction threshold is ₹30,000 and the aggregate annual threshold is ₹1 lakh per job-worker. The TDS is deposited by the 7th of the following month and reflected in the job-worker's Form 26AS or AIS. The same invoice also carries GST on the conversion service.",
          "article": "Tier-2 Sub-Vendor Job-Work Reconciliation for Indian Auto Components (Section 143)",
          "url": "https://www.terra-insight.com/insights/tier2-subvendor-jobwork-reconciliation-auto-india"
        },
        {
          "q": "What is the four-way match in auto job-work reconciliation?",
          "a": "The four-way match ties the job-work challan (parts sent out under Section 143), the physical-return GRN (parts received back, with quantity and the process applied), the conversion-charge invoice from the job-worker (the billed service with GST and Section 393(1)(a) TDS), and the ITC-04 reporting position. A clean match confirms that what was sent equals what returned within the process-loss tolerance, that the conversion invoice prices the returned quantity at the agreed rate, that the TDS was deducted at the correct Section 393 rate, and that the open balance feeding ITC-04 is accurate. Breaks point to short-returns, unbilled conversion, mis-applied TDS, or challans drifting toward the one-year deemed-supply window.",
          "article": "Tier-2 Sub-Vendor Job-Work Reconciliation for Indian Auto Components (Section 143)",
          "url": "https://www.terra-insight.com/insights/tier2-subvendor-jobwork-reconciliation-auto-india"
        },
        {
          "q": "Is tooling capitalised or expensed in the Indian Tier 1 books?",
          "a": "Tooling is capitalised as plant and machinery under Ind AS 16 when the supplier holds ownership and the asset has a useful life beyond one accounting period. Section 32 of the Income Tax Act allows depreciation at the prescribed plant-and-machinery rate (typically 15% WDV for general plant, with additional depreciation possible). When the OEM owns the tool and the supplier merely holds custody, the supplier does not capitalise — the tool is recorded as a custodial asset off balance sheet and the OEM books it. The choice is dictated by the commercial agreement, not by accounting preference.",
          "article": "Tooling Amortisation Reconciliation for Indian Automotive and Engineering Manufacturers",
          "url": "https://www.terra-insight.com/insights/tooling-amortisation-reconciliation-india"
        },
        {
          "q": "How is per-part tooling amortisation recovered from the OEM?",
          "a": "When the supplier owns the tool, the commercial agreement defines a per-part amortisation amount and a committed cumulative volume cap. For a ₹8 crore tool committed against 100,000 units, the amortisation is ₹80 per part. Every shipped part carries the ₹80 line as a separate amortisation component on the invoice (or bundled into part price with a contractual recovery schedule). Reconciliation tracks cumulative parts shipped against the 100,000-unit cap — exceeding the cap means over-recovery is owed back to the OEM; under-recovery is the supplier's exposure at programme exit.",
          "article": "Tooling Amortisation Reconciliation for Indian Automotive and Engineering Manufacturers",
          "url": "https://www.terra-insight.com/insights/tooling-amortisation-reconciliation-india"
        },
        {
          "q": "Does GST apply on tooling supply separately from part supply?",
          "a": "Yes. Tooling supplied to or paid for by the OEM is a separate taxable supply under the CGST Act. Two structures are common: the supplier invoices the tool upfront as a one-time supply (typically GST 18% on plant and machinery) with a separate commercial agreement on the production part price; or the per-part amortisation is bundled into the part price and the part GST rate (28% for most auto components, 18% on selected categories) applies on the gross. The structure must be locked at programme award because mid-programme switching creates GST reconciliation gaps.",
          "article": "Tooling Amortisation Reconciliation for Indian Automotive and Engineering Manufacturers",
          "url": "https://www.terra-insight.com/insights/tooling-amortisation-reconciliation-india"
        },
        {
          "q": "How is capital-goods ITC reconciled under Rule 43 when the supplier owns the tool?",
          "a": "When the supplier capitalises the tool and claims ITC on the input GST paid (steel, tool-shop services, design), Rule 43 of the CGST Rules requires the ITC to be amortised over 60 months of useful life with the formula prescribed for capital goods. If any portion of the tool's output is used for exempt supplies (export under LUT, supply to a SEZ), a proportionate ITC reversal applies. Reconciliation must maintain the 60-month amortisation schedule per tool and trigger Rule 43 reversals on the monthly portion attributable to exempt output.",
          "article": "Tooling Amortisation Reconciliation for Indian Automotive and Engineering Manufacturers",
          "url": "https://www.terra-insight.com/insights/tooling-amortisation-reconciliation-india"
        },
        {
          "q": "What happens to the tool at programme end — buyback or scrap?",
          "a": "Commercial outcomes at end of programme are typically: OEM-funded tooling — tool is buyback-eligible at residual book value or returned to OEM custody; supplier-owned tooling — tool is either retained for service-part production (often a 10-15 year service-part obligation under OEM warranty law), repurposed for a successor programme, or scrapped. Scrap sale attracts TCS under Section 394 code 1071 at 1% (legacy 206C(1)). Reconciliation must close out the tooling asset register at programme end with disposal value, residual book value, depreciation catch-up, and TCS deposited on the scrap proceeds.",
          "article": "Tooling Amortisation Reconciliation for Indian Automotive and Engineering Manufacturers",
          "url": "https://www.terra-insight.com/insights/tooling-amortisation-reconciliation-india"
        }
      ]
    },
    "gst-reconciliation": {
      "label": "GST Reconciliation",
      "faqs": [
        {
          "q": "How often should IMS reconciliation run — daily or only before the GSTR-3B deadline?",
          "a": "For volumes above 500 inward invoices a month, daily IMS pulls are recommended. Suppliers file GSTR-1 throughout the month, so invoices appear in IMS on a rolling basis. Daily processing spreads the exception-handling load across 20 working days instead of compressing it into the 14th-to-20th window. For volumes below 500, a twice-monthly cadence (around the 10th and the 14th) is workable.",
          "article": "How to Automate GST IMS Reconciliation in India (FY 2026-27 Playbook)",
          "url": "https://www.terra-insight.com/insights/automate-gst-ims-reconciliation-india"
        },
        {
          "q": "Can IMS decisions be reversed once submitted on the GST portal?",
          "a": "Yes — until GSTR-3B is filed for that month. An Accept can be changed to Reject, a Reject to Accept, and Pending to either decision. Once GSTR-3B is filed, the IMS state for that period is locked. Any subsequent change requires the supplier to file a GSTR-1 amendment, which then re-surfaces the invoice in a later IMS cycle.",
          "article": "How to Automate GST IMS Reconciliation in India (FY 2026-27 Playbook)",
          "url": "https://www.terra-insight.com/insights/automate-gst-ims-reconciliation-india"
        },
        {
          "q": "What audit-trail evidence does Rule 36(4) require for IMS-era ITC claims?",
          "a": "The audit trail must link each ITC claim in GSTR-3B Table 4 to a purchase register entry, a corresponding IMS Accept decision, the resulting GSTR-2B line, and proof of supplier payment within 180 days under Rule 37. The IMS Accept timestamp from the portal is the new evidence element added by the October 2024 regime. Software-generated audit packs typically bundle these four artefacts per invoice.",
          "article": "How to Automate GST IMS Reconciliation in India (FY 2026-27 Playbook)",
          "url": "https://www.terra-insight.com/insights/automate-gst-ims-reconciliation-india"
        },
        {
          "q": "How does multi-GSTIN consolidation work when each GSTIN has its own IMS dashboard?",
          "a": "The GST portal exposes a separate IMS dashboard per GSTIN. A consolidated workflow pulls each dashboard via the portal, normalises the data into a single decision queue keyed on supplier GSTIN plus invoice number, applies the same purchase-register-match logic for each entity, then posts decisions back to the relevant GSTIN. Shared service centres typically maintain one purchase master with a GSTIN-to-state mapping table.",
          "article": "How to Automate GST IMS Reconciliation in India (FY 2026-27 Playbook)",
          "url": "https://www.terra-insight.com/insights/automate-gst-ims-reconciliation-india"
        },
        {
          "q": "What happens if my purchase register has an invoice the supplier has not filed in GSTR-1?",
          "a": "The invoice will not appear in IMS or GSTR-2B for the current month. Three options: hold the ITC claim and follow up with the supplier for next month's filing, defer the ITC until the supplier files (within the Section 16(4) time limit), or escalate to the supplier-management team for repeat offenders. ITC cannot be claimed in GSTR-3B against an invoice that is not in GSTR-2B.",
          "article": "How to Automate GST IMS Reconciliation in India (FY 2026-27 Playbook)",
          "url": "https://www.terra-insight.com/insights/automate-gst-ims-reconciliation-india"
        },
        {
          "q": "What is Section 17(5) of the CGST Act?",
          "a": "Section 17(5) of the CGST Act, 2017 is a non-obstante clause that lists specific categories of goods and services where input tax credit is permanently blocked — meaning ITC cannot be claimed even if the purchase is used in the course or furtherance of business. The blocked list includes motor vehicles, food and beverages, outdoor catering, health and fitness services, travel benefits like LTC, club memberships, and works contracts for immovable property.",
          "article": "Blocked ITC Under Section 17(5): What Cannot Be Claimed and Why",
          "url": "https://www.terra-insight.com/insights/blocked-itc-section-17-5"
        },
        {
          "q": "Can ITC be claimed on motor vehicles used for employee transport?",
          "a": "No. ITC on motor vehicles used for transporting employees to and from their workplace is blocked under Section 17(5)(a). The exception applies only when the vehicle is used for transporting goods, transporting passengers as a taxable service (e.g., a cab aggregator), running a driving school, or for motor vehicle testing. A company providing a company cab to employees cannot claim ITC on that vehicle purchase or GST paid on the cab service.",
          "article": "Blocked ITC Under Section 17(5): What Cannot Be Claimed and Why",
          "url": "https://www.terra-insight.com/insights/blocked-itc-section-17-5"
        },
        {
          "q": "Is ITC available on outdoor catering for employee meals?",
          "a": "Generally no. ITC on food, beverages, and outdoor catering is blocked under Section 17(5)(b). The sole exception is when the provision of such food is a statutory obligation — for example, canteens maintained under Section 46 of the Factories Act, 1948 for factories employing more than 250 workers. In that case, ITC on canteen services at the 5% GST rate is available. For all other employee meal or event catering expenses, the credit is blocked.",
          "article": "Blocked ITC Under Section 17(5): What Cannot Be Claimed and Why",
          "url": "https://www.terra-insight.com/insights/blocked-itc-section-17-5"
        },
        {
          "q": "How should blocked ITC under Section 17(5) be treated in GSTR-3B?",
          "a": "Blocked ITC must be reversed in GSTR-3B Table 4(B)(1), labelled 'ITC Available but Not Availed (Others)'. If the credit was already posted to the electronic credit ledger in a prior month, a reversal entry in Table 4(B) is required in the current month. A reconciliation of GSTR-2B credits against Section 17(5) categories should be performed before every GSTR-3B filing, since GSTR-2B reflects what the supplier reported — not whether the expense is eligible under your business.",
          "article": "Blocked ITC Under Section 17(5): What Cannot Be Claimed and Why",
          "url": "https://www.terra-insight.com/insights/blocked-itc-section-17-5"
        },
        {
          "q": "What is the penalty for wrongly claiming blocked ITC under Section 17(5)?",
          "a": "Wrongly claimed ITC under Section 17(5) is treated as erroneous refund or excess ITC under Section 74 (if fraud or suppression is alleged) or Section 73 (if no intent). Interest under Section 50(3) is levied at 24% per annum on the excess ITC from the date of claim. A penalty of 10% of the tax amount (minimum ₹10,000) applies under Section 73; under Section 74, the penalty can be 100% of the tax involved. Additionally, the supplier's GSTIN can be flagged during departmental audit.",
          "article": "Blocked ITC Under Section 17(5): What Cannot Be Claimed and Why",
          "url": "https://www.terra-insight.com/insights/blocked-itc-section-17-5"
        },
        {
          "q": "Is DRC-01B a final demand notice?",
          "a": "No. DRC-01B is a pre-adjudication notice that gives you an opportunity to explain the liability mismatch between GSTR-1 and GSTR-3B before a formal demand is raised. If you reply within seven days with a valid explanation — or make the payment via DRC-03 — no further action is taken for that period. If you do not reply within seven days, the GST department may proceed to issue a proper demand notice under Section 73 (non-fraud) or Section 74 (fraud or suppression) depending on the nature of the discrepancy.",
          "article": "DRC-01B Notice: What It Means and How to Respond to the GST Liability Mismatch Notice",
          "url": "https://www.terra-insight.com/insights/drc-01b-reconciliation-reply"
        },
        {
          "q": "Can I dispute a DRC-01B if I believe the mismatch is incorrect?",
          "a": "Yes. In your DRC-01B Part B reply, you can select option (c) — Other reasons — and provide a detailed explanation of why the apparent mismatch does not represent an actual liability shortfall. Common legitimate reasons include an ITC adjustment in GSTR-3B that reduced net liability, credit notes issued to customers that reduced taxable turnover, or a data entry difference between GSTR-1 and GSTR-3B that has already been corrected in a subsequent amendment. Supporting documents should be retained even if not submitted with the reply.",
          "article": "DRC-01B Notice: What It Means and How to Respond to the GST Liability Mismatch Notice",
          "url": "https://www.terra-insight.com/insights/drc-01b-reconciliation-reply"
        },
        {
          "q": "How many days do I have to reply to DRC-01B?",
          "a": "You have seven days from the date the DRC-01B is issued to file your reply on the GST portal. The reply is filed as DRC-01B Part B under Services → Returns → DRC-01B. Missing this seven-day window does not automatically result in a demand notice, but it removes the opportunity to present your explanation before the department initiates adjudication proceedings under Section 73 or 74.",
          "article": "DRC-01B Notice: What It Means and How to Respond to the GST Liability Mismatch Notice",
          "url": "https://www.terra-insight.com/insights/drc-01b-reconciliation-reply"
        },
        {
          "q": "What is the threshold for DRC-01B to be triggered?",
          "a": "DRC-01B is triggered when the tax liability declared in GSTR-1 (or IFF for QRMP filers) exceeds the tax paid in GSTR-3B by more than ₹1 lakh OR more than 20% of the GSTR-3B liability amount, whichever is lower. If your GSTR-3B liability is ₹4 lakh and GSTR-1 shows ₹5 lakh, the difference is ₹1 lakh (25% of 3B liability). Since ₹1 lakh equals the rupee threshold, DRC-01B would be triggered. Organisations with consistently high throughput and minor month-end adjustments are most frequently triggered.",
          "article": "DRC-01B Notice: What It Means and How to Respond to the GST Liability Mismatch Notice",
          "url": "https://www.terra-insight.com/insights/drc-01b-reconciliation-reply"
        },
        {
          "q": "What is the difference between DRC-01B and DRC-01C?",
          "a": "DRC-01B covers the liability mismatch — it is triggered when your GSTR-1 output tax liability is higher than the tax paid in GSTR-3B. DRC-01C covers the ITC mismatch — it is triggered when the ITC you claimed in GSTR-3B is higher than the ITC available in GSTR-2B. Both are auto-generated by the GST system after GSTR-3B filing, both require a reply within seven days, and both can escalate to Section 73/74 demand proceedings if unanswered. An organisation can receive both notices in the same period if they have both a liability underpayment and an excess ITC claim.",
          "article": "DRC-01C Notice: How to Respond to the GST ITC Mismatch Auto-Notice",
          "url": "https://www.terra-insight.com/insights/drc-01c-itc-mismatch-reconciliation-reply"
        },
        {
          "q": "Can IGST import ITC cause a DRC-01C notice?",
          "a": "Yes, IGST paid on imports does not appear in GSTR-2B — it is reflected in ICEGATE records and must be claimed via Table 4A(1) of GSTR-3B separately. If you claim IGST import ITC in GSTR-3B without the corresponding entry in GSTR-2B, the difference can trigger DRC-01C. In your DRC-01C reply, use option (b) — claiming that the excess ITC is eligible under IGST on imports — and provide the Bill of Entry reference numbers and ICEGATE acknowledgement as supporting evidence.",
          "article": "DRC-01C Notice: How to Respond to the GST ITC Mismatch Auto-Notice",
          "url": "https://www.terra-insight.com/insights/drc-01c-itc-mismatch-reconciliation-reply"
        },
        {
          "q": "What happens if I ignore DRC-01C?",
          "a": "If you do not reply to DRC-01C within seven days, the GST department may initiate adjudication proceedings under Section 73 (non-fraud) or Section 74 (fraud/suppression). Section 73 proceedings can result in a demand for the excess ITC amount plus 18% interest per annum and a 10% penalty on the tax due. Section 74 proceedings (invoked when suppression or misstatement is alleged) carry a 100% penalty. Proactive reply within seven days, even with option (c) — other reasons — preserves the opportunity to explain the claim before a demand order is passed.",
          "article": "DRC-01C Notice: How to Respond to the GST ITC Mismatch Auto-Notice",
          "url": "https://www.terra-insight.com/insights/drc-01c-itc-mismatch-reconciliation-reply"
        },
        {
          "q": "What is the ITC mismatch threshold that triggers DRC-01C?",
          "a": "DRC-01C is triggered when ITC claimed in GSTR-3B exceeds ITC available in GSTR-2B by more than ₹1 lakh OR more than 20% of GSTR-2B ITC, whichever is lower. For example, if GSTR-2B shows ₹8 lakh of ITC and you claimed ₹10 lakh in GSTR-3B, the excess is ₹2 lakh (25% of GSTR-2B). Since ₹1 lakh is lower than ₹2 lakh, the ₹1 lakh threshold applies and DRC-01C is triggered. The notice is issued from FY 2024-25 onwards after each GSTR-3B filing.",
          "article": "DRC-01C Notice: How to Respond to the GST ITC Mismatch Auto-Notice",
          "url": "https://www.terra-insight.com/insights/drc-01c-itc-mismatch-reconciliation-reply"
        },
        {
          "q": "What is an e-invoice and who needs to generate it in India?",
          "a": "An e-invoice in India is a JSON-format invoice uploaded to the Invoice Registration Portal (IRP), which validates the data and returns a unique Invoice Reference Number (IRN) and a digitally signed QR code. The e-invoice mandate is currently applicable to businesses with annual aggregate turnover exceeding ₹5 Crore (threshold effective August 1, 2023). B2C transactions, financial credit notes, and certain exempt supplies are outside the e-invoice mandate.",
          "article": "E-Invoice Reconciliation in India: IRN, GSTR-1, and GSTR-2B Alignment",
          "url": "https://www.terra-insight.com/insights/e-invoice-reconciliation-india"
        },
        {
          "q": "Does e-invoicing eliminate GSTR-2B reconciliation?",
          "a": "No. E-invoicing auto-populates the supplier's GSTR-1 and the buyer's GSTR-2B, which reduces data entry errors. However, it does not eliminate reconciliation. New mismatches arise from cancelled IRNs that remain in GSTR-2B until a credit note is processed, invoices from multiple IRP portals that need to be consolidated, and B2C or exempted supplies that are not covered by e-invoicing and still require manual matching.",
          "article": "E-Invoice Reconciliation in India: IRN, GSTR-1, and GSTR-2B Alignment",
          "url": "https://www.terra-insight.com/insights/e-invoice-reconciliation-india"
        },
        {
          "q": "What happens if an e-invoice is cancelled after the IRN is generated?",
          "a": "An e-invoice can be cancelled within 24 hours of IRN generation through the IRP. After 24 hours, cancellation through the IRP is not possible; the supplier must issue a credit note. If the IRN was cancelled within 24 hours, the entry should not appear in the buyer's GSTR-2B. If cancellation happened after auto-population to GSTR-1, the supplier must amend GSTR-1 and the corresponding GSTR-2B entry of the buyer will be adjusted in the next GSTR-2B cycle (generated on the 14th of the following month).",
          "article": "E-Invoice Reconciliation in India: IRN, GSTR-1, and GSTR-2B Alignment",
          "url": "https://www.terra-insight.com/insights/e-invoice-reconciliation-india"
        },
        {
          "q": "Can an e-invoice be amended after generation?",
          "a": "No. Once an IRN is generated by the IRP, the e-invoice data is locked. Amendments to invoice value, GST rate, or supply details cannot be made to the original IRN. The correct process is to issue a credit note (for reduction) or a debit note (for increase) referencing the original IRN. The credit or debit note must itself be e-invoiced if the supplier is within the e-invoice mandate threshold of ₹5 Crore turnover.",
          "article": "E-Invoice Reconciliation in India: IRN, GSTR-1, and GSTR-2B Alignment",
          "url": "https://www.terra-insight.com/insights/e-invoice-reconciliation-india"
        },
        {
          "q": "What is the threshold for mandatory e-invoicing in India?",
          "a": "As of August 1, 2023, e-invoicing is mandatory for all registered taxpayers with annual aggregate turnover exceeding ₹5 Crore in any preceding financial year from 2017-18 onward. The threshold has been progressively reduced from ₹500 Crore (October 2020) to ₹100 Crore (January 2021), ₹50 Crore (April 2021), ₹20 Crore (April 2022), ₹10 Crore (October 2022), and ₹5 Crore (August 2023). Further reductions to ₹1 Crore or below are anticipated.",
          "article": "E-Invoice Reconciliation in India: IRN, GSTR-1, and GSTR-2B Alignment",
          "url": "https://www.terra-insight.com/insights/e-invoice-reconciliation-india"
        },
        {
          "q": "What is GSTR-9 and who must file it?",
          "a": "GSTR-9 is the annual GST return that consolidates all monthly or quarterly returns filed during a financial year. Filing is mandatory for registered taxpayers with annual aggregate turnover exceeding ₹2 Crore. Composition taxpayers file GSTR-9A (not GSTR-9). Input service distributors, casual taxable persons, non-resident taxable persons, and persons deducting TDS under Section 51 are exempt from GSTR-9.",
          "article": "GSTR-9 Reconciliation: Aligning the Annual Return With Monthly Filings",
          "url": "https://www.terra-insight.com/insights/gst-annual-return-gstr-9-reconciliation"
        },
        {
          "q": "How does GSTR-9 differ from monthly GSTR-1 and GSTR-3B?",
          "a": "GSTR-1 is a monthly outward supply statement filed by the 11th of each month; GSTR-3B is a monthly summary return filed by the 20th. GSTR-9 is the annual consolidation of both — it requires all 12 GSTR-1 and GSTR-3B figures to be reconciled and summarised into a single annual return. GSTR-9 also captures final ITC reversals under Rule 42 and 43 for the full year, which may differ from month-wise provisional reversals.",
          "article": "GSTR-9 Reconciliation: Aligning the Annual Return With Monthly Filings",
          "url": "https://www.terra-insight.com/insights/gst-annual-return-gstr-9-reconciliation"
        },
        {
          "q": "What is the deadline for filing GSTR-9?",
          "a": "GSTR-9 must be filed by 31 December of the year following the financial year. For FY 2024-25, the deadline is 31 December 2025. The deadline has historically been extended by CBIC notification, but businesses should target the statutory date. Late filing attracts a fee of ₹200 per day (₹100 CGST + ₹100 SGST), subject to a maximum of 0.25% of annual turnover.",
          "article": "GSTR-9 Reconciliation: Aligning the Annual Return With Monthly Filings",
          "url": "https://www.terra-insight.com/insights/gst-annual-return-gstr-9-reconciliation"
        },
        {
          "q": "What is GSTR-9C and is it mandatory?",
          "a": "GSTR-9C is a reconciliation statement between the audited annual accounts and GSTR-9. From FY 2020-21 onward, GSTR-9C is self-certified (no CA/CMA signature required) for taxpayers with turnover between ₹5 Crore and ₹10 Crore. For taxpayers with turnover exceeding ₹10 Crore, GSTR-9C must be certified by a chartered accountant or cost accountant. GSTR-9C is mandatory for all taxpayers with annual aggregate turnover exceeding ₹5 Crore.",
          "article": "GSTR-9 Reconciliation: Aligning the Annual Return With Monthly Filings",
          "url": "https://www.terra-insight.com/insights/gst-annual-return-gstr-9-reconciliation"
        },
        {
          "q": "How should ITC differences between monthly GSTR-3B and GSTR-9 be handled?",
          "a": "ITC differences arise when credits were claimed in GSTR-3B but are not reflected in GSTR-2B for the corresponding period, or when Rule 42/43 provisional reversals during the year differ from the annual final calculation. Any excess ITC shown in GSTR-9 Table 7 (ITC Reversals) over what was reversed in GSTR-3B must be paid as tax with interest at 18% per annum. Short-claimed ITC from prior months can be corrected in GSTR-9 up to the November return of the next financial year — the annual return is the final opportunity.",
          "article": "GSTR-9 Reconciliation: Aligning the Annual Return With Monthly Filings",
          "url": "https://www.terra-insight.com/insights/gst-annual-return-gstr-9-reconciliation"
        },
        {
          "q": "What is a GST credit note and when must it be issued?",
          "a": "A GST credit note is a document issued under Section 34 of the CGST Act when the taxable value or GST amount on a previous supply is reduced — typically due to goods return, post-sale price revision, or discount agreed after invoice. The supplier must issue a credit note when the original supply value decreases, and the buyer must correspondingly reverse the ITC already claimed on the original invoice.",
          "article": "GST Credit Note Reconciliation: Supplier Amendments and ITC Reversal",
          "url": "https://www.terra-insight.com/insights/gst-credit-note-reconciliation"
        },
        {
          "q": "What is the time limit for issuing a GST credit note?",
          "a": "Under Section 34, a credit note for any supply in a financial year must be issued before the earlier of: (a) September 30 of the following financial year, or (b) the date on which the annual return for that year is filed. For example, a credit note for an April 2025 supply must be issued by September 30, 2026 (or the GSTR-9 filing date for FY 2025-26, if earlier).",
          "article": "GST Credit Note Reconciliation: Supplier Amendments and ITC Reversal",
          "url": "https://www.terra-insight.com/insights/gst-credit-note-reconciliation"
        },
        {
          "q": "Does a GST credit note always appear in the buyer's GSTR-2B?",
          "a": "No. A credit note appears in the buyer's GSTR-2B only if the supplier links it to the original invoice reference when reporting it in GSTR-1. If the supplier reports the credit note without the original invoice reference — or with an incorrect document number — it appears as an unlinked credit note in GSTR-2B, which is harder for the buyer to match to their purchase register. The buyer still has the ITC reversal obligation but must identify the match manually.",
          "article": "GST Credit Note Reconciliation: Supplier Amendments and ITC Reversal",
          "url": "https://www.terra-insight.com/insights/gst-credit-note-reconciliation"
        },
        {
          "q": "How should a buyer reconcile a credit note received from a supplier?",
          "a": "The reconciliation requires 3-way matching: (1) credit note received from supplier (physical/email document), (2) credit note appearance in buyer's GSTR-2B (negative ITC entry), and (3) ITC reversal posted in buyer's GSTR-3B Table 4(B). All three must reflect the same amount and tax head. If the GSTR-2B credit note appears in month N but the buyer's accounts team posts the reversal in month N+2, the intervening GSTR-3B filings will have an excess ITC claim — which is taxable with 18% interest.",
          "article": "GST Credit Note Reconciliation: Supplier Amendments and ITC Reversal",
          "url": "https://www.terra-insight.com/insights/gst-credit-note-reconciliation"
        },
        {
          "q": "What happens if a credit note is not reconciled before the annual return filing?",
          "a": "If the buyer has claimed ITC on the original invoice and the supplier's credit note reduces that supply, but the buyer has not reversed the proportional ITC in GSTR-3B by the annual return filing date, the unreconciled ITC becomes a recoverable demand. GSTR-9 includes a specific reconciliation of ITC claimed versus ITC reversals — a discrepancy triggers a notice under Section 73 or Section 74 of the CGST Act, with interest at 18% per annum on the excess ITC from the date of claim.",
          "article": "GST Credit Note Reconciliation: Supplier Amendments and ITC Reversal",
          "url": "https://www.terra-insight.com/insights/gst-credit-note-reconciliation"
        },
        {
          "q": "Does the GST portal support a single IMS dashboard across multiple GSTINs?",
          "a": "No. The portal is structurally per-GSTIN. Each GSTIN has its own login or sub-login and its own IMS dashboard. A consolidated view is created outside the portal — a reconciliation tool pulls each dashboard, normalises the data, and presents a unified decision queue. Decisions are then posted back to the respective GSTIN dashboard.",
          "article": "GST IMS for Multi-GSTIN Enterprises in India: Consolidated Decision Workflow",
          "url": "https://www.terra-insight.com/insights/gst-ims-multi-gstin-enterprise-india"
        },
        {
          "q": "How should intercompany stock-transfer invoices be reconciled in IMS?",
          "a": "Inter-state stock transfers within the same legal entity attract IGST and appear in IMS as inward invoices on the receiving GSTIN. They should always Accept since the dispatching GSTIN filed them. Internal controls should flag any IGST-bearing inward invoice that does not have a matched inter-state transfer on the dispatching side. Mismatches usually indicate one side filed and the other did not record the transfer in time.",
          "article": "GST IMS for Multi-GSTIN Enterprises in India: Consolidated Decision Workflow",
          "url": "https://www.terra-insight.com/insights/gst-ims-multi-gstin-enterprise-india"
        },
        {
          "q": "What is the difference between a shared service centre and decentralised state IMS model?",
          "a": "Shared service centre: central AP team handles IMS for all GSTINs, running the same decision engine and posting to each dashboard. Decentralised: state finance teams own their GSTIN's IMS dashboard and apply local decision-making. Hybrid: central runs auto-recommendations, state teams override exceptions. The hybrid model is most common for groups with 5+ GSTINs.",
          "article": "GST IMS for Multi-GSTIN Enterprises in India: Consolidated Decision Workflow",
          "url": "https://www.terra-insight.com/insights/gst-ims-multi-gstin-enterprise-india"
        },
        {
          "q": "How do you handle a vendor with a single PAN but multiple GSTINs?",
          "a": "Each supplier GSTIN files its own GSTR-1, even within the same PAN. A vendor with operations in Maharashtra, Karnataka, and Delhi files three separate GSTR-1s under three GSTINs. They appear as three separate suppliers in the buyer's IMS across the relevant buyer GSTINs. PAN-level consolidation happens in vendor master data, not in the GSTR-1 or IMS feed.",
          "article": "GST IMS for Multi-GSTIN Enterprises in India: Consolidated Decision Workflow",
          "url": "https://www.terra-insight.com/insights/gst-ims-multi-gstin-enterprise-india"
        },
        {
          "q": "What is the audit-trail requirement for multi-GSTIN IMS under Rule 36(4)?",
          "a": "Rule 36(4) compliance is per-GSTIN. Each GSTIN's audit pack must independently link purchase register, IMS Accept timestamp, GSTR-2B line, and GSTR-3B Table 4 figure. The audit pack is typically structured as one per GSTIN per month, with a group-level consolidation report on top. The actor identity captured in each Accept must reflect the authorised user for that GSTIN.",
          "article": "GST IMS for Multi-GSTIN Enterprises in India: Consolidated Decision Workflow",
          "url": "https://www.terra-insight.com/insights/gst-ims-multi-gstin-enterprise-india"
        },
        {
          "q": "What are the categories of GST refund in India?",
          "a": "The main categories are: (1) zero-rated exports — with IGST payment or under Letter of Undertaking (LUT); (2) inverted duty structure — where input tax rate exceeds output tax rate causing ITC accumulation; (3) excess balance in the electronic cash ledger; (4) refund on finalisation of provisional assessment; and (5) refund of tax paid under wrong head (e.g., IGST paid but CGST+SGST was applicable).",
          "article": "GST Refund Reconciliation: Tracking Claims from RFD-01 to Bank Credit",
          "url": "https://www.terra-insight.com/insights/gst-refund-reconciliation"
        },
        {
          "q": "How long does it take to receive a GST refund after filing RFD-01?",
          "a": "A provisional refund of 90% of the claim amount must be sanctioned within 7 days of the acknowledgement date for export refunds. The final refund order must be issued within 60 days of the RFD-01 filing date. If the final refund is not issued within 60 days, interest at 6% per annum accrues on the delayed amount under Section 56 of the CGST Act.",
          "article": "GST Refund Reconciliation: Tracking Claims from RFD-01 to Bank Credit",
          "url": "https://www.terra-insight.com/insights/gst-refund-reconciliation"
        },
        {
          "q": "What happens if the GST refund amount sanctioned differs from the claim?",
          "a": "The GST officer may partially reject a refund claim if the claimed ITC is disputed, the export documentation is incomplete, or the officer finds that certain inputs are not eligible. A partial sanction order (RFD-06) is issued specifying the rejected portion and the grounds. The taxpayer can appeal within 3 months of the order date. The sanctioned amount is credited separately; the rejected portion remains in the credit ledger pending appeal.",
          "article": "GST Refund Reconciliation: Tracking Claims from RFD-01 to Bank Credit",
          "url": "https://www.terra-insight.com/insights/gst-refund-reconciliation"
        },
        {
          "q": "Is interest paid on delayed GST refunds?",
          "a": "Yes. Under Section 56 of the CGST Act, if the refund is not paid within 60 days of the RFD-01 filing date, interest at 6% per annum is payable from the date immediately after the expiry of 60 days. For cases of fraudulent refund claims later recovered, Section 50 applies a higher 24% interest rate on recovery.",
          "article": "GST Refund Reconciliation: Tracking Claims from RFD-01 to Bank Credit",
          "url": "https://www.terra-insight.com/insights/gst-refund-reconciliation"
        },
        {
          "q": "How do exporters reconcile GST refund claims with shipping bills?",
          "a": "Exporters must match each shipping bill number and port code with the corresponding export invoice in GSTR-1. The ICEGATE system transmits export data to the GST portal automatically for zero-rated supplies. A mismatch in invoice value, GSTIN, or shipping bill date between GSTR-1 and the customs record blocks the automated refund. IT services exporters using LUT must additionally reconcile FIRC (Foreign Inward Remittance Certificate) amounts with the invoiced value to confirm realisation within the RBI-prescribed timeline.",
          "article": "GST Refund Reconciliation: Tracking Claims from RFD-01 to Bank Credit",
          "url": "https://www.terra-insight.com/insights/gst-refund-reconciliation"
        },
        {
          "q": "What is GST TCS and who collects it from e-commerce sellers?",
          "a": "GST TCS (Tax Collected at Source under Section 52 of the CGST Act) is collected by e-commerce operators — Amazon, Flipkart, Meesho, Swiggy, Zomato — on the net taxable value of supplies made by sellers through their platforms. The operator deducts TCS before releasing the seller's payout and deposits it against the seller's GSTIN.",
          "article": "GST TCS Reconciliation for E-Commerce Sellers: Claiming the Credit",
          "url": "https://www.terra-insight.com/insights/gst-tcs-ecommerce-reconciliation"
        },
        {
          "q": "What is the rate of TCS under Section 52 of the CGST Act?",
          "a": "The TCS rate is 1% of the net taxable value. For inter-state supplies, 1% IGST is collected. For intra-state supplies, 0.5% CGST and 0.5% SGST are collected separately. A seller in Maharashtra fulfilling orders to Karnataka customers will see 1% IGST TCS, while Maharashtra-to-Maharashtra orders attract 0.5% CGST + 0.5% SGST.",
          "article": "GST TCS Reconciliation for E-Commerce Sellers: Claiming the Credit",
          "url": "https://www.terra-insight.com/insights/gst-tcs-ecommerce-reconciliation"
        },
        {
          "q": "Where does TCS credit appear for the seller?",
          "a": "TCS credit appears in two places: (1) the seller's GSTR-2B, auto-populated from the operator's GSTR-8 filed by the 10th of the following month; and (2) Form 26AS Part F, which consolidates TCS credits across both income tax and GST frameworks for the seller's PAN.",
          "article": "GST TCS Reconciliation for E-Commerce Sellers: Claiming the Credit",
          "url": "https://www.terra-insight.com/insights/gst-tcs-ecommerce-reconciliation"
        },
        {
          "q": "How do I claim the TCS credit deducted by Amazon or Flipkart?",
          "a": "Once the credit appears in GSTR-2B, the seller claims it by adjusting the TCS credit against output tax liability in GSTR-3B. The credit reduces net tax payable. If output tax is insufficient to absorb the credit in a given month, the balance carries forward to subsequent months — there is no direct cash refund mechanism for TCS credit under normal circumstances.",
          "article": "GST TCS Reconciliation for E-Commerce Sellers: Claiming the Credit",
          "url": "https://www.terra-insight.com/insights/gst-tcs-ecommerce-reconciliation"
        },
        {
          "q": "What happens if the TCS shown in my GSTR-2B differs from the settlement statement?",
          "a": "A mismatch means either the operator filed GSTR-8 with an incorrect taxable value, or the seller's own payout records are incomplete. The seller must raise a discrepancy with the operator's seller support team and obtain a corrected GSTR-8 before the 10th of the following month. Under Section 52, operators can revise GSTR-8 to correct errors, which then flows through to an updated GSTR-2B.",
          "article": "GST TCS Reconciliation for E-Commerce Sellers: Claiming the Credit",
          "url": "https://www.terra-insight.com/insights/gst-tcs-ecommerce-reconciliation"
        },
        {
          "q": "What causes GSTR-1 and GSTR-3B to not match?",
          "a": "The most common causes are: (1) invoices uploaded in GSTR-1 but tax not paid in GSTR-3B for the same period — often because 3B was filed in a hurry using an estimated figure; (2) tax paid in GSTR-3B without filing the corresponding GSTR-1, typically when a business realises it has underpaid tax and tops up via 3B; (3) amendments filed in GSTR-1 via the amendment tables (9A, 9B, 9C) that are not mirrored in a corrected 3B; (4) e-invoices generated late in the period that missed the 3B but were included in GSTR-1 the following month. For a company with ₹5 crore monthly turnover, even a 1% misreporting variance amounts to ₹5 lakh in output tax exposure.",
          "article": "GSTR-1 vs GSTR-3B Reconciliation: Resolving the Output Tax Mismatch",
          "url": "https://www.terra-insight.com/insights/gstr-1-vs-gstr-3b-reconciliation"
        },
        {
          "q": "Can I correct a GSTR-1 vs 3B mismatch after filing?",
          "a": "Yes. GSTR-1 can be amended in the next period using the amendment tables — Table 9A for B2B invoice amendments, 9B for credit note amendments, 9C for unregistered supply amendments. GSTR-3B cannot be amended directly; the correction is made by adjusting the output tax in the next period's 3B. If the mismatch resulted in short payment of tax, interest at 18% per annum is applicable from the due date of the original 3B until the date of payment. The filing deadline for GSTR-3B is the 20th of the following month, so a mismatch identified before that date can be corrected without any interest liability.",
          "article": "GSTR-1 vs GSTR-3B Reconciliation: Resolving the Output Tax Mismatch",
          "url": "https://www.terra-insight.com/insights/gstr-1-vs-gstr-3b-reconciliation"
        },
        {
          "q": "What happens if GSTR-1 shows higher tax than GSTR-3B?",
          "a": "If GSTR-1 declares more output tax than GSTR-3B pays, GSTN treats this as short payment. The department can issue a ASMT-10 scrutiny notice requesting explanation, followed by a DRC-01 demand notice for the differential tax plus interest at 18% per annum and, in cases of deliberate suppression, a penalty of up to 100% of the tax amount. If the difference is due to a genuine data entry error in GSTR-1, the invoice should be amended in the next GSTR-1 using Table 9A and the corresponding tax should be adjusted in 3B. If it is a genuine short payment, the tax plus interest should be paid immediately via Form DRC-03.",
          "article": "GSTR-1 vs GSTR-3B Reconciliation: Resolving the Output Tax Mismatch",
          "url": "https://www.terra-insight.com/insights/gstr-1-vs-gstr-3b-reconciliation"
        },
        {
          "q": "How often should GSTR-1 vs 3B reconciliation be done?",
          "a": "Monthly, without exception. The GSTR-1 filing deadline is the 11th of the following month; GSTR-3B is due on the 20th. This nine-day gap between the two deadlines is the natural reconciliation window — finance teams should run the comparison after filing GSTR-1 on the 11th and before finalising GSTR-3B on the 20th. Businesses with more than 500 invoices per month should automate this comparison using purpose-built GST reconciliation software rather than rely on manual VLOOKUP matching, which does not scale and introduces its own reconciliation errors.",
          "article": "GSTR-1 vs GSTR-3B Reconciliation: Resolving the Output Tax Mismatch",
          "url": "https://www.terra-insight.com/insights/gstr-1-vs-gstr-3b-reconciliation"
        },
        {
          "q": "Does GSTN automatically flag GSTR-1 vs 3B discrepancies?",
          "a": "Yes. GSTN's ADVAIT analytics system compares GSTR-1 declared supply values with GSTR-3B tax payment values for every taxpayer every month. Discrepancies beyond a threshold (which varies by taxpayer risk profile) trigger automated scrutiny. The first communication is typically an ASMT-10 notice asking for reconciliation details. If the response is unsatisfactory or the discrepancy persists across multiple periods, a DRC-01 demand notice is issued. As of FY 2024-25, GSTN has significantly increased the frequency of automated scrutiny notices, meaning persistent mismatches that were ignored in earlier years are now being actively pursued.",
          "article": "GSTR-1 vs GSTR-3B Reconciliation: Resolving the Output Tax Mismatch",
          "url": "https://www.terra-insight.com/insights/gstr-1-vs-gstr-3b-reconciliation"
        },
        {
          "q": "What is the difference between GSTR-2A and GSTR-2B?",
          "a": "GSTR-2A is a dynamic statement that updates in real time each time a supplier files their GSTR-1 or GSTR-5 return. It reflects all inward supply invoices reported against the taxpayer's GSTIN at any given moment and can change multiple times during a month. GSTR-2B is a static monthly snapshot generated on or around the 14th of the following month. It captures only invoices filed by suppliers up to the GSTR-1 deadline (11th of the month) and does not change once generated. Since the Finance Act 2022, GSTR-2B — not GSTR-2A — is the operative document for ITC claims under Rule 36(4) of the CGST Rules.",
          "article": "GSTR-2A vs GSTR-2B: Which Statement Controls ITC Claims?",
          "url": "https://www.terra-insight.com/insights/gstr-2a-vs-gstr-2b-difference"
        },
        {
          "q": "Can I claim ITC that appears in GSTR-2A but not GSTR-2B?",
          "a": "No. Under Rule 36(4) as amended effective 1 January 2022, ITC is restricted to amounts reflected in GSTR-2B for the period. If an invoice appears in GSTR-2A (because the supplier filed after the cut-off) but not in GSTR-2B, the ITC cannot be claimed for the current month. It will flow into the following month's GSTR-2B when that month's snapshot is generated — provided the supplier's late-filed GSTR-1 is captured before the next cut-off. Claiming ITC based on GSTR-2A alone constitutes excess ITC claiming, which attracts interest at 18% per annum on the excess amount.",
          "article": "GSTR-2A vs GSTR-2B: Which Statement Controls ITC Claims?",
          "url": "https://www.terra-insight.com/insights/gstr-2a-vs-gstr-2b-difference"
        },
        {
          "q": "When is GSTR-2B generated each month?",
          "a": "GSTR-2B is generated by GSTN on the 14th of the month following the return period (for example, the GSTR-2B for March 2025 is available from 14 April 2025). The statement is compiled from supplier GSTR-1 and GSTR-5 filings that were submitted up to the 11th of the month (the GSTR-1 filing deadline for monthly filers). For QRMP scheme taxpayers, GSTR-2B is generated quarterly and reflects IFF filings for months 1 and 2, and the full GSTR-1 for month 3 of the quarter.",
          "article": "GSTR-2A vs GSTR-2B: Which Statement Controls ITC Claims?",
          "url": "https://www.terra-insight.com/insights/gstr-2a-vs-gstr-2b-difference"
        },
        {
          "q": "What happens if a supplier files GSTR-1 after the 13th of the month?",
          "a": "If a supplier files their GSTR-1 after the GSTR-1 deadline of the 11th (and after the GSTR-2B cut-off on or around the 13th), the invoices they report will not appear in the current month's GSTR-2B. They will instead appear in the next month's GSTR-2B. The recipient therefore cannot claim ITC on those invoices in the current period and must wait until the following month. This is a common situation with smaller vendors and subcontractors who are habitual late filers — each month of late filing defers ITC by one full month. For a business buying ₹50 lakh worth of taxable services monthly from a consistently late supplier at 18% GST, this deferral is ₹9 lakh of ITC per cycle.",
          "article": "GSTR-2A vs GSTR-2B: Which Statement Controls ITC Claims?",
          "url": "https://www.terra-insight.com/insights/gstr-2a-vs-gstr-2b-difference"
        },
        {
          "q": "Is GSTR-2A still relevant after Rule 36(4) changes?",
          "a": "Yes, but for a different purpose. GSTR-2A is still useful for: (1) monitoring supplier filing behaviour during the month — finance teams can check GSTR-2A mid-month to identify which suppliers have not yet filed; (2) chasing suppliers before the 11th GSTR-1 deadline to ensure invoices appear in the current month's GSTR-2B; (3) dispute resolution — if a supplier claims they have filed but the invoice is absent from GSTR-2B, GSTR-2A shows whether the filing was made before or after the cut-off. GSTR-2A is a monitoring tool; GSTR-2B is the compliance instrument. Both should be part of a structured monthly ITC reconciliation workflow.",
          "article": "GSTR-2A vs GSTR-2B: Which Statement Controls ITC Claims?",
          "url": "https://www.terra-insight.com/insights/gstr-2a-vs-gstr-2b-difference"
        },
        {
          "q": "What is the static lock date on GSTR-2B and what does it mean for decisions?",
          "a": "GSTR-2B is generated on the 14th of each month and incorporates all IMS decisions taken up to that point. Decisions taken between the 14th and the 20th (GSTR-3B filing deadline) update GSTR-2B before it is used for ITC claim. After the 20th, the GSTR-2B for that period is locked. Any subsequent change requires a supplier-side GSTR-1 amendment that creates a new entry in a later IMS cycle.",
          "article": "Automating GSTR-2B Compliance Under IMS Rules: What Changed from October 2024",
          "url": "https://www.terra-insight.com/insights/gstr-2b-compliance-under-ims-rules"
        },
        {
          "q": "What is the 30-day buffer rule for Pending invoices?",
          "a": "An invoice marked Pending in IMS sits in the buyer's review queue for up to 30 days from the date it appears in IMS. If no Accept or Reject decision is taken within 30 days, the invoice is treated as Accepted by default and flows into the next GSTR-2B. This is the deemed-accept mechanism — it prevents indefinite deferral. Finance teams must therefore work the Pending queue at least monthly to avoid losing the Reject option.",
          "article": "Automating GSTR-2B Compliance Under IMS Rules: What Changed from October 2024",
          "url": "https://www.terra-insight.com/insights/gstr-2b-compliance-under-ims-rules"
        },
        {
          "q": "How is Pending different from explicit Reject in terms of timing risk?",
          "a": "Reject removes the invoice from the current and future GSTR-2B unless the supplier files an amendment. Pending defers the decision by up to 30 days, after which deemed-accept kicks in. The timing risk of Pending is that an unwatched invoice can quietly become Accepted past the 30-day mark, claiming ITC the buyer would otherwise have rejected. Reject is final and explicit; Pending is provisional and time-bound.",
          "article": "Automating GSTR-2B Compliance Under IMS Rules: What Changed from October 2024",
          "url": "https://www.terra-insight.com/insights/gstr-2b-compliance-under-ims-rules"
        },
        {
          "q": "What is the IMS feed-in pipeline and how is it timed?",
          "a": "Supplier files GSTR-1 by the 11th of the month (or rolling earlier). The IMS dashboard is populated by the 12th with all such filings. Buyer reviews and acts on each invoice before the 14th cut-off. GSTR-2B is generated on the 14th reflecting current IMS state. Buyer can continue to act on IMS through the 20th, updating GSTR-2B before GSTR-3B filing. The five-stage timing is filing → dashboard population → action window → generation → final action window.",
          "article": "Automating GSTR-2B Compliance Under IMS Rules: What Changed from October 2024",
          "url": "https://www.terra-insight.com/insights/gstr-2b-compliance-under-ims-rules"
        },
        {
          "q": "What changes for ITC claim under the new IMS-driven GSTR-2B?",
          "a": "Pre-IMS, ITC in GSTR-3B was claimed against the auto-populated GSTR-2B. Post-IMS, ITC is claimed against the IMS-decided GSTR-2B — only invoices Accepted (explicitly or by 30-day default) appear and are eligible. Rejected invoices are excluded. Pending invoices not yet aged into deemed-accept are also excluded. The mechanical formula is the same; the upstream content of GSTR-2B is now controlled by buyer decisions.",
          "article": "Automating GSTR-2B Compliance Under IMS Rules: What Changed from October 2024",
          "url": "https://www.terra-insight.com/insights/gstr-2b-compliance-under-ims-rules"
        },
        {
          "q": "Who is required to file GSTR-9C?",
          "a": "GSTR-9C is mandatory for every registered person whose aggregate turnover during a financial year exceeds ₹5 crore. The reconciliation statement must be self-certified by the taxpayer from FY 2020-21 onwards. Prior to that, it required certification by a Chartered Accountant. The due date aligns with GSTR-9, which is typically 31 December of the following financial year, though extensions are common.",
          "article": "GSTR-9C: The Three-Way Mismatch Trap Between Books, GSTR-2B, and GSTR-3B",
          "url": "https://www.terra-insight.com/insights/gstr-9c-three-way-mismatch-reconciliation-india"
        },
        {
          "q": "What are Tables 12A, 12E, and 12F in GSTR-9C?",
          "a": "Table 12A captures ITC as per the audited financial statements or books of account. Table 12E captures ITC as declared in the GSTR-9 annual return. Table 12F shows the unreconciled difference between 12A and 12E. Table 13 requires the taxpayer to provide reasons for every difference reported in 12F. These four tables together form the core of the three-way reconciliation that GSTR-9C enforces.",
          "article": "GSTR-9C: The Three-Way Mismatch Trap Between Books, GSTR-2B, and GSTR-3B",
          "url": "https://www.terra-insight.com/insights/gstr-9c-three-way-mismatch-reconciliation-india"
        },
        {
          "q": "What is the penalty for excess ITC claimed in GSTR-3B?",
          "a": "Excess ITC that does not appear in GSTR-2B attracts interest at 18% per annum under Section 50(1) of the CGST Act from the date of availment to the date of reversal. Section 122(1)(ii) imposes a penalty of ₹10,000 or the tax amount involved, whichever is greater, for claiming ITC without an invoice or valid document. For fraud cases, Section 74 allows a 100% penalty on the tax amount, and Section 132 provides for criminal prosecution where the ITC amount exceeds ₹5 crore.",
          "article": "GSTR-9C: The Three-Way Mismatch Trap Between Books, GSTR-2B, and GSTR-3B",
          "url": "https://www.terra-insight.com/insights/gstr-9c-three-way-mismatch-reconciliation-india"
        },
        {
          "q": "How does the Invoice Management System affect GSTR-9C reconciliation?",
          "a": "IMS, live since October 2024, adds an accept/reject/pending status to every inward invoice before it flows into GSTR-2B. This creates a fourth data point in the reconciliation chain: the IMS action status must now align with the GSTR-2B inclusion, the GSTR-3B claim, and the books entry. An invoice accepted in IMS but not reflected in GSTR-2B due to the supplier's filing delay, or an invoice rejected in IMS but still claimed in GSTR-3B, creates a mismatch that surfaces in GSTR-9C.",
          "article": "GSTR-9C: The Three-Way Mismatch Trap Between Books, GSTR-2B, and GSTR-3B",
          "url": "https://www.terra-insight.com/insights/gstr-9c-three-way-mismatch-reconciliation-india"
        },
        {
          "q": "Should GSTR-9C reconciliation be done monthly or only at year-end?",
          "a": "Running the three-way match monthly rather than at year-end prevents the accumulation of unresolvable differences. A monthly cadence allows the finance team to identify supplier GSTR-1 amendments, credit note mismatches, and IMS status discrepancies while correction is still possible. At year-end, many of these differences become permanent because the amendment window under Section 37 closes after the September return of the following year.",
          "article": "GSTR-9C: The Three-Way Mismatch Trap Between Books, GSTR-2B, and GSTR-3B",
          "url": "https://www.terra-insight.com/insights/gstr-9c-three-way-mismatch-reconciliation-india"
        },
        {
          "q": "What determines whether IGST or CGST/SGST applies to a transaction?",
          "a": "The place of supply rules under the IGST Act determine the applicable tax. If the supplier's state and the buyer's state are different, the supply is inter-state and IGST applies. If both are in the same state (or union territory), the supply is intra-state and CGST + SGST (or CGST + UTGST for union territories) applies. For services, the place of supply is typically the recipient's location; for goods, it is the delivery location.",
          "article": "IGST, CGST, and SGST Reconciliation: Managing Multi-State Tax Accounts",
          "url": "https://www.terra-insight.com/insights/igst-cgst-sgst-reconciliation"
        },
        {
          "q": "Can CGST Input Tax Credit be used to pay SGST liability?",
          "a": "No. CGST ITC cannot be used to offset SGST liability. Under the ITC set-off rules amended by the Finance Act 2019, CGST ITC can offset CGST liability first, and then IGST liability. Similarly, SGST ITC can offset SGST liability first, then IGST. Cross-utilisation of CGST against SGST (or vice versa) is explicitly prohibited.",
          "article": "IGST, CGST, and SGST Reconciliation: Managing Multi-State Tax Accounts",
          "url": "https://www.terra-insight.com/insights/igst-cgst-sgst-reconciliation"
        },
        {
          "q": "How does a multi-state business reconcile different GST heads across GSTINs?",
          "a": "Each GSTIN operates as an independent tax entity with its own GSTR-1, GSTR-3B, and electronic ledgers. The reconciliation requires: (1) verifying that each inter-state supply between two GSTINs of the same entity is declared as an IGST transaction; (2) confirming that ITC on inter-GSTIN stock transfers (taxable at the applicable GST rate) is correctly claimed in the destination GSTIN; and (3) ensuring GSTR-3B for each GSTIN uses the correct offset sequence without cross-head utilisation.",
          "article": "IGST, CGST, and SGST Reconciliation: Managing Multi-State Tax Accounts",
          "url": "https://www.terra-insight.com/insights/igst-cgst-sgst-reconciliation"
        },
        {
          "q": "What happens when IGST is charged incorrectly as CGST and SGST?",
          "a": "If an inter-state supply is incorrectly taxed as CGST+SGST, the buyer receives CGST and SGST ITC in GSTR-2B, which cannot offset IGST liability. Additionally, the GST department may issue a demand for the correct IGST while the incorrectly deposited CGST and SGST sit in the wrong government account. Rectification requires the supplier to issue a credit note for the incorrect invoice, raise a new IGST invoice, and file a revised GSTR-1. Refund of incorrectly paid CGST+SGST requires a separate RFD-01 application.",
          "article": "IGST, CGST, and SGST Reconciliation: Managing Multi-State Tax Accounts",
          "url": "https://www.terra-insight.com/insights/igst-cgst-sgst-reconciliation"
        },
        {
          "q": "What is the ITC set-off order for IGST, CGST, and SGST?",
          "a": "Under the Finance Act 2019 amendment, the mandatory ITC offset sequence is: IGST ITC must first offset IGST liability, then CGST, then SGST (any remaining). CGST ITC must first offset CGST liability, then IGST. SGST ITC must first offset SGST liability, then IGST. This sequence is enforced in the GSTR-3B portal — taxpayers cannot manually choose a different order.",
          "article": "IGST, CGST, and SGST Reconciliation: Managing Multi-State Tax Accounts",
          "url": "https://www.terra-insight.com/insights/igst-cgst-sgst-reconciliation"
        },
        {
          "q": "What happens if I leave an invoice in Pending past 30 days?",
          "a": "Under the IMS rules, an invoice in Pending status for more than 30 days from first appearance is treated as Accepted by default. The system flows it into the next applicable GSTR-2B and makes the ITC available. The buyer loses the option to Reject the invoice after this point. This is the deemed-accept mechanism, and it is the single most important timing rule in the IMS workflow.",
          "article": "IMS Accept / Reject / Pending Workflow for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/ims-accept-reject-pending-workflow-india"
        },
        {
          "q": "When should I use Reject instead of Pending?",
          "a": "Use Reject when you are confident the invoice does not belong to you — wrong GSTIN, fictitious supplier, amount you never agreed to, goods you never received. Reject is final unless the supplier files a GSTR-1 amendment. Use Pending when you need time to investigate — supplier follow-up needed, GRN not yet posted, internal approval pending. Pending is provisional and has a 30-day clock.",
          "article": "IMS Accept / Reject / Pending Workflow for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/ims-accept-reject-pending-workflow-india"
        },
        {
          "q": "Can I change an Accepted decision back to Reject before GSTR-3B is filed?",
          "a": "Yes. Until GSTR-3B for the period is filed (by the 20th of the month), IMS decisions can be changed in any direction. An Accept can be changed to Reject, a Reject to Accept, and Pending to either. Once GSTR-3B is filed, the IMS state is locked for that period and any change requires a supplier-side amendment in a later cycle.",
          "article": "IMS Accept / Reject / Pending Workflow for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/ims-accept-reject-pending-workflow-india"
        },
        {
          "q": "What audit-trail evidence does the GST audit examine for IMS decisions?",
          "a": "The audit examines the linkage from purchase register entry to IMS decision timestamp to GSTR-2B line to GSTR-3B Table 4 figure. For Rejected invoices, the audit also examines the rejection reason. For Pending invoices that aged into deemed-Accept, the audit examines why the buyer did not actively decide within 30 days. Spreadsheet workflows rarely capture the IMS decision timestamp; automated workflows do so by default.",
          "article": "IMS Accept / Reject / Pending Workflow for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/ims-accept-reject-pending-workflow-india"
        },
        {
          "q": "How should multi-person AP teams divide accept/reject/pending authority?",
          "a": "A common pattern: AP analysts post Accept on auto-recommended matches (no override authority on Reject), an AP manager posts Reject and reviews Pending decisions, and the finance controller has override authority on disputed items. The split prevents a single analyst from rejecting valid invoices and causing irreversible ITC loss. The audit trail captures the actor identity per decision.",
          "article": "IMS Accept / Reject / Pending Workflow for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/ims-accept-reject-pending-workflow-india"
        },
        {
          "q": "What is the difference between Type 9 and Type 9A GSTR-1 amendments?",
          "a": "Type 9 is an amendment of a B2B invoice filed in the current tax period — used when a supplier corrects an invoice within the same monthly cycle. Type 9A is an amendment of a B2B invoice filed in a prior tax period — used when the supplier corrects an invoice from an earlier month, subject to the Section 16(4) time limit. Both types flow into the buyer's IMS as amended entries requiring re-action.",
          "article": "IMS Amendment Cycle Reconciliation in India: Supplier Edits, Buyer Re-Action, Recurring Reviews",
          "url": "https://www.terra-insight.com/insights/ims-amendment-cycle-reconciliation-india"
        },
        {
          "q": "If I accepted an original invoice and the supplier amends it, what happens?",
          "a": "The amendment surfaces in your IMS as a new entry with a reference to the original. You must re-act on the amended entry: Accept the amended version (rolls back the original Accept), Reject the amendment (keeps the original Accept), or mark Pending. If you Accept the amended version, GSTR-2B reflects the amended amount; the original is treated as superseded. The ITC differential flows through GSTR-3B accordingly.",
          "article": "IMS Amendment Cycle Reconciliation in India: Supplier Edits, Buyer Re-Action, Recurring Reviews",
          "url": "https://www.terra-insight.com/insights/ims-amendment-cycle-reconciliation-india"
        },
        {
          "q": "What is the time lag between supplier amendment filing and IMS surfacing?",
          "a": "Typically same-day or next-day. A supplier filing a Type 9 amendment by 5 PM sees it in their GSTR-1 immediately; the buyer's IMS dashboard updates within 24 hours. Type 9A amendments to prior periods follow the same timing but flow into the current month's IMS, not the original month's. This means a January invoice amended in May will appear in the May IMS cycle for buyer re-action.",
          "article": "IMS Amendment Cycle Reconciliation in India: Supplier Edits, Buyer Re-Action, Recurring Reviews",
          "url": "https://www.terra-insight.com/insights/ims-amendment-cycle-reconciliation-india"
        },
        {
          "q": "What is the ghost invoice problem in amendment cycles?",
          "a": "When a supplier amends an invoice that the buyer previously Rejected, the original Reject does not automatically apply to the amendment. The amendment appears as a new actionable entry. If the buyer ignores it, the 30-day deemed-Accept clock applies to the amendment, potentially flowing it into GSTR-2B against the buyer's original Reject intent. Ghost invoices are the result of unwatched amendment queues.",
          "article": "IMS Amendment Cycle Reconciliation in India: Supplier Edits, Buyer Re-Action, Recurring Reviews",
          "url": "https://www.terra-insight.com/insights/ims-amendment-cycle-reconciliation-india"
        },
        {
          "q": "Does the amendment cycle affect Section 16(4) time limits for ITC claim?",
          "a": "Yes. Section 16(4) sets the deadline for claiming ITC on an invoice — generally the earlier of November 30 of the following financial year or the annual return filing date. Amendments do not extend this deadline. If a supplier amends an invoice in October 2026 for a financial year 2025-26 transaction, the buyer must still ensure the resulting ITC is claimed within the Section 16(4) window. Amendments that surface after the window are effectively unclaimable.",
          "article": "IMS Amendment Cycle Reconciliation in India: Supplier Edits, Buyer Re-Action, Recurring Reviews",
          "url": "https://www.terra-insight.com/insights/ims-amendment-cycle-reconciliation-india"
        },
        {
          "q": "How does IMS reconciliation scale from 1,000 to 5,000 monthly purchase invoices?",
          "a": "Linear-time decision logic per invoice does not scale linearly in human review time. At 1,000 invoices, a 5 percent exception rate produces 50 manual reviews. At 5,000 invoices, the same exception rate produces 250 reviews — far more than a 2-person AP team can complete in the six-day window. Volume above 2,500 invoices typically requires a dedicated reconciliation tool with exception triage.",
          "article": "Invoice Management System (IMS) Software for High-Volume Indian Retail and E-commerce",
          "url": "https://www.terra-insight.com/insights/ims-software-high-volume-indian-retail"
        },
        {
          "q": "How does IMS work for marketplace sellers on Amazon and Flipkart?",
          "a": "Marketplace sellers receive thousands of B2B invoices from marketplace operators (commission, logistics, advertising) and from category-level vendors. Each marketplace operator files GSTR-1 with the seller's GSTIN as recipient. These appear in the seller's IMS dashboard for accept/reject/pending action. Sellers must reconcile marketplace-issued invoices against marketplace settlement reports — a separate reconciliation that flows into the same IMS decision.",
          "article": "Invoice Management System (IMS) Software for High-Volume Indian Retail and E-commerce",
          "url": "https://www.terra-insight.com/insights/ims-software-high-volume-indian-retail"
        },
        {
          "q": "Can IMS decisions vary by product category or vendor type?",
          "a": "Operationally, yes. A retailer might auto-Accept invoices from category-A strategic suppliers (above ₹10 lakh, three-way matched), apply manual review to category-B mid-tier suppliers (₹1-10 lakh), and apply tight tolerance to category-C tail vendors (below ₹1 lakh). The GST portal does not distinguish — all decisions are uniform from the portal's view — but the internal decision engine can apply category-specific rules before posting.",
          "article": "Invoice Management System (IMS) Software for High-Volume Indian Retail and E-commerce",
          "url": "https://www.terra-insight.com/insights/ims-software-high-volume-indian-retail"
        },
        {
          "q": "What is the IMS impact on retail cash flow tied to inventory cycles?",
          "a": "Retail ITC is a working-capital input. An invoice held Pending in IMS defers ITC by one month, increasing GST cash outflow on GSTR-3B by the deferred amount. For a retailer with ₹50 crore monthly inward purchases, a 10 percent Pending rate represents ₹90 lakh of deferred ITC (assuming 18 percent GST) — direct working-capital impact tied to the inventory turnover cycle.",
          "article": "Invoice Management System (IMS) Software for High-Volume Indian Retail and E-commerce",
          "url": "https://www.terra-insight.com/insights/ims-software-high-volume-indian-retail"
        },
        {
          "q": "How does IMS reconciliation handle the multi-state retail model (8-12 GSTINs)?",
          "a": "Each state of operation requires a separate GSTIN with its own IMS dashboard. A retailer with stores in 10 states maintains 10 dashboards. The reconciliation tool pulls each dashboard, applies a common decision engine against a unified purchase master, then posts decisions back to each GSTIN. State-level finance owners typically retain override authority on their GSTIN even when central operations runs the engine.",
          "article": "Invoice Management System (IMS) Software for High-Volume Indian Retail and E-commerce",
          "url": "https://www.terra-insight.com/insights/ims-software-high-volume-indian-retail"
        },
        {
          "q": "If I reject an invoice in IMS, does my GSTR-2B automatically update?",
          "a": "Yes. GSTR-2B reflects the net of your IMS decisions. An invoice you Reject in IMS is excluded from GSTR-2B entirely. An invoice you Accept appears in GSTR-2B and makes the ITC available for that month's GSTR-3B. The GSTR-2B is generated on the 14th and reflects whatever IMS status each invoice holds at that point — so actions taken between the 14th and the 20th (GSTR-3B filing deadline) update GSTR-2B before it is used for ITC claims.",
          "article": "IMS vs GSTR-2B: The New Three-Way Reconciliation Indian Businesses Must Do",
          "url": "https://www.terra-insight.com/insights/ims-vs-gstr-2b-reconciliation"
        },
        {
          "q": "How many days do I have to complete IMS actions for a given month?",
          "a": "The effective window is from the 14th (when GSTR-2B is generated and IMS is populated) to the 20th of the month (standard GSTR-3B filing deadline). That is a six-day window. Taxpayers under the QRMP scheme have until their quarterly filing date, but IMS is still populated monthly. For organisations with high invoice volumes, automating the purchase register vs IMS comparison is the only way to complete actions within this window.",
          "article": "IMS vs GSTR-2B: The New Three-Way Reconciliation Indian Businesses Must Do",
          "url": "https://www.terra-insight.com/insights/ims-vs-gstr-2b-reconciliation"
        },
        {
          "q": "Does IMS affect invoices from before October 2024?",
          "a": "No. IMS applies to inward supplies from October 2024 onwards. Invoices from suppliers who filed GSTR-1 before October 14, 2024 follow the old GSTR-2A / GSTR-2B process without an IMS layer. Any unresolved ITC from pre-October 2024 periods should be handled through the GSTR-2A vs GSTR-2B mismatch resolution process and, if within the time limit, through the supplier filing a correction GSTR-1 amendment.",
          "article": "IMS vs GSTR-2B: The New Three-Way Reconciliation Indian Businesses Must Do",
          "url": "https://www.terra-insight.com/insights/ims-vs-gstr-2b-reconciliation"
        },
        {
          "q": "What is the difference between IMS and GSTR-2A for reconciliation purposes?",
          "a": "GSTR-2A is a dynamic real-time statement that updates whenever a supplier files or amends their GSTR-1. It is read-only — you cannot take action on it. IMS is an actionable layer where you Accept, Reject, or mark invoices as Pending before they lock into GSTR-2B. For reconciliation, GSTR-2A remains useful for monitoring supplier filing compliance in real time throughout the month, while IMS is the mechanism that determines what actually appears in your GSTR-2B.",
          "article": "IMS vs GSTR-2B: The New Three-Way Reconciliation Indian Businesses Must Do",
          "url": "https://www.terra-insight.com/insights/ims-vs-gstr-2b-reconciliation"
        },
        {
          "q": "When did the IMS regime replace the traditional GSTR-2B matching model?",
          "a": "The IMS regime went live on October 14, 2024. From that date, all inward supplies appearing in GSTR-1 filings (from October 2024 onwards) flow through the IMS layer before populating GSTR-2B. Invoices for tax periods before October 2024 follow the legacy auto-populated GSTR-2B model and are not subject to IMS action.",
          "article": "IMS vs Traditional GSTR-2B Matching: What Changed and Why It Matters",
          "url": "https://www.terra-insight.com/insights/ims-vs-traditional-gstr-2b-matching"
        },
        {
          "q": "What is the cash flow difference between the two models for a ₹5 crore monthly inward purchase company?",
          "a": "Under the traditional model, ITC on ₹5 crore at 18 percent GST (₹90 lakh) was claimable in the same month's GSTR-3B as long as suppliers filed GSTR-1 by the 11th. Under IMS, the same ₹90 lakh ITC requires explicit Accept before the 14th-to-20th window — if Pending status is not resolved, ITC defers by one month, creating a one-month working-capital lock of ₹90 lakh on the affected portion.",
          "article": "IMS vs Traditional GSTR-2B Matching: What Changed and Why It Matters",
          "url": "https://www.terra-insight.com/insights/ims-vs-traditional-gstr-2b-matching"
        },
        {
          "q": "Does the IMS model produce more or fewer mismatches than the traditional model?",
          "a": "Total mismatches are similar — supplier errors, amount differences, and GSTIN typos occur at the same rate. What changes is when they surface. Traditional model: mismatches discovered after GSTR-2B generation, resolved next month. IMS model: mismatches surfaced in the IMS dashboard before GSTR-2B locks, resolvable within the same cycle via Reject or Pending. The IMS model gives preventive control where the traditional model only allowed corrective control.",
          "article": "IMS vs Traditional GSTR-2B Matching: What Changed and Why It Matters",
          "url": "https://www.terra-insight.com/insights/ims-vs-traditional-gstr-2b-matching"
        },
        {
          "q": "How does Rule 36(4) compliance differ between the two models?",
          "a": "Traditional model: Rule 36(4) required ITC claim only against invoices in GSTR-2B. Audit trail: purchase register, GSTR-2B, GSTR-3B Table 4. IMS model: same Rule 36(4) requirement, but GSTR-2B is now the IMS-decided subset. Audit trail adds the IMS Accept timestamp as the fourth artefact. The compliance bar is operationally higher because the buyer's active decision is now part of the evidence chain.",
          "article": "IMS vs Traditional GSTR-2B Matching: What Changed and Why It Matters",
          "url": "https://www.terra-insight.com/insights/ims-vs-traditional-gstr-2b-matching"
        },
        {
          "q": "Can a buyer revert to the traditional model or opt out of IMS?",
          "a": "No. The IMS regime is mandatory for all GST-registered taxpayers from October 2024 onwards. There is no opt-out. Buyers who do not actively decide on IMS invoices have those invoices flow into GSTR-2B via the 30-day deemed-Accept mechanism — but the IMS decision step is unavoidable. The traditional auto-populated GSTR-2B model is closed for current-period invoices.",
          "article": "IMS vs Traditional GSTR-2B Matching: What Changed and Why It Matters",
          "url": "https://www.terra-insight.com/insights/ims-vs-traditional-gstr-2b-matching"
        },
        {
          "q": "Is the GST Invoice Management System mandatory for all taxpayers?",
          "a": "IMS is available to all GST-registered recipients whose suppliers file GSTR-1. Taking action in IMS (Accept, Reject, or Pending) is not legally mandated for every invoice, but the default treatment if no action is taken is 'Pending,' which defers the invoice to the next month's GSTR-2B. For businesses that need ITC in the current month's GSTR-3B, deliberate IMS actions before the 20th filing deadline are necessary.",
          "article": "GST Invoice Management System (IMS): How It Changes Your Reconciliation Workflow",
          "url": "https://www.terra-insight.com/insights/invoice-management-system-ims-reconciliation"
        },
        {
          "q": "What happens if I don't take any action in IMS before filing GSTR-3B?",
          "a": "If you take no action, the invoice is treated as 'Pending' by default and excluded from the current month's GSTR-2B. The invoice will roll forward to the next month's GSTR-2B generation cycle on the 14th. This means ITC is deferred by one month, which affects cash flow and may require you to fund the GST payment from working capital in the interim period.",
          "article": "GST Invoice Management System (IMS): How It Changes Your Reconciliation Workflow",
          "url": "https://www.terra-insight.com/insights/invoice-management-system-ims-reconciliation"
        },
        {
          "q": "Can I change my IMS decision after filing GSTR-3B?",
          "a": "Once GSTR-3B is filed, the IMS actions for that month's cycle are locked. You cannot reverse an Accept or Reject after the 3B has been submitted. This is why reconciling your purchase register against IMS before the GSTR-3B deadline (typically the 20th of the month) is critical. Incorrect accepts or rejects must be corrected through the next month's cycle via supplier amendments.",
          "article": "GST Invoice Management System (IMS): How It Changes Your Reconciliation Workflow",
          "url": "https://www.terra-insight.com/insights/invoice-management-system-ims-reconciliation"
        },
        {
          "q": "Does IMS replace GSTR-2A?",
          "a": "No. GSTR-2A remains active as a dynamic statement that updates in real time as suppliers file. IMS is a separate actionable layer that sits between GSTR-2A and GSTR-2B. Think of IMS as the confirmation mechanism: GSTR-2A shows what suppliers have filed, IMS allows you to Accept or Reject before the invoice locks into the static GSTR-2B on the 14th of each month.",
          "article": "GST Invoice Management System (IMS): How It Changes Your Reconciliation Workflow",
          "url": "https://www.terra-insight.com/insights/invoice-management-system-ims-reconciliation"
        },
        {
          "q": "How does IMS affect my GSTR-2B values?",
          "a": "Only invoices you Accept in IMS (or leave as default Accepted) will appear in your GSTR-2B. Invoices you Reject will be excluded from your GSTR-2B entirely. Invoices marked Pending will be excluded from the current month's GSTR-2B and moved to the next month's cycle. Because GSTR-2B is the basis for ITC claims under Rule 36(4), incorrect IMS actions directly alter the ITC available in your return.",
          "article": "GST Invoice Management System (IMS): How It Changes Your Reconciliation Workflow",
          "url": "https://www.terra-insight.com/insights/invoice-management-system-ims-reconciliation"
        },
        {
          "q": "What is ITC reversal under Rule 42?",
          "a": "Rule 42 of the CGST Rules requires reversal of ITC on inputs and input services that are used partly for taxable supplies and partly for exempt supplies or non-business purposes. The reversal is calculated using a two-part formula: D1 represents the exempt-supply proportion of common ITC (common ITC × exempt turnover ÷ total turnover), and D2 represents the non-business proportion (5% of common ITC, per the rule). The total reversal each month is D1 + D2. For example, if a company has ₹10 lakh of common ITC, ₹2 crore exempt turnover, and ₹8 crore total turnover, D1 = ₹10L × 20% = ₹2L, D2 = ₹10L × 5% = ₹50,000. Total reversal = ₹2.5 lakh, reported in GSTR-3B Table 4(B)(1).",
          "article": "ITC Reversal Under Rule 42 and 43: How the Calculation Works",
          "url": "https://www.terra-insight.com/insights/itc-reversal-rule-42-43"
        },
        {
          "q": "How is ITC reversal calculated for mixed-use inputs?",
          "a": "Mixed-use ITC reversal under Rule 42 uses the turnover ratio method. The formula is: T1 (exclusively taxable ITC) is fully claimable; T2 (exclusively exempt ITC) is fully reversed; T3 (blocked under Section 17(5)) is fully reversed; T4 (remaining common ITC) is apportioned. From T4: D1 = T4 × (exempt turnover ÷ total turnover), D2 = T4 × 5% for non-business use, and the balance (T4 − D1 − D2) is eligible. The classification of each invoice into T1, T2, T3, or T4 requires a mapping of each input or input service to its use — which is the reconciliation challenge. Common services like office maintenance at ₹18% GST where the company has both exempt and taxable revenue always land in T4.",
          "article": "ITC Reversal Under Rule 42 and 43: How the Calculation Works",
          "url": "https://www.terra-insight.com/insights/itc-reversal-rule-42-43"
        },
        {
          "q": "What is the difference between Rule 42 and Rule 43 reversal?",
          "a": "Rule 42 covers inputs and input services (recurring purchases — raw materials, professional fees, software subscriptions). The reversal is calculated monthly using the current period turnover ratio and reported immediately. Rule 43 covers capital goods (machinery, servers, vehicles purchased for business use). Because capital goods have a useful life of 60 months under GST, the ITC credit is spread across 60 months at 1/60th per month, and the exempt-proportion reversal is applied each month on the 1/60th amount. A ₹30 lakh server purchased at 18% GST generates ₹5.4 lakh ITC, which is spread at ₹9,000 per month over 60 months. If 25% of usage is for exempt supplies, the Rule 43 reversal is ₹2,250 per month.",
          "article": "ITC Reversal Under Rule 42 and 43: How the Calculation Works",
          "url": "https://www.terra-insight.com/insights/itc-reversal-rule-42-43"
        },
        {
          "q": "Where do Rule 42 and 43 reversals appear in GSTR-3B?",
          "a": "Both Rule 42 and Rule 43 reversals are reported in GSTR-3B Table 4(B) — 'ITC Reversed'. Within Table 4(B), Rule 42 reversals go in row (1): 'As per Rule 42 and 43 of CGST/SGST Rules'. Rule 43 reversals for the monthly 1/60th portion are also included in the same row. Reversals under Section 17(5) (blocked credits) go in row (2). Reversal of IGST credit on import of goods goes in row (3). Any other reversals are in row (4). A common error is combining Rule 42 and Section 17(5) reversals without segregating them, which makes the GSTR-9 reconciliation at year-end significantly more difficult.",
          "article": "ITC Reversal Under Rule 42 and 43: How the Calculation Works",
          "url": "https://www.terra-insight.com/insights/itc-reversal-rule-42-43"
        },
        {
          "q": "How is Rule 42 ITC reversal reconciled in the annual GSTR-9?",
          "a": "Monthly Rule 42 reversals are calculated using provisional turnover ratios — the turnover for that specific month. At year-end, the actual annual turnover ratio (exempt ÷ total for the full financial year) may differ from the sum of monthly provisional ratios. GSTR-9 requires the taxpayer to compute the final Rule 42 reversal for the entire year using the actual annual ratio and compare it to the sum of monthly GSTR-3B reversals. If the annual computation requires more reversal than was done monthly, the differential must be reversed in the March GSTR-3B (or the year's last return). If the annual computation shows over-reversal, the excess can be reclaimed in the March 3B or reported in GSTR-9C. For a company with ₹50 crore total ITC and 15% exempt proportion, a 2% variance in the exempt ratio between provisional and actual generates ₹1 crore in adjustment.",
          "article": "ITC Reversal Under Rule 42 and 43: How the Calculation Works",
          "url": "https://www.terra-insight.com/insights/itc-reversal-rule-42-43"
        },
        {
          "q": "When exactly must ITC be reversed under Rule 37 for non-payment to the supplier?",
          "a": "ITC must be reversed in the GSTR-3B return for the tax period immediately following the expiry of 180 days from the invoice date. For example, if an invoice is dated January 15, 2024, the 180-day period expires on July 13, 2024. If payment has not been made by that date, the ITC must be reversed in the GSTR-3B for July 2024, filed by August 20, 2024. The reversal is proportionate to the unpaid amount.",
          "article": "Rule 37 and Rule 37A: ITC Reversal When Your Supplier Defaults",
          "url": "https://www.terra-insight.com/insights/rule-37-37a-itc-reversal-supplier-default-india"
        },
        {
          "q": "Does Rule 37 require reversal of the entire ITC or only the unpaid portion?",
          "a": "Rule 37 requires proportionate reversal. If 60% of the invoice value has been paid within 180 days and 40% remains outstanding, only the ITC attributable to the 40% unpaid amount must be reversed. The calculation is straightforward: ITC reversed = Total ITC on invoice multiplied by (unpaid amount divided by total invoice value including GST).",
          "article": "Rule 37 and Rule 37A: ITC Reversal When Your Supplier Defaults",
          "url": "https://www.terra-insight.com/insights/rule-37-37a-itc-reversal-supplier-default-india"
        },
        {
          "q": "What is the interest rate on ITC reversed under Rule 37 or Rule 37A?",
          "a": "Interest at 18% per annum under Section 50 of the CGST Act applies if the ITC was utilised before reversal. If the ITC was merely availed (credited to the electronic credit ledger) but not utilised to discharge any tax liability, no interest is payable on reversal. The distinction between availment and utilisation is critical for computing the interest liability accurately.",
          "article": "Rule 37 and Rule 37A: ITC Reversal When Your Supplier Defaults",
          "url": "https://www.terra-insight.com/insights/rule-37-37a-itc-reversal-supplier-default-india"
        },
        {
          "q": "Can ITC reversed under Rule 37A be re-availed if the supplier subsequently files GSTR-3B?",
          "a": "Yes. Rule 37A explicitly permits re-availment of reversed ITC once the supplier files the pending GSTR-3B. There is no time limit for this re-availment, and Section 16(4) does not apply to re-claims of previously reversed ITC. The buyer should re-avail the credit in the GSTR-3B for the period in which the supplier's filing is confirmed in the buyer's GSTR-2B.",
          "article": "Rule 37 and Rule 37A: ITC Reversal When Your Supplier Defaults",
          "url": "https://www.terra-insight.com/insights/rule-37-37a-itc-reversal-supplier-default-india"
        },
        {
          "q": "How does DRC-01C relate to Rule 37 and Rule 37A reversals?",
          "a": "DRC-01C is an auto-generated notice issued when ITC claimed in GSTR-3B exceeds the ITC available in GSTR-2B. While Rule 37 and Rule 37A require reversal based on payment and supplier filing status respectively, DRC-01C targets the aggregate ITC mismatch at the GSTIN level. A buyer who has not reversed ITC under Rule 37A (because the supplier has not filed) may simultaneously receive a DRC-01C notice for the same excess ITC. The response deadline is 7 days from the date of notice.",
          "article": "Rule 37 and Rule 37A: ITC Reversal When Your Supplier Defaults",
          "url": "https://www.terra-insight.com/insights/rule-37-37a-itc-reversal-supplier-default-india"
        },
        {
          "q": "What is the exact deadline under Section 16(4) for claiming ITC on an invoice dated March 15, 2024?",
          "a": "For an invoice dated March 15, 2024, the ITC must be claimed in GSTR-3B filed on or before November 30, 2024, or the date of filing the annual return (GSTR-9) for FY 2023-24, whichever is earlier. If the GSTR-9 for FY 2023-24 is filed on October 15, 2024, the deadline accelerates to October 15, 2024. After this date, the credit is permanently forfeited with no recovery mechanism.",
          "article": "Section 16(4): The Permanent ITC Loss Deadline Every Finance Team Must Track",
          "url": "https://www.terra-insight.com/insights/section-16-4-itc-time-bar-india"
        },
        {
          "q": "Does the Section 16(4) time bar apply to ITC reversed under Rule 37 or Rule 37A?",
          "a": "No. The Section 16(4) time limit applies only to the initial availment of ITC. ITC that was legitimately claimed, subsequently reversed under Rule 37 (180-day non-payment) or Rule 37A (supplier non-filing), and then re-availed upon the condition being met, is not subject to the Section 16(4) deadline. There is no statutory time limit for re-claiming reversed ITC.",
          "article": "Section 16(4): The Permanent ITC Loss Deadline Every Finance Team Must Track",
          "url": "https://www.terra-insight.com/insights/section-16-4-itc-time-bar-india"
        },
        {
          "q": "What happens if a supplier files GSTR-1 late and the invoice appears in GSTR-2B after November 30?",
          "a": "If the supplier files GSTR-1 late and the invoice appears in the buyer's GSTR-2B only after the November 30 deadline, the ITC is permanently lost to the buyer. Section 16(2)(aa) requires the invoice to appear in GSTR-2B as a precondition for claiming ITC, and Section 16(4) imposes the hard deadline. The buyer's only recourse is commercial recovery from the supplier for the lost credit amount.",
          "article": "Section 16(4): The Permanent ITC Loss Deadline Every Finance Team Must Track",
          "url": "https://www.terra-insight.com/insights/section-16-4-itc-time-bar-india"
        },
        {
          "q": "How does Rule 36(4) interact with Section 16(4) for ITC claims?",
          "a": "Rule 36(4) was amended effective January 1, 2022 to restrict ITC claims to the amount appearing in GSTR-2B with zero tolerance. No provisional or excess ITC claim is permitted. This means the buyer must wait for the invoice to appear in GSTR-2B before claiming ITC, while simultaneously tracking the Section 16(4) deadline. If the supplier delays filing beyond November 30 of the following FY, the buyer loses the credit permanently.",
          "article": "Section 16(4): The Permanent ITC Loss Deadline Every Finance Team Must Track",
          "url": "https://www.terra-insight.com/insights/section-16-4-itc-time-bar-india"
        },
        {
          "q": "How much ITC is at risk from GSTR-2B mismatches in India?",
          "a": "The GST Council's annual report for FY 2024-25 noted ₹1.79 lakh crore in ITC fraud detected across 44,938 cases over the preceding 5 years. Industry estimates suggest 5-10% of total ITC claimed by mid-size enterprises faces temporary blocking due to GSTR-2B mismatches each quarter. For an enterprise claiming ₹50 lakh ITC per month, a 5% mismatch rate means ₹2.5 lakh per month at risk of permanent loss if not resolved before the Section 16(4) deadline.",
          "article": "Section 16(4): The Permanent ITC Loss Deadline Every Finance Team Must Track",
          "url": "https://www.terra-insight.com/insights/section-16-4-itc-time-bar-india"
        },
        {
          "q": "What are the five conditions for ITC claim under Section 16 of the CGST Act?",
          "a": "The five conditions are: possession of a tax invoice or debit note, receipt of goods or services (or both), the tax charged has been actually paid to the government by the supplier, the recipient has filed the relevant GSTR-3B return, and payment to the supplier within 180 days from invoice date. All five must be satisfied for an ITC claim to be valid. The IMS regime adds explicit acceptance as a Rule 36(4) compliance step on top of these.",
          "article": "Section 16 ITC Under the IMS Regime: Rule 36(4) Compliance and Audit Defence",
          "url": "https://www.terra-insight.com/insights/section-16-itc-ims-regime-india"
        },
        {
          "q": "Does the IMS Accept timestamp replace any of the Section 16 conditions?",
          "a": "No. The IMS Accept timestamp is an additional Rule 36(4) compliance artefact, not a replacement for the five Section 16 conditions. A buyer must still hold a valid tax invoice, have received the goods or services, ensure the supplier has paid the tax (which the GSTR-1 filing implicitly evidences), file GSTR-3B, and pay the supplier within 180 days. The IMS Accept confirms the buyer's positive action on the invoice — it sits alongside, not in place of, the five conditions.",
          "article": "Section 16 ITC Under the IMS Regime: Rule 36(4) Compliance and Audit Defence",
          "url": "https://www.terra-insight.com/insights/section-16-itc-ims-regime-india"
        },
        {
          "q": "What is the Rule 37 reversal at 180 days and how does it interact with IMS?",
          "a": "Rule 37 of the CGST Rules requires the buyer to reverse ITC if the supplier has not been paid within 180 days from the invoice date. The reversal happens in GSTR-3B Table 4(B). If the buyer subsequently pays the supplier, the ITC can be re-claimed. The IMS workflow is independent of Rule 37 — an invoice can be Accepted in IMS, ITC claimed, and then reversed under Rule 37 if payment is delayed. The audit trail must capture both the IMS Accept and the Rule 37 reversal where applicable.",
          "article": "Section 16 ITC Under the IMS Regime: Rule 36(4) Compliance and Audit Defence",
          "url": "https://www.terra-insight.com/insights/section-16-itc-ims-regime-india"
        },
        {
          "q": "What does the audit defence look like for a Section 16 ITC claim under IMS?",
          "a": "The audit defence is a five-artefact chain per invoice: tax invoice in possession (PDF or digital copy), goods receipt or service-acceptance evidence (GRN, delivery note, service report), supplier GSTR-1 filing evidence (visible in IMS and GSTR-2B), IMS Accept timestamp from the portal, and supplier payment evidence within 180 days (bank statement or remittance proof). The audit pack ties these together with the GSTR-3B Table 4 line item where the ITC was claimed.",
          "article": "Section 16 ITC Under the IMS Regime: Rule 36(4) Compliance and Audit Defence",
          "url": "https://www.terra-insight.com/insights/section-16-itc-ims-regime-india"
        },
        {
          "q": "What happens if Section 16 conditions are met but IMS shows the invoice as Pending?",
          "a": "If all five Section 16 conditions are met but the buyer has not Accepted the invoice in IMS, the invoice does not appear in GSTR-2B for the current month and ITC cannot be claimed in current GSTR-3B. The buyer must Accept in IMS first. If the invoice ages to day 31 in Pending, deemed-Accept fires and the ITC becomes claimable in the next GSTR-2B. The mechanical sequence is: Section 16 conditions plus IMS Accept plus GSTR-2B presence plus GSTR-3B filing plus 180-day payment.",
          "article": "Section 16 ITC Under the IMS Regime: Rule 36(4) Compliance and Audit Defence",
          "url": "https://www.terra-insight.com/insights/section-16-itc-ims-regime-india"
        }
      ]
    },
    "healthcare": {
      "label": "Healthcare Reconciliation",
      "faqs": [
        {
          "q": "How many treatment packages does PM-JAY cover and how are rates determined?",
          "a": "PM-JAY covers 1,929 treatment packages across 27 specialities. Package rates are set by the National Health Authority (NHA) at the central level, but states can modify rates within a band — some states like Rajasthan and Tamil Nadu have state-specific rate cards that differ from the central package rates. Hospitals must reconcile settlements against the applicable state rate, not the central rate, which creates a reconciliation challenge for multi-state hospital chains.",
          "article": "Ayushman Bharat PM-JAY Claim Reconciliation for Empanelled Hospitals",
          "url": "https://www.terra-insight.com/insights/ayushman-bharat-pmjay-claim-reconciliation"
        },
        {
          "q": "What is the TMS portal and how does it affect PM-JAY claim reconciliation?",
          "a": "TMS (Transaction Management System) is the digital platform through which all PM-JAY claims are submitted, tracked, and settled. Hospitals submit claims through TMS with treatment details, package codes, and supporting documents. The claim moves through stages — submitted, under review, approved, settled — and each stage is timestamped in TMS. Reconciliation requires matching the TMS-approved claim amount against the actual bank credit received, as the settlement is processed through the State Health Agency (SHA).",
          "article": "Ayushman Bharat PM-JAY Claim Reconciliation for Empanelled Hospitals",
          "url": "https://www.terra-insight.com/insights/ayushman-bharat-pmjay-claim-reconciliation"
        },
        {
          "q": "Why do PM-JAY settlement amounts differ from the approved package rate?",
          "a": "Settlement amounts may differ from approved package rates for several reasons: the state applies a different rate than the central package rate, the SHA deducts TDS under Section 194J at 10% on the gross settlement, the claim was partially approved due to incomplete documentation, or the hospital is classified under a different tier (public vs private, NABH-accredited vs non-accredited) with different rate multipliers. Each of these variances must be identified and categorised separately during reconciliation.",
          "article": "Ayushman Bharat PM-JAY Claim Reconciliation for Empanelled Hospitals",
          "url": "https://www.terra-insight.com/insights/ayushman-bharat-pmjay-claim-reconciliation"
        },
        {
          "q": "How long does PM-JAY claim settlement take from discharge to bank credit?",
          "a": "The NHA target is 15 days from claim approval to settlement. In practice, settlement timelines vary by state — some states like Kerala settle within 20–30 days, while others take 60–90 days. The full cycle from patient discharge to bank credit includes claim submission (1–3 days), claim review and approval (7–15 days), and settlement processing by the SHA (15–60 days). Total end-to-end timelines of 30 to 90 days are common across most states.",
          "article": "Ayushman Bharat PM-JAY Claim Reconciliation for Empanelled Hospitals",
          "url": "https://www.terra-insight.com/insights/ayushman-bharat-pmjay-claim-reconciliation"
        },
        {
          "q": "How should hospitals handle PM-JAY claims that are approved in TMS but not yet settled in the bank?",
          "a": "Claims approved in TMS but not yet reflected as bank credits should be tracked as receivables with ageing analysis. Under Indian Accounting Standards (Ind AS 115), revenue can be recognised at the point of claim approval if collection is probable. However, the bank reconciliation must separately track the approved-but-unsettled bucket. If a claim remains unsettled beyond 90 days, it should be escalated to the SHA and provisioned as a doubtful receivable per the hospital's provisioning policy.",
          "article": "Ayushman Bharat PM-JAY Claim Reconciliation for Empanelled Hospitals",
          "url": "https://www.terra-insight.com/insights/ayushman-bharat-pmjay-claim-reconciliation"
        },
        {
          "q": "What is the IRDAI-mandated timeline for cashless claim preauthorisation?",
          "a": "Under IRDAI guidelines, insurers and TPAs must provide initial preauthorisation for cashless claims within 1 hour of the hospital's request for planned admissions. For emergency admissions, the initial response must come within 1 hour of intimation. If additional information is needed, the TPA must communicate this within the same 1-hour window. Final preauth approval or rejection must be communicated within 24 hours. Non-compliance exposes the insurer to regulatory action by IRDAI.",
          "article": "Cashless Claim Settlement Reconciliation for Hospitals and Insurers",
          "url": "https://www.terra-insight.com/insights/cashless-claim-settlement-reconciliation"
        },
        {
          "q": "How does the preauth amount differ from the final settlement amount in cashless claims?",
          "a": "The preauth amount is an initial approval based on the expected treatment plan. The final settlement is based on the actual treatment delivered. For example, a knee replacement may receive a preauth of ₹2.5 lakh, but the final bill may be ₹3.2 lakh due to extended ICU stay or additional procedures. The TPA reviews the final bill and may approve the full amount, apply sub-limits (e.g., ICU charges capped at ₹5,000/day), or disallow certain items. The difference between preauth and final settlement creates the reconciliation variance that must be tracked.",
          "article": "Cashless Claim Settlement Reconciliation for Hospitals and Insurers",
          "url": "https://www.terra-insight.com/insights/cashless-claim-settlement-reconciliation"
        },
        {
          "q": "What is split-payer reconciliation in cashless hospital claims?",
          "a": "Split-payer reconciliation occurs when a patient's hospital bill is paid by two or more parties. In a typical cashless claim, the insurer pays the approved amount through TPA settlement, and the patient pays the co-pay or non-covered charges directly. For a ₹5 lakh bill where the insurer approves ₹4.5 lakh, the patient must pay ₹50,000 as co-pay. Both amounts must reconcile against the same patient episode — the TPA settlement arrives as part of a batch credit weeks later, while the patient co-pay may be collected at discharge via cash or UPI.",
          "article": "Cashless Claim Settlement Reconciliation for Hospitals and Insurers",
          "url": "https://www.terra-insight.com/insights/cashless-claim-settlement-reconciliation"
        },
        {
          "q": "How long does final cashless claim settlement take after patient discharge?",
          "a": "IRDAI mandates that final claim settlement must occur within 30 days of the hospital submitting the final bill and all supporting documents to the TPA. In practice, the hospital submits the final bill within 3–5 days of discharge, and the TPA processes it within 15–30 days. Bank credit for the batch settlement may take an additional 5–10 days. The total cycle from discharge to bank credit typically ranges from 25 to 45 days, though disputed claims can extend beyond 60 days.",
          "article": "Cashless Claim Settlement Reconciliation for Hospitals and Insurers",
          "url": "https://www.terra-insight.com/insights/cashless-claim-settlement-reconciliation"
        },
        {
          "q": "What happens when a TPA enhances or reduces the preauth amount mid-treatment?",
          "a": "Enhancement requests occur when the treatment cost exceeds the original preauth. The hospital submits an enhancement request through the TPA portal with clinical justification. The TPA has 4 hours to respond to enhancement requests under IRDAI norms. If approved, the new preauth amount replaces the original. If denied, the excess becomes patient liability. Each enhancement creates a new preauth entry that must be linked to the original claim for reconciliation. Some claims have 2–3 enhancements, each changing the expected settlement amount.",
          "article": "Cashless Claim Settlement Reconciliation for Hospitals and Insurers",
          "url": "https://www.terra-insight.com/insights/cashless-claim-settlement-reconciliation"
        },
        {
          "q": "How many beneficiaries does CGHS cover in India?",
          "a": "CGHS covers approximately 38 lakh beneficiaries across India, including serving central government employees, pensioners, Members of Parliament, judges, and freedom fighters. The scheme operates through CGHS wellness centres in 80+ cities, with empanelled hospitals providing cashless or reimbursement-based treatment. Settlements are processed by city-wise CGHS offices, each with its own processing cadence.",
          "article": "CGHS Reconciliation: How Hospitals Match Central Government Health Scheme Claims",
          "url": "https://www.terra-insight.com/insights/cghs-reconciliation-india"
        },
        {
          "q": "Why do CGHS rates differ from private hospital rates?",
          "a": "CGHS rates are fixed by the Ministry of Health and Family Welfare and are typically 30-50% lower than NABH-accredited private hospital rates. For example, a knee replacement surgery that a hospital bills at ₹3.5 lakh under private insurance may carry a CGHS package rate of ₹1.8-2.2 lakh. Empanelled hospitals agree to accept CGHS rates as full payment for listed procedures, making rate-difference reconciliation a structural part of every settlement cycle.",
          "article": "CGHS Reconciliation: How Hospitals Match Central Government Health Scheme Claims",
          "url": "https://www.terra-insight.com/insights/cghs-reconciliation-india"
        },
        {
          "q": "What is the referral chain requirement for CGHS claims?",
          "a": "Every CGHS claim requires a valid referral from a CGHS wellness centre to the empanelled hospital. The referral letter specifies the approved procedure or treatment category. Claims submitted without a valid referral — or where the treatment performed differs from the referral scope — are rejected during CGHS audit. Hospitals must match each claim against the referral letter number and validate that the procedure code falls within the referral scope before submission.",
          "article": "CGHS Reconciliation: How Hospitals Match Central Government Health Scheme Claims",
          "url": "https://www.terra-insight.com/insights/cghs-reconciliation-india"
        },
        {
          "q": "How long does CGHS take to settle hospital claims?",
          "a": "CGHS settlement timelines vary by city office and claim type. Routine outpatient claims settle in 30-45 days. Inpatient package claims take 45-90 days on average, with some city offices reporting backlogs extending to 120 days. Emergency claims without prior referral take longer due to additional documentation requirements. Hospitals should track ageing by city office and claim type separately to identify systemic delays.",
          "article": "CGHS Reconciliation: How Hospitals Match Central Government Health Scheme Claims",
          "url": "https://www.terra-insight.com/insights/cghs-reconciliation-india"
        },
        {
          "q": "What documents are required for CGHS claim submission?",
          "a": "CGHS claims require: (1) valid CGHS beneficiary card or e-card details, (2) referral letter from the CGHS wellness centre with permission number, (3) discharge summary with procedure codes, (4) itemised bill matching CGHS rate schedule, (5) pre-authorisation approval for listed procedures, and (6) investigation reports supporting the treatment. Missing any document results in claim return, and resubmission resets the settlement clock.",
          "article": "CGHS Reconciliation: How Hospitals Match Central Government Health Scheme Claims",
          "url": "https://www.terra-insight.com/insights/cghs-reconciliation-india"
        },
        {
          "q": "How many beneficiaries does ECHS cover in India?",
          "a": "ECHS covers approximately 55 lakh beneficiaries, including ex-servicemen, their dependants, and war widows. The scheme operates through 427 ECHS polyclinics across India and empanels private hospitals for secondary and tertiary care. Each beneficiary holds a smart card that must be validated at the point of admission for cashless treatment.",
          "article": "ECHS Reconciliation: Ex-Servicemen Health Scheme Claim Settlement Matching",
          "url": "https://www.terra-insight.com/insights/echs-reconciliation-india"
        },
        {
          "q": "What is the typical ECHS settlement cycle for empanelled hospitals?",
          "a": "ECHS settlements take 60 to 120 days from claim submission. The claim flows from the empanelled hospital to the Station HQ, then to the Regional Centre for audit and approval, and finally to the payment authority. Claims requiring additional documentation or those flagged during audit can extend to 150+ days. Hospitals should maintain separate ageing buckets for ECHS claims given this extended cycle.",
          "article": "ECHS Reconciliation: Ex-Servicemen Health Scheme Claim Settlement Matching",
          "url": "https://www.terra-insight.com/insights/echs-reconciliation-india"
        },
        {
          "q": "How do ECHS package rates compare to CGHS and PM-JAY rates?",
          "a": "ECHS package rates are independently set and differ from both CGHS and PM-JAY schedules. For a standard cataract surgery, ECHS may reimburse ₹15,000-20,000, CGHS ₹18,000-25,000, and PM-JAY ₹12,000 under Health Benefit Package 2.2. Hospitals empanelled under multiple government schemes must maintain separate rate cards and ensure the correct rate schedule is applied during billing.",
          "article": "ECHS Reconciliation: Ex-Servicemen Health Scheme Claim Settlement Matching",
          "url": "https://www.terra-insight.com/insights/echs-reconciliation-india"
        },
        {
          "q": "What is the polyclinic referral requirement for ECHS claims?",
          "a": "Every ECHS claim requires a referral from an ECHS polyclinic. The referral specifies the condition, approved specialty, and the empanelled hospital. Emergency admissions can bypass polyclinic referral but require post-facto intimation within 24 hours and subsequent validation by the polyclinic medical officer. Claims submitted without referral or with expired referrals are rejected at Station HQ audit.",
          "article": "ECHS Reconciliation: Ex-Servicemen Health Scheme Claim Settlement Matching",
          "url": "https://www.terra-insight.com/insights/echs-reconciliation-india"
        },
        {
          "q": "Why do ECHS claims get rejected during Station HQ audit?",
          "a": "Common ECHS rejection reasons include: referral letter expired or not matching the treatment performed, smart card not validated at admission, procedure not listed in the ECHS package directory, billing above ECHS package rate, incomplete discharge summary, and missing investigation reports. The Station HQ medical audit team reviews every claim before forwarding to the Regional Centre for payment, and any documentation gap results in claim return with a 30-45 day resubmission delay.",
          "article": "ECHS Reconciliation: Ex-Servicemen Health Scheme Claim Settlement Matching",
          "url": "https://www.terra-insight.com/insights/echs-reconciliation-india"
        },
        {
          "q": "How does GST apply to hospital room rent in India and what is the reconciliation impact?",
          "a": "Since the July 2022 GST amendment, hospital room rent above ₹5,000 per day attracts 5% GST without input tax credit. Room rent at or below ₹5,000 per day remains exempt. For multi-speciality hospitals with rooms at different price points, the billing system must split GST and non-GST components on the same patient invoice. The reconciliation system must verify that GST collected matches GST reported in GSTR-1 and that exempt room revenue is correctly excluded.",
          "article": "Hospital Billing Reconciliation: OPD, IPD, and Patient Deposit Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-billing-reconciliation-india"
        },
        {
          "q": "What is patient deposit lifecycle tracking and why is it a reconciliation challenge?",
          "a": "Patient deposits follow a lifecycle: initial deposit at admission, partial consumption during treatment, possible top-ups, and final settlement or refund at discharge. A patient admitted with a ₹1 lakh deposit may consume ₹60,000 during a 5-day stay, receive a ₹40,000 refund at discharge, and then have an insurance claim settle ₹3.5 lakh separately. The deposit, consumption, refund, and insurance settlement are four separate entries that must all reconcile against the same patient episode in the HIS.",
          "article": "Hospital Billing Reconciliation: OPD, IPD, and Patient Deposit Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-billing-reconciliation-india"
        },
        {
          "q": "How do UPI collections appear in a hospital's bank statement for reconciliation?",
          "a": "UPI collections from OPD counters and pharmacy terminals are settled by the payment gateway (Razorpay, Pine Labs, etc.) as a netted daily credit — total UPI collections minus MDR and GST on MDR. A hospital collecting ₹4.2 lakh in UPI payments across 180 transactions receives a single bank credit of approximately ₹4.12 lakh after MDR deduction. The 180 individual transaction details are available only in the payment gateway settlement report, not in the bank narration.",
          "article": "Hospital Billing Reconciliation: OPD, IPD, and Patient Deposit Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-billing-reconciliation-india"
        },
        {
          "q": "How should hospitals reconcile cash deposits against OPD collections?",
          "a": "Cash collected at OPD counters is deposited into the bank account, typically at end of day. A hospital with 5 OPD counters may make 2–3 cash deposits daily, each covering collections from multiple counters. The bank statement shows the deposit amount and a deposit slip reference — not the counter-level breakdown. Reconciliation requires matching the bank deposit entry to the cash register totals from each counter in the HIS, accounting for any denomination differences or cash handling discrepancies.",
          "article": "Hospital Billing Reconciliation: OPD, IPD, and Patient Deposit Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-billing-reconciliation-india"
        },
        {
          "q": "What is the TDS impact on corporate health checkup billing for hospitals?",
          "a": "When hospitals invoice corporates for employee health checkups, the corporate deducts TDS under Section 194J at 10% before payment. A hospital billing ₹10 lakh for a bulk health checkup receives ₹9 lakh in the bank. The ₹1 lakh TDS must be tracked as a receivable and verified against Form 26AS. If the corporate files the TDS return late or with incorrect details, the hospital cannot claim the TDS credit in its income tax return until the mismatch is resolved through TRACES.",
          "article": "Hospital Billing Reconciliation: OPD, IPD, and Patient Deposit Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-billing-reconciliation-india"
        },
        {
          "q": "How many insurance companies does a typical Indian hospital deal with?",
          "a": "A mid-size Indian hospital (100-300 beds) typically manages empanelments with 5 to 15 insurance companies simultaneously. Each insurer operates through one or more TPAs, and each TPA has its own claim submission portal, file format, rate negotiation, and settlement cycle. A 500-bed multi-specialty hospital may deal with 20+ insurer-TPA combinations, each requiring separate reconciliation tracking.",
          "article": "Hospital-Insurance Reconciliation: Multi-Payer Settlement Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-insurance-reconciliation-india"
        },
        {
          "q": "What is the IRDAI-mandated timeline for settling cashless health insurance claims?",
          "a": "Under IRDAI Health Insurance Regulations 2024, insurers must process preauthorisation requests within 1 hour for cashless claims. Final claim settlement must be completed within 30 days of receiving the last necessary document from the hospital. Delays beyond 30 days entitle the hospital to interest on the outstanding amount. Hospitals should track the 'last document submitted' date per claim to enforce this timeline during reconciliation.",
          "article": "Hospital-Insurance Reconciliation: Multi-Payer Settlement Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-insurance-reconciliation-india"
        },
        {
          "q": "What causes revenue leakage in hospital-insurance reconciliation?",
          "a": "The five primary revenue leakage sources are: (1) underpaid claims where the insurer settles below the agreed tariff without documented disallowance, (2) rejected claims not resubmitted within the appeal window, (3) co-pay amounts billed to patients but not collected, (4) TDS deducted by insurers under Section 194J but not reflected in Form 26AS, and (5) rate differences between the hospital's billed amount and the TPA-negotiated tariff that are written off without review.",
          "article": "Hospital-Insurance Reconciliation: Multi-Payer Settlement Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-insurance-reconciliation-india"
        },
        {
          "q": "How do TPA batch settlements complicate hospital reconciliation?",
          "a": "TPAs batch multiple claim settlements into a single bank transfer. One NEFT credit of ₹12 lakh may cover 40-80 individual claims, with partial payments, disallowances, and deductions netted into the total. The hospital receives a settlement file (CSV or Excel) listing individual claim amounts, but the sum of individual amounts often differs from the bank credit by ₹500-5,000 due to TDS deductions, processing fees, or rounding. Unpacking each batch requires line-by-line matching against the hospital billing system.",
          "article": "Hospital-Insurance Reconciliation: Multi-Payer Settlement Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-insurance-reconciliation-india"
        },
        {
          "q": "Is TDS applicable on insurance claim settlements to hospitals?",
          "a": "TDS under Section 194J at 10% applies when insurance companies or TPAs make payments to hospitals for corporate health checkup packages or retainer-based wellness programmes. Regular cashless claim settlements are generally treated as reimbursement of medical expenses and not subject to TDS. However, some insurers deduct TDS on bulk settlements, creating a TDS receivable that must be reconciled against Form 26AS quarterly.",
          "article": "Hospital-Insurance Reconciliation: Multi-Payer Settlement Matching in India",
          "url": "https://www.terra-insight.com/insights/hospital-insurance-reconciliation-india"
        },
        {
          "q": "What is the IRDAI-mandated claim settlement timeline for health insurance?",
          "a": "Under IRDAI Health Insurance Regulations 2024, insurers must settle claims within 30 days of receiving the last necessary document. For cashless claims, initial preauthorisation must be processed within 1 hour. If the insurer requires additional documents, the request must be made within 15 days of claim receipt. Failure to settle within the mandated timeline entitles the claimant to interest at the bank rate on the outstanding amount from the date of claim to the date of payment.",
          "article": "IRDAI Compliance Reconciliation: Audit Trail and Claim Settlement Reporting for Hospitals",
          "url": "https://www.terra-insight.com/insights/irdai-compliance-reconciliation-india"
        },
        {
          "q": "What is IGMS and how does it affect hospital reconciliation?",
          "a": "IGMS (Integrated Grievance Management System) is IRDAI's centralised portal for insurance grievances. When a hospital or patient files a complaint regarding claim settlement delays, partial payments, or wrongful rejections, IGMS generates a unique grievance number. Insurers must respond within 15 days. Hospitals should track IGMS grievance numbers alongside claim IDs in their reconciliation system to monitor which disputed claims have active regulatory complaints.",
          "article": "IRDAI Compliance Reconciliation: Audit Trail and Claim Settlement Reporting for Hospitals",
          "url": "https://www.terra-insight.com/insights/irdai-compliance-reconciliation-india"
        },
        {
          "q": "What audit trail documents must hospitals maintain for IRDAI compliance?",
          "a": "Hospitals must maintain: (1) preauthorisation requests and approvals with timestamps, (2) claim submission records with document checklists, (3) settlement files from TPAs with line-by-line reconciliation, (4) disallowance communications with insurer responses, (5) IGMS grievance records for disputed claims, (6) rate agreements with each TPA/insurer, and (7) patient consent forms for cashless treatment. These records must be retained for a minimum of 8 years as per IRDAI guidelines.",
          "article": "IRDAI Compliance Reconciliation: Audit Trail and Claim Settlement Reporting for Hospitals",
          "url": "https://www.terra-insight.com/insights/irdai-compliance-reconciliation-india"
        },
        {
          "q": "How does IRDAI regulate TPA operations in India?",
          "a": "IRDAI registers and regulates all Third Party Administrators under the IRDAI (TPA - Health Services) Regulations. TPAs must maintain a minimum net worth of ₹1 crore, employ qualified medical professionals for claim adjudication, and submit quarterly reports to IRDAI on claim processing volumes, settlement ratios, and turnaround times. Hospitals empanelled with TPAs can verify TPA registration status on the IRDAI website and escalate through IRDAI if a TPA violates settlement timelines.",
          "article": "IRDAI Compliance Reconciliation: Audit Trail and Claim Settlement Reporting for Hospitals",
          "url": "https://www.terra-insight.com/insights/irdai-compliance-reconciliation-india"
        },
        {
          "q": "What penalties can IRDAI impose for non-compliance with claim settlement norms?",
          "a": "IRDAI can impose penalties up to ₹1 crore per violation under Section 102 of the Insurance Act, 1938 (as amended). For repeated delays in claim settlement, IRDAI can issue directions to the insurer, suspend the insurer's licence for specific product lines, or initiate action against the TPA's registration. Hospitals can use these regulatory provisions as leverage when following up on systematically delayed settlements by filing complaints through IGMS.",
          "article": "IRDAI Compliance Reconciliation: Audit Trail and Claim Settlement Reporting for Hospitals",
          "url": "https://www.terra-insight.com/insights/irdai-compliance-reconciliation-india"
        },
        {
          "q": "How many TPAs operate in India and do they use the same settlement file format?",
          "a": "There are 19+ licensed TPAs in India, including Star Health TPA, Medi Assist, Paramount Health Services, and MD India. Each TPA uses a different settlement file format — some send CSV, others send Excel with varying column structures. There is no IRDAI-mandated standard file format for settlement sidecar files, which means hospitals must maintain a separate parsing configuration for each TPA they work with.",
          "article": "TPA Settlement Reconciliation for Indian Hospitals",
          "url": "https://www.terra-insight.com/insights/tpa-settlement-reconciliation-india"
        },
        {
          "q": "What is the typical settlement cycle for TPA claims in Indian hospitals?",
          "a": "TPA settlement cycles in India range from 15 to 90 days depending on the insurer and claim type. Cashless claims under IRDAI guidelines must receive initial preauthorisation within 1 hour and final settlement within 30 days of discharge. In practice, reimbursement claims take 45 to 90 days. Partial settlements and disputed amounts extend the effective cycle further, with some claims remaining open for 120+ days.",
          "article": "TPA Settlement Reconciliation for Indian Hospitals",
          "url": "https://www.terra-insight.com/insights/tpa-settlement-reconciliation-india"
        },
        {
          "q": "What is a TPA settlement sidecar file and why is it needed for reconciliation?",
          "a": "A TPA settlement sidecar file is the claim-level detail file that accompanies a batch bank credit. When a TPA settles 200 claims in one payment, the bank statement shows a single credit entry. The sidecar file lists each individual claim number, patient name, approved amount, deducted amount, and net payable. Without this file, the hospital cannot determine which specific claims were settled, partially paid, or rejected within that batch.",
          "article": "TPA Settlement Reconciliation for Indian Hospitals",
          "url": "https://www.terra-insight.com/insights/tpa-settlement-reconciliation-india"
        },
        {
          "q": "How do TPA clawbacks appear in hospital bank statements?",
          "a": "TPA clawbacks appear as negative settlement amounts — a debit entry in the bank statement referencing a previous batch. This happens when the TPA reverses a previously settled claim due to audit findings, duplicate claims, or policy disputes. Clawback amounts are netted against the current batch settlement, so the bank credit may be lower than the sum of approved claims. Some TPAs send a separate clawback file; others include negative line items within the regular settlement sidecar.",
          "article": "TPA Settlement Reconciliation for Indian Hospitals",
          "url": "https://www.terra-insight.com/insights/tpa-settlement-reconciliation-india"
        },
        {
          "q": "What happens when a TPA partially settles a claim and how should it be reconciled?",
          "a": "A partial settlement occurs when the TPA approves less than the hospital's billed amount — typically due to rate differences between the hospital's tariff and the insurer's approved package rate. For example, a hospital bills ₹2.5 lakh for a procedure but the TPA approves ₹1.8 lakh based on the insurance policy's sub-limits. The ₹70,000 difference must be tracked separately as either patient liability (co-pay) or a write-off. The reconciliation system must match the partial settlement to the original claim and flag the variance for billing follow-up.",
          "article": "TPA Settlement Reconciliation for Indian Hospitals",
          "url": "https://www.terra-insight.com/insights/tpa-settlement-reconciliation-india"
        }
      ]
    },
    "bsa-forensics": {
      "label": "Bank Statement Fraud and Forensics",
      "faqs": [
        {
          "q": "What is balance chain verification in a bank statement?",
          "a": "Balance chain verification is the process of independently recomputing the running balance for each transaction row: prior balance plus credit minus debit must equal the printed balance for that row. If the computed balance differs from the printed balance at any point in the statement, that discrepancy indicates that a transaction was added, deleted, or altered — the running balance chain is broken. This check is performed row by row across the entire statement.",
          "article": "Balance Chain Verification: Catching Altered Bank Statements Row by Row",
          "url": "https://www.terra-insight.com/insights/balance-chain-verification-bank-statement"
        },
        {
          "q": "What does a boosted opening balance indicate?",
          "a": "A boosted opening balance occurs when the opening balance on the statement is set higher than what the observable cash flows — deposits and withdrawals during the statement period — can explain. This is a common manipulation used to make an account appear well-funded for credit purposes. The fraud lies in the opening balance figure itself, which was manually inflated before the rest of the statement was constructed around it.",
          "article": "Balance Chain Verification: Catching Altered Bank Statements Row by Row",
          "url": "https://www.terra-insight.com/insights/balance-chain-verification-bank-statement"
        },
        {
          "q": "Can balance chain verification be done manually for a 6-month bank statement?",
          "a": "Technically yes, but practically it is not viable at scale. A 6-month statement from an active business account may contain 500 to 2,000 transaction rows. Manually recomputing each running balance and cross-checking it against the printed balance would take 4 to 8 hours per statement. Automated checking covers the same work in seconds, with a row-level exception output that shows exactly which row breaks the chain.",
          "article": "Balance Chain Verification: Catching Altered Bank Statements Row by Row",
          "url": "https://www.terra-insight.com/insights/balance-chain-verification-bank-statement"
        },
        {
          "q": "Does balance chain verification work on scanned bank statements?",
          "a": "It works on scanned statements after OCR extraction. The accuracy depends on OCR quality — degraded or low-resolution scans can introduce extraction errors that produce false balance mismatches. Automated systems flag this distinction: a mismatch on a digital PDF is a strong fraud signal; a mismatch on a low-quality scan warrants OCR verification before a fraud conclusion is drawn.",
          "article": "Balance Chain Verification: Catching Altered Bank Statements Row by Row",
          "url": "https://www.terra-insight.com/insights/balance-chain-verification-bank-statement"
        },
        {
          "q": "Is balance chain verification different from bank reconciliation?",
          "a": "Yes. Bank reconciliation compares a bank statement against an entity's own accounting records to identify timing differences — outstanding cheques, deposits in transit. Balance chain verification is an internal consistency check within the statement itself — it asks whether the statement's own numbers are arithmetically coherent. You do not need the entity's books to run it; you need only the statement.",
          "article": "Balance Chain Verification: Catching Altered Bank Statements Row by Row",
          "url": "https://www.terra-insight.com/insights/balance-chain-verification-bank-statement"
        },
        {
          "q": "What PDF metadata fields indicate a bank statement has been tampered with?",
          "a": "The most telling fields are CreationDate and ModDate. If ModDate is later than CreationDate, the file was modified after it was first generated — a strong indicator of editing. The Creator and Producer fields also matter: a genuine bank-generated PDF will show banking software like Finacle, Flexcube, iText, or Crystal Reports. If those fields show a consumer PDF editor such as iLovePDF, Foxit PDF Editor, Adobe Acrobat DC, or LibreOffice, the document was processed through an editing tool after generation.",
          "article": "Bank Statement PDF Metadata Inspection: What Credit Teams Should Check",
          "url": "https://www.terra-insight.com/insights/bank-statement-metadata-inspection"
        },
        {
          "q": "Can a bank statement be modified without changing the metadata?",
          "a": "Advanced tools can strip or spoof metadata, but this requires deliberate effort and leaves other traces. Most statement fraud uses consumer tools — online PDF editors, desktop software — that update metadata automatically. Even when metadata is stripped, balance chain verification and digit-pattern analysis provide independent checks that do not rely on metadata integrity.",
          "article": "Bank Statement PDF Metadata Inspection: What Credit Teams Should Check",
          "url": "https://www.terra-insight.com/insights/bank-statement-metadata-inspection"
        },
        {
          "q": "Do all Indian banks produce PDFs with the same metadata format?",
          "a": "No. Large private sector banks — HDFC, ICICI, Axis — tend to produce PDFs with consistent, clean metadata from their core banking systems. PSU banks (SBI, PNB, Bank of Baroda) and smaller co-operative and RRB banks vary considerably. Some regional co-operative banks generate statements via third-party reporting tools, which may produce different but still legitimate Creator and Producer values. Unknown or ambiguous metadata is categorised separately from clearly flagged values.",
          "article": "Bank Statement PDF Metadata Inspection: What Credit Teams Should Check",
          "url": "https://www.terra-insight.com/insights/bank-statement-metadata-inspection"
        },
        {
          "q": "Is PDF metadata inspection sufficient on its own to flag a fraudulent statement?",
          "a": "No. Metadata inspection is one signal among several. A statement with clean metadata can still have altered transaction amounts or a manipulated balance chain. Conversely, a legitimate statement may have been re-exported through a PDF tool for legitimate reasons (e.g., password removal by a CA). Credit teams should treat metadata inspection as an initial filter, not a standalone verdict.",
          "article": "Bank Statement PDF Metadata Inspection: What Credit Teams Should Check",
          "url": "https://www.terra-insight.com/insights/bank-statement-metadata-inspection"
        },
        {
          "q": "Which credit teams benefit most from automated PDF metadata inspection?",
          "a": "NBFC credit managers reviewing 50 to 500 files per month benefit the most. Manual metadata inspection requires opening each file's document properties, which takes 2 to 3 minutes per file. At 200 files per month, that is 7 to 10 staff hours spent on a single check. Automated inspection delivers the same signal in seconds per file, so credit teams can focus review time on files that actually show flags.",
          "article": "Bank Statement PDF Metadata Inspection: What Credit Teams Should Check",
          "url": "https://www.terra-insight.com/insights/bank-statement-metadata-inspection"
        },
        {
          "q": "What does counterparty spread analysis check in a bank statement?",
          "a": "Counterparty spread analysis examines the distribution of transaction counterparties across the statement. Genuine accounts show a concentration pattern: a small number of counterparties account for a large share of transactions and value, with a long tail of infrequent one-offs. Fabricated statements tend to show a more uniform distribution — many counterparties appearing at similar frequencies — because the person constructing the statement adds variety deliberately but ends up with an unnaturally flat distribution that real spending does not produce.",
          "article": "Counterparty Spread Analysis: Detecting Unnatural Distribution in Bank Statements",
          "url": "https://www.terra-insight.com/insights/counterparty-spread-analysis-statements"
        },
        {
          "q": "How is counterparty spread analysis different from AML round-trip detection?",
          "a": "They address different questions. Counterparty spread analysis asks: does the distribution of payees look like genuine organic spending? It flags fabrication by detecting unnatural uniformity. AML round-trip detection asks: are specific credit-debit pairs with the same counterparty at similar amounts suggesting circular fund movement? Round-trip detection identifies suspicious fund flows in otherwise genuine-looking accounts. A statement can fail one check but pass the other — they are complementary, not duplicative.",
          "article": "Counterparty Spread Analysis: Detecting Unnatural Distribution in Bank Statements",
          "url": "https://www.terra-insight.com/insights/counterparty-spread-analysis-statements"
        },
        {
          "q": "Which Indian consumer counterparties should appear in a genuine retail account?",
          "a": "A genuine Indian consumer account active over 6 to 12 months would typically show repeated transactions from a predictable set: utility providers (electricity, mobile, broadband), food delivery (Swiggy, Zomato), e-commerce (Amazon, Flipkart, Myntra), ride sharing (Ola, Uber), and financial services (insurance, EMIs, mutual fund platforms). The absence of any recognisable consumer counterparties — combined with an unusually even spread of unfamiliar names — is a notable signal, particularly when the account purports to be a salaried individual's primary account.",
          "article": "Counterparty Spread Analysis: Detecting Unnatural Distribution in Bank Statements",
          "url": "https://www.terra-insight.com/insights/counterparty-spread-analysis-statements"
        },
        {
          "q": "Does counterparty spread analysis work for business current accounts?",
          "a": "Yes, with different expectations. A business current account has a different counterparty profile than a salary account: fewer consumer platforms, more vendor and client names, possibly higher transaction values per counterparty. The spread check is calibrated for the account type. A business account with an even spread of 150 counterparties at similar transaction values is as anomalous as a salary account with the same pattern — real businesses have dominant vendors and customers, just as individuals have dominant merchants.",
          "article": "Counterparty Spread Analysis: Detecting Unnatural Distribution in Bank Statements",
          "url": "https://www.terra-insight.com/insights/counterparty-spread-analysis-statements"
        },
        {
          "q": "Can legitimate accounts have even counterparty distributions?",
          "a": "Yes, in some specific cases. A newly opened account with only 2 to 3 months of history will have a thinner counterparty set and the distribution may be less informative. An account used exclusively for a single purpose — such as a rental collection account or a business account that only receives client payments — may have a narrow and even counterparty spread for structural reasons. Counterparty spread analysis is most diagnostic for primary transaction accounts with 6 or more months of diverse activity.",
          "article": "Counterparty Spread Analysis: Detecting Unnatural Distribution in Bank Statements",
          "url": "https://www.terra-insight.com/insights/counterparty-spread-analysis-statements"
        },
        {
          "q": "How does digit-distribution analysis detect fabricated bank statement amounts?",
          "a": "In large sets of naturally occurring financial data, the distribution of leading digits follows a predictable non-uniform pattern — lower digits appear as the first digit far more often than higher digits. Genuine transactions follow this pattern because amounts are determined by independent external events: bills, purchases, salary cycles. A fraudster manually constructing amounts tends to distribute digits more evenly, because the pattern is not intuitive to replicate. Significant deviation from the expected distribution is a fabrication signal that warrants human review.",
          "article": "Detecting Fabricated Bank Statements: How Digit-Pattern Analysis Works",
          "url": "https://www.terra-insight.com/insights/digit-analysis-fabricated-bank-statements"
        },
        {
          "q": "Can digit-pattern analysis produce false positives on legitimate bank statements?",
          "a": "Yes, and this is why it is treated as a signal for review rather than a verdict. Some legitimate account types — salary accounts receiving a fixed monthly credit, EMI-heavy accounts with large round-number recurring payments — deviate from the expected digit distribution for structural reasons. The analysis is most reliable when applied to current accounts with diverse transaction types over a minimum of 3 months of data. Results are interpreted in context alongside other checks.",
          "article": "Detecting Fabricated Bank Statements: How Digit-Pattern Analysis Works",
          "url": "https://www.terra-insight.com/insights/digit-analysis-fabricated-bank-statements"
        },
        {
          "q": "What does sequence pattern analysis check in a bank statement?",
          "a": "Sequence pattern analysis checks whether transaction amounts show rhythms or progressions that would not occur in genuine spending data. Real transactions — electricity bills, grocery purchases, fuel fills — arrive in amounts determined by independent external events. Fabricated transactions often show subtle arithmetic patterns in their amounts: increments of a fixed value, repeated same-amount clusters, or sequences that look artificially varied. The output is a flag indicating whether the amount sequence looks organic or patterned.",
          "article": "Detecting Fabricated Bank Statements: How Digit-Pattern Analysis Works",
          "url": "https://www.terra-insight.com/insights/digit-analysis-fabricated-bank-statements"
        },
        {
          "q": "Which types of applicants are most commonly associated with fabricated bank statements in Indian credit?",
          "a": "MSME and microfinance applicants are the primary risk segment, based on the composition of fraud cases identified in Indian credit bureau and RBI enforcement data. Small business owners and self-employed applicants who do not have audited financial statements may be motivated to present a stronger banking profile. Salaried applicants with below-qualifying income sometimes inflate salary credits. The pattern is not restricted to any income band — forensic CAs have identified fabricated statements at loan values from ₹50,000 microloans to ₹5 crore working capital facilities.",
          "article": "Detecting Fabricated Bank Statements: How Digit-Pattern Analysis Works",
          "url": "https://www.terra-insight.com/insights/digit-analysis-fabricated-bank-statements"
        },
        {
          "q": "Does digit-pattern analysis work on statements with a small number of transactions?",
          "a": "Digit-pattern analysis is less reliable on statements with fewer than 50 transactions because the sample is too small to produce a statistically meaningful distribution comparison. For thin statements, balance chain verification and metadata inspection are the primary forensic checks. Sequence pattern analysis is also less diagnostic on sparse data but can still flag obviously artificial patterns even in small samples.",
          "article": "Detecting Fabricated Bank Statements: How Digit-Pattern Analysis Works",
          "url": "https://www.terra-insight.com/insights/digit-analysis-fabricated-bank-statements"
        },
        {
          "q": "What counts as a duplicate transaction in a bank statement?",
          "a": "A duplicate is identified by three matching fields: same transaction date, same description (or sufficiently similar description after normalisation), and same amount. This exact-match definition is strict by design — a legitimate vendor paid twice in one day for different services would not match because the descriptions or amounts would differ. The strict definition minimises false positives while surfacing genuinely identical entries that require explanation.",
          "article": "Duplicate Transaction Detection in Bank Statements: What It Means for Credit Review",
          "url": "https://www.terra-insight.com/insights/duplicate-transaction-detection-bank-statement"
        },
        {
          "q": "How common are genuine duplicates in multi-statement uploads?",
          "a": "Multi-statement uploads from overlapping periods are a frequent source of genuine duplicates. An NBFC asking for a 12-month statement may receive three separate 4-month PDF files from the applicant. If months 4 and 5 overlap across two of the files, every transaction in that overlap period appears twice in the combined set. Period deduplication removes these before forensic duplicate analysis is applied — without it, a genuine account with overlapping uploads would be incorrectly flagged.",
          "article": "Duplicate Transaction Detection in Bank Statements: What It Means for Credit Review",
          "url": "https://www.terra-insight.com/insights/duplicate-transaction-detection-bank-statement"
        },
        {
          "q": "What duplicate count relative to total transactions suggests fabrication rather than a genuine error?",
          "a": "There is no universal threshold, but as a practical heuristic, 3 or more exact duplicates in a statement with no overlapping period uploads, particularly involving the same counterparty and round-number amounts, warrants investigation. A single duplicate in a 500-transaction statement may be a bank processing error. Ten duplicates across 200 transactions — all involving the same salary payer or vendor, all round amounts — suggests copy-paste construction.",
          "article": "Duplicate Transaction Detection in Bank Statements: What It Means for Credit Review",
          "url": "https://www.terra-insight.com/insights/duplicate-transaction-detection-bank-statement"
        },
        {
          "q": "Can a bank legitimately process the same transaction twice?",
          "a": "Yes, in rare cases. NEFT and RTGS systems occasionally produce duplicate settlement credits due to processing retries, typically followed by a reversal entry. A genuine bank duplicate in the statement should therefore appear as a credit entry followed by a debit reversal of the same amount. A duplicate with no corresponding reversal — two identical credits from the same counterparty on the same date, both showing as permanent entries — is not consistent with a legitimate bank processing double.",
          "article": "Duplicate Transaction Detection in Bank Statements: What It Means for Credit Review",
          "url": "https://www.terra-insight.com/insights/duplicate-transaction-detection-bank-statement"
        },
        {
          "q": "What is period deduplication and why does it matter for bank statement forensics?",
          "a": "Period deduplication identifies and removes transactions that appear in multiple uploaded statements because the statement periods overlap. For example, if a January–June statement and a May–September statement are both uploaded, May and June transactions appear in both files. Without period deduplication, the combined analysis would show those months' transactions twice — inflating apparent income, transaction volume, and balance averages. Period deduplication ensures the analysis runs on a clean, non-overlapping transaction set before any further forensic checks are applied.",
          "article": "Duplicate Transaction Detection in Bank Statements: What It Means for Credit Review",
          "url": "https://www.terra-insight.com/insights/duplicate-transaction-detection-bank-statement"
        },
        {
          "q": "Which payment rails in India are closed on bank holidays?",
          "a": "NEFT (National Electronic Funds Transfer) and RTGS (Real Time Gross Settlement) both operate through RBI's clearing infrastructure, which is closed on RBI-notified national bank holidays, 2nd and 4th Saturdays, and Sundays. Cheque clearing through the CTS (Cheque Truncation System) is similarly closed on those days. UPI and IMPS operate 24 hours a day, 7 days a week, including all holidays. Cash withdrawals and deposits are not time-restricted by settlement rail — their availability depends on branch operating hours.",
          "article": "Impossible-Date Transactions: Why Bank Holiday Checks Matter in Statement Forensics",
          "url": "https://www.terra-insight.com/insights/impossible-date-transactions-bank-statements"
        },
        {
          "q": "Is a NEFT transaction on a national holiday always a fraud signal?",
          "a": "In practice, yes — a NEFT transaction dated on a day when the NEFT network is closed could not have been processed by a real bank. The date in the statement would have to have been manually altered, because the bank's core banking system records the actual settlement date, not a user-specified date. There is no legitimate scenario in which a live banking system produces a NEFT settlement on a closed-network date. This makes it one of the clearest binary fraud signals in statement forensics.",
          "article": "Impossible-Date Transactions: Why Bank Holiday Checks Matter in Statement Forensics",
          "url": "https://www.terra-insight.com/insights/impossible-date-transactions-bank-statements"
        },
        {
          "q": "What Indian bank holidays are most commonly seen in fraudulent statement date entries?",
          "a": "Republic Day (26 January), Independence Day (15 August), Gandhi Jayanti (2 October), and Christmas (25 December) are national holidays that appear most frequently as fraudulent transaction dates — partly because they are memorable dates on which a statement fabricator might set a transaction date without checking whether the bank was open. Diwali and other major regional holidays also appear. The 2nd and 4th Saturdays are a less obvious but equally common source of impossible dates.",
          "article": "Impossible-Date Transactions: Why Bank Holiday Checks Matter in Statement Forensics",
          "url": "https://www.terra-insight.com/insights/impossible-date-transactions-bank-statements"
        },
        {
          "q": "Why does the holiday calendar need to cover multiple years for bank statement forensics?",
          "a": "Credit teams typically review 12-month bank statements, and some forensic and insolvency reviews cover 3 to 5 years of statements. A holiday calendar that covers only the current year will miss impossible dates in historical portions of the statement. With 150+ RBI-notified bank holidays from 2019 to 2026 built in, automated checking applies the correct calendar year for each transaction date rather than applying a single year's list to the entire statement.",
          "article": "Impossible-Date Transactions: Why Bank Holiday Checks Matter in Statement Forensics",
          "url": "https://www.terra-insight.com/insights/impossible-date-transactions-bank-statements"
        },
        {
          "q": "Does the holiday check apply differently to UPI and IMPS transactions?",
          "a": "UPI and IMPS are explicitly excluded from this check because both rails operate 24x7, including all national holidays and weekends. A UPI transaction on 26 January is normal and expected. Flagging it would produce false positives that undermine the signal quality of the check. The holiday-date check applies only to NEFT, RTGS, and cheque — the three rails that use RBI's batch settlement infrastructure.",
          "article": "Impossible-Date Transactions: Why Bank Holiday Checks Matter in Statement Forensics",
          "url": "https://www.terra-insight.com/insights/impossible-date-transactions-bank-statements"
        },
        {
          "q": "How can you tell if a bank statement PDF has been tampered with?",
          "a": "Four signals are detectable automatically: a creator or producer field showing a consumer PDF editor (iLovePDF, Foxit, LibreOffice) instead of banking software (Finacle, T24, iText); a modification timestamp later than the creation date indicating post-creation editing; font inconsistencies across pages pointing to inserted text blocks; and a balance chain break where the recomputed running balance does not match the printed figure on one or more rows. Each signal is individually flagged and listed in the document's authenticity record — the combination indicates what warrants closer review. The final decision on the application stays with the credit officer.",
          "article": "PDF Tampering Detection for Bank Statements: How Indian Lenders Verify Document Authenticity",
          "url": "https://www.terra-insight.com/insights/pdf-tampering-detection-bank-statements-india"
        },
        {
          "q": "What metadata fields are checked during PDF tampering detection?",
          "a": "The five core metadata fields are: Creator (the authoring application that produced the original document), Producer (the PDF conversion software), CreationDate (when the PDF was first generated), ModDate (the last modification timestamp), and PDF version. Authentic bank-generated PDFs carry consistent internal signatures — Oracle Finacle and Infosys Finacle, Temenos T24, Intellect, iText, Crystal Reports, JasperReports, Oracle BI Publisher, Adobe Acrobat Distiller, and Adobe LiveCycle are the typical creator/producer pairs. A mismatch between the Creator/Producer pair and a known banking-software signature is the primary metadata red flag.",
          "article": "PDF Tampering Detection for Bank Statements: How Indian Lenders Verify Document Authenticity",
          "url": "https://www.terra-insight.com/insights/pdf-tampering-detection-bank-statements-india"
        },
        {
          "q": "Can a tampered bank statement PDF pass manual review?",
          "a": "Yes — reliably. Font differences of 0.5pt, metadata fields buried in document properties, and invisible layer structures are undetectable by human reviewers at normal origination volumes. Forensic audit firms that previously conducted manual reviews required 30 to 45 days per batch review and still missed row-level balance manipulations that automated balance chain verification catches in seconds. The problem is not reviewer skill — it is that the manipulation exists in parts of the document humans are not able to inspect during standard credit appraisal.",
          "article": "PDF Tampering Detection for Bank Statements: How Indian Lenders Verify Document Authenticity",
          "url": "https://www.terra-insight.com/insights/pdf-tampering-detection-bank-statements-india"
        },
        {
          "q": "What are the legal consequences of submitting a forged bank statement for a loan in India?",
          "a": "A borrower submitting a forged bank statement to obtain credit faces liability under BNS Section 318 (cheating — formerly IPC Section 420), which carries up to seven years imprisonment, and BNS Section 465 (forgery of a valuable security or document used as evidence), which also carries up to two years. If the fraud involves proceeds of crime, PMLA provisions apply. For lenders, RBI's Master Direction on Digital Lending requires document verification controls; when fraud is detected, FIU-IND Suspicious Transaction Report filing is mandatory under PMLA obligations.",
          "article": "PDF Tampering Detection for Bank Statements: How Indian Lenders Verify Document Authenticity",
          "url": "https://www.terra-insight.com/insights/pdf-tampering-detection-bank-statements-india"
        },
        {
          "q": "How does TransactIQ handle PDF tampering detection as part of bank statement analysis?",
          "a": "TransactIQ runs a forensic check layer during document ingestion — before credit signal extraction begins. PDF metadata is validated against a library of known banking-software signatures. Font inventory is checked for consistency across pages. Balance chain is recomputed row by row and compared to printed figures. Transactions are checked against 150+ RBI bank holidays from 2019 to 2026 to flag impossible-date entries for NEFT, RTGS, and cheque instruments. Each processed statement receives a document-level verdict (clean, flagged, or unknown) with specific findings attached, plus an audit trail of what was checked. A flagged document is routed for human review — TransactIQ produces the signal; the credit officer makes the final decision.",
          "article": "PDF Tampering Detection for Bank Statements: How Indian Lenders Verify Document Authenticity",
          "url": "https://www.terra-insight.com/insights/pdf-tampering-detection-bank-statements-india"
        },
        {
          "q": "What level of round-number concentration in a bank statement is considered suspicious?",
          "a": "There is no universal threshold, and the interpretation must account for the account type and transaction mix. As a general heuristic used in forensic review, a concentration above 40–50% of non-ATM transactions ending in three or more zeros is unusual enough to warrant closer examination. ATM withdrawals are excluded from this calculation because Indian ATMs dispense only in multiples of ₹100, ₹200, or ₹500 — making round-number ATM withdrawals structurally expected rather than suspicious.",
          "article": "Round-Number Clustering in Bank Statements: A Fraud Detection Heuristic",
          "url": "https://www.terra-insight.com/insights/round-number-clustering-fraud-detection"
        },
        {
          "q": "Why do fabricated bank statements tend to have more round-number amounts?",
          "a": "When a person manually constructs transaction amounts intended to look realistic, they tend to choose psychologically round figures — amounts ending in zeros — because those feel natural and are easy to construct. The discipline required to consistently generate amounts like ₹47,836 or ₹12,450 rather than ₹50,000 or ₹12,500 is cognitively demanding. This results in fabricated statements having a disproportionately high share of round amounts compared to genuine spending, where amounts are determined by actual purchases, bills, and transfers.",
          "article": "Round-Number Clustering in Bank Statements: A Fraud Detection Heuristic",
          "url": "https://www.terra-insight.com/insights/round-number-clustering-fraud-detection"
        },
        {
          "q": "Does round-number clustering apply to both credits and debits?",
          "a": "The check applies to all transaction amounts. Round-number clustering in credits only — for example, all income entries being exact round amounts while debits look organic — is a specific pattern that can indicate selectively fabricated income entries. Clustering in both credits and debits at high rates suggests wholesale fabrication. The distinction between credit-only and mixed clustering is surfaced in the output so reviewers can interpret the pattern appropriately.",
          "article": "Round-Number Clustering in Bank Statements: A Fraud Detection Heuristic",
          "url": "https://www.terra-insight.com/insights/round-number-clustering-fraud-detection"
        },
        {
          "q": "Do MSME accounts in India legitimately have high round-number concentrations?",
          "a": "Yes, and this is an important calibration consideration. Indian informal MSME businesses often receive and make payments in exact round figures — a subcontractor paid ₹25,000 in cash, a supplier invoice settled at ₹1,00,000. Accounts that primarily process cash-equivalent or informal business payments can legitimately show 30–40% round-number concentration. This is why round-number clustering is treated as a signal for human review rather than an automatic flag, and why it is interpreted alongside the account's industry context and other fraud signals.",
          "article": "Round-Number Clustering in Bank Statements: A Fraud Detection Heuristic",
          "url": "https://www.terra-insight.com/insights/round-number-clustering-fraud-detection"
        },
        {
          "q": "Can round-number clustering appear in salary accounts without indicating fraud?",
          "a": "Salary accounts legitimately receive a fixed round salary amount every month — for example, ₹45,000 on the 1st of each month. This produces a genuine round-number credit that should not be flagged. The concentration check is calibrated against the diversity of transactions in the account. A salary account with 12 round salary credits out of 200 total transactions has a round-number rate of 6%, which is not elevated. The signal triggers only when the proportion is high across a diverse transaction set.",
          "article": "Round-Number Clustering in Bank Statements: A Fraud Detection Heuristic",
          "url": "https://www.terra-insight.com/insights/round-number-clustering-fraud-detection"
        }
      ]
    },
    "bank-reconciliation": {
      "label": "Bank Reconciliation",
      "faqs": [
        {
          "q": "What GST rate applies to bank service charges in India?",
          "a": "All bank service charges in India attract GST at 18% under SAC code 997119 (banking and related financial services). This applies to NEFT charges, RTGS charges, account maintenance fees, cheque book charges, IMPS charges, DD charges, and locker charges. Basic savings account services are exempt, but all current account services and transaction fees are taxable at 18%.",
          "article": "Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching",
          "url": "https://www.terra-insight.com/insights/bank-charges-reconciliation-india"
        },
        {
          "q": "Can companies claim ITC on GST paid on bank charges?",
          "a": "Yes. GST paid on bank charges is eligible for ITC under Section 16 of the CGST Act, provided the company is registered under GST and the charges relate to business use. The bank issues a tax invoice (or consolidated statement with GSTIN) at the end of each month. The ITC can be claimed in the same month's GSTR-3B after it appears in GSTR-2B, typically within 30–45 days of the charge being levied.",
          "article": "Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching",
          "url": "https://www.terra-insight.com/insights/bank-charges-reconciliation-india"
        },
        {
          "q": "How do NEFT and RTGS charges appear in bank statement narrations?",
          "a": "NEFT charges typically appear as 'NEFT CHG' or 'NEFT TRN CHG' followed by the transaction batch date and count — for example, 'NEFT CHG 15MAR26 12TXN 236.00 GST 42.48'. RTGS charges appear as 'RTGS CHG' with the individual transaction reference. The combined debit (charge plus 18% GST) is auto-debited without a prior debit note, making narration-based matching the only viable matching method.",
          "article": "Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching",
          "url": "https://www.terra-insight.com/insights/bank-charges-reconciliation-india"
        },
        {
          "q": "Why do bank charges generate disproportionate exceptions in reconciliation?",
          "a": "Bank charges create exceptions because they arrive without prior invoice or purchase order, are batched across multiple transaction types in a single auto-debit, carry a GST component that must be split from the base charge for ITC purposes, and vary month to month based on transaction volume. A company processing 500 NEFT transactions in March and 800 in April will receive different charge amounts — making fixed-amount matching fail and requiring narration-pattern matching instead.",
          "article": "Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching",
          "url": "https://www.terra-insight.com/insights/bank-charges-reconciliation-india"
        },
        {
          "q": "What is the recommended tolerance rule for matching bank charges in automated reconciliation?",
          "a": "The recommended tolerance for bank charge matching is ±₹5 for charges below ₹500 and ±1% for charges above ₹500. This accommodates rounding differences in GST calculation (banks calculate GST on the total monthly charge before rounding, not per transaction) and minor fee schedule revisions. Charges outside tolerance should be flagged as FEE_VARIANCE for manual review rather than auto-matched.",
          "article": "Bank Charges Reconciliation in India: Service Fees, GST on Charges, and Auto-Debit Matching",
          "url": "https://www.terra-insight.com/insights/bank-charges-reconciliation-india"
        },
        {
          "q": "What is the UTR format in Indian bank statement narrations?",
          "a": "A UTR (Unique Transaction Reference) is 22 characters long for NEFT, RTGS, and IMPS. It follows the format: 4-character bank code + 2-digit year + 3-digit day of year + 7-digit sequence number. For example, HDFC260801234567 in a NEFT narration uniquely identifies the transaction for matching.",
          "article": "Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them",
          "url": "https://www.terra-insight.com/insights/bank-statement-narration-patterns-india"
        },
        {
          "q": "Why do NEFT narrations from HDFC and ICICI differ in format?",
          "a": "The Reserve Bank of India mandates the UTR structure but does not standardise the full narration text. Each bank appends counterparty name, reference, and additional fields in its own format. HDFC uses 'NEFT CR:[UTR]/[name]/[ref]' while ICICI typically uses 'NEFT-[UTR]-[name]-[ref]', requiring separate parser configurations for each bank.",
          "article": "Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them",
          "url": "https://www.terra-insight.com/insights/bank-statement-narration-patterns-india"
        },
        {
          "q": "How does a reconciliation system handle NACH batch credits where one bank line covers 500 mandates?",
          "a": "A single NACH credit line in the bank statement represents the total of all successful mandates in that batch — often 200 to 500 individual transactions. Reconciliation systems must explode the batch: they retrieve the NACH batch file from NPCI or the sponsor bank, match each mandate reference to the sub-ledger, and flag the net difference as unreconciled. Batch explosion requires the mandate ID, amount, and settlement date for each record.",
          "article": "Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them",
          "url": "https://www.terra-insight.com/insights/bank-statement-narration-patterns-india"
        },
        {
          "q": "What happens when a bank narration is truncated and the UTR is cut off?",
          "a": "Many Indian bank CSV exports limit the narration field to 50 or 100 characters. A NEFT narration carrying a 22-character UTR plus counterparty name may be cut mid-string, losing the last digits of the UTR. In this case, reconciliation systems fall back to amount-plus-date matching, which generates false positives when two transactions of the same value arrive on the same day. MT940 format avoids truncation by using a dedicated :86: field.",
          "article": "Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them",
          "url": "https://www.terra-insight.com/insights/bank-statement-narration-patterns-india"
        },
        {
          "q": "Which Indian payment instruments do not carry a unique transaction reference in narrations?",
          "a": "Cash deposits and over-the-counter deposits rarely carry a system-generated reference in bank narrations — they typically show only branch code and teller ID. Some older NEFT inward credits from cooperative banks may omit the UTR. Cheque credits show the cheque number but not a unique digital reference. These instruments require manual or rule-based matching rather than reference-key lookup.",
          "article": "Bank Statement Narration Patterns in India: How Reconciliation Systems Parse Them",
          "url": "https://www.terra-insight.com/insights/bank-statement-narration-patterns-india"
        },
        {
          "q": "Which companies are covered under CARO 2020 bank reconciliation reporting?",
          "a": "CARO 2020 applies to all companies except banking companies, insurance companies, Section 8 companies, one-person companies, and small companies as defined under Section 2(85) of the Companies Act, 2013. Clause 3(ii)(b) specifically applies where the aggregate working capital limit from banks or financial institutions exceeds ₹5 crore at any point during the year. Listed companies, NBFCs above threshold, and manufacturing companies with working capital facilities are the most commonly affected.",
          "article": "CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies",
          "url": "https://www.terra-insight.com/insights/caro-2020-bank-reconciliation-audit-india"
        },
        {
          "q": "What happens if the quarterly BRS does not match the bank statement?",
          "a": "Auditors must disclose the nature and amount of discrepancies in their report under Clause 3(ii)(b). Persistent unexplained items older than 90 days typically trigger a material weakness observation under Section 143(3)(i). If the discrepancy is large relative to working capital, the auditor may issue a qualified opinion. Companies must then disclose the qualification in their annual return filed with the MCA.",
          "article": "CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies",
          "url": "https://www.terra-insight.com/insights/caro-2020-bank-reconciliation-audit-india"
        },
        {
          "q": "What is the Digital Bank Confirmation Portal and how does it affect bank reconciliation?",
          "a": "The DBCP was launched in July 2025 by the Indian Banks' Association in collaboration with ICAI. It provides digitally signed bank balance confirmations directly to auditors, eliminating manual balance confirmation letters. Currently, Canara Bank, Punjab National Bank, Bank of Maharashtra, and UCO Bank are live on the portal. Auditors can request balance confirmations for specific dates, and the digitally signed response is admissible as audit evidence under SA 505.",
          "article": "CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies",
          "url": "https://www.terra-insight.com/insights/caro-2020-bank-reconciliation-audit-india"
        },
        {
          "q": "How does GST enforcement use bank data to detect turnover mismatches?",
          "a": "GST authorities cross-reference declared turnover in GSTR-1 against total bank inflows received through data-sharing arrangements with banks. Unreconciled credits sitting in suspense accounts or unexplained bank deposits that exceed declared sales create a presumption of suppressed turnover. This triggers a demand notice under Section 73 or Section 74 of the CGST Act, with interest at 18% per annum and penalties ranging from 10% to 100% of the tax amount depending on whether fraud is established.",
          "article": "CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies",
          "url": "https://www.terra-insight.com/insights/caro-2020-bank-reconciliation-audit-india"
        },
        {
          "q": "How long does manual bank reconciliation take for companies under CARO 2020?",
          "a": "For a company with 3 to 5 bank accounts processing 500 to 2,000 transactions per month, manual reconciliation typically requires 3 to 7 staff days per month. Companies with payment gateway settlements and NACH collections face higher volumes and typically spend 10 to 15 staff days per month. The manual error rate ranges from 15% to 25%, primarily from narration mismatches and date-proximity errors across UPI, NEFT, and RTGS entries.",
          "article": "CARO 2020 and Bank Reconciliation: Audit Requirements for Indian Companies",
          "url": "https://www.terra-insight.com/insights/caro-2020-bank-reconciliation-audit-india"
        },
        {
          "q": "What narration format does HDFC Bank use for NEFT credits?",
          "a": "HDFC Bank NEFT inward credits follow the format 'NEFT CR:[UTR]/[counterparty name]/[reference]' in the narration field. The UTR is 22 characters: 4-digit bank code + 2-digit year + 3-digit day of year + 7-digit sequence (for example, HDFC2268012345678). Forward slashes delimit the fields. In MT940 :86: tag, this narration is prefixed with /INF/.",
          "article": "HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns",
          "url": "https://www.terra-insight.com/insights/hdfc-bank-reconciliation-india"
        },
        {
          "q": "Does HDFC Bank support MT940 statement export for all current account holders?",
          "a": "No. MT940 is available only for HDFC current account holders enrolled in the CMS (Cash Management Services) platform. Standard current accounts and savings accounts receive CSV or PDF downloads via NetBanking only. CMS enrollment generally requires a monthly average balance above ₹5 lakh and a formal onboarding with the HDFC relationship manager.",
          "article": "HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns",
          "url": "https://www.terra-insight.com/insights/hdfc-bank-reconciliation-india"
        },
        {
          "q": "How does HDFC CMS differ from NetBanking for reconciliation purposes?",
          "a": "HDFC NetBanking provides a CSV download with narration as free text — fields are not standardised and narration may be truncated at 100 characters. HDFC CMS delivers MT940 via SFTP or a REST API endpoint at configurable intervals (end-of-day or intraday MT942). CMS also provides structured collection reports for NACH mandates, RTGS high-value credits, and bulk NEFT batches — data that NetBanking does not expose in machine-readable form.",
          "article": "HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns",
          "url": "https://www.terra-insight.com/insights/hdfc-bank-reconciliation-india"
        },
        {
          "q": "How are HDFC Bank service charges (GST included) matched in reconciliation?",
          "a": "HDFC Bank debits service charges as auto-debit entries. The narration follows the format 'HDFC CHRG [service type] [period]' — for example, 'HDFC CHRG NEFT FEB2026'. GST at 18% on service fees is added in the same debit or as a separate line. Reconciliation systems map these entries to the 'bank charges' GL code and match the GST component against HDFC's monthly tax invoice. Section 194A TDS at 10% applies to HDFC interest credits above ₹40,000 per year and appears as a separate debit in the statement.",
          "article": "HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns",
          "url": "https://www.terra-insight.com/insights/hdfc-bank-reconciliation-india"
        },
        {
          "q": "What is the HDFC /INF/ prefix in the MT940 :86: field?",
          "a": "The /INF/ prefix is HDFC Bank's internal marker indicating that structured narration information follows. It appears at the start of the :86: tag content — for example, ':86:/INF/NEFT CR:HDFC2268012345678 ABC CORP INV-2024-001'. Reconciliation parsers configured for HDFC must strip the /INF/ prefix before extracting the UTR and counterparty. Systems not configured for this prefix will fail to extract any match key from HDFC MT940 files.",
          "article": "HDFC Bank Reconciliation: Statement Formats, CMS API, and Narration Patterns",
          "url": "https://www.terra-insight.com/insights/hdfc-bank-reconciliation-india"
        },
        {
          "q": "What format does ICICI Bank use for NEFT and RTGS narrations in statements?",
          "a": "ICICI Bank NEFT inward credits appear as 'NEFT-[UTR]-[counterparty name]-[reference]' in the narration field, using hyphens as delimiters — different from HDFC's forward-slash format. RTGS credits follow 'RTGS CR:[UTR] [counterparty] [reference]'. The UTR is 22 characters starting with ICIC for ICICI-originated transfers or the originating bank's 4-character code for inward credits.",
          "article": "ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching",
          "url": "https://www.terra-insight.com/insights/icici-bank-reconciliation-india"
        },
        {
          "q": "How does the ICICI MT940 :86: field differ from HDFC's MT940 format?",
          "a": "ICICI uses /TXT/ as the prefix in the :86: narration field, while HDFC uses /INF/. A typical ICICI MT940 :86: line reads ':86:/TXT/NEFT-ICIC2268012345678-ABC CORP-INV-2026-001'. Reconciliation parsers must be configured with the correct prefix per bank. Using the HDFC /INF/ parser on ICICI files — a common misconfiguration — results in null extraction of all match keys and 100% manual fallback.",
          "article": "ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching",
          "url": "https://www.terra-insight.com/insights/icici-bank-reconciliation-india"
        },
        {
          "q": "Does ICICI Bank's iCollect product affect how reconciliation is configured?",
          "a": "Yes. ICICI iCollect is a collections management service where each payer is assigned a unique virtual account number. Inward payments to a virtual account appear in the main current account statement with the virtual account number in the narration — for example, 'NEFT-[UTR]-ICICI iCollect-[VA number]-[payer name]'. Reconciliation systems must extract the virtual account number as the primary match key, not the UTR or payer name, to correctly attribute the payment to the right invoice or mandate.",
          "article": "ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching",
          "url": "https://www.terra-insight.com/insights/icici-bank-reconciliation-india"
        },
        {
          "q": "How are ICICI Bank service charges and GST on charges handled in reconciliation?",
          "a": "ICICI auto-debits service fees with narrations in the format 'ICICI BANK CHARGES [service description] [month]'. GST at 18% on banking service fees is included in the same debit entry or posted as a separate line depending on the account type. ICICI issues a monthly GST invoice. Finance teams must match the charge debit to the ICICI invoice and claim the 18% GST as input tax credit. Section 194A TDS at 10% applies to ICICI fixed deposit interest above ₹40,000 per financial year.",
          "article": "ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching",
          "url": "https://www.terra-insight.com/insights/icici-bank-reconciliation-india"
        },
        {
          "q": "What is the recommended export method for ICICI Bank statement reconciliation at enterprise scale?",
          "a": "For enterprise accounts on ICICI CIB, MT940 via SFTP is the recommended method — it delivers structured, field-tagged data daily (end-of-day) or intraday (configurable). For accounts not on CIB, CIB portal CSV export is the next best option. PDF statement via InstaAlert or NetBanking should be avoided for reconciliation at scale — it requires OCR and produces 3 to 5 times more manual intervention per 1,000 transactions compared to MT940.",
          "article": "ICICI Bank Reconciliation: CIB Statement Format and Enterprise Account Matching",
          "url": "https://www.terra-insight.com/insights/icici-bank-reconciliation-india"
        },
        {
          "q": "Which Indian banks support MT940 bank statement export?",
          "a": "As of 2026, MT940 export is supported by HDFC Bank (via CMS), ICICI Bank (via CIB), Axis Bank (via CMS), Kotak Mahindra Bank (via Kotak CMS), and SBI (for select current account products under the Corporate Banking platform). MT940 is generally available only for current accounts with a CMS or corporate banking relationship — savings accounts and basic current accounts are not eligible.",
          "article": "MT940 Bank Statement Format in India: How It Enables Automated Reconciliation",
          "url": "https://www.terra-insight.com/insights/mt940-bank-statement-reconciliation-india"
        },
        {
          "q": "What is the :86: tag in MT940 and why does it matter for reconciliation?",
          "a": "The :86: tag is the information-to-account owner field in MT940. It contains the narration text for each transaction — including the UTR, counterparty name, and payment reference. HDFC uses a /INF/ prefix inside :86:, while ICICI uses /TXT/. This prefix tells the parser where the structured narration begins. Without correct :86: parsing, a reconciliation system extracts no match keys and every transaction falls to manual review.",
          "article": "MT940 Bank Statement Format in India: How It Enables Automated Reconciliation",
          "url": "https://www.terra-insight.com/insights/mt940-bank-statement-reconciliation-india"
        },
        {
          "q": "How is MT940 different from CSV or PDF bank statement formats for reconciliation?",
          "a": "CSV exports from NetBanking are unstructured — narration, amount, date, and balance appear as free-text columns with no guaranteed field positions. PDFs require OCR. MT940 uses fixed SWIFT tags: :60F: for opening balance, :61: for each transaction line (date, amount, reference), and :86: for narration. A reconciliation system can reliably extract UTR, value date, and credit/debit indicator from :61: without any text parsing — reducing mismatch errors by 30 to 50 percent compared to CSV import.",
          "article": "MT940 Bank Statement Format in India: How It Enables Automated Reconciliation",
          "url": "https://www.terra-insight.com/insights/mt940-bank-statement-reconciliation-india"
        },
        {
          "q": "Does SBI support MT940 for all current account holders?",
          "a": "No. SBI MT940 is available selectively under the Corporate Banking and Large Corporate segments. Standard current account holders using SBI OnlineSBI or YONO Business receive CSV or PDF downloads only. Enterprises requiring MT940 from SBI must apply through their relationship manager and may need to maintain a minimum average balance of ₹10 lakh or more in the corporate tier.",
          "article": "MT940 Bank Statement Format in India: How It Enables Automated Reconciliation",
          "url": "https://www.terra-insight.com/insights/mt940-bank-statement-reconciliation-india"
        },
        {
          "q": "What is the typical time lag between a transaction and its appearance in an MT940 file?",
          "a": "MT940 files are typically generated once per business day — usually by 8:00–9:00 AM IST covering transactions up to the prior day's bank cut-off. For HDFC and ICICI CMS clients, intraday MT940 (MT942) is available at configurable intervals of 2 to 4 hours. RTGS and NEFT credits posted after the bank's day-end cut-off (generally 6:00 PM IST) appear in the next business day's MT940 file.",
          "article": "MT940 Bank Statement Format in India: How It Enables Automated Reconciliation",
          "url": "https://www.terra-insight.com/insights/mt940-bank-statement-reconciliation-india"
        },
        {
          "q": "What is the most common cause of opening balance mismatches in Indian bank reconciliation?",
          "a": "The most common cause is a NACH or ECS credit received on the last working day of the month that the bank posts on that date but the company's ERP records in the following period — a 1-day timing difference that creates an opening balance variance of exactly the credit amount. For companies processing 200 or more NACH mandates monthly, this timing mismatch can affect 5–12 transactions in any given month-end cycle.",
          "article": "Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies",
          "url": "https://www.terra-insight.com/insights/opening-balance-reconciliation-india"
        },
        {
          "q": "How should a TDS receivable that was posted in the wrong period be corrected in the opening balance?",
          "a": "The correction requires a journal entry reversing the prior-period TDS receivable debit and re-posting it in the correct period. The TDS certificate (Form 16A or 16B) carries the quarter and financial year of deduction, which determines the correct period. If the TDS deduction was under Section 194C or 194J and was booked in Q3 but the certificate covers Q2, the correction must be made before filing the ITR for that financial year to avoid mismatch in Form 26AS.",
          "article": "Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies",
          "url": "https://www.terra-insight.com/insights/opening-balance-reconciliation-india"
        },
        {
          "q": "How long does opening balance reconciliation typically take for a company with 5 bank accounts?",
          "a": "For a company with 5 bank accounts running monthly reconciliation, opening balance verification should take 30–60 minutes if the prior period was clean and signed off. If prior-period items were left unresolved, the investigation extends to 2–4 hours per account. Companies that automate opening balance carry-forward and flag unresolved prior-period items reduce this to under 15 minutes per account in 90% of months.",
          "article": "Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies",
          "url": "https://www.terra-insight.com/insights/opening-balance-reconciliation-india"
        },
        {
          "q": "Can an opening balance mismatch in GSTR-2B affect the bank opening balance reconciliation?",
          "a": "A GSTR-2B mismatch does not directly affect the bank opening balance, but it can affect the ITC ledger opening balance. If a GST credit note was received from a supplier in March but not reflected in GSTR-2B until April, and the company booked the ITC in March, the ITC ledger opening balance for April will show a higher credit than what GSTR-2B supports — creating a GST reconciliation exception that must be resolved separately from the bank reconciliation.",
          "article": "Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies",
          "url": "https://www.terra-insight.com/insights/opening-balance-reconciliation-india"
        },
        {
          "q": "What is the correct journal entry to correct an opening balance variance discovered in the current period?",
          "a": "The standard approach is a prior-period adjustment entry: debit or credit the relevant account (bank, TDS receivable, GST ITC) with a corresponding credit or debit to a Prior Period Adjustments account (under Other Income or Other Expenses per Schedule III of the Companies Act 2013). If the amount is material (typically above ₹5 lakh for mid-size companies or as defined in the accounting policy), it must be disclosed separately in the notes to financial statements.",
          "article": "Opening Balance Reconciliation in India: Resolving Month-Start Discrepancies",
          "url": "https://www.terra-insight.com/insights/opening-balance-reconciliation-india"
        },
        {
          "q": "How does a bulk salary NEFT appear in bank statement narrations?",
          "a": "A bulk salary NEFT batch appears as a single debit line with a narration such as 'NEFT DR BULK SALARY MAR26 412 EMP' or 'BULK SAL NEFT 412EMPS REF2600312'. The total debit equals the sum of all net salary credits to individual employee accounts. The bank's bulk payment acknowledgement file (CSV or PDF) carries the individual employee-level UTR references — which are the match keys against the payroll register's employee-wise net pay column.",
          "article": "Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment",
          "url": "https://www.terra-insight.com/insights/salary-payroll-bank-reconciliation-india"
        },
        {
          "q": "What TDS section applies to salary payments, and when must TDS be deposited?",
          "a": "Salary TDS falls under Section 192 of the Income Tax Act. It is deducted at source based on the estimated annual income of each employee and the applicable slab rate. The deducted TDS must be deposited via Challan ITNS 281 by the 7th of the following month — except for the month of March, where the deadline is 30 April. The CIN (BSR code + date + serial number) from the challan is the match key against TRACES records.",
          "article": "Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment",
          "url": "https://www.terra-insight.com/insights/salary-payroll-bank-reconciliation-india"
        },
        {
          "q": "How should the PF contribution bank debit be matched to the payroll register in reconciliation?",
          "a": "PF contribution debits should be matched using the TRRN (Transaction Reference Number from EPFO's ECR portal) as the primary match key. The debit appears as 'PF CONTRIBUTION MMYY TRRN XXXXXXXXXX' and covers both the employee share (12% of basic) and the employer share (3.67% EPF + 8.33% EPS + 0.5% EDLI + 0.5% admin). The total PF debit should equal the sum of the employer and employee PF amounts from the payroll register for all employees earning above ₹15,000 basic.",
          "article": "Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment",
          "url": "https://www.terra-insight.com/insights/salary-payroll-bank-reconciliation-india"
        },
        {
          "q": "What causes salary payroll bank reconciliation to fail mid-month?",
          "a": "The most common mid-month failure is an off-cycle salary run — arrear payments, salary revisions, or joining bonuses paid outside the regular payroll date — that creates an additional bank debit not captured in the main payroll register. A revision in July for April through June arrears generates a debit that the reconciliation engine cannot match to the standard payroll file. Off-cycle payments must be tagged in both the payroll system and the bank transfer narration with a distinct reference code.",
          "article": "Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment",
          "url": "https://www.terra-insight.com/insights/salary-payroll-bank-reconciliation-india"
        },
        {
          "q": "How is ESI contribution reconciled separately from the salary bank debit?",
          "a": "ESI contributions are debited separately from the salary NEFT — typically 3–7 days before or after the salary date — as 'ESI CONTRIBUTION MMYY REGNO XXXXXXXXXX'. The total debit covers the employer share (3.25%) and employee share (0.75%) for all employees earning ₹21,000 per month or below. The match key against the ESIC portal (esic.gov.in) is the ESI employer registration number and the challan reference. ESI challan deadline is the 15th of the following month.",
          "article": "Salary and Payroll Bank Reconciliation in India: Bulk Transfer Matching and TDS Alignment",
          "url": "https://www.terra-insight.com/insights/salary-payroll-bank-reconciliation-india"
        },
        {
          "q": "What statement format does SBI support for automated bank reconciliation?",
          "a": "SBI YONO Business supports CSV download for most current accounts. Select CMP (Cash Management Product) and corporate CMS accounts additionally support MT940 format, which is required for direct integration with SAP and Oracle Financials. Standard CSV from YONO Business is the default for accounts without CMP enrollment.",
          "article": "SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing",
          "url": "https://www.terra-insight.com/insights/sbi-bank-reconciliation-india"
        },
        {
          "q": "How do PFMS government payment credits appear in SBI bank statement narrations?",
          "a": "PFMS credits appear with the narration prefix 'PFMS' followed by the scheme code and beneficiary reference — for example, 'PFMS/MNREGS/2024-25/REF12345678'. The UTR number occupies characters 1–22 and is the primary match key. Finance teams must parse PFMS narrations separately from standard NEFT credits because the structure differs.",
          "article": "SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing",
          "url": "https://www.terra-insight.com/insights/sbi-bank-reconciliation-india"
        },
        {
          "q": "Does SBI YONO Business support MT940 export for enterprise accounts?",
          "a": "MT940 export is available only for accounts enrolled in SBI's CMP (Cash Management Product) or select CMS (Cash Management Services) arrangements, typically accounts with a monthly transaction volume above ₹5 crore. Standard current accounts on YONO Business receive CSV statements only. MT940 enablement requires a separate application to SBI's corporate banking team.",
          "article": "SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing",
          "url": "https://www.terra-insight.com/insights/sbi-bank-reconciliation-india"
        },
        {
          "q": "How do GST refund credits from GSTN appear in SBI bank statements?",
          "a": "GST refund credits appear with the narration 'GSTN REFUND' followed by the GSTIN, refund application reference number (ARN), and the tax period — for example, 'GSTN REFUND 29ABCDE1234F1Z5/ARN-AB-2024-1234567/032024'. The credit typically arrives 7–10 working days after GSTN processes the refund order and is routed via SBI's government payments gateway.",
          "article": "SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing",
          "url": "https://www.terra-insight.com/insights/sbi-bank-reconciliation-india"
        },
        {
          "q": "What is the recommended reconciliation approach for companies using SBI as their primary bank alongside HDFC or ICICI?",
          "a": "Companies running SBI alongside HDFC or ICICI should configure separate statement parsers for each bank because narration formats, UTR placement, and date formats differ significantly. SBI narrations are longer (up to 50 characters) and UTR position varies by payment type, whereas HDFC and ICICI follow a more consistent 22-character UTR prefix structure. A multi-pass matching engine that normalises narration formats across banks before attempting UTR extraction reduces the exception rate from approximately 18% to below 4%.",
          "article": "SBI Bank Reconciliation: Government Account Formats, YONO Business, and Statement Parsing",
          "url": "https://www.terra-insight.com/insights/sbi-bank-reconciliation-india"
        }
      ]
    },
    "reconciliation-fundamentals": {
      "label": "Reconciliation Fundamentals",
      "faqs": [
        {
          "q": "What is a Bank Reconciliation Statement (BRS)?",
          "a": "A Bank Reconciliation Statement is a document that explains the difference between the cash book balance (the bank balance per the company's own records) and the bank statement balance (the balance per the bank's records) as at a specific date. The difference arises from timing items — cheques issued but not yet presented to the bank, deposits recorded in the books but not yet credited by the bank, and bank charges not yet recorded in the books. The BRS is a standard internal control document required for statutory audit.",
          "article": "Bank Reconciliation Statement (BRS): Format and Preparation for Indian Companies",
          "url": "https://www.terra-insight.com/insights/bank-reconciliation-statement-brs-india"
        },
        {
          "q": "What is the standard format for a BRS in India?",
          "a": "The standard BRS format starts with either the cash book balance or the bank statement balance, then adds or deducts timing items to arrive at the other. Starting from cash book balance: add unpresented cheques (issued but not cleared), deduct deposits in transit (added to books but not yet credited by bank), add/deduct bank errors, deduct direct bank charges not recorded in books = Bank statement balance. The BRS is dated as at the period-end date and signed by the preparer and a reviewer.",
          "article": "Bank Reconciliation Statement (BRS): Format and Preparation for Indian Companies",
          "url": "https://www.terra-insight.com/insights/bank-reconciliation-statement-brs-india"
        },
        {
          "q": "What are the most common items in a BRS for Indian companies?",
          "a": "The most common BRS items for Indian companies are: (1) NEFT/RTGS payments that clear the next business day — timing difference between initiation and bank debit; (2) cheques issued to vendors that have not been presented — outstanding cheques; (3) bank charges and service fees debited by the bank but not yet recorded in the books; (4) direct credits from debtors (NEFT) that appear in the bank statement before the AR team has booked the receipt; (5) TDS deducted at source appearing as bank debits that the tax team needs to record.",
          "article": "Bank Reconciliation Statement (BRS): Format and Preparation for Indian Companies",
          "url": "https://www.terra-insight.com/insights/bank-reconciliation-statement-brs-india"
        },
        {
          "q": "How often should a BRS be prepared for statutory audit?",
          "a": "Statutory auditors expect a BRS as at the last day of the financial year (March 31) for all bank accounts. For mid-year review, a BRS as at each quarter end (June 30, September 30, December 31) is typically requested. For companies with high transaction volumes, monthly BRS preparation is standard practice — it prevents the accumulation of unidentified items that become difficult to explain at year-end.",
          "article": "Bank Reconciliation Statement (BRS): Format and Preparation for Indian Companies",
          "url": "https://www.terra-insight.com/insights/bank-reconciliation-statement-brs-india"
        },
        {
          "q": "What is the maximum acceptable time to clear outstanding items in a BRS?",
          "a": "Outstanding cheques should clear within 3 months of issuance (cheques in India are valid for 3 months). If a cheque has been outstanding for more than 3 months, it has expired and the payable should be reversed. Deposits in transit should clear within 1–3 business days for NEFT/RTGS. Items that remain in the BRS for more than 30 days without explanation are typically flagged as audit observations.",
          "article": "Bank Reconciliation Statement (BRS): Format and Preparation for Indian Companies",
          "url": "https://www.terra-insight.com/insights/bank-reconciliation-statement-brs-india"
        },
        {
          "q": "What is cash flow reconciliation?",
          "a": "Cash flow reconciliation is the process of confirming that the net change in cash and cash equivalents shown in the cash flow statement equals the difference between opening and closing bank balances in the books. If the bank reconciliation is complete and the AR/AP ledgers are reconciled, the cash flow statement should balance. Differences indicate either an unreconciled bank item, an unreconciled non-cash adjustment (depreciation, provisions), or a classification error between operating, investing, and financing activities.",
          "article": "Cash Flow Reconciliation: Matching P&L to Actual Bank Movements",
          "url": "https://www.terra-insight.com/insights/cash-flow-reconciliation-india"
        },
        {
          "q": "What is the difference between direct and indirect method cash flow in India?",
          "a": "The direct method shows actual cash receipts (from customers) and cash payments (to suppliers, employees, taxes) in the operating section. The indirect method starts with net profit and adjusts for non-cash items (depreciation, provisions) and working capital changes (AR increase, AP increase, inventory change). Ind AS 7 permits both; most Indian companies use the indirect method because it is easier to prepare from standard accounting outputs. The direct method requires a full breakdown of actual bank receipts and payments.",
          "article": "Cash Flow Reconciliation: Matching P&L to Actual Bank Movements",
          "url": "https://www.terra-insight.com/insights/cash-flow-reconciliation-india"
        },
        {
          "q": "Why does a cash flow statement not balance in practice?",
          "a": "The most common reasons a cash flow statement does not balance: (1) bank reconciliation is incomplete — unresolved bank entries that are not in the books cause the bank balance to differ from the book cash balance; (2) TDS receivable is shown as cash receipt rather than advance tax; (3) intercompany flows are not eliminated in group entities; (4) a capital expenditure is misclassified as an operating expense, distorting operating vs investing cash flow.",
          "article": "Cash Flow Reconciliation: Matching P&L to Actual Bank Movements",
          "url": "https://www.terra-insight.com/insights/cash-flow-reconciliation-india"
        },
        {
          "q": "How does TDS affect the cash flow statement?",
          "a": "TDS deducted on receivables reduces the cash received from customers — but the gross amount of the invoice is the revenue. In the indirect method cash flow, the TDS receivable appears as an increase in current assets (working capital outflow), reducing operating cash flow from the net profit figure. In the direct method, only the net cash received (after TDS) appears as operating inflow. Reconciling TDS receivable movements to the cash flow is an often-missed step in year-end cash flow preparation.",
          "article": "Cash Flow Reconciliation: Matching P&L to Actual Bank Movements",
          "url": "https://www.terra-insight.com/insights/cash-flow-reconciliation-india"
        },
        {
          "q": "What do PE investors and boards look for in cash flow reconciliation?",
          "a": "PE investors and boards focus on free cash flow quality: whether operating cash flow is genuinely from operations, or includes proceeds from asset sales, customer advances, or delayed supplier payments (AP stretching). Reconciling cash flow requires showing: operating cash flow excluding non-recurring items, capex reconciled to the fixed asset addition schedule, and working capital movement reconciled to AR, AP, and inventory ledgers. Unreconciled items in any of these reduce the credibility of the reported cash position.",
          "article": "Cash Flow Reconciliation: Matching P&L to Actual Bank Movements",
          "url": "https://www.terra-insight.com/insights/cash-flow-reconciliation-india"
        },
        {
          "q": "How does UPI settlement work for merchants in India?",
          "a": "For most UPI merchants, payments collected during a day are settled to the merchant's bank account on the next business day (T+1). The settlement is typically a single bulk credit on the bank statement — for example, a ₹48,750 credit representing 23 individual UPI payments. The reconciliation task is to disaggregate this bulk credit into individual transactions using the settlement report from the payment aggregator (Razorpay, PayU, Cashfree, PhonePe Business, etc.).",
          "article": "Cash-to-Bank Reconciliation for UPI and POS Transactions in India",
          "url": "https://www.terra-insight.com/insights/cash-to-bank-reconciliation-upi-pos-india"
        },
        {
          "q": "What is MDR on POS transactions and how is it reconciled?",
          "a": "Merchant Discount Rate (MDR) is the fee charged by the acquiring bank for POS (point-of-sale) card processing. For credit cards, MDR ranges from 1.5–2.5% of the transaction value. For debit cards and RuPay, MDR is zero per government mandate. The POS settlement file from the acquirer shows the gross transaction value and the MDR deducted — the net credit to the bank is gross minus MDR. Reconciliation must account for the MDR deduction, not just match the gross invoice amount.",
          "article": "Cash-to-Bank Reconciliation for UPI and POS Transactions in India",
          "url": "https://www.terra-insight.com/insights/cash-to-bank-reconciliation-upi-pos-india"
        },
        {
          "q": "Why does UPI reconciliation fail when done manually?",
          "a": "Manual UPI reconciliation fails at scale because: (1) the bank statement shows only the settlement total, not individual transaction details; (2) the settlement report from the payment aggregator uses internal transaction IDs, not the UTR visible to customers; (3) chargebacks and refunds may reduce the settlement amount without a separate bank debit; and (4) multiple payment aggregators' settlements may arrive on the same day as separate bank credits. Matching requires the aggregator's settlement file as an intermediate source.",
          "article": "Cash-to-Bank Reconciliation for UPI and POS Transactions in India",
          "url": "https://www.terra-insight.com/insights/cash-to-bank-reconciliation-upi-pos-india"
        },
        {
          "q": "How is TCS on UPI transactions reconciled?",
          "a": "Tax Collected at Source (TCS) under Section 206C(1H) applies to e-commerce operators. For most standard UPI merchant payments, TCS does not apply directly. However, e-commerce marketplace sellers receive payments through the operator net of TCS (0.1%). The marketplace's settlement statement shows TCS deducted — this must be reconciled to Form 26AS (TCS section Part F) and recorded as a TCS receivable, similar to TDS receivable treatment.",
          "article": "Cash-to-Bank Reconciliation for UPI and POS Transactions in India",
          "url": "https://www.terra-insight.com/insights/cash-to-bank-reconciliation-upi-pos-india"
        },
        {
          "q": "How long does the POS settlement take to appear in the bank?",
          "a": "Standard POS settlement timelines in India: T+1 for most acquiring banks and payment processors. Some banks offer same-day settlement for premium merchant accounts. Weekend and holiday settlements may be delayed to the next business day. The reconciliation must account for these timing differences — a POS terminal's end-of-day settlement on Friday may only credit the bank account on Monday, creating a 3-day timing difference.",
          "article": "Cash-to-Bank Reconciliation for UPI and POS Transactions in India",
          "url": "https://www.terra-insight.com/insights/cash-to-bank-reconciliation-upi-pos-india"
        },
        {
          "q": "What is a chargeback in the context of payment gateway reconciliation?",
          "a": "A chargeback is a forced reversal of a card payment initiated by the card issuer on the cardholder's behalf — typically because the cardholder disputes the transaction. From a reconciliation perspective, a chargeback appears as a deduction from a future settlement statement: the gateway deducts the original transaction amount (and often a chargeback processing fee) from the next settlement. The finance team must match this deduction to the original transaction, reverse the revenue, and record any chargeback fee.",
          "article": "Chargeback Reconciliation for Payment Gateways: A Finance Team Guide",
          "url": "https://www.terra-insight.com/insights/chargeback-dispute-reconciliation-payment-gateway"
        },
        {
          "q": "How long after a transaction can a chargeback occur?",
          "a": "Card network rules (Visa, Mastercard) allow chargebacks up to 120 days (Visa) or 120 days (Mastercard) after the transaction date for most dispute types. In India, RBI regulations require banks to resolve disputes within 30 days (extendable). This means a transaction from 3–4 months ago may generate a chargeback in the current period — requiring the reconciliation to match a current deduction against a transaction from a prior accounting period.",
          "article": "Chargeback Reconciliation for Payment Gateways: A Finance Team Guide",
          "url": "https://www.terra-insight.com/insights/chargeback-dispute-reconciliation-payment-gateway"
        },
        {
          "q": "How should prior-period chargebacks be treated in P&L?",
          "a": "A chargeback for a transaction from a prior accounting period should be treated as a current-period P&L charge (chargeback expense or bad debt) rather than a prior-period revenue adjustment — unless the amount is material. For material chargebacks (above ₹1 lakh or 0.1% of revenue), the prior-period nature should be disclosed in the notes. The GST adjustment may also require a credit note in the current period, which should be matched to the original invoice's GST return.",
          "article": "Chargeback Reconciliation for Payment Gateways: A Finance Team Guide",
          "url": "https://www.terra-insight.com/insights/chargeback-dispute-reconciliation-payment-gateway"
        },
        {
          "q": "What is a chargeback ratio and how does it affect reconciliation?",
          "a": "A chargeback ratio is chargebacks divided by total transactions (by count) in a month. Card networks set thresholds: Visa's standard threshold is 0.9%; Mastercard's is 1.0%. If a merchant exceeds these thresholds, the gateway may impose higher MDR rates, withhold a rolling reserve, or terminate the merchant account. The rolling reserve (typically 5–10% of daily settlements held for 90–180 days) must be reconciled separately — it is a receivable from the gateway, not settled cash.",
          "article": "Chargeback Reconciliation for Payment Gateways: A Finance Team Guide",
          "url": "https://www.terra-insight.com/insights/chargeback-dispute-reconciliation-payment-gateway"
        },
        {
          "q": "How are chargeback fees reconciled?",
          "a": "Payment gateways and acquirers charge a fee per chargeback — typically ₹500–₹2,000 per dispute. This fee appears as a separate line item in the settlement statement, distinct from the chargeback reversal amount. Both must be reconciled: the reversal amount is matched to the original transaction and revenue reversed; the chargeback fee is posted to a fee expense account. Missing the fee creates a small but recurring expense understatement.",
          "article": "Chargeback Reconciliation for Payment Gateways: A Finance Team Guide",
          "url": "https://www.terra-insight.com/insights/chargeback-dispute-reconciliation-payment-gateway"
        },
        {
          "q": "Which industries in India require daily reconciliation?",
          "a": "Daily reconciliation is operationally required for: NBFCs with daily NACH collections (bounce rate must be updated in the LMS same day), payment aggregators (daily settlement from nodal account to merchant accounts under RBI guidelines), e-commerce platforms (daily settlement to sellers), and banks and MFIs (daily loan account reconciliation). It is also strongly recommended for any business with daily average transactions above ₹1 crore in settlement volume.",
          "article": "Daily vs Monthly Reconciliation: When Each Approach Makes Sense",
          "url": "https://www.terra-insight.com/insights/daily-vs-monthly-reconciliation-india"
        },
        {
          "q": "What is the technology requirement for daily reconciliation?",
          "a": "Daily reconciliation requires: (1) automated data ingestion — bank statements via API or SFTP, not manual download; (2) a matching engine that can process the day's transaction volume in under 60 minutes; (3) an exception routing workflow that notifies the correct reviewer within the same business day; and (4) a sign-off process that completes within the day. Manual daily reconciliation is operationally unsustainable above 200 daily transactions.",
          "article": "Daily vs Monthly Reconciliation: When Each Approach Makes Sense",
          "url": "https://www.terra-insight.com/insights/daily-vs-monthly-reconciliation-india"
        },
        {
          "q": "Can monthly reconciliation work for a company with GST turnover above ₹5 crore?",
          "a": "Monthly reconciliation is viable for a company with ₹5 crore GST turnover if: transaction volume is below 1,000 per month, there are fewer than 20 active TDS deductors, and there is no NACH, platform settlement, or marketplace activity. Above these thresholds, monthly reconciliation creates a backlog that is difficult to clear before the 20th (GSTR-3B deadline) — resulting in ITC being claimed before GSTR-2B matching is complete.",
          "article": "Daily vs Monthly Reconciliation: When Each Approach Makes Sense",
          "url": "https://www.terra-insight.com/insights/daily-vs-monthly-reconciliation-india"
        },
        {
          "q": "How do I move from monthly to daily reconciliation without disrupting operations?",
          "a": "Move in stages: (1) Week 1-2 — automate bank statement ingestion; reconcile daily bank vs cash book without changing other processes; (2) Week 3-4 — add daily platform settlement matching; (3) Month 2 — add daily exception routing with SLAs; (4) Month 3 — add daily TDS posting for incoming payments. The month-end close becomes a sign-off exercise rather than a matching exercise once all daily matching is in place.",
          "article": "Daily vs Monthly Reconciliation: When Each Approach Makes Sense",
          "url": "https://www.terra-insight.com/insights/daily-vs-monthly-reconciliation-india"
        },
        {
          "q": "What is the hybrid daily-monthly approach?",
          "a": "The hybrid approach applies daily reconciliation to high-volume, high-risk transaction types and monthly reconciliation to low-volume types. Typical hybrid: daily for bank and platform settlements (high volume, daily settlement lag), weekly for TDS receivable updates (Form 26AS updates 3-7 days after challan deposit), monthly for GSTR-2B matching (only available on 14th of each month). This approach balances operational efficiency with the risk profile of each reconciliation type.",
          "article": "Daily vs Monthly Reconciliation: When Each Approach Makes Sense",
          "url": "https://www.terra-insight.com/insights/daily-vs-monthly-reconciliation-india"
        },
        {
          "q": "What is the difference between debtors reconciliation and bank reconciliation?",
          "a": "Bank reconciliation matches your cash book against the bank statement — confirming actual cash receipts. Debtors reconciliation matches your accounts receivable ledger against the customer's accounts payable ledger — confirming that both sides agree on what is owed. A customer may have paid, but if their payment is recorded against the wrong invoice in your books, the bank reconciliation will pass but the debtors reconciliation will show a mismatch.",
          "article": "Debtors and Creditors Reconciliation: Ledger Matching Best Practices",
          "url": "https://www.terra-insight.com/insights/debtors-creditors-reconciliation-india"
        },
        {
          "q": "How often should accounts receivable reconciliation be done in India?",
          "a": "AR reconciliation with counterparties should be done at minimum quarterly for amounts above ₹5 lakh. For high-value customers (above ₹25 lakh outstanding), monthly confirmation is best practice. Statutory auditors expect confirmation of balances from debtors representing more than 5% of total AR — if these are not reconciled regularly, the audit process becomes more time-consuming.",
          "article": "Debtors and Creditors Reconciliation: Ledger Matching Best Practices",
          "url": "https://www.terra-insight.com/insights/debtors-creditors-reconciliation-india"
        },
        {
          "q": "What is age-wise analysis and why does it matter for India GST?",
          "a": "Age-wise analysis classifies AR by the number of days since the invoice date — typically in buckets: 0–30, 31–60, 61–90, 90–180, and 180+ days. Under GST rules, if a buyer does not pay within 180 days of the invoice date, the ITC claimed on that purchase must be reversed (Section 16(2)(b) of the CGST Act). Age-wise analysis identifies invoices approaching the 180-day threshold and triggers ITC reversal before the compliance deadline.",
          "article": "Debtors and Creditors Reconciliation: Ledger Matching Best Practices",
          "url": "https://www.terra-insight.com/insights/debtors-creditors-reconciliation-india"
        },
        {
          "q": "How do disputed invoices affect debtors reconciliation?",
          "a": "A disputed invoice creates a difference between your AR ledger and the customer's AP ledger — you show an outstanding receivable; they show nothing (or a reduced amount pending dispute resolution). Disputed invoices must be separately classified in the AR ledger — not aged with normal receivables — and the dispute terms documented. If the dispute results in a credit note, the credit note must be reconciled to both the original invoice and the GST credit note in GSTR-1.",
          "article": "Debtors and Creditors Reconciliation: Ledger Matching Best Practices",
          "url": "https://www.terra-insight.com/insights/debtors-creditors-reconciliation-india"
        },
        {
          "q": "What is a balance confirmation letter and when is it required?",
          "a": "A balance confirmation letter is a written statement from the counterparty confirming the outstanding balance in their books as of a specific date. Statutory auditors under SA 505 (External Confirmations) require confirmation letters from debtors representing significant AR balances — typically above ₹10 lakh per debtor, or the top 10 debtors by balance. Confirmation letters must be sent by the auditor directly (not by the management) to be effective as audit evidence.",
          "article": "Debtors and Creditors Reconciliation: Ledger Matching Best Practices",
          "url": "https://www.terra-insight.com/insights/debtors-creditors-reconciliation-india"
        },
        {
          "q": "What counts as a reconciliation exception?",
          "a": "A reconciliation exception is any transaction that did not match automatically after all matching passes were applied. This includes: amount mismatches (bank credit of ₹90,000 vs invoice of ₹1,00,000 where TDS was not accounted for), reference mismatches (NEFT credit with a narration that does not match any invoice reference), missing items (invoice in the ledger with no bank credit), and excess items (bank credit with no corresponding invoice). Each type requires different resolution logic.",
          "article": "Exception Management in Reconciliation: From Detection to Resolution",
          "url": "https://www.terra-insight.com/insights/exception-management-reconciliation-india"
        },
        {
          "q": "How should reconciliation exceptions be classified?",
          "a": "Exceptions should be classified by type before routing for review. Standard classification for Indian reconciliation: TAX_DEDUCTION (TDS or TCS deducted — expected, generates receivable entry), FEE_DEDUCTION (MDR, platform commission — expected, no further action), TIMING_DIFFERENCE (amount correct, wrong period — carry forward), AMOUNT_MISMATCH (genuine discrepancy — investigate), and MISSING_CREDIT (payment made, no bank confirmation — follow up with bank). Named classifications route exceptions to the right resolver automatically.",
          "article": "Exception Management in Reconciliation: From Detection to Resolution",
          "url": "https://www.terra-insight.com/insights/exception-management-reconciliation-india"
        },
        {
          "q": "What are appropriate resolution SLAs for reconciliation exceptions?",
          "a": "Standard resolution SLAs for Indian finance teams: TAX_DEDUCTION exceptions — 2 business days (verify against Form 26AS or GSTR-2B); TIMING_DIFFERENCE — 5 business days or carry to next period; AMOUNT_MISMATCH — 3 business days for amounts above ₹10,000 (escalate to finance manager); MISSING_CREDIT — 1 business day (contact bank with UTR); FEE_DEDUCTION — auto-resolve within same day. All exceptions above ₹1 lakh should have CFO or controller visibility within 24 hours.",
          "article": "Exception Management in Reconciliation: From Detection to Resolution",
          "url": "https://www.terra-insight.com/insights/exception-management-reconciliation-india"
        },
        {
          "q": "How do you identify root causes of recurring reconciliation exceptions?",
          "a": "Root cause analysis for recurring exceptions requires looking at patterns across multiple periods: if the same TDS deductor generates monthly exceptions, they are likely filing with the wrong PAN or section code (fix: send correction request once; add to watch list). If platform settlement exceptions recur monthly for the same gateway, the MDR rate in your system may be wrong (fix: update the rate; reconcile retroactively). Exception pattern analysis over 3 months typically identifies 3–5 systemic causes that account for 70–80% of total exceptions.",
          "article": "Exception Management in Reconciliation: From Detection to Resolution",
          "url": "https://www.terra-insight.com/insights/exception-management-reconciliation-india"
        },
        {
          "q": "What is an exception prevention system in reconciliation?",
          "a": "An exception prevention system uses the patterns from historical exceptions to prevent new ones. Examples: (1) a counterparty watch list — deductors who have historically filed with wrong PAN are auto-flagged before their TDS entry is posted; (2) a rate validation rule — if MDR charged differs from contracted rate by more than 0.05%, flag before posting; (3) a duplicate detection rule — if a credit with the same UTR has been processed before, block the entry. Prevention reduces new exceptions; it does not eliminate the need for exception management on the residual.",
          "article": "Exception Management in Reconciliation: From Detection to Resolution",
          "url": "https://www.terra-insight.com/insights/exception-management-reconciliation-india"
        },
        {
          "q": "What is fixed asset reconciliation in India?",
          "a": "Fixed asset reconciliation is the process of confirming that the fixed asset register (listing of all assets, their cost, accumulated depreciation, and net book value) agrees with the general ledger FA account, that depreciation calculated matches the depreciation charge in the P&L, and that assets physically exist and are in the condition recorded. In India, it also includes reconciling GST ITC on capital assets and confirming that the depreciation method (WDV or SLM) is consistently applied under Schedule II of the Companies Act.",
          "article": "Fixed Asset Reconciliation: Register, Depreciation, and Physical Verification",
          "url": "https://www.terra-insight.com/insights/fixed-asset-reconciliation-india"
        },
        {
          "q": "What is the difference between WDV and SLM depreciation for reconciliation purposes?",
          "a": "Written Down Value (WDV) method applies the depreciation rate to the net book value each year — so the depreciation amount decreases each year as the book value reduces. Straight Line Method (SLM) applies the rate to the original cost — so depreciation is constant each year. Schedule II of the Companies Act prescribes useful lives for different asset classes; the depreciation rate depends on whether WDV or SLM is used. Reconciliation must confirm which method is applied per asset class and that it has been applied consistently.",
          "article": "Fixed Asset Reconciliation: Register, Depreciation, and Physical Verification",
          "url": "https://www.terra-insight.com/insights/fixed-asset-reconciliation-india"
        },
        {
          "q": "How is GST ITC on capital assets reconciled?",
          "a": "GST ITC on capital goods (fixed assets) must appear in GSTR-2B for the period the asset was purchased. Under the ITC rules, there are specific restrictions on capital goods ITC: vehicles used for passenger transport are blocked under Section 17(5), and certain categories of capital goods have ITC restrictions. Reconciliation confirms that ITC claimed on capital goods matches GSTR-2B, that blocked ITC has been reversed, and that any proportional reversal under Rule 43 (for assets used for both taxable and exempt supplies) has been applied.",
          "article": "Fixed Asset Reconciliation: Register, Depreciation, and Physical Verification",
          "url": "https://www.terra-insight.com/insights/fixed-asset-reconciliation-india"
        },
        {
          "q": "What happens if the physical verification count differs from the register?",
          "a": "Discrepancies between physical count and the register require investigation: (1) assets in the register but not found physically — may have been disposed of, scrapped, or stolen; these must be written off with proper documentation (disposal approval, GST credit note if applicable, income tax treatment of capital loss); (2) assets found physically but not in the register — may be expensed items above the capitalisation threshold, or additions not yet posted; these must be capitalised at cost and the GST ITC claim reviewed.",
          "article": "Fixed Asset Reconciliation: Register, Depreciation, and Physical Verification",
          "url": "https://www.terra-insight.com/insights/fixed-asset-reconciliation-india"
        },
        {
          "q": "When must fixed asset reconciliation be completed for statutory audit?",
          "a": "Fixed asset reconciliation must be completed before the statutory auditor begins the audit. The auditor performs procedures including: tracing additions to purchase invoices and capital expenditure approval; confirming depreciation calculations against the Schedule II useful life table; and attending or reviewing the physical verification (SA 501 requires auditors to attend inventory counts; the same principle applies to significant fixed assets). Any reconciliation gaps discovered during audit extend the audit timeline and may result in observations.",
          "article": "Fixed Asset Reconciliation: Register, Depreciation, and Physical Verification",
          "url": "https://www.terra-insight.com/insights/fixed-asset-reconciliation-india"
        },
        {
          "q": "What are the main reconciliation challenges for foreign currency transactions in India?",
          "a": "The three main challenges are: (1) exchange rate differences — the invoice is raised in USD at one rate, the bank credits INR at a different rate on the actual settlement date, creating an exchange difference that must be posted to P&L; (2) NOSTRO account reconciliation — for companies with foreign currency accounts, the NOSTRO balance must be reconciled to the bank's statement in foreign currency; (3) forward contract settlements — if the company hedged the receivable with a forward contract, the settlement reconciliation must match the forward contract rate against the actual settlement rate.",
          "article": "Forex Reconciliation for Indian Companies: Matching Foreign Currency Transactions",
          "url": "https://www.terra-insight.com/insights/forex-reconciliation-india"
        },
        {
          "q": "How does the exchange rate difference arise in forex reconciliation?",
          "a": "An Indian IT company raises an invoice for USD 10,000 when the exchange rate is ₹83.50. The invoice is booked at ₹8,35,000. When payment arrives 45 days later, the exchange rate is ₹84.20 — the bank credits ₹8,42,000. The ₹7,000 difference is a foreign exchange gain and must be posted to the P&L under Ind AS 21. The reconciliation must identify the invoice rate vs settlement rate difference and route the variance to the correct P&L account.",
          "article": "Forex Reconciliation for Indian Companies: Matching Foreign Currency Transactions",
          "url": "https://www.terra-insight.com/insights/forex-reconciliation-india"
        },
        {
          "q": "What is a NOSTRO account and how is it reconciled?",
          "a": "A NOSTRO account is a foreign currency account maintained by an Indian bank on behalf of a company for receiving foreign payments. The NOSTRO balance appears on the company's books in INR (converted at the current rate) and on the bank's statement in foreign currency (USD, EUR, GBP, etc.). NOSTRO reconciliation involves: matching the bank's foreign currency statement to the ledger foreign currency balance, then revaluing the ledger balance at the period-end RBI reference rate and posting the revaluation gain or loss.",
          "article": "Forex Reconciliation for Indian Companies: Matching Foreign Currency Transactions",
          "url": "https://www.terra-insight.com/insights/forex-reconciliation-india"
        },
        {
          "q": "How is TDS handled on foreign payments received in India?",
          "a": "For foreign payments received by Indian residents — typically export income — TDS is generally not applicable as the foreign payer is not subject to Indian TDS obligations. However, if an Indian company receives a payment from an Indian subsidiary of a foreign company, the Indian subsidiary is subject to TDS rules and must deduct accordingly. Section 195 governs TDS on payments to non-residents made from India. The reconciliation logic differs depending on whether the payment is from a domestic or foreign entity.",
          "article": "Forex Reconciliation for Indian Companies: Matching Foreign Currency Transactions",
          "url": "https://www.terra-insight.com/insights/forex-reconciliation-india"
        },
        {
          "q": "What is form 15CA/15CB and does it affect reconciliation?",
          "a": "Form 15CA is a declaration filed online by an Indian entity making a payment to a non-resident, and Form 15CB is a CA certificate accompanying it for payments above a threshold. These forms govern the remittance of payments out of India under FEMA. For reconciliation purposes, each outward foreign payment must be matched to the corresponding Form 15CA filing — if Form 15CA was not filed before the payment, the payment is a FEMA violation and must be reported to the bank.",
          "article": "Forex Reconciliation for Indian Companies: Matching Foreign Currency Transactions",
          "url": "https://www.terra-insight.com/insights/forex-reconciliation-india"
        },
        {
          "q": "Must GST be charged on intercompany transactions in India?",
          "a": "Yes. Under Section 7(1)(c) of the CGST Act, supply between distinct persons (different GSTINs of the same legal entity or different group companies) is treated as supply even without consideration. The value is determined under Rule 28 of the CGST Valuation Rules — for related parties, the value must be the open market value or the cost-plus margin acceptable under GST rules. Failing to charge GST on intercompany supplies is a common compliance gap in Indian group companies.",
          "article": "Intercompany Reconciliation in India: Group Finance Complexity",
          "url": "https://www.terra-insight.com/insights/intercompany-reconciliation-india"
        },
        {
          "q": "Does TDS apply to payments between group companies in India?",
          "a": "Yes. TDS provisions apply to all payments between Indian entities regardless of group relationship. A holding company paying a subsidiary for professional services must deduct TDS under Section 194J at 10%. A subsidiary paying a parent for technical consultancy is similarly liable. Group company status does not exempt any party from TDS obligations — a common misconception that leads to TDS demand notices.",
          "article": "Intercompany Reconciliation in India: Group Finance Complexity",
          "url": "https://www.terra-insight.com/insights/intercompany-reconciliation-india"
        },
        {
          "q": "What is intercompany reconciliation in the context of consolidation?",
          "a": "In group consolidation under Ind AS or Companies Act, intercompany transactions must be eliminated — the holding company's receivable from the subsidiary must equal the subsidiary's payable to the holding company. If both sides of the intercompany balance are not identical (due to timing differences, currency, or GST treatment), elimination entries create residual balances in the consolidated statements. Reconciling intercompany balances before consolidation prevents these residuals.",
          "article": "Intercompany Reconciliation in India: Group Finance Complexity",
          "url": "https://www.terra-insight.com/insights/intercompany-reconciliation-india"
        },
        {
          "q": "How does transfer pricing documentation affect intercompany reconciliation?",
          "a": "Transfer pricing requires that intercompany transactions are priced at arm's length value. The actual transaction amounts must reconcile with the pricing documented in the transfer pricing study. If actual charges differ from the study rates — due to volume changes, cost center adjustments, or currency movements — the transfer pricing documentation must be updated, and the difference may trigger a transfer pricing adjustment notice from the Income Tax Department.",
          "article": "Intercompany Reconciliation in India: Group Finance Complexity",
          "url": "https://www.terra-insight.com/insights/intercompany-reconciliation-india"
        },
        {
          "q": "What is the most common intercompany reconciliation error in Indian group companies?",
          "a": "The most common error is timing differences: Company A records an intercompany sale in March, but Company B records the purchase in April (next financial year). This creates a balance that eliminates in one company's books but not the other's — resulting in a consolidation difference. The solution is an agreed intercompany cut-off date (typically the last working day of February) with both sides recording transactions by the same date for FY close purposes.",
          "article": "Intercompany Reconciliation in India: Group Finance Complexity",
          "url": "https://www.terra-insight.com/insights/intercompany-reconciliation-india"
        },
        {
          "q": "Why does gross vs net create reconciliation failures in India?",
          "a": "In India, TDS is deducted at source by the payer — not by the payee. When an invoice of ₹1,00,000 is paid with 10% TDS deducted, the bank credit is ₹90,000. A generic matching system that tries to match ₹90,000 against a ₹1,00,000 invoice fails — creating a ₹10,000 exception. The correct approach splits the match: bank credit of ₹90,000 + TDS receivable of ₹10,000 = gross invoice of ₹1,00,000. This requires the matching logic to know the applicable TDS section and rate.",
          "article": "Invoice Matching With TDS: Net vs Gross Reconciliation for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/invoice-matching-tds-net-gross-india"
        },
        {
          "q": "What is the TDS rate for professional services under Section 194J?",
          "a": "Under Section 194J, TDS is deducted at 10% on fees for professional services (including technical services in most cases). A ₹1,00,000 professional services invoice results in a ₹90,000 bank credit and a ₹10,000 TDS receivable. For pure technical services or call centre services, the rate may be 2% — resulting in a ₹98,000 credit and ₹2,000 receivable. The correct section code determines which rate applies.",
          "article": "Invoice Matching With TDS: Net vs Gross Reconciliation for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/invoice-matching-tds-net-gross-india"
        },
        {
          "q": "How does TDS matching work for Section 194C contractors?",
          "a": "Section 194C applies to contract payments at 1% (individual/HUF) or 2% (others). A ₹5,00,000 contract payment to a company results in a ₹4,90,000 bank credit and a ₹10,000 TDS receivable. The matching logic for 194C requires: identifying the client as a payer subject to 194C deduction, applying 2% to the invoice gross, and flagging the resulting net credit for TDS receivable generation.",
          "article": "Invoice Matching With TDS: Net vs Gross Reconciliation for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/invoice-matching-tds-net-gross-india"
        },
        {
          "q": "What happens when the deductor applies the wrong TDS rate?",
          "a": "If a deductor applies 10% under Section 194J on what should be a 2% technical services payment under 194J (using the post-Finance Act 2020 rate), the bank credit will be lower than expected: ₹90,000 instead of ₹98,000 on a ₹1,00,000 invoice. This creates both a cash flow difference and a Form 26AS mismatch. The resolution requires the deductor to file a correction return — and the payee to carry the excess TDS receivable until it appears in Form 26AS.",
          "article": "Invoice Matching With TDS: Net vs Gross Reconciliation for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/invoice-matching-tds-net-gross-india"
        },
        {
          "q": "How do you handle partial TDS deductions?",
          "a": "Partial TDS deductions occur when a client deducts TDS on only part of the invoice — often when the invoice covers both taxable and non-taxable components. The matching logic must support partial TDS allocation: match the bank credit against the taxable portion of the invoice net of TDS, and the non-taxable portion at gross, producing a blended match. This requires the matching engine to parse invoice line items, not just invoice totals.",
          "article": "Invoice Matching With TDS: Net vs Gross Reconciliation for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/invoice-matching-tds-net-gross-india"
        },
        {
          "q": "What reconciliation is required for a DRHP filing?",
          "a": "SEBI's ICDR Regulations require three years of restated financial statements — balance sheet, P&L, and cash flow statement — with a reconciliation between the originally reported figures and the restated figures. Finance teams must also reconcile: TDS receivable to Form 26AS for all three years, ITC claimed to GSTR-2B for all years, related party transaction disclosures, and working capital as at the date of filing.",
          "article": "IPO Reconciliation: What Finance Teams Must Do Before Filing the DRHP",
          "url": "https://www.terra-insight.com/insights/ipo-reconciliation-drhp-india"
        },
        {
          "q": "How do restated financials differ from audited financials in an IPO?",
          "a": "Restated financials adjust the prior-year audited financials for material errors, changes in accounting policy, and adjustments identified during the IPO due diligence process. The restatement reconciliation must explain every line-item difference between the originally audited figures and the restated figures — this reconciliation is reviewed by SEBI and is included in the DRHP.",
          "article": "IPO Reconciliation: What Finance Teams Must Do Before Filing the DRHP",
          "url": "https://www.terra-insight.com/insights/ipo-reconciliation-drhp-india"
        },
        {
          "q": "What TDS reconciliation is required before an IPO?",
          "a": "All TDS receivable must be reconciled to Form 26AS for each year covered by the DRHP. Outstanding TDS demands or unrecognised TDS credits must be disclosed or resolved before filing. TDS demand notices received during the DRHP period are material disclosures under SEBI's risk factor requirements.",
          "article": "IPO Reconciliation: What Finance Teams Must Do Before Filing the DRHP",
          "url": "https://www.terra-insight.com/insights/ipo-reconciliation-drhp-india"
        },
        {
          "q": "How far in advance should IPO reconciliation begin?",
          "a": "IPO reconciliation should begin at least 12–18 months before the anticipated DRHP filing date. This provides time to resolve Form 26AS mismatches (which require deductor correction returns), settle pending GST demands, clear intercompany balances, and produce clean restated financials. Companies that start reconciliation in the final 3 months before filing typically find material items that delay the DRHP.",
          "article": "IPO Reconciliation: What Finance Teams Must Do Before Filing the DRHP",
          "url": "https://www.terra-insight.com/insights/ipo-reconciliation-drhp-india"
        },
        {
          "q": "What is the impact of unreconciled GST on an IPO?",
          "a": "Unreconciled GST — excess ITC claimed, pending GSTR-9 reconciliation, or unresolved GST demands — must be disclosed in the DRHP as contingent liabilities. GST demand notices received in the last 12 months are typically highlighted in the statutory auditor's report and reviewed closely by SEBI. Material unreconciled amounts can delay IPO approval.",
          "article": "IPO Reconciliation: What Finance Teams Must Do Before Filing the DRHP",
          "url": "https://www.terra-insight.com/insights/ipo-reconciliation-drhp-india"
        },
        {
          "q": "How many staff hours does manual reconciliation take per month for a mid-size Indian company?",
          "a": "A company with 5 bank accounts, 30 active TDS deductors, and GST turnover above ₹5 crore typically spends 8–15 staff days per month on manual reconciliation — covering bank reconciliation, Form 26AS matching, GSTR-2B vs purchase register, and platform settlement matching. This is equivalent to 1–1.5 FTEs doing reconciliation work only.",
          "article": "Manual vs Automated Reconciliation: The True Cost Comparison",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-reconciliation-india"
        },
        {
          "q": "What is the error rate for spreadsheet-based reconciliation in India?",
          "a": "Spreadsheet-based matching typically achieves 51–65% auto-match rates for Indian transaction sets, with the rest requiring manual review. Errors in manual reconciliation are most common at three points: TDS rate application (wrong section rate used), GSTR-2B timing (prior-month invoices matched to current GSTR-2B), and partial payment allocation (amount split across multiple invoices incorrectly).",
          "article": "Manual vs Automated Reconciliation: The True Cost Comparison",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-reconciliation-india"
        },
        {
          "q": "When does manual reconciliation still make sense?",
          "a": "Manual reconciliation remains viable when: monthly transaction volume is below 300 items, the company has a single bank account, there are fewer than 10 active TDS deductors, and GST turnover is below ₹2 crore. Above these thresholds, spreadsheet-based matching produces error rates and staff costs that exceed the cost of purpose-built tooling.",
          "article": "Manual vs Automated Reconciliation: The True Cost Comparison",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-reconciliation-india"
        },
        {
          "q": "How do I calculate the ROI on reconciliation automation?",
          "a": "ROI = (Staff hours saved × blended hourly cost) + (ITC recovered that would have been missed) + (TDS credits recovered) + (Penalty avoidance value) — divided by annual software cost. For a company saving 8 staff days per month at ₹2,500/day, the staff saving alone is ₹2,40,000/year. Add ITC recovery and penalty avoidance, and most organisations see payback in 6–12 months.",
          "article": "Manual vs Automated Reconciliation: The True Cost Comparison",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-reconciliation-india"
        },
        {
          "q": "What is the fastest way to transition from manual to automated reconciliation?",
          "a": "The fastest transition follows three steps: (1) map all current data sources — bank statements, TRACES Form 26AS, GSTR-2B, and platform settlement files; (2) define matching rules for each reconciliation type before switching tools; (3) run manual and automated processes in parallel for one full month to validate match accuracy before going live. Most deployments complete in 2–4 weeks.",
          "article": "Manual vs Automated Reconciliation: The True Cost Comparison",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-reconciliation-india"
        },
        {
          "q": "How long should month-end close reconciliation take for an Indian company?",
          "a": "For a company with 3–5 bank accounts, 20–40 TDS deductors, and monthly GST turnover above ₹2 crore, month-end reconciliation should take 3–5 working days with manual processes. With automated matching, the matching phase compresses to 4–8 hours, with 1–2 days reserved for exception review and sign-off. Close cycles taking more than 7 days typically indicate a process problem — volume, tool limitations, or unresolved prior-month exceptions.",
          "article": "Month-End Close Reconciliation Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/month-end-close-reconciliation-checklist-india"
        },
        {
          "q": "On what date should month-end bank reconciliation be completed?",
          "a": "Bank reconciliation should be completed within 3 working days of month-end — by the 3rd or 4th of the following month. This allows time for GSTR-3B filing (due 20th of the following month) to be based on accurate tax liability figures. Outstanding cheques and deposits in transit from month-end should be documented and followed up within 5 working days.",
          "article": "Month-End Close Reconciliation Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/month-end-close-reconciliation-checklist-india"
        },
        {
          "q": "What is the GSTR-3B filing deadline and how does it affect the close schedule?",
          "a": "GSTR-3B is due on the 20th of the month following the tax period (18th for quarterly filers under QRMP scheme). ITC reconciliation against GSTR-2B must be completed before filing, since excess ITC claimed carries 18% interest under Section 50 of the CGST Act. This means GSTR-2B vs purchase register reconciliation must be complete by the 15th of each month to allow time for GSTR-3B preparation.",
          "article": "Month-End Close Reconciliation Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/month-end-close-reconciliation-checklist-india"
        },
        {
          "q": "What should be in a month-end reconciliation sign-off?",
          "a": "A month-end reconciliation sign-off should document: the date of final bank reconciliation for each account, the outstanding exception count and materiality classification, TDS mismatches pending deductor correction returns, ITC reversals made in GSTR-3B, platform settlement variances carried forward, and the name and designation of the approving authority. This documentation serves as the audit trail for the month.",
          "article": "Month-End Close Reconciliation Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/month-end-close-reconciliation-checklist-india"
        },
        {
          "q": "How do platform settlements affect the month-end close schedule?",
          "a": "Platform settlements (Razorpay, PayU, Cashfree) have a T+1 to T+3 settlement lag, meaning revenue collected on the 30th of a month may arrive in the bank account on the 1st or 2nd of the next month. Month-end reconciliation must account for these in-transit credits and match them against the settlement files — not the bank statement — to avoid revenue recognition timing errors.",
          "article": "Month-End Close Reconciliation Checklist for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/month-end-close-reconciliation-checklist-india"
        },
        {
          "q": "Why do Indian companies operate multiple bank accounts?",
          "a": "Indian companies typically maintain multiple bank accounts for operational separation: a primary current account for vendor payments, a dedicated NACH mandate collection account (required by NPCI for NACH debits), a salary disbursement account (for payroll processing via NEFT/RTGS), a GST refund credit account (some companies prefer to segregate these credits), and escrow accounts for regulatory requirements (RERA, marketplace nodal accounts). Each account has different reconciliation requirements and frequency.",
          "article": "Multi-Bank Reconciliation in India: How to Manage Multiple Bank Accounts",
          "url": "https://www.terra-insight.com/insights/multi-bank-reconciliation-india"
        },
        {
          "q": "What is the biggest challenge in multi-bank reconciliation?",
          "a": "The biggest challenge is inter-bank transfers — when money moves from one company account to another (for example, sweeping collections from the NACH account to the main operating account). An inter-bank transfer appears as a debit in one account and a credit in the other. Without a matching process across both accounts, the transfer appears as an unmatched debit in account A and an unmatched credit in account B — creating false exceptions in both reconciliations.",
          "article": "Multi-Bank Reconciliation in India: How to Manage Multiple Bank Accounts",
          "url": "https://www.terra-insight.com/insights/multi-bank-reconciliation-india"
        },
        {
          "q": "How should inter-bank transfers be reconciled?",
          "a": "Inter-bank transfers must be matched across accounts, not just within each account. The matching logic: identify the transfer reference (UTR number for NEFT/RTGS), match the debit in account A to the credit in account B using the UTR, mark both as reconciled. The UTR is the linking key — it appears in both the sending account's debit record and the receiving account's credit record. Transfers that do not match within 1 business day are investigated for system errors or failed transfers.",
          "article": "Multi-Bank Reconciliation in India: How to Manage Multiple Bank Accounts",
          "url": "https://www.terra-insight.com/insights/multi-bank-reconciliation-india"
        },
        {
          "q": "What is a cash pooling structure and how does it affect reconciliation?",
          "a": "Cash pooling is an arrangement where a group of bank accounts maintains a zero balance at end of day — all balances are automatically swept to a master account overnight. The next morning, sub-accounts are funded from the master account as needed. Each sweep creates a debit in the sub-account and a credit in the master (or vice versa). Reconciliation must match all pool sweeps, which may number 15–30 per day across all accounts in the pool.",
          "article": "Multi-Bank Reconciliation in India: How to Manage Multiple Bank Accounts",
          "url": "https://www.terra-insight.com/insights/multi-bank-reconciliation-india"
        },
        {
          "q": "How do you get a consolidated cash position from multiple bank accounts?",
          "a": "A consolidated cash position requires real-time or near-real-time data from all bank accounts. Options: (1) bank API integration — the reconciliation system pulls the current balance from each bank's API; (2) MT940 SWIFT messages — banks send the previous day's statement in MT940 format each morning; (3) manual download — each account's statement is downloaded and uploaded to the reconciliation system. API integration is the most accurate; manual download introduces a 1-day lag.",
          "article": "Multi-Bank Reconciliation in India: How to Manage Multiple Bank Accounts",
          "url": "https://www.terra-insight.com/insights/multi-bank-reconciliation-india"
        },
        {
          "q": "What is netting in the context of financial reconciliation?",
          "a": "Netting is the offsetting of amounts owed between two parties — where instead of each party paying the other separately, only the net difference is settled. In reconciliation, netting creates a mismatch: the bank statement shows the net settlement amount, but the books show the gross receivable and gross payable separately. Reconciliation must match the net bank credit against the appropriate combination of individual transactions.",
          "article": "Netting Reconciliation in India: How to Handle Net Payments Between Counterparties",
          "url": "https://www.terra-insight.com/insights/netting-reconciliation-india"
        },
        {
          "q": "Is netting of TDS receivable against TDS payable allowed in India?",
          "a": "TDS receivable (amounts deducted on payments received) and TDS payable (amounts to be deducted on payments made) cannot be netted against each other for remittance purposes. TDS payable must be deposited in full by the 7th of the following month against the correct challan codes. TDS receivable is claimed as a credit against advance tax. The two operate in different regulatory frameworks and cannot be offset at the treasury level.",
          "article": "Netting Reconciliation in India: How to Handle Net Payments Between Counterparties",
          "url": "https://www.terra-insight.com/insights/netting-reconciliation-india"
        },
        {
          "q": "How does platform netting work in Indian marketplace businesses?",
          "a": "Marketplace platforms net payable commissions against receivable settlements. For example, a seller on a platform may be owed ₹1,00,000 in GMV share while owing ₹8,000 in commission — the platform settles ₹92,000 (net). The seller's finance team must reconcile the gross ₹1,00,000 receivable, the ₹8,000 commission payable, and the ₹92,000 bank credit as three separate entries — not just match the net settlement.",
          "article": "Netting Reconciliation in India: How to Handle Net Payments Between Counterparties",
          "url": "https://www.terra-insight.com/insights/netting-reconciliation-india"
        },
        {
          "q": "What are the GST implications of netting between a client and a supplier?",
          "a": "GST must be charged on the gross invoice value — not on the netted amount. If a company is both a customer and supplier to the same counterparty, both invoices must be raised at full value with full GST. The netting arrangement only applies to the cash settlement. Attempting to raise a net invoice (net of the offsetting transaction) violates GST invoice rules and results in incorrect ITC claims for both parties.",
          "article": "Netting Reconciliation in India: How to Handle Net Payments Between Counterparties",
          "url": "https://www.terra-insight.com/insights/netting-reconciliation-india"
        },
        {
          "q": "How should group company netting be documented for audit purposes?",
          "a": "Group company netting arrangements must be documented with: a formal netting agreement signed by both entities, a monthly netting statement showing the individual transactions, the gross amounts, and the net settlement, confirmation of the net amount by both entities' finance teams, and bank-level confirmation of the settlement. The statutory auditor will request netting agreements as part of the related party transaction review.",
          "article": "Netting Reconciliation in India: How to Handle Net Payments Between Counterparties",
          "url": "https://www.terra-insight.com/insights/netting-reconciliation-india"
        },
        {
          "q": "What is a nodal account in India?",
          "a": "A nodal account is a dedicated bank account maintained by a payment aggregator or marketplace to hold buyer funds collected from online transactions, before settling them to merchants. RBI regulations require payment aggregators to maintain all collected funds in a nodal account with a scheduled commercial bank — the funds cannot be commingled with the aggregator's own funds. Settlement to merchants must occur within T+1 (for small merchants) or T+2 (standard) of the transaction date.",
          "article": "Nodal and Escrow Account Reconciliation: RBI Compliance for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/nodal-escrow-reconciliation-india"
        },
        {
          "q": "What reconciliation does RBI require for nodal accounts?",
          "a": "RBI's guidelines for payment aggregators require: (1) daily reconciliation of the nodal account balance against collected but unsettled funds; (2) daily settlement of merchant payouts from the nodal account within the prescribed timeline; (3) maintenance of a transaction-level ledger showing each buyer payment, the corresponding merchant, and the settlement date; (4) monthly reporting to RBI on the nodal account balance and settlement performance. The nodal reconciliation must demonstrate that the account holds no excess funds (only unsettled merchant payouts).",
          "article": "Nodal and Escrow Account Reconciliation: RBI Compliance for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/nodal-escrow-reconciliation-india"
        },
        {
          "q": "What is RERA escrow and how is it reconciled?",
          "a": "RERA Section 4(2)(l)(D) requires real estate developers to deposit at least 70% of collections from home buyers into a dedicated RERA escrow account. Withdrawals from the escrow are permitted only for land costs, construction costs, and services for the project — supported by architect certificates. Escrow reconciliation must track every deposit (70% of each flat payment), every withdrawal (with documentary evidence), and the closing balance must agree to the RERA authority portal's registered escrow balance.",
          "article": "Nodal and Escrow Account Reconciliation: RBI Compliance for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/nodal-escrow-reconciliation-india"
        },
        {
          "q": "What happens if the nodal account balance is insufficient to settle merchants?",
          "a": "If a payment aggregator's nodal account does not have sufficient balance to settle merchants on schedule, this is a regulatory violation. RBI can impose penalties, suspend the aggregator's licence, and require immediate settlement. The reconciliation control that prevents this: daily comparison of the nodal balance against the outstanding merchant settlement obligation. A nodal balance below the settlement obligation is a same-day escalation to the CFO and compliance team.",
          "article": "Nodal and Escrow Account Reconciliation: RBI Compliance for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/nodal-escrow-reconciliation-india"
        },
        {
          "q": "Can escrow funds earn interest in India?",
          "a": "Yes — RERA escrow accounts can earn interest, and under RERA, the interest must be treated as project income (credited to the project and withdrawn only per RERA withdrawal rules). For payment aggregator nodal accounts, RBI guidelines allow interest to accrue — the treatment depends on the specific nodal account agreement. Escrow interest reconciliation must track the interest credited, the applicable tax (TDS on interest under Section 194A if above threshold), and the regulatory treatment.",
          "article": "Nodal and Escrow Account Reconciliation: RBI Compliance for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/nodal-escrow-reconciliation-india"
        },
        {
          "q": "What is a partial payment in AR reconciliation?",
          "a": "A partial payment is when a client pays an amount less than the full invoice value — for example, paying ₹85,000 against an invoice of ₹1,00,000. The ₹15,000 difference remains as an outstanding balance. In India, partial payments are complicated by TDS: if the client deducts 10% TDS, the correct interpretation is ₹90,000 payment (gross) less ₹10,000 TDS = ₹80,000 bank credit. Distinguishing between a genuine partial payment and a TDS-net payment is the primary reconciliation challenge.",
          "article": "Partial Payment Reconciliation: How to Allocate and Match in Indian Finance",
          "url": "https://www.terra-insight.com/insights/partial-payment-reconciliation-india"
        },
        {
          "q": "How is TDS calculated on a partial payment?",
          "a": "TDS is calculated on the amount actually paid, not on the invoice total. If a client pays ₹80,000 against a ₹1,00,000 invoice and deducts TDS at 10%, the TDS is ₹8,000 (10% of ₹80,000), and the bank credit is ₹72,000. The TDS receivable is ₹8,000. The remaining open balance on the invoice is ₹20,000. When the remaining ₹20,000 is paid later, TDS of ₹2,000 is deducted, and the bank credit is ₹18,000.",
          "article": "Partial Payment Reconciliation: How to Allocate and Match in Indian Finance",
          "url": "https://www.terra-insight.com/insights/partial-payment-reconciliation-india"
        },
        {
          "q": "How do you allocate a single payment across multiple invoices?",
          "a": "When a client makes a single payment that covers multiple invoices — for example, paying ₹4,50,000 against three invoices of ₹1,50,000 each — the allocation logic must: (1) identify which invoices the payment applies to (using remittance advice or client reference); (2) allocate the payment amount to each invoice; (3) apply TDS proportionally if the payment is net of TDS; (4) close invoices that are fully settled and update open balances for partially settled ones. Without a remittance advice, the allocation is ambiguous and requires client confirmation.",
          "article": "Partial Payment Reconciliation: How to Allocate and Match in Indian Finance",
          "url": "https://www.terra-insight.com/insights/partial-payment-reconciliation-india"
        },
        {
          "q": "What is the impact of incorrect partial payment allocation on GST?",
          "a": "Incorrect partial payment allocation does not directly affect the GST payable (which is liability-based on invoice date), but it affects the accounts receivable balance — which in turn affects the working capital statement, the debtors' age analysis, and the calculation of bad debt provisions. If partial payments are systematically misallocated, the AR ledger will show incorrect outstanding balances and the bad debt provision will be incorrect.",
          "article": "Partial Payment Reconciliation: How to Allocate and Match in Indian Finance",
          "url": "https://www.terra-insight.com/insights/partial-payment-reconciliation-india"
        },
        {
          "q": "How should credit notes be applied in partial payment reconciliation?",
          "a": "A credit note reduces the invoice outstanding balance before any cash payment is allocated. If a ₹1,00,000 invoice has a ₹10,000 credit note applied, the net outstanding is ₹90,000. A subsequent payment of ₹81,000 (with 10% TDS on ₹90,000) fully settles the invoice: ₹81,000 bank credit + ₹9,000 TDS receivable = ₹90,000 net outstanding. The reconciliation must apply credit notes before applying payments.",
          "article": "Partial Payment Reconciliation: How to Allocate and Match in Indian Finance",
          "url": "https://www.terra-insight.com/insights/partial-payment-reconciliation-india"
        },
        {
          "q": "What reconciliation standards do PE investors typically require?",
          "a": "PE investors typically require: monthly close completed by day 5 of the following month, board pack with reconciled financials delivered by day 10, variance analysis explaining deviations from budget and prior month, TDS receivable reconciled to Form 26AS quarterly, GST ITC reconciled to GSTR-2B monthly, and bank statements reconciled at month-end for all accounts. These are minimum standards — many PE funds require weekly cash reporting and daily settlement reconciliation.",
          "article": "Reconciliation in PE-Backed Companies: Meeting Investor Reporting Standards",
          "url": "https://www.terra-insight.com/insights/pe-backed-company-reconciliation-india"
        },
        {
          "q": "What is the biggest reconciliation gap in founder-led companies before PE investment?",
          "a": "The most common reconciliation gap in founder-led companies pre-PE is the absence of a continuous reconciliation process — most run batch reconciliation at year-end for the audit, not monthly. The result is that the PE investor's first 90-day financial review uncovers TDS mismatches, unreconciled platform settlements, and GSTR-2B mismatches that were never caught. The cleanup cost of 2–3 years of backlog is typically borne by the company in the first 6 months post-investment.",
          "article": "Reconciliation in PE-Backed Companies: Meeting Investor Reporting Standards",
          "url": "https://www.terra-insight.com/insights/pe-backed-company-reconciliation-india"
        },
        {
          "q": "How do PE funds verify reconciliation quality during due diligence?",
          "a": "PE due diligence teams typically request 12 months of bank reconciliation statements, Form 26AS vs TDS receivable reconciliation for the last 2–3 years, GSTR-2B vs purchase register reconciliation for the last 12 months, and platform settlement reconciliation for any marketplace or payment gateway channel. Gaps in any of these are marked as post-investment action items and may affect the valuation or deal structure.",
          "article": "Reconciliation in PE-Backed Companies: Meeting Investor Reporting Standards",
          "url": "https://www.terra-insight.com/insights/pe-backed-company-reconciliation-india"
        },
        {
          "q": "How should PE-backed companies structure monthly reconciliation for board reporting?",
          "a": "Board-ready reconciliation requires: bank reconciliation completed by day 2, platform settlements reconciled by day 3, AR and AP ledgers updated by day 4, GSTR-2B matched against the prior month's purchase register by day 5, and TDS receivable updated by day 5. This timeline requires continuous reconciliation running through the month — not a day-1 batch run.",
          "article": "Reconciliation in PE-Backed Companies: Meeting Investor Reporting Standards",
          "url": "https://www.terra-insight.com/insights/pe-backed-company-reconciliation-india"
        },
        {
          "q": "What is a reconciliation pack and what should it contain?",
          "a": "A reconciliation pack is the supporting documentation behind the board pack financials — typically a set of schedules showing: bank reconciliation for all accounts, AR ageing with reconciliation to the ledger, AP ageing with reconciliation, TDS receivable balance reconciled to Form 26AS, ITC claimed reconciled to GSTR-2B, and platform settlement summary. The reconciliation pack is what the auditor reviews at year-end — and what the next PE investor reviews in the next round's due diligence.",
          "article": "Reconciliation in PE-Backed Companies: Meeting Investor Reporting Standards",
          "url": "https://www.terra-insight.com/insights/pe-backed-company-reconciliation-india"
        },
        {
          "q": "How long must reconciliation records be retained under Indian law?",
          "a": "Under the Income Tax Act, books of account and supporting documents must be retained for 8 years from the end of the relevant assessment year (Section 44AA). Under GST law, records must be retained for 6 years from the last date of filing the annual return for the financial year (Rule 56 of CGST Rules). For companies under the Companies Act, records must be retained for 8 years from the end of the financial year. The effective minimum retention period for reconciliation records is 8 years.",
          "article": "Reconciliation Audit Trail: What Regulators Expect in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-audit-trail-india"
        },
        {
          "q": "What does CBDT expect in a reconciliation audit trail?",
          "a": "CBDT expects: a reconciliation of TDS receivable per books to Form 26AS for each assessment year, with named exceptions documented; evidence that correction return requests were filed for mismatched TDS entries; and a reconciliation of advance tax paid to TDS credit claimed. For companies subject to tax audit under Section 44AB, the reconciliation must be available for review by the tax auditor within 30 days of the audit commencement date.",
          "article": "Reconciliation Audit Trail: What Regulators Expect in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-audit-trail-india"
        },
        {
          "q": "What does a GST audit officer look for in reconciliation documentation?",
          "a": "A GST audit officer conducting scrutiny under Section 65 or investigation under Section 67 will request: the purchase register for the audit period, the GSTR-2B downloads for the same period, and the reconciliation statement showing how ITC claimed in GSTR-3B was derived from GSTR-2B. They will also request evidence of reversals made for ITC claimed without GSTR-2B support, and the basis for any proportional ITC reversal under Rules 42 and 43.",
          "article": "Reconciliation Audit Trail: What Regulators Expect in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-audit-trail-india"
        },
        {
          "q": "Can a spreadsheet serve as a reconciliation audit trail?",
          "a": "A spreadsheet can serve as an audit trail only if it is tamper-evident, dated, and version-controlled. In practice, spreadsheets do not meet these requirements — rows can be deleted, formulas changed, and dates edited without a record of the change. Statutory auditors and GST officers increasingly require system-generated audit trails, not spreadsheet exports, especially for organisations with monthly transactions above 500.",
          "article": "Reconciliation Audit Trail: What Regulators Expect in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-audit-trail-india"
        },
        {
          "q": "What is the difference between a digital and paper audit trail for reconciliation?",
          "a": "A digital audit trail is generated automatically by the reconciliation system — every match, every exception classification, every override is time-stamped and user-attributed. A paper audit trail is printed output signed by the finance manager. Digital trails are superior for regulatory purposes because they are immutable, searchable, and can be exported on demand. Under the DPDP Act and GST rules, digital records with appropriate access controls meet the requirements for electronic record-keeping.",
          "article": "Reconciliation Audit Trail: What Regulators Expect in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-audit-trail-india"
        },
        {
          "q": "What is the typical ROI of reconciliation automation for an Indian company?",
          "a": "For an organisation processing 1,000+ transactions per month, reconciliation automation typically delivers 300–500% ROI over 3 years. The primary drivers are staff cost savings (8–12 days/month → 1–2 days), ITC recovery (systematic GSTR-2B matching recovers 0.5–2% of purchases annually), and TDS credit recovery (unmatched TRACES credits). Payback period for mid-size companies is typically 6–12 months.",
          "article": "Reconciliation Automation ROI: A Framework for Indian Finance Leaders",
          "url": "https://www.terra-insight.com/insights/reconciliation-automation-roi-india"
        },
        {
          "q": "How do I calculate staff time saved from reconciliation automation?",
          "a": "Calculate: (Hours per month spent on reconciliation matching) × (Blended hourly rate of finance staff). For a 10-person finance team spending 30% of their time on reconciliation tasks, that is 3 FTE-equivalents. At ₹40,000/month per analyst, that is ₹1.2 lakh/month in staff cost attributable to reconciliation — or ₹14.4 lakh/year before salary growth.",
          "article": "Reconciliation Automation ROI: A Framework for Indian Finance Leaders",
          "url": "https://www.terra-insight.com/insights/reconciliation-automation-roi-india"
        },
        {
          "q": "How much ITC can a company recover through better GSTR-2B reconciliation?",
          "a": "Indian businesses with monthly purchases above ₹1 crore typically have 1–3% of purchase invoices with GSTR-2B timing issues — supplier filed late, GSTIN mismatch, or credit note not processed. At 18% GST on ₹1 crore monthly purchases (₹18 lakh/month ITC), even a 1% recovery improvement recovers ₹18,000/month or ₹2.16 lakh/year in ITC that would otherwise have been written off.",
          "article": "Reconciliation Automation ROI: A Framework for Indian Finance Leaders",
          "url": "https://www.terra-insight.com/insights/reconciliation-automation-roi-india"
        },
        {
          "q": "How do you quantify penalty avoidance as part of reconciliation ROI?",
          "a": "Calculate: (Average excess ITC claim per year at risk of notice) × 18% interest rate + expected penalty. For an organisation with ₹5 lakh in excess ITC claims discovered annually in audit, the interest alone is ₹90,000/year. Add a 25% penalty (₹1.25 lakh) and the penalty avoidance value is ₹2.15 lakh/year. This is a conservative estimate — actual notices often cover multiple years.",
          "article": "Reconciliation Automation ROI: A Framework for Indian Finance Leaders",
          "url": "https://www.terra-insight.com/insights/reconciliation-automation-roi-india"
        },
        {
          "q": "What is the three-year ROI model for reconciliation automation?",
          "a": "A three-year model adds: Year 1 = staff savings + ITC recovery + penalty avoidance − software cost − implementation cost. Year 2 = same benefits, no implementation cost. Year 3 = same benefits. For a company saving ₹18 lakh/year in combined benefits and paying ₹6 lakh/year for software (₹3 lakh implementation in Year 1), the three-year net benefit is ₹33 lakh. Three-year ROI = 183%.",
          "article": "Reconciliation Automation ROI: A Framework for Indian Finance Leaders",
          "url": "https://www.terra-insight.com/insights/reconciliation-automation-roi-india"
        },
        {
          "q": "What is a good match rate for bank reconciliation in India?",
          "a": "A good match rate for bank reconciliation is 90% or above for auto-matching (before manual review). Companies using bank API or MT940 integration typically achieve 92–96% auto-match rates. Companies relying on manual CSV downloads typically achieve 80–88%. A match rate below 80% indicates systematic issues: narration format mismatches, multiple payment channels not configured, or a high volume of NACH credits not being disaggregated.",
          "article": "Reconciliation Benchmarks for Indian Finance Teams: What Good Looks Like",
          "url": "https://www.terra-insight.com/insights/reconciliation-benchmarks-india-finance"
        },
        {
          "q": "What is the benchmark for GSTR-2B reconciliation match rates?",
          "a": "GSTR-2B match rates of 80–88% are typical for well-run Indian finance teams. The 12–20% that does not auto-match consists primarily of supplier filing delays (invoices not yet in GSTR-2B), GSTIN mismatches (supplier filed with wrong GSTIN), and rate differences (supplier applied a different GST rate than the purchase order). A match rate below 75% typically indicates a vendor master data quality issue — incorrect GSTINs or section codes in the system.",
          "article": "Reconciliation Benchmarks for Indian Finance Teams: What Good Looks Like",
          "url": "https://www.terra-insight.com/insights/reconciliation-benchmarks-india-finance"
        },
        {
          "q": "How many days should monthly reconciliation take to complete?",
          "a": "For a company with 5 bank accounts, 30 TDS deductors, and ₹5 crore+ GST turnover: manual reconciliation typically takes 8–12 days; automated reconciliation (matching phase) takes 1–2 days, with 1–2 days for exception review = 3–4 days total. Closing reconciliation by day 5 of the following month is achievable with automated matching. Closing by day 10 is achievable manually for mid-size companies. Closing after day 15 indicates a process problem.",
          "article": "Reconciliation Benchmarks for Indian Finance Teams: What Good Looks Like",
          "url": "https://www.terra-insight.com/insights/reconciliation-benchmarks-india-finance"
        },
        {
          "q": "What is the benchmark for exception resolution time in India?",
          "a": "Standard exception resolution SLAs for Indian reconciliation: TAX_DEDUCTION exceptions (TDS/TCS) — 2 business days; TIMING_DIFFERENCE — 5 business days or carry to next period; AMOUNT_MISMATCH above ₹10,000 — 3 business days; MISSING_CREDIT — 1 business day; FEE_DEDUCTION — same-day auto-resolution. Exceptions remaining unresolved after 30 days are a high-risk item — many ITC claims have a 30-day window before they require manual follow-up with suppliers.",
          "article": "Reconciliation Benchmarks for Indian Finance Teams: What Good Looks Like",
          "url": "https://www.terra-insight.com/insights/reconciliation-benchmarks-india-finance"
        },
        {
          "q": "What is the benchmark for reconciliation staff productivity in India?",
          "a": "Manual reconciliation: a senior finance analyst can process approximately 200–300 invoices per day in matching mode (before exceptions). For exception review, approximately 30–50 exceptions per day at ₹5,000–₹50,000 each. Automated reconciliation shifts the analyst's role from matching to exception review — the same analyst can review 80–100 classified exceptions per day vs manually matching 200–300 transactions. The productivity improvement is 3–5x, not in the number of transactions processed, but in the quality of time spent.",
          "article": "Reconciliation Benchmarks for Indian Finance Teams: What Good Looks Like",
          "url": "https://www.terra-insight.com/insights/reconciliation-benchmarks-india-finance"
        },
        {
          "q": "What is reconciliation debt?",
          "a": "Reconciliation debt is the accumulation of unmatched or unresolved financial transactions in your books — TDS credits in Form 26AS that have not been matched to the ledger, ITC in GSTR-2B that has not been reconciled against purchases, or bank credits sitting in a suspense account. Unlike financial debt, reconciliation debt grows without producing any corresponding asset — it represents potential future write-offs, penalties, and audit findings.",
          "article": "Reconciliation Debt: What It Costs Indian Companies Every Year",
          "url": "https://www.terra-insight.com/insights/reconciliation-debt-india"
        },
        {
          "q": "How does reconciliation debt accumulate in Indian companies?",
          "a": "Reconciliation debt accumulates when the matching process is deferred — typically because the team is overwhelmed by volume, the matching tools are inadequate, or the process runs monthly instead of continuously. Each deferred month adds new unmatched items on top of unresolved prior items. TDS entries older than the ITR filing deadline become unrecoverable. ITC older than the GSTR-9 deadline requires reversal with interest.",
          "article": "Reconciliation Debt: What It Costs Indian Companies Every Year",
          "url": "https://www.terra-insight.com/insights/reconciliation-debt-india"
        },
        {
          "q": "Which industries have the highest reconciliation debt in India?",
          "a": "Industries with the highest reconciliation debt are those combining high transaction volume with complex deduction structures: e-commerce (platform settlements with TCS and MDR), healthcare (TPA settlements with Section 194J TDS), IT services (multiple 194J deductors with different section interpretations), and real estate (buyer TDS under Section 194IA across hundreds of units).",
          "article": "Reconciliation Debt: What It Costs Indian Companies Every Year",
          "url": "https://www.terra-insight.com/insights/reconciliation-debt-india"
        },
        {
          "q": "Can reconciliation debt from prior years be recovered?",
          "a": "TDS credits from prior years can generally be recovered if the deductor filed the TDS return correctly and the credit appears in Form 26AS for the relevant assessment year. You can claim these credits by filing a revised ITR or through a refund claim, subject to the limitation period under the Income Tax Act (typically 4–6 years). ITC missed beyond the September return of the following year is generally irrecoverable under GST rules.",
          "article": "Reconciliation Debt: What It Costs Indian Companies Every Year",
          "url": "https://www.terra-insight.com/insights/reconciliation-debt-india"
        },
        {
          "q": "How do you calculate a company's reconciliation backlog?",
          "a": "Calculate reconciliation backlog by adding: (a) TDS receivable in books not matched to Form 26AS, (b) ITC claimed without GSTR-2B support, (c) bank suspense account balance, (d) accounts receivable older than 180 days without invoice confirmation. The total is the gross reconciliation debt. The recoverable portion depends on whether correction returns can still be filed and whether ITC claim deadlines have passed.",
          "article": "Reconciliation Debt: What It Costs Indian Companies Every Year",
          "url": "https://www.terra-insight.com/insights/reconciliation-debt-india"
        },
        {
          "q": "What is the most common cause of GST demand notices for Indian businesses?",
          "a": "The most common cause is ITC claimed in GSTR-3B that does not appear in GSTR-2B for the same period. Under Rule 36(4) of the CGST Rules, ITC can only be claimed for invoices appearing in GSTR-2B. Claims above this amount trigger an automated GSTR-2A/2B mismatch notice from the GSTN system. The solution is to reconcile GSTR-2B against the purchase register before filing GSTR-3B each month.",
          "article": "Top 10 Reconciliation Errors That Trigger GST Notices",
          "url": "https://www.terra-insight.com/insights/reconciliation-errors-gst-notices-india"
        },
        {
          "q": "How does a TDS deduction rate error trigger a GST notice?",
          "a": "TDS under Section 194C is deducted on the taxable value of a supply — not on the GST-inclusive amount. If TDS is incorrectly deducted on the total (taxable value + GST), the excess deduction creates a discrepancy in the buyer's books and may trigger a notice for excess TDS deduction under the Income Tax Act as well as a GST on reverse charge discrepancy. The correct deduction basis is the taxable value only.",
          "article": "Top 10 Reconciliation Errors That Trigger GST Notices",
          "url": "https://www.terra-insight.com/insights/reconciliation-errors-gst-notices-india"
        },
        {
          "q": "What is the penalty for ITC claimed without GSTR-2B support?",
          "a": "ITC claimed without GSTR-2B support is treated as excess ITC under Section 50 of the CGST Act. Interest is charged at 18% per annum from the date of excess claim to the date of reversal. There is no minimum threshold — even a ₹1,000 ITC claim without GSTR-2B support attracts interest. Additionally, if the claim is found in an audit, a penalty of up to 100% of the excess ITC may apply under Section 122.",
          "article": "Top 10 Reconciliation Errors That Trigger GST Notices",
          "url": "https://www.terra-insight.com/insights/reconciliation-errors-gst-notices-india"
        },
        {
          "q": "How do duplicate invoice entries cause GST notices?",
          "a": "A supplier who files the same invoice twice in GSTR-1 creates a duplicate entry in the buyer's GSTR-2B. If the buyer claims ITC on the duplicate without noticing, the total ITC claimed exceeds the actual supply value. When the supplier subsequently corrects the duplicate, the GSTR-2B update removes the entry — and the buyer's GSTR-3B shows ITC claimed that is no longer in GSTR-2B, triggering a mismatch notice.",
          "article": "Top 10 Reconciliation Errors That Trigger GST Notices",
          "url": "https://www.terra-insight.com/insights/reconciliation-errors-gst-notices-india"
        },
        {
          "q": "What should I do if I receive a GSTR-2A/2B mismatch notice?",
          "a": "On receiving a mismatch notice, you have 30 days to respond. Steps: (1) download the notice details and identify the specific invoices in dispute; (2) check whether the difference is a timing issue (supplier filed late) or a genuine discrepancy; (3) for timing differences, reverse the ITC in the current GSTR-3B and re-claim when the GSTR-2B is updated; (4) for genuine discrepancies, contact the supplier to file a correction return and provide a written response to the GST officer with supporting documentation.",
          "article": "Top 10 Reconciliation Errors That Trigger GST Notices",
          "url": "https://www.terra-insight.com/insights/reconciliation-errors-gst-notices-india"
        },
        {
          "q": "What is reconciliation infrastructure?",
          "a": "Reconciliation infrastructure is a configurable platform — not a fixed-function tool — that handles multiple reconciliation types (TDS, GST, bank, NACH, platform settlements) through a shared matching engine. It is 'infrastructure' in the sense that it is embedded in the finance operations layer and works across business types and data sources, rather than solving a single specific matching problem. Industry presets configure it for healthcare, NBFC, real estate, or e-commerce without custom code.",
          "article": "Reconciliation Infrastructure vs Reconciliation Software: A Critical Distinction",
          "url": "https://www.terra-insight.com/insights/reconciliation-infrastructure-vs-software"
        },
        {
          "q": "What is the difference between reconciliation software and reconciliation infrastructure?",
          "a": "Reconciliation software is a point solution: a bank reconciliation tool, a TDS matching tool, or a GST ITC tool. It solves one problem well but requires a separate tool for each reconciliation type. Reconciliation infrastructure is a unified platform: one matching engine, one exception queue, one audit trail — configured for all reconciliation types through rules and presets. As the business adds new reconciliation requirements (new payment gateways, new compliance forms), infrastructure scales without adding new tools.",
          "article": "Reconciliation Infrastructure vs Reconciliation Software: A Critical Distinction",
          "url": "https://www.terra-insight.com/insights/reconciliation-infrastructure-vs-software"
        },
        {
          "q": "What does API-first mean for reconciliation?",
          "a": "API-first reconciliation infrastructure connects to data sources programmatically — pulling bank statements via bank API, GSTN data via API (where available), ERP data via SAP RFC or Oracle API — rather than requiring manual file downloads and uploads. This enables near-real-time matching (daily or intraday) rather than monthly batch matching. For NBFCs, payment aggregators, and e-commerce companies processing thousands of daily transactions, API-first is the only viable architecture.",
          "article": "Reconciliation Infrastructure vs Reconciliation Software: A Critical Distinction",
          "url": "https://www.terra-insight.com/insights/reconciliation-infrastructure-vs-software"
        },
        {
          "q": "Why do industry presets matter in reconciliation infrastructure?",
          "a": "Industry presets encode the matching logic specific to a sector without requiring custom code for each deployment. A healthcare preset knows that a TPA settlement represents multiple patient claims and applies the correct split-matching logic. An NBFC preset knows that a NACH batch credit must be disaggregated against individual loan account mandates. Without presets, configuring these rules requires development work — adding weeks to deployment and cost to implementation.",
          "article": "Reconciliation Infrastructure vs Reconciliation Software: A Critical Distinction",
          "url": "https://www.terra-insight.com/insights/reconciliation-infrastructure-vs-software"
        },
        {
          "q": "How long does reconciliation infrastructure take to deploy?",
          "a": "Reconciliation infrastructure configured with industry presets typically deploys in 2–4 weeks — including data source connection, rule configuration, and parallel run validation. Point solutions deploying for a single reconciliation type may be faster. Custom-built solutions without presets typically take 3–6 months. The deployment window is relevant to the business case: a 2-week deployment means the first full month of operation captures ROI starting in month 2.",
          "article": "Reconciliation Infrastructure vs Reconciliation Software: A Critical Distinction",
          "url": "https://www.terra-insight.com/insights/reconciliation-infrastructure-vs-software"
        },
        {
          "q": "What are the most important KPIs for reconciliation in India?",
          "a": "The six most important reconciliation KPIs for Indian finance teams are: (1) overall auto-match rate — percentage of transactions matched without human intervention; (2) days to close — business days from period end to completed reconciliation; (3) exception resolution rate — percentage of exceptions resolved within SLA; (4) exception aging — percentage of open exceptions older than 30 days; (5) ITC leakage rate — percentage of eligible ITC not claimed due to reconciliation failure; (6) TDS credit recovery rate — percentage of Form 26AS TDS credits successfully claimed.",
          "article": "Reconciliation KPIs for Indian Finance Teams: Metrics, Targets, and Measurement",
          "url": "https://www.terra-insight.com/insights/reconciliation-kpis-india"
        },
        {
          "q": "How is the auto-match rate calculated?",
          "a": "Auto-match rate = (Transactions matched automatically ÷ Total transactions) × 100. For example: 850 of 1,000 transactions matched automatically = 85% auto-match rate. Calculate this separately for each reconciliation type — bank, TDS, GSTR-2B, platform settlement — because the baseline and benchmark differ by type. Track month-over-month trend, not just point-in-time value. A declining match rate is a leading indicator of process deterioration.",
          "article": "Reconciliation KPIs for Indian Finance Teams: Metrics, Targets, and Measurement",
          "url": "https://www.terra-insight.com/insights/reconciliation-kpis-india"
        },
        {
          "q": "How do you measure ITC leakage in reconciliation?",
          "a": "ITC leakage rate = (ITC available in GSTR-2B − ITC claimed in GSTR-3B − ITC pending from prior periods) ÷ ITC available in GSTR-2B × 100. A leakage rate above 2% warrants investigation — it means more than 2% of eligible input tax credit is being lost, either because invoices are not in GSTR-2B (supplier filing delay), the purchase register has errors (wrong GSTIN), or ITC was reversed due to excess claim. Each rupee of ITC leakage is a direct P&L charge.",
          "article": "Reconciliation KPIs for Indian Finance Teams: Metrics, Targets, and Measurement",
          "url": "https://www.terra-insight.com/insights/reconciliation-kpis-india"
        },
        {
          "q": "What is the TDS credit recovery rate and how is it tracked?",
          "a": "TDS credit recovery rate = (TDS credits claimed in ITR ÷ TDS credits booked in TDS receivable ledger) × 100. A rate below 90% indicates that some TDS receivable is not being recovered — either because the deductor filed incorrectly (wrong PAN, wrong section), the correction return was not filed in time, or the TDS receivable ledger has errors. Track this rate quarterly (aligned with ITR and advance tax filing timelines) rather than monthly.",
          "article": "Reconciliation KPIs for Indian Finance Teams: Metrics, Targets, and Measurement",
          "url": "https://www.terra-insight.com/insights/reconciliation-kpis-india"
        },
        {
          "q": "How often should reconciliation KPIs be reviewed?",
          "a": "Match rate and exception aging should be reviewed weekly by the finance controller and monthly by the CFO. Close cycle time is reviewed monthly. ITC leakage rate and TDS credit recovery rate are reviewed quarterly (aligned with GST quarterly review and advance tax instalment calculation). Annual review covers the full-year trend, benchmark comparison, and KPI target setting for the next financial year.",
          "article": "Reconciliation KPIs for Indian Finance Teams: Metrics, Targets, and Measurement",
          "url": "https://www.terra-insight.com/insights/reconciliation-kpis-india"
        },
        {
          "q": "What reconciliation metrics should a CFO review monthly?",
          "a": "CFOs should review five reconciliation metrics monthly: (1) overall match rate by reconciliation type (bank, TDS, GST, platform) — target above 85%; (2) exception aging — what percentage of open exceptions are older than 30 days; (3) reconciliation debt balance — total value of unresolved items; (4) high-value exceptions — any single exception above ₹5 lakh; (5) close cycle time — days from period end to completed reconciliation. These five metrics predict audit risk and cash leakage before they materialise.",
          "article": "Reconciliation Patterns Indian CFOs Should Track",
          "url": "https://www.terra-insight.com/insights/reconciliation-patterns-india-cfo"
        },
        {
          "q": "What does a declining match rate signal?",
          "a": "A declining match rate — GSTR-2B match rate dropping from 82% to 71% over 3 months, for example — typically signals one of three things: transaction volume has grown faster than the matching capacity of the current process; a supplier or deductor has changed their filing behaviour (new PAN, different section code, delayed filing); or a data source has changed format and the matching rules have not been updated. A declining match rate predicts an increasing exception backlog 2–3 periods ahead.",
          "article": "Reconciliation Patterns Indian CFOs Should Track",
          "url": "https://www.terra-insight.com/insights/reconciliation-patterns-india-cfo"
        },
        {
          "q": "How does reconciliation debt accumulate in Indian companies?",
          "a": "Reconciliation debt accumulates in layers. Month 1: 50 unresolved exceptions from GSTR-2B mismatch. Month 2: 50 new + 20 carry-forward = 70 exceptions. Month 3: the 20 month-1 items approach the ITC claim deadline — resolution becomes urgent. By month 4, some month-1 items are past the deadline and the ITC is permanently lost. The debt converted to a P&L charge. This pattern repeats unless the root cause is addressed.",
          "article": "Reconciliation Patterns Indian CFOs Should Track",
          "url": "https://www.terra-insight.com/insights/reconciliation-patterns-india-cfo"
        },
        {
          "q": "What is an exception aging report and why does it matter?",
          "a": "An exception aging report categorises open reconciliation exceptions by how long they have been unresolved: 0–7 days (within SLA), 8–30 days (approaching deadline), 31–90 days (at risk), and 90+ days (likely unrecoverable for ITC; correction return window for TDS may be closing). CFOs who review exception aging monthly catch the 31–90 day bucket before it becomes 90+. CFOs who do not see this report discover the problem at the audit.",
          "article": "Reconciliation Patterns Indian CFOs Should Track",
          "url": "https://www.terra-insight.com/insights/reconciliation-patterns-india-cfo"
        },
        {
          "q": "How do reconciliation patterns differ across Indian industries?",
          "a": "TDS-heavy industries (IT services, professional services, staffing) see the highest TDS exception rates — Section 194J and 194C mismatches are the dominant pattern. Marketplace and e-commerce businesses see platform settlement exceptions as the primary pattern — MDR deductions, TCS withheld, and bulk credit disaggregation. Manufacturing businesses with high purchase volumes see GSTR-2B matching as the primary exception source. The pattern determines the reconciliation investment priority.",
          "article": "Reconciliation Patterns Indian CFOs Should Track",
          "url": "https://www.terra-insight.com/insights/reconciliation-patterns-india-cfo"
        },
        {
          "q": "Do ERPs like SAP and Oracle handle reconciliation automatically?",
          "a": "ERPs handle the accounting layer — recording transactions, generating trial balances, and producing standard reports. They do not handle the external verification layer: matching the AR ledger against Form 26AS (TRACES), matching the purchase register against GSTR-2B (GSTN), or matching bank accounts against bank-issued statements via MT940. These external matches require a reconciliation layer that connects to government portals and bank systems — not just the ERP's internal data.",
          "article": "What CFOs Get Wrong About Reconciliation: 7 Costly Misconceptions",
          "url": "https://www.terra-insight.com/insights/reconciliation-misconceptions-cfo-india"
        },
        {
          "q": "Why is once-a-month reconciliation insufficient for Indian businesses above ₹5 crore GST turnover?",
          "a": "GSTR-2B is generated on the 14th of each month for the prior month's transactions, and GSTR-3B is due on the 20th. That gives finance teams 6 days to complete GSTR-2B vs purchase register reconciliation and file GSTR-3B. For organisations with 500+ purchase invoices per month, 6 days is insufficient if reconciliation has not been run continuously. Monthly batch reconciliation consistently results in ITC being claimed before GSTR-2B matching is complete — creating excess claims and interest exposure.",
          "article": "What CFOs Get Wrong About Reconciliation: 7 Costly Misconceptions",
          "url": "https://www.terra-insight.com/insights/reconciliation-misconceptions-cfo-india"
        },
        {
          "q": "Is reconciliation a back-office function?",
          "a": "Reconciliation failures have direct P&L consequences: lost TDS credits reduce the advance tax offset, ITC leakage increases the effective cost of goods, and GST penalties affect cash flow. These are CFO-level concerns, not back-office administrative matters. Organisations that treat reconciliation as a back-office task typically under-invest in tooling and understaff the function — producing exactly the audit findings and penalty exposure that CFOs consider strategic risks.",
          "article": "What CFOs Get Wrong About Reconciliation: 7 Costly Misconceptions",
          "url": "https://www.terra-insight.com/insights/reconciliation-misconceptions-cfo-india"
        },
        {
          "q": "Is manual review more accurate than automated reconciliation?",
          "a": "Manual review is more contextually accurate for genuine exceptions — a human can evaluate whether a ₹5,000 variance is a rounding error or a genuine discrepancy better than a rule-based system. But manual review is not more accurate than automation for the matching phase itself. Automation applies rules consistently across thousands of transactions without fatigue errors. Manual matching at scale introduces errors that accumulate — the same analyst who correctly resolves one exception makes errors on the 50th exception of the day.",
          "article": "What CFOs Get Wrong About Reconciliation: 7 Costly Misconceptions",
          "url": "https://www.terra-insight.com/insights/reconciliation-misconceptions-cfo-india"
        },
        {
          "q": "Can reconciliation debt be managed long-term?",
          "a": "Reconciliation debt cannot be sustainably managed — it can only be eliminated and prevented from re-accumulating. Managed reconciliation debt grows: each month's unresolved items add to the prior backlog, and ITC claim deadlines expire while TDS correction windows narrow. An organisation that decides to 'manage' ₹20 lakh in reconciliation debt for 3 months will typically find it has grown to ₹60 lakh by month 3, with portions becoming unrecoverable.",
          "article": "What CFOs Get Wrong About Reconciliation: 7 Costly Misconceptions",
          "url": "https://www.terra-insight.com/insights/reconciliation-misconceptions-cfo-india"
        },
        {
          "q": "Does SAP handle TDS reconciliation with Form 26AS?",
          "a": "SAP's India localisation (SAP S/4HANA for India) includes TDS deduction and posting capabilities, but does not natively connect to TRACES or download Form 26AS for automated matching. Finance teams using SAP typically export TDS receivable data from SAP and match it manually against Form 26AS downloads — or use a third-party reconciliation layer connected to SAP via RFC or file export.",
          "article": "Reconciliation in SAP vs Oracle vs Tally: What Finance Teams Need to Know",
          "url": "https://www.terra-insight.com/insights/reconciliation-sap-oracle-tally-india"
        },
        {
          "q": "Can Tally be used for GST reconciliation with GSTR-2B?",
          "a": "Tally Prime (TallyPrime 3.0 onwards) includes GSTR-2B import and reconciliation functionality. However, the reconciliation is at the invoice level and requires the supplier's GSTIN to be correctly entered in Tally. For organisations with 200+ purchase invoices per month, the Tally GSTR-2B reconciliation process still requires manual exception handling, particularly for invoices with GSTIN mismatches or debit/credit note adjustments.",
          "article": "Reconciliation in SAP vs Oracle vs Tally: What Finance Teams Need to Know",
          "url": "https://www.terra-insight.com/insights/reconciliation-sap-oracle-tally-india"
        },
        {
          "q": "What reconciliation capabilities does Oracle Financials have for India?",
          "a": "Oracle Fusion Financials includes India localisation for TDS (Oracle Tax Withholding) and GST (Oracle GST for India), but the GSTR-2B matching functionality requires Oracle's GST module to be configured and the GSTR-2B JSON to be uploaded manually each month. Oracle does not have a direct GSTN API integration in standard deployments — reconciliation against GSTR-2B still requires a separate process step.",
          "article": "Reconciliation in SAP vs Oracle vs Tally: What Finance Teams Need to Know",
          "url": "https://www.terra-insight.com/insights/reconciliation-sap-oracle-tally-india"
        },
        {
          "q": "When is an ERP not enough for reconciliation?",
          "a": "An ERP is not enough when: (1) transaction volume exceeds the ERP's matching performance (typically 1,000+ transactions/month), (2) the organisation uses multiple payment gateways whose settlement files do not integrate into the ERP, (3) NACH batch reconciliation is needed (most ERPs have no NACH-specific matching), or (4) the organisation requires continuous reconciliation rather than month-end processing.",
          "article": "Reconciliation in SAP vs Oracle vs Tally: What Finance Teams Need to Know",
          "url": "https://www.terra-insight.com/insights/reconciliation-sap-oracle-tally-india"
        },
        {
          "q": "How does a reconciliation layer integrate with SAP, Oracle, or Tally?",
          "a": "Integration approaches vary by ERP: SAP integration uses RFC calls or file-based export (BAPI or SAP FTP export in FBL1N/FBL5N format). Oracle integration uses Oracle API Gateway or scheduled exports from Oracle BI Publisher. Tally integration uses the Tally XML API or CSV export from standard Tally reports. Most reconciliation platforms support all three through pre-built connectors or configurable file-based ingestion.",
          "article": "Reconciliation in SAP vs Oracle vs Tally: What Finance Teams Need to Know",
          "url": "https://www.terra-insight.com/insights/reconciliation-sap-oracle-tally-india"
        },
        {
          "q": "What is the maximum acceptable month-end close time for an Indian company?",
          "a": "Industry benchmark for mid-size Indian companies (₹50–200 crore turnover) is 3–5 working days from month-end. A close cycle consistently exceeding 7 working days indicates a reconciliation process problem — either volume has outgrown the tools, or prior-month exceptions are not being resolved before the next cycle starts. Best-in-class organisations with automated reconciliation close in 1–2 days.",
          "article": "10 Signs Your Reconciliation Process Is Broken",
          "url": "https://www.terra-insight.com/insights/signs-reconciliation-process-broken-india"
        },
        {
          "q": "How many GST notices per year is considered a reconciliation problem?",
          "a": "Any GSTR-2B mismatch notice represents a preventable reconciliation failure — there is no acceptable baseline of 'some notices.' However, in practice, organisations receiving more than 2 demand notices or mismatch letters per financial year have a systematic reconciliation gap that needs process intervention, not just individual notice responses.",
          "article": "10 Signs Your Reconciliation Process Is Broken",
          "url": "https://www.terra-insight.com/insights/signs-reconciliation-process-broken-india"
        },
        {
          "q": "What does it mean when a finance team works weekends for month-end close?",
          "a": "Weekend work for month-end close is a leading indicator that the reconciliation process is broken — volume has outgrown the team's capacity within a normal work week. It indicates either that the matching is manual (and scales with transaction volume rather than being automated), or that prior-month exceptions are consuming time that should go to the current month's close.",
          "article": "10 Signs Your Reconciliation Process Is Broken",
          "url": "https://www.terra-insight.com/insights/signs-reconciliation-process-broken-india"
        },
        {
          "q": "What is a suspense account and why is a large suspense balance a warning sign?",
          "a": "A suspense account is used to temporarily park transactions that cannot be immediately classified — bank credits with no matching invoice, NACH credits not yet allocated, or cash receipts pending identification. A suspense account balance above ₹1 lakh that persists for more than 10 days indicates that reconciliation is being deferred rather than completed. A persistently large suspense balance is an audit observation under the Companies Act.",
          "article": "10 Signs Your Reconciliation Process Is Broken",
          "url": "https://www.terra-insight.com/insights/signs-reconciliation-process-broken-india"
        },
        {
          "q": "What causes frequent audit qualifications related to reconciliation?",
          "a": "Frequent audit qualifications on reconciliation typically arise from: bank reconciliation statements not prepared within 15 days of period end, TDS receivable not reconciled to Form 26AS, accounts receivable not confirmed with counterparties for amounts above ₹10 lakh, and suspense account items older than 30 days without documentation. Each of these is a standard statutory auditor check that a functioning reconciliation process prevents.",
          "article": "10 Signs Your Reconciliation Process Is Broken",
          "url": "https://www.terra-insight.com/insights/signs-reconciliation-process-broken-india"
        },
        {
          "q": "What is tolerance matching in reconciliation?",
          "a": "Tolerance matching is the practice of automatically resolving reconciliation differences that fall within a pre-defined threshold — for example, auto-resolving any variance of ₹5 or less as a rounding difference, without requiring human review. Tolerance rules reduce exception queues by handling the high-volume low-value variances that are predictable in Indian reconciliation (TDS rounding, MDR calculation differences, GST rounding).",
          "article": "Tolerance Matching in Reconciliation: Setting Thresholds for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tolerance-matching-reconciliation-india"
        },
        {
          "q": "What tolerance threshold is appropriate for TDS rounding differences?",
          "a": "TDS is calculated as a percentage of the gross payment amount. At low invoice values, this creates rounding differences of ₹1–₹5 depending on the calculation method (round half up vs round half down). A tolerance of ₹5 per TDS deduction is generally appropriate for auto-resolution. For high-value invoices where 1% TDS generates ₹200–₹500 in rounding differences, a percentage-based tolerance (0.5% of TDS amount) may be more appropriate.",
          "article": "Tolerance Matching in Reconciliation: Setting Thresholds for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tolerance-matching-reconciliation-india"
        },
        {
          "q": "What tolerance is appropriate for GST reconciliation?",
          "a": "GST amounts are calculated on invoice totals and rounded to the nearest rupee per the CGST Act. GSTR-2B may show amounts rounded differently from the purchase invoice. A tolerance of ₹2 per invoice line for GST amount differences is generally appropriate for auto-resolution. However, tolerance should not apply to GSTIN mismatches or invoice number mismatches — these require human review regardless of the amount.",
          "article": "Tolerance Matching in Reconciliation: Setting Thresholds for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tolerance-matching-reconciliation-india"
        },
        {
          "q": "Can tolerance matching be used for bank reconciliation?",
          "a": "Tolerance matching is appropriate for bank reconciliation differences arising from bank charges that vary slightly from expected (for example, bank charges of ₹118 instead of ₹120 in a month where charges typically run at ₹120). It is not appropriate for unexplained bank differences above ₹100 or any difference involving an unidentified credit or debit. The principle: tolerance applies to expected minor calculation differences, not to unexplained items.",
          "article": "Tolerance Matching in Reconciliation: Setting Thresholds for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tolerance-matching-reconciliation-india"
        },
        {
          "q": "How do you document tolerance-resolved exceptions for audit purposes?",
          "a": "Tolerance-resolved exceptions must be logged with: the original amount in each source, the variance amount, the tolerance rule applied, the date of auto-resolution, and the total monthly volume of tolerance-resolved items. Auditors review the tolerance resolution log as part of the reconciliation audit trail. The total amount auto-resolved under tolerance rules should be disclosed in the reconciliation sign-off documentation.",
          "article": "Tolerance Matching in Reconciliation: Setting Thresholds for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/tolerance-matching-reconciliation-india"
        },
        {
          "q": "What is a virtual account number in Indian banking?",
          "a": "A virtual account number (VAN) is a unique account number assigned to a specific customer or purpose, which routes incoming payments to a single physical bank account. When a customer pays using their assigned VAN via NEFT or RTGS, the bank automatically identifies the payment as coming from that customer — no narration parsing required. The physical bank account receives the credit, but the bank's system tags the credit with the VAN, enabling automatic reconciliation.",
          "article": "Virtual Account Reconciliation in India: How Auto-Matching Works",
          "url": "https://www.terra-insight.com/insights/virtual-account-reconciliation-india"
        },
        {
          "q": "How does virtual account reconciliation work?",
          "a": "When a payment is received on a VAN, the bank generates an event notification (via API webhook) containing: the VAN, the amount, the UTR, the payer account number, and the timestamp. The reconciliation system receives this webhook, looks up which customer is assigned to this VAN, and automatically creates the receipt entry against the appropriate AR ledger record. If the amount matches an open invoice, the invoice is closed. If not, the receipt is flagged for allocation.",
          "article": "Virtual Account Reconciliation in India: How Auto-Matching Works",
          "url": "https://www.terra-insight.com/insights/virtual-account-reconciliation-india"
        },
        {
          "q": "What are the types of virtual accounts used in India?",
          "a": "Three types: (1) Bank-issued VANs — assigned by banks like HDFC, ICICI, or Yes Bank as part of a cash management service; (2) Payment gateway VANs — issued by Razorpay, PayU, or Cashfree for NEFT collection; (3) NACH virtual accounts — used by NBFCs and lenders to receive EMI payments, where each borrower's mandate routes to a unique VAN. Each type has different API formats and different reconciliation events.",
          "article": "Virtual Account Reconciliation in India: How Auto-Matching Works",
          "url": "https://www.terra-insight.com/insights/virtual-account-reconciliation-india"
        },
        {
          "q": "What are the failure modes in virtual account reconciliation?",
          "a": "The main failure modes are: (1) customer pays from a different account than expected and the bank identifies the payer incorrectly; (2) customer pays an amount that does not match any open invoice (overpayment or underpayment); (3) the VAN webhook fails to reach the reconciliation system due to a network timeout; (4) multiple customers share a VAN due to a configuration error (this creates misattribution at scale). Each failure requires different resolution logic.",
          "article": "Virtual Account Reconciliation in India: How Auto-Matching Works",
          "url": "https://www.terra-insight.com/insights/virtual-account-reconciliation-india"
        },
        {
          "q": "How is TDS handled with virtual account payments?",
          "a": "When a client pays via VAN and deducts TDS, the VAN credit is the net amount (gross invoice minus TDS). The reconciliation system receives the VAN credit and must determine whether the shortfall from the invoice amount is due to TDS deduction or a partial payment. This determination requires either: (1) remittance advice from the client specifying TDS deduction, or (2) automated TDS detection based on the client's known TDS deduction pattern (section and rate).",
          "article": "Virtual Account Reconciliation in India: How Auto-Matching Works",
          "url": "https://www.terra-insight.com/insights/virtual-account-reconciliation-india"
        },
        {
          "q": "What is financial reconciliation in simple terms?",
          "a": "Financial reconciliation is the process of confirming that two sets of financial records agree — for example, that your bank statement balance matches your cash ledger, or that TDS shown in Form 26AS matches the TDS receivable in your books. In India, reconciliation must cover bank accounts, TDS deductions, GST credits, and platform settlements — each requiring separate matching logic.",
          "article": "What Is Financial Reconciliation? A Complete Guide for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-financial-reconciliation-india"
        },
        {
          "q": "How is reconciliation different in India compared to other countries?",
          "a": "India's reconciliation complexity comes from three tax-at-source mechanisms running simultaneously: TDS (deducted on payments received), GST (with ITC matching across GSTR-2A, GSTR-2B, and purchase register), and TCS (collected by e-commerce operators). Each creates a timing mismatch between the transaction date and the date the tax record appears in a government portal — requiring continuous reconciliation rather than a one-time match.",
          "article": "What Is Financial Reconciliation? A Complete Guide for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-financial-reconciliation-india"
        },
        {
          "q": "What happens if reconciliation is not done on time in India?",
          "a": "Unreconciled TDS results in lost credits that may not be claimable after the ITR filing deadline. Unreconciled GSTR-2B mismatches result in ITC reversals with 18% interest under Section 50 of the CGST Act. Bank reconciliation failures obscure the true cash position and can lead to incorrect financial statements — a statutory audit risk for companies under the Companies Act.",
          "article": "What Is Financial Reconciliation? A Complete Guide for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-financial-reconciliation-india"
        },
        {
          "q": "What is the difference between reconciliation and accounting?",
          "a": "Accounting records transactions (receipts, payments, invoices, expenses). Reconciliation confirms that those recorded transactions match an independent external source — a bank statement, a government portal (Form 26AS, GSTR-2B), or a counterparty's records. A journal entry creates a ledger balance; reconciliation verifies that ledger balance is accurate.",
          "article": "What Is Financial Reconciliation? A Complete Guide for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-financial-reconciliation-india"
        },
        {
          "q": "How long does financial reconciliation take for an Indian company with 3 bank accounts and 30 active TDS deductors?",
          "a": "Manual monthly reconciliation for 3 bank accounts and 30 TDS deductors typically takes 2–4 working days. Adding GST reconciliation (GSTR-2B vs purchase register) adds another 1–2 days. With automated matching, the matching phase compresses to under 4 hours — the remaining time is spent on exception review and resolution.",
          "article": "What Is Financial Reconciliation? A Complete Guide for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-financial-reconciliation-india"
        },
        {
          "q": "What is a reconciliation engine?",
          "a": "A reconciliation engine is a software component that automatically matches financial transactions across two or more data sources using configurable rules. It applies matching logic — exact match, tolerance-based match, pattern-based match — in multiple sequential passes, classifies unmatched items by exception type, and routes them to reviewers. It differs from a spreadsheet in that it can process hundreds of thousands of transactions in minutes and applies consistent logic without human intervention.",
          "article": "What Is a Reconciliation Engine? How It Differs from Spreadsheet Tools",
          "url": "https://www.terra-insight.com/insights/what-is-reconciliation-engine-india"
        },
        {
          "q": "How does a multi-pass matching engine work?",
          "a": "A multi-pass engine applies increasingly flexible matching criteria in sequence. Pass 1 attempts exact matches on primary reference fields (UTR, invoice number). Pass 2 applies tolerance-based matching for rounding differences (±₹1 or ±1%). Pass 3 applies pattern-based matching for known deduction types (TDS at 10% = 194J). Items unmatched after all passes become genuine exceptions requiring human review — a much smaller set than the full transaction volume.",
          "article": "What Is a Reconciliation Engine? How It Differs from Spreadsheet Tools",
          "url": "https://www.terra-insight.com/insights/what-is-reconciliation-engine-india"
        },
        {
          "q": "What is variance taxonomy in reconciliation?",
          "a": "Variance taxonomy is the classification system a reconciliation engine uses to describe why an item did not match. Common variance codes include: FEE_DEDUCTION (MDR or platform fee), TAX_DEDUCTION (TDS), TIMING_DIFFERENCE (amount correct but dates differ), AMOUNT_MISMATCH (genuine discrepancy), and ROUNDING (sub-rupee difference). A named variance is actionable; an unnamed exception requires investigation from scratch.",
          "article": "What Is a Reconciliation Engine? How It Differs from Spreadsheet Tools",
          "url": "https://www.terra-insight.com/insights/what-is-reconciliation-engine-india"
        },
        {
          "q": "When should an Indian company move from spreadsheets to a reconciliation engine?",
          "a": "The transition point is typically 500–800 monthly transactions, or when any single reconciliation type (bank, TDS, or GST) consistently takes more than 2 days per month. Below 300 monthly transactions, a well-structured spreadsheet remains viable. Above 1,000 transactions, spreadsheet-based reconciliation produces systematic errors that cost more to fix than the software investment.",
          "article": "What Is a Reconciliation Engine? How It Differs from Spreadsheet Tools",
          "url": "https://www.terra-insight.com/insights/what-is-reconciliation-engine-india"
        },
        {
          "q": "Does a reconciliation engine replace the ERP?",
          "a": "A reconciliation engine does not replace an ERP — it complements it. The ERP records transactions; the reconciliation engine verifies them against external sources (bank, TRACES, GSTN). Most ERPs have limited built-in reconciliation capability, especially for Indian-specific requirements like TDS section-level matching and GSTR-2B comparison. A reconciliation engine connects to the ERP via API or file export and handles the matching layer.",
          "article": "What Is a Reconciliation Engine? How It Differs from Spreadsheet Tools",
          "url": "https://www.terra-insight.com/insights/what-is-reconciliation-engine-india"
        },
        {
          "q": "Why is reconciliation harder in India than in other countries?",
          "a": "India has three simultaneous tax-at-source mechanisms that directly affect payment amounts: TDS (payer deducts before remitting), TCS (e-commerce operators collect before settling), and GST with ITC matching across government portals. Each creates a gap between the transaction amount and the received amount, requiring additional matching logic that generic accounting tools do not handle natively.",
          "article": "Why Reconciliation Is Different in India: TDS, GST, and Platform Complexity",
          "url": "https://www.terra-insight.com/insights/why-reconciliation-different-india"
        },
        {
          "q": "What is the TDS impact on payment reconciliation?",
          "a": "When a client pays an invoice of ₹1,00,000 for professional services under Section 194J, they deduct 10% TDS and remit ₹90,000. The bank credit is ₹90,000, the invoice is ₹1,00,000, and a TDS receivable of ₹10,000 should appear in Form 26AS on TRACES within 3–7 days of the deductor depositing the TDS challan. Matching all three — bank credit, invoice, and TRACES credit — is what makes Indian reconciliation structurally different.",
          "article": "Why Reconciliation Is Different in India: TDS, GST, and Platform Complexity",
          "url": "https://www.terra-insight.com/insights/why-reconciliation-different-india"
        },
        {
          "q": "How does GST create timing mismatches in reconciliation?",
          "a": "Under the GST framework, ITC can be claimed in GSTR-3B only to the extent it appears in GSTR-2B, which is generated on the 14th of each month based on suppliers' GSTR-1 filings for the prior month. A supplier who files late causes the buyer's ITC to appear one or two months after the invoice date — creating a persistent mismatch between the purchase register and GSTR-2B.",
          "article": "Why Reconciliation Is Different in India: TDS, GST, and Platform Complexity",
          "url": "https://www.terra-insight.com/insights/why-reconciliation-different-india"
        },
        {
          "q": "What is platform aggregation and why does it complicate reconciliation?",
          "a": "Platform aggregation means a single bank credit represents multiple underlying transactions. A Razorpay settlement of ₹5,23,477 might represent 312 individual orders, minus MDR on each, minus GST on MDR, minus TCS at 1% on the merchant's gross sales. Reconciling this credit requires unpacking the settlement statement line-by-line — not matching the bulk credit to a revenue figure.",
          "article": "Why Reconciliation Is Different in India: TDS, GST, and Platform Complexity",
          "url": "https://www.terra-insight.com/insights/why-reconciliation-different-india"
        },
        {
          "q": "What does reconciliation infrastructure mean versus reconciliation software?",
          "a": "Reconciliation software is a standalone tool for a specific matching task — bank reconciliation or TDS matching. Reconciliation infrastructure is a configurable platform that handles all matching types (TDS, GST, bank, NACH, platform settlements) through a shared engine with industry-specific presets. Infrastructure scales across transaction types without requiring a separate tool for each.",
          "article": "Why Reconciliation Is Different in India: TDS, GST, and Platform Complexity",
          "url": "https://www.terra-insight.com/insights/why-reconciliation-different-india"
        },
        {
          "q": "What is the deadline for GSTR-9 annual return filing?",
          "a": "GSTR-9 for a financial year is typically due by 31 December of the following year. For FY 2024-25, the due date is 31 December 2025. However, the GSTR-9 reconciliation process should begin in April after the FY close, not in December — starting early prevents last-minute ITC reversals and penalty exposure.",
          "article": "Year-End Reconciliation Guide for Indian Companies: FY Close Best Practices",
          "url": "https://www.terra-insight.com/insights/year-end-reconciliation-fy-close-india"
        },
        {
          "q": "How do I resolve TDS mismatches in Form 26AS before March 31?",
          "a": "Download your Form 26AS from the TRACES portal (tdscpc.gov.in) and match each TDS entry against your receivable ledger. For mismatches, identify whether the deductor filed an incorrect PAN, wrong amount, or wrong section code. Contact the deductor to file a correction return (Form 26QB/27A) before March 31 — corrections filed after year-end affect the current assessment year, not the prior one.",
          "article": "Year-End Reconciliation Guide for Indian Companies: FY Close Best Practices",
          "url": "https://www.terra-insight.com/insights/year-end-reconciliation-fy-close-india"
        },
        {
          "q": "What is the last date to claim ITC for FY 2024-25?",
          "a": "Input Tax Credit for invoices of FY 2024-25 can be claimed up to the earlier of: the due date of the September 2025 GSTR-3B return (typically 20 October 2025), or the date of filing the annual return GSTR-9 for FY 2024-25. Reconciliation of GSTR-2B against the purchase register must be completed before this deadline to avoid permanent ITC loss.",
          "article": "Year-End Reconciliation Guide for Indian Companies: FY Close Best Practices",
          "url": "https://www.terra-insight.com/insights/year-end-reconciliation-fy-close-india"
        },
        {
          "q": "What reconciliation tasks must be completed for statutory audit?",
          "a": "Statutory auditors under the Companies Act require: bank reconciliation statements for all accounts as at March 31, TDS receivable reconciled to Form 26AS, accounts receivable and payable confirmation of balances, fixed asset register reconciled to book value, and GSTR-2B vs purchase register reconciliation. Gaps in any of these typically result in audit observations.",
          "article": "Year-End Reconciliation Guide for Indian Companies: FY Close Best Practices",
          "url": "https://www.terra-insight.com/insights/year-end-reconciliation-fy-close-india"
        },
        {
          "q": "How long does year-end reconciliation take for a mid-size Indian company?",
          "a": "For a company with 5–10 bank accounts, 50+ active TDS deductors, and GST turnover above ₹5 crore, manual year-end reconciliation typically takes 10–15 working days. Automated matching with structured tooling compresses the matching phase to 1–2 days, leaving the team to focus on exception resolution and audit documentation.",
          "article": "Year-End Reconciliation Guide for Indian Companies: FY Close Best Practices",
          "url": "https://www.terra-insight.com/insights/year-end-reconciliation-fy-close-india"
        }
      ]
    },
    "bsa": {
      "label": "Bank Statement Analysis — TransactIQ",
      "faqs": [
        {
          "q": "Which bank statement signal is the strongest predictor of NBFC loan default in India?",
          "a": "NACH/EMI continuity is consistently the strongest predictor of repayment behaviour for NBFC loans in India. A borrower with 3 or more NACH returns in the prior 6 months defaults at materially higher rates than a borrower with a clean mandate execution record, even when the borrower's income and FOIR appear acceptable. NACH return codes visible in statement narrations — NACH-10 (insufficient funds), NACH-12 (account closed), RTNACH — capture delinquency that bureau data does not yet reflect, typically 60 to 90 days before a formal default registers.",
          "article": "Bank Statement Analysis Accuracy: Which Signals Matter Most for Indian Credit Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-accuracy-signals"
        },
        {
          "q": "How does income regularity scoring work in bank statement analysis?",
          "a": "Income regularity scoring measures the consistency of salary or business receipt credits over the statement period. For salaried borrowers, a regularity score tracks whether credits arrive within a ±3 day window of the expected date each month, whether amounts are within ±10% of the average, and whether the income source (employer narration) is consistent. For self-employed borrowers, regularity is scored differently — variance in monthly business receipts is expected, but a 3-month period with no receipts above ₹5,000 is a concern regardless of the statement average.",
          "article": "Bank Statement Analysis Accuracy: Which Signals Matter Most for Indian Credit Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-accuracy-signals"
        },
        {
          "q": "What is balance distribution analysis and why does it matter for credit risk?",
          "a": "Balance distribution analysis measures how account balances are spread across the month — particularly on the dates when NACH mandates typically execute (1st, 5th, and 15th of month). A borrower with a high average monthly balance but consistent low balance on these specific dates (below the EMI amount) will bounce mandates despite appearing financially healthy in aggregate metrics. This pattern is common among MSMEs who pay vendor obligations in bulk on specific dates, leaving the account temporarily depleted.",
          "article": "Bank Statement Analysis Accuracy: Which Signals Matter Most for Indian Credit Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-accuracy-signals"
        },
        {
          "q": "Why do PSU and co-operative bank statement formats reduce signal accuracy?",
          "a": "PSU and co-operative bank statements frequently use non-standard column layouts, abbreviated narration codes, and scanned PDFs that require OCR extraction. Three problems arise: (1) OCR introduces character errors in amount fields, leading to incorrect transaction values; (2) abbreviated NACH return codes (INS FND, A/C CL, RTN NAC) are not standardised across banks, causing signal misclassification; (3) narration truncation at 30 to 40 characters cuts off the instrument reference needed to distinguish an EMI debit from a utility payment. Each issue reduces signal confidence. A parser trained specifically on these bank formats handles them more accurately than a generic tool.",
          "article": "Bank Statement Analysis Accuracy: Which Signals Matter Most for Indian Credit Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-accuracy-signals"
        },
        {
          "q": "How many signals does a comprehensive bank statement analysis cover for Indian NBFC underwriting?",
          "a": "A comprehensive bank statement analysis for Indian NBFC underwriting covers 40+ engineered signals across 10 risk categories and 24 expense categories. Key signal families include: NACH/EMI continuity (3–6 months), income regularity score, average monthly balance on key dates, FOIR (existing and post-proposed-EMI), balance trend (12 months), PDF authenticity checks, round-trip transaction flags, risk word category hits (gambling, crypto, informal lending), salary consistency, and inward return frequency. The 40+ count reflects India-specific signals — NACH codes, UPI autopay patterns, and co-op bank narration normalisation — not covered by generic global tools.",
          "article": "Bank Statement Analysis Accuracy: Which Signals Matter Most for Indian Credit Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-accuracy-signals"
        },
        {
          "q": "What is the minimum bank statement period NBFCs require for credit underwriting?",
          "a": "Most Indian NBFCs require a minimum of 3 months for small-ticket loans below ₹1 lakh, 6 months for personal and business loans between ₹1 lakh and ₹10 lakh, and 12 months for MSME working capital and term loans above ₹10 lakh. RBI's MSME lending guidelines recommend cash-flow-based underwriting using a statement period that covers at least one complete business cycle — for seasonal businesses such as agriculture-linked MSMEs, this means 12 months.",
          "article": "Bank Statement Analysis in Credit Underwriting: How Indian NBFCs Use It",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-credit-underwriting-india"
        },
        {
          "q": "How is income classified from a bank statement for NBFC underwriting?",
          "a": "Income classification from bank statements involves categorising all credit entries into: salary credits (regular, same-day-each-month, from a single employer-coded NEFT/UPI), business receipts (RTGS/NEFT from multiple counterparties with business narrations), rental income (recurring credits from fixed payors), and other income (dividends, refunds, one-time receipts). Inter-account transfers and loan disbursals are excluded from income. Average monthly income is computed as the mean of classified credit totals across the statement period, excluding outlier months.",
          "article": "Bank Statement Analysis in Credit Underwriting: How Indian NBFCs Use It",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-credit-underwriting-india"
        },
        {
          "q": "What is NACH continuation and why does it matter for underwriting?",
          "a": "NACH continuation refers to the uninterrupted execution of NACH/ECS debit mandates — typically EMI payments — across the statement period. An active NACH mandate that has executed every month without a return code indicates that the borrower is servicing existing obligations. A mandate that returned (NACH-10 insufficient funds, NACH-12 account closed, or similar codes) in any of the prior 6 months is a delinquency signal. Lenders typically require NACH continuation for all active mandates over the 3 months immediately preceding the application date.",
          "article": "Bank Statement Analysis in Credit Underwriting: How Indian NBFCs Use It",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-credit-underwriting-india"
        },
        {
          "q": "How does round-trip detection work in bank statement underwriting?",
          "a": "Round-trip detection identifies credits that are followed by matching debits within 3 to 7 days — indicating that money was moved into the account temporarily to inflate the apparent balance or turnover. Common patterns include business owners transferring from a personal account to a current account on the last day of the month and transferring back on the 2nd or 3rd of the following month. Automated analysis flags entries where the credit amount matches a debit amount within a 7-day window and the counterparty accounts are linked to the applicant.",
          "article": "Bank Statement Analysis in Credit Underwriting: How Indian NBFCs Use It",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-credit-underwriting-india"
        },
        {
          "q": "Does bank statement analysis for MSME loans require a separate salary slip?",
          "a": "For salaried MSME owners or co-borrowers, bank statements with a consistent salary credit from a named employer (identifiable by NEFT narration prefix or NACH originator code) can substitute for a salary slip in many NBFC credit policies. The statement-derived salary must match at least 3 consecutive months with less than 10% variation. For self-employed MSME borrowers with no salary, bank statements serve as the primary income document — ITR and GST returns provide corroborating evidence but are not always available for informal-sector businesses.",
          "article": "Bank Statement Analysis in Credit Underwriting: How Indian NBFCs Use It",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-credit-underwriting-india"
        },
        {
          "q": "What bank statement period do NBFCs typically require for MSME loans?",
          "a": "Most NBFCs require a minimum of 6 months of bank statements for MSME working capital loans and 12 months for term loans above ₹10 lakh. For microfinance and small-ticket digital lending, 3 months is common. RBI's revised MSME lending guidelines encourage cash-flow-based underwriting, which means the statement period should cover at least two full business cycles — typically 12 months for seasonal businesses.",
          "article": "Bank Statement Analysis for NBFCs: Five Use Cases That Drive Underwriting Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-nbfc-use-cases"
        },
        {
          "q": "What is FOIR and how is it calculated from a bank statement?",
          "a": "FOIR (Fixed Obligation to Income Ratio) is the proportion of a borrower's monthly income that is committed to existing EMI obligations and fixed payments. From a bank statement, FOIR is calculated by identifying all recurring debit entries that match NACH/ECS/UPI autopay patterns and dividing their sum by the average monthly credit inflows (net of business-to-business receipts and transfers). RBI guidance for retail lending typically expects FOIR below 50–55% at the point of disbursement.",
          "article": "Bank Statement Analysis for NBFCs: Five Use Cases That Drive Underwriting Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-nbfc-use-cases"
        },
        {
          "q": "How does bank statement analysis help detect loan stacking in NBFC lending?",
          "a": "Loan stacking — where a borrower has taken multiple loans from different lenders simultaneously — is visible in bank statements through NACH debits originating from multiple NBFC or bank originators. Automated analysis flags accounts with 3 or more active NACH mandates across different financial institutions, cross-referenced against the borrower's income to compute FOIR overrun. This pattern is a leading indicator of stress; stacked borrowers default at materially higher rates.",
          "article": "Bank Statement Analysis for NBFCs: Five Use Cases That Drive Underwriting Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-nbfc-use-cases"
        },
        {
          "q": "Which bank statement signals predict NACH mandate bounce in NBFC lending?",
          "a": "The strongest predictors of NACH bounce are: (1) average monthly balance on mandate debit dates that is consistently below the EMI amount, (2) salary or income credits arriving 5 or more days after the typical NACH debit date, (3) prior NACH return codes (such as NACH-10 insufficient funds) visible in statement narrations, and (4) end-of-month balance depletion patterns where the account regularly drops below ₹500–1,000 before the next credit. These patterns together are more predictive than credit bureau scores for first-time borrowers.",
          "article": "Bank Statement Analysis for NBFCs: Five Use Cases That Drive Underwriting Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-nbfc-use-cases"
        },
        {
          "q": "Can bank statement analysis replace bureau checks for thin-file NBFC borrowers?",
          "a": "Bank statement analysis is complementary to bureau checks, not a replacement. For thin-file borrowers — first-time NBFC customers with limited bureau history — statements provide behavioral credit signals (income regularity, balance trends, bounce patterns) that bureaus cannot supply. RBI's account aggregator framework under the DIGI-Locker and NBFC norms makes consent-based statement access feasible, allowing lenders to run bureau and statement analysis in parallel and improve credit inclusion without relaxing underwriting standards.",
          "article": "Bank Statement Analysis for NBFCs: Five Use Cases That Drive Underwriting Decisions",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-nbfc-use-cases"
        },
        {
          "q": "Is bank statement analysis the same as a bank statement audit in India?",
          "a": "No. Bank statement analysis is an automated or manual extraction of credit signals — income, FOIR, bounce history, NACH continuity — used for lending decisions. It is completed in minutes to hours and has no statutory standing. A bank statement audit is a formal opinion by a Chartered Accountant on whether the statements presented reflect the true financial position, conducted under ICAI auditing standards, and takes days to weeks. Lenders use analysis for underwriting and auditors use audits for statutory compliance.",
          "article": "Bank Statement Analysis vs Bank Statement Audit: What Indian Lenders Need to Know",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-vs-bank-statement-audit"
        },
        {
          "q": "What legal standing does an automated bank statement analysis report have in India?",
          "a": "Automated bank statement analysis reports do not carry statutory standing under the Companies Act, Income Tax Act, or ICAI auditing standards. They are internal credit decision documents. However, they are legitimate evidence in NBFC credit files for RBI inspection purposes — as long as the analysis methodology is documented and the source statements are authenticated. The analysis supports the credit appraisal note (CAN) but does not replace it.",
          "article": "Bank Statement Analysis vs Bank Statement Audit: What Indian Lenders Need to Know",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-vs-bank-statement-audit"
        },
        {
          "q": "When is a bank statement audit required by law in India?",
          "a": "A formal bank statement audit is required when financial statements (of which bank balances are a component) are subject to statutory audit under the Companies Act 2013, when an NBFC undergoes an RBI inspection, or when income tax assessment proceedings require independent verification of bank balances under Section 131 or 133 of the Income Tax Act. For loan underwriting, a bank statement audit is not a legal requirement — lenders use analysis for credit decisions.",
          "article": "Bank Statement Analysis vs Bank Statement Audit: What Indian Lenders Need to Know",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-vs-bank-statement-audit"
        },
        {
          "q": "Can a CA's certificate on bank statements replace automated analysis for NBFC lending?",
          "a": "A CA certificate on bank statements verifies the authenticity and accuracy of reported balances and cash flows — it does not extract the 40+ credit signals (FOIR, NACH continuity, salary regularity, risk word flags) that drive underwriting decisions. Lenders typically require both: a CA certificate for balance verification on larger loans (above ₹25–50 lakh), and automated analysis for the credit signal extraction that informs pricing and tenure decisions.",
          "article": "Bank Statement Analysis vs Bank Statement Audit: What Indian Lenders Need to Know",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-vs-bank-statement-audit"
        },
        {
          "q": "How long does a bank statement audit take compared to automated analysis?",
          "a": "Automated bank statement analysis processes a 12-month PDF statement in under 5 minutes, producing a structured report with income classification, FOIR, bounce analysis, and risk flags. A bank statement audit by a CA firm typically takes 3 to 10 business days for a company with multiple bank accounts, involving physical statement verification, cash book reconciliation, and a formal opinion letter. The two processes serve different purposes and operate on different timelines.",
          "article": "Bank Statement Analysis vs Bank Statement Audit: What Indian Lenders Need to Know",
          "url": "https://www.terra-insight.com/insights/bank-statement-analysis-vs-bank-statement-audit"
        },
        {
          "q": "What is the first thing to check when reading a bank statement for credit risk?",
          "a": "The first check is PDF authenticity — whether the statement is an original bank-generated PDF or has been edited. Edited PDFs show inconsistent font sizes across table cells, broken character encoding in the narration column, or closing balances that do not equal opening balance plus net transactions for a given period. Most Indian banks embed a digital certificate in their PDF exports; a missing or invalid certificate is an immediate red flag. Statements from SBI, HDFC, ICICI, and Axis Bank are machine-generated PDFs — scanned or printed-and-rescanned PDFs of these require additional verification.",
          "article": "How to Read a Bank Statement for Credit Risk: A Guide for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/how-to-read-bank-statement-credit-risk"
        },
        {
          "q": "How do you compute FOIR from a bank statement?",
          "a": "FOIR (Fixed Obligation to Income Ratio) from a bank statement is computed as: (sum of all recurring debit entries matching NACH/ECS/UPI autopay patterns over 3 months, divided by 3) ÷ (average monthly classified income). Classified income excludes inter-account transfers, loan disbursals, and one-time receipts. The proposed new EMI is added to the numerator before comparing against the NBFC's FOIR threshold — typically 50% for retail lending and 55% for MSME lending.",
          "article": "How to Read a Bank Statement for Credit Risk: A Guide for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/how-to-read-bank-statement-credit-risk"
        },
        {
          "q": "How do you identify NACH bounces in a bank statement narration?",
          "a": "NACH bounces appear as debit reversal pairs in bank statements — a debit entry on the mandate execution date followed by a credit reversal 1 to 3 days later with a narration containing codes such as NACH-10 (insufficient funds), NACH-12 (account closed), RTNACH, or NPCI RTN. PSU bank statements often use abbreviated codes: INS FND (insufficient funds), A/C CL (account closed). For accounts with 3 or more bounces in a 6-month period, the pattern is a primary delinquency indicator regardless of current balance.",
          "article": "How to Read a Bank Statement for Credit Risk: A Guide for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/how-to-read-bank-statement-credit-risk"
        },
        {
          "q": "What are round-trip transactions and how do you spot them in a bank statement?",
          "a": "Round-trip transactions are credits followed by matching debits within 3 to 7 days, used to artificially inflate apparent monthly turnover or end-of-period balance. The pattern typically appears as a credit from a related party account (another account held by the same owner) on the last 2 to 3 days of a month, with a corresponding debit in the first 3 days of the following month. The simplest manual check: compare credit entries on the 28th–31st against debit entries on the 1st–5th of the next month. Amounts within ±5% of each other from the same counterparty are strong round-trip indicators.",
          "article": "How to Read a Bank Statement for Credit Risk: A Guide for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/how-to-read-bank-statement-credit-risk"
        },
        {
          "q": "What is the risk word category check in bank statement analysis?",
          "a": "Risk word category checks scan narration entries for terms associated with 10 defined risk categories: gambling (e.g., 'BETWAY', 'DREAM11' in large or frequent amounts), alcohol (recurring bulk purchases from liquor distributors), legal proceedings (court-ordered debits), crypto exchanges (WAZIRX, COINDCX), loan sharks (informal lender narrations), and others. The [Financial Intelligence Unit India](https://fiuindia.gov.in/) publishes suspicious transaction guidance that underpins these categories. A single high-value narration hit is not an automatic reject — frequency and proportion of income are the deciding factors.",
          "article": "How to Read a Bank Statement for Credit Risk: A Guide for Indian Lenders",
          "url": "https://www.terra-insight.com/insights/how-to-read-bank-statement-credit-risk"
        },
        {
          "q": "How long does manual bank statement review take per file in India?",
          "a": "Manual review of a 12-month bank statement for a MSME borrower typically takes 90 minutes to 3 hours for an experienced credit analyst — covering income classification, average balance calculation, EMI identification, and risk flag scanning. For PSU or co-operative bank statements with scanned or poorly formatted PDFs, add 30 to 60 minutes for manual data extraction. At 20 applications per week, this translates to 30 to 60 analyst hours weekly on statement review alone.",
          "article": "Manual vs Automated Bank Statement Review: What Changes for Indian Credit Teams",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-bank-statement-review"
        },
        {
          "q": "What signals do manual reviewers commonly miss in Indian bank statements?",
          "a": "The signals most frequently missed in manual review are: (1) NACH return narrations buried in mid-statement entries with non-standard bank codes, (2) round-trip transactions where money leaves and returns within 3 to 7 days to inflate closing balance, (3) salary credit irregularity when deposits arrive 2 to 4 days late due to festival or state holidays, (4) co-mingled personal and business expenses that inflate apparent business turnover. These patterns require systematic scanning across 3 to 6 months of data simultaneously — which manual review does not do reliably.",
          "article": "Manual vs Automated Bank Statement Review: What Changes for Indian Credit Teams",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-bank-statement-review"
        },
        {
          "q": "Does automated bank statement review work for PSU and co-operative bank PDFs?",
          "a": "Yes, but quality varies significantly by tool. PSU bank statements (SBI, Bank of Baroda, Canara Bank) and co-operative bank statements often use scanned PDFs, non-standard column headers, or regional language labels. A purpose-built Indian bank statement parser trained on 300+ format variants handles these with OCR fallback when digital extraction fails. Generic PDF parsers or Excel-based tools fail on these formats, which is why manual review has persisted for PSU borrowers even when automation is used for private bank statement files.",
          "article": "Manual vs Automated Bank Statement Review: What Changes for Indian Credit Teams",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-bank-statement-review"
        },
        {
          "q": "What is the accuracy difference between manual and automated bank statement review?",
          "a": "Studies on NBFC credit file audits indicate that manual review misses 15 to 25% of identifiable risk signals in a typical bank statement, primarily due to time pressure and format inconsistency. Automated review with a purpose-built tool consistently extracts 40+ signals per statement with documented methodology — providing both higher signal coverage and an audit trail that manual review cannot produce. The gap widens for statements from PSU or co-operative banks where format inconsistency slows manual extraction.",
          "article": "Manual vs Automated Bank Statement Review: What Changes for Indian Credit Teams",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-bank-statement-review"
        },
        {
          "q": "How does the Account Aggregator framework change bank statement review for NBFCs?",
          "a": "The Account Aggregator (AA) framework under Sahamati enables NBFCs to receive digitally verified bank statement data directly from the borrower's bank with consent, eliminating PDF submission entirely. AA-sourced data arrives in structured JSON format with provenance attestation, which automated review tools process faster and with higher accuracy than PDF parsing. For NBFCs using AA-sourced data, the manual vs automated distinction shifts — the question becomes which analytical tool extracts the most credit-relevant signals from the structured feed.",
          "article": "Manual vs Automated Bank Statement Review: What Changes for Indian Credit Teams",
          "url": "https://www.terra-insight.com/insights/manual-vs-automated-bank-statement-review"
        },
        {
          "q": "What is bank statement analysis and how is it used in Indian lending?",
          "a": "Bank statement analysis (BSA) is the systematic review of a borrower's transaction history to verify income, assess repayment capacity, and identify risk signals. Indian NBFCs and digital lenders use BSA as a primary underwriting input under RBI's digital lending guidelines, which require lenders to verify income and cash flow before sanctioning loans. A 3-to-6-month statement review is standard practice; some lenders extend to 12 months for MSME borrowers.",
          "article": "Bank Statement Analysis India: What Lenders and NBFCs Actually Check",
          "url": "https://www.terra-insight.com/insights/what-is-bank-statement-analysis-india"
        },
        {
          "q": "How does automated bank statement analysis differ from manual review?",
          "a": "Manual review of a single bank statement takes 2–3 hours at best, and analyst output varies depending on experience and workload. Automated analysis processes the same statement in minutes, applies consistent classification rules across 24 expense categories and 10 risk word groups, and flags tampered-PDF signals that a visual review would miss entirely. At 200+ applications per day — a common volume for mid-size digital lenders — manual review is not operationally viable.",
          "article": "Bank Statement Analysis India: What Lenders and NBFCs Actually Check",
          "url": "https://www.terra-insight.com/insights/what-is-bank-statement-analysis-india"
        },
        {
          "q": "Which Indian banks and statement formats does a bank statement analyser support?",
          "a": "A production-grade Indian bank statement analyser must cover PSU banks (SBI, PNB, Bank of Baroda), large private banks (HDFC, ICICI, Axis), new private banks (Kotak, IDFC First, IndusInd), small finance banks (AU, Equitas, Ujjivan), co-operative and regional rural banks, and foreign bank branches. Statement format heterogeneity is substantial — the same bank may issue PDF, CSV, or Excel exports with 300+ column-name variants across branches and core banking versions. Scanned and password-protected PDFs require separate OCR handling.",
          "article": "Bank Statement Analysis India: What Lenders and NBFCs Actually Check",
          "url": "https://www.terra-insight.com/insights/what-is-bank-statement-analysis-india"
        },
        {
          "q": "What credit signals does bank statement analysis produce for NBFC underwriting?",
          "a": "BSA produces three categories of signals. Income signals include salary credit consistency, business inflow regularity, and income-to-obligation ratios. Obligation signals track EMI debit patterns, NACH return counts, and bounce frequency by period. Risk signals surface gambling transactions, round-tripping patterns, salary-to-debit velocity anomalies, and exposure to predatory lending platforms. For MSME borrowers, 40+ engineered signals are extracted — none of which appear in CIBIL data.",
          "article": "Bank Statement Analysis India: What Lenders and NBFCs Actually Check",
          "url": "https://www.terra-insight.com/insights/what-is-bank-statement-analysis-india"
        },
        {
          "q": "How is bank statement analysis different from CIBIL scoring for MSME loans?",
          "a": "CIBIL scores measure repayment history on formal credit products already on the bureau. They cannot assess borrowers with thin or absent credit histories — which describes the majority of India's 63 million MSMEs competing for a share of the estimated ₹65-trillion MSME credit demand gap. Bank statement analysis surfaces cash flow, income patterns, and business transaction behaviour directly from the account record, making it the primary underwriting tool for thin-file and no-CIBIL borrowers.",
          "article": "Bank Statement Analysis India: What Lenders and NBFCs Actually Check",
          "url": "https://www.terra-insight.com/insights/what-is-bank-statement-analysis-india"
        }
      ]
    },
    "bsa-ocr": {
      "label": "Bank Statement OCR and Parsing",
      "faqs": [
        {
          "q": "Why don't Indian banks use a standard statement format?",
          "a": "The Reserve Bank of India has not mandated a uniform bank statement format. Each bank deploys its own core banking system — Finacle, Oracle FlexCube, TCS BaNCS, T24, or smaller regional packages — and each system generates its own statement layout. Within the same bank, different channels (app, desktop net banking, branch counter) often use different rendering engines with different column labels. There is no industry-wide agreement on what to call the debit column, the date column, or the balance column.",
          "article": "Bank Statement Column Variants in India: Why 300+ Format Patterns Exist",
          "url": "https://www.terra-insight.com/insights/bank-statement-column-variant-parsing"
        },
        {
          "q": "How many layout variants can a single bank have?",
          "a": "Large banks can have 3 to 5 active variants simultaneously. SBI has distinct layouts for YONO (mobile app), OnlineSBI (desktop), and branch-printed statements — at minimum three variants. HDFC Bank has separate formats for its net-banking PDF, its corporate banking portal, and older legacy exports. After bank mergers, the acquiring bank's statement may carry residual layout patterns from merged entities in accounts that were migrated rather than recreated. A parser handling SBI effectively must address at least three layout configurations.",
          "article": "Bank Statement Column Variants in India: Why 300+ Format Patterns Exist",
          "url": "https://www.terra-insight.com/insights/bank-statement-column-variant-parsing"
        },
        {
          "q": "What is the risk if a debit column is misidentified as a credit column?",
          "a": "Misidentifying debit and credit columns is a catastrophic parsing error. An income credit read as a debit inflates apparent expenses and deflates apparent income. An EMI debit read as a credit appears as income, making the applicant's financial position look better than it is. The balance chain verification step catches column swaps because the recomputed running balance will immediately diverge from the printed balance — but this means the statement produces a verification failure rather than incorrect data, which the credit team must then resolve.",
          "article": "Bank Statement Column Variants in India: Why 300+ Format Patterns Exist",
          "url": "https://www.terra-insight.com/insights/bank-statement-column-variant-parsing"
        },
        {
          "q": "What is the 'Value Date' vs 'Transaction Date' distinction and why does it matter?",
          "a": "Indian banks record two dates for many transactions: the transaction date (when the payment was initiated or received) and the value date (when the funds were actually credited or debited to the account). NEFT and RTGS payments frequently show a transaction date one day before the value date. Some banks print both dates; others print only one. A parser that misreads the value date column as the transaction date will classify certain transactions as occurring on bank holidays — which is a fraud signal for NEFT and RTGS, but not an actual transaction anomaly. The distinction between these two date fields matters for accurate holiday-date fraud detection.",
          "article": "Bank Statement Column Variants in India: Why 300+ Format Patterns Exist",
          "url": "https://www.terra-insight.com/insights/bank-statement-column-variant-parsing"
        },
        {
          "q": "What does the generic header-matching engine do when it encounters an unlisted column name?",
          "a": "The generic engine maintains a ranked match list for each column type. When a header cannot be matched to any variant in the library, the engine attempts positional inference: if the column appears in the position where a balance column is expected (rightmost column, monotonically changing values), it is tentatively classified as Balance. Positional inference is less reliable than header matching and its confidence is flagged in the processing output. Columns that cannot be classified by either method are left unassigned, and the rows that depend on that column produce incomplete transaction records.",
          "article": "Bank Statement Column Variants in India: Why 300+ Format Patterns Exist",
          "url": "https://www.terra-insight.com/insights/bank-statement-column-variant-parsing"
        },
        {
          "q": "What is the difference between digital PDF parsing and OCR for bank statements?",
          "a": "Digital PDFs downloaded from net banking already contain a machine-readable text layer — data can be extracted without OCR, typically in seconds. Scanned or photocopied statements have no text layer; the system must first convert pixel images to text using OCR before any transaction data can be structured. Indian lenders routinely receive both types in the same batch, often from the same applicant.",
          "article": "Bank Statement OCR India: How Lenders Process Scanned and Digital PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-ocr-india"
        },
        {
          "q": "Which Indian banks are supported by automated bank statement processing tools?",
          "a": "Coverage varies across vendors. Most tools offer dedicated parsers for the large private banks — HDFC, ICICI, Axis, Kotak. TransactIQ supports 34+ Indian banks with bank-specific parsers, including PSU banks (SBI, PNB, Canara, Union Bank), small finance banks (AU, Ujjivan, Equitas), and regional private banks. For banks outside the 34+, a generic fallback engine recognises 300+ column-name variants used across Indian banks, including co-operative and regional rural banks.",
          "article": "Bank Statement OCR India: How Lenders Process Scanned and Digital PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-ocr-india"
        },
        {
          "q": "How does bank statement OCR handle password-protected PDFs in India?",
          "a": "If the applicant provides the password during the application, the system uses it directly. For forgotten passwords, tools can attempt systematic derivation from information provided during KYC — common patterns include combinations of PAN number, registered mobile number, date of birth, and account holder name. These patterns cover the most common password formats used by Indian banks for net-banking statement downloads.",
          "article": "Bank Statement OCR India: How Lenders Process Scanned and Digital PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-ocr-india"
        },
        {
          "q": "What happens when a scanned bank statement is too degraded for OCR to read?",
          "a": "A well-implemented pipeline has two stages. The primary OCR engine processes the image after pre-processing (deskew, denoise, contrast normalisation). If the primary engine's confidence falls below an acceptable threshold — common for faded dot-matrix prints, camera photos taken at an angle, or photocopies of photocopies — a premium cloud OCR service processes the document as a fallback. This two-stage approach handles the range of scan quality seen in PSU and co-operative bank submissions from tier-2 and tier-3 cities.",
          "article": "Bank Statement OCR India: How Lenders Process Scanned and Digital PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-ocr-india"
        },
        {
          "q": "What RBI compliance requirements apply to NBFCs using bank statement OCR tools?",
          "a": "RBI's Digital Lending Guidelines (2022, updated 2023) require that customer financial data accessed by a lending service provider be consent-based, stored only for the stated credit assessment purpose, and kept within India's data boundary. NBFCs must ensure their BSA vendor agreements address data localisation, processing purpose limitation, DPDP Act 2023 obligations, and provide an audit trail for regulator-directed reviews. These are due-diligence requirements that should be part of any vendor evaluation, not just a post-selection check.",
          "article": "Bank Statement OCR India: How Lenders Process Scanned and Digital PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-ocr-india"
        },
        {
          "q": "What are the three types of PDF bank statements Indian lenders encounter?",
          "a": "The three types are: (1) native digital PDFs, downloaded directly from net banking, where the transaction text is already encoded in the PDF and can be extracted without OCR — these are the cleanest and fastest to parse; (2) scanned PDFs, where a physical statement has been photocopied or photographed and converted to PDF, containing only image data that requires OCR to extract; and (3) hybrid or mixed PDFs, where some pages are native text and others are scanned images, often arising when an applicant combines multiple documents into one PDF using a consumer tool.",
          "article": "PDF Bank Statement Parsing in India: How Structured Data Is Extracted from PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-pdf-parsing-india"
        },
        {
          "q": "Why do Indian bank statements use different number formatting than international standards?",
          "a": "Indian number formatting follows the lakh-crore system: 1,00,000 (one lakh) rather than 100,000, and 1,00,00,000 (one crore) rather than 10,000,000. Commas are placed differently from the international grouping system. A general-purpose PDF parser or international financial data tool that expects standard three-digit grouping will misread Indian amounts — treating 1,00,000 as 100,000 is a 10x error that breaks every balance calculation downstream. India-specific parsers must handle both comma-grouping conventions because not all Indian banks use the lakh system in their PDFs.",
          "article": "PDF Bank Statement Parsing in India: How Structured Data Is Extracted from PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-pdf-parsing-india"
        },
        {
          "q": "What makes UPI and NACH narration strings in Indian bank statements different from Western bank narrations?",
          "a": "UPI narrations typically follow patterns like 'UPI/[VPA or app name]/[merchant name]/[UPI reference ID]' — long alphanumeric strings where the useful signal is the merchant or counterparty name embedded in a fixed position. NACH narrations carry the mandate registration reference, the sponsor bank code, and the utility or lender name. IMPS narrations carry the sender's account's remitter reference. These patterns are defined by NPCI rails and are India-specific — no international parser has reference data to extract counterparty names from Indian payment rail narrations.",
          "article": "PDF Bank Statement Parsing in India: How Structured Data Is Extracted from PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-pdf-parsing-india"
        },
        {
          "q": "How does a bank-specific parser differ from the generic 300+ column variant fallback?",
          "a": "A bank-specific parser has hard-coded knowledge of a particular bank's column layout, date format, narration patterns, and page structure. It can extract data reliably even when formatting is unusual or column positions vary across pages. The generic fallback identifies column headers by matching against a list of 300+ known column-name variants used across Indian banks, then extracts data based on identified column positions. It handles unknown banks adequately for transaction tables, but may miss bank-specific narration codes that are needed for payment channel classification and income categorisation.",
          "article": "PDF Bank Statement Parsing in India: How Structured Data Is Extracted from PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-pdf-parsing-india"
        },
        {
          "q": "What is a hybrid PDF and how is it handled differently from a pure scan?",
          "a": "A hybrid PDF has some pages with native text layers and other pages that are scanned images — typically arising when an applicant merges a net-banking export with a scanned additional page, or when a multi-page statement was partially re-scanned. The parser must assess each page independently: native text pages are processed without OCR; image-only pages go through the OCR pipeline. The extracted data from both page types is then merged into a single transaction table. Hybrid PDFs are more common than pure scans in the overall submission mix.",
          "article": "PDF Bank Statement Parsing in India: How Structured Data Is Extracted from PDFs",
          "url": "https://www.terra-insight.com/insights/bank-statement-pdf-parsing-india"
        },
        {
          "q": "How many co-operative banks and RRBs operate in India and why does this matter for parsers?",
          "a": "India has over 1,500 urban co-operative banks and 43 Regional Rural Banks as of 2024. This is not a long-tail problem — co-operative banks collectively hold over ₹12 lakh crore in deposits and serve tens of millions of customers, many of whom are NBFC borrowers. No centralised core banking standard applies across these institutions. Each bank may run its own software or a localised deployment of a generic cooperative banking package. The result is that no two co-operative bank statement formats are identical.",
          "article": "Co-operative and RRB Bank Statement OCR: The Last-Mile Parsing Challenge",
          "url": "https://www.terra-insight.com/insights/co-operative-bank-statement-ocr"
        },
        {
          "q": "What makes RRB and co-operative bank PDFs harder to parse than PSU bank PDFs?",
          "a": "PSU banks have at least deployed named core banking systems (Finacle, BaNCS, FlexCube) with documented statement formats. Most co-operative banks use smaller, less-documented software packages or generate statements through Microsoft Excel or Word templates. Branch-generated PDFs frequently lack consistent column headers. Some include handwritten account summaries on a separate sheet scanned alongside the printed statement. Teller stamps, correction marks, and account officer signatures overlapping transaction rows add OCR noise that is absent from PSU or private bank PDFs.",
          "article": "Co-operative and RRB Bank Statement OCR: The Last-Mile Parsing Challenge",
          "url": "https://www.terra-insight.com/insights/co-operative-bank-statement-ocr"
        },
        {
          "q": "How does the generic column-variant fallback engine handle co-operative bank statements?",
          "a": "The generic fallback engine attempts to identify the transaction table by matching column headers against a library of 300+ known column-name variants used across Indian banks. For co-operative bank statements with legible printed headers, this produces a reasonable transaction extraction. Where the fallback degrades is on narration classification — co-operative bank narrations for NACH, ECS, and local clearing transactions follow local patterns not present in the variant library, so payment channel classification defaults to 'Other' for a larger share of rows than with dedicated parsers.",
          "article": "Co-operative and RRB Bank Statement OCR: The Last-Mile Parsing Challenge",
          "url": "https://www.terra-insight.com/insights/co-operative-bank-statement-ocr"
        },
        {
          "q": "What does a handwritten supplement page in a co-operative bank statement contain and how is it handled?",
          "a": "Some co-operative banks append a handwritten page that summarises the account holder's name, account number, and balance certificate stamp — a legacy practice from pre-core-banking operations that persists in certain smaller societies. These pages are recognised as non-transaction pages during parsing and excluded from the transaction table extraction. The stamp and signature fields are not processed for data. If the handwritten page contains additional transactions not in the printed table, those are outside automated extraction scope and are flagged for manual review.",
          "article": "Co-operative and RRB Bank Statement OCR: The Last-Mile Parsing Challenge",
          "url": "https://www.terra-insight.com/insights/co-operative-bank-statement-ocr"
        },
        {
          "q": "Is it possible to build a dedicated parser for a specific co-operative bank?",
          "a": "Yes, but the economics differ from building a dedicated parser for a large PSU or private bank. A dedicated co-operative bank parser is justified when the lender's portfolio has a significant concentration of applicants from that specific institution — for example, a state-level NBFC where 30% of applications come from a single large urban co-operative bank. For smaller co-operative banks where submission volumes are single digits per month, the generic fallback is more practical than a dedicated parser that would be used infrequently.",
          "article": "Co-operative and RRB Bank Statement OCR: The Last-Mile Parsing Challenge",
          "url": "https://www.terra-insight.com/insights/co-operative-bank-statement-ocr"
        },
        {
          "q": "Why do loan applicants submit multiple overlapping bank statement PDFs?",
          "a": "Several factors produce overlapping submissions. Applicants sometimes misread the lender's requirement and submit both a 6-month statement and a separate 3-month statement, not realising they cover the same period. Agents in the field collect whatever statements the applicant has downloaded, which may include partial periods from different sessions. Some applicants download monthly statements sequentially rather than a single 6-month or 12-month export. The result is a set of PDFs that together cover the required period but with substantial overlap between individual files.",
          "article": "Multi-Statement Bank Statement Upload: How Deduplication and Period Merging Work",
          "url": "https://www.terra-insight.com/insights/multi-statement-upload-reconciliation"
        },
        {
          "q": "How does transaction deduplication work across overlapping statement periods?",
          "a": "Deduplication identifies transactions that appear in more than one uploaded PDF. The primary matching key is the combination of transaction date, debit or credit amount, and closing balance for that row. When two rows across different PDFs share all three values, one instance is retained and the duplicate is dropped. The merged transaction list is then sorted into strict chronological order and the balance chain is verified — the retained closing balance for each transaction must equal the prior row's closing balance plus or minus the transaction amount.",
          "article": "Multi-Statement Bank Statement Upload: How Deduplication and Period Merging Work",
          "url": "https://www.terra-insight.com/insights/multi-statement-upload-reconciliation"
        },
        {
          "q": "What happens when the same transaction appears with slightly different narration in two statements?",
          "a": "Indian bank statement narrations are sometimes truncated differently depending on the export channel. A UPI transaction narration that reads 'UPI/PHONEPE/ZOMATO INDIA PRIVATE LIM' in a 6-month export may appear as 'UPI/PHONEPE/ZOMATO INDIA PR' in a monthly export because the monthly export has a shorter narration field. The deduplication logic does not rely on narration matching — it uses date, amount, and balance as primary keys. A narration mismatch between two rows that match on all three numeric fields is not treated as a different transaction.",
          "article": "Multi-Statement Bank Statement Upload: How Deduplication and Period Merging Work",
          "url": "https://www.terra-insight.com/insights/multi-statement-upload-reconciliation"
        },
        {
          "q": "How does the system handle statements printed in reverse chronological order?",
          "a": "Some Indian banks — particularly certain PSU bank branches — print statements with the most recent transaction first and the oldest last. Before deduplication, each uploaded PDF is assessed for sort order. Reverse-sorted PDFs are flipped to chronological order before the merge. This matters because the balance chain check — verifying that each row's closing balance follows mathematically from the prior row — will fail on a reverse-sorted statement if the order correction is not applied first.",
          "article": "Multi-Statement Bank Statement Upload: How Deduplication and Period Merging Work",
          "url": "https://www.terra-insight.com/insights/multi-statement-upload-reconciliation"
        },
        {
          "q": "What is the output of a multi-statement merge and how is it different from processing each PDF separately?",
          "a": "The merged output is a single transaction list covering the full period across all uploaded PDFs, with duplicates removed, chronological order enforced, and the balance chain verified end to end. Separate processing would produce multiple reports with inflated totals — the same salary credit counted two or three times, the same EMI debit appearing in multiple months. The merged view produces accurate monthly income, accurate FOIR, and accurate fraud signals because each transaction is represented exactly once.",
          "article": "Multi-Statement Bank Statement Upload: How Deduplication and Period Merging Work",
          "url": "https://www.terra-insight.com/insights/multi-statement-upload-reconciliation"
        },
        {
          "q": "Why do Indian banks password-protect bank statement PDFs?",
          "a": "Most large Indian private sector banks password-protect net-banking PDF downloads as a security measure to prevent unauthorised access to customer financial data. The practice aligns with RBI's KYC and account security guidelines. HDFC Bank, ICICI Bank, Axis Bank, Kotak, and Yes Bank all apply PDF password protection by default. The password is typically a deterministic derivation from customer data — name, date of birth, PAN, or account number — rather than a user-set passphrase.",
          "article": "Password-Protected Bank Statement PDFs: How Indian Lenders Handle Them",
          "url": "https://www.terra-insight.com/insights/password-protected-bank-statement-india"
        },
        {
          "q": "What is a consent-based password collection workflow for loan applications?",
          "a": "In a consent-based workflow, the loan applicant explicitly shares their bank statement password with the lender's agent or inputs it directly into a secure form during the application process. The customer is informed that the password is required only to unlock the statement for underwriting purposes. The password is used transiently and is not stored beyond the document processing stage. This approach is the primary collection method and avoids the need for any password derivation.",
          "article": "Password-Protected Bank Statement PDFs: How Indian Lenders Handle Them",
          "url": "https://www.terra-insight.com/insights/password-protected-bank-statement-india"
        },
        {
          "q": "What happens when a bank statement password fails and the applicant cannot provide it?",
          "a": "If the customer-supplied password is incorrect and the applicant cannot recall the correct one, the parser attempts a set of derived candidate passwords based on publicly documented bank-specific formats (such as the first four characters of the customer's name combined with their date of birth in DDMM format for certain banks). If all candidates fail, the system returns a clear failure status. The credit team then requests a fresh statement download from the applicant or asks the applicant to regenerate the PDF with password protection disabled.",
          "article": "Password-Protected Bank Statement PDFs: How Indian Lenders Handle Them",
          "url": "https://www.terra-insight.com/insights/password-protected-bank-statement-india"
        },
        {
          "q": "Which Indian banks use which password formats for PDF statements?",
          "a": "Password formats for Indian bank statement PDFs are publicly documented. ICICI Bank statements use the first four characters of the account holder's name (uppercase) followed by the date of birth in DDMMYYYY format. HDFC Bank uses the customer's date of birth in DDMMYYYY format. Axis Bank uses the registered mobile number's last four digits combined with the date of birth. Kotak uses the account holder's date of birth in DDMMYYYY. These formats are disclosed in each bank's net-banking help documentation and are widely referenced in financial services.",
          "article": "Password-Protected Bank Statement PDFs: How Indian Lenders Handle Them",
          "url": "https://www.terra-insight.com/insights/password-protected-bank-statement-india"
        },
        {
          "q": "Is there a privacy or compliance concern with derived-password attempts?",
          "a": "The derived-password approach uses only information the customer has already provided in the loan application — name, PAN, date of birth, phone number. No external lookup or brute-force scanning is involved. The approach is equivalent to the applicant providing a limited set of candidates based on their own data. Under the Digital Personal Data Protection Act 2023 (DPDP Act), the customer's consent to process their bank statement for underwriting covers this step, provided the data processing purpose is clearly disclosed.",
          "article": "Password-Protected Bank Statement PDFs: How Indian Lenders Handle Them",
          "url": "https://www.terra-insight.com/insights/password-protected-bank-statement-india"
        },
        {
          "q": "Which PSU banks are hardest to parse and why?",
          "a": "SBI is the highest-volume PSU bank for loan applications but has the widest statement format variation — YONO app PDFs, OnlineSBI net-banking PDFs, and branch-printed statements all have different column layouts and date formats. PNB statements carry residual format inconsistencies from the 2020 merger with Oriental Bank of Commerce and United Bank of India. Bank of Baroda shows three distinct narration patterns corresponding to legacy BoB, Vijaya Bank, and Dena Bank customer segments. Each requires separate parser logic.",
          "article": "PSU Bank Statement OCR Challenges: Why Public Sector Statements Need Dedicated Parsers",
          "url": "https://www.terra-insight.com/insights/psb-bank-statement-ocr-challenges"
        },
        {
          "q": "What narration inconsistencies did the 2019–2020 bank mergers create?",
          "a": "The six PSU bank mergers between 2019 and 2020 consolidated 10 banks into 4. Customers from merged entities (OBC, UBI, Vijaya, Dena, Andhra, Syndicate, Corporation Bank) were migrated to the acquiring bank's systems, but legacy narration prefixes were not always normalised. A PNB statement for a former OBC customer may carry OBC-format NEFT/NACH narration codes for years after migration. Parsers must recognise the full set of legacy prefixes for each merged entity, not just the current bank's standard format.",
          "article": "PSU Bank Statement OCR Challenges: Why Public Sector Statements Need Dedicated Parsers",
          "url": "https://www.terra-insight.com/insights/psb-bank-statement-ocr-challenges"
        },
        {
          "q": "How are YONO and OnlineSBI statement formats different?",
          "a": "YONO (the SBI mobile app) generates PDFs through a different rendering pipeline than OnlineSBI (the desktop net-banking portal). Column headers, date formatting, and page layout differ between the two. YONO statements typically use a more compact layout with abbreviated column names. OnlineSBI statements use a wider table with more explicit column labels. Branch-printed SBI statements add a third format variation. A parser tuned to OnlineSBI will misread YONO statements and vice versa.",
          "article": "PSU Bank Statement OCR Challenges: Why Public Sector Statements Need Dedicated Parsers",
          "url": "https://www.terra-insight.com/insights/psb-bank-statement-ocr-challenges"
        },
        {
          "q": "Why do PSU bank customers in tier-2 and tier-3 cities submit more scanned statements?",
          "a": "PSU banks — particularly SBI, Bank of India, and Central Bank of India — have far larger branch footprints in rural and semi-urban areas than private banks. Many customers in these areas use branch counter services rather than net banking, and their statements are printed at the branch counter and then photocopied or scanned before submission to a lender. Private banks' customer bases are more concentrated in urban centres where net banking and app-based statement downloads are the norm.",
          "article": "PSU Bank Statement OCR Challenges: Why Public Sector Statements Need Dedicated Parsers",
          "url": "https://www.terra-insight.com/insights/psb-bank-statement-ocr-challenges"
        },
        {
          "q": "Does a generic column-variant fallback engine handle PSU bank statements adequately?",
          "a": "For straightforward PSU bank digital PDFs, a generic fallback that recognises common column-name variants can parse the transaction table. Where it fails is on narration interpretation: PSU bank narrations for NACH, NEFT, and RTGS transactions carry bank-specific prefix patterns (e.g., 'BY TRANSFER-INWARD NEFT-HDFC0000123-SBI123456789' vs 'NEFT CR-HDFC0000123') that a generic parser cannot classify by payment channel without bank-specific knowledge. Income classification and fraud signal accuracy both suffer on generic fallback paths.",
          "article": "PSU Bank Statement OCR Challenges: Why Public Sector Statements Need Dedicated Parsers",
          "url": "https://www.terra-insight.com/insights/psb-bank-statement-ocr-challenges"
        },
        {
          "q": "Why are so many bank statements in India submitted as scanned images rather than digital PDFs?",
          "a": "A significant share of Indian bank customers, particularly in tier-2 and tier-3 cities, access their accounts through branch counters rather than net banking. Branch-printed statements are often photocopied or scanned before submission to a lender. PSU banks such as SBI, Bank of Baroda, and PNB have large branch networks where counter-printed statements are the norm. Co-operative banks and Regional Rural Banks (RRBs) frequently lack net banking portals, making physical statement submission the only available route.",
          "article": "Scanned Bank Statement OCR in India: How Lenders Handle Degraded PDFs",
          "url": "https://www.terra-insight.com/insights/scanned-bank-statement-ocr-india"
        },
        {
          "q": "What image quality problems make scanned Indian bank statements hard to parse?",
          "a": "The most common issues are faded ink (particularly from dot-matrix branch printers), skewed scan angles, low resolution from mobile phone cameras, watermarks or stamps overlapping transaction rows, and partial page cuts where the scanner misses the edge columns. Multi-page statements with inconsistent brightness across pages are also common. These problems compound when a statement is photocopied more than once before being scanned — each generation adds noise.",
          "article": "Scanned Bank Statement OCR in India: How Lenders Handle Degraded PDFs",
          "url": "https://www.terra-insight.com/insights/scanned-bank-statement-ocr-india"
        },
        {
          "q": "What is a premium cloud OCR fallback and when does it apply?",
          "a": "When an automated OCR pipeline fails to extract transaction data at sufficient confidence — typically due to very low resolution, heavy background noise, or severe skew — the document is routed to a premium cloud OCR service that applies more compute-intensive image enhancement before extraction. This fallback adds processing time but avoids returning an empty or partially parsed result, which would require the credit team to manually re-enter data.",
          "article": "Scanned Bank Statement OCR in India: How Lenders Handle Degraded PDFs",
          "url": "https://www.terra-insight.com/insights/scanned-bank-statement-ocr-india"
        },
        {
          "q": "Which Indian banks most commonly produce scanned statements that need OCR?",
          "a": "Co-operative banks, Regional Rural Banks, district co-operative banks, and smaller urban cooperative societies routinely produce statements via branch counter printers. Among PSU banks, tier-2 and tier-3 branches of SBI, PNB, Bank of India, and Bank of Maharashtra are common sources of low-quality PDFs. Private banks (HDFC, ICICI, Axis) overwhelmingly provide digital net-banking PDFs that do not require OCR at all.",
          "article": "Scanned Bank Statement OCR in India: How Lenders Handle Degraded PDFs",
          "url": "https://www.terra-insight.com/insights/scanned-bank-statement-ocr-india"
        },
        {
          "q": "Does OCR accuracy vary between transaction fields on the same statement?",
          "a": "Yes. Date columns and balance columns tend to parse more reliably because their formats are structured and limited in character set. Narration fields — which carry UPI reference strings, NEFT remarks, and free-text descriptions — are more prone to OCR errors because they contain alphanumeric strings with no predictable pattern. Post-OCR validation checks balance chain consistency to catch numeric extraction errors that visual OCR confidence scores would miss.",
          "article": "Scanned Bank Statement OCR in India: How Lenders Handle Degraded PDFs",
          "url": "https://www.terra-insight.com/insights/scanned-bank-statement-ocr-india"
        }
      ]
    },
    "hospitality": {
      "label": "Hotel and Hospitality Reconciliation",
      "faqs": [
        {
          "q": "Is GST payable on a banquet advance receipt?",
          "a": "Yes. Under Section 13 of the CGST Act, the time of supply for services is the earlier of invoice date or payment receipt. When a hotel receives an advance for a banquet booking, GST becomes payable on the advance in the month of receipt at 18%. A receipt voucher is issued, and the tax is reported in GSTR-1 as an advance. When the event is finally consumed and the tax invoice issued, the advance and its GST are adjusted against the final invoice through the GSTR-1 advance-adjustment table.",
          "article": "Banquet Event Advance Reconciliation: Contract to Final Folio in India",
          "url": "https://www.terra-insight.com/insights/banquet-event-advance-reconciliation"
        },
        {
          "q": "What is the typical advance percentage for an Indian banquet contract?",
          "a": "Industry practice runs 30 to 50% of the contract value as a confirmation advance, with the balance due before or on the event date. Premium properties and peak-season weddings often demand a higher first instalment and a second instalment 30 to 60 days before the event. Cancellation slabs typically forfeit the first instalment if cancelled inside 90 days, with a higher forfeit or full retention inside 30 days.",
          "article": "Banquet Event Advance Reconciliation: Contract to Final Folio in India",
          "url": "https://www.terra-insight.com/insights/banquet-event-advance-reconciliation"
        },
        {
          "q": "How is a banquet final folio reconciled to the original contract?",
          "a": "The contract carries the hall hire, menu rate per cover, expected covers, decor, AV, and bar — each as a separate line. The final folio is built from actual consumption: hall hire as contracted, menu at actual covers served (subject to a guarantee minimum), decor as quoted, bar at actual consumption. The reconciliation matches each line to its source — F&B BEO for menu, banquet ops for hall, vendor pass-through for decor — and clears the advance against the final invoice. Variances are addressed before settlement.",
          "article": "Banquet Event Advance Reconciliation: Contract to Final Folio in India",
          "url": "https://www.terra-insight.com/insights/banquet-event-advance-reconciliation"
        },
        {
          "q": "What happens when an event is cancelled after advance receipt?",
          "a": "If the contract permits forfeit, the advance is retained as cancellation revenue. The GST treatment depends on whether the forfeit is consideration for a supply or a liquidated damage. Where the hotel issues a tax invoice for the forfeit, GST applies; where the forfeit is purely a deposit retained without supply, the advance GST may need to be claimed back through a refund voucher and a credit note adjustment in GSTR-1, depending on contract construction. Most hotels treat forfeits as taxable supply with 18% GST.",
          "article": "Banquet Event Advance Reconciliation: Contract to Final Folio in India",
          "url": "https://www.terra-insight.com/insights/banquet-event-advance-reconciliation"
        },
        {
          "q": "How does the PMS advance-deposit ledger fit into the reconciliation?",
          "a": "The PMS advance-deposit ledger holds every confirmed advance against an event ID, with the receipt voucher reference, GST charged, and the bank or card credit. At event close, the deposit ledger is debited and the final folio credited for the same amount, leaving zero balance on the event. Open balances after event close indicate either an unbilled element (decor not yet captured) or a refund pending (excess advance over actual consumption).",
          "article": "Banquet Event Advance Reconciliation: Contract to Final Folio in India",
          "url": "https://www.terra-insight.com/insights/banquet-event-advance-reconciliation"
        },
        {
          "q": "What commission does Booking.com charge Indian hotels?",
          "a": "Booking.com's commission for Indian properties typically ranges from 15% to 18% on a standard contract, with Genius programme participation, Preferred Partner placement, and Visibility Booster opt-ins each adding incremental percentage points. The commission is billed by Booking.com B.V. (Netherlands) on a monthly invoice raised in INR or EUR depending on contract terms. Boutique hotels and chains with negotiated terms may sit below 15%, while properties opting into multiple visibility programmes can exceed 20% blended.",
          "article": "Booking.com Hotel Settlement Reconciliation in India: Commission, RCM GST, and Forex Variance",
          "url": "https://www.terra-insight.com/insights/booking-com-hotel-settlement-reconciliation"
        },
        {
          "q": "How is GST applied on Booking.com commission to an Indian hotel?",
          "a": "Because Booking.com B.V. is a non-resident supplier of online intermediary services, the commission is an import of service for the Indian hotel. Under Section 9(3) of the CGST Act read with the IGST Act, the hotel must pay 18% IGST under reverse charge mechanism (RCM), self-invoice for the supply, and claim the same 18% as ITC subject to eligibility. The Booking.com invoice itself does not carry GST. Missing the RCM self-invoice and corresponding GSTR-3B Table 3.1(d) entry is a recurring audit finding for properties accepting OTA traffic from foreign-entity OTAs.",
          "article": "Booking.com Hotel Settlement Reconciliation in India: Commission, RCM GST, and Forex Variance",
          "url": "https://www.terra-insight.com/insights/booking-com-hotel-settlement-reconciliation"
        },
        {
          "q": "How does the Booking.com virtual-card payout option affect reconciliation?",
          "a": "Booking.com offers two payment models. Under the standard model the hotel collects payment from the guest at check-out, then receives a Booking.com invoice for commission and pays it. Under the virtual-card model Booking.com issues a one-time virtual card for each booking that the hotel charges at check-in, and Booking.com later raises the commission invoice. The virtual-card route shifts cash-flow timing and brings card-network MDR into the picture. Reconciliation must distinguish virtual-card bookings from collect-at-property bookings because the gross room revenue, MDR, and commission appear on different ledgers.",
          "article": "Booking.com Hotel Settlement Reconciliation in India: Commission, RCM GST, and Forex Variance",
          "url": "https://www.terra-insight.com/insights/booking-com-hotel-settlement-reconciliation"
        },
        {
          "q": "How is forex variance handled on Booking.com commission paid in EUR?",
          "a": "If the Booking.com invoice is denominated in EUR, the hotel books commission expense at the RBI reference rate on invoice date and settles at the actual rupee rate on payment date. The difference is forex gain or loss recognised in the period of settlement under Ind AS 21 or AS 11. For RCM IGST purposes the rupee value at invoice date is used for the 18% IGST liability — subsequent forex movement does not change the IGST already paid. Reconciliation must keep the invoice-date and payment-date rupee values separate to avoid double-counting forex variance into either ITC or expense.",
          "article": "Booking.com Hotel Settlement Reconciliation in India: Commission, RCM GST, and Forex Variance",
          "url": "https://www.terra-insight.com/insights/booking-com-hotel-settlement-reconciliation"
        },
        {
          "q": "What is the place of supply for a foreign-entity OTA booking made by an Indian guest?",
          "a": "For the room night supplied by the hotel to the guest, place of supply is the hotel's location under Section 12(3) of the IGST Act — this does not change because the booking flowed through Booking.com. For the commission service supplied by Booking.com B.V. to the hotel, place of supply under Section 13(2) is the location of the recipient (the hotel in India) — which is what triggers the RCM IGST liability. The two flows are taxed independently and reported in different schedules of GSTR-1 and GSTR-3B.",
          "article": "Booking.com Hotel Settlement Reconciliation in India: Commission, RCM GST, and Forex Variance",
          "url": "https://www.terra-insight.com/insights/booking-com-hotel-settlement-reconciliation"
        },
        {
          "q": "Are Goibibo and MakeMyTrip settlements the same after the merger?",
          "a": "Goibibo is now part of MMT Group following the 2017 merger but operates as a distinct OTA brand with its own contracts, commission rates, and settlement file format. While back-office consolidation has aligned some processes, hotels typically receive separate settlement files for Goibibo and MakeMyTrip bookings and must reconcile each independently. Commission rates on Goibibo are often calibrated for the price-sensitive segment and can differ from MMT B2C rates on the same property. Some chains have negotiated joint contracts that consolidate billing, but file-level reconciliation per OTA remains the conservative approach for audit purposes.",
          "article": "Goibibo and Yatra Hotel Settlement Reconciliation in India: Multi-OTA Inventory and Settlement Timing",
          "url": "https://www.terra-insight.com/insights/goibibo-yatra-hotel-settlement-reconciliation"
        },
        {
          "q": "What commission does Yatra charge hotels in India?",
          "a": "Yatra's hotel commission typically falls in the 12% to 20% range depending on property category, prepaid versus pay-at-hotel inventory, and any participation in Yatra's promotional programmes. Yatra's corporate travel arm (Yatra for Business) has separate negotiated rates that are often lower than B2C in exchange for volume commitments. Like MMT, Yatra raises an 18% GST tax invoice on the commission earned, which is ITC-eligible for the hotel against output GST on room revenue.",
          "article": "Goibibo and Yatra Hotel Settlement Reconciliation in India: Multi-OTA Inventory and Settlement Timing",
          "url": "https://www.terra-insight.com/insights/goibibo-yatra-hotel-settlement-reconciliation"
        },
        {
          "q": "What is the dispute window on Goibibo and Yatra settlement files?",
          "a": "Both Goibibo and Yatra typically allow a 30 to 45 day window from settlement date for the hotel to raise disputes on individual bookings — covering issues like commission rate misapplication, missing TDS credit, no-show retention disagreements, and cancellation reversal timing. Disputes raised after the window are often non-acceptable per contract terms. Reconciliation must surface mismatches within the window so they can be opened with the OTA's account manager before the deadline. Holding disputes over period-end and discovering them in a quarter-end audit is a common source of bad-debt write-offs.",
          "article": "Goibibo and Yatra Hotel Settlement Reconciliation in India: Multi-OTA Inventory and Settlement Timing",
          "url": "https://www.terra-insight.com/insights/goibibo-yatra-hotel-settlement-reconciliation"
        },
        {
          "q": "How is multi-OTA inventory parity reconciled with settlement?",
          "a": "Inventory parity reconciliation is operationally distinct from commercial settlement reconciliation. The channel manager pushes the same room inventory to MMT, Goibibo, Yatra, Booking.com, and direct booking engines. When two OTAs sell the last room within seconds, the channel manager must either suppress one booking or the property must reaccommodate the guest. The settlement reconciliation surfaces the commercial impact — whether the hotel collected commission-bearing revenue on both sides, whether one was reversed, and whether the reaccommodation cost was netted against any OTA payout. Parity SLA breaches sometimes appear as commission penalties in subsequent settlement files.",
          "article": "Goibibo and Yatra Hotel Settlement Reconciliation in India: Multi-OTA Inventory and Settlement Timing",
          "url": "https://www.terra-insight.com/insights/goibibo-yatra-hotel-settlement-reconciliation"
        },
        {
          "q": "How do Goibibo and Yatra settlement timings compare?",
          "a": "Goibibo settlements typically run on a weekly cadence aligned with MMT Group's processing calendar, with payouts landing 7 to 10 days after the cycle close. Yatra historically operates on a fortnightly to monthly cadence depending on contract terms, with prepaid bookings settled faster than pay-at-hotel reconciled commissions. The cadence difference matters for working-capital planning — a hotel with mixed Goibibo and Yatra inventory has overlapping cycles that must be reconciled separately rather than monthly-aggregated, otherwise period-end accruals drift.",
          "article": "Goibibo and Yatra Hotel Settlement Reconciliation in India: Multi-OTA Inventory and Settlement Timing",
          "url": "https://www.terra-insight.com/insights/goibibo-yatra-hotel-settlement-reconciliation"
        },
        {
          "q": "Why does commission paid to a foreign OTA trigger GST RCM in India?",
          "a": "Section 9(3) of the CGST Act 2017 read with Notification 10/2017-Integrated Tax (Rate) places the GST liability on the recipient when a service is imported from outside India and the supplier has no registered presence in India. A foreign OTA such as Booking.com BV (Netherlands), Agoda Pte Ltd (Singapore), or Expedia (US) charges commission on Indian hotel bookings without an Indian GSTIN. The commission is therefore an import of service under Section 2(11) of the IGST Act, and the Indian hotel must pay 18 percent IGST under reverse charge. GST law on this point is unchanged by the new Income Tax Act 2025 — the income-tax TDS treatment changed but GST law did not.",
          "article": "GST RCM on Hotel Commission Paid to Foreign OTAs: Reconciliation Under Section 9(3)",
          "url": "https://www.terra-insight.com/insights/gst-rcm-hotel-foreign-ota-import-services"
        },
        {
          "q": "How is the RCM payment on foreign OTA commission made and reported?",
          "a": "The hotel raises a self-invoice under Section 31(3)(f) of the CGST Act for the commission amount in INR (using the relevant exchange rate on the date of payment or invoice). 18 percent IGST is computed on that INR value. The IGST is paid via the electronic cash ledger — RCM liability cannot be discharged by offsetting input tax credit. The output is reported in GSTR-3B Table 3.1(d) (inward supplies liable to reverse charge) for the month the liability arises. The same amount becomes available as ITC in the next return period under Section 16, subject to the conditions in Section 16(2) including possession of the self-invoice and payment of tax.",
          "article": "GST RCM on Hotel Commission Paid to Foreign OTAs: Reconciliation Under Section 9(3)",
          "url": "https://www.terra-insight.com/insights/gst-rcm-hotel-foreign-ota-import-services"
        },
        {
          "q": "What forex variance arises in the foreign OTA RCM reconciliation?",
          "a": "The OTA commission is denominated in foreign currency on the OTA invoice but the GST self-invoice is in INR. Three values can differ: the OTA's invoice exchange rate, the rate on the date the hotel records the liability in books, and the rate on the date the bank actually remits or the OTA nets the commission from settlement. Under GST rules the self-invoice INR value is what drives the IGST computation. Reconciliation tracks all three rates, classifies the difference as a FOREX_VARIANCE entry against the commission line, and ensures the IGST on RCM and the ITC claimed both use the GST self-invoice rate so the ledger reconciles back to the GSTR-3B entry.",
          "article": "GST RCM on Hotel Commission Paid to Foreign OTAs: Reconciliation Under Section 9(3)",
          "url": "https://www.terra-insight.com/insights/gst-rcm-hotel-foreign-ota-import-services"
        },
        {
          "q": "Can a hotel offset the RCM liability against existing ITC instead of paying cash?",
          "a": "No. Section 49(4) of the CGST Act read with Rule 86B requires that any tax payable under reverse charge be paid through the electronic cash ledger only. ITC cannot be used to discharge an RCM liability. The cash payment creates a fresh ITC entry that becomes available for use against forward-charge output liability in the next return period, but the RCM payment itself must hit cash. This is one of the most common reconciliation breaks for hotels new to foreign OTA settlements — the GSTR-3B Table 3.1(d) entry must be backed by a cash-ledger debit, not an ITC offset.",
          "article": "GST RCM on Hotel Commission Paid to Foreign OTAs: Reconciliation Under Section 9(3)",
          "url": "https://www.terra-insight.com/insights/gst-rcm-hotel-foreign-ota-import-services"
        },
        {
          "q": "How is RCM on foreign OTA commission different from TDS Section 413 on the same commission?",
          "a": "They are two different taxes on the same underlying transaction. GST RCM under Section 9(3) is an indirect tax — 18 percent IGST on the commission, paid via electronic cash ledger and recoverable as ITC. Income-tax TDS under Section 413 of the new Income Tax Act 2025 (the equivalent of legacy Section 195) is a direct tax withholding on the payment to the non-resident OTA at the rate prescribed under the Act or the relevant DTAA. Both apply on the same commission line and both require their own evidence trail. The reconciliation must classify the OTA settlement variance into OTA_COMMISSION_GROSS, RCM_IGST, TDS_NON_RESIDENT, and any FOREX_VARIANCE separately.",
          "article": "GST RCM on Hotel Commission Paid to Foreign OTAs: Reconciliation Under Section 9(3)",
          "url": "https://www.terra-insight.com/insights/gst-rcm-hotel-foreign-ota-import-services"
        },
        {
          "q": "What is bill-to-company (BTC) billing for hotels and how does it differ from direct guest billing?",
          "a": "Bill-to-company billing is a credit-sale arrangement where the corporate client, not the guest, settles the room and incidentals on a monthly invoice with 30, 60, or 90-day credit terms. At check-in the guest signs a BTC voucher referencing a pre-negotiated Local Rate Agreement (LRA) or Negotiated Rate (NDC) contract code. Folio charges accrue against the corporate's account number and route to a monthly statement-of-account, not to the guest's card at check-out. The reconciliation challenge is that the room is consumed and revenue is earned at check-out, but the cash arrives 30 to 90 days later through a single NEFT credit covering many folios — so the hotel's AR sub-ledger has to track each folio against the eventual statement payment with a typed variance trail.",
          "article": "Hotel Corporate Billing (BTC) Reconciliation in India: LRA, GST, TDS, GSTR-2B",
          "url": "https://www.terra-insight.com/insights/hotel-corporate-billing-btc-reconciliation-india"
        },
        {
          "q": "When does GST become payable on a corporate BTC invoice — at check-out or at invoice date?",
          "a": "GST time-of-supply under Section 13 of the CGST Act is the earlier of invoice date or payment receipt for services. For BTC corporate billing where the hotel issues the tax invoice within 30 days of service completion (the statutory window for services), the invoice date governs GST liability. In practice most hotels invoice at month-end consolidating all stays in the period, so check-out date and invoice date diverge. The reconciliation must keep both dates because the corporate's GSTR-2B will only reflect the invoice once the hotel files its GSTR-1 for the invoice month, and the auto-drafted ITC view at the corporate end depends on the hotel's filing cadence.",
          "article": "Hotel Corporate Billing (BTC) Reconciliation in India: LRA, GST, TDS, GSTR-2B",
          "url": "https://www.terra-insight.com/insights/hotel-corporate-billing-btc-reconciliation-india"
        },
        {
          "q": "How is corporate AR ageing tracked for hotel BTC accounts?",
          "a": "Corporate AR ageing is tracked in 30/60/90/120+ buckets from invoice date, with the dispute window typically locked at 30 days from invoice. Within the 30-day dispute window the corporate can raise queries on individual folios — incidental charges, mini-bar disputes, no-show charges, late check-out fees — and the hotel adjusts via credit note. After the 30-day window, disputes still get raised but become contractual recovery work. The reconciliation tracks invoice age, dispute status, partial payment allocations, and credit note linkages, because a single statement-of-account payment from a corporate often covers six to forty folios across two or three invoice cycles, and the cash application logic has to match the corporate's remittance advice.",
          "article": "Hotel Corporate Billing (BTC) Reconciliation in India: LRA, GST, TDS, GSTR-2B",
          "url": "https://www.terra-insight.com/insights/hotel-corporate-billing-btc-reconciliation-india"
        },
        {
          "q": "Does TDS apply to corporate hotel bills, and which Income Tax Act 2025 section governs it?",
          "a": "Routine business travel — short-stay hotel accommodation booked occasion by occasion — is not treated as rent and typically does not attract TDS at the source. However, where a corporate enters a contracted long-stay arrangement that takes on the character of rent (extended stay over a defined period at a negotiated room rent), the corporate may deduct TDS under Section 393(1)(e) of the Income Tax Act 2025, mapped to payment code 1009 in the new payment-code regime. The legacy reference is Section 194I, which Section 393(1)(e) replaces from the 2026 transition. The reconciliation must classify each corporate account as either rent-treated (TDS applies, payment code 1009) or routine business travel (no TDS), and the post-payment Form 26AS reconciliation under the corporate's TAN must match the cumulative TDS withheld.",
          "article": "Hotel Corporate Billing (BTC) Reconciliation in India: LRA, GST, TDS, GSTR-2B",
          "url": "https://www.terra-insight.com/insights/hotel-corporate-billing-btc-reconciliation-india"
        },
        {
          "q": "How does GSTIN-vs-GSTIN matching work between a hotel's GSTR-1 and a corporate's GSTR-2B?",
          "a": "The corporate buyer downloads GSTR-2B monthly to claim input tax credit on hotel invoices. Each hotel invoice the corporate paid must appear in the buyer's GSTR-2B with matching GSTIN, invoice number, invoice date, taxable value, and GST amount. If the hotel files late or files with a wrong buyer GSTIN, the line drops from GSTR-2B and the corporate cannot claim ITC, which usually triggers a payment hold. The reconciliation pulls the hotel's GSTR-1 outward supply register and matches it field by field to the corporate's GSTR-2B view, flagging GSTIN mismatches, invoice-number formatting differences, and tax-period misalignments before the corporate AR team escalates.",
          "article": "Hotel Corporate Billing (BTC) Reconciliation in India: LRA, GST, TDS, GSTR-2B",
          "url": "https://www.terra-insight.com/insights/hotel-corporate-billing-btc-reconciliation-india"
        },
        {
          "q": "Is GST payable when a hotel receives an advance against room charges?",
          "a": "Yes for advances against room charges. Under Section 13 of the CGST Act, the time of supply for services is the earlier of invoice date or payment receipt. When a hotel receives an advance against room charges, GST becomes payable on the receipt at the applicable slab — 12 percent below ₹7,500 per night, 18 percent at or above ₹7,500. A receipt voucher is issued and the tax reported in GSTR-1 as an advance, then adjusted at check-in when the tax invoice is raised. A refundable security deposit, by contrast, is not consideration for a supply and does not attract GST on receipt.",
          "article": "Hotel Deposit, Refund, and No-Show Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/hotel-deposit-refund-no-show-reconciliation-india"
        },
        {
          "q": "How is a refundable security deposit different from a deposit-against-room-charges?",
          "a": "A refundable security deposit is held against potential damage or incidental usage, sits on the balance sheet as a liability, and carries no GST on receipt because it is not consideration for a supply. A deposit-against-room-charges is an advance applied to the contracted stay; revenue recognises only at check-in, but GST under Section 13 of the CGST Act is triggered on receipt. The two must be tracked in separate ledger accounts in the PMS and the accounting system, because they have different revenue triggers, different GST timing, and different audit treatment.",
          "article": "Hotel Deposit, Refund, and No-Show Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/hotel-deposit-refund-no-show-reconciliation-india"
        },
        {
          "q": "How do hotels charge no-show fees, and what is the GST treatment?",
          "a": "No-show charges are typically one night's room rate, charged either to the credit card on file or held against any advance already received. Most hotels treat the no-show as a taxable supply because the room was held and not made available to others, attracting GST at the room-tariff slab. A tax invoice is issued in the no-show guest's name. Some operators treat it as liquidated damages with a different tax view; the correct construction depends on the contract wording and the property's accounting policy, ideally consistent across the portfolio.",
          "article": "Hotel Deposit, Refund, and No-Show Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/hotel-deposit-refund-no-show-reconciliation-india"
        },
        {
          "q": "How does cancellation refund flow work for an Indian hotel booking?",
          "a": "Cancellation policies typically refund full advance if cancelled outside a window — for example more than seven days before arrival — partial inside the window, and zero inside 48 hours. When a refund is issued, the corresponding GST advance must be reversed through a refund voucher and reflected in GSTR-1 advance-adjustment. Reconciliation tracks the original receipt, the partial refund, the retained portion that becomes either revenue or forfeit, and the GST adjustment line. Without typed tracking, refunds that cross GST return periods create open advance-and-adjustment lines.",
          "article": "Hotel Deposit, Refund, and No-Show Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/hotel-deposit-refund-no-show-reconciliation-india"
        },
        {
          "q": "What is CARO 2020's view on long-outstanding deposit-payable balances?",
          "a": "CARO 2020 expects auditors to comment on whether liabilities, including deposit-payable balances, are properly classified, supported, and not stale. A refundable security deposit held against a guest who has long since checked out, with no clear basis for retention, is a stale liability. Auditors will probe ageing reports on the deposit ledger, evidence of refund-attempt or retention rationale, and consistency between PMS deposit ledger and accounting AP or AR balances. Hotels with messy deposit ledgers and no ageing controls typically draw an audit comment.",
          "article": "Hotel Deposit, Refund, and No-Show Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/hotel-deposit-refund-no-show-reconciliation-india"
        },
        {
          "q": "What GST rate applies when F&B is charged to a room folio?",
          "a": "F&B charged to a room folio retains the restaurant's own GST rate, not the room's. If the in-house restaurant is at 18% with ITC (because any room in the hotel is published at or above ₹7,500), the F&B chit posts at 18% to the folio. If the restaurant is at 5% no-ITC (because all rooms are published below ₹7,500), the F&B posts at 5% to the folio. The room-night line on the same folio carries its own rate independently — 12% or 18% based on the realised tariff.",
          "article": "Hotel F&B Room Charge Reconciliation: POS to Folio with GST Splits",
          "url": "https://www.terra-insight.com/insights/hotel-fb-room-charge-reconciliation"
        },
        {
          "q": "How is a room-charge F&B chit reconciled back to the POS?",
          "a": "Every room-charge chit at the POS writes a posting to the PMS folio with a unique chit reference, room number, amount, and tax. The reconciliation matches each PMS folio F&B line to its source POS chit by reference, and confirms that no POS chit posted to a room is missing from the corresponding folio. Tickets paid directly at the restaurant should not appear on the folio, and any that do are flagged as duplicate posts.",
          "article": "Hotel F&B Room Charge Reconciliation: POS to Folio with GST Splits",
          "url": "https://www.terra-insight.com/insights/hotel-fb-room-charge-reconciliation"
        },
        {
          "q": "What is the MINIBAR_LATE_POST variance?",
          "a": "MINIBAR_LATE_POST is a recurring variance where minibar consumption is discovered during room servicing after the guest has checked out — the housekeeping team posts the consumption to the folio late, and the post lands after the folio was closed at checkout. The variance shows up as an open balance against a closed folio, requiring either a settlement against the guest's stored card or a write-off if the amount is not recoverable. Tracking it as a named variance lets finance trend the leakage and tighten the housekeeping cut-off.",
          "article": "Hotel F&B Room Charge Reconciliation: POS to Folio with GST Splits",
          "url": "https://www.terra-insight.com/insights/hotel-fb-room-charge-reconciliation"
        },
        {
          "q": "How is service charge treated under the 2022 CCPA guidelines?",
          "a": "The July 2022 CCPA Guidelines prohibit hotels and restaurants from levying service charge automatically or by default on the food bill. Service charge cannot be added without explicit guest consent, cannot be collected by another name, and cannot be made a condition of entry or service. Hotels that retain a service charge mechanism must operate it as opt-in, disclosed up front, and reconciled into a transparent tip-pool ledger that distributes to staff per a documented policy.",
          "article": "Hotel F&B Room Charge Reconciliation: POS to Folio with GST Splits",
          "url": "https://www.terra-insight.com/insights/hotel-fb-room-charge-reconciliation"
        },
        {
          "q": "How does banquet F&B differ from à la carte room-charge F&B?",
          "a": "Banquet F&B is contracted upfront as part of an event — covers per menu rate are fixed in the BEO, and the consumption is invoiced through the banquet folio against the event advance. À la carte room-charge F&B is consumed by an in-house guest at a restaurant or via room service, posted chit-by-chit to the room folio, and settled at checkout. Both attract restaurant GST treatment, but the reconciliation paths run through different sub-systems — BEO for banquet, restaurant POS for room-charge.",
          "article": "Hotel F&B Room Charge Reconciliation: POS to Folio with GST Splits",
          "url": "https://www.terra-insight.com/insights/hotel-fb-room-charge-reconciliation"
        },
        {
          "q": "What GST rate applies to a hotel room in India after October 2024?",
          "a": "The applicable GST rate is determined by the actual transaction value of the room per night. If the room tariff is below ₹7,500 per unit per day, GST is 12% with input tax credit available to the hotel. If the room tariff is ₹7,500 or above per unit per day, GST is 18% with ITC. The classification is decided at folio level based on the realised tariff after discounts, not the published rack rate.",
          "article": "Hotel GST Reconciliation: 12% vs 18% Room Tariff Rules in India",
          "url": "https://www.terra-insight.com/insights/hotel-gst-reconciliation-12pct-vs-18pct"
        },
        {
          "q": "What GST rate applies to a restaurant inside a hotel?",
          "a": "Restaurant GST inside a hotel depends on the hotel's room tariff slab. If any room in the hotel has a published tariff of ₹7,500 or above, the in-house restaurant attracts 18% GST with full ITC. If no room crosses ₹7,500, the restaurant attracts 5% GST with no ITC. The classification is at hotel level, not at folio level — a hotel does not switch restaurant rates guest-by-guest.",
          "article": "Hotel GST Reconciliation: 12% vs 18% Room Tariff Rules in India",
          "url": "https://www.terra-insight.com/insights/hotel-gst-reconciliation-12pct-vs-18pct"
        },
        {
          "q": "How do I reconcile a folio that carries multiple GST rates?",
          "a": "Each folio line must be tagged with its own HSN/SAC, rate, and ITC eligibility before consolidation. The reconciliation is run at line level — room nights at 12% or 18%, F&B at 5% or 18%, banquet at 18%, laundry at 18% — and then summed back to the folio total. The PMS folio total must match the sum of POS, banquet, and ancillary tickets posted against that folio, with each rate stream reconciling separately to GSTR-1.",
          "article": "Hotel GST Reconciliation: 12% vs 18% Room Tariff Rules in India",
          "url": "https://www.terra-insight.com/insights/hotel-gst-reconciliation-12pct-vs-18pct"
        },
        {
          "q": "How are these rates reported in GSTR-1?",
          "a": "Each rate stream is reported on its own line in GSTR-1, typically Table 7 for B2C and Table 4/5 for B2B with GSTIN. A guest billed ₹6,000 room at 12%, ₹2,000 F&B at 18%, and ₹500 laundry at 18% generates three separate output tax lines, not one. Many PMS exports default to a single consolidated tax line, which is the most common GSTR-1 mismatch source for hotels.",
          "article": "Hotel GST Reconciliation: 12% vs 18% Room Tariff Rules in India",
          "url": "https://www.terra-insight.com/insights/hotel-gst-reconciliation-12pct-vs-18pct"
        },
        {
          "q": "What happens when a discount drops a room tariff from ₹8,000 to ₹7,200?",
          "a": "GST is charged on the actual transaction value, so a ₹7,200 realised tariff falls in the 12% slab even if the rack rate is ₹8,000. However, the in-house restaurant rate continues at 18% as long as any published room rate in the hotel is at or above ₹7,500 — the published rate, not the discounted rate, governs the restaurant classification. Auditors test this distinction during scrutiny.",
          "article": "Hotel GST Reconciliation: 12% vs 18% Room Tariff Rules in India",
          "url": "https://www.terra-insight.com/insights/hotel-gst-reconciliation-12pct-vs-18pct"
        },
        {
          "q": "How are hotel loyalty points treated in the books — revenue or liability?",
          "a": "Hotel loyalty points are a deferred-revenue liability under Ind AS 115. The accounting standard treats points awarded on a paid stay as a separate performance obligation distinct from the stay itself. At accrual the hotel allocates a portion of the transaction price to the points, recognises the cash-paid stay as revenue, and parks the points-allocated portion on the balance sheet as a liability. Revenue is recognised on the points only when they are redeemed (a future stay or other reward) or when they expire unredeemed. Programs like Marriott Bonvoy, Hilton Honors, IHG One Rewards, ITC Hotels Green Points, Taj InnerCircle, Lemon Tree Smiles, and OYO Wizard all operate under this framework, with the central program operator typically running the liability ledger across the chain.",
          "article": "Hotel Loyalty Program Reconciliation in India: Bonvoy, Honors, IHG, ITC, Taj",
          "url": "https://www.terra-insight.com/insights/hotel-loyalty-program-reconciliation-india"
        },
        {
          "q": "What happens when a guest pays for a stay entirely with loyalty points — is GST payable?",
          "a": "On a points-only redemption stay where the guest pays no cash and the property does not receive any consideration, GST is generally not payable because there is no taxable supply for consideration. However, where the chain reimburses the property from the loyalty fund (an inter-company recharge), the property recognises that recharge as revenue and may attract GST on the reimbursement under place-of-supply rules, depending on whether the chain operator is in the same state. The cleaner pattern most chains use is property-level zero consideration with central inter-property liability transfer outside the GST chain. Reconciliation has to identify each redemption stay and tag it as zero-consideration, partial-redemption, or chain-reimbursed because each path has a different GST and revenue posture.",
          "article": "Hotel Loyalty Program Reconciliation in India: Bonvoy, Honors, IHG, ITC, Taj",
          "url": "https://www.terra-insight.com/insights/hotel-loyalty-program-reconciliation-india"
        },
        {
          "q": "How is breakage rate estimated for a hotel loyalty program?",
          "a": "Breakage is the proportion of points expected to expire unredeemed. Under Ind AS 115 the hotel can recognise breakage revenue in proportion to the pattern of points redemption, provided breakage can be reliably estimated from historical redemption behaviour. Most chain programs use rolling 24 to 36-month redemption rates, member-tier-segmented (Silver, Gold, Platinum, Titanium for Bonvoy; Diamond, Gold, Silver for Honors; equivalent tiers for IHG, ITC, Taj). Breakage rates typically run between 12 and 25 percent depending on program design, expiry rules, and member engagement. The reconciliation surfaces the breakage estimate as a quarterly true-up against the actual redemption pattern so the deferred-revenue liability stays calibrated.",
          "article": "Hotel Loyalty Program Reconciliation in India: Bonvoy, Honors, IHG, ITC, Taj",
          "url": "https://www.terra-insight.com/insights/hotel-loyalty-program-reconciliation-india"
        },
        {
          "q": "Why does a property's loyalty register rarely match the chain's central ledger?",
          "a": "The chain's central loyalty ledger holds the program-wide liability, the per-member point balance, the accrual posted at every stay across every property, and the redemption posted at every redemption stay. A single property only sees its own accruals and redemptions. Three timing differences typically open: a stay closed at the property's night-audit cut-off may post to the central ledger a day later; an inter-property transfer (member earned points at property A but redeemed at property B) creates an accrual on one property and a redemption on another with a chain-level recharge; and rate-of-accrual changes (promotional double-points, status bonuses) are calculated centrally and may not reflect in the property's PMS view immediately. Reconciliation has to bridge these three with a typed variance trail.",
          "article": "Hotel Loyalty Program Reconciliation in India: Bonvoy, Honors, IHG, ITC, Taj",
          "url": "https://www.terra-insight.com/insights/hotel-loyalty-program-reconciliation-india"
        },
        {
          "q": "What evidence does statutory audit need for a hotel's loyalty program reconciliation?",
          "a": "For a property within a chain, the auditor needs the property's accruals and redemptions reconciled to the chain's central liability ledger, the breakage-rate methodology and the period's true-up calculation, the deferred-revenue movement on the property's books (or the inter-company recharge if liability sits at chain level), the GST treatment on each redemption pattern (zero consideration versus chain reimbursement), and the audit trail from PMS folio to loyalty transaction to chain ledger entry. Properties without typed evidence on these five lines typically draw audit comments, particularly on Ind AS 115 application around the points-allocated transaction price and the breakage-rate basis.",
          "article": "Hotel Loyalty Program Reconciliation in India: Bonvoy, Honors, IHG, ITC, Taj",
          "url": "https://www.terra-insight.com/insights/hotel-loyalty-program-reconciliation-india"
        },
        {
          "q": "What is hotel night audit and why is it run between midnight and 6 a.m.?",
          "a": "Night audit is the daily close routine in a hotel property management system that posts room and tax charges to every in-house folio, closes the day in the PMS, rolls the system date forward, and produces the day's revenue and cash position reports. It runs in the lowest-occupancy window — typically between midnight and 6 a.m. — because the PMS is briefly locked for posting during the close, and front-office activity must pause. The cut-off time is property-defined and stays consistent so that revenue is recognised in the right operating day even when checkouts and arrivals overlap the boundary.",
          "article": "Hotel Night Audit Close Reconciliation: PMS Day-Close Discipline",
          "url": "https://www.terra-insight.com/insights/hotel-night-audit-close-reconciliation"
        },
        {
          "q": "What does a typical night audit checklist cover?",
          "a": "The checklist covers PMS day-close (room and tax posting, system date roll), F&B outlet daily-Z from each restaurant and bar POS, banquet daily settlement against the event register, minibar postings flagged by housekeeping, no-show charges processed against the credit card on file, pending arrivals and departures cleared or rolled, deposit and float verification at the front-desk cash drawer, and reconciliation against the bank deposit slip plus the credit-card terminal batch and UPI or QR daily settlement summary.",
          "article": "Hotel Night Audit Close Reconciliation: PMS Day-Close Discipline",
          "url": "https://www.terra-insight.com/insights/hotel-night-audit-close-reconciliation"
        },
        {
          "q": "How do PMS systems like Opera, IDS Next, eZee, and Hotelogix handle the close routine?",
          "a": "Each PMS exposes a night-audit module that walks the auditor through a fixed sequence — post room and tax, close outlet sub-systems, run revenue reports, roll the business date, and lock the prior day. Opera and IDS Next ship enterprise-grade close routines with detailed exception lists; eZee and Hotelogix run cloud-native close routines with similar steps. The commonality is the system date roll: once executed, the previous day is closed for posting and any late charge has to go to a current-day adjustment with a reference to the original folio.",
          "article": "Hotel Night Audit Close Reconciliation: PMS Day-Close Discipline",
          "url": "https://www.terra-insight.com/insights/hotel-night-audit-close-reconciliation"
        },
        {
          "q": "Why do PMS day-close revenue and bank deposit rarely match on the same date?",
          "a": "PMS day-close runs at the night-audit cut-off and produces the property's gross revenue for the operating day. The bank deposit slip is built from physical cash collected at the front desk and dropped at the bank on the next working day. The credit-card terminal batch settles to the bank on T+1 or T+2, net of MDR and net of GST on MDR. UPI and QR daily settlements settle on their own gateway cycle. So gross PMS revenue on the 10th appears as net cash in the bank across the 10th, 11th, and 12th, with timing and MDR variances that have to be classified before any folio-level match.",
          "article": "Hotel Night Audit Close Reconciliation: PMS Day-Close Discipline",
          "url": "https://www.terra-insight.com/insights/hotel-night-audit-close-reconciliation"
        },
        {
          "q": "What are common night-audit exception classes?",
          "a": "Five classes recur. Cash short or over at the front-desk float compared with the system-expected cash. Unposted F&B charge, where a guest signed for a restaurant bill but the room-charge transfer never reached the folio. Delayed minibar posting flagged as MINIBAR_LATE_POST when housekeeping inspects after the guest has checked out. Settled-but-uncharged, where a payment was received but the corresponding charge was not posted, leaving an open credit on the folio. And partial folio, where some charges hit the master and others the room — typically a routing rule misconfiguration.",
          "article": "Hotel Night Audit Close Reconciliation: PMS Day-Close Discipline",
          "url": "https://www.terra-insight.com/insights/hotel-night-audit-close-reconciliation"
        },
        {
          "q": "What is the difference between inventory parity reconciliation and commercial reconciliation?",
          "a": "Inventory parity reconciliation confirms that the same room is not sold twice across channels — it operates in real time at the channel manager and prevents overbooking. Commercial reconciliation is the after-the-fact financial match: did the booking that landed in the PMS produce the correct OTA payout net of commission, GST, and TDS, and did that payout arrive in the bank? The two are different problems with different tools. Channel managers like SiteMinder, STAAH, and RateGain solve parity. Reconciliation software solves the commercial match. Conflating the two leaves either overbooking exposure or revenue leakage on the table.",
          "article": "Hotel PMS and Channel Manager Reconciliation in India: From Folio to Ledger",
          "url": "https://www.terra-insight.com/insights/hotel-pms-channel-manager-reconciliation"
        },
        {
          "q": "Which PMS systems are common in Indian hotels?",
          "a": "Oracle Opera (large chains, business hotels), IDS Next (mid-market, popular among Indian properties), eZee Frontdesk (budget and mid-market), Hotelogix (cloud-based, common with smaller properties), and Innkey, Aatithya, and other regional PMS products serving specific segments. Each PMS has different folio data structures, different OTA reference field conventions, and different export formats. A reconciliation solution must adapt to the property's PMS rather than assuming Opera-style data structures.",
          "article": "Hotel PMS and Channel Manager Reconciliation in India: From Folio to Ledger",
          "url": "https://www.terra-insight.com/insights/hotel-pms-channel-manager-reconciliation"
        },
        {
          "q": "Which channel managers are common in India?",
          "a": "SiteMinder (global market leader, broad OTA connectivity), STAAH (strong Indian and APAC presence), and RateGain (Indian-origin platform with both channel manager and revenue management products) are the most widely deployed. AxisRooms and ResAvenue also have meaningful share among Indian properties. The channel manager pushes inventory and rates outward to OTAs and pulls bookings inward to the PMS. Each channel manager has different log granularity for parity events and different export capabilities for reconciliation.",
          "article": "Hotel PMS and Channel Manager Reconciliation in India: From Folio to Ledger",
          "url": "https://www.terra-insight.com/insights/hotel-pms-channel-manager-reconciliation"
        },
        {
          "q": "What are the typical breakpoints in the OTA-to-PMS-to-bank chain?",
          "a": "Five recurring breakpoints. First, OTA booking received but channel manager fails to push it to PMS (lost booking, guest arrives without folio). Second, PMS folio created but rate or room category drifted from the OTA booking (rate leakage). Third, PMS folio closed but OTA reference number not stored on the folio (settlement match becomes manual). Fourth, OTA settlement file received but cancellation flag not propagated through channel manager and PMS (revenue overstated). Fifth, bank credit received but cannot be linked to the originating OTA settlement file (cash unreconciled). Each breakpoint produces a different audit and accounting consequence.",
          "article": "Hotel PMS and Channel Manager Reconciliation in India: From Folio to Ledger",
          "url": "https://www.terra-insight.com/insights/hotel-pms-channel-manager-reconciliation"
        },
        {
          "q": "How is a folio-level audit trail constructed for a multi-OTA property?",
          "a": "The folio is the canonical record of the stay. The audit trail starts with the OTA booking confirmation (channel and OTA reference number), flows through the channel manager log (timestamp of inventory consumption), enters the PMS as a folio with the OTA reference stored, accumulates incidentals during stay, closes at check-out with final folio amount, and is then matched to the OTA settlement file (commission, GST, TDS, net payout) and the bank credit. Reconciliation software builds this trail by indexing each step on the OTA reference number and the folio number, so an auditor can pull a single record and see all five layers.",
          "article": "Hotel PMS and Channel Manager Reconciliation in India: From Folio to Ledger",
          "url": "https://www.terra-insight.com/insights/hotel-pms-channel-manager-reconciliation"
        },
        {
          "q": "What is a virtual credit card in the OTA hotel context?",
          "a": "A virtual credit card (VCC) is a single-use card number issued by the OTA — Booking.com, Agoda, Expedia, and others — to the hotel at the time of booking. The hotel charges the VCC like a normal card transaction at check-in, the funds flow through the hotel's acquiring bank, and the OTA reconciles the VCC against the booking on its own ledger. The hotel never receives a wire transfer for that booking — the OTA's commission is netted out of the VCC face value the OTA loads.",
          "article": "Hotel OTA Virtual Card Reconciliation: Booking.com and Agoda VCC Settlement",
          "url": "https://www.terra-insight.com/insights/hotel-ota-virtual-card-reconciliation"
        },
        {
          "q": "How does VCC settlement timing differ from net-settlement OTA bookings?",
          "a": "Net-settlement OTAs (MakeMyTrip, Goibibo, Yatra in many contracts) collect from the guest, withhold their commission, and wire the net amount to the hotel weekly or fortnightly. VCC bookings (typical for Booking.com, Agoda, Expedia) work in reverse — the OTA loads the VCC with the net amount payable to the hotel after commission, the hotel charges that VCC at check-in, and the funds settle to the hotel via the acquiring bank in the standard card-settlement cycle. There is no separate OTA wire.",
          "article": "Hotel OTA Virtual Card Reconciliation: Booking.com and Agoda VCC Settlement",
          "url": "https://www.terra-insight.com/insights/hotel-ota-virtual-card-reconciliation"
        },
        {
          "q": "Why does VCC reconciliation create a three-date timing problem?",
          "a": "Three dates matter and rarely align: the booking date (when the VCC was issued), the charge date (when the hotel actually swiped or processed the VCC at check-in), and the bank credit date (when the acquiring bank settled the charge). A booking made in February for a March stay charged on 14 March settles to the hotel's bank on 16 March or later. Revenue must be recognised on the correct night, but the cash trace runs through three different periods.",
          "article": "Hotel OTA Virtual Card Reconciliation: Booking.com and Agoda VCC Settlement",
          "url": "https://www.terra-insight.com/insights/hotel-ota-virtual-card-reconciliation"
        },
        {
          "q": "What happens when a VCC charge fails or the cardholder disputes it?",
          "a": "If the VCC declines at check-in — typically because the OTA released the VCC late, the activation window has not opened, or the hotel attempted to charge before the eligible date — the hotel must escalate to the OTA's partner desk for VCC reissuance or modification. If the cardholder disputes the charge after the fact, the OTA's chargeback liability framework governs. For a confirmed and consumed booking with a successful charge, the dispute is rare; for cancellations after charge, the reversal flows through the same VCC.",
          "article": "Hotel OTA Virtual Card Reconciliation: Booking.com and Agoda VCC Settlement",
          "url": "https://www.terra-insight.com/insights/hotel-ota-virtual-card-reconciliation"
        },
        {
          "q": "How do I match VCC charges back to PMS folios?",
          "a": "Each VCC carries a reference that ties it to the OTA booking ID, which in turn maps to a PMS reservation number. The reconciliation runs three-way: the OTA extranet booking export (booking ID, guest name, VCC reference, face value, commission), the hotel's acquiring bank settlement file (charge date, amount, card mask, batch number), and the PMS folio (reservation, room nights, taxes). The match key chain is OTA booking ID to PMS reservation to acquiring bank charge.",
          "article": "Hotel OTA Virtual Card Reconciliation: Booking.com and Agoda VCC Settlement",
          "url": "https://www.terra-insight.com/insights/hotel-ota-virtual-card-reconciliation"
        },
        {
          "q": "How do Indian hotels reconcile OTA settlements from MakeMyTrip, Goibibo, and Booking.com?",
          "a": "OTAs settle net of commission (typically 15 to 25 percent), TDS under Section 194H at 5 percent on the commission, GST on the commission, and any cancellation adjustments. Reconciliation maps each settlement UTR in the bank statement to the OTA's settlement report, then decomposes the gap between gross booking value and net credit into four expected variance categories: OTA_COMMISSION, OTA_TDS_194H, GST_ON_COMMISSION, and OTA_CANCELLATION. Any residual after those four is an unclassified adjustment that needs investigation. One settlement batch from MakeMyTrip or Goibibo can cover 20 to 200 bookings, so the match is one bank credit to many PMS folios.",
          "article": "Hotel Reconciliation in India: OTA, PMS, Banquet, and GST Split",
          "url": "https://www.terra-insight.com/insights/hotel-reconciliation-india"
        },
        {
          "q": "What is the GST rate on hotel rooms in India after the October 2024 changes?",
          "a": "Room tariff below ₹7,500 per night attracts 12 percent GST with input tax credit available. Room tariff at or above ₹7,500 attracts 18 percent GST with ITC. For restaurants inside a hotel where any room tariff in the property crosses ₹7,500, restaurant supplies attract 18 percent GST with ITC. For restaurants inside a hotel where no room exceeds ₹7,500, restaurant supplies attract 5 percent GST without ITC. The classification is property-level for the financial year, so hotels with mixed inventory must run the F&B GST through both rules during reconciliation.",
          "article": "Hotel Reconciliation in India: OTA, PMS, Banquet, and GST Split",
          "url": "https://www.terra-insight.com/insights/hotel-reconciliation-india"
        },
        {
          "q": "How is banquet and event revenue reconciled when 50 percent is taken as advance?",
          "a": "Banquet bookings in India typically follow a 50 percent advance on confirmation and balance on the event date. Two bank credits or card receipts must link to a single event booking ID. Reconciliation tracks the advance as deferred revenue, then on the event date matches the balance receipt and recognises full revenue net of any final-folio adjustments such as additional covers, beverage upgrades, or service changes. GST is generally payable on the advance on receipt, not on event date, so the reconciliation also tracks GST timing separately from revenue recognition.",
          "article": "Hotel Reconciliation in India: OTA, PMS, Banquet, and GST Split",
          "url": "https://www.terra-insight.com/insights/hotel-reconciliation-india"
        },
        {
          "q": "Why do PMS exports from Opera, IDS Next, and eZee not match the bank statement directly?",
          "a": "PMS systems close the day at the night-audit cut-off, which is typically a hotel-defined time between midnight and 6 a.m. Bank settlements close on calendar-day cut-offs, and card or UPI gateways typically settle T+1 or T+2 net of MDR. So a folio closed on the 10th in the PMS often appears in the bank on the 11th or 12th, after MDR deduction. The PMS will show gross room revenue including taxes; the bank will show a net amount. Reconciliation has to bridge night-audit cut-off, gateway settlement lag, and the MDR-and-GST-on-MDR deduction before any folio-level match is possible.",
          "article": "Hotel Reconciliation in India: OTA, PMS, Banquet, and GST Split",
          "url": "https://www.terra-insight.com/insights/hotel-reconciliation-india"
        },
        {
          "q": "How do Indian hotels handle TDS deducted by OTAs on commission?",
          "a": "Under Section 194H, OTAs deduct TDS at 5 percent on the commission they charge the hotel. This deduction reduces the net settlement and must appear in the hotel's Form 26AS against the OTA's TAN within the relevant quarter. Reconciliation tracks each settlement's tds_by_ota field, classifies it as OTA_TDS_194H, and at quarter end matches the cumulative deducted amount to Form 26AS. Mismatches typically arise from cross-quarter timing or from the OTA filing late, leaving a credit pending in the next 26AS update.",
          "article": "Hotel Reconciliation in India: OTA, PMS, Banquet, and GST Split",
          "url": "https://www.terra-insight.com/insights/hotel-reconciliation-india"
        },
        {
          "q": "What evidence does CARO 2020 require for a hotel's reconciliation?",
          "a": "CARO 2020 requires statutory auditors to comment on whether revenue, receivables, and bank balances are properly reconciled. For a hotel, that means a documented trail from PMS folio to OTA settlement report to bank credit, with each variance classified and supported. Auditors also test the GST classification at room-tariff slab level, the TDS reconciliation against Form 26AS for OTA commissions and corporate clients, and the treatment of banquet advances as deferred revenue. Properties without typed variance evidence and without a reconciled bridge between PMS, OTA reports, and the bank typically draw an audit qualification.",
          "article": "Hotel Reconciliation in India: OTA, PMS, Banquet, and GST Split",
          "url": "https://www.terra-insight.com/insights/hotel-reconciliation-india"
        },
        {
          "q": "What commission does MakeMyTrip charge hotels in India?",
          "a": "Publicly available data and FHRAI member discussions place MakeMyTrip's hotel commission in the 15% to 25% range depending on contract type, hotel category, and inventory placement (preferred listing, MMT Assured, prepaid versus pay-at-hotel). Budget and mid-market properties typically see the higher end, while large chains negotiate lower rates. Promotional inventory and last-minute deals carry incremental marketing fees on top. Each settlement file shows the commission deducted per booking, which is the figure that should be used for reconciliation rather than a contract average.",
          "article": "MakeMyTrip Hotel Settlement Reconciliation in India: Commission, GST, and TDS Treatment",
          "url": "https://www.terra-insight.com/insights/makemytrip-hotel-settlement-reconciliation"
        },
        {
          "q": "How is GST applied on MakeMyTrip commission?",
          "a": "MMT raises a tax invoice on the hotel for commission earned, charging 18% GST under SAC 998559 (other support services). This GST is ITC-eligible for the hotel against its output GST on room revenue, which is 12% for tariffs up to ₹7,500 per night and 18% above that. The reconciliation must capture both the commission expense and the 18% GST on commission as a separate ITC claim, with the MMT tax invoice filed as the source document for GSTR-2B matching.",
          "article": "MakeMyTrip Hotel Settlement Reconciliation in India: Commission, GST, and TDS Treatment",
          "url": "https://www.terra-insight.com/insights/makemytrip-hotel-settlement-reconciliation"
        },
        {
          "q": "Does TDS apply on MakeMyTrip settlements — 194H or 194O?",
          "a": "When MMT acts as an e-commerce operator under Section 194-O, it deducts 1% TDS on the gross room amount paid to the hotel and remits net of TDS. When MMT operates as an agent on commission, the hotel must deduct 1% TDS under Section 194H on the commission paid to MMT. The settlement file indicates which mode applies per booking — controllers should not assume one section across all transactions. From October 2024 onwards 194-O coverage has expanded, so most prepaid bookings now flow through 194-O.",
          "article": "MakeMyTrip Hotel Settlement Reconciliation in India: Commission, GST, and TDS Treatment",
          "url": "https://www.terra-insight.com/insights/makemytrip-hotel-settlement-reconciliation"
        },
        {
          "q": "How are MMT cancellation refunds handled in reconciliation?",
          "a": "Cancellations appear as negative line items in subsequent settlement files. The original booking's commission is reversed, GST on commission is reversed against the original tax invoice via a credit note, and any room revenue already booked must be reversed in the period the cancellation occurs. If the cancellation crosses a GST filing period, a credit note in GSTR-1 is required. No-show bookings where MMT retains a retention amount carry a different commission treatment and must be flagged separately.",
          "article": "MakeMyTrip Hotel Settlement Reconciliation in India: Commission, GST, and TDS Treatment",
          "url": "https://www.terra-insight.com/insights/makemytrip-hotel-settlement-reconciliation"
        },
        {
          "q": "What is the difference between MMT B2C and MMT MyBiz settlements?",
          "a": "MMT MyBiz is the corporate booking arm where employer accounts pay for employee travel. Commission structures differ — MyBiz typically negotiates lower commission in exchange for volume guarantees, and corporate GSTINs appear on the tax invoice issued to the employer (with the hotel as the supplier). The hotel's reconciliation must split B2C and MyBiz bookings because GST place-of-supply rules treat them differently: B2C bookings use the customer's billing state, while MyBiz bookings use the corporate GSTIN's registered state under IGST Act Section 12.",
          "article": "MakeMyTrip Hotel Settlement Reconciliation in India: Commission, GST, and TDS Treatment",
          "url": "https://www.terra-insight.com/insights/makemytrip-hotel-settlement-reconciliation"
        },
        {
          "q": "How does the OYO revenue-share model differ from a commission-only OTA?",
          "a": "On a commission-only OTA the hotel sets the room rate, owns the guest-facing brand experience, and pays the OTA a commission for the booking. On OYO the property typically operates under an OYO brand sub-name (Townhouse, Capital O, OYO Hotels), OYO owns the rate-setting and customer relationship, and the property receives a contracted share of revenue or a minimum guarantee — whichever is higher. This shifts the reconciliation from commission-on-gross to revenue-share-on-net, with OYO retaining significantly more of the gross than a typical OTA commission.",
          "article": "OYO Hotel Settlement Reconciliation in India: Revenue Share, Minimum Guarantee, and SLA Deductions",
          "url": "https://www.terra-insight.com/insights/oyo-hotel-settlement-reconciliation"
        },
        {
          "q": "What is a minimum guarantee in an OYO contract?",
          "a": "Many OYO partner contracts include a minimum guarantee — a baseline monthly payout to the property regardless of actual occupancy, calculated per room or per property. If the revenue-share calculation falls below the minimum guarantee, OYO tops up to the guaranteed floor. If it exceeds the guarantee, the higher amount is paid. The reconciliation must compute both legs each month and verify which leg the settlement file paid against. Mismatches typically arise from disagreements on how SLA deductions interact with the guarantee — whether deductions apply before or after the guarantee floor.",
          "article": "OYO Hotel Settlement Reconciliation in India: Revenue Share, Minimum Guarantee, and SLA Deductions",
          "url": "https://www.terra-insight.com/insights/oyo-hotel-settlement-reconciliation"
        },
        {
          "q": "What kinds of SLA deductions appear on OYO settlements?",
          "a": "OYO partner contracts typically include service-level commitments on cleanliness scores, guest response time, complaint resolution, on-property amenities, and minimum rating thresholds on OYO's review platform. Breaches trigger contractually defined deductions that appear as line items in the settlement file. Deductions can also flow from booking-level events — no-show treatment, walkthrough audit findings, OTA channel parity violations. The reconciliation must capture each deduction with its reason code so the property can dispute incorrect applications within the contract's dispute window.",
          "article": "OYO Hotel Settlement Reconciliation in India: Revenue Share, Minimum Guarantee, and SLA Deductions",
          "url": "https://www.terra-insight.com/insights/oyo-hotel-settlement-reconciliation"
        },
        {
          "q": "How does OYO Townhouse or Capital O differ from a standard OYO listing?",
          "a": "OYO Townhouse and Capital O are higher-tier sub-brands with stricter property standards, different revenue-share splits, and typically higher minimum guarantees. The contracts often include capex commitments — branding, room refresh, amenity upgrades — that are recovered from the property's revenue share over a contracted period. The reconciliation for these properties must distinguish operational settlement from capex recovery deductions, since the latter affect the property's net cash but not its revenue or expense recognition.",
          "article": "OYO Hotel Settlement Reconciliation in India: Revenue Share, Minimum Guarantee, and SLA Deductions",
          "url": "https://www.terra-insight.com/insights/oyo-hotel-settlement-reconciliation"
        },
        {
          "q": "Who owns the GST liability on OYO bookings — the property or OYO?",
          "a": "It depends on the contract structure. Where OYO acts as the supplier of accommodation under its brand and the property is a sub-licensee, OYO raises the invoice on the guest with OYO's GSTIN and pays the output GST. The property then receives revenue share net of GST and books it as a service rendered to OYO under SAC 996311 with 18% GST forward charge. Where the property remains the supplier and OYO is a marketing and technology partner, the property invoices the guest directly and OYO bills its share. Reading the contract carefully before designing the GST reconciliation is essential — the wrong choice produces a GSTR-1 misclassification that surfaces in scrutiny.",
          "article": "OYO Hotel Settlement Reconciliation in India: Revenue Share, Minimum Guarantee, and SLA Deductions",
          "url": "https://www.terra-insight.com/insights/oyo-hotel-settlement-reconciliation"
        },
        {
          "q": "How is GST treated for stays of 30 days or more at a service apartment?",
          "a": "When a service apartment contract is structured as a recurring monthly stay of 30 days or more with a fixed rent-shaped consideration, the supply is generally characterised as renting of immovable property rather than hotel accommodation. Renting of immovable property for residential purposes by a registered person to another registered person is taxable under reverse charge in some structures, while renting to an unregistered individual for residence remains exempt. Where the property is held out as a hotel-style serviced unit and the room tariff slabs apply, the 12 percent or 18 percent slab logic from the October 2024 hotel rules can still apply. The classification is contract-by-contract and properties such as Oakwood, Tata Tribute Living, and Olive by Embassy typically maintain a written GST classification flag against each booking based on stay length and contract shape.",
          "article": "Service Apartment and Extended-Stay Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/service-apartment-extended-stay-reconciliation-india"
        },
        {
          "q": "How are security deposits handled in service apartment reconciliation?",
          "a": "Security deposits are refundable and are not revenue at receipt — they sit on the balance sheet as a liability against the booking. Reconciliation tracks the deposit as a separate ledger line, links it to the booking ID, and matches the refund against either a bank debit at check-out or a deduction from the final folio for damages or unpaid charges. GST does not apply to a refundable security deposit; it applies only to any portion that is forfeited, at which point the forfeited amount becomes a taxable supply. A typed variance code such as DEPOSIT_REFUND or DEPOSIT_FORFEITURE separates these from the rent and F&B revenue lines.",
          "article": "Service Apartment and Extended-Stay Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/service-apartment-extended-stay-reconciliation-india"
        },
        {
          "q": "Why do corporate guests deduct TDS under Section 393(1)(e) payment code 1009 instead of the hotel services code?",
          "a": "Under the new Income Tax Act 2025, Section 393 consolidates the TDS framework and payment code 1009 corresponds to rent payments — replacing legacy Section 194I. When a corporate occupies a service apartment for an extended stay under a rent-shaped contract (fixed monthly consideration, exclusive occupation, multi-month tenure), the corporate finance team typically treats the payment as rent and deducts TDS at the rate applicable to payment code 1009 rather than at the lower rate that would apply to a transient hotel stay. The service apartment must reconcile each corporate settlement against the corporate's TDS certificate, classify the deduction as CORPORATE_TDS_RENT, and confirm the entry appears against the property's TAN in the relevant quarter.",
          "article": "Service Apartment and Extended-Stay Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/service-apartment-extended-stay-reconciliation-india"
        },
        {
          "q": "How is recurring monthly billing different from daily room-rate reconciliation?",
          "a": "Transient hotel reconciliation is folio-by-folio: each guest checks in, accumulates charges, and checks out, producing a single folio that must reconcile to a single payment. Service apartment recurring billing is contract-driven: a single booking generates a monthly invoice for the duration of the stay, with rent-equivalent consideration plus optional F&B and laundry add-ons, plus periodic deposit and refund movements. The reconciliation tracks the booking as a long-running entity with multiple monthly billing events, multiple bank credits (or NEFTs from a corporate), and a closing event when the resident checks out and the deposit settles. Properties such as Saffronstays and Lemon Tree Service Apartments run both transient and extended models, so the reconciliation logic must branch by stay length and contract shape.",
          "article": "Service Apartment and Extended-Stay Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/service-apartment-extended-stay-reconciliation-india"
        },
        {
          "q": "How are F&B and laundry add-ons treated against the rent line in extended-stay billing?",
          "a": "F&B and laundry are distinct supplies and carry their own GST treatment regardless of how the rent line is classified. F&B at a service apartment with restaurant operations typically follows the hotel-property GST classification (5 percent without ITC if no room exceeds the slab threshold, 18 percent with ITC otherwise). Laundry, housekeeping upgrades, and parking are taxed at their applicable rates. Reconciliation keeps the rent line, the F&B line, and the auxiliary services line in separate variance buckets so the GSTR-1 outward supplies break-up reflects the right rate against the right HSN or SAC code, and the corporate's TDS certificate matches the rent portion only.",
          "article": "Service Apartment and Extended-Stay Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/service-apartment-extended-stay-reconciliation-india"
        },
        {
          "q": "Which section and payment code apply when a hotel deducts TDS on OTA commission from April 1, 2026?",
          "a": "Section 393(1)(f) of the Income Tax Act 2025 with payment code 1007. This replaces Section 194H of the Income Tax Act 1961 for any deduction made on or after April 1, 2026. The rate is 5% on commission paid to a resident OTA such as MakeMyTrip, Goibibo, Yatra, or OYO domestic. The hotel is the deductor; the OTA is the deductee. Challan 281, Form 26Q, and Form 16A issued for these deductions must reference 393(1)(f) and code 1007. For deductions made up to March 31, 2026, the legacy Section 194H reference continues to apply on the original challan and certificate, even if the return is filed after April 1, 2026.",
          "article": "Section 393(1)(f) and Payment Code 1007: Hotel TDS Reconciliation on Domestic OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-393-hotel-ota-commission-reconciliation"
        },
        {
          "q": "Does Section 393(1)(f) apply when MakeMyTrip operates as an e-commerce operator under Section 194-O?",
          "a": "No. The two sections cover different transaction shapes and only one applies per booking. When the OTA acts as an e-commerce operator and itself deducts 1% TDS on the gross room amount paid to the hotel, the relevant section in the 2025 Act is the e-commerce operator provision, not 393(1)(f). When the hotel pays a commission invoice raised by the OTA in an agency model, the hotel deducts 5% under 393(1)(f) and code 1007. The settlement file usually marks the mode per booking. The reconciliation must route on this flag — applying 393(1)(f) blanket would cause double deduction on bookings where the OTA has already withheld at the gross level.",
          "article": "Section 393(1)(f) and Payment Code 1007: Hotel TDS Reconciliation on Domestic OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-393-hotel-ota-commission-reconciliation"
        },
        {
          "q": "How is foreign-currency commission handled on a domestic OTA invoice?",
          "a": "Most domestic OTA commission is invoiced in INR, but a small share — typically Goibibo or MakeMyTrip handling inbound foreign-currency settlements for international guests — can land as a separate INR-equivalent line for the foreign-currency leg. The TDS under 393(1)(f) is computed on the rupee value of the commission on the date of credit or payment, whichever is earlier. Forex variance between credit date and payment date is booked as a separate ledger entry and does not change the TDS already deducted. Reconciliation should keep the rupee TDS base, the forex movement, and the final settlement as three distinct lines so that Form 16A reconciles to the original invoice.",
          "article": "Section 393(1)(f) and Payment Code 1007: Hotel TDS Reconciliation on Domestic OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-393-hotel-ota-commission-reconciliation"
        },
        {
          "q": "How does deduction-date routing work for cross-era reconciliation?",
          "a": "From April 1, 2026 the reconciliation engine has to handle both code sets at the same time. Commission invoices dated up to March 31, 2026 — even if paid in April or May — were governed by the old Act if credit was already given in the books before April 1. Invoices and credits arising on or after April 1, 2026 fall under 393(1)(f) and code 1007. The matching engine must tag each TDS line with its deduction date and route to the correct rate and code, rather than assuming a single section per vendor. A vendor master with one fixed code field will produce false mismatches across the transition.",
          "article": "Section 393(1)(f) and Payment Code 1007: Hotel TDS Reconciliation on Domestic OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-393-hotel-ota-commission-reconciliation"
        },
        {
          "q": "What does the OTA see in Form 168 and how does the hotel verify it?",
          "a": "From April 1, 2026, Form 168 is the deductee-side annual statement that replaces the deductee view of Form 26AS for entries deducted under the new Act. The OTA — MakeMyTrip, Goibibo, Yatra, or OYO domestic — pulls Form 168 from the e-filing portal and sees credits tagged with 393(1)(f), code 1007, and the hotel's TAN. The hotel verifies its side by reconciling the deducted amount on its books to the Challan 281 receipt, then to its Form 26Q quarterly return, and finally to the Form 131 deductee-wise certificate generated for the OTA. The OTA's Form 168 figure should equal the hotel's Form 131 figure at deductee level — any mismatch points to a return-filing or BIN error that must be corrected before the OTA closes its tax workings.",
          "article": "Section 393(1)(f) and Payment Code 1007: Hotel TDS Reconciliation on Domestic OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-393-hotel-ota-commission-reconciliation"
        },
        {
          "q": "Which section governs TDS on foreign OTA commission from April 1, 2026?",
          "a": "Section 413 of the Income Tax Act 2025 governs TDS on payments to non-residents from April 1, 2026, replacing Section 195 of the Income Tax Act 1961. For hotel commission paid to Booking.com B.V. (Netherlands), Agoda (Singapore), Expedia (US or UK entity), the hotel withholds tax under 413, references it on Challan 281, and reports it in Form 27Q quarterly. For deductions made up to March 31, 2026 the legacy Section 195 reference continues to apply on the original challan and Form 16A even if the return is filed after April 1, 2026.",
          "article": "Section 413 of the Income Tax Act 2025: Hotel TDS Reconciliation on Foreign OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-section-413-hotel-foreign-ota-reconciliation"
        },
        {
          "q": "How is the DTAA treaty rate determined?",
          "a": "The hotel applies the lower of the rate under the Income Tax Act 2025 read with the relevant DTAA, treaty article. For Netherlands the India–Netherlands DTAA caps royalty and fees for technical services at 10%. For Singapore the India–Singapore DTAA caps at 10% with the Most-Favoured-Nation reduction logic. For the US the India–US DTAA Article 12 covers royalty and FTS at 15% in most cases. Treaty rate eligibility requires a valid Tax Residency Certificate (TRC) from the foreign OTA plus Form 10F. Without a TRC and Form 10F the higher Act rate applies. The reconciliation must store the treaty article, the TRC validity period, and the Form 10F date against each foreign OTA in the vendor master.",
          "article": "Section 413 of the Income Tax Act 2025: Hotel TDS Reconciliation on Foreign OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-section-413-hotel-foreign-ota-reconciliation"
        },
        {
          "q": "Are commission payments to foreign OTAs royalty, FTS, or business income?",
          "a": "Classification is contested and depends on the OTA's contractual posture and whether it has a Permanent Establishment (PE) in India. The conservative position taken by most Indian hotels is to treat OTA commission as Indian-source business income paid to a non-resident with no PE — which under most DTAAs is not taxable in India and does not attract withholding. The aggressive tax authority position has at times argued FTS or royalty classification, which would attract treaty-rate withholding of 10% to 15%. Where there is doubt, hotels obtain a Section 197 (now 393(2) under the 2025 Act) lower withholding certificate or proceed with treaty-rate withholding to manage downside risk. The classification position must be documented in the vendor file and applied consistently.",
          "article": "Section 413 of the Income Tax Act 2025: Hotel TDS Reconciliation on Foreign OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-section-413-hotel-foreign-ota-reconciliation"
        },
        {
          "q": "Why will Form 168 not show foreign OTA TDS credits?",
          "a": "Form 168 is the deductee-side annual statement under the Income Tax Act 2025 — the successor to Form 26AS — and it is generated for resident deductees with PAN. Foreign OTAs without an Indian PAN do not have a Form 168 view. Their Indian-source TDS evidence is the Form 16A (now Form 131 under the new Act) issued by the hotel, the Form 15CA acknowledgement, and the Form 15CB certificate. The reconciliation must keep this evidence trail in a separate outbound TDS register because there is no deductee-side cross-check via Form 168.",
          "article": "Section 413 of the Income Tax Act 2025: Hotel TDS Reconciliation on Foreign OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-section-413-hotel-foreign-ota-reconciliation"
        },
        {
          "q": "When are Form 15CA and Form 15CB required for an OTA commission remittance?",
          "a": "Form 15CA is required for any remittance to a non-resident that is chargeable to tax in India. Form 15CB — a chartered accountant's certificate — is required where a single remittance exceeds ₹5,00,000 in a financial year and the remittance is taxable. For most active hotels, monthly Booking.com or Agoda commission remittances cross this threshold quickly, so Form 15CB is the operating norm. The Form 15CA Part C and Form 15CB pair must reference the DTAA article, the treaty rate applied, the TRC, and Form 10F. The hotel's bank uses these forms to clear the outward remittance. A reconciliation that ignores 15CA/CB acknowledgements at month-end will leave a gap between the outbound TDS register and the bank-confirmed remittance amount.",
          "article": "Section 413 of the Income Tax Act 2025: Hotel TDS Reconciliation on Foreign OTA Commission",
          "url": "https://www.terra-insight.com/insights/tds-section-413-hotel-foreign-ota-reconciliation"
        }
      ]
    },
    "buyers-guide": {
      "label": "Buyer's Guide and Software Evaluation",
      "faqs": [
        {
          "q": "What should reconciliation software handle for TDS in India?",
          "a": "It must handle TDS net-of-gross receipt matching — where the invoice amount, TDS deducted at source, and net bank credit are three separate figures that all need to reconcile simultaneously. The software must match the TDS certificate reference, PAN of the deductor, the applicable section (194C, 194J, 194H, etc.), and deposit quarter to Form 26AS. Organisations on generic accounting platforms find that this three-way match requires manual adjustment outside the system — which reintroduces the same exception management overhead that automation is meant to eliminate.",
          "article": "Best Reconciliation Software for Indian Businesses in 2025: A CFO Buyer Guide",
          "url": "https://www.terra-insight.com/insights/best-reconciliation-software-india-2025"
        },
        {
          "q": "Does reconciliation software in India need to handle GSTR-2B specifically, or is generic GST reconciliation sufficient?",
          "a": "GSTR-2B is a supplier-level, GSTIN-level document with locking behaviour — ITC appearing in GSTR-2B for a period is locked to that period and cannot be claimed in an earlier period even if the invoice was dated earlier. Generic GST reconciliation tools that compare invoices to GSTR-2A (the older, non-locking document) will produce a different exception set than GSTR-2B-based matching. The Rule 36(4) ITC cap is calculated on GSTR-2B data, not GSTR-2A. Any reconciliation software evaluated for Indian ITC claiming must demonstrate GSTR-2B-specific matching, not just GST reconciliation in general.",
          "article": "Best Reconciliation Software for Indian Businesses in 2025: A CFO Buyer Guide",
          "url": "https://www.terra-insight.com/insights/best-reconciliation-software-india-2025"
        },
        {
          "q": "How quickly can reconciliation software be deployed for an Indian mid-market company?",
          "a": "A purpose-built platform with India-specific presets configures and deploys in 2 to 4 weeks. Week 1 covers ERP field mapping and data source connection. Week 2 is integration testing with live transaction data. Week 3 is a parallel run alongside the existing manual process. Week 4 is production cutover and sign-off. Generic or custom-built tools without India presets typically require 3 to 6 months of configuration and development, since the TDS, GST, and NACH matching logic must be built from scratch.",
          "article": "Best Reconciliation Software for Indian Businesses in 2025: A CFO Buyer Guide",
          "url": "https://www.terra-insight.com/insights/best-reconciliation-software-india-2025"
        },
        {
          "q": "What match rate should Indian enterprises expect from reconciliation software?",
          "a": "A realistic contract target for a purpose-built reconciliation platform is 70–85% automated match rate across all transaction types. This means 70–85% of transactions are confirmed without human intervention. The remaining 15–30% form a structured exception queue classified by variance code — FEE_DEDUCTION, TAX_DEDUCTION, ROUNDING, PARTIAL_PAYMENT, PENALTY_OR_INTEREST, or UNEXPLAINED — so exceptions are pre-sorted by resolution path rather than presented as an undifferentiated list of unmatched items.",
          "article": "Best Reconciliation Software for Indian Businesses in 2025: A CFO Buyer Guide",
          "url": "https://www.terra-insight.com/insights/best-reconciliation-software-india-2025"
        },
        {
          "q": "What does India data residency mean for reconciliation software, and why does it matter?",
          "a": "India data residency means the reconciliation platform stores all financial transaction data — bank statements, ERP records, TDS certificates, GSTR-2B data — within India-based data centre infrastructure. For listed companies and regulated entities (NBFCs, payment aggregators), RBI and SEBI guidelines require financial data to be stored within India. AWS Mumbai (ap-south-1) satisfies this requirement. Platforms hosted on generic EU or US infrastructure may not satisfy domestic data localisation obligations, creating compliance risk separate from the reconciliation function itself.",
          "article": "Best Reconciliation Software for Indian Businesses in 2025: A CFO Buyer Guide",
          "url": "https://www.terra-insight.com/insights/best-reconciliation-software-india-2025"
        },
        {
          "q": "Is reconciliation software suitable for multi-entity Indian organisations?",
          "a": "Yes, provided the platform supports entity-level separation within a single instance — separate ledgers, separate TDS reconciliation runs, separate GSTR-2B matching per GSTIN, but a consolidated exception dashboard across entities. CAs working with spreadsheet-based multi-entity clients flag that cross-entity reconciliation requires manual export-and-merge workflows across separate files, which introduces reconciliation errors and makes consolidated audit trails impossible. A multi-entity reconciliation platform eliminates the merge step and maintains entity-level audit integrity.",
          "article": "Best Reconciliation Software for Indian Businesses in 2025: A CFO Buyer Guide",
          "url": "https://www.terra-insight.com/insights/best-reconciliation-software-india-2025"
        },
        {
          "q": "What is the most important criterion when evaluating reconciliation software for India?",
          "a": "For most Indian enterprises, TDS compliance coverage is the highest-stakes criterion because errors in Form 26AS matching carry 18% per annum interest under Section 201 of the Income Tax Act, plus potential disallowance of expenses. Specifically, verify that the platform handles TDS net-of-gross matching — where TDS is deducted from gross invoice value but the bank credit arrives net — and supports all relevant sections (194C, 194J, 194H, 194I, 194Q) rather than a generic TDS flag.",
          "article": "How to Evaluate Reconciliation Software: A 10-Point Framework for Indian CFOs",
          "url": "https://www.terra-insight.com/insights/evaluate-reconciliation-software-india"
        },
        {
          "q": "How long should reconciliation software take to deploy in India?",
          "a": "A platform with pre-built India-specific presets and config-only deployment should be live in 2 to 4 weeks. Week 1 covers ERP field mapping and connector setup; Week 2 covers matching rule configuration and tolerance band calibration; Week 3 is a parallel run against the existing manual process; Week 4 is production cutover and sign-off. Any vendor quoting more than 8 weeks for standard deployment is likely building custom code — which extends timelines, increases cost, and creates maintenance dependency.",
          "article": "How to Evaluate Reconciliation Software: A 10-Point Framework for Indian CFOs",
          "url": "https://www.terra-insight.com/insights/evaluate-reconciliation-software-india"
        },
        {
          "q": "What security certifications should Indian enterprises require from reconciliation software vendors?",
          "a": "At minimum, require ISO 27001:2022 certification and AWS Mumbai (ap-south-1) data residency for most Indian enterprises. Regulated entities — NBFCs, payment aggregators, banks, and insurance companies — should additionally verify alignment with RBI's IT and cyber security frameworks, and SEBI's cloud framework for market intermediaries. DPDP Act 2023 compliance documentation should be requested from any vendor handling personal financial data of Indian customers.",
          "article": "How to Evaluate Reconciliation Software: A 10-Point Framework for Indian CFOs",
          "url": "https://www.terra-insight.com/insights/evaluate-reconciliation-software-india"
        },
        {
          "q": "What is the difference between config-only and custom-development reconciliation platforms?",
          "a": "A config-only platform deploys in 2 to 4 weeks by setting parameters — ERP field mappings, matching rules, tolerance bands, industry presets — without writing code. A custom-development platform requires developers to build or extend matching logic for each client, typically taking 3 to 6 months and creating ongoing maintenance dependency on the vendor. For Indian enterprises, config-only is preferable because regulatory changes (new GST rules, new TDS sections, revised NACH codes) are absorbed by the vendor through rule updates rather than requiring a new development engagement.",
          "article": "How to Evaluate Reconciliation Software: A 10-Point Framework for Indian CFOs",
          "url": "https://www.terra-insight.com/insights/evaluate-reconciliation-software-india"
        },
        {
          "q": "How do you evaluate matching engine quality in a reconciliation software demo?",
          "a": "Ask the vendor to run your own sample data — a month of bank statements and ERP exports — through their matching engine before you sign. A credible engine should achieve at minimum 70% match rate on your first pass, with exceptions classified by variance code (not just flagged as unmatched). Request to see the signal hierarchy applied: UTR should carry the highest priority because it is the most deterministic Indian payment identifier. If the vendor cannot demonstrate match rate improvement across multiple passes on your own data, their published benchmark numbers apply to a different dataset.",
          "article": "How to Evaluate Reconciliation Software: A 10-Point Framework for Indian CFOs",
          "url": "https://www.terra-insight.com/insights/evaluate-reconciliation-software-india"
        },
        {
          "q": "At what transaction volume should an Indian company move from Excel to reconciliation software?",
          "a": "The practical threshold is 2,000 transactions per month. Below 500 transactions with simple matching rules, Excel is workable. Between 500 and 2,000, error rates climb and audit trail gaps become a risk. Above 2,000, manual reconciliation in Excel typically consumes 40–60 staff hours per month and produces reconciliation sign-off delays that affect the monthly close cycle.",
          "article": "Excel vs Python vs Reconciliation Software: What Indian Finance Teams Should Use When",
          "url": "https://www.terra-insight.com/insights/excel-python-reconciliation-software-india"
        },
        {
          "q": "Can Python scripts handle TDS net-of-gross matching for Indian enterprises?",
          "a": "Python can handle TDS matching for stable, structured data, but it breaks when deduction rules change across sections (194C, 194J, 194H) or when gross receipt amounts vary by counterparty. India-specific scenarios — particularly TDS matched to Form 26AS entries with different PAN-TAN combinations — require logic that must be rebuilt every quarter if maintained in scripts.",
          "article": "Excel vs Python vs Reconciliation Software: What Indian Finance Teams Should Use When",
          "url": "https://www.terra-insight.com/insights/excel-python-reconciliation-software-india"
        },
        {
          "q": "Does GSTR-2B reconciliation require purpose-built software or can it be done in Excel?",
          "a": "GSTR-2B reconciliation can be started in Excel, but ITC eligibility under Rule 36(4) changes with each GST council notification, and GSTIN validation requires a live check against the GST portal. Excel has no mechanism for portal-integrated validation, which means eligibility decisions must be made manually. For businesses claiming more than ₹5 lakh per month in ITC, manual eligibility decisions create material audit exposure.",
          "article": "Excel vs Python vs Reconciliation Software: What Indian Finance Teams Should Use When",
          "url": "https://www.terra-insight.com/insights/excel-python-reconciliation-software-india"
        },
        {
          "q": "What audit trail does purpose-built reconciliation software produce that Excel cannot?",
          "a": "A purpose-built reconciliation platform logs every match decision, every manual override, the user identity who made each change, and the timestamp. This produces a structured, queryable audit trail that satisfies statutory auditors under the Companies Act and income tax proceedings. Excel workbooks log nothing by default, and even with manual change tracking, the audit trail is neither tamper-evident nor machine-queryable.",
          "article": "Excel vs Python vs Reconciliation Software: What Indian Finance Teams Should Use When",
          "url": "https://www.terra-insight.com/insights/excel-python-reconciliation-software-india"
        },
        {
          "q": "How long does it take to implement reconciliation software compared to building a Python solution in-house?",
          "a": "A configuration-based reconciliation platform typically deploys in 2–4 weeks from initial discovery to go-live. An in-house Python solution requires a developer, a testing cycle, and ongoing maintenance each time a bank statement format, GST rule, or ERP export format changes. The maintenance burden alone — typically 8–15 developer hours per quarter just to keep up with Indian regulatory format changes — often makes the build-vs-buy calculation straightforward.",
          "article": "Excel vs Python vs Reconciliation Software: What Indian Finance Teams Should Use When",
          "url": "https://www.terra-insight.com/insights/excel-python-reconciliation-software-india"
        },
        {
          "q": "What is the typical staff cost of manual reconciliation at a mid-size Indian enterprise?",
          "a": "A mid-size Indian enterprise running manual reconciliation across bank, TDS, and GSTR-2B streams typically spends 40–80 staff hours per month on reconciliation tasks. At a loaded cost of ₹600–₹1,200 per hour for qualified finance staff, the annual staff cost ranges from ₹2.9 lakh to ₹11.5 lakh — before accounting for the CA time required for sign-off review.",
          "article": "How to Justify Reconciliation Software to Your Board: A CFO Playbook",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-board-justification-india"
        },
        {
          "q": "How much TDS receivable is typically written off by Indian companies due to reconciliation failures?",
          "a": "The amount varies by industry, but companies processing more than ₹2 crore in TDS deductions annually and reconciling manually commonly write off 1–3% of TDS receivable due to unmatched Form 26AS entries. At ₹2 crore in annual TDS deductions, a 2% write-off rate is a ₹4 lakh direct P&L loss that disappears with correct reconciliation — this is the most concrete number in any board business case.",
          "article": "How to Justify Reconciliation Software to Your Board: A CFO Playbook",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-board-justification-india"
        },
        {
          "q": "What is the GST penalty rate for ITC claimed beyond the Rule 36(4) limit?",
          "a": "ITC claimed in excess of the Rule 36(4) provisional limit, or ITC not reversed when a supplier fails to file, attracts 18% annual interest under Section 50 of the CGST Act, plus potential penalty of up to 100% of the excess credit under Section 74. For enterprises claiming ₹50 lakh per month in ITC, a 5% eligibility error rate produces a ₹2.5 lakh monthly exposure — ₹30 lakh annualised at 18% interest.",
          "article": "How to Justify Reconciliation Software to Your Board: A CFO Playbook",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-board-justification-india"
        },
        {
          "q": "How does a delayed close cycle affect working capital for an Indian enterprise?",
          "a": "Each additional day in the monthly close cycle delays invoice approval, payment authorisation, and bank drawdown decisions. For a company with ₹10 crore in monthly operating payments, each day of close delay at 10% cost of capital is approximately ₹27,400 in working capital cost. A reconciliation-driven 3-day close delay costs roughly ₹82,000 per month — ₹9.8 lakh per year — in working capital friction alone.",
          "article": "How to Justify Reconciliation Software to Your Board: A CFO Playbook",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-board-justification-india"
        },
        {
          "q": "Can reconciliation software be scoped and deployed before board approval is final?",
          "a": "Unlike project implementations, a configuration-based reconciliation platform can be scoped to your specific use case in an initial discovery conversation. This means the business case presented to the board can include a specific deployment timeline, a projected match rate improvement based on a sample data review, and a defined go-live milestone — all before the approval is granted. The 2–4 week deployment window means the board can approve in one cycle and expect live results before the next quarterly close.",
          "article": "How to Justify Reconciliation Software to Your Board: A CFO Playbook",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-board-justification-india"
        },
        {
          "q": "How long does reconciliation software implementation typically take for an Indian enterprise?",
          "a": "A configuration-based reconciliation platform typically deploys in 2–4 weeks from the initial discovery conversation to go-live for a single-use case (for example, bank reconciliation or TDS reconciliation). A multi-stream deployment covering bank, TDS, GSTR-2B, and payment gateway reconciliation typically completes within 6–8 weeks. The 30-60-90 day framework applies to deployments where multiple reconciliation streams are configured, tested in parallel, and signed off sequentially.",
          "article": "Reconciliation Software Implementation: What to Expect in 30-60-90 Days",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-implementation-india"
        },
        {
          "q": "What data does an Indian enterprise need to prepare before reconciliation software implementation begins?",
          "a": "The minimum data requirement for an implementation kick-off is: 3 months of historical transaction data in the source formats used (MT940 or CSV bank statements, ERP export in the standard format, TDS challan CSVs, GSTR-2B JSON or Excel exports), a list of all counterparties and their PAN/GSTIN details, and sample exception cases from the current manual process. Data quality issues — inconsistent narrations, missing UTRs, duplicate entries — are better discovered during the review phase than after configuration begins.",
          "article": "Reconciliation Software Implementation: What to Expect in 30-60-90 Days",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-implementation-india"
        },
        {
          "q": "What is the difference between a configuration-based implementation and a custom development implementation?",
          "a": "A configuration-based implementation adjusts matching rules, tolerance thresholds, variance codes, and workflow routing within the platform's existing architecture — no code is written. A custom development implementation builds or modifies the software itself for the client's specific requirements. Configuration implementations are faster (2–4 weeks vs. 3–6 months), more predictable in timeline, and less expensive to maintain. For Indian enterprises, the key advantage is that configuration changes can be made in hours when matching rules need to be updated for a regulatory change — a code change requires a development cycle.",
          "article": "Reconciliation Software Implementation: What to Expect in 30-60-90 Days",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-implementation-india"
        },
        {
          "q": "What causes reconciliation software implementations in India to run over timeline?",
          "a": "The three most common causes of implementation delays for Indian enterprises are: (1) ERP export formats that are non-standard and require transformation before the matching engine can ingest them — this is the most common cause; (2) bank statement narration inconsistencies across HDFC, ICICI, and SBI formats that require custom normalisation rules; and (3) incomplete counterparty master data that prevents PAN/GSTIN-level matching for TDS and GST streams. All three can be identified and mitigated during the data quality review in days 1–30.",
          "article": "Reconciliation Software Implementation: What to Expect in 30-60-90 Days",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-implementation-india"
        },
        {
          "q": "How does the parallel run phase work, and what sign-off criteria should it meet?",
          "a": "During the parallel run phase (typically days 31–60), the reconciliation engine runs against live transaction data at the same time the existing manual process continues. The parallel run produces side-by-side match outputs for comparison. Sign-off criteria should include: match rate on the configured streams meets the contractual target (70–85%), exception volumes are stable and reviewable within the exception workflow, and the team operating the dashboard can process the daily exception queue without vendor support. The parallel run should run for at least two complete monthly close cycles before go-live sign-off.",
          "article": "Reconciliation Software Implementation: What to Expect in 30-60-90 Days",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-implementation-india"
        },
        {
          "q": "How do I calculate the staff cost of manual reconciliation for an ROI model?",
          "a": "Identify the number of finance team members involved in reconciliation across all types — bank, TDS, GSTR-2B, NACH, platform settlements. Estimate the hours per month each spends on reconciliation tasks: data downloads, VLOOKUP/formula work, exception investigation, follow-up with vendors or banks. Multiply hours by fully-loaded cost per hour (salary plus overhead, typically 1.4–1.6x gross salary). For a mid-size Indian enterprise with 3 finance staff spending 40% of their time on reconciliation, the annual staff cost of reconciliation often ranges from ₹18 to ₹36 lakh, depending on seniority and location.",
          "article": "Reconciliation Software ROI: How Indian Finance Teams Build the Business Case",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-roi-india"
        },
        {
          "q": "What is reconciliation debt, and how does it translate into a rupee figure?",
          "a": "Reconciliation debt is the accumulation of financial mismatches that have not been resolved and represent either recoverable value or compliance liability. In India, the two largest categories are TDS receivable not reflected in Form 26AS (value: tax credit that cannot be claimed in the income tax return, attracting interest at 18% p.a. if a demand results) and ITC not claimed because a vendor invoice did not appear in GSTR-2B (value: the GST amount, which must either be forgone or pursued through a vendor correction). For a company with ₹50 crore annual vendor spend, even 0.5% unreconciled ITC represents ₹25 lakh of potential leakage per year.",
          "article": "Reconciliation Software ROI: How Indian Finance Teams Build the Business Case",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-roi-india"
        },
        {
          "q": "How does slow reconciliation affect the financial close calendar?",
          "a": "Reconciliation exceptions outstanding at month-end prevent closure of the bank ledger, the TDS receivable ledger, and the ITC ledger. Each open exception must be investigated, resolved, or provisioned before the trial balance is reliable. A finance team processing 10,000 monthly transactions manually typically spends 8–12 days resolving exceptions before the close can proceed. Automated reconciliation that reduces exceptions to a classified queue — where ROUNDING exceptions are bulk-approved, TAX_DEDUCTION exceptions are pre-understood, and UNEXPLAINED exceptions are the genuine investigation cases — compresses this to 1–2 days of targeted exception review.",
          "article": "Reconciliation Software ROI: How Indian Finance Teams Build the Business Case",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-roi-india"
        },
        {
          "q": "What is audit penalty exposure from unreconciled TDS or ITC positions?",
          "a": "Under Section 201 of the Income Tax Act, an entity assessed as an assessee-in-default for TDS non-deduction or short-deduction faces interest at 1% per month from the due date of deduction, plus interest at 1.5% per month from the date of deduction to the date of actual deposit. A penalty equal to the TDS amount can also be levied under Section 271C. For ITC, Section 73 of the CGST Act imposes a 10% penalty on the disputed ITC amount, or 100% if fraud is established. Organisations that reconcile TDS and ITC positions quarterly rather than monthly face a compounding exposure that grows with each missed period.",
          "article": "Reconciliation Software ROI: How Indian Finance Teams Build the Business Case",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-roi-india"
        },
        {
          "q": "Does a reconciliation software ROI model need to account for IT infrastructure cost?",
          "a": "For cloud-deployed reconciliation software, no significant IT infrastructure investment is required — the platform runs on the vendor's infrastructure (AWS Mumbai in the case of ISO 27001:2022-certified Indian platforms) and is accessed via web interface. The implementation cost is configuration time (typically 2–4 weeks at the vendor's standard professional services rate) plus internal effort for data mapping and parallel run validation. The ROI model should include these implementation costs in the investment figure and offset them against the first year's savings in staff time, reconciliation debt recovery, and penalty risk reduction.",
          "article": "Reconciliation Software ROI: How Indian Finance Teams Build the Business Case",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-roi-india"
        },
        {
          "q": "When does the business case for reconciliation software become self-evident in India?",
          "a": "The business case is typically self-evident above three thresholds: 10,000 monthly transactions across all reconciliation types, more than one compliance reconciliation obligation (e.g., both TDS and GSTR-2B), and a quarterly filing deadline where exception backlogs are visible. Below these thresholds, the staff cost savings may not justify a dedicated platform. Above them, the combination of staff cost reduction, TDS and ITC debt recovery, audit penalty risk reduction, and close cycle compression typically yields payback in 6 to 18 months — before accounting for the risk mitigation value of having an immutable audit trail.",
          "article": "Reconciliation Software ROI: How Indian Finance Teams Build the Business Case",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-roi-india"
        },
        {
          "q": "Can SAP or Oracle handle bank reconciliation for Indian enterprises without additional software?",
          "a": "SAP and Oracle both include bank reconciliation modules that handle statement import and basic ledger matching. However, producing a reconciled view across bank statements, TDS receivables from Form 26AS, GST ITC from GSTR-2B, and NACH batch returns requires manual steps outside the standard SAP FICO or Oracle Financials workflows. India-specific exception types — TDS net-of-gross, NACH bounce disaggregation, GST TCS under Section 52 — are not natively classified by the standard ERP matching logic, requiring manual adjustment for each occurrence.",
          "article": "Reconciliation Software vs ERP: Why Indian Finance Teams Need Both",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-vs-erp-india"
        },
        {
          "q": "What does reconciliation software do that an ERP cannot?",
          "a": "Reconciliation software ingests data from external sources — bank MT940 files, GSTN JSON, NPCI NACH return files, payment gateway settlement CSVs, TRACES Form 26AS — normalises them into a common schema, and applies multi-signal matching against ERP ledger entries. It produces a variance code for each unmatched item (FEE_DEDUCTION, TAX_DEDUCTION, ROUNDING, PARTIAL_PAYMENT, PENALTY_OR_INTEREST, UNEXPLAINED), routes exceptions to the correct reviewer, and writes cleared items back to the ERP. These are not capabilities built into standard ERP modules — they operate as a matching layer on top of the ERP's recorded data.",
          "article": "Reconciliation Software vs ERP: Why Indian Finance Teams Need Both",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-vs-erp-india"
        },
        {
          "q": "How does the reconciliation software write cleared entries back to SAP or Tally?",
          "a": "Once the reconciliation engine confirms a match — either through exact matching, composite-signal matching with confidence above threshold, or human approval of a classified exception — the cleared entry is posted back to the ERP via the configured integration. For SAP, this uses an RFC or BAPI call to post a clearing document in the relevant FI module. For Tally, the cleared journal entry is written as an import file. This writeback step closes the loop: the ERP's open items are cleared, and the reconciliation audit trail records the match reference.",
          "article": "Reconciliation Software vs ERP: Why Indian Finance Teams Need Both",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-vs-erp-india"
        },
        {
          "q": "Does reconciliation software replace the ERP general ledger?",
          "a": "No. Reconciliation software does not replace the ERP general ledger — it operates on top of it. The ERP remains the system of record for all ledger entries, vouchers, and financial statements. Reconciliation software's role is to verify that what the ERP recorded matches what external sources (banks, tax portals, payment gateways) confirm actually happened, and to classify and route the differences. The two systems have complementary functions; removing either creates a gap in the financial control chain.",
          "article": "Reconciliation Software vs ERP: Why Indian Finance Teams Need Both",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-vs-erp-india"
        },
        {
          "q": "For a mid-market Indian company on Tally, is reconciliation software relevant?",
          "a": "Yes, particularly for TDS and GSTR-2B reconciliation. A company with 500 or more transactions per month on Tally faces the same India-specific compliance challenges as a large enterprise on SAP: TDS deducted by customers must be traced to Form 26AS each quarter; ITC claimed in GSTR-3B must be verified against GSTR-2B; NACH debits must be reconciled against bank credits. Tally does not have native connectors to TRACES or the GST portal. Reconciliation software handles the ingestion, matching, and exception classification — Tally remains the accounting system of record.",
          "article": "Reconciliation Software vs ERP: Why Indian Finance Teams Need Both",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-vs-erp-india"
        },
        {
          "q": "What is the most important question to ask a reconciliation vendor in India about TDS handling?",
          "a": "The most diagnostic question is: 'How does your platform handle TDS net-of-gross receipt matching when the same counterparty deducts under multiple sections in the same month?' A vendor with genuine TDS matching capability will explain how section-level deduction rates (194C at 1–2%, 194J at 10%, 194H at 5%) are applied separately before the net receipt is matched to the bank credit. A vendor without India-specific TDS logic will describe a generic tolerance match that treats TDS as a rounding difference — which produces mismatch on multi-section deductions.",
          "article": "15 Questions to Ask When Selecting a Reconciliation Vendor in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-vendor-selection-questions-india"
        },
        {
          "q": "Should a reconciliation vendor be able to commit to a contractual match rate?",
          "a": "Yes. A vendor with a patented matching engine and a defined pipeline architecture should be able to commit to a match rate target range — typically 70–85% — based on a review of a sample of the client's actual transaction data. This commitment should appear in the contract as a measurable service level. A vendor who declines to commit to a match rate, or who only expresses the commitment as a best-efforts statement, is signalling uncertainty about the engine's performance on Indian transaction data.",
          "article": "15 Questions to Ask When Selecting a Reconciliation Vendor in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-vendor-selection-questions-india"
        },
        {
          "q": "How should a CFO evaluate a vendor's answer to the question about use case scoping?",
          "a": "A vendor who conducts a structured discovery conversation to map the client's transaction types, matching rule requirements, and India compliance scope before configuring the engine will achieve higher match rates than one who delivers a generic setup. When evaluating the answer, listen for whether the vendor distinguishes between different matching streams (bank vs. TDS vs. GSTR-2B), asks about counterparty volume and PAN/GSTIN completeness, and sets a match rate expectation based on the specific data — not a generic claim. Generic answers to the scoping question are a proxy for generic configuration.",
          "article": "15 Questions to Ask When Selecting a Reconciliation Vendor in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-vendor-selection-questions-india"
        },
        {
          "q": "What ERP connectors should a reconciliation vendor support natively for Indian enterprises?",
          "a": "The four ERP systems with the highest penetration among mid-size Indian enterprises are SAP Business One / S/4HANA, Oracle NetSuite, Tally Prime, and Busy Accounting. A vendor with native connectors for all four avoids the custom transformation step that most commonly delays implementations. Beyond ERP connectors, Indian enterprises should verify native support for bank statement ingestion (MT940 from HDFC, ICICI, SBI, Axis, Kotak), GST portal export (GSTR-2B JSON), TRACES challan CSV, and payment gateway settlement files from Razorpay, Cashfree, and PayU.",
          "article": "15 Questions to Ask When Selecting a Reconciliation Vendor in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-vendor-selection-questions-india"
        },
        {
          "q": "What is the difference between a rule-based and a composite-signal matching engine, and why does it matter for Indian transaction data?",
          "a": "A rule-based matching engine matches transactions when they satisfy a defined rule exactly — same amount, same reference, same date. It fails when Indian transaction data introduces partial references, truncated UTRs, or TDS net-of-gross differences that prevent exact matches. A composite-signal engine assigns confidence scores to multiple matching signals, with UTR as the strongest signal, followed by partial payment reference, counterparty name, and date, and matches transactions that exceed a confidence threshold even when no single signal is an exact match. For Indian enterprises where UTR-present-but-narration-inconsistent is a common pattern, a composite-signal engine is required to achieve match rates above 70%.",
          "article": "15 Questions to Ask When Selecting a Reconciliation Vendor in India",
          "url": "https://www.terra-insight.com/insights/reconciliation-vendor-selection-questions-india"
        },
        {
          "q": "Does SaaS reconciliation software on AWS Mumbai satisfy RBI data localisation requirements?",
          "a": "For most Indian enterprises, yes. RBI's 2018 circular on storage of payment system data mandates that data be stored only in systems located in India. AWS Mumbai (ap-south-1) is a data centre region physically located in India. A SaaS platform configured to store and process data exclusively in ap-south-1 — with no data transfer to non-India regions — satisfies this requirement. Payment system operators and payment aggregators regulated under the Payment Aggregator guidelines should verify the vendor's region configuration documentation before deployment.",
          "article": "SaaS vs On-Premise Reconciliation Software: What Indian Enterprises Should Choose",
          "url": "https://www.terra-insight.com/insights/saas-vs-on-premise-reconciliation-india"
        },
        {
          "q": "Which Indian enterprises must use on-premise or private cloud for reconciliation software?",
          "a": "The primary categories are: scheduled banks regulated by RBI under the IT and Cyber Security Framework, insurance companies regulated by IRDAI with specific data residency mandates, PSUs operating under government data sovereignty policies, and stock brokers or market intermediaries subject to SEBI's cloud framework. For entities in these categories, on-premise or private cloud (dedicated VPC within AWS Mumbai) is the compliant architecture. For all other Indian enterprises — NBFCs, mid-market manufacturers, IT services firms, e-commerce companies — SaaS on AWS Mumbai is both compliant and operationally preferable.",
          "article": "SaaS vs On-Premise Reconciliation Software: What Indian Enterprises Should Choose",
          "url": "https://www.terra-insight.com/insights/saas-vs-on-premise-reconciliation-india"
        },
        {
          "q": "What is the total cost of ownership difference between SaaS and on-premise reconciliation software?",
          "a": "On-premise deployment requires: server hardware (typically ₹15–30 lakh for an enterprise setup), annual maintenance contracts, internal IT staff time for patching and updates, database administration, and disaster recovery infrastructure. SaaS deployment eliminates all of these in exchange for a subscription fee. Over a 3-year period, on-premise TCO is typically 2 to 4 times higher than SaaS TCO for mid-market organisations processing under 5 million transactions per month, because hardware and IT staff costs do not scale proportionally with usage.",
          "article": "SaaS vs On-Premise Reconciliation Software: What Indian Enterprises Should Choose",
          "url": "https://www.terra-insight.com/insights/saas-vs-on-premise-reconciliation-india"
        },
        {
          "q": "How does the DPDP Act 2023 affect the choice between SaaS and on-premise reconciliation software?",
          "a": "The Digital Personal Data Protection Act 2023 applies to entities processing personal digital data of Indian residents. Financial transaction data containing PAN numbers, Aadhaar references, or bank account details falls within its scope. Under the Act, data fiduciaries must implement reasonable security safeguards. For SaaS vendors, ISO 27001:2022 certification and AWS Mumbai residency are evidence of such safeguards. For on-premise deployments, the enterprise itself assumes full responsibility for implementing equivalent controls — without the vendor's certification coverage.",
          "article": "SaaS vs On-Premise Reconciliation Software: What Indian Enterprises Should Choose",
          "url": "https://www.terra-insight.com/insights/saas-vs-on-premise-reconciliation-india"
        },
        {
          "q": "How long does SaaS reconciliation software deployment take compared to on-premise?",
          "a": "SaaS deployment on a config-only platform with India presets typically takes 2 to 4 weeks: connector setup and data source mapping in Week 1, matching rule and tolerance configuration in Week 2, parallel run validation in Week 3, production cutover in Week 4. On-premise deployment adds infrastructure provisioning (2 to 4 weeks for server procurement and setup) and network security configuration before any application deployment begins. Private cloud (dedicated VPC) deployment falls between the two: infrastructure is vendor-managed but provisioning takes 1 to 2 additional weeks compared to shared SaaS.",
          "article": "SaaS vs On-Premise Reconciliation Software: What Indian Enterprises Should Choose",
          "url": "https://www.terra-insight.com/insights/saas-vs-on-premise-reconciliation-india"
        },
        {
          "q": "Does ISO 27001 certification guarantee that a reconciliation vendor's platform is secure?",
          "a": "ISO 27001:2022 certification confirms that the vendor has an audited information security management system covering the scoped environment, but the scope matters. A certification that covers only the vendor's corporate office, and not the reconciliation application and its data hosting environment, provides no assurance about the application itself. Always verify that the certification scope explicitly includes the reconciliation platform and the infrastructure on which it runs.",
          "article": "Security Checklist for Reconciliation Software: What Indian Enterprises Must Verify",
          "url": "https://www.terra-insight.com/insights/security-checklist-reconciliation-software-india"
        },
        {
          "q": "What does India data residency mean for reconciliation software, and why does it matter?",
          "a": "Data residency means that financial data — bank statements, TDS certificates, settlement reports — is stored and processed on servers physically located in India. RBI's Master Direction on IT Governance requires regulated entities to ensure data localisation for critical financial data. For non-RBI-regulated enterprises, the DPDP Act 2023 creates additional obligations around cross-border data transfers. An India-hosted deployment on AWS Mumbai, for example, satisfies both requirements and avoids cross-border transfer complexity.",
          "article": "Security Checklist for Reconciliation Software: What Indian Enterprises Must Verify",
          "url": "https://www.terra-insight.com/insights/security-checklist-reconciliation-software-india"
        },
        {
          "q": "What audit trail standard should a reconciliation platform meet for income tax proceedings?",
          "a": "The Income Tax Act and the Companies Act both require that books of account and supporting records be maintained in a form that can be produced during an audit or assessment proceeding. For reconciliation records, this means the audit trail must be user-attributed (who matched or overrode each entry), timestamped (when each action occurred), tamper-evident (the trail cannot be modified retroactively), and queryable (an auditor can search by date range, user, or transaction reference). Platforms that log actions only in application logs, without a structured queryable interface, typically do not satisfy the evidentiary standard.",
          "article": "Security Checklist for Reconciliation Software: What Indian Enterprises Must Verify",
          "url": "https://www.terra-insight.com/insights/security-checklist-reconciliation-software-india"
        },
        {
          "q": "How does the DPDP Act 2023 affect reconciliation software procurement in India?",
          "a": "The Digital Personal Data Protection Act 2023 classifies individuals' financial data as personal data. When reconciliation software processes bank statements or TDS certificates containing individual account holder or deductee details, the enterprise deploying the software is a data fiduciary, and the software vendor is a data processor. The enterprise must ensure the vendor operates under a lawful data processing agreement, implements adequate security safeguards, and does not transfer personal data outside India without meeting the DPDP Act's cross-border transfer conditions.",
          "article": "Security Checklist for Reconciliation Software: What Indian Enterprises Must Verify",
          "url": "https://www.terra-insight.com/insights/security-checklist-reconciliation-software-india"
        },
        {
          "q": "What penetration testing frequency should a reconciliation software vendor demonstrate?",
          "a": "Enterprise-grade security practice for financial applications requires at minimum annual penetration testing by an independent CERT-In empanelled auditor, with results disclosed to prospective customers under NDA. Vendors processing significant financial data volumes should conduct testing twice yearly. Ask specifically for the date of the most recent penetration test, the scope of the test (black box, white box, or grey box), and whether critical or high findings from the last test have been remediated before deployment.",
          "article": "Security Checklist for Reconciliation Software: What Indian Enterprises Must Verify",
          "url": "https://www.terra-insight.com/insights/security-checklist-reconciliation-software-india"
        }
      ]
    },
    "erp-integrations": {
      "label": "ERP Integrations for Reconciliation",
      "faqs": [
        {
          "q": "What data layer does Busy Accounting Software use, and how does that affect reconciliation?",
          "a": "Busy uses a DBF (dBASE) file-based data layer up to Busy 21, and a proprietary indexed binary format from Busy 21 onwards. Each company is a separate folder with DBF tables like MASTERS.DBF, VOUCHERS.DBF, and GSTINFO.DBF. Direct DBF read via ODBC or third-party DBF readers is technically possible but not supported by Busy Infotech. The sanctioned export path is ASCII/XML export from within the Busy UI — limiting real-time reconciliation to scheduled extracts rather than continuous sync.",
          "article": "Busy Accounting Software Reconciliation in India: DBF Data, Multi-Company, and Import-Export Patterns",
          "url": "https://www.terra-insight.com/insights/busy-software-reconciliation-india"
        },
        {
          "q": "Does Busy Accounting Software have native GSTR-2A/2B reconciliation?",
          "a": "Yes. Busy Professional Edition and Enterprise Edition include a GST Reconciliation module that imports GSTR-2A and GSTR-2B JSON from the GST portal and matches against the purchase register on GSTIN + invoice number + invoice date + taxable value. The module was introduced in Busy 18 and refined in Busy 21 with support for debit note and credit note matching. At volumes below 300 invoices/month, it is adequate; above that, GSTIN typo and timing-mismatch exceptions become burdensome without external handling.",
          "article": "Busy Accounting Software Reconciliation in India: DBF Data, Multi-Company, and Import-Export Patterns",
          "url": "https://www.terra-insight.com/insights/busy-software-reconciliation-india"
        },
        {
          "q": "How does Busy handle multi-company or multi-branch consolidation for reconciliation?",
          "a": "Busy supports multi-company operation where each company is a separate data directory. The consolidation module in Busy Enterprise allows grouping of companies for consolidated balance sheet and P&L. For reconciliation specifically, the standard pattern is ASCII or XML export from each branch/company on a scheduled basis (daily or weekly), followed by consolidation in an external layer. Busy has no built-in cross-company bank or GST reconciliation — it is single-company within each data folder.",
          "article": "Busy Accounting Software Reconciliation in India: DBF Data, Multi-Company, and Import-Export Patterns",
          "url": "https://www.terra-insight.com/insights/busy-software-reconciliation-india"
        },
        {
          "q": "What import/export formats does Busy Accounting Software support?",
          "a": "Busy supports ASCII (fixed-width and delimited), XML, and Excel import/export for masters (ledger, item, party), vouchers (sale, purchase, payment, receipt), and report output. The ASCII format is documented in the Busy Help and is the most reliable for bulk import back into Busy. XML is used primarily for GST return data exchange. Excel import is convenient for small-volume master creation but not recommended for transaction volumes above 500 rows per file.",
          "article": "Busy Accounting Software Reconciliation in India: DBF Data, Multi-Company, and Import-Export Patterns",
          "url": "https://www.terra-insight.com/insights/busy-software-reconciliation-india"
        },
        {
          "q": "What is the typical reconciliation integration pattern for Busy Accounting Software users in India?",
          "a": "The standard pattern is: (1) scheduled ASCII or XML export from each Busy company directory at end of day, (2) SFTP drop to a shared location, (3) ingestion by an external reconciliation layer that handles bank, TDS, and GSTR-2B matching across all entities, (4) exception resolution outside Busy, and (5) manual or ASCII-import posting of cleared status back into Busy vouchers. High-volume CA firms managing 20+ client companies on Busy typically run this as an overnight batch.",
          "article": "Busy Accounting Software Reconciliation in India: DBF Data, Multi-Company, and Import-Export Patterns",
          "url": "https://www.terra-insight.com/insights/busy-software-reconciliation-india"
        },
        {
          "q": "What India localisation does Microsoft Dynamics 365 Business Central include?",
          "a": "Dynamics 365 Business Central (version 23 / 2023 Release Wave 2 onwards) includes Indian GST tax determination, TDS deduction under major sections (194C, 194J, 194I, 194Q, 195), GST e-invoice generation with IRP integration, and Form 26Q quarterly TDS return output. The India localisation is delivered as the IN_Localization extension and is activated through the Feature Management page. GSTR-2B reconciliation against the purchase register and Form 26AS matching are not part of the localisation.",
          "article": "Microsoft Dynamics 365 Reconciliation in India: Business Central and Finance & Operations Localisation",
          "url": "https://www.terra-insight.com/insights/microsoft-dynamics-365-reconciliation-india"
        },
        {
          "q": "How does D365 Finance & Operations handle GST in India?",
          "a": "D365 Finance & Operations (formerly AX) has deeper India localisation than Business Central — the Tax Engine module supports multi-tax determination, GST TCS under 194O, ISD (Input Service Distributor) allocation, and GSTR-1 return generation as JSON. e-invoice integration via GSP (GST Suvidha Provider) is supported through partner connectors. GSTR-2B JSON matching against the purchase register is available in recent releases (10.0.34+) but requires manual JSON download and upload.",
          "article": "Microsoft Dynamics 365 Reconciliation in India: Business Central and Finance & Operations Localisation",
          "url": "https://www.terra-insight.com/insights/microsoft-dynamics-365-reconciliation-india"
        },
        {
          "q": "What are the integration options between D365 and an external reconciliation layer?",
          "a": "Three patterns are common: (1) OData REST API — D365 exposes standard entities (VendInvoice, GeneralJournalAccountEntry, BankStatementLine) that an external tool can query with OAuth 2.0, (2) Data Management Framework (DMF) — batch CSV or Excel export/import via the DMF job scheduler, and (3) Dataverse integration for Business Central — entities synchronise to Dataverse from which Power Automate or external tools can consume them. Most India deployments use DMF for scheduled export and OData for write-back.",
          "article": "Microsoft Dynamics 365 Reconciliation in India: Business Central and Finance & Operations Localisation",
          "url": "https://www.terra-insight.com/insights/microsoft-dynamics-365-reconciliation-india"
        },
        {
          "q": "Can Dynamics 365 Business Central ingest NACH batch files and bank statements automatically?",
          "a": "Business Central's Bank Reconciliation with Auto Match supports MT940 and BAI2 file import via the Bank Statement Import functionality, and a single NACH batch credit appears as one line on the bank statement. The NPCI response file listing each mandate's outcome with return codes (R01–R99) is not natively parsed. Disaggregation of the batch into mandate-level outcomes and posting cleared status back to the customer ledgers requires an external layer or custom AL extension.",
          "article": "Microsoft Dynamics 365 Reconciliation in India: Business Central and Finance & Operations Localisation",
          "url": "https://www.terra-insight.com/insights/microsoft-dynamics-365-reconciliation-india"
        },
        {
          "q": "Does the Microsoft Dynamics 365 India localisation support Form 26AS matching?",
          "a": "No. The D365 India localisation posts TDS payable on deduction and tracks challan numbers against section codes, but it does not connect to TRACES to download Form 26AS or match TDS receivable against the external record. For TDS receivable reconciliation under sections where customers deduct on the entity's receivables (194C, 194J, 194Q, 194O, 194H), Form 26AS export and matching happen outside D365. This is true for both Business Central and Finance & Operations as of release 10.0.40.",
          "article": "Microsoft Dynamics 365 Reconciliation in India: Business Central and Finance & Operations Localisation",
          "url": "https://www.terra-insight.com/insights/microsoft-dynamics-365-reconciliation-india"
        },
        {
          "q": "What modules does the Odoo India localisation include?",
          "a": "Odoo's India fiscal localisation (available from Odoo 15 onwards and complete in Odoo 17) includes l10n_in (base chart of accounts and tax structure), l10n_in_gst (GST tax determination and return generation), l10n_in_edi (e-invoice IRN generation via IRP), l10n_in_hr_payroll (Indian payroll with TDS on salary under Section 192), and l10n_in_reports (GSTR-1, GSTR-3B). TDS on vendor payments under 194C, 194J etc. is available via partner modules or Odoo Studio customisation, not the core localisation.",
          "article": "Odoo Reconciliation in India: Localisation, Community vs Enterprise, and Integration Paths",
          "url": "https://www.terra-insight.com/insights/odoo-reconciliation-india"
        },
        {
          "q": "What are the differences between Odoo Community and Odoo Enterprise for India reconciliation?",
          "a": "Odoo Community (free) includes the base l10n_in module and basic GST tax determination but lacks the e-invoice module, automated GSTR-1 JSON generation, and the Bank Reconciliation screen's AI-suggestion feature. Odoo Enterprise (paid, approximately ₹31/user/month for India as of 2026) adds l10n_in_edi, GSTR-1/3B JSON, the advanced bank reconciliation UI, and the Accounting app's document recognition. For India-scale reconciliation, Enterprise is the practical starting point.",
          "article": "Odoo Reconciliation in India: Localisation, Community vs Enterprise, and Integration Paths",
          "url": "https://www.terra-insight.com/insights/odoo-reconciliation-india"
        },
        {
          "q": "How does Odoo's bank reconciliation feature work?",
          "a": "Odoo Enterprise's bank reconciliation (Accounting → Bank) ingests bank statements via CSV, OFX, QIF, CAMT.053, or direct bank feed (Salt Edge / Yodlee connectors). Each statement line is matched against open customer and vendor invoices using a model-based rule engine — reference, amount, partner name, and date are the signals. Reconciliation models can be configured per bank account for repetitive transactions like bank charges or interest. Line-level acceptance is manual by default; auto-reconciliation is possible but requires rule tuning to avoid false positives.",
          "article": "Odoo Reconciliation in India: Localisation, Community vs Enterprise, and Integration Paths",
          "url": "https://www.terra-insight.com/insights/odoo-reconciliation-india"
        },
        {
          "q": "How is Odoo typically integrated with an external reconciliation layer in India?",
          "a": "Odoo exposes XML-RPC at /xmlrpc/2/object (and JSON-RPC at /jsonrpc) for all models including account.move (journal entries), account.move.line (GL lines), account.bank.statement.line (bank transactions), and res.partner (parties). An external reconciliation layer authenticates with API key (Odoo 14+) or username/password, reads open items, processes matching outside Odoo, and writes cleared status back by creating account.payment and account.move.line reconciliation records via XML-RPC. Rate limits depend on the hosting: Odoo.sh caps at 100 requests/minute per instance.",
          "article": "Odoo Reconciliation in India: Localisation, Community vs Enterprise, and Integration Paths",
          "url": "https://www.terra-insight.com/insights/odoo-reconciliation-india"
        },
        {
          "q": "Does Odoo handle GSTR-2B matching for Indian purchase reconciliation?",
          "a": "Odoo Enterprise's India localisation includes GSTR-1 and GSTR-3B return generation but does not include native GSTR-2B reconciliation against the purchase register as of Odoo 17. Some community partner modules (from Indian Odoo consultants like Cybrosys, Serpent Consulting) add GSTR-2B import and matching. For production-grade Indian GST reconciliation at 300+ invoices/month, the standard pattern is to export the Odoo purchase register via XML-RPC and match against GSTR-2B JSON in an external layer.",
          "article": "Odoo Reconciliation in India: Localisation, Community vs Enterprise, and Integration Paths",
          "url": "https://www.terra-insight.com/insights/odoo-reconciliation-india"
        },
        {
          "q": "Does Oracle Fusion Cloud ERP have a direct GSTN API integration?",
          "a": "No. Oracle Fusion Cloud ERP's India Localization module (release 23D through 24C) supports GST tax determination and GSTR-1 outward supply report generation, but it does not pull GSTR-2B JSON from the GST portal automatically. Monthly GSTR-2B reconciliation requires a manual JSON download from gst.gov.in and upload into the GST Reconciliation dashboard — or a file handoff to an external reconciliation layer.",
          "article": "Oracle Fusion Cloud ERP Reconciliation in India: What Localisation Does and Doesn't Cover",
          "url": "https://www.terra-insight.com/insights/oracle-fusion-reconciliation-india"
        },
        {
          "q": "How does Oracle Fusion handle TDS under the Indian Income Tax Act?",
          "a": "The India Localization module supports withholding tax codes for TDS sections 194C, 194J, 194I, 194Q, 195 and others. TDS is deducted at AP invoice validation, posted to the TDS payable account, and reported via the Withholding Tax Reporting module. Form 26Q XML file generation is supported for quarterly TDS return filing. Form 26AS matching, however, is not — that requires an external step.",
          "article": "Oracle Fusion Cloud ERP Reconciliation in India: What Localisation Does and Doesn't Cover",
          "url": "https://www.terra-insight.com/insights/oracle-fusion-reconciliation-india"
        },
        {
          "q": "What Oracle Fusion tables and reports are used for reconciliation data extraction?",
          "a": "Key data sources are AP_INVOICE_DISTRIBUTIONS_ALL (AP lines with withholding), XLA_AE_LINES (subledger accounting journal lines), GL_JE_LINES (general ledger entries), and the JG_ZZ_* tables for India-specific tax data. Extraction happens via OTBI (Oracle Transactional BI) reports, BI Publisher templates, or BICC extracts scheduled through the Enterprise Scheduler.",
          "article": "Oracle Fusion Cloud ERP Reconciliation in India: What Localisation Does and Doesn't Cover",
          "url": "https://www.terra-insight.com/insights/oracle-fusion-reconciliation-india"
        },
        {
          "q": "Can Oracle Fusion ingest payment gateway settlement files from Razorpay or PayU?",
          "a": "Not natively. Oracle Fusion Cash Management ingests bank statements via BAI2 or camt.053 at the bank-account level, but payment gateway settlement files (Razorpay net payout CSV, PayU consolidated settlement, Cashfree vendor split) are not recognised by Cash Management. Gateway reconciliation requires either a custom ingestion via FBDI file import or an external reconciliation layer that consumes the gateway files and returns cleared-status updates.",
          "article": "Oracle Fusion Cloud ERP Reconciliation in India: What Localisation Does and Doesn't Cover",
          "url": "https://www.terra-insight.com/insights/oracle-fusion-reconciliation-india"
        },
        {
          "q": "What is the typical Oracle Fusion integration for an external reconciliation platform?",
          "a": "Three standard patterns: (1) REST API — Oracle Fusion exposes REST endpoints for AP invoices, GL journals, and bank statements that a reconciliation platform can pull, (2) BI Publisher scheduled export — BIP templates generate CSV/XML to an SFTP or UCM (Universal Content Management) location, and (3) FBDI (File-Based Data Import) — the reconciliation platform writes cleared-status updates back to Oracle via FBDI zip uploads. Most customers combine BIP export for outbound and FBDI for inbound.",
          "article": "Oracle Fusion Cloud ERP Reconciliation in India: What Localisation Does and Doesn't Cover",
          "url": "https://www.terra-insight.com/insights/oracle-fusion-reconciliation-india"
        },
        {
          "q": "What Indian localisation does Sage X3 include by default?",
          "a": "Sage X3 is sold in India with a tax and compliance module that covers GST tax determination on purchase and sales lines, TDS deduction under Indian sections, and Indian fiscal calendar support. Unlike SAP or Oracle, the GSTN and TRACES integration layers are not part of the standard product — they are typically delivered through a local implementation partner's pre-built connector. The module depth is adequate for manufacturing and distribution but lighter on TDS-at-source than Tally or Busy.",
          "article": "Sage Reconciliation in India: X3 and Sage 300 for Mid-Market Finance Teams",
          "url": "https://www.terra-insight.com/insights/sage-reconciliation-india"
        },
        {
          "q": "Does Sage 300 support Indian GST and TDS natively?",
          "a": "Sage 300 (formerly Accpac) is sold with Indian localisation through certified partners. The core product supports tax schedules and withholding tax at the vendor level, which maps to TDS with partner-delivered configuration. GSTR return generation and e-invoice integration are handled by add-on modules from partners like Greytrix, Ezypay, or custom implementations. Native GSTR-2B matching is typically not in the base product and is added via an external layer or partner module.",
          "article": "Sage Reconciliation in India: X3 and Sage 300 for Mid-Market Finance Teams",
          "url": "https://www.terra-insight.com/insights/sage-reconciliation-india"
        },
        {
          "q": "How do Sage X3 and Sage 300 expose data for external reconciliation?",
          "a": "Sage X3 exposes data through the Syracuse web services layer (REST and SOAP), the Adonix ERP query language, and scheduled exports via the X3 batch server. Sage 300 uses the Sage 300 Web API (REST), direct SQL Server access (for on-premise deployments), and Macro / VBA exports. Both products support scheduled CSV exports to SFTP, which is the most common integration path for Indian deployments.",
          "article": "Sage Reconciliation in India: X3 and Sage 300 for Mid-Market Finance Teams",
          "url": "https://www.terra-insight.com/insights/sage-reconciliation-india"
        },
        {
          "q": "What audit trail requirements apply to Sage deployments in India?",
          "a": "Under the Companies (Accounts) Rules as amended April 2023, all accounting software used by Indian companies must maintain an edit log at voucher level with date, user, and change detail (the 'audit trail' rule in CARO 2020). Sage X3 and Sage 300 both offer this through the Audit Log module in X3 and the Transaction History functionality in Sage 300 — but the feature must be explicitly enabled in configuration. External reconciliation layers must not bypass the audit trail when posting back cleared status.",
          "article": "Sage Reconciliation in India: X3 and Sage 300 for Mid-Market Finance Teams",
          "url": "https://www.terra-insight.com/insights/sage-reconciliation-india"
        },
        {
          "q": "What is the typical Sage integration pattern for reconciliation in India?",
          "a": "Typical flow: (1) Sage X3 or Sage 300 exports vendor invoice, customer invoice, bank statement, and GL journal data to SFTP on a scheduled basis via the batch server or a custom script, (2) external reconciliation layer ingests the CSV/XML exports, (3) processes bank reconciliation, TDS Form 26AS matching, GSTR-2B matching, and platform settlement outside Sage, (4) returns cleared-status updates and variance classifications to Sage via REST API or CSV re-import, preserving the audit trail at each write.",
          "article": "Sage Reconciliation in India: X3 and Sage 300 for Mid-Market Finance Teams",
          "url": "https://www.terra-insight.com/insights/sage-reconciliation-india"
        },
        {
          "q": "Does SAP S/4HANA automatically reconcile Form 26AS with the TDS receivable ledger?",
          "a": "No. SAP S/4HANA's India localisation includes transaction codes like J1INMIS and J1INCHLN for TDS challan tracking and Form 26Q filing, but it does not connect to TRACES to download Form 26AS. Finance teams export TDS receivable data from FBL5N or a custom CDS view, download Form 26AS separately from TRACES, and match outside SAP. This is true for both S/4HANA (all releases through 2024 FPS02) and SAP ECC 6.0.",
          "article": "SAP FI Reconciliation in India: Where S/4HANA and ECC Stop Short",
          "url": "https://www.terra-insight.com/insights/sap-fi-reconciliation-india"
        },
        {
          "q": "How does SAP handle GSTR-2B reconciliation in India?",
          "a": "SAP FI with the India GST localisation stores input tax credit at the line-item level via tax codes (V0, V1 etc.) and the J_1IG* tables. GSTR-2B reconciliation requires the JSON to be downloaded from the GST portal monthly and matched against the MIRO purchase register. SAP does not have a GSTN API integration in standard deployments. Most customers use a file export from FBL1N or table BSIK and a separate reconciliation layer.",
          "article": "SAP FI Reconciliation in India: Where S/4HANA and ECC Stop Short",
          "url": "https://www.terra-insight.com/insights/sap-fi-reconciliation-india"
        },
        {
          "q": "Can SAP ingest NACH batch credit files directly into the bank GL?",
          "a": "SAP's Electronic Bank Statement (EBS) via transaction FF.5 can ingest MT940 or BAI2 files, but NACH batch credits typically arrive as a single lump-sum entry with a separate NPCI detail file. SAP does not disaggregate the batch into individual mandate outcomes. Customers either use custom ABAP to parse the NPCI file or route NACH reconciliation through an external layer that posts cleared mandates back to SAP via BAPI or IDoc.",
          "article": "SAP FI Reconciliation in India: Where S/4HANA and ECC Stop Short",
          "url": "https://www.terra-insight.com/insights/sap-fi-reconciliation-india"
        },
        {
          "q": "Which SAP FI tables and tcodes are used for TDS reconciliation exports?",
          "a": "The core tables are WITH_ITEM (withholding tax line items), BSIS/BSAS (open and cleared GL items for the TDS accounts), and J_1IEWTNO (India withholding tax challan numbers). Common tcodes for export are FBL3N for GL line items, J1INMIS for TDS certificate tracking, and S_P00_07000134 for the section-wise TDS summary. These exports feed the external reconciliation layer.",
          "article": "SAP FI Reconciliation in India: Where S/4HANA and ECC Stop Short",
          "url": "https://www.terra-insight.com/insights/sap-fi-reconciliation-india"
        },
        {
          "q": "What is the typical SAP integration pattern for a reconciliation tool in India?",
          "a": "Three patterns are common: (1) scheduled file export — SAP writes CSV or XML to an SFTP location nightly via a background job in SM36, (2) RFC-enabled BAPI calls — the reconciliation tool pulls open items through BAPI_GL_ACC_GETBALANCE or custom Z-BAPIs, and (3) IDoc — SAP sends FINSTA or custom reconciliation IDocs. Most Indian deployments start with file export for simplicity, then move to BAPI once volumes exceed 20,000 line items per month.",
          "article": "SAP FI Reconciliation in India: Where S/4HANA and ECC Stop Short",
          "url": "https://www.terra-insight.com/insights/sap-fi-reconciliation-india"
        },
        {
          "q": "What is the most reliable way to export data from Tally Prime for reconciliation?",
          "a": "For data volumes up to 5,000 vouchers per month, CSV export from standard Tally reports (Day Book, Ledger Vouchers, GSTR-2B reconciliation) is adequate. Above that, the Tally XML API is the recommended path — it returns complete voucher data including narration, cost centres, and tax analysis in a single call. TallyODBC is an alternative for read-only BI queries but is limited to SQL syntax Tally supports and has been formally deprecated from TallyPrime 4.0 onwards in favour of the HTTP interface.",
          "article": "Tally Prime Reconciliation Automation: Integration Paths for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tally-prime-reconciliation-automation-india"
        },
        {
          "q": "How does Tally Prime's GSTR-2B reconciliation module work?",
          "a": "TallyPrime 3.0 onwards (released December 2023) added native GSTR-2B import and reconciliation. The JSON is downloaded from the GST portal, imported via Gateway → Display More Reports → GST Reports → GSTR-2B, and Tally matches against the purchase register on GSTIN + invoice number + date + value. Line-level status is one of Available, Fully Matched, Partially Matched, or Available Only in GSTR-2B. Performance degrades above 500 invoices per month and manual exception handling is still required for GSTIN typos and credit-note timing mismatches.",
          "article": "Tally Prime Reconciliation Automation: Integration Paths for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tally-prime-reconciliation-automation-india"
        },
        {
          "q": "Can Tally Prime consolidate reconciliation across multiple branches or companies?",
          "a": "Tally Prime supports multi-company operation with one data folder per company, but consolidated reconciliation across companies requires manually switching between companies or using Group Company consolidation (Enterprise licence). For organisations with 5+ branches, the standard pattern is to export each company to CSV or XML on a scheduled basis and consolidate in an external layer that handles cross-branch TDS, GST, and bank reconciliation.",
          "article": "Tally Prime Reconciliation Automation: Integration Paths for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tally-prime-reconciliation-automation-india"
        },
        {
          "q": "What does the Tally Connector HTTP interface expose?",
          "a": "Tally Connector (enabled via F12 Configuration → Enable ODBC / HTTP) exposes an HTTP endpoint on port 9000 by default. POST requests with a TDL-formatted XML payload return voucher data, ledger balances, and report output. Common reconciliation queries pull Day Book, Bank Reconciliation Statement, and GSTR-2B mismatch report. The interface requires the Tally instance to be running and does not support concurrent write operations.",
          "article": "Tally Prime Reconciliation Automation: Integration Paths for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tally-prime-reconciliation-automation-india"
        },
        {
          "q": "How is Tally bank reconciliation different from ERP-level bank reconciliation?",
          "a": "Tally's Banking → Bank Reconciliation screen (Ctrl+B from the bank ledger) lets the user match bank statement entries imported via Excel or CSV against voucher entries. It works well for single-bank SME use. At scale — 2,000+ bank lines per month, 5+ bank accounts, multi-currency — the manual reconciliation screen becomes impractical. External reconciliation layers read the Tally ledger via XML API and the bank statement via MT940 or SFTP, then post cleared voucher numbers back to Tally via XML import.",
          "article": "Tally Prime Reconciliation Automation: Integration Paths for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/tally-prime-reconciliation-automation-india"
        },
        {
          "q": "What are the volume limits for Zoho Books reconciliation?",
          "a": "Zoho Books on the Standard plan (₹749/user/month as of 2026) supports up to 5,000 invoices per year; the Professional plan raises that to 10,000 and the Premium plan to 25,000. API rate limits are 100 calls/minute per organisation on Professional and 200 on Premium. Bulk import via CSV is capped at 500 rows per import file. Organisations processing more than 1,000 monthly transactions per bank account typically reach the practical reconciliation ceiling within Zoho's UI.",
          "article": "Zoho Books Reconciliation Limits: What Breaks When Indian Businesses Scale",
          "url": "https://www.terra-insight.com/insights/zoho-books-reconciliation-limitations-india"
        },
        {
          "q": "Does Zoho Books reconcile GSTR-2B automatically?",
          "a": "Yes, Zoho Books has GSTR-2B reconciliation built into the GST section. The 2B JSON can be imported from the GST portal and the engine matches against purchase invoices on GSTIN + invoice number + date + taxable value. Line-level status is shown as Matched, Missing in Books, or Missing in 2B. The matching is effective for clean data but does not auto-correct supplier-side typos (wrong invoice number, transposed GSTIN digits), which constitute the majority of exceptions above 300 purchase invoices per month.",
          "article": "Zoho Books Reconciliation Limits: What Breaks When Indian Businesses Scale",
          "url": "https://www.terra-insight.com/insights/zoho-books-reconciliation-limitations-india"
        },
        {
          "q": "How does Zoho Books handle payment gateway settlement reconciliation?",
          "a": "Zoho Books integrates with Razorpay, PayU, Stripe, and Cashfree through pre-built connectors that pull payment-level data. Net-settlement reconciliation (gross sale less MDR less GST on MDR less TCS less refund adjustments) is not fully automated — the connector posts individual payment-in entries and fee deductions as separate lines, but aggregating them to match a single net bank credit requires manual or external processing. Marketplace fee audit (Flipkart, Amazon, Meesho commission splits) is not natively supported.",
          "article": "Zoho Books Reconciliation Limits: What Breaks When Indian Businesses Scale",
          "url": "https://www.terra-insight.com/insights/zoho-books-reconciliation-limitations-india"
        },
        {
          "q": "Can Zoho Books classify variance types for audit evidence?",
          "a": "Zoho Books' bank reconciliation shows Matched, Pending, and Excluded. It does not classify unmatched variance into categories like FEE_DEDUCTION, TAX_DEDUCTION, TIMING_DIFFERENCE, ROUNDING, or DUPLICATE — which auditors request during CARO 2020 and Ind AS 115 reviews. Variance classification for audit evidence typically requires an external reconciliation layer that reads Zoho's bank reconciliation output via API and applies rule-based tagging.",
          "article": "Zoho Books Reconciliation Limits: What Breaks When Indian Businesses Scale",
          "url": "https://www.terra-insight.com/insights/zoho-books-reconciliation-limitations-india"
        },
        {
          "q": "What is the typical integration pattern between Zoho Books and an external reconciliation tool?",
          "a": "Zoho Books exposes a REST API (Books API v3) with OAuth 2.0 authentication. External tools authenticate once, pull invoice, bill, and bank transaction data on a scheduled basis, process reconciliation externally, and push back matched-status updates. Common endpoints are /invoices, /bills, /banktransactions, and /customerpayments. Rate limits apply (100–200 calls/minute depending on plan), so high-volume organisations typically pull data in batched windows of 200 records per call.",
          "article": "Zoho Books Reconciliation Limits: What Breaks When Indian Businesses Scale",
          "url": "https://www.terra-insight.com/insights/zoho-books-reconciliation-limitations-india"
        }
      ]
    },
    "ca-firm": {
      "label": "CA Firm Reconciliation Workflow",
      "faqs": [
        {
          "q": "How long does client onboarding take in a CA firm's reconciliation workflow?",
          "a": "Client onboarding typically takes 5 to 15 working days for an enterprise engagement. The time covers signing the engagement letter, collecting client master data (GSTINs, PAN, TAN, bank accounts, Tally backup), mapping the chart of accounts, configuring TDS section rules per vendor type, and running a parallel reconciliation for the prior month to validate the setup. Firms onboarding 3 to 5 new clients per month need a standardised template or onboarding delays cascade into the monthly cycle.",
          "article": "CA Firm Client Reconciliation Workflow: Onboarding to Monthly Cycle",
          "url": "https://www.terra-insight.com/insights/ca-firm-client-reconciliation-workflow-india"
        },
        {
          "q": "What does a typical monthly reconciliation cycle look like for a CA firm?",
          "a": "The monthly cycle runs on statutory deadlines: 1st to 5th — pull GSTR-2B, Form 26AS, and bank statements; 6th to 10th — match against purchase register, vendor ledger, and book of accounts; 11th to 13th — exception review with client (TDS return filing due 7th of following month); 14th to 18th — GSTR-3B preparation and sign-off; 19th to 20th — filing. The cycle restarts on the 1st of the following month. A CA firm running 80 clients executes 80 cycles in parallel every month.",
          "article": "CA Firm Client Reconciliation Workflow: Onboarding to Monthly Cycle",
          "url": "https://www.terra-insight.com/insights/ca-firm-client-reconciliation-workflow-india"
        },
        {
          "q": "How are exceptions reviewed and resolved in a CA firm's workflow?",
          "a": "Exceptions are classified into four buckets: vendor error (vendor has not filed GSTR-1 or has filed with wrong GSTIN), client error (missing invoice in purchase register), timing difference (invoice in current period 2B but booked in next period), and data quality (amount mismatch, GSTIN mismatch). Typically 5 to 12% of monthly transactions hit exceptions. The article clerk drafts a resolution note, the manager reviews, and the partner signs off before the exception register is shared with the client.",
          "article": "CA Firm Client Reconciliation Workflow: Onboarding to Monthly Cycle",
          "url": "https://www.terra-insight.com/insights/ca-firm-client-reconciliation-workflow-india"
        },
        {
          "q": "What deliverables does a CA firm provide to each client monthly?",
          "a": "Monthly deliverables typically include: the GSTR-2B reconciliation report (with matched, unmatched, and variance line items), the Form 26AS vs TDS receivable ledger reconciliation, the bank reconciliation statement for each active bank account, the filed GSTR-3B and GSTR-1 challan, the TDS challan copies, and an exception register with resolutions. For enterprise clients this is 15 to 50 pages per month, branded under the firm's letterhead.",
          "article": "CA Firm Client Reconciliation Workflow: Onboarding to Monthly Cycle",
          "url": "https://www.terra-insight.com/insights/ca-firm-client-reconciliation-workflow-india"
        },
        {
          "q": "How does SA 230 documentation apply to the CA firm's reconciliation workflow?",
          "a": "ICAI's SA 230 (Audit Documentation) requires that the firm retain evidence of the work performed, the judgements made, and the conclusions reached. For reconciliation engagements, this means the firm must archive the source data (GSTR-2B JSON, Form 26AS download, bank statements), the matched output, the exception register with resolution notes, and the partner sign-off — typically for 7 years. Digital reconciliation platforms that maintain this audit trail automatically reduce the firm's documentation burden significantly.",
          "article": "CA Firm Client Reconciliation Workflow: Onboarding to Monthly Cycle",
          "url": "https://www.terra-insight.com/insights/ca-firm-client-reconciliation-workflow-india"
        },
        {
          "q": "How long does it take a CA firm to run GSTR-2B reconciliation for 50 clients manually?",
          "a": "Manual GSTR-2B reconciliation for 50 clients with an average of 150 ITC line items per client takes 4 to 6 working days each month. The work includes logging into the GST portal per GSTIN, downloading GSTR-2B JSON, importing to Excel, matching against the purchase register, and flagging mismatches. A dedicated CA firm GST reconciliation tool compresses this to 6 to 12 hours of exception review for the same volume.",
          "article": "CA Firm GST Reconciliation Tool: Running GSTR-2B for 50+ Clients",
          "url": "https://www.terra-insight.com/insights/ca-firm-gst-reconciliation-tool-india"
        },
        {
          "q": "Under which rule must ITC claimed in GSTR-3B match GSTR-2B?",
          "a": "Rule 36(4) of the CGST Rules restricts Input Tax Credit in GSTR-3B to invoices that appear in GSTR-2B. After the Invoice Management System (IMS) rollout in October 2024 and full enforcement from January 2025, only invoices explicitly accepted in IMS flow into the auto-populated GSTR-3B. A mismatch between GSTR-3B ITC and GSTR-2B triggers an automated DRC-01C notice under Rule 88D.",
          "article": "CA Firm GST Reconciliation Tool: Running GSTR-2B for 50+ Clients",
          "url": "https://www.terra-insight.com/insights/ca-firm-gst-reconciliation-tool-india"
        },
        {
          "q": "What is DRC-01C and how should a CA firm respond?",
          "a": "DRC-01C is an automated intimation issued under Rule 88D of the CGST Rules when ITC claimed in GSTR-3B exceeds ITC available in GSTR-2B by more than a threshold. The taxpayer has 7 days to either reverse the excess ITC in DRC-03 or file Part B of DRC-01C with reasons. CA firms managing 50+ clients need a reconciliation tool that flags the mismatch before GSTR-3B is filed, so the DRC-01C never triggers.",
          "article": "CA Firm GST Reconciliation Tool: Running GSTR-2B for 50+ Clients",
          "url": "https://www.terra-insight.com/insights/ca-firm-gst-reconciliation-tool-india"
        },
        {
          "q": "Can a CA firm GST reconciliation tool handle clients with multiple GSTINs?",
          "a": "Yes. A manufacturing client with operations in 6 states has 6 GSTINs, each with its own GSTR-1, GSTR-2B, and GSTR-3B. A CA firm GST reconciliation tool must treat each GSTIN as a separate reconciliation unit within the same client workspace, while aggregating the client-level ITC position for partner review. Approximately 30 to 40% of mid-market CA firm clients hold 3 or more GSTINs.",
          "article": "CA Firm GST Reconciliation Tool: Running GSTR-2B for 50+ Clients",
          "url": "https://www.terra-insight.com/insights/ca-firm-gst-reconciliation-tool-india"
        },
        {
          "q": "How does IMS change the CA firm's GST reconciliation workflow?",
          "a": "The Invoice Management System makes ITC acceptance explicit — every vendor invoice must be accepted, rejected, or kept pending in IMS before it flows into GSTR-2B and then GSTR-3B. This shifts the CA firm's workflow to a two-stage cycle: the first week of the month is IMS triage (accept/reject invoices), and the second week is GSTR-3B filing. A reconciliation tool that integrates IMS status into the purchase register match is essential from the October 2024 rollout onwards.",
          "article": "CA Firm GST Reconciliation Tool: Running GSTR-2B for 50+ Clients",
          "url": "https://www.terra-insight.com/insights/ca-firm-gst-reconciliation-tool-india"
        },
        {
          "q": "Why do Indian enterprises outsource GST compliance to CA firms?",
          "a": "Three reasons dominate. First, specialised GST expertise is expensive to retain in-house — a typical enterprise needs 1 to 3 days of GST work per month but cannot hire a 20% FTE. Second, ICAI-member firms carry professional indemnity and are accountable under ICAI's Code of Ethics, giving the enterprise a clear liability party. Third, multi-state operations with 5 to 15 GSTINs are operationally easier to hand to a firm that already handles the GST portal login and filing rhythm for 80 to 200 clients.",
          "article": "Outsourced GST Compliance Reconciliation: The Enterprise-CA Shared Surface",
          "url": "https://www.terra-insight.com/insights/outsourced-gst-compliance-reconciliation-india"
        },
        {
          "q": "Where does liability sit when a CA firm handles GST compliance for an enterprise?",
          "a": "Legal liability for GST filing accuracy sits with the taxpayer (the enterprise), not the CA firm. The firm's liability is professional — limited to the standard of care expected under ICAI's SA 230 and SA 500. If a GST demand notice is issued under Section 73 or 74 for wrong ITC, the taxpayer pays; the firm faces an ICAI disciplinary question only if the work was performed below professional standards. The engagement letter typically caps the firm's indemnity at the annual fee.",
          "article": "Outsourced GST Compliance Reconciliation: The Enterprise-CA Shared Surface",
          "url": "https://www.terra-insight.com/insights/outsourced-gst-compliance-reconciliation-india"
        },
        {
          "q": "What data does the enterprise hand to the CA firm for GST reconciliation?",
          "a": "The enterprise typically hands over: the purchase register (from Tally, SAP, or Zoho Books) with vendor-wise invoices, GST credentials or DSC for portal access, the master vendor list with GSTINs, the HSN/SAC mapping, and any special rate applications (composition scheme, reverse charge). The GSTR-2B, IMS status, and e-way bill data are pulled by the firm directly from the GST portal using the enterprise's credentials or API access.",
          "article": "Outsourced GST Compliance Reconciliation: The Enterprise-CA Shared Surface",
          "url": "https://www.terra-insight.com/insights/outsourced-gst-compliance-reconciliation-india"
        },
        {
          "q": "How has IMS changed the outsourced GST compliance model?",
          "a": "The Invoice Management System (IMS), rolled out in October 2024, made ITC acceptance explicit — every vendor invoice must be accepted, rejected, or kept pending in IMS. This adds 500 to 5,000 decisions per enterprise per month depending on vendor volume. Most enterprises delegate IMS triage to the CA firm, but the decisions carry judgement (reject a vendor's invoice and the vendor relationship is affected). The firm and enterprise typically agree a rule-based framework — accept all vendors above ₹10,000 per month invoice volume, reject all with wrong GSTIN, flag all others for enterprise review.",
          "article": "Outsourced GST Compliance Reconciliation: The Enterprise-CA Shared Surface",
          "url": "https://www.terra-insight.com/insights/outsourced-gst-compliance-reconciliation-india"
        },
        {
          "q": "What reconciliation platform features are needed to support outsourced GST compliance?",
          "a": "Three features are essential. First, dual-access — both the enterprise's internal finance team and the CA firm must see the same reconciliation workspace, with role-based segregation. Second, audit trail — every action (invoice accepted in IMS, exception flagged, GSTR-3B signed off) must be timestamped and attributed. Third, handoff markers — the platform must make clear where firm responsibility ends and enterprise responsibility begins for each transaction. Most general-purpose GST tools do not support this dual-party model.",
          "article": "Outsourced GST Compliance Reconciliation: The Enterprise-CA Shared Surface",
          "url": "https://www.terra-insight.com/insights/outsourced-gst-compliance-reconciliation-india"
        },
        {
          "q": "How is reconciliation software for CA firms different from regular accounting software?",
          "a": "Accounting software like Tally or Zoho Books is built for a single entity's books. Reconciliation software for CA firms must handle 30 to 500 client engagements in parallel, with per-client data isolation, per-client rate cards (TDS sections, GST registration states), and the ability to deliver branded reconciliation output back to the client. Standard accounting tools do not manage multi-tenant client directories or automate the monthly cycle of pulling GSTR-2B, Form 26AS, and bank statements across clients.",
          "article": "Reconciliation Software for CA Firms in India: Beyond Audit Tools",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-for-ca-firms-india"
        },
        {
          "q": "How many client engagements can a typical CA firm handle with reconciliation software?",
          "a": "A mid-size CA firm in India with 4 to 6 article clerks can service 50 to 150 compliance clients when reconciliation is manual in Excel. The same team, with reconciliation software handling GSTR-2B download, Form 26AS matching, and bank reconciliation, can service 200 to 400 clients. The bottleneck shifts from data entry to exception review and client communication.",
          "article": "Reconciliation Software for CA Firms in India: Beyond Audit Tools",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-for-ca-firms-india"
        },
        {
          "q": "Does reconciliation software satisfy ICAI audit documentation requirements?",
          "a": "Reconciliation software used by CA firms must produce audit-ready documentation: matched and unmatched transaction registers, exception logs, and a timestamped audit trail showing who reviewed and signed off each reconciliation. This supports ICAI's SA 230 (Audit Documentation) and SA 500 (Audit Evidence) requirements. The firm still owns the professional judgement and the sign-off — the software only structures the evidence file.",
          "article": "Reconciliation Software for CA Firms in India: Beyond Audit Tools",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-for-ca-firms-india"
        },
        {
          "q": "Can multiple article clerks work on different clients at the same time?",
          "a": "Yes. Purpose-built reconciliation software for CA firms enforces role-based access so that article clerks can only see and edit clients assigned to them. A single clerk may own 15 to 30 clients, with a partner or manager reviewing exceptions. Data isolation between clients is mandatory to meet both ICAI ethics rules and the Digital Personal Data Protection Act 2023 requirements on client confidentiality.",
          "article": "Reconciliation Software for CA Firms in India: Beyond Audit Tools",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-for-ca-firms-india"
        },
        {
          "q": "What typical monthly fee do CA firms charge for outsourced compliance reconciliation?",
          "a": "For a mid-size enterprise client with monthly GSTR-1, GSTR-3B, TDS returns, and bank reconciliation, CA firms in India typically charge ₹5,000 to ₹25,000 per month depending on transaction volume and number of GST registrations. Margin expansion for the firm comes from reducing the staff hours per engagement — if reconciliation software cuts each client cycle from 6 hours to 90 minutes, the same team absorbs 3x the client load.",
          "article": "Reconciliation Software for CA Firms in India: Beyond Audit Tools",
          "url": "https://www.terra-insight.com/insights/reconciliation-software-for-ca-firms-india"
        },
        {
          "q": "What does white-label reconciliation software include for a CA firm?",
          "a": "White-label reconciliation software for CA firms typically includes firm-branded PDF reports (logo, firm name, partner signature block), a custom sub-domain for the client portal (clients.firmname.com), firm email templates for automated notifications, and removal of the software vendor's branding from all client-facing output. Some platforms also allow custom terminology — the firm can rename 'exceptions' to the firm's preferred term.",
          "article": "White-Label Reconciliation for CA Firms: Branded Client Deliverables",
          "url": "https://www.terra-insight.com/insights/white-label-reconciliation-ca-firms-india"
        },
        {
          "q": "Is white-labelling permitted under ICAI Code of Ethics?",
          "a": "Yes. ICAI's Code of Ethics permits CAs to use third-party technology and deliver output under the firm's name, provided the firm retains professional responsibility for the work. What is not permitted is holding out technology capabilities as the firm's own proprietary system when they are clearly vendor software, or using white-labelling to mislead clients about the service being provided. Most firms disclose the underlying technology in the engagement letter.",
          "article": "White-Label Reconciliation for CA Firms: Branded Client Deliverables",
          "url": "https://www.terra-insight.com/insights/white-label-reconciliation-ca-firms-india"
        },
        {
          "q": "How much does white-label reconciliation typically add to the CA firm's per-client deliverable quality?",
          "a": "White-labelling converts a working paper file into a client-facing deliverable. A typical client reconciliation report of 8 to 15 pages with the firm's letterhead and partner sign-off commands ₹2,000 to ₹8,000 more in monthly fee versus a raw Excel output. For a firm with 100 clients, this represents ₹2.4 to ₹9.6 lakh in annualised fee uplift with no additional staff cost.",
          "article": "White-Label Reconciliation for CA Firms: Branded Client Deliverables",
          "url": "https://www.terra-insight.com/insights/white-label-reconciliation-ca-firms-india"
        },
        {
          "q": "Can clients log into a CA firm's branded reconciliation portal?",
          "a": "Yes. White-label platforms typically support a client portal under the firm's sub-domain where clients upload source documents (bank statements, purchase invoices), download reconciled reports, and review exceptions. The portal displays the firm's branding exclusively. Client access is segregated per client — one client cannot see another client's workspace even if both are on the same firm's portal.",
          "article": "White-Label Reconciliation for CA Firms: Branded Client Deliverables",
          "url": "https://www.terra-insight.com/insights/white-label-reconciliation-ca-firms-india"
        },
        {
          "q": "Does white-label reconciliation software support the firm's practice management system?",
          "a": "Integration with practice management tools like CCH Axcess, ProSeries, or domestic Indian tools like Winman and Taxmann varies by vendor. The most common integration points are client directory sync (adding a client in practice management creates the reconciliation workspace automatically) and time tracking (hours logged on reconciliation flow into the firm's billing). Firms evaluating white-label platforms should confirm these specific integrations match their existing stack.",
          "article": "White-Label Reconciliation for CA Firms: Branded Client Deliverables",
          "url": "https://www.terra-insight.com/insights/white-label-reconciliation-ca-firms-india"
        }
      ]
    },
    "bsa-msme": {
      "label": "MSME Synthetic Financial Statements",
      "faqs": [
        {
          "q": "How are operating cash flows derived from an MSME bank statement?",
          "a": "Operating cash flows are calculated as total business inflows (revenue receipts from customers, excluding loan disbursements and personal credits) minus total operating outflows (vendor payments, staff costs, GST and TDS payments, rent and utility payments). NACH EMI debits to financial institutions are excluded from operating cash flow and classified under financing. The result represents cash generated from the business's core trade activity — the most direct measure of repayment capacity for a working capital loan.",
          "article": "Cash Flow Analysis for MSME Lending Using Bank Statement Data",
          "url": "https://www.terra-insight.com/insights/cash-flow-analysis-msme-bank-statement-india"
        },
        {
          "q": "Why is cash flow from bank data considered more reliable than synthetic P&L for MSME credit?",
          "a": "A synthetic P&L requires multiple inference steps — revenue classification, cost categorisation, COGS estimation — each of which introduces error. The operating cash flow from a bank statement is closer to a direct measurement: it adds up what came in and subtracts what went out, with classification applied to distinguish business from personal and operating from financing. Fewer inference steps mean fewer error sources. For MSMEs with ₹10 lakh to ₹2 crore annual turnover, studies published by SIDBI show that cash flow adequacy is the primary predictor of loan performance in this segment.",
          "article": "Cash Flow Analysis for MSME Lending Using Bank Statement Data",
          "url": "https://www.terra-insight.com/insights/cash-flow-analysis-msme-bank-statement-india"
        },
        {
          "q": "How are financing cash flows identified in an MSME bank statement?",
          "a": "Financing cash flows include: loan disbursement inflows (identified by NEFT credits from banks or NBFCs with loan account references in narrations), NACH EMI debits (fixed-amount recurring debits to financial institution accounts), and CC/OD drawdowns (NEFT credits from current account linked OD facilities). Owner capital injections appear as large self-transfers from personal accounts and are classified as equity financing inflows. Dividend or profit distributions to owners are classified as financing outflows when identifiable.",
          "article": "Cash Flow Analysis for MSME Lending Using Bank Statement Data",
          "url": "https://www.terra-insight.com/insights/cash-flow-analysis-msme-bank-statement-india"
        },
        {
          "q": "What seasonal cash flow patterns are common in Indian MSME bank statements?",
          "a": "Manufacturing MSMEs often show Q3 (October–December) inflow peaks tied to festive season procurement cycles, with a corresponding payables surge in Q4. Agricultural input suppliers show pre-Kharif (May–June) and pre-Rabi (October–November) spikes. Textile traders peak around Diwali and wedding season. GST-compliance-driven outflow spikes occur in the first week of each month (GSTR-3B payment deadline) and quarter-end months (when reconciliation payments are settled). A 12-month analysis window is minimum to capture seasonal variance correctly.",
          "article": "Cash Flow Analysis for MSME Lending Using Bank Statement Data",
          "url": "https://www.terra-insight.com/insights/cash-flow-analysis-msme-bank-statement-india"
        },
        {
          "q": "Can operating cash flow from bank data be used to calculate DSCR?",
          "a": "Yes — Debt Service Coverage Ratio is calculated as operating cash flow divided by total debt service (principal + interest due in the period). For MSME lending, debt service is directly readable from the bank statement: NACH EMI debits show the exact amount and frequency. If the borrower has multiple loans, all NACH debits to financial institutions are summed. A DSCR of 1.25x or above (₹1.25 of operating cash flow for every ₹1 of debt service) is a common working capital loan approval threshold for NBFCs, though each lender sets their own floor.",
          "article": "Cash Flow Analysis for MSME Lending Using Bank Statement Data",
          "url": "https://www.terra-insight.com/insights/cash-flow-analysis-msme-bank-statement-india"
        },
        {
          "q": "What percentage of Indian MSMEs file audited financial statements?",
          "a": "Published estimates consistently place the share of Indian MSMEs with regularly audited accounts below 10%. Mandatory audit thresholds under the Companies Act 2013 apply to private limited companies with turnover above ₹1 crore or paid-up capital above ₹50 lakh — thresholds that the majority of India's approximately 63 million registered MSMEs (mostly proprietorships and partnership firms) do not reach. Under the MSME Development Act 2006, no audit requirement exists for micro and small enterprises below specified turnover thresholds, creating a structural documentation gap.",
          "article": "MSME Credit Assessment Without Audited Financials: The Bank Statement Approach",
          "url": "https://www.terra-insight.com/insights/msme-credit-without-audited-financials-india"
        },
        {
          "q": "What is the difference between decisioning-grade and auditor-grade financial data?",
          "a": "Auditor-grade data meets the assurance standards of the Institute of Chartered Accountants of India (ICAI) — it has been independently verified, follows Ind AS or IGAAP, and carries the auditor's professional liability. Decisioning-grade data is documented, reproducible, and sufficiently reliable to support a lending decision, but does not carry independent assurance. Bank statement analysis produces decisioning-grade outputs: the underlying data is a bank-issued document, the methodology is systematic and reproducible, but the output is explicitly not an audited representation of the borrower's financial position.",
          "article": "MSME Credit Assessment Without Audited Financials: The Bank Statement Approach",
          "url": "https://www.terra-insight.com/insights/msme-credit-without-audited-financials-india"
        },
        {
          "q": "How have lenders historically assessed MSME creditworthiness without audited accounts?",
          "a": "The three traditional methods for undocumented MSME credit assessment are: (1) surrogate income — using a proxy such as electricity bills, GST returns, or property ownership to estimate income capacity; (2) CA-prepared income estimates — a chartered accountant visits the business and prepares a projected income statement based on records inspection and judgment; and (3) collateral-first underwriting — lending against property or equipment value regardless of cash flow adequacy. All three have significant limitations: surrogates are imprecise, CA estimates are costly and slow, and collateral-first lending produces stressed portfolios when business cash flow is inadequate.",
          "article": "MSME Credit Assessment Without Audited Financials: The Bank Statement Approach",
          "url": "https://www.terra-insight.com/insights/msme-credit-without-audited-financials-india"
        },
        {
          "q": "Does RBI permit bank statement analysis as a substitute for audited financials in MSME lending?",
          "a": "RBI's Digital Lending Guidelines (2022, updated 2023) require regulated lenders to use documented, verifiable, and consented data sources for credit assessment. Bank statements, obtained with the borrower's consent, meet these requirements. The guidelines do not prescribe audited financials as a mandatory requirement for MSME loans. NBFC-MFIs and small finance banks extending Priority Sector Lending to MSMEs under RBI guidelines can and do use bank statement analysis as the primary income documentation method for loans below ₹25 lakh where the borrower lacks formal accounts.",
          "article": "MSME Credit Assessment Without Audited Financials: The Bank Statement Approach",
          "url": "https://www.terra-insight.com/insights/msme-credit-without-audited-financials-india"
        },
        {
          "q": "What does 'decisioning-grade' mean in practice for an NBFC credit team?",
          "a": "Decisioning-grade means the data is sufficient to approve or decline a loan application with documented justification — it satisfies the lender's internal credit policy, the RBI's documentation requirements, and the audit trail requirement under NBFC regulations (Master Direction on NBFCs, RBI). It does not mean the data is auditor-certified. In practice, an NBFC using bank statement analysis would document: the statement source, the analysis methodology, the key output (operating cash flow, DSCR, synthetic P&L), and how those outputs mapped to the credit policy scorecard. That documentation package constitutes the credit file for the loan.",
          "article": "MSME Credit Assessment Without Audited Financials: The Bank Statement Approach",
          "url": "https://www.terra-insight.com/insights/msme-credit-without-audited-financials-india"
        },
        {
          "q": "What line items can a synthetic MSME P&L reliably estimate from bank data?",
          "a": "Revenue (gross inflows from business counterparties), cost of goods sold (outflows to identifiable vendor/supplier accounts), staff costs (recurring salary credits or NEFT transfers to employees), loan repayment obligations (NACH debits or scheduled EMI outflows), and tax payments (GST/TDS outflows to government accounts). Items that cannot be reliably estimated include depreciation, non-cash provisions, inventory holding costs, and accrued but unpaid liabilities.",
          "article": "Constructing a Synthetic P&L for MSMEs from Bank Transaction Data",
          "url": "https://www.terra-insight.com/insights/msme-synthetic-profit-loss-bank-statement-india"
        },
        {
          "q": "How is revenue inferred from a bank statement if there are no invoice references?",
          "a": "Revenue inference relies on inflow characterisation: business-type UPI credits (merchant-registered counterparties), NEFT/RTGS receipts from corporate payers (identified by counterparty name patterns and CIN references in narration), and IMPS receipts with B2B transaction markers. Credits from financial institutions (loan disbursals), government accounts (GST refunds, subsidy credits), and identified personal senders are excluded. The residual business inflow total is treated as gross revenue for the period.",
          "article": "Constructing a Synthetic P&L for MSMEs from Bank Transaction Data",
          "url": "https://www.terra-insight.com/insights/msme-synthetic-profit-loss-bank-statement-india"
        },
        {
          "q": "Is a synthetic P&L acceptable to lenders under RBI Digital Lending Guidelines?",
          "a": "RBI's Digital Lending Guidelines (2022, updated 2023) require lenders to maintain documented underwriting criteria and to use verified data sources. Bank statement analysis is an explicitly recognised alternative income documentation method for MSMEs and thin-file borrowers. The guidelines require lenders to disclose their credit assessment methodology to borrowers but do not prescribe that audited financials are mandatory — synthetic P&Ls based on bank data satisfy the documented, verifiable data source requirement when the methodology is reproducible.",
          "article": "Constructing a Synthetic P&L for MSMEs from Bank Transaction Data",
          "url": "https://www.terra-insight.com/insights/msme-synthetic-profit-loss-bank-statement-india"
        },
        {
          "q": "What is the difference between a synthetic P&L and a CA-prepared income estimate?",
          "a": "A CA-prepared income estimate (used in some MSME lending programs) is based on a site visit, business records review, and professional judgment — it may be more accurate for businesses with complex inventory or barter arrangements. A synthetic P&L is fully automated from bank data, covers only the transactions visible in the statement, and can be produced in minutes. The CA estimate takes days and costs the borrower professional fees. For ticket sizes below ₹25 lakh and turnaround requirements under 48 hours, the synthetic P&L is the operationally viable option.",
          "article": "Constructing a Synthetic P&L for MSMEs from Bank Transaction Data",
          "url": "https://www.terra-insight.com/insights/msme-synthetic-profit-loss-bank-statement-india"
        },
        {
          "q": "How does GST return data complement a bank-statement-derived synthetic P&L?",
          "a": "For GST-registered MSMEs (turnover above ₹40 lakh for goods, ₹20 lakh for services), GSTR-1 contains the taxable supply ledger — a near-complete revenue record. Cross-referencing GSTR-1 against the bank statement's business inflow total provides a consistency check: if GSTR-1 revenue significantly exceeds bank inflows, the borrower may be collecting through non-banking channels; if bank inflows significantly exceed GSTR-1 revenue, some inflows may be personal or non-taxable. The gap analysis flags divergence for manual review rather than automated override.",
          "article": "Constructing a Synthetic P&L for MSMEs from Bank Transaction Data",
          "url": "https://www.terra-insight.com/insights/msme-synthetic-profit-loss-bank-statement-india"
        },
        {
          "q": "How is the cash conversion cycle estimated from an MSME bank statement?",
          "a": "The cash conversion cycle is approximated as the average number of days between when supplier payments go out (operating outflow dates) and when customer receipts come in (operating inflow dates) for matched transaction pairs. For a trading MSME with identifiable supplier and customer payment patterns, this can be estimated within a 7-to-10-day margin. For services MSMEs, the cycle is shorter (30–45 days typical) versus manufacturing (45–90 days). The methodology requires at least 6 months of statement data to establish reliable payment timing distributions.",
          "article": "MSME Working Capital Assessment from Bank Statement Analysis",
          "url": "https://www.terra-insight.com/insights/msme-working-capital-assessment-bank-statement"
        },
        {
          "q": "What is the difference in working capital patterns between manufacturing, trading, and services MSMEs in India?",
          "a": "Manufacturing MSMEs typically show longer working capital cycles (60–90 days) with large periodic outflows for raw material procurement and delayed inflows from distributor payments. Trading MSMEs show shorter cycles (15–45 days) with higher transaction frequency and smaller average transaction values. Services MSMEs (IT, consulting, facility management) show the shortest cycles and most predictable monthly cash flow patterns, but may have milestone-payment structures that create 30-to-60-day inflow gaps. NACH mandates for manufacturing MSMEs tend to be for raw material procurement agreements; for services, they are typically for software subscriptions or utility payments.",
          "article": "MSME Working Capital Assessment from Bank Statement Analysis",
          "url": "https://www.terra-insight.com/insights/msme-working-capital-assessment-bank-statement"
        },
        {
          "q": "How does bank statement analysis determine peak working capital requirement?",
          "a": "Peak working capital requirement is identified by measuring the maximum net cash deficit across the analysis period: the date when the gap between cumulative outflows and cumulative inflows was widest. For seasonal businesses, this peak typically occurs 4–6 weeks before the peak revenue month. For a textile trader, the peak deficit typically falls in September–October (pre-festive inventory purchase) before October–December inflows arrive. The peak deficit amount, averaged over 2–3 years of statement data, provides the reference point for working capital loan sizing.",
          "article": "MSME Working Capital Assessment from Bank Statement Analysis",
          "url": "https://www.terra-insight.com/insights/msme-working-capital-assessment-bank-statement"
        },
        {
          "q": "Is NABARD-style working capital assessment applicable to bank statement analysis for MSMEs?",
          "a": "NABARD's agricultural and rural MSME lending programs use a drawing power calculation based on the borrower's estimated inventory and receivables — a traditional working capital assessment approach. Bank statement analysis maps to the same conceptual framework but derives the inputs differently: inventory holding cost is proxied from the lag between procurement outflows and sales inflows; receivables are proxied from payment timing analysis. For NABARD-linked NBFC programs targeting rural MSMEs, bank statement analysis outputs can be presented in the drawing power format to satisfy scheme documentation requirements.",
          "article": "MSME Working Capital Assessment from Bank Statement Analysis",
          "url": "https://www.terra-insight.com/insights/msme-working-capital-assessment-bank-statement"
        },
        {
          "q": "What minimum statement period is required for a reliable MSME working capital assessment?",
          "a": "A 12-month statement period is recommended for MSMEs with seasonal cash flow patterns (agri-input dealers, textile traders, construction material suppliers). A 6-month minimum is acceptable for services MSMEs with predictable monthly billing cycles. Assessments based on fewer than 3 months of data should not be used for loan sizing above ₹5 lakh — short windows may capture an atypically high or low cash flow period and produce a misleading working capital picture. For new businesses with less than 12 months of history, lenders should supplement bank data with GST returns and purchase orders.",
          "article": "MSME Working Capital Assessment from Bank Statement Analysis",
          "url": "https://www.terra-insight.com/insights/msme-working-capital-assessment-bank-statement"
        },
        {
          "q": "Why do most Indian MSME owners use a single account for personal and business transactions?",
          "a": "Most Indian MSMEs operate as sole proprietorships or partnership firms with fewer than 10 employees. Regulatory requirements for separate business accounts only become mandatory at the GST registration stage for firms above ₹40 lakh turnover (₹20 lakh for services). Below that threshold, many proprietors never formalise separate accounts, and even registered firms frequently route household expenses, family transfers, and vendor payments through the same current account.",
          "article": "Personal vs Business Transaction Separation in MSME Bank Statements",
          "url": "https://www.terra-insight.com/insights/personal-vs-business-transaction-separation-msme"
        },
        {
          "q": "What types of transactions are most commonly misclassified as business income in MSME bank statements?",
          "a": "The three most frequently misclassified inflows are: (1) UPI credits from family members that appear as business-size transfers, (2) NEFT/IMPS receipts from personal asset sales — property advances, vehicle sales — that spike apparent revenue in a single month, and (3) loan disbursements credited directly to the current account. All three inflate apparent business income if not filtered before the P&L inference step.",
          "article": "Personal vs Business Transaction Separation in MSME Bank Statements",
          "url": "https://www.terra-insight.com/insights/personal-vs-business-transaction-separation-msme"
        },
        {
          "q": "How does UPI counterparty type help identify personal vs business transactions?",
          "a": "UPI transaction narrations include the registered counterparty name and, in many cases, the VPA (Virtual Payment Address) domain suffix. VPAs ending in @okaxis, @ybl, @paytm with individual-name prefixes are strong indicators of peer-to-peer transfers. VPAs with business-name prefixes, registered merchant IDs, or GST-linked counterparty names point to business activity. The signal is probabilistic, not deterministic — a proprietor may use a personal VPA for genuine business receipts.",
          "article": "Personal vs Business Transaction Separation in MSME Bank Statements",
          "url": "https://www.terra-insight.com/insights/personal-vs-business-transaction-separation-msme"
        },
        {
          "q": "What is the impact of misclassification on MSME credit decisions?",
          "a": "If 20–30% of inflows in a mixed account are personal (family transfers, personal UPI credits, loan receipts), treating them as business revenue inflates apparent monthly turnover by a corresponding percentage. For an MSME with ₹8 lakh in monthly bank credits where ₹2 lakh is personal, the corrected business revenue view is ₹6 lakh — a 25% reduction. Loan sizing based on the uncorrected figure would produce an over-leveraged credit that defaults at the first cash flow stress point.",
          "article": "Personal vs Business Transaction Separation in MSME Bank Statements",
          "url": "https://www.terra-insight.com/insights/personal-vs-business-transaction-separation-msme"
        },
        {
          "q": "Does SIDBI or RBI require MSME borrowers to maintain separate business accounts?",
          "a": "SIDBI's lending programs and RBI's Priority Sector Lending guidelines do not mandate a dedicated business account as a loan eligibility condition for MSMEs below certain turnover thresholds. However, SIDBI's underwriting guidelines for schemes like MUDRA and Stand-Up India prefer at least 12 months of business account history. For accounts below ₹50 lakh turnover, lenders typically accept a primary current account even if it has personal transactions — making robust separation methodology essential rather than optional.",
          "article": "Personal vs Business Transaction Separation in MSME Bank Statements",
          "url": "https://www.terra-insight.com/insights/personal-vs-business-transaction-separation-msme"
        },
        {
          "q": "Which balance sheet items can be reliably approximated from a bank statement?",
          "a": "Cash and bank balances are directly observable — the closing balance on the analysis date is exact. Working capital can be approximated as the net of average business inflows (receivables proxy) minus average business outflows (payables proxy) over a 3-to-6-month window. Trade receivables outstanding can be proxied by the gap between when invoiced counterparties typically pay versus the standard credit period for the industry. Current liabilities can be estimated from known NACH mandate amounts and recurring vendor payment obligations visible in the statement.",
          "article": "Synthetic Balance Sheet for MSME Lending: What Bank Statements Can Approximate",
          "url": "https://www.terra-insight.com/insights/synthetic-balance-sheet-msme-bank-statement"
        },
        {
          "q": "Why can fixed assets not be approximated from a bank statement?",
          "a": "Fixed asset values require valuation at cost or fair value, plus accumulated depreciation — none of which appear in cash transaction data. A large one-time outflow may represent a machinery purchase, a security deposit, a property advance, or a large vendor payment for inventory. Without supporting documentation (invoice, registration certificate, asset schedule), the transaction cannot be confirmed as a capital expenditure, let alone valued. As a result, gross block, net block, and capital work-in-progress are excluded from synthetic balance sheets.",
          "article": "Synthetic Balance Sheet for MSME Lending: What Bank Statements Can Approximate",
          "url": "https://www.terra-insight.com/insights/synthetic-balance-sheet-msme-bank-statement"
        },
        {
          "q": "How does RBI Digital Lending Guidance affect the use of synthetic balance sheets in credit decisions?",
          "a": "RBI's Digital Lending Guidelines require lenders to use verifiable, documented data sources and to maintain a clear audit trail of the underwriting decision. A synthetic balance sheet derived from bank statement data satisfies the verifiable source requirement — the underlying data is a bank-issued document. However, lenders must document their methodology, disclose its use in the credit assessment to the borrower, and ensure the synthetic data is not misrepresented as auditor-certified. Regulated entities (NBFCs, banks) may also face internal policy requirements on minimum documentation that go beyond the RBI minimum.",
          "article": "Synthetic Balance Sheet for MSME Lending: What Bank Statements Can Approximate",
          "url": "https://www.terra-insight.com/insights/synthetic-balance-sheet-msme-bank-statement"
        },
        {
          "q": "What is the receivables proxy in a synthetic balance sheet and how accurate is it?",
          "a": "The receivables proxy estimates trade receivables outstanding by analysing the payment lag pattern for recurring business counterparties. If a counterparty consistently pays 30–45 days after the expected payment date (based on payment frequency analysis), the month-end receivable from that counterparty can be approximated as one month's average receipt. For trading MSMEs with 10–30 regular customers, this proxy tends to be directionally correct within 15–25% of the actual outstanding. It degrades in accuracy for businesses with irregular payment terms or where customers pay via multiple instruments.",
          "article": "Synthetic Balance Sheet for MSME Lending: What Bank Statements Can Approximate",
          "url": "https://www.terra-insight.com/insights/synthetic-balance-sheet-msme-bank-statement"
        },
        {
          "q": "Can a synthetic balance sheet be used to calculate net worth for MSME lending?",
          "a": "Net worth (equity) cannot be directly computed from a bank statement because it requires the total asset base minus total liabilities — and the bank statement covers neither fixed assets nor all external liabilities (undisclosed borrowings, guarantees, contingent liabilities). What can be approximated is a liquidity-adjusted working capital net position: current assets (cash + receivables proxy) minus current liabilities (NACH obligations + identified payables). Some lenders use this as a proxy for working capital net worth, clearly labelling it as a bank-data-derived estimate rather than a certified balance sheet figure.",
          "article": "Synthetic Balance Sheet for MSME Lending: What Bank Statements Can Approximate",
          "url": "https://www.terra-insight.com/insights/synthetic-balance-sheet-msme-bank-statement"
        },
        {
          "q": "What is a synthetic financial statement for MSME borrowers?",
          "a": "A synthetic financial statement is a P&L, balance sheet, or cash flow statement reconstructed algorithmically from a borrower's bank transaction history, without requiring audited accounts or CA-certified financials. It is produced by classifying bank debits and credits into income, expense, asset, liability, and financing categories. RBI's account aggregator framework, which became live for NBFCs in 2023, provides the consent-native data pipe that makes this process both scalable and audit-ready. For an MSME with annual turnover below ₹5 crore that has never filed CMA data, a synthetic statement is often the only structured financial view available to a prospective lender. The accuracy of the output depends on the quality of the transaction separation, categorisation, and industry-adjusted margin logic applied.",
          "article": "Synthetic Financial Statements for MSME Credit: What They Are and How They Work",
          "url": "https://www.terra-insight.com/insights/synthetic-financial-statements-msme-bank-statement-india"
        },
        {
          "q": "Can a bank statement replace audited accounts for an MSME loan?",
          "a": "For loans up to ₹50 lakh, most NBFCs and many PSU banks now accept bank statement analysis as a substitute or primary input when audited accounts are unavailable, provided the analysis produces a structured income and cash flow view. The RBI's MSME lending guidelines and the Emergency Credit Line Guarantee Scheme (ECLGS) framework both explicitly contemplate bank-statement-based underwriting for sub-₹2 crore exposures. However, for working capital facilities above ₹50 lakh or term loans with tenure beyond 36 months, institutional lenders typically require at minimum a synthetic balance sheet — not just income verification — to calculate DSCR and size the facility correctly. A four-layer synthetic statement package can satisfy this requirement in the absence of audited accounts. Lenders should note that synthetic statements carry their own model risk and should be validated against GST filing data and ITR summaries where available.",
          "article": "Synthetic Financial Statements for MSME Credit: What They Are and How They Work",
          "url": "https://www.terra-insight.com/insights/synthetic-financial-statements-msme-bank-statement-india"
        },
        {
          "q": "How do NBFCs assess MSME creditworthiness when the borrower has no ITR?",
          "a": "NBFCs have four primary alternative data sources when ITR is unavailable: bank transaction history (12–24 months), GST return filings (GSTR-1, GSTR-3B), trade reference checks, and bureau data from CRIF, Equifax, or CIBIL. Bank statement analysis is the most information-dense of these inputs because it captures all cash movement, not just tax-declared income. When neither ITR nor GST filings exist — which applies to approximately 40% of MSME borrowers who operate below the ₹40 lakh GST registration threshold — bank statement analysis becomes the sole structured financial input. Sophisticated platforms derive 40 or more credit signals from transaction data, including bounce prediction, salary consistency scoring, and debt service coverage estimates. NBFC credit teams typically cross-validate synthetic income against the account's average quarterly balance and NACH debit density as a reasonableness check.",
          "article": "Synthetic Financial Statements for MSME Credit: What They Are and How They Work",
          "url": "https://www.terra-insight.com/insights/synthetic-financial-statements-msme-bank-statement-india"
        },
        {
          "q": "What is the MSME credit gap in India and why does it persist?",
          "a": "SIDBI estimates India's MSME credit gap at approximately ₹69 trillion — the difference between total credit demand from the segment and what formal lenders actually disburse. The gap persists primarily because of documentation barriers, not borrower credit quality: roughly 63 million of the 73 million Udyam-registered MSMEs cannot produce audited P&L or balance sheet statements that satisfy standard appraisal templates. A secondary driver is risk-aversion among lenders who lack tools to differentiate viable businesses from genuinely risky ones without traditional documents. The account aggregator framework and maturing bank statement analysis platforms are gradually addressing the documentation barrier. However, lenders that rely on income-only analysis — rather than full synthetic financials — are still underwriting against an incomplete credit picture, which contributes to both over-lending and under-lending within the eligible MSME population.",
          "article": "Synthetic Financial Statements for MSME Credit: What They Are and How They Work",
          "url": "https://www.terra-insight.com/insights/synthetic-financial-statements-msme-bank-statement-india"
        },
        {
          "q": "How does the RBI account aggregator framework improve MSME credit assessment?",
          "a": "The RBI's account aggregator (AA) framework, governed by the Master Direction on NBFC-AA issued in 2016 and operationalised through the Account Aggregator ecosystem from 2023, allows individuals and businesses to share their financial data — including bank statements from any participating FIP — with lenders via a consent-gated, standardised API. For MSME credit assessment, the AA framework eliminates the manual PDF submission and tampering risk associated with traditional bank statement collection; data arrives in structured JSON directly from the originating bank. Statements obtained via AA carry cryptographic provenance, making the underlying data audit-ready and reducing the compliance burden for NBFCs who must document their underwriting rationale under RBI's IRACP norms. As of 2024, over 20 scheduled commercial banks and several cooperative banks are live as Financial Information Providers (FIPs) on the AA network, covering the majority of MSME current accounts.",
          "article": "Synthetic Financial Statements for MSME Credit: What They Are and How They Work",
          "url": "https://www.terra-insight.com/insights/synthetic-financial-statements-msme-bank-statement-india"
        }
      ]
    },
    "restaurant-fnb": {
      "label": "Restaurant and F&B Reconciliation",
      "faqs": [
        {
          "q": "Can a cloud kitchen run multiple brands under a single GSTIN?",
          "a": "Yes. Under the CGST Act, GSTIN registration is at the level of legal entity per state, not per brand. A single Pvt Ltd company operating five virtual brands from one Bangalore commissary registers one Karnataka GSTIN and lists each brand separately on Zomato, Swiggy, and other aggregators. Each aggregator listing maps to the same GSTIN at the back end. GSTR-1 consolidates all brand sales into a single filing, which means brand-level revenue must be derived from operational reports, not from GST data.",
          "article": "Cloud Kitchen Multi-Brand Reconciliation: One GSTIN, Many Brand Identities",
          "url": "https://www.terra-insight.com/insights/cloud-kitchen-multi-brand-reconciliation"
        },
        {
          "q": "How is brand-level P&L reconciled when GST and bank flows are GSTIN-level?",
          "a": "Brand P&L requires a separate accounting layer above the GSTIN. Each aggregator settlement file carries a brand or restaurant ID per order, even when the underlying GSTIN is shared. The reconciliation pipeline tags every order with its brand identifier, allocates kitchen cost via a cost driver (orders, prep minutes, ingredient weight), and produces brand-level revenue, COGS, marketing spend, and contribution margin. The GSTIN-level filing remains the source of truth for tax; brand P&L is the source of truth for menu and marketing decisions.",
          "article": "Cloud Kitchen Multi-Brand Reconciliation: One GSTIN, Many Brand Identities",
          "url": "https://www.terra-insight.com/insights/cloud-kitchen-multi-brand-reconciliation"
        },
        {
          "q": "How does a commissary or central kitchen flow affect reconciliation?",
          "a": "A commissary that prepares semi-finished items shipped to satellite cloud kitchens introduces an internal stock transfer that may or may not require an e-way bill depending on inter-state movement and value. Within a single GSTIN and state, commissary-to-kitchen transfers are not GST-relevant supplies. Across states, they trigger IGST under self-supply rules. The reconciliation must separate the COGS flow (ingredient cost moving from commissary to kitchen) from the revenue flow (orders served from each kitchen) so brand profitability is not distorted by transfer pricing.",
          "article": "Cloud Kitchen Multi-Brand Reconciliation: One GSTIN, Many Brand Identities",
          "url": "https://www.terra-insight.com/insights/cloud-kitchen-multi-brand-reconciliation"
        },
        {
          "q": "What is the typical cloud kitchen revenue mix between Zomato, Swiggy, and direct?",
          "a": "For most aggregator-only cloud kitchens, Zomato and Swiggy together represent 80% to 95% of revenue, with the split varying by city — Swiggy tends to lead in Bangalore and Hyderabad, Zomato in Delhi and metros. Direct ordering through brand websites or WhatsApp typically contributes 5% to 15% in cities where brand awareness has been built. The reconciliation must consolidate aggregator-led revenue (with 194O, TCS, commission deductions) and direct revenue (with payment gateway settlement) into a single brand P&L.",
          "article": "Cloud Kitchen Multi-Brand Reconciliation: One GSTIN, Many Brand Identities",
          "url": "https://www.terra-insight.com/insights/cloud-kitchen-multi-brand-reconciliation"
        },
        {
          "q": "How are aggregator commissions allocated across brands sharing one kitchen?",
          "a": "Each aggregator settlement file carries the brand listing ID at the order line. Commission, 194O TDS, Section 52 TCS, and ad spend are deducted at the brand level even though the bank credit lands as a single payout for the GSTIN. Allocation requires reading each settlement line by brand ID and posting commission expense, GST input credit, and TDS receivable to the brand's sub-ledger. Allocating commission as a flat percentage of gross revenue is a common error — actual commission tiers vary by brand rating, cuisine category, and aggregator promo participation.",
          "article": "Cloud Kitchen Multi-Brand Reconciliation: One GSTIN, Many Brand Identities",
          "url": "https://www.terra-insight.com/insights/cloud-kitchen-multi-brand-reconciliation"
        },
        {
          "q": "What does Section 9(5) of the CGST Act do for restaurant services?",
          "a": "Section 9(5) of the CGST Act empowers the government to notify categories of services where the e-commerce operator, rather than the actual supplier, is liable to pay GST. By Notification 17/2017 as amended effective 1 January 2022, restaurant services supplied through e-commerce operators were brought under Section 9(5). For these supplies, Zomato or Swiggy is liable to pay 5% GST to the exchequer, and the restaurant is not the supplier of record for GST purposes. Section 9(5) of the CGST Act is unchanged by the new Income Tax Act 2025.",
          "article": "GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not",
          "url": "https://www.terra-insight.com/insights/gst-section-9-5-aggregator-restaurant-liability"
        },
        {
          "q": "Which restaurants fall under Section 9(5) and which do not?",
          "a": "Standalone restaurants supplying through Zomato, Swiggy, or any e-commerce operator fall under Section 9(5) — the aggregator pays GST. Cloud kitchens supplying only via aggregators also fall under Section 9(5). Restaurants located in a hotel where any unit of accommodation has a declared tariff of ₹7,500 or above per unit per day are excluded from Section 9(5) — these continue to charge 18% GST themselves with full ITC, regardless of the aggregator route. The threshold is the published tariff, not the discounted rate.",
          "article": "GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not",
          "url": "https://www.terra-insight.com/insights/gst-section-9-5-aggregator-restaurant-liability"
        },
        {
          "q": "Can a Section 9(5) restaurant claim ITC on inputs attributable to aggregator supplies?",
          "a": "No. Because the standalone restaurant is not the supplier of record for GST on Section 9(5) supplies, it cannot claim input tax credit on inputs attributable to those supplies — rent, ingredients, equipment, packaging, aggregator commission, and ad spend all flow to expense gross of GST. The 5% no-ITC regime that already applies to standalone restaurants compounds this — there is no parallel ITC stream to recover the input tax. This is a structural feature of the regime, not a temporary measure.",
          "article": "GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not",
          "url": "https://www.terra-insight.com/insights/gst-section-9-5-aggregator-restaurant-liability"
        },
        {
          "q": "How is Section 9(5) reported in GSTR-3B by the restaurant?",
          "a": "The restaurant reports the value of supplies made through the e-commerce operator under Section 9(5) in Table 3.1.1 of GSTR-3B as an outward supply where tax is paid by the operator. The tax itself is not paid by the restaurant — Zomato or Swiggy reports and pays it through their own GSTR-3B under the corresponding Section 9(5) supplier table. The restaurant's books still record gross revenue, but the GST liability sits with the aggregator. Misreporting Section 9(5) supplies as direct outward supplies double-counts tax and surfaces in GSTR-9C reconciliation.",
          "article": "GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not",
          "url": "https://www.terra-insight.com/insights/gst-section-9-5-aggregator-restaurant-liability"
        },
        {
          "q": "What happens to a Section 9(5) supply when the order is cancelled?",
          "a": "The aggregator issues a return or refund and reverses the Section 9(5) GST in its own GSTR-3B for the period. The restaurant's books reverse the gross revenue and any cost-of-goods accrual against that order. Because the restaurant did not pay GST on the original supply, there is no output tax to reverse on the restaurant side — only revenue. If the cancellation crosses a filing month, the aggregator handles the GST reversal in its filing, and the restaurant adjusts revenue in the period of cancellation, with the audit trail traced through the aggregator settlement file order ID.",
          "article": "GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not",
          "url": "https://www.terra-insight.com/insights/gst-section-9-5-aggregator-restaurant-liability"
        },
        {
          "q": "How does Magicpin settlement differ from Zomato or Swiggy for a restaurant?",
          "a": "Magicpin operates primarily as a voucher and discovery platform rather than a full delivery aggregator. Restaurants list a discount voucher; the guest buys it on the app and redeems at the outlet. Magicpin remits the voucher value net of platform fee to the restaurant on a weekly or fortnightly cycle. Settlement files carry voucher ID, redemption time, gross voucher value, platform fee, GST on platform fee, and net payout. The reconciliation matches each redeemed voucher in the Magicpin file to the corresponding bill at the outlet POS, then to the bank credit batch.",
          "article": "Magicpin and Dunzo Restaurant Settlement Reconciliation: Vouchers, Cashback, and TCS",
          "url": "https://www.terra-insight.com/insights/magicpin-dunzo-restaurant-settlement-reconciliation"
        },
        {
          "q": "How are Magicpin promos and cashback accounted for at the restaurant?",
          "a": "Magicpin runs voucher promos where the guest pays a discounted price (say ₹400 for a ₹500 voucher), and Magicpin remits the merchant value (₹500 minus platform fee) to the restaurant. The cashback or promo cost is borne by Magicpin, not the restaurant. The restaurant books revenue at gross voucher face value with GST on the gross. Loyalty cashback that hits the merchant — instances where the platform passes promo cost to the restaurant — appears as a separate negative line in the settlement and is booked as a sales discount with proportional GST adjustment.",
          "article": "Magicpin and Dunzo Restaurant Settlement Reconciliation: Vouchers, Cashback, and TCS",
          "url": "https://www.terra-insight.com/insights/magicpin-dunzo-restaurant-settlement-reconciliation"
        },
        {
          "q": "What is the Dunzo restaurant settlement format where it still operates?",
          "a": "Dunzo's restaurant partner settlements, in markets where the service is operating, follow a daily payout cycle. The settlement file carries order ID, delivery completion time, gross order value, commission (typically 18% to 22%), GST on commission, packaging charge, and net merchant payout. The reconciliation pattern is the same as Zomato or Swiggy: match each order to the POS bill, derive commission expense with ITC on the GST component, and reconcile the net to the bank credit batch.",
          "article": "Magicpin and Dunzo Restaurant Settlement Reconciliation: Vouchers, Cashback, and TCS",
          "url": "https://www.terra-insight.com/insights/magicpin-dunzo-restaurant-settlement-reconciliation"
        },
        {
          "q": "How does TCS treatment differ for secondary aggregators?",
          "a": "Section 52 of the CGST Act requires every e-commerce operator to collect TCS at 0.5% (CGST 0.25% + SGST 0.25% intra-state, or IGST 0.5% inter-state) on the net taxable value of supplies made through the platform. Magicpin, Dunzo, Zomato, and Swiggy all qualify as e-commerce operators and deduct TCS uniformly. The TCS appears in the merchant's GSTR-2A and is claimable as a tax credit in GSTR-3B. The treatment does not differ by platform — what differs is the timing of TCS reflection and the granularity of platform-issued TCS certificates, which secondary aggregators sometimes provide quarterly rather than monthly.",
          "article": "Magicpin and Dunzo Restaurant Settlement Reconciliation: Vouchers, Cashback, and TCS",
          "url": "https://www.terra-insight.com/insights/magicpin-dunzo-restaurant-settlement-reconciliation"
        },
        {
          "q": "How do you reconcile a voucher-based platform like Magicpin to outlet POS?",
          "a": "The reconciliation key is the voucher redemption code. The guest redeems a voucher at the outlet, the cashier enters the voucher code on the POS, and the voucher value flows into a separate tender type on the Z-report. Magicpin's settlement file lists each redeemed voucher with the same code. Matching by voucher code closes the loop between platform and outlet. Voucher fraud — guests claiming a voucher was redeemed when it was not — surfaces when settlement-side redemptions exceed POS-side redemptions over a period.",
          "article": "Magicpin and Dunzo Restaurant Settlement Reconciliation: Vouchers, Cashback, and TCS",
          "url": "https://www.terra-insight.com/insights/magicpin-dunzo-restaurant-settlement-reconciliation"
        },
        {
          "q": "What GST rate applies to outdoor catering in India?",
          "a": "Outdoor catering is taxed at 18% GST with full input tax credit. This is distinct from a standalone restaurant's dine-in or takeaway supply, which is taxed at 5% without ITC under Notification 11/2017-CTR. Where the same caterer runs a dine-in restaurant alongside an outdoor catering line, the two revenue streams are taxed and ITC-eligible separately, and the working sheet must keep them apart line by line.",
          "article": "Outdoor Catering Reconciliation in India: GST 18% with ITC, Advance Receipts, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/outdoor-catering-reconciliation-india"
        },
        {
          "q": "When does GST become payable on an advance received for a catering event?",
          "a": "Under Section 13 of the CGST Act, the time of supply for services is the earlier of invoice date or payment receipt date. An advance receipt for a catering event therefore triggers GST liability in the month the advance is received, even if the event is months away. The caterer must issue a receipt voucher, report the advance in GSTR-1 (Table 11), and pay the 18% GST in the same period's GSTR-3B. When the final invoice is later issued, the advance is adjusted via Table 11A in GSTR-1 to avoid double counting.",
          "article": "Outdoor Catering Reconciliation in India: GST 18% with ITC, Advance Receipts, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/outdoor-catering-reconciliation-india"
        },
        {
          "q": "Which TDS section applies to a corporate customer paying an outdoor caterer in 2026?",
          "a": "Under the Income Tax Act 2025, contractor-side TDS for catering services is deducted under Section 393(1)(a) using payment code 1002, replacing the legacy Section 194C of the 1961 Act. The rate is 1% where the payee is an individual or HUF and 2% otherwise, applied on payments above the prescribed threshold. The caterer reconciles deductions against Form 26AS quarterly. References to 194C still appear in older purchase orders and accounting systems but the operative provision for current-year deductions is Section 393(1)(a) payment code 1002.",
          "article": "Outdoor Catering Reconciliation in India: GST 18% with ITC, Advance Receipts, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/outdoor-catering-reconciliation-india"
        },
        {
          "q": "How does milestone billing work for a multi-day wedding or conference event?",
          "a": "Multi-day catering contracts typically run on a three-stage milestone billing pattern: a booking advance (often 25 to 40 percent) on PO confirmation, a pre-event milestone (often 50 to 60 percent) seven to fourteen days before the event, and a final reconciliation invoice within seven days of event close that adjusts for actual head count, menu upgrades, extension hours, and damage charges. Each milestone is its own tax invoice with 18% GST; advances flow through Section 13 receipt-voucher accounting; the final invoice nets the booking and milestone advances.",
          "article": "Outdoor Catering Reconciliation in India: GST 18% with ITC, Advance Receipts, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/outdoor-catering-reconciliation-india"
        },
        {
          "q": "What is the right reconciliation match shape for outdoor catering revenue?",
          "a": "The match shape is purchase order to event manifest to tax invoice to bank receipt — not POS to bank credit. The PO carries the contracted head count, menu, rate card, payment terms, and customer GSTIN and PAN. The event manifest captures actuals on the day. The tax invoice prices the actuals against the rate card and applies 18% GST. The bank receipt arrives net of any customer-deducted TDS under Section 393(1)(a). The reconciliation control is: invoice value minus TDS deducted equals the bank credit, and 26AS reflects the deducted amount within the same quarter.",
          "article": "Outdoor Catering Reconciliation in India: GST 18% with ITC, Advance Receipts, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/outdoor-catering-reconciliation-india"
        },
        {
          "q": "How does a multi-outlet QSR chain reconcile across multiple GSTINs?",
          "a": "Each state of operation requires a separate GSTIN, so a chain operating in Karnataka, Tamil Nadu, Maharashtra, and Delhi files four GSTR-1 and four GSTR-3B returns each month. The reconciliation runs at three levels: per-outlet sales matched to the local GSTIN, per-state aggregate matched to the state-GSTIN return, and chain-level consolidation for management reporting. Inter-GSTIN flows — central kitchen supplies, royalty fees, brand fees — move through tax invoices between the related GSTINs and require separate reconciliation against e-invoice and GSTR-2B.",
          "article": "QSR Chain Multi-Outlet Reconciliation: Rollup, Commissary, and Per-Outlet P&L",
          "url": "https://www.terra-insight.com/insights/qsr-chain-multi-outlet-reconciliation"
        },
        {
          "q": "How is central kitchen or commissary inventory reconciled to outlet sales?",
          "a": "The commissary issues delivery challans or tax invoices against outlet purchase orders. The reconciliation matches issued quantity to received quantity at the outlet, theoretical consumption from POS recipe maps to actual consumption from inventory counts, and the variance becomes the cost-of-goods variance per outlet. Persistent shortfalls at a specific outlet point to either receiving discrepancies or in-outlet wastage. The commissary also collects spoilage data that feeds into a chain-level wastage benchmark.",
          "article": "QSR Chain Multi-Outlet Reconciliation: Rollup, Commissary, and Per-Outlet P&L",
          "url": "https://www.terra-insight.com/insights/qsr-chain-multi-outlet-reconciliation"
        },
        {
          "q": "How are royalty and franchise fees reconciled across a chain?",
          "a": "Royalty is typically a percentage of franchisee gross sales — often 5% to 8% — invoiced monthly. The franchisor reconciles franchisee POS sales reports against the royalty invoice base. Variances usually arise from disputed sales (cancelled orders booked in the franchisee POS but not in the chain reporting feed) or aggregator versus dine-in mix where rates differ. A separate brand-fund or marketing-fund contribution at 1% to 3% follows the same logic. Both flows generate inter-company tax invoices that must reconcile to GSTR-1 at the franchisor's GSTIN.",
          "article": "QSR Chain Multi-Outlet Reconciliation: Rollup, Commissary, and Per-Outlet P&L",
          "url": "https://www.terra-insight.com/insights/qsr-chain-multi-outlet-reconciliation"
        },
        {
          "q": "How is per-outlet P&L produced for a 50-outlet chain?",
          "a": "Revenue at outlet level comes from POS daily close. Cost of goods comes from commissary issues plus local purchases, adjusted for opening and closing inventory. Direct costs (rent, electricity, payroll, utilities) are tagged to the outlet at booking. Allocated costs (head office, marketing fund, technology) are distributed by sales weight or fixed allocation. The reconciliation step is to ensure outlet revenue ties to the chain-level revenue per the GSTR-1 filings, after adjustments for inter-outlet supplies and aggregator settlements.",
          "article": "QSR Chain Multi-Outlet Reconciliation: Rollup, Commissary, and Per-Outlet P&L",
          "url": "https://www.terra-insight.com/insights/qsr-chain-multi-outlet-reconciliation"
        },
        {
          "q": "What does multi-bank consolidation look like for a QSR chain?",
          "a": "Different outlets often bank with whichever branch is nearest, producing a dozen current accounts across three or four banks. The chain-level cash position is the consolidation of all these accounts plus cash-in-transit and PG-in-transit balances. The reconciliation pulls bank statements from each account, matches deposits to the source outlet, applies inter-account transfers (sweep to chain master account), and produces a single chain treasury position daily. Variances flag stale items at outlet-level accounts that need clearing.",
          "article": "QSR Chain Multi-Outlet Reconciliation: Rollup, Commissary, and Per-Outlet P&L",
          "url": "https://www.terra-insight.com/insights/qsr-chain-multi-outlet-reconciliation"
        },
        {
          "q": "How should a restaurant chain frame total cost of ownership for aggregator reconciliation?",
          "a": "TCO has six components, none of them the headline subscription cost. First, finance team time at full-loaded cost — typically the largest line. Second, audit risk cost — the expected value of GST audit findings, CARO 2020 qualifications, and Section 393 TDS receivables that lapse. Third, dispute window losses on Swiggy and Zomato that go unrecovered. Fourth, ITC and cash-ledger leakage on commission GST and Section 52 TCS that is never claimed. Fifth, ERP integration and re-keying labour. Sixth, scale-out cost when adding a new aggregator or a new state GSTIN. A spreadsheet is cheap on line one and expensive on every other line; reconciliation infrastructure inverts that profile.",
          "article": "Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework",
          "url": "https://www.terra-insight.com/insights/restaurant-aggregator-reconciliation-build-vs-buy-vs-vendor-evaluation"
        },
        {
          "q": "What is the capability checklist for evaluating restaurant aggregator reconciliation software in India?",
          "a": "The minimum capability set is: multi-aggregator coverage (Zomato, Swiggy Food, Swiggy Instamart, ONDC, Magicpin, direct-channel) on a single engine; multi-outlet and multi-GSTIN rollup at outlet, GSTIN, state, channel, and chain level; India tax framework support — Section 393 TDS at 1% with payment code 1010, Section 52 CGST TCS with intra-state CGST/SGST and inter-state IGST split, Section 9(5) GST classifier, Section 17(5) blocked-credit handling; GSTR-2B commission ITC matching; GSTR-8A cash-ledger acceptance flow; GSTR-3B utilization mapping; CARO 2020 audit evidence retention; ERP write-back to Tally, SAP, Oracle, NetSuite, and Zoho without per-aggregator integration projects; SLA penalty and dispute-window management for Swiggy.",
          "article": "Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework",
          "url": "https://www.terra-insight.com/insights/restaurant-aggregator-reconciliation-build-vs-buy-vs-vendor-evaluation"
        },
        {
          "q": "When does building in-house with Excel and SQL still make sense for a restaurant chain?",
          "a": "Build in-house with Excel and SQL is defensible for chains below approximately 10 outlets and ₹50 lakh monthly aggregator GMV, and only if the chain operates within a single GSTIN. The break point is the cycle close that slips past the GSTR-3B and quarterly TDS filing windows. Once cycle close is at risk, the cost of audit findings and lapsed receivables exceeds the cost of any reconciliation product within one quarter. Chains that are growing fast should plan the transition before the break point, not after.",
          "article": "Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework",
          "url": "https://www.terra-insight.com/insights/restaurant-aggregator-reconciliation-build-vs-buy-vs-vendor-evaluation"
        },
        {
          "q": "What is the difference between per-aggregator reconciliation tools and reconciliation infrastructure?",
          "a": "Per-aggregator reconciliation tools — the category of products dedicated to a single aggregator surface — own the deduction trace inside that platform's settlement file. They are typically excellent at Zomato or at Swiggy individually. They stop at the platform boundary: GSTR-2B commission ITC matching, GSTR-8A cash-ledger acceptance, multi-aggregator consolidation, four-rail joins (aggregator + POS + bank + tax), and ERP write-back are usually outside the tool's scope. Reconciliation infrastructure treats restaurant aggregator reconciliation as one preset of many verticals on a config-driven engine, with all of those capabilities native and consistent across aggregators.",
          "article": "Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework",
          "url": "https://www.terra-insight.com/insights/restaurant-aggregator-reconciliation-build-vs-buy-vs-vendor-evaluation"
        },
        {
          "q": "How should a 100-outlet chain run a vendor evaluation?",
          "a": "Run a five-step evaluation. Step 1, define the four-rail close standard — aggregator, POS, bank, GST — that any candidate must demonstrate end to end. Step 2, score on the ten-dimension rubric (multi-aggregator, multi-outlet, India tax framework, GSTR-2B match, GSTR-8A acceptance, CARO 2020 evidence, ERP integration, dispute-window management, SLA penalty handling, multi-GSTIN rollup). Step 3, run a 30-day pilot on three weekly cycles for two outlets across two aggregators to validate cycle close. Step 4, assess implementation timeline (industry typical is 2 to 4 weeks for a config-driven engine; significantly longer for build-in-house or per-aggregator tool stacks). Step 5, validate audit posture — pull CARO 2020 evidence on the pilot data and have the chain's auditor sign off.",
          "article": "Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework",
          "url": "https://www.terra-insight.com/insights/restaurant-aggregator-reconciliation-build-vs-buy-vs-vendor-evaluation"
        },
        {
          "q": "What audit-grade evidence does CARO 2020 require for restaurant aggregator reconciliation?",
          "a": "CARO 2020 reporting requires the auditor to comment on internal financial controls, on undisputed statutory dues paid on time, and on any material discrepancy between physical and book records. For aggregator reconciliation, the evidence set is: order-level trace from gross sale through commission, GST on commission, Section 393 TDS, Section 52 CGST TCS, restaurant-borne discounts, SLA penalties, and refund reversals to the bank credit; reconciled GSTR-2B commission ITC per GSTIN; accepted GSTR-8A entries with cash-ledger utilization mapped to GSTR-3B; new TDS statement validation against book Section 393 receivable. Pull-on-demand for any cycle, any outlet, any GSTIN.",
          "article": "Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework",
          "url": "https://www.terra-insight.com/insights/restaurant-aggregator-reconciliation-build-vs-buy-vs-vendor-evaluation"
        },
        {
          "q": "How should a restaurant reconcile its POS Z-report to the bank cash deposit?",
          "a": "Run a four-point match each business day: POS Z-report cash component (gross sales minus card, UPI, wallet, aggregator), cash drawer count at shift close, cash room handover sheet to the pickup agent, and the bank credit narration referencing the deposit slip number. The four numbers should agree to the rupee. Any variance is classified into one of four buckets — short, over, voids, or refunds — and aged into a daily exception register that the outlet manager closes within 24 hours.",
          "article": "Restaurant Daily Cash Deposit Reconciliation: POS Z-Report to Bank Credit",
          "url": "https://www.terra-insight.com/insights/restaurant-daily-cash-deposit-reconciliation"
        },
        {
          "q": "What does a clean cash variance taxonomy look like for a restaurant?",
          "a": "Four buckets cover most outlets. Short: drawer count is below the Z-report cash figure with no documented reason. Over: drawer is above the Z-report (typically a missed void or an unreceipted sale). Voids: items struck off the bill after preparation, requiring manager override. Refunds: cash returned to the guest for billing errors or quality complaints. Each bucket has a separate signing authority and a separate ledger so end-of-month patterns are visible — repeated voids by a single cashier surface within a week.",
          "article": "Restaurant Daily Cash Deposit Reconciliation: POS Z-Report to Bank Credit",
          "url": "https://www.terra-insight.com/insights/restaurant-daily-cash-deposit-reconciliation"
        },
        {
          "q": "How do you detect pickup-agent shrinkage on cash deposits?",
          "a": "Reconcile three timestamps: cash room handover slip time, agent's deposit-slip stamp time at the bank, and the bank credit time. Persistent gaps of more than a few hours, or deposit-slip amounts that lag the handover sheet, point to either route diversions or partial deposits with shortfalls covered the next day. A daily aged variance report at outlet level highlights agents whose deposits routinely show timing or amount drift.",
          "article": "Restaurant Daily Cash Deposit Reconciliation: POS Z-Report to Bank Credit",
          "url": "https://www.terra-insight.com/insights/restaurant-daily-cash-deposit-reconciliation"
        },
        {
          "q": "How is multi-outlet daily cash rollup handled for a chain?",
          "a": "Each outlet posts its own four-point reconciliation to a central ledger that aggregates by region, brand, and bank. The chain-level rollup compares total POS Z-report cash across all outlets to total bank credits in the cash-collection account, exposing systemic gaps that single-outlet views miss. Outlets are ranked daily on variance per ₹1 lakh of cash sales — outliers two standard deviations above the chain average are escalated to area managers.",
          "article": "Restaurant Daily Cash Deposit Reconciliation: POS Z-Report to Bank Credit",
          "url": "https://www.terra-insight.com/insights/restaurant-daily-cash-deposit-reconciliation"
        },
        {
          "q": "What is the right cut-off for a restaurant cash deposit?",
          "a": "Two cut-offs work in practice. Late-night cash from dinner service is sealed in a tamper-evident bag at outlet close and held in the safe until morning pickup. Lunch and afternoon cash deposits same day if the bank branch accepts late-clearing deposits. The reconciliation books cash at the date of sale, not the date of bank credit, with a separate cash-in-transit ledger that ages each deposit until it clears the bank statement.",
          "article": "Restaurant Daily Cash Deposit Reconciliation: POS Z-Report to Bank Credit",
          "url": "https://www.terra-insight.com/insights/restaurant-daily-cash-deposit-reconciliation"
        },
        {
          "q": "What does a typical Indian restaurant franchisee pay the franchisor every month?",
          "a": "A franchisee in a QSR chain such as Domino's, Subway, or KFC, or in an Indian-origin chain like Wow! Momo or Chai Point, typically pays four recurring components: brand royalty as a percentage of gross sales (commonly 4% to 8%), a contribution to the national marketing fund or NMF (often 1% to 3%), a technology or platform fee for the POS and ordering stack, and a supply-chain margin embedded in commissary or central-kitchen purchases. There is also a one-time franchise fee at signing, which is amortised in the franchisee's books. Each component is invoiced separately and reconciled separately.",
          "article": "Restaurant Franchise Royalty Reconciliation in India: Brand Royalty, NMF, Tech Fee, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/restaurant-franchise-royalty-reconciliation-india"
        },
        {
          "q": "How is GST handled on royalty and other franchise fees?",
          "a": "Brand royalty, NMF contribution, and technology fee are inward supplies of services to the franchisee from the franchisor, taxed at 18% IGST or CGST+SGST depending on whether the parties are in different states. The franchisee claims input tax credit on these against the franchisee's outward supplies — but only against the 18%-with-ITC revenue lines such as catering or hotel-attached services. ITC against the 5% standalone restaurant supply line is blocked under Notification 11/2017-CTR. Supply-chain purchases from the franchisor commissary follow the GST rate of the underlying goods (typically 5% on prepared foods, 12% or 18% on packaged inputs).",
          "article": "Restaurant Franchise Royalty Reconciliation in India: Brand Royalty, NMF, Tech Fee, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/restaurant-franchise-royalty-reconciliation-india"
        },
        {
          "q": "What TDS applies on royalty paid by a franchisee to a franchisor in 2026?",
          "a": "Under the Income Tax Act 2025, royalty payments by a franchisee to a franchisor fall under Section 393(1)(b) and are deducted using payment code 1003 in the new TDS schedule. The legacy reference is Section 194J at 10% TDS on royalty and fees for technical services. The new code 1003 carries the same TDS rate band, but the schedule, return form, and challan minor head all change — franchisees must update their TDS engine to use the new section and code on every royalty payment from the new tax year, with cross-era reconciliation against any opening-balance royalty payable from the prior period.",
          "article": "Restaurant Franchise Royalty Reconciliation in India: Brand Royalty, NMF, Tech Fee, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/restaurant-franchise-royalty-reconciliation-india"
        },
        {
          "q": "How is national marketing fund (NMF) contribution reconciled?",
          "a": "NMF is collected from each franchisee at a contractual percentage of gross sales — typically 1% to 3% — and pooled centrally by the franchisor for brand-level advertising. The franchisee invoice from the franchisor shows NMF as a separate line. The reconciliation is two-sided: the franchisee verifies that NMF billed matches the franchisee's POS gross sales feed × NMF rate; the franchisor reconciles total NMF collected across all franchisees against total NMF marketing spend, with any surplus or deficit carried in a separate fund balance. Disputes typically arise on whether cancelled or refunded sales are included in the NMF base.",
          "article": "Restaurant Franchise Royalty Reconciliation in India: Brand Royalty, NMF, Tech Fee, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/restaurant-franchise-royalty-reconciliation-india"
        },
        {
          "q": "How does a franchisee reconcile commissary purchases against POS recipe consumption?",
          "a": "The franchisor commissary supplies prepared inputs and packaging to the franchisee against tax invoices. The franchisee receives the goods and matches receipt to invoice. Theoretical consumption from POS recipe maps gives the expected usage by SKU; physical inventory counts give actual usage; the variance is the commissary cost-of-goods variance per outlet. Persistent shortfalls point to receiving discrepancies, in-outlet wastage, or recipe yield issues. The supply-chain margin embedded in commissary pricing is not directly reconcilable by the franchisee — it is a contracted price — but the franchisee can benchmark commissary pricing against alternative-vendor pricing where the contract permits.",
          "article": "Restaurant Franchise Royalty Reconciliation in India: Brand Royalty, NMF, Tech Fee, and TDS Under Section 393",
          "url": "https://www.terra-insight.com/insights/restaurant-franchise-royalty-reconciliation-india"
        },
        {
          "q": "What GST rate does a standalone restaurant in India charge?",
          "a": "Standalone restaurants — those not located inside a hotel with declared room tariff of ₹7,500 or above — charge 5% GST (2.5% CGST + 2.5% SGST) without input tax credit, under Notification 11/2017 (CGST Rate) as amended. The rate applies whether the restaurant serves dine-in, takeaway, or supplies to aggregator platforms like Zomato and Swiggy. The no-ITC condition means GST paid on rent, equipment, ingredients (where applicable), and other inputs cannot be claimed against output liability.",
          "article": "Restaurant GST Reconciliation: When 5% Applies, When 18% Applies, and Why ITC Differs",
          "url": "https://www.terra-insight.com/insights/restaurant-gst-reconciliation-5pct-vs-18pct"
        },
        {
          "q": "When does a restaurant charge 18% GST with ITC?",
          "a": "Outdoor catering, banqueting services, and restaurants located inside a hotel with declared room tariff of ₹7,500 or above per unit per day charge 18% GST (9% CGST + 9% SGST or 18% IGST) with full input tax credit. The ₹7,500 threshold refers to the published tariff, not the actually charged rate after discounts. A hotel that publishes a ₹8,000 room tariff but discounts to ₹6,500 for the season still falls in the 18% with-ITC bracket for its restaurant.",
          "article": "Restaurant GST Reconciliation: When 5% Applies, When 18% Applies, and Why ITC Differs",
          "url": "https://www.terra-insight.com/insights/restaurant-gst-reconciliation-5pct-vs-18pct"
        },
        {
          "q": "How is the room tariff threshold tested for hotel-restaurants?",
          "a": "The threshold test under the rate notification is the declared tariff of any unit of accommodation in the hotel, not the average tariff and not the most-sold room category. If even one room category in the hotel is published at ₹7,500 or above, the entire restaurant operation falls into the 18% with-ITC bracket. The test is applied per financial year and the GSTIN must be consistent — switching mid-year requires careful documentation and is rarely advisable.",
          "article": "Restaurant GST Reconciliation: When 5% Applies, When 18% Applies, and Why ITC Differs",
          "url": "https://www.terra-insight.com/insights/restaurant-gst-reconciliation-5pct-vs-18pct"
        },
        {
          "q": "How are aggregator orders treated when a restaurant charges 5% GST?",
          "a": "For a 5% no-ITC restaurant supplying through Zomato or Swiggy, the aggregator collects 5% GST from the customer and the restaurant remits this through GSTR-3B as output tax. Section 9(5) of the CGST Act, as amended for restaurant services in 2022, makes the e-commerce operator liable to pay GST on certain restaurant services through the platform. The restaurant must reconcile the GSTR-2B aggregator entries against its own 5% output liability so reverse charge or operator-paid GST is correctly accounted for. Misclassification produces double payment or under-payment that surfaces in annual return GSTR-9C.",
          "article": "Restaurant GST Reconciliation: When 5% Applies, When 18% Applies, and Why ITC Differs",
          "url": "https://www.terra-insight.com/insights/restaurant-gst-reconciliation-5pct-vs-18pct"
        },
        {
          "q": "Can a hotel-restaurant claim ITC on aggregator commission?",
          "a": "Yes, if the hotel-restaurant is in the 18% with-ITC bracket. Aggregator commission charged at 18% GST is fully ITC-eligible against output tax from restaurant supplies. For a 5% no-ITC restaurant, the 18% GST on aggregator commission is not claimable as input credit and must be expensed gross. This single distinction can shift the after-tax economics of an outlet by 2% to 4% of revenue — material in a thin-margin business — and is a recurring source of overstated tax cost in 5% restaurants run by operators who did not realise the ITC bar applies.",
          "article": "Restaurant GST Reconciliation: When 5% Applies, When 18% Applies, and Why ITC Differs",
          "url": "https://www.terra-insight.com/insights/restaurant-gst-reconciliation-5pct-vs-18pct"
        },
        {
          "q": "Can a restaurant claim ITC on GST charged by Zomato or Swiggy on commission?",
          "a": "Yes, an 18% with-ITC restaurant can claim full input tax credit on the 18% GST charged by Zomato, Swiggy, or Magicpin on commission. The aggregator issues a monthly tax invoice for commission with GST, the entry flows into the restaurant's GSTR-2B as an inward supply, and the credit is claimable in GSTR-3B once the entry appears. A 5% no-ITC standalone restaurant cannot claim this credit and must expense the commission gross of GST. The distinction depends on the restaurant's own GST regime, not on the aggregator.",
          "article": "Restaurant GSTR-2B Commission ITC Reconciliation: Claiming 18% on Aggregator Commission",
          "url": "https://www.terra-insight.com/insights/restaurant-gstr-2b-commission-itc-reconciliation"
        },
        {
          "q": "What is Rule 36(4) and how does it apply to aggregator commission ITC?",
          "a": "Rule 36(4) of the CGST Rules limits ITC to invoices that have been uploaded by the supplier in GSTR-1 and reflected in the recipient's GSTR-2B. A restaurant cannot claim ITC on the aggregator commission invoice merely because it holds the invoice — the entry must appear in GSTR-2B for that month. If the aggregator files GSTR-1 late or under a wrong GSTIN, the credit slips to the next month or is lost entirely, and any provisional claim breaches Rule 36(4) and triggers a reversal with interest under Section 50.",
          "article": "Restaurant GSTR-2B Commission ITC Reconciliation: Claiming 18% on Aggregator Commission",
          "url": "https://www.terra-insight.com/insights/restaurant-gstr-2b-commission-itc-reconciliation"
        },
        {
          "q": "Why does aggregator commission sometimes not appear in GSTR-2B?",
          "a": "Three common causes. First, the aggregator filed GSTR-1 against a wrong restaurant GSTIN — common when a restaurant has multiple outlets across states and the aggregator's master data is out of date. Second, the aggregator filed late, pushing the entry to the next month's GSTR-2B. Third, the aggregator issued the invoice but did not file it in GSTR-1 at all — usually a data error that surfaces only when the restaurant queries the aggregator. Each cause requires a different remediation path with the aggregator's finance team.",
          "article": "Restaurant GSTR-2B Commission ITC Reconciliation: Claiming 18% on Aggregator Commission",
          "url": "https://www.terra-insight.com/insights/restaurant-gstr-2b-commission-itc-reconciliation"
        },
        {
          "q": "How are order cancellations handled in commission ITC reconciliation?",
          "a": "When an order is cancelled, the aggregator commission accrued on that order must be reversed. The aggregator issues a credit note in the same or subsequent month, which appears in the restaurant's GSTR-2B as a negative entry. The restaurant's GSTR-3B input tax credit must be reduced by the same amount in the period the credit note appears in 2B. Failing to track credit notes against original commission invoices is the single largest source of overstated ITC in restaurant filings and a top finding in GSTR-9C audits.",
          "article": "Restaurant GSTR-2B Commission ITC Reconciliation: Claiming 18% on Aggregator Commission",
          "url": "https://www.terra-insight.com/insights/restaurant-gstr-2b-commission-itc-reconciliation"
        },
        {
          "q": "What is the audit trail for commission ITC reconciliation?",
          "a": "Four artifacts. First, the aggregator settlement file with order-level commission and GST breakup. Second, the aggregator's monthly tax invoice for commission. Third, the GSTR-2B entry under the aggregator's GSTIN with matching invoice number and amount. Fourth, the restaurant's purchase register entry posting commission expense, input GST, and bank/payable settlement. All four must reconcile to the rupee for the credit to survive a Section 65 audit. Multi-outlet restaurants typically build this reconciliation in software because manual matching at order level is unworkable beyond 500 orders a month.",
          "article": "Restaurant GSTR-2B Commission ITC Reconciliation: Claiming 18% on Aggregator Commission",
          "url": "https://www.terra-insight.com/insights/restaurant-gstr-2b-commission-itc-reconciliation"
        },
        {
          "q": "Is liquor taxable under GST in India?",
          "a": "No. Alcoholic liquor for human consumption is constitutionally outside the GST regime under Article 366(12A) of the Constitution. It is taxed instead under the state-excise and VAT laws of each state. The GST Council has no jurisdiction over liquor pricing or rate. A restaurant or bar selling liquor charges state-VAT or excise duty as the case may be, not CGST or SGST. Bar food sold alongside the liquor remains under GST at 5% (standalone restaurant) or 18% (hotel-attached above the tariff threshold).",
          "article": "Restaurant Liquor and Bar Sales Reconciliation in India: State Excise vs GST, Permits, and Daily Stock Registers",
          "url": "https://www.terra-insight.com/insights/restaurant-liquor-bar-sales-reconciliation-india"
        },
        {
          "q": "How do excise rules differ across Karnataka, Maharashtra, Delhi, Tamil Nadu, and Telangana?",
          "a": "Karnataka operates through the Karnataka State Beverages Corporation Limited as a wholesale monopoly; FL-licensed retailers and bars buy stock against state-issued permits. Maharashtra licenses retailers under FL-II, FL-III, and FL-BR-II classes, with Mumbai and Pune carrying separate cess. Delhi runs through the Delhi State Industrial and Infrastructure Development Corporation with periodic policy resets. Tamil Nadu retails through TASMAC as a state monopoly — bars hold an FL-3 licence to serve TASMAC stock. Telangana licenses through the Prohibition and Excise Department with a quota-and-permit model. Each state's daily stock register format, return frequency, and excise duty structure differs.",
          "article": "Restaurant Liquor and Bar Sales Reconciliation in India: State Excise vs GST, Permits, and Daily Stock Registers",
          "url": "https://www.terra-insight.com/insights/restaurant-liquor-bar-sales-reconciliation-india"
        },
        {
          "q": "Why does a single restaurant bill often mix liquor and bar food?",
          "a": "A guest at a restaurant bar typically orders both food and drink. The same printed bill carries GST-taxable bar food lines (5% or 18% depending on outlet classification) and excise-or-VAT-taxable liquor lines. The POS must tag each line at source so that the day-end split feeds two parallel revenue ledgers — GST outward supply for food, excise sales for liquor — and the totals reconcile to bank credits without contaminating either tax leg.",
          "article": "Restaurant Liquor and Bar Sales Reconciliation in India: State Excise vs GST, Permits, and Daily Stock Registers",
          "url": "https://www.terra-insight.com/insights/restaurant-liquor-bar-sales-reconciliation-india"
        },
        {
          "q": "What is a daily stock-and-sales register and why does it matter for reconciliation?",
          "a": "Every FL-licence holder is required by state excise rules to maintain a daily stock register that records opening stock, receipts against permits, closing stock, and sales — typically in physical bottle units, not just rupee value. The register is open to inspection by excise officers and is the primary statutory record of liquor revenue. Reconciliation links three documents: permit-against-supply records from the state wholesaler, the daily physical stock register, and POS liquor sales — and surfaces variance as either short stock (operational shrinkage or pilferage) or excess sales (cash leakage, off-permit dispensing).",
          "article": "Restaurant Liquor and Bar Sales Reconciliation in India: State Excise vs GST, Permits, and Daily Stock Registers",
          "url": "https://www.terra-insight.com/insights/restaurant-liquor-bar-sales-reconciliation-india"
        },
        {
          "q": "Why does cash predominate for liquor sales in many states?",
          "a": "Several state excise regimes restrict or impose surcharges on card and digital payments at retail and bar outlets, and many TASMAC-style state-monopoly outlets are cash-only by policy. Even where digital payments are allowed at bars, customer behaviour skews cash because of privacy and rounding. The reconciliation consequence is that the cash leg of liquor revenue is much heavier than the cash leg of food revenue, and till variance discipline matters more — the daily till audit and the daily stock register together are the two-key control on liquor revenue integrity.",
          "article": "Restaurant Liquor and Bar Sales Reconciliation in India: State Excise vs GST, Permits, and Daily Stock Registers",
          "url": "https://www.terra-insight.com/insights/restaurant-liquor-bar-sales-reconciliation-india"
        },
        {
          "q": "What is the typical MDR by payment instrument for a restaurant in India?",
          "a": "UPI carries 0% MDR for merchant transactions under the current zero-MDR notification. Debit cards range from 0.4% to 0.9% depending on transaction value brackets. Domestic credit cards run 1.5% to 2%. International cards range from 2.5% to 3.5%. Wallet and BNPL instruments fall between 1.8% and 2.5%. The terminal acquirer — Pine Labs, MSwipe, Innoviti, or a bank — issues a monthly MDR statement that splits the deduction by instrument. GST at 18% on MDR is claimable as ITC against the acquirer's tax invoice.",
          "article": "Restaurant POS Payment Gateway Reconciliation: MDR, Settlement Cycle, and ITC",
          "url": "https://www.terra-insight.com/insights/restaurant-pos-payment-gateway-reconciliation"
        },
        {
          "q": "What are the typical settlement cycles for restaurant POS gateways in India?",
          "a": "Pine Labs and MSwipe settle T+1 for most card and UPI transactions, with international card payments often T+2 or T+3. Razorpay's POS product settles T+2 standard, T+1 with early settlement on card; UPI is T+1. PayU settles T+1 to T+2 by merchant category. Paytm-for-Business settles T+1 for QR-based UPI and T+2 for card payments. The settlement timing depends on the underlying network rails — UPI is faster than the card switch network.",
          "article": "Restaurant POS Payment Gateway Reconciliation: MDR, Settlement Cycle, and ITC",
          "url": "https://www.terra-insight.com/insights/restaurant-pos-payment-gateway-reconciliation"
        },
        {
          "q": "How is GST on MDR claimable as ITC for a restaurant?",
          "a": "The acquirer or gateway issues a monthly tax invoice carrying gross MDR plus 18% GST. The 18% GST on MDR is input tax credit available to the restaurant under Section 16 of the CGST Act, since payment processing is a service used in the course of business. The MDR expense and the ITC entry are booked monthly when the acquirer's invoice is received. ITC is claimed in the GSTR-3B for that period. The acquirer's GSTIN must appear on the invoice for the ITC to be valid.",
          "article": "Restaurant POS Payment Gateway Reconciliation: MDR, Settlement Cycle, and ITC",
          "url": "https://www.terra-insight.com/insights/restaurant-pos-payment-gateway-reconciliation"
        },
        {
          "q": "How are refund reversals handled in POS gateway reconciliation?",
          "a": "When a guest refund is processed on the POS terminal, the gateway reverses the original transaction in a later settlement cycle. The refund appears as a negative line in the settlement file, typically with the original transaction reference. The reconciliation matches the refund back to the original sale, reverses the revenue and output GST in the refund period (or via credit note in GSTR-1 if it crosses a filing period), and writes off the proportional MDR if the acquirer refunds it — most acquirers do not refund MDR on reversed transactions.",
          "article": "Restaurant POS Payment Gateway Reconciliation: MDR, Settlement Cycle, and ITC",
          "url": "https://www.terra-insight.com/insights/restaurant-pos-payment-gateway-reconciliation"
        },
        {
          "q": "What is the most common reconciliation error for restaurant POS payments?",
          "a": "Treating the bank credit as revenue. The bank credit is net of MDR, GST on MDR, and any in-cycle refunds. Booking the net figure as sales understates output tax (GST is collected on gross, not net) and ignores the ITC available on MDR. The right pattern is to reconstruct gross sales from the gateway settlement file at transaction level, book gross revenue with output GST on the gross, book MDR as a separate expense with GST on MDR as ITC, and net to the bank credit only at the cash-flow level.",
          "article": "Restaurant POS Payment Gateway Reconciliation: MDR, Settlement Cycle, and ITC",
          "url": "https://www.terra-insight.com/insights/restaurant-pos-payment-gateway-reconciliation"
        },
        {
          "q": "What GST rate applies to a dine-in restaurant in India in 2026?",
          "a": "Standalone restaurants — dine-in or takeaway — are taxed at 5% GST without input tax credit under Notification 11/2017-CTR (as amended). The 5% rate is mandatory; the restaurant cannot opt to pay 18% to claim ITC. The exception is a restaurant inside a hotel where the declared room tariff for any room in the same premises is ₹7,500 or above per night — that restaurant is taxed at 18% with full ITC.",
          "article": "Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split",
          "url": "https://www.terra-insight.com/insights/restaurant-reconciliation-india"
        },
        {
          "q": "Who pays GST on a Zomato or Swiggy order — the restaurant or the aggregator?",
          "a": "Since 1 January 2022, e-commerce operators including Zomato and Swiggy are liable to pay 5% GST on restaurant services delivered through their platform under Section 9(5) of the CGST Act. The restaurant does not charge GST to the aggregator on the food value for these orders, but the aggregator's commission invoice to the restaurant carries 18% GST, which is input-eligible for the restaurant against any 18%-with-ITC revenue lines.",
          "article": "Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split",
          "url": "https://www.terra-insight.com/insights/restaurant-reconciliation-india"
        },
        {
          "q": "What is TDS Section 194O and how does it apply to restaurants on Zomato and Swiggy?",
          "a": "Section 194O requires e-commerce operators to deduct 1% TDS on the gross sale value of goods or services facilitated through the platform when the seller is resident and the annual gross facilitated value exceeds ₹5 lakh. Zomato and Swiggy deduct 194O TDS from restaurant payouts and report it in the restaurant's Form 26AS. The TDS is on gross order value before commission, not on the net payout.",
          "article": "Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split",
          "url": "https://www.terra-insight.com/insights/restaurant-reconciliation-india"
        },
        {
          "q": "How is TCS under Section 52 different from TDS 194O on aggregator payouts?",
          "a": "TCS under Section 52 of the CGST Act is collected at 0.5% (0.25% CGST + 0.25% SGST, or 0.5% IGST) on the net taxable supplies made through the e-commerce platform — separate from income-tax TDS under 194O. TCS is reported in GSTR-8 by the operator and credited to the restaurant's electronic cash ledger via Form GSTR-2X claim. Restaurants must reconcile both in parallel: 194O against Form 26AS, TCS Section 52 against GSTR-2X.",
          "article": "Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split",
          "url": "https://www.terra-insight.com/insights/restaurant-reconciliation-india"
        },
        {
          "q": "How often should a restaurant in India reconcile aggregator payouts to bank credits?",
          "a": "Most chains run a daily three-way reconciliation: POS order log vs aggregator settlement report vs bank credit. Net settlement cycles are typically T+1 to T+7 depending on contract — Zomato is commonly T+7 weekly, Swiggy T+1 to T+3 daily — so the bank-leg match is rolling. A weekly variance close on commission, TDS 194O, TCS Section 52, packaging fee, and cancellation deductions catches under-payouts before they age beyond the dispute window.",
          "article": "Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split",
          "url": "https://www.terra-insight.com/insights/restaurant-reconciliation-india"
        },
        {
          "q": "What is a typical commission rate charged by Zomato and Swiggy to restaurants?",
          "a": "Public commission ranges disclosed in trade reporting and CCI proceedings sit in the 18–30% band on order value, with new restaurant onboardings and high-discount campaigns reaching 30–35%. The exact rate is contract-specific and varies by city, cuisine, exclusivity tier, and promotional participation. The reconciliation control is not the rate itself — it is verifying that the rate billed in each settlement matches the rate agreed in the contract, line-by-line.",
          "article": "Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split",
          "url": "https://www.terra-insight.com/insights/restaurant-reconciliation-india"
        },
        {
          "q": "Is service charge mandatory in Indian restaurants in 2026?",
          "a": "No. The Central Consumer Protection Authority guidelines dated 4 July 2022 made it clear that service charge cannot be added automatically or by default to a food bill. Customers must be informed that service charge is voluntary, and they can request that it be removed. The guidelines remain in force in 2026 — they are CCPA consumer-protection law and are unaffected by the new Income Tax Act 2025. Restaurants that auto-bill service charge without explicit consent face customer complaints under the Consumer Protection Act 2019 and possible enforcement action by CCPA.",
          "article": "Restaurant Service Charge and Tip Pool Reconciliation in India: CCPA Rules, GST, and Salary TDS on Tips",
          "url": "https://www.terra-insight.com/insights/restaurant-service-charge-tip-pool-reconciliation-india"
        },
        {
          "q": "What GST rate applies to service charge collected by a restaurant?",
          "a": "Service charge is treated as part of the consideration for the supply of restaurant service and is taxed at the same rate as the food bill it sits alongside. A standalone restaurant taxed at 5% GST without ITC under Notification 11/2017-CTR charges 5% GST on service charge as well. A restaurant inside a hotel where any declared room tariff is ₹7,500 or above per night is taxed at 18% with full ITC, and the service charge follows that 18% line. Service charge is included in the taxable value of supply — it is not a separate exempt line.",
          "article": "Restaurant Service Charge and Tip Pool Reconciliation in India: CCPA Rules, GST, and Salary TDS on Tips",
          "url": "https://www.terra-insight.com/insights/restaurant-service-charge-tip-pool-reconciliation-india"
        },
        {
          "q": "How is the tip pool taxed when distributed to staff?",
          "a": "If the tip pool is formally added to staff salary or wages and runs through the payroll register, it is taxable in the hands of the employee under the head Salaries and the employer must deduct salary TDS under Section 392 of the Income Tax Act 2025 using payment code 1001 in the new TDS schedule (the legacy reference is Section 192). If the restaurant treats tip pool as a pass-through outside payroll — collected at the till and physically distributed to staff without entering the payroll system — the tax obligation shifts to the employee individually under Income from Other Sources, and the employer does not deduct TDS. Most chains formalise the tip pool through payroll for audit and ESI/PF clarity.",
          "article": "Restaurant Service Charge and Tip Pool Reconciliation in India: CCPA Rules, GST, and Salary TDS on Tips",
          "url": "https://www.terra-insight.com/insights/restaurant-service-charge-tip-pool-reconciliation-india"
        },
        {
          "q": "How is service charge reconciled when a customer opts out?",
          "a": "The POS must support a customer-opt-out function that removes the service charge line from the bill at the till. The reconciliation control is that opt-out adjustments are recorded as a separate POS event with a reason code, not as a simple discount. End-of-shift, the service charge collected as a percentage of the chargeable bill must tie to the POS service-charge line item, which must tie to revenue in the books. Where opt-outs are recorded as discounts, GST recalculation becomes ambiguous and the audit trail is broken.",
          "article": "Restaurant Service Charge and Tip Pool Reconciliation in India: CCPA Rules, GST, and Salary TDS on Tips",
          "url": "https://www.terra-insight.com/insights/restaurant-service-charge-tip-pool-reconciliation-india"
        },
        {
          "q": "Are tip pool distributions subject to PF and ESI?",
          "a": "If the tip pool is added to salary as a regular component, the EPF and ESI Acts include it in the wages definition — particularly where the distribution is contractual or customary. The safer treatment, adopted by most organised chains, is to include tip pool in PF/ESI wages where it forms a regular part of compensation, and to document the policy in the appointment letter. Treating tips as a wholly separate gratuity outside wages exposes the restaurant to retrospective demand if the labour authorities reclassify.",
          "article": "Restaurant Service Charge and Tip Pool Reconciliation in India: CCPA Rules, GST, and Salary TDS on Tips",
          "url": "https://www.terra-insight.com/insights/restaurant-service-charge-tip-pool-reconciliation-india"
        },
        {
          "q": "How does Swiggy's settlement structure differ from Zomato's for reconciliation purposes?",
          "a": "The shared deductions are commission, 18% GST on commission, Section 393 TDS at 1% under payment code 1010, and Section 52 CGST TCS at 1%. The Swiggy-specific layers that change the reconciliation workflow are: SLA penalty fees for late preparation, post-acceptance cancellation, or rejection; explicit restaurant-borne discount components for campaigns where the restaurant agreed to fund part of the offer; and the Food vs Instamart channel split with different GST treatments and commission tables. These structural differences mean a Zomato reconciliation playbook cannot be ported to Swiggy without channel-specific rules.",
          "article": "Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation",
          "url": "https://www.terra-insight.com/insights/swiggy-reconciliation-comparison-multi-outlet-qsr"
        },
        {
          "q": "What is the Swiggy Partner Portal dispute window?",
          "a": "Swiggy Partner Portal allows disputes on settlement entries within 7 to 14 days of cycle close, depending on the dispute category. Commission variances, refund reversals, and SLA penalties each carry their own resolution windows. Disputes raised after the window close are not entertained and the deduction stands. For a 50-outlet chain processing roughly 70,000 orders a week, missing the dispute window is a financial loss that no audit cycle can recover.",
          "article": "Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation",
          "url": "https://www.terra-insight.com/insights/swiggy-reconciliation-comparison-multi-outlet-qsr"
        },
        {
          "q": "What is the Section 393 TDS rate Swiggy deducts under the new Income Tax Act?",
          "a": "Section 393 of the Income Tax Act 2025 carries forward the e-commerce operator TDS regime from legacy Section 194O. Swiggy deducts 1% on gross supply value, deposits under payment code 1010, and reports in the new TDS statement format under the chain's PAN. The threshold exemption is ₹5 lakh aggregate per financial year for individual or HUF restaurant deductees. The reconciliation must claim this credit in the same year against advance tax instalments.",
          "article": "Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation",
          "url": "https://www.terra-insight.com/insights/swiggy-reconciliation-comparison-multi-outlet-qsr"
        },
        {
          "q": "How does the four-rail framework apply to Swiggy reconciliation?",
          "a": "The four rails are aggregator (Swiggy Partner settlement), POS (the chain's order management system), cash (the bank credit narration), and GST (GSTR-2B for commission ITC plus GSTR-8A for Section 52 TCS plus the electronic cash ledger). A reconciliation closes only when all four rails join at order level for each weekly cycle. Manual Excel can join two rails consistently. An aggregator-side tool joins aggregator and POS. Reconciliation infrastructure joins all four with multi-statute posting.",
          "article": "Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation",
          "url": "https://www.terra-insight.com/insights/swiggy-reconciliation-comparison-multi-outlet-qsr"
        },
        {
          "q": "How does multi-GSTIN consolidation work for a 30 to 100 outlet Swiggy chain?",
          "a": "A 30 to 100 outlet chain typically operates under 5 to 18 GSTINs depending on state spread. Each GSTIN has its own GSTR-1, GSTR-3B, GSTR-8A acceptance, and electronic cash ledger. Swiggy issues a separate settlement file per channel (Food and Instamart) but rolls commission tax invoices to the chain's billing GSTINs as agreed. Consolidation must aggregate at outlet, GSTIN, state, channel, and chain levels — five rollup dimensions — and reconcile each against the GST portal's GSTIN-level filings.",
          "article": "Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation",
          "url": "https://www.terra-insight.com/insights/swiggy-reconciliation-comparison-multi-outlet-qsr"
        },
        {
          "q": "When does an aggregator-side reconciliation tool stop being enough for a Swiggy chain?",
          "a": "Aggregator-side reconciliation tools cover the Swiggy-specific deduction stack cleanly within the platform boundary. They typically stop at the point where the chain needs: GSTR-2B commission ITC matching across states, GSTR-8A Section 52 cash-ledger acceptance per GSTIN, Section 9(5) GST liability classification, multi-aggregator consolidation (Zomato, ONDC, Magicpin, direct-channel) on the same engine, four-rail joins for CARO 2020 audit evidence, and ERP write-back without a separate integration per aggregator. Past those needs, the chain is stitching multiple tools and reintroducing the workflow gaps the tool was bought to remove.",
          "article": "Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation",
          "url": "https://www.terra-insight.com/insights/swiggy-reconciliation-comparison-multi-outlet-qsr"
        },
        {
          "q": "How does Swiggy's settlement structure differ from Zomato's?",
          "a": "Both deduct platform commission, 18% GST on commission, 1% TDS under Section 194O, and 1% TCS under Section 52. Swiggy adds two distinct deduction lines that Zomato handles differently: SLA penalty fees for late preparation, rejected orders, or excessive cancellations, and explicit restaurant-borne discount components for offers like Swiggy One or coupon-funded promotions where the restaurant agreed to bear part of the discount. Swiggy's payout cycle is weekly, typically credited every Tuesday or Wednesday, in line with Zomato's cadence.",
          "article": "Swiggy Restaurant Settlement Reconciliation: Food, Instamart, and SLA Penalties",
          "url": "https://www.terra-insight.com/insights/swiggy-restaurant-settlement-reconciliation"
        },
        {
          "q": "What is the dispute window for a Swiggy settlement entry?",
          "a": "Swiggy Partner Portal allows restaurants to raise a dispute on a settlement entry within 7 to 14 days of the cycle close, depending on the dispute category. Disputes on commission calculation, refund reversals, or SLA penalties are reviewed by the Swiggy partner support team, with resolution typically in 5 to 10 business days. Disputes raised after the window close are not entertained and the deduction stands. Reconciliation must surface variances within the dispute window or the financial loss becomes permanent.",
          "article": "Swiggy Restaurant Settlement Reconciliation: Food, Instamart, and SLA Penalties",
          "url": "https://www.terra-insight.com/insights/swiggy-restaurant-settlement-reconciliation"
        },
        {
          "q": "How are Swiggy Instamart payouts different from Swiggy Food payouts?",
          "a": "Swiggy Instamart operates as a quick-commerce inventory model, where the seller relationship and GST treatment differ from Swiggy Food restaurant listings. Instamart sellers typically operate under standard 18% or 12% GST rates depending on product category, while restaurant food on Swiggy Food is taxed at 5% without ITC under composition or specific notifications. Commission structures, settlement files, and SLA frameworks for Instamart are issued separately from the Food platform — the two should never be reconciled in the same workflow.",
          "article": "Swiggy Restaurant Settlement Reconciliation: Food, Instamart, and SLA Penalties",
          "url": "https://www.terra-insight.com/insights/swiggy-restaurant-settlement-reconciliation"
        },
        {
          "q": "What is the typical commission Swiggy charges restaurants?",
          "a": "Swiggy commission ranges from 18% to 25% for standard partner tiers, climbing to 25% to 30% or higher for delivery-only kitchens and metro zones. Newly onboarded restaurants and restaurants on subscription or zero-fee programs face different slabs. Swiggy issues a monthly tax invoice for commission at 18% GST that is fully ITC-eligible. The GST on commission alone, on a ₹10 lakh monthly gross, can be ₹40,000 to ₹50,000 of recoverable input tax.",
          "article": "Swiggy Restaurant Settlement Reconciliation: Food, Instamart, and SLA Penalties",
          "url": "https://www.terra-insight.com/insights/swiggy-restaurant-settlement-reconciliation"
        },
        {
          "q": "How does a restaurant reconcile food token or coupon-borne discounts on Swiggy?",
          "a": "Swiggy offers two types of discounts: platform-borne (funded entirely by Swiggy and not deducted from the restaurant payout) and restaurant-borne (funded by the restaurant under a campaign agreement, deducted from the payout). The settlement file separates these as discount-Swiggy and discount-restaurant lines. For 194O TDS, the gross sale value excludes platform-borne discounts. For book revenue, the restaurant must accrue at the customer-paid value and book the restaurant-borne discount as a separate marketing expense. Mixing the two understates revenue and TDS receivable.",
          "article": "Swiggy Restaurant Settlement Reconciliation: Food, Instamart, and SLA Penalties",
          "url": "https://www.terra-insight.com/insights/swiggy-restaurant-settlement-reconciliation"
        },
        {
          "q": "Has Section 52 of the CGST Act changed under the Income Tax Act 2025?",
          "a": "No. Section 52 of the CGST Act 2017 is GST law and is completely unchanged by the Income Tax Act 2025. The 1% TCS collection by e-commerce aggregators on net taxable supplies, the monthly GSTR-8 filing requirement, and the auto-population of the credit into the supplier's electronic cash ledger all continue exactly as before. Section 52 must not be confused with Section 206C of the Income Tax Act, which is the income-tax TCS regime — that one did move to Section 394 of the new Income Tax Act 2025 with payment codes 1071 onward, but Section 52 sits in a separate statute and stays put.",
          "article": "TCS Section 52 on Restaurant Aggregator Settlements: Reconciling GSTR-8 to the GST Cash Ledger",
          "url": "https://www.terra-insight.com/insights/tcs-section-52-restaurant-aggregator-reconciliation"
        },
        {
          "q": "What is the base for Section 52 TCS on a restaurant supply through Zomato or Swiggy?",
          "a": "Section 52 applies 1% TCS on the net value of taxable supplies made by the restaurant through the e-commerce platform during the calendar month. Net taxable supply means the gross outward supply less any returns, refunds, or cancellations processed in the same month. The base excludes supplies that are not taxable (zero-rated or exempt items, where applicable). The 1% is split as 0.5% CGST and 0.5% SGST for intra-state supplies, or charged as 1% IGST for inter-state supplies. The aggregator computes the figure restaurant-by-restaurant and reports it in GSTR-8.",
          "article": "TCS Section 52 on Restaurant Aggregator Settlements: Reconciling GSTR-8 to the GST Cash Ledger",
          "url": "https://www.terra-insight.com/insights/tcs-section-52-restaurant-aggregator-reconciliation"
        },
        {
          "q": "How does the Section 52 TCS credit reach the restaurant's electronic cash ledger?",
          "a": "The aggregator files GSTR-8 by the 10th of the following month, declaring the TCS collected supplier-wise. The portal auto-populates the entries into the supplier's GSTR-2A and into a TCS-specific section of the supplier's electronic cash ledger. The restaurant accepts the entries via its GSTR-8A reconciliation view and the credit becomes available for utilization. The credit is not ITC — it is a cash-ledger balance that offsets the restaurant's output GST liability when GSTR-3B is filed. The claim-and-clear cycle therefore moves through GSTR-8 (aggregator) to GSTR-8A (auto-populated for supplier) to the cash ledger to GSTR-3B utilization.",
          "article": "TCS Section 52 on Restaurant Aggregator Settlements: Reconciling GSTR-8 to the GST Cash Ledger",
          "url": "https://www.terra-insight.com/insights/tcs-section-52-restaurant-aggregator-reconciliation"
        },
        {
          "q": "How are refunds and cancellations reflected in Section 52 TCS reconciliation?",
          "a": "When a restaurant order is refunded or cancelled within the same calendar month as the original supply, the aggregator nets the refund into the month's gross taxable supply before computing 1% TCS — so the GSTR-8 entry already reflects the reversal. If the refund is processed in a later month, the aggregator reduces the next month's net taxable supply and the corresponding TCS, resulting in a smaller credit in the supplier's cash ledger that month. Reconciliation must therefore match each refund-period reversal back to the original sale period in the books while accepting that the GSTR-8 timing follows aggregator processing, not the original transaction date.",
          "article": "TCS Section 52 on Restaurant Aggregator Settlements: Reconciling GSTR-8 to the GST Cash Ledger",
          "url": "https://www.terra-insight.com/insights/tcs-section-52-restaurant-aggregator-reconciliation"
        },
        {
          "q": "Is Section 52 TCS the same as the income-tax TCS that Zomato collects?",
          "a": "No, and conflating the two is the most common reconciliation mistake. Section 52 TCS is a GST-law mechanism — 1% collected by the aggregator on net taxable supplies, deposited under the CGST Act, reported in GSTR-8, and credited into the supplier's GST electronic cash ledger to offset output GST. Income-tax TCS sits under Section 206C of the Income Tax Act 1961, now Section 394 of the Income Tax Act 2025 with payment codes 1071 onward, and applies in different transactional contexts. Restaurant aggregator settlements involve only the GST Section 52 TCS, not income-tax Section 206C / Section 394. The two regimes have separate bases, separate filings, and separate ledgers.",
          "article": "TCS Section 52 on Restaurant Aggregator Settlements: Reconciling GSTR-8 to the GST Cash Ledger",
          "url": "https://www.terra-insight.com/insights/tcs-section-52-restaurant-aggregator-reconciliation"
        },
        {
          "q": "What replaced Section 194O for TDS on restaurant aggregator settlements?",
          "a": "From April 1, 2026, Section 194O of the Income Tax Act 1961 has been replaced by Section 393 of the Income Tax Act 2025, with payment code 1010 used on the new challan ITNS 281 for e-commerce operator deductions. The substantive provisions remain similar — 1% TDS on the gross amount of sale of goods or services facilitated through an e-commerce platform — but the deduction is now reported under code 1010 in Form 168, the new annual tax statement that replaces Form 26AS. Aggregators including Zomato and Swiggy migrated their TAN-level deduction reporting to the new code from FY 2026-27 onward.",
          "article": "Section 393 TDS on Restaurant Aggregator Settlements: Reconciling Payment Code 1010",
          "url": "https://www.terra-insight.com/insights/tds-393-restaurant-aggregator-reconciliation"
        },
        {
          "q": "Is Section 393 TDS computed on gross order value or net of commission?",
          "a": "Section 393, like its predecessor 194O, applies 1% TDS on the gross amount of sale of goods or services facilitated through the platform — meaning the order value paid by the customer, before the aggregator deducts its commission. The base does include the GST component of the underlying supply by the restaurant, but excludes any platform-borne discounts or coupons that the aggregator absorbs. Reconciliation breaks most often occur when finance teams accrue TDS on the net payout (after commission) rather than the gross order value, leading to a permanent understatement of the receivable in books.",
          "article": "Section 393 TDS on Restaurant Aggregator Settlements: Reconciling Payment Code 1010",
          "url": "https://www.terra-insight.com/insights/tds-393-restaurant-aggregator-reconciliation"
        },
        {
          "q": "How do FY 2025-26 deductions under Section 194O appear in FY 2026-27 Form 168?",
          "a": "Deductions made by aggregators on or before March 31, 2026 fall under legacy Section 194O and the old payment codes; deductions from April 1, 2026 onward use Section 393 and payment code 1010. The transition window is messy because aggregator settlement files often span the cross-era boundary — an order placed on March 30 may settle on April 4 with TDS deducted under the new code, while a March 28 order may carry old-code TDS that lands in the FY 2025-26 Form 26AS. Form 168 for FY 2026-27 will show only Section 393 entries; FY 2025-26 final Form 26AS captures the residual 194O credits. Reconciliation must split the receivable ledger accordingly.",
          "article": "Section 393 TDS on Restaurant Aggregator Settlements: Reconciling Payment Code 1010",
          "url": "https://www.terra-insight.com/insights/tds-393-restaurant-aggregator-reconciliation"
        },
        {
          "q": "What are the typical reconciliation gaps between aggregator TDS and Form 168?",
          "a": "Three gaps recur. First, timing — aggregators deposit TDS by the 7th of the following month, so a March 28 deduction lands in Form 168 for FY 2026-27 only after the deductor files its quarterly TDS return. Second, wrong PAN — multi-outlet restaurants sometimes register different PANs at the aggregator level versus the bank account level, causing TDS to credit the wrong entity. Third, settlement-period crossover — refunds and RTO reversals processed in a later cycle reduce the original TDS base, but the aggregator's revised TDS filing may lag the settlement file by 30 to 60 days.",
          "article": "Section 393 TDS on Restaurant Aggregator Settlements: Reconciling Payment Code 1010",
          "url": "https://www.terra-insight.com/insights/tds-393-restaurant-aggregator-reconciliation"
        },
        {
          "q": "Which challan and payment code does an aggregator use for Section 393 deductions on restaurant payouts?",
          "a": "Aggregators deposit Section 393 TDS using challan ITNS 281 with payment code 1010, which is the dedicated code for e-commerce operator deductions under the Income Tax Act 2025. The challan carries the deductor's TAN, the assessment year, and the section reference. Restaurants do not file the challan themselves — they verify the deposit by matching the deductor TAN and the rupee figure against their Form 168 entries, and by ensuring the aggregator's quarterly TDS return (Form 26Q) reconciles to the order-level breakdown in the settlement file.",
          "article": "Section 393 TDS on Restaurant Aggregator Settlements: Reconciling Payment Code 1010",
          "url": "https://www.terra-insight.com/insights/tds-393-restaurant-aggregator-reconciliation"
        },
        {
          "q": "At what outlet count does manual Excel reconciliation of Zomato settlements break down?",
          "a": "The break point is not a fixed outlet count — it is the order volume at which the deduction-stack arithmetic starts to drop entries. Practically, a finance team can hold the workflow together up to about 10 outlets and roughly 6,000 orders a week. Beyond that, weekly cycle close starts slipping past the GSTR-3B and quarterly TDS filing windows. At 50 outlets and 30,000-plus orders a week, manual Excel cannot complete a full order-level trace inside a month, and Section 52 cash-ledger balances drift against GSTR-2B.",
          "article": "Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets",
          "url": "https://www.terra-insight.com/insights/zomato-reconciliation-comparison-excel-cointab-transactig"
        },
        {
          "q": "What does an aggregator-side reconciliation tool do that Excel does not?",
          "a": "Aggregator-side reconciliation tools — the per-platform category that includes products dedicated to Zomato or Swiggy reconciliation — automate the Zomato settlement file ingestion, decompose the deduction stack at order level, and surface variances against POS data. They remove the manual VLOOKUP burden and the multi-tab risk. Where they typically stop is the boundary of the Zomato workflow itself: bank-reconciliation linking, GSTR-2B commission ITC matching, and Section 393 TDS posting into the books for cross-period claim are usually outside the tool's scope and handed back to the finance team.",
          "article": "Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets",
          "url": "https://www.terra-insight.com/insights/zomato-reconciliation-comparison-excel-cointab-transactig"
        },
        {
          "q": "What is the Section 393 TDS rate and payment code for Zomato restaurant settlements?",
          "a": "Section 393 of the Income Tax Act 2025 carries forward the e-commerce operator TDS regime from legacy Section 194O. The rate is 1% on the gross amount of supply facilitated through the platform, deducted by Zomato and deposited under payment code 1010. The threshold exemption is the same ₹5 lakh aggregate per financial year for individual or HUF restaurant deductees. The deduction reflects in the new TDS statement format and feeds the restaurant's tax credit, claimable in the same year. References to legacy Section 194O remain valid for historical periods only.",
          "article": "Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets",
          "url": "https://www.terra-insight.com/insights/zomato-reconciliation-comparison-excel-cointab-transactig"
        },
        {
          "q": "How does the Section 52 CGST TCS interact with the Section 393 income tax TDS on the same Zomato order?",
          "a": "Section 52 of the CGST Act and Section 393 of the Income Tax Act 2025 are two separate regimes operating on the same transaction. Section 393 deducts 1% income tax TDS on the gross supply value, deposited under payment code 1010, and reaches the restaurant via the income-tax credit ledger. Section 52 collects 1% GST TCS on the net taxable supply (gross less same-month refunds), filed by Zomato in monthly GSTR-8, and reaches the restaurant via the GST electronic cash ledger to offset output GST in GSTR-3B. The bases are different and the ledgers are different. Reconciliation must keep them strictly separate.",
          "article": "Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets",
          "url": "https://www.terra-insight.com/insights/zomato-reconciliation-comparison-excel-cointab-transactig"
        },
        {
          "q": "What CARO 2020 audit evidence does Zomato reconciliation need to produce?",
          "a": "CARO 2020 reporting requires the auditor to comment on whether the company's books reflect undisputed statutory dues paid on time, on whether material discrepancies exist between physical and book records, and on internal financial controls. For Zomato settlements, that translates into order-level trace from gross sale through commission, GST on commission, Section 393 TDS, Section 52 TCS, restaurant-borne discounts, and bank credit, plus reconciled GSTR-2B commission ITC, GSTR-8A cash-ledger acceptance, and Form 26AS / new TDS statement validation. The evidence must be pull-on-demand for each weekly cycle of the audit period.",
          "article": "Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets",
          "url": "https://www.terra-insight.com/insights/zomato-reconciliation-comparison-excel-cointab-transactig"
        },
        {
          "q": "What buyer-side criteria distinguish reconciliation infrastructure from a Zomato-only tool?",
          "a": "Five criteria separate the two categories. First, multi-aggregator scope on the same engine — Zomato, Swiggy Food, Swiggy Instamart, ONDC, Magicpin, and direct-channel orders. Second, the four-rail join — aggregator, POS, bank, and tax (GST plus TDS). Third, India tax framework support out of the box: Section 393 with payment code 1010, Section 52 CGST TCS with intra-state and inter-state split, Section 9(5) GST liability flagging, GSTR-2B commission ITC matching. Fourth, multi-outlet and multi-GSTIN rollup with audit-grade evidence retention. Fifth, ERP write-back without a separate integration project for each aggregator. A Zomato-only tool covers the first item only.",
          "article": "Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets",
          "url": "https://www.terra-insight.com/insights/zomato-reconciliation-comparison-excel-cointab-transactig"
        },
        {
          "q": "How does Zomato deduct TDS under Section 194O on a restaurant payout?",
          "a": "Section 194O requires e-commerce operators to deduct 1% TDS on the gross amount of sale of goods or services facilitated through their platform. For a restaurant on Zomato, the 1% TDS applies on the net taxable supply (after discounts borne by Zomato are excluded but before commission deduction). The deduction appears as a separate line on the weekly settlement and reflects in Form 26AS of the restaurant's PAN. Threshold exemption is ₹5 lakh in aggregate per financial year for individual or HUF restaurant owners.",
          "article": "Zomato Restaurant Settlement Reconciliation: How Weekly Payouts Match Orders",
          "url": "https://www.terra-insight.com/insights/zomato-restaurant-settlement-reconciliation"
        },
        {
          "q": "What is the TCS rate Zomato collects under Section 52 of CGST Act?",
          "a": "Under Section 52 of the CGST Act, e-commerce operators including Zomato collect TCS at 1% (0.5% CGST + 0.5% SGST for intra-state, or 1% IGST for inter-state) on the net value of taxable supplies made through the platform. Zomato deposits this TCS and files GSTR-8 monthly. The restaurant claims the TCS credit by accepting the auto-populated entry in GSTR-2A and offsetting against output GST liability.",
          "article": "Zomato Restaurant Settlement Reconciliation: How Weekly Payouts Match Orders",
          "url": "https://www.terra-insight.com/insights/zomato-restaurant-settlement-reconciliation"
        },
        {
          "q": "What commission percentage does Zomato charge restaurants?",
          "a": "Public commission ranges run from 18% to 25% for standard partner restaurants, scaling to 25% to 35% for delivery-only or zero-fee subscription tiers depending on city, restaurant rating, and order value. Zomato Gold or Pro partner programs carry separate commission slabs. The commission is deducted gross of GST, with Zomato issuing a tax invoice for the commission at 18% GST that is ITC-eligible for the restaurant against its output tax.",
          "article": "Zomato Restaurant Settlement Reconciliation: How Weekly Payouts Match Orders",
          "url": "https://www.terra-insight.com/insights/zomato-restaurant-settlement-reconciliation"
        },
        {
          "q": "How are refunds and RTO orders handled in Zomato's weekly settlement?",
          "a": "Refunds processed during a settlement week appear as negative line items in the next payout file, often spanning the cycle after the original sale. Return-to-origin (RTO) for delivery cancellations is reversed in full if the cancellation occurs before dispatch; partial refund applies for post-dispatch cancellations. The reconciliation must match each refund or RTO back to the original order ID and reverse the output GST and 194O TDS accrued in the original sale period via GSTR-1 amendment if it crosses a filing month.",
          "article": "Zomato Restaurant Settlement Reconciliation: How Weekly Payouts Match Orders",
          "url": "https://www.terra-insight.com/insights/zomato-restaurant-settlement-reconciliation"
        },
        {
          "q": "Why does the bank credit from Zomato never match the order total in Zomato dashboard?",
          "a": "The bank credit is the residual after seven deductions: commission (18 to 35 percent), GST on commission (18 percent), TDS under 194O (1 percent), TCS under Section 52 (1 percent), ad spend or promoted-listing fees, refund reversals from earlier cycles, and platform charges or packaging fees if applicable. A ₹1,00,000 gross sales week can settle at ₹62,000 to ₹70,000 net. Reconciliation requires unpacking each of these heads against the order-level data, not the dashboard summary.",
          "article": "Zomato Restaurant Settlement Reconciliation: How Weekly Payouts Match Orders",
          "url": "https://www.terra-insight.com/insights/zomato-restaurant-settlement-reconciliation"
        }
      ]
    },
    "audit-assurance": {
      "label": "Audit and Assurance",
      "faqs": [
        {
          "q": "Which branches and NBFCs are required to have a concurrent audit?",
          "a": "Under the RBI Master Direction on Concurrent Audit System in Commercial Banks (updated 2019 with subsequent revisions), concurrent audit is mandatory for: all specialised branches handling foreign exchange, large corporate credit, and treasury; branches contributing 50% or more of a bank's total deposits, advances, or non-fund-based business; and all NBFCs in the upper and middle layers under the Scale Based Regulation of October 2022. The scope explicitly includes daily reconciliation of inter-office accounts, nostro accounts, and suspense accounts.",
          "article": "Concurrent Audit of Reconciliation: Daily Verification for Banks and NBFCs",
          "url": "https://www.terra-insight.com/insights/concurrent-audit-reconciliation-india"
        },
        {
          "q": "What reconciliation items does a concurrent auditor verify daily?",
          "a": "The daily checklist includes: clearing and settlement account balances, ATM cash-vault reconciliation, suspense account aging (items over 7 days flagged), NACH return file matching against the previous day's batch, UPI and IMPS settlement reconciliation with NPCI reports, and nostro balance verification against SWIFT MT940 statements. For NBFCs, the scope adds EMI collection reconciliation against NACH presentation and daily loan disbursement matching against bank debits.",
          "article": "Concurrent Audit of Reconciliation: Daily Verification for Banks and NBFCs",
          "url": "https://www.terra-insight.com/insights/concurrent-audit-reconciliation-india"
        },
        {
          "q": "What is the escalation threshold for unreconciled items in concurrent audit?",
          "a": "RBI guidance requires that items in inter-branch and suspense accounts older than 6 months be reported to the audit committee, with a provisioning requirement of 100% for items older than 1 year under Income Recognition and Asset Classification (IRAC) norms. Concurrent auditors typically flag items aged beyond 30 days in the daily report and escalate items aged beyond 90 days to the branch head and the zonal inspecting official.",
          "article": "Concurrent Audit of Reconciliation: Daily Verification for Banks and NBFCs",
          "url": "https://www.terra-insight.com/insights/concurrent-audit-reconciliation-india"
        },
        {
          "q": "How does concurrent audit of NACH reconciliation work at an NBFC?",
          "a": "For an NBFC running 50,000 to 200,000 monthly NACH debit presentations, the concurrent auditor verifies each day's return file (received T+1 to T+2 from NPCI) against the previous day's presentation file. Return codes are classified: Code 01 (funds insufficient) triggers retry logic, Code 25 (mandate cancelled) triggers collections escalation, Code 20 (account closed) triggers NPA risk review. Items not matching within the UMRN-based reconciliation are investigated within 48 hours.",
          "article": "Concurrent Audit of Reconciliation: Daily Verification for Banks and NBFCs",
          "url": "https://www.terra-insight.com/insights/concurrent-audit-reconciliation-india"
        },
        {
          "q": "How is concurrent audit different from internal audit for reconciliation purposes?",
          "a": "Internal audit is periodic (quarterly or annual) and tests samples. Concurrent audit is daily and covers 100% of high-risk transactions — it is a continuous, real-time verification rather than a sampled one. Internal audit reports to the Audit Committee; concurrent audit reports to branch and zonal management with monthly summaries to the Audit Committee. Both are mandated separately — concurrent audit does not replace the Section 138 internal audit obligation.",
          "article": "Concurrent Audit of Reconciliation: Daily Verification for Banks and NBFCs",
          "url": "https://www.terra-insight.com/insights/concurrent-audit-reconciliation-india"
        },
        {
          "q": "Which companies are required to report on ICFR under Section 143(3)(i)?",
          "a": "Section 143(3)(i) of the Companies Act, 2013 read with Rule 11(g) of the Companies (Audit and Auditors) Rules, 2014 requires ICFR reporting for: all listed companies; all unlisted public companies with paid-up share capital of ₹50 crore or more, or turnover of ₹200 crore or more, or outstanding loans of ₹100 crore or more; and all private companies with turnover of ₹200 crore or more or outstanding loans of ₹100 crore or more. One-person companies and small companies are exempt.",
          "article": "ICFR and Reconciliation Controls: Design, Testing, and Reporting Under Section 143(3)(i)",
          "url": "https://www.terra-insight.com/insights/icfr-internal-financial-controls-reconciliation-india"
        },
        {
          "q": "What is a material weakness in the context of reconciliation controls?",
          "a": "Under the ICAI Guidance Note on Audit of Internal Financial Controls, a material weakness is a deficiency, or combination of deficiencies, in internal financial controls such that there is a reasonable possibility that a material misstatement of the company's annual or interim financial statements will not be prevented or detected on a timely basis. Persistent unreconciled bank items older than 90 days, or GST ITC reconciliation gaps above ₹10 lakh, are the two most commonly cited reconciliation-related material weaknesses in audit reports since 2023.",
          "article": "ICFR and Reconciliation Controls: Design, Testing, and Reporting Under Section 143(3)(i)",
          "url": "https://www.terra-insight.com/insights/icfr-internal-financial-controls-reconciliation-india"
        },
        {
          "q": "How does the statutory auditor test the operating effectiveness of reconciliation controls?",
          "a": "The auditor applies a dual-purpose test under SA 330 (Auditor's Responses to Assessed Risks): substantive procedures combined with tests of control operating effectiveness. For bank reconciliation, this typically means selecting 25 to 60 reconciliations from the period, verifying that each was prepared, reviewed, and signed off by the designated personnel within the policy timeline (usually within 15 days of month-end), and that exceptions were resolved within the aging threshold. A failure rate above 10% indicates the control is not operating effectively.",
          "article": "ICFR and Reconciliation Controls: Design, Testing, and Reporting Under Section 143(3)(i)",
          "url": "https://www.terra-insight.com/insights/icfr-internal-financial-controls-reconciliation-india"
        },
        {
          "q": "What is the ICAI Guidance Note on Audit of Internal Financial Controls?",
          "a": "The ICAI Guidance Note, first issued in 2015 and revised multiple times since, provides the authoritative framework for ICFR audit in India. It maps the COSO Internal Control — Integrated Framework (2013) to Indian requirements, defines the five components (Control Environment, Risk Assessment, Control Activities, Information and Communication, Monitoring), and prescribes testing approaches for entity-level and process-level controls. Reconciliation is a process-level control under the Control Activities component.",
          "article": "ICFR and Reconciliation Controls: Design, Testing, and Reporting Under Section 143(3)(i)",
          "url": "https://www.terra-insight.com/insights/icfr-internal-financial-controls-reconciliation-india"
        },
        {
          "q": "What are the consequences of an adverse opinion on ICFR?",
          "a": "An adverse opinion on ICFR must be disclosed in the Board's Report under Section 134 and in the audit report under Section 143. It is also reported in the MCA filings (AOC-4 and MGT-7). Lenders typically treat an adverse ICFR opinion as a breach of financial covenants, triggering a review of credit facilities. For listed companies, SEBI LODR Regulation 33 requires the same disclosure in quarterly financial results, affecting analyst coverage and stock valuation.",
          "article": "ICFR and Reconciliation Controls: Design, Testing, and Reporting Under Section 143(3)(i)",
          "url": "https://www.terra-insight.com/insights/icfr-internal-financial-controls-reconciliation-india"
        },
        {
          "q": "Which companies are required to appoint an internal auditor under the Companies Act?",
          "a": "Section 138 of the Companies Act, 2013 read with Rule 13 of the Companies (Accounts) Rules, 2014 makes internal audit mandatory for: every listed company; every unlisted public company with paid-up share capital of ₹50 crore or more, turnover of ₹200 crore or more, outstanding loans or borrowings of ₹100 crore or more, or outstanding deposits of ₹25 crore or more; and every private company with turnover of ₹200 crore or more or outstanding loans of ₹100 crore or more. Reconciliation testing is a standard scope area in these engagements.",
          "article": "Internal Audit of Reconciliation in India: Testing, Sampling, and Evidence",
          "url": "https://www.terra-insight.com/insights/internal-audit-reconciliation-india"
        },
        {
          "q": "What sample size should an internal auditor use for bank reconciliation testing?",
          "a": "SA 530 on Audit Sampling does not prescribe a fixed sample size. For bank reconciliation testing, internal auditors typically select 15 to 25 items per account for a quarterly review using monetary unit sampling for high-value items and random sampling for the residual population. For accounts with more than 2,000 monthly transactions, stratified sampling with a 95% confidence level and 5% tolerable error rate is the default benchmark documented in the ICAI Technical Guide on Internal Audit.",
          "article": "Internal Audit of Reconciliation in India: Testing, Sampling, and Evidence",
          "url": "https://www.terra-insight.com/insights/internal-audit-reconciliation-india"
        },
        {
          "q": "What counts as sufficient audit evidence for reconciliation under the SIA framework?",
          "a": "Under SIA 330 on Internal Audit Documentation and SIA 350 on Review and Supervision, sufficient evidence includes: the source records (bank statement, Form 26AS, GSTR-2B), the reconciliation worksheet with matching logic, exception logs with aging analysis, management responses to variances, and evidence of follow-through on prior-period observations. Spreadsheet-based reconciliations without version history typically fail the sufficiency test during peer review.",
          "article": "Internal Audit of Reconciliation in India: Testing, Sampling, and Evidence",
          "url": "https://www.terra-insight.com/insights/internal-audit-reconciliation-india"
        },
        {
          "q": "How does internal audit testing of reconciliation feed into ICFR reporting?",
          "a": "Internal audit findings on reconciliation control failures are a direct input to the ICFR assessment under Section 143(3)(i) of the Companies Act. A reconciliation control that fails operating effectiveness testing during internal audit — for example, more than 5% of samples showing unresolved items older than 90 days — must be reported as a deficiency. If the deficiency is material, the statutory auditor issues a qualified opinion on internal financial controls.",
          "article": "Internal Audit of Reconciliation in India: Testing, Sampling, and Evidence",
          "url": "https://www.terra-insight.com/insights/internal-audit-reconciliation-india"
        },
        {
          "q": "What is the typical timeline for an internal audit reconciliation review at a mid-size Indian company?",
          "a": "For a company with 4 to 6 bank accounts, 150 to 250 active party ledgers, and quarterly statutory returns, a focused reconciliation review typically takes 8 to 12 audit days per quarter. This covers scope definition, sample selection, walkthrough of matching procedures, variance testing, and reporting. Annual cycles run 35 to 50 days depending on whether ICFR operating effectiveness testing is included in the scope.",
          "article": "Internal Audit of Reconciliation in India: Testing, Sampling, and Evidence",
          "url": "https://www.terra-insight.com/insights/internal-audit-reconciliation-india"
        },
        {
          "q": "Which Indian subsidiaries are in scope for SOX compliance testing?",
          "a": "A US-listed parent (NYSE, Nasdaq, or OTC with SEC registration) must certify internal controls under Sarbanes-Oxley Section 404. Subsidiaries are in scope if they contribute a material portion to consolidated financial statements — typically above 5% of revenue, 5% of total assets, or any other quantitative or qualitative materiality indicator defined by the group auditor. Indian IT services subsidiaries of US parents, captive finance arms of US banks, and Indian manufacturing arms of US industrials are the most common in-scope populations.",
          "article": "SOX Compliance Reconciliation: What Indian Subsidiaries of US-Listed Parents Must Prove",
          "url": "https://www.terra-insight.com/insights/sox-compliance-reconciliation-india"
        },
        {
          "q": "How does SOX 404 testing differ from ICFR testing under Section 143(3)(i)?",
          "a": "Both frameworks derive from the COSO 2013 Internal Control — Integrated Framework, so the control taxonomy is similar. Differences: SOX testing is performed by a PCAOB-registered auditor under AS 2201 (An Audit of Internal Control Over Financial Reporting); ICFR is performed by an ICAI-registered auditor under SA 610 and the ICAI Guidance Note. SOX requires quarterly sub-certifications by management (CEO/CFO); ICFR requires only an annual opinion. SOX materiality is set at the consolidated group level; ICFR at the individual company level.",
          "article": "SOX Compliance Reconciliation: What Indian Subsidiaries of US-Listed Parents Must Prove",
          "url": "https://www.terra-insight.com/insights/sox-compliance-reconciliation-india"
        },
        {
          "q": "What reconciliation controls are tested under SOX at a typical Indian subsidiary?",
          "a": "The standard scope includes: bank reconciliation for all operating bank accounts (monthly, within 15 days of close), intercompany balance reconciliation with the US parent and other group entities, revenue cut-off reconciliation, GST ITC reconciliation with GSTR-2B, TDS reconciliation with Form 26AS, payroll reconciliation (gross-to-net), and journal entry completeness testing. For IT services subsidiaries, unbilled revenue to invoice conversion is added. For manufacturing subsidiaries, inventory to GL reconciliation is a high-risk scope item.",
          "article": "SOX Compliance Reconciliation: What Indian Subsidiaries of US-Listed Parents Must Prove",
          "url": "https://www.terra-insight.com/insights/sox-compliance-reconciliation-india"
        },
        {
          "q": "What is a SOX Key Control and how is it identified?",
          "a": "A Key Control is one that directly addresses a specific financial reporting risk at the assertion level (existence, completeness, accuracy, valuation, rights/obligations, presentation). The external auditor selects 30 to 80 key controls at a typical Indian subsidiary based on a risk assessment. For reconciliation, the monthly bank reconciliation review, the quarterly GSTR-2B to ITC reconciliation sign-off, and the intercompany balance confirmation are nearly always key controls — each is tested for both design and operating effectiveness.",
          "article": "SOX Compliance Reconciliation: What Indian Subsidiaries of US-Listed Parents Must Prove",
          "url": "https://www.terra-insight.com/insights/sox-compliance-reconciliation-india"
        },
        {
          "q": "What happens if a SOX key control fails at an Indian subsidiary?",
          "a": "A failed key control is classified by severity: control deficiency (minor), significant deficiency (meaningful), or material weakness (severe). A material weakness must be disclosed in the parent's 10-K filing and the CEO/CFO certification under Sections 302 and 404. Under SEC enforcement precedents, a material weakness disclosure typically triggers a share price decline of 1 to 5% on announcement, increased auditor fees of 15 to 30%, and remediation plans reviewed by the Audit Committee each quarter until closed.",
          "article": "SOX Compliance Reconciliation: What Indian Subsidiaries of US-Listed Parents Must Prove",
          "url": "https://www.terra-insight.com/insights/sox-compliance-reconciliation-india"
        },
        {
          "q": "What is the statutory auditor's materiality threshold for reconciliation items?",
          "a": "Under SA 320 (Materiality in Planning and Performing an Audit), materiality is determined by the auditor based on the company's financial position. The common benchmark for a profit-making company is 5% of profit before tax or 0.5% of revenue, whichever is lower. For reconciliation items, performance materiality (typically 50% to 75% of overall materiality) applies. An individual unreconciled item above this level or an aggregate of similar items triggers a separate disclosure in the audit report.",
          "article": "Statutory Audit Reconciliation Checklist: Bank, Party, TDS, and GST Items",
          "url": "https://www.terra-insight.com/insights/statutory-audit-reconciliation-checklist-india"
        },
        {
          "q": "What does the auditor do during bank balance confirmation under SA 505?",
          "a": "Under SA 505 (External Confirmations) revised in 2016, the auditor sends a confirmation request directly to each bank holding the company's accounts. For companies on the Digital Bank Confirmation Portal (launched July 2025 by Indian Banks' Association with ICAI), the response is received digitally signed within 7 to 10 days. For banks not on the portal, manual confirmations take 3 to 6 weeks. Non-response by the balance sheet date typically triggers modified procedures — cut-off testing, alternative confirmation routes, or a modified opinion in severe cases.",
          "article": "Statutory Audit Reconciliation Checklist: Bank, Party, TDS, and GST Items",
          "url": "https://www.terra-insight.com/insights/statutory-audit-reconciliation-checklist-india"
        },
        {
          "q": "How does the auditor verify TDS receivable during statutory audit?",
          "a": "The auditor obtains Form 26AS for the financial year from the TRACES portal, downloads the TDS receivable ledger, and performs a three-way reconciliation: book amount vs Form 26AS vs TDS certificates (Form 16A). Variances above performance materiality are investigated. Unclaimed TDS — where the deduction appears in Form 26AS but is not booked — is reviewed for revenue recognition impact. Writebacks — where TDS is booked but does not appear in 26AS after 2 quarters — are evaluated for provision adequacy.",
          "article": "Statutory Audit Reconciliation Checklist: Bank, Party, TDS, and GST Items",
          "url": "https://www.terra-insight.com/insights/statutory-audit-reconciliation-checklist-india"
        },
        {
          "q": "What GST-related reconciliation does the auditor check?",
          "a": "The standard scope covers four items. First, GSTR-3B to GSTR-1 reconciliation (outward supply match). Second, GSTR-2B to ITC claimed reconciliation (input tax credit match). Third, GSTR-9 to books reconciliation (annual return match). Fourth, Rule 42/43 proportional reversal calculation for taxpayers with both taxable and exempt supplies. Unreconciled items trigger notes to accounts and, if material, qualifications. Section 73/74 demand notices received during the year are reviewed for provisioning adequacy.",
          "article": "Statutory Audit Reconciliation Checklist: Bank, Party, TDS, and GST Items",
          "url": "https://www.terra-insight.com/insights/statutory-audit-reconciliation-checklist-india"
        },
        {
          "q": "What is the typical statutory audit timeline for reconciliation work?",
          "a": "For a ₹500 crore turnover company with 5 to 8 bank accounts, 200 to 400 active party ledgers, and quarterly statutory returns, statutory audit reconciliation work typically takes 12 to 18 audit days. This is compressed into the March-to-September window (post year-end close, before AGM filing deadline of 30 September for most companies). Companies with pre-prepared reconciliation packs and audit trails often reduce this to 7 to 10 days, which reduces the audit fee and improves the relationship with the audit firm.",
          "article": "Statutory Audit Reconciliation Checklist: Bank, Party, TDS, and GST Items",
          "url": "https://www.terra-insight.com/insights/statutory-audit-reconciliation-checklist-india"
        },
        {
          "q": "Which entities are required to get a tax audit under Section 44AB?",
          "a": "Section 44AB of the Income Tax Act, 1961 applies to: every business with total sales, turnover, or gross receipts above ₹1 crore in the previous year (₹10 crore if cash receipts and cash payments are each less than 5% of aggregate); every profession with gross receipts above ₹75 lakh (increased from ₹50 lakh with effect from AY 2024-25); and every presumptive taxpayer (Section 44AD, 44ADA, 44AE) declaring income below the presumptive rate. The tax audit report must be uploaded on the e-filing portal at least one month before the income tax return filing due date.",
          "article": "Tax Audit Form 3CD: Reconciliation Items the Auditor Verifies Under Section 44AB",
          "url": "https://www.terra-insight.com/insights/tax-audit-3cd-reconciliation-india"
        },
        {
          "q": "What is the penalty for non-filing of tax audit report under Section 271B?",
          "a": "Under Section 271B of the Income Tax Act, 1961, failure to get accounts audited or furnish the audit report by the due date attracts a penalty of 0.5% of turnover or gross receipts, subject to a maximum of ₹1,50,000. The penalty can be waived under Section 273B if the taxpayer proves reasonable cause. Late filing also results in loss of deduction under Chapter VI-A for certain items and disallowance of carried-forward losses under Section 80 if the return itself is late.",
          "article": "Tax Audit Form 3CD: Reconciliation Items the Auditor Verifies Under Section 44AB",
          "url": "https://www.terra-insight.com/insights/tax-audit-3cd-reconciliation-india"
        },
        {
          "q": "What reconciliation does Form 3CD Clause 34 require for TDS?",
          "a": "Clause 34(a) requires the auditor to report whether the assessee was required to deduct or collect TDS/TCS and whether it was deducted at the correct rate and deposited on time. Clause 34(b) requires disclosure of transactions where TDS was not deducted at source or was deducted at a lower rate, with the relevant section and amount. Clause 34(c) reconciles TDS payable per books with challans deposited per Form 26AS. Under the new Form 26, Clauses 49 to 51 replace these with enhanced counts and monetary amounts of unreported transactions.",
          "article": "Tax Audit Form 3CD: Reconciliation Items the Auditor Verifies Under Section 44AB",
          "url": "https://www.terra-insight.com/insights/tax-audit-3cd-reconciliation-india"
        },
        {
          "q": "What does Form 3CD Clause 26 require for Section 43B items?",
          "a": "Clause 26 requires disclosure of sums referred to in Section 43B — statutory dues (GST, PF, ESI, professional tax), interest on loans from banks and public financial institutions, and from April 2024, payments to MSMEs beyond the 45-day limit under Section 43B(h). The auditor verifies: amounts payable at the end of the year, amounts actually paid before the due date of filing the return, and amounts disallowed in the computation of business income because they were not paid within the time prescribed. Unreconciled statutory liability balances are the most common Clause 26 observation.",
          "article": "Tax Audit Form 3CD: Reconciliation Items the Auditor Verifies Under Section 44AB",
          "url": "https://www.terra-insight.com/insights/tax-audit-3cd-reconciliation-india"
        },
        {
          "q": "How does Form 3CD transition to Form 26 under the new Income Tax Act 2025?",
          "a": "The new Income Tax Act 2025 replaces Form 3CD with Form 26. The Ministry of Finance notified the transition with a phased rollout: first full year of Form 26 is FY 2025-26 (AY 2026-27), with reporting due by 30 September 2026 for most taxpayers. Key changes in Form 26: Clauses 49 to 51 require exact counts and monetary amounts of unreported TDS and TCS transactions, Clause 52 adds related-party loan reconciliation with AIS cross-reference, and Clause 55 introduces digital audit trail attestation for taxpayers above ₹50 crore turnover.",
          "article": "Tax Audit Form 3CD: Reconciliation Items the Auditor Verifies Under Section 44AB",
          "url": "https://www.terra-insight.com/insights/tax-audit-3cd-reconciliation-india"
        }
      ]
    },
    "tds-core": {
      "label": "TDS 2026 Migration and Core TDS",
      "faqs": [
        {
          "q": "What is cross-era TDS reconciliation?",
          "a": "Cross-era TDS reconciliation is the process of matching TDS receivable and TDS payable records that span both the Income Tax Act 1961 and the Income Tax Act 2025 classification systems. From April 1, 2026 until the FY 2025-26 correction window closes on March 31, 2029, the same reconciliation run will need to handle transactions with old section codes (194C, 194J, 194I, and others) alongside transactions with new payment codes in the 1001 to 1092 range. Cross-era matching treats the equivalent pairs, for example Section 194J and payment code 1003 under Section 393, as referring to the same transaction type.",
          "article": "Cross-Era TDS Reconciliation: Matching Old Section Codes to New Payment Codes",
          "url": "https://www.terra-insight.com/insights/cross-era-tds-reconciliation-india"
        },
        {
          "q": "How long does the cross-era transition period last?",
          "a": "Under current TDS correction rules, a deductor can revise TDS returns for up to six years from the end of the relevant financial year. This means corrections to FY 2025-26 returns can be filed until March 31, 2029, with the revised statements retaining old section codes because they refer to transactions under the 1961 Act. Practically, finance teams should plan for cross-era reconciliation capability through at least FY 2028-29, covering Q4 FY 2025-26 credits that surface late, client correction statements that update old-code entries in Form 168, and Form 16A reissues for FY 2025-26.",
          "article": "Cross-Era TDS Reconciliation: Matching Old Section Codes to New Payment Codes",
          "url": "https://www.terra-insight.com/insights/cross-era-tds-reconciliation-india"
        },
        {
          "q": "What happens when a client issues a March 2026 Form 16A in May 2026?",
          "a": "Form 16A certificates for Q4 FY 2025-26 (January to March 2026 deductions) are due from the deductor by 15 June 2026. When that certificate arrives in May or June, it carries Section 194J or Section 194C in the section field because the underlying deduction occurred under the 1961 Act. Your TDS receivable ledger must book the credit against the original March invoice under the old section code, even though newer invoices in your ledger carry new payment codes. The reconciliation engine must treat both identifiers as matchable to the same vendor's receivable account.",
          "article": "Cross-Era TDS Reconciliation: Matching Old Section Codes to New Payment Codes",
          "url": "https://www.terra-insight.com/insights/cross-era-tds-reconciliation-india"
        },
        {
          "q": "Will Form 168 show old section codes for FY 2025-26 entries?",
          "a": "Yes. Form 168, which replaces Form 26AS from April 1, 2026, will carry historical entries in their original classification. A deduction made in February 2026 and reported in the Q4 FY 2025-26 return will appear in Form 168 under Section 194C or 194J (or whichever old section applied), even though the deductee downloads Form 168 in June 2026. Entries for deductions from April 1, 2026 onwards will appear under the new payment codes. A single Form 168 download for a mid-size company will routinely show both code systems for at least two financial years.",
          "article": "Cross-Era TDS Reconciliation: Matching Old Section Codes to New Payment Codes",
          "url": "https://www.terra-insight.com/insights/cross-era-tds-reconciliation-india"
        },
        {
          "q": "How do TDS correction returns work during the cross-era period?",
          "a": "Correction returns for FY 2025-26 and earlier years continue to use old section codes because the original return and the underlying deductions fall under the 1961 Act. A revision to a Q2 FY 2025-26 return filed in September 2027 will still reference Section 194J or 194C in the corrected entries. Correction returns for FY 2026-27 onwards use new payment codes. Finance teams preparing corrections during the transition must select the correct era by financial year, not by the calendar date the correction is being filed.",
          "article": "Cross-Era TDS Reconciliation: Matching Old Section Codes to New Payment Codes",
          "url": "https://www.terra-insight.com/insights/cross-era-tds-reconciliation-india"
        },
        {
          "q": "When is Form 131 issued during the Tax Year?",
          "a": "Form 131 is issued quarterly by every deductor, following the same cadence as Form 16A. For non-salary deductions under Chapter XX, the certificate must be issued within 15 days of the due date for filing the quarterly TDS return. For Q1 (April-June) the return is due by July 31 and the certificate by August 15. For Q4 (January-March) the return is due by May 31 and the certificate by June 15.",
          "article": "Form 131 TDS Certificate: The Quarterly Deductor Certificate Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-131-tds-certificate-india"
        },
        {
          "q": "What is the penalty for not issuing Form 131 on time?",
          "a": "Late issuance or non-issuance of Form 131 attracts a penalty of ₹100 per day per certificate under the continuing default provisions of the Income Tax Act 2025, capped at the total TDS amount for the period. A deductor issuing 500 certificates that are 10 days late carries ₹5 lakh penalty exposure. The deductee can also escalate to the Assessing Officer if certificates are withheld beyond the due date.",
          "article": "Form 131 TDS Certificate: The Quarterly Deductor Certificate Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-131-tds-certificate-india"
        },
        {
          "q": "How does Form 131 differ from Form 16A?",
          "a": "Form 131 carries the new payment code (1001 to 1092) in place of the legacy section code (194C, 194J, etc.). It labels the period as Tax Year rather than Assessment Year. It introduces an enriched metadata block that includes the deductor's TAN, the PAN of the deductee, invoice or payment reference numbers where applicable, and the Form 168 reference line. The overall purpose — certifying TDS deducted and deposited — is unchanged.",
          "article": "Form 131 TDS Certificate: The Quarterly Deductor Certificate Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-131-tds-certificate-india"
        },
        {
          "q": "Can the deductee use Form 131 alone to claim a tax credit?",
          "a": "No. The credit claim is validated against Form 168, not against Form 131. Form 131 serves as the deductor-issued certificate that supports the deductee's reconciliation — if a credit appears on Form 131 but not on Form 168, the deductee must escalate to the deductor for a correction statement. The income tax return credit schedule must match Form 168 entries, not Form 131 entries alone.",
          "article": "Form 131 TDS Certificate: The Quarterly Deductor Certificate Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-131-tds-certificate-india"
        },
        {
          "q": "Is Form 131 accepted as proof during a statutory audit?",
          "a": "Form 131 is one of the primary supporting documents for TDS receivable balances during statutory audit under CARO 2020. Auditors typically require both Form 131 (deductor-issued) and Form 168 (government-issued) for every material TDS receivable. A mismatch between the two is a flagged exception that must be either resolved before sign-off or disclosed as an unreconciled item in the audit working papers.",
          "article": "Form 131 TDS Certificate: The Quarterly Deductor Certificate Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-131-tds-certificate-india"
        },
        {
          "q": "What forms does Form 141 replace?",
          "a": "Form 141 consolidates four legacy forms from April 1, 2026: Form 26QB (TDS on sale of immovable property under Section 194-IA), Form 26QC (TDS on rent exceeding ₹50,000 per month under Section 194-IB), Form 26QD (TDS on specified contractor and professional payments by individuals or HUFs under Section 194M), and Form 26QE (TDS on transfer of virtual digital assets under Section 194S). All four scenarios now file through a single challan-cum-statement.",
          "article": "Form 141 Challan-cum-Statement: The Unified Filing for Property, Rent, Contractor, and Crypto TDS",
          "url": "https://www.terra-insight.com/insights/form-141-unified-challan-statement-india"
        },
        {
          "q": "What is the due date for filing Form 141?",
          "a": "Form 141 retains the 30-day filing window of the legacy forms. It must be filed within 30 days from the end of the month in which the deduction was made. For a property purchase transaction where the payment was made on May 10, 2026, Form 141 must be filed by June 30, 2026. Late filing attracts a fee of ₹200 per day under Section 234E, capped at the TDS amount.",
          "article": "Form 141 Challan-cum-Statement: The Unified Filing for Property, Rent, Contractor, and Crypto TDS",
          "url": "https://www.terra-insight.com/insights/form-141-unified-challan-statement-india"
        },
        {
          "q": "Does Form 141 require a TAN?",
          "a": "No. Like the forms it replaces, Form 141 is designed for transactions where the deductor is typically an individual or HUF who does not hold a Tax Deduction Account Number. The PAN of the deductor is used as the identifier, and the PAN of the deductee is required. This allows property buyers, tenants, and small specified payers to meet their TDS obligation without registering for a TAN.",
          "article": "Form 141 Challan-cum-Statement: The Unified Filing for Property, Rent, Contractor, and Crypto TDS",
          "url": "https://www.terra-insight.com/insights/form-141-unified-challan-statement-india"
        },
        {
          "q": "Can one Form 141 cover multiple transactions?",
          "a": "Form 141 is filed one filing per transaction per deductee for property and virtual digital asset scenarios, mirroring the Forms 26QB and 26QE rule. For recurring rent under Section 194-IB, the legacy one-time annual filing cadence is retained — a single Form 141 covers the full tenancy year. For Section 194M specified contractor payments, the 30-day-per-payment filing rule applies as it did under Form 26QD.",
          "article": "Form 141 Challan-cum-Statement: The Unified Filing for Property, Rent, Contractor, and Crypto TDS",
          "url": "https://www.terra-insight.com/insights/form-141-unified-challan-statement-india"
        },
        {
          "q": "What is the TDS certificate issued against a Form 141 filing?",
          "a": "Each Form 141 filing generates a corresponding certificate — Form 131A for property, Form 131B for rent, Form 131C for specified contractor payments, and Form 131D for virtual digital assets. These sub-variants of Form 131 carry the payment code, transaction reference, and deductee PAN, and are downloadable from the e-filing portal after the Form 141 is processed. The deductor must issue the certificate to the deductee within 15 days of the Form 141 filing.",
          "article": "Form 141 Challan-cum-Statement: The Unified Filing for Property, Rent, Contractor, and Crypto TDS",
          "url": "https://www.terra-insight.com/insights/form-141-unified-challan-statement-india"
        },
        {
          "q": "When does Form 168 replace Form 26AS?",
          "a": "Form 168 takes effect from April 1, 2026, applying to Tax Year 2025-26 onwards. Transactions deducted from that date will appear in Form 168, not Form 26AS. Historical Form 26AS data for FY 2025-26 and earlier will remain accessible on the e-filing portal, but new tax year credits will only be reflected on the Form 168 statement.",
          "article": "Form 168 TDS Statement: The New Unified Annual Statement Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-168-new-tds-statement-india"
        },
        {
          "q": "What is the main difference between Form 168 and Form 26AS?",
          "a": "Form 168 is a single unified annual statement that consolidates tax credit data previously split between Form 26AS and the Annual Information Statement. It includes TDS, TCS, advance tax, self-assessment tax, refunds, and high-value financial transactions in one document keyed to PAN. Form 26AS remained structured in Parts A through F with AIS as a separate statement; Form 168 merges the two into one statement with a unified schema.",
          "article": "Form 168 TDS Statement: The New Unified Annual Statement Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-168-new-tds-statement-india"
        },
        {
          "q": "Does Form 168 include the new payment code from the Income Tax Act 2025?",
          "a": "Yes. Every entry in Form 168 carries a payment code (1001 through 1092 range) that identifies the nature of the payment under Chapter XX of the Income Tax Act 2025. This replaces the legacy section code field (194C, 194J, etc.) used in Form 26AS. For reconciliation, finance teams must map each payment code back to the equivalent legacy section during the cross-over year.",
          "article": "Form 168 TDS Statement: The New Unified Annual Statement Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-168-new-tds-statement-india"
        },
        {
          "q": "How often is Form 168 updated?",
          "a": "Form 168 is updated within 3 to 7 working days after a TDS challan is processed by the authorised bank and flows through the Tax Information Network. Quarterly return data — which adds deductee-level PAN and payment code details — appears within 7 to 10 working days after the return is processed by the TDS CPC. Tax Year 2025-26 March quarter data typically stabilises in late May or early June.",
          "article": "Form 168 TDS Statement: The New Unified Annual Statement Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-168-new-tds-statement-india"
        },
        {
          "q": "Can Form 168 be used for ITR filing credit claims?",
          "a": "Yes. From Tax Year 2025-26, the Income Tax Department will match ITR TDS and TCS credit claims against Form 168 entries. Any credit claimed in the return that does not appear in Form 168 will be flagged and can trigger a demand notice. The credit must also match on PAN, payment code, Tax Year, and amount — not just on total aggregate.",
          "article": "Form 168 TDS Statement: The New Unified Annual Statement Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/form-168-new-tds-statement-india"
        },
        {
          "q": "How does Tax Year map to Assessment Year?",
          "a": "Tax Year refers to the period in which income is earned, matching what was previously called Financial Year. Assessment Year was the following year — the year in which that income was assessed. Under the Income Tax Act 2025, the two-label system ends. FY 2025-26 (April 1, 2025 to March 31, 2026) becomes Tax Year 2025-26. What would have been AY 2026-27 under the 1961 Act is simply Tax Year 2025-26 under the new act.",
          "article": "Tax Year vs Assessment Year in India: The Terminology Change Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tax-year-vs-assessment-year-india"
        },
        {
          "q": "Does the Tax Year start on April 1 like the Financial Year?",
          "a": "Yes. The Tax Year under the Income Tax Act 2025 runs from April 1 to March 31, matching the existing Financial Year. There is no change in the fiscal calendar. Tax Year 2025-26 means the period from April 1, 2025 to March 31, 2026. The change is purely terminological — one label replaces the two labels used in the 1961 Act.",
          "article": "Tax Year vs Assessment Year in India: The Terminology Change Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tax-year-vs-assessment-year-india"
        },
        {
          "q": "Which forms reference Tax Year instead of Assessment Year?",
          "a": "All new forms under the Income Tax Act 2025 reference Tax Year. This includes Form 168 (replacing Form 26AS), Form 131 (replacing Form 16A), Form 141 (the unified challan-cum-statement), and the updated ITR forms from Tax Year 2025-26 onwards. Historical filings and Form 26AS downloads for periods up to FY 2025-26 retain the Assessment Year label.",
          "article": "Tax Year vs Assessment Year in India: The Terminology Change Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tax-year-vs-assessment-year-india"
        },
        {
          "q": "How do we handle Assessment Year references in historical reconciliation data?",
          "a": "Finance systems should maintain a dual-label view during the cross-over period. A TDS receivable booked against AY 2025-26 (FY 2024-25) must be reconcilable against a Form 26AS labelled for that Assessment Year, while new bookings for FY 2026-27 must be reconcilable against Form 168 labelled as Tax Year 2026-27. A translation table that converts AY to the corresponding Tax Year prevents mismatches in cross-period trend reports and audit working papers.",
          "article": "Tax Year vs Assessment Year in India: The Terminology Change Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tax-year-vs-assessment-year-india"
        },
        {
          "q": "Does the terminology change impact income tax return filing?",
          "a": "Yes. From Tax Year 2025-26 onwards, the ITR forms drop the Assessment Year field and use Tax Year. A taxpayer filing the return for income earned in FY 2025-26 (what would previously have been AY 2026-27) now selects Tax Year 2025-26 on the portal. The filing due dates remain unchanged — July 31 for non-audit cases and October 31 for audit cases, assuming no deadline extensions.",
          "article": "Tax Year vs Assessment Year in India: The Terminology Change Under the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tax-year-vs-assessment-year-india"
        },
        {
          "q": "When must the TDS 2026 migration be completed?",
          "a": "All critical migration steps must be completed before the first payroll cycle and the first vendor payment cycle of April 2026. The hard deadline is the April 7, 2026 challan deposit due date for March TDS deductions, which will be the final challan window using old section codes for most companies. April payroll TDS and the first post-April-1 vendor payment must deposit under new payment codes, so ERP master data, GL codes, challan interface configuration, and TRACES integration must all be ready by March 31, 2026. Reconciliation configuration should be tested on dummy data at least one week before go-live.",
          "article": "TDS 2026 Migration Checklist: What Indian Finance Teams Must Do Before April 1",
          "url": "https://www.terra-insight.com/insights/tds-2026-migration-checklist-india"
        },
        {
          "q": "Do I need to close all FY 2025-26 correction windows before migration?",
          "a": "Correction windows for FY 2018-19 through FY 2022-23 become time-barred on March 31, 2026 under the six-year correction rule. Any TDS mismatch or incorrect entry in those years must have a correction statement filed by that date. FY 2023-24, FY 2024-25, and FY 2025-26 correction windows remain open beyond April 1, 2026 but must be handled through the legacy classification system. Before the migration, run a full correction audit for FY 2018-19 to FY 2022-23, file statements for any outstanding errors, and confirm TRACES acceptance receipts are received before close of business on March 31, 2026.",
          "article": "TDS 2026 Migration Checklist: What Indian Finance Teams Must Do Before April 1",
          "url": "https://www.terra-insight.com/insights/tds-2026-migration-checklist-india"
        },
        {
          "q": "What happens to 206AB and 206CCA vendor flags in the ERP?",
          "a": "Sections 206AB and 206CCA, which imposed higher TDS and TCS rates on non-filers of income tax returns, are abolished under the Income Tax Act 2025. Any ERP vendor master flag, compliance screening workflow, or monthly non-filer check against the compliance portal should be decommissioned effective April 1, 2026. Before decommissioning, retain a read-only archive of 206AB status history for FY 2025-26 and earlier years, because correction statements for those years, which can be filed until 2029, still require the old higher rate where it applied. The active filter logic, however, can be switched off on April 1.",
          "article": "TDS 2026 Migration Checklist: What Indian Finance Teams Must Do Before April 1",
          "url": "https://www.terra-insight.com/insights/tds-2026-migration-checklist-india"
        },
        {
          "q": "How long does a typical TDS cut-over weekend take?",
          "a": "For a mid-size Indian enterprise with 80 to 200 active vendors and a single-entity structure, a TDS cut-over weekend typically runs 16 to 24 hours of elapsed time across ERP master data updates, GL code additions, reconciliation system configuration, and end-to-end test runs. For group entities with multiple legal entities and shared services, cut-over extends to a full weekend of 40 to 48 hours. The critical path is return preparation utility testing: the updated FVU validator for Q1 FY 2026-27 returns must be installed, tested on a sample file, and confirmed working before the first live challan deposit in April.",
          "article": "TDS 2026 Migration Checklist: What Indian Finance Teams Must Do Before April 1",
          "url": "https://www.terra-insight.com/insights/tds-2026-migration-checklist-india"
        },
        {
          "q": "Is dual-mode reporting legally required or operationally needed?",
          "a": "It is operationally needed, not legally mandated. No provision of the Income Tax Act 2025 requires a deductor to run both legacy and new classifications in parallel. Dual-mode reporting is required because the same finance team in FY 2026-27 is simultaneously responsible for current-period filings under the 2025 Act (new payment codes) and correction statements for FY 2025-26 and earlier under the 1961 Act (old section codes). Reconciliation systems that cannot produce both classifications from a single source of truth will force the team to maintain two parallel sets of records, which creates audit risk and close-of-book delays.",
          "article": "TDS 2026 Migration Checklist: What Indian Finance Teams Must Do Before April 1",
          "url": "https://www.terra-insight.com/insights/tds-2026-migration-checklist-india"
        },
        {
          "q": "What is TDS payment code 1002?",
          "a": "TDS payment code 1002 is the four-digit identifier under Section 393(1)(a) of the Income Tax Act 2025 for tax deducted on payments made to resident contractors and sub-contractors. It applies from April 1, 2026 and replaces the legacy Section 194C reference on challan ITNS 281, Form 26Q quarterly returns, Form 131 deductee certificates, and Form 168 (the new Form 26AS). The code covers civil works, transport contracts, supply contracts, advertising contracts, catering, manpower supply, and most other works-contract relationships with resident parties.",
          "article": "TDS Payment Code 1002 (Section 393(1)(a)): Contractor Payments Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1002-section-393-1-a-contractor"
        },
        {
          "q": "What is the rate and threshold for payment code 1002?",
          "a": "Payment code 1002 carries two rates: 1% if the contractor is an individual or Hindu Undivided Family (HUF), and 2% if the contractor is a company, firm, LLP, AOP, BOI, or any other entity. The threshold is ₹30,000 for any single payment OR ₹1,00,000 in aggregate to the same contractor in a financial year — whichever is breached first triggers deduction on all subsequent payments and retrospectively on the breaching payment. No PAN means deduction at 20% under the standard non-PAN penalty rule.",
          "article": "TDS Payment Code 1002 (Section 393(1)(a)): Contractor Payments Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1002-section-393-1-a-contractor"
        },
        {
          "q": "What did payment code 1002 replace under the 1961 Act?",
          "a": "Payment code 1002 replaces Section 194C of the Income Tax Act 1961. The rate structure (1% / 2%), the per-transaction threshold (₹30,000), and the aggregate threshold (₹1,00,000 per FY) all carry over unchanged. The transport contractor exemption — no TDS if the contractor owns ten or fewer goods carriages and furnishes a declaration with PAN — also carries over. What changes is the identifier on the challan and the return: April 2026 onwards deductions key off 1002, while March 2026 and earlier deductions remain under 194C.",
          "article": "TDS Payment Code 1002 (Section 393(1)(a)): Contractor Payments Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1002-section-393-1-a-contractor"
        },
        {
          "q": "How does code 1002 appear in Form 168 (the new Form 26AS)?",
          "a": "Form 168 lists each contractor TDS credit with the deductor TAN, deductor name, payment code 1002, parent section 393, payment description (Contractor and sub-contractor payments), date of deduction, gross amount paid, tax deducted, status (booked / pending / under processing), and challan CIN. To reconcile contractor receivables, filter Form 168 by payment code 1002 and join against your TDS receivable ledger on deductor TAN plus quarter. Aggregate amounts on Form 168 should reconcile to invoice-level TDS in your accounting system.",
          "article": "TDS Payment Code 1002 (Section 393(1)(a)): Contractor Payments Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1002-section-393-1-a-contractor"
        },
        {
          "q": "What are the most common reconciliation issues for code 1002?",
          "a": "Four issues recur for code 1002. First, rate mismatch — a deductor applied 2% to an individual contractor (should be 1%), or 1% to a partnership firm (should be 2%), which surfaces as an under-deduction or over-deduction on Form 168. Second, threshold miscount — the aggregate ₹1,00,000 was tracked per invoice rather than per financial year. Third, transport contractor declaration not collected, causing TDS to be deducted on payments that qualified for the ten-vehicle exemption. Fourth, classification error — a payment that should sit under code 1003 (professional fees, 10%) was coded as 1002 (contractor, 2%), shorting the deduction.",
          "article": "TDS Payment Code 1002 (Section 393(1)(a)): Contractor Payments Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1002-section-393-1-a-contractor"
        },
        {
          "q": "What is TDS payment code 1003?",
          "a": "TDS payment code 1003 is the four-digit identifier under Section 393(1)(b) of the Income Tax Act 2025 for tax deducted on professional fees, technical service fees, royalties, and non-compete payments made to resident parties. It applies from April 1, 2026 and replaces the legacy Section 194J reference on challan ITNS 281, Form 26Q quarterly returns, Form 131 deductee certificates, and Form 168 (the new Form 26AS). The code covers lawyers, chartered accountants, consultants, doctors, architects, engineers, software service providers, and any other professional or technical service relationship with resident parties.",
          "article": "TDS Payment Code 1003 (Section 393(1)(b)): Professional and Technical Fees Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1003-section-393-1-b-professional-fees"
        },
        {
          "q": "What is the rate and threshold for payment code 1003?",
          "a": "Payment code 1003 carries two distinct rates by service sub-category: 10% for professional services, royalty, and non-compete fees, and 2% for technical services (including software, technical consultancy, and any service in the nature of fees for technical services). The threshold is ₹30,000 per service category per financial year — the ₹30,000 floor applies separately to professional fees and to technical fees from the same deductee. No PAN triggers a 20% non-PAN deduction rate.",
          "article": "TDS Payment Code 1003 (Section 393(1)(b)): Professional and Technical Fees Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1003-section-393-1-b-professional-fees"
        },
        {
          "q": "What did payment code 1003 replace under the 1961 Act?",
          "a": "Payment code 1003 replaces Section 194J of the Income Tax Act 1961. The 10% rate for professional services, the 2% rate for technical services (the 2% rate was introduced via the 2020 Finance Act amendment to 194J), and the ₹30,000 per-category threshold all carry over unchanged. The Income Tax Act 2025 is a renumbering exercise; the substantive rate and threshold structure for professional fees remains identical.",
          "article": "TDS Payment Code 1003 (Section 393(1)(b)): Professional and Technical Fees Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1003-section-393-1-b-professional-fees"
        },
        {
          "q": "How does code 1003 appear in Form 168 (the new Form 26AS)?",
          "a": "Form 168 lists each professional fee TDS credit with the deductor TAN, deductor name, payment code 1003, parent section 393, payment description (Professional and technical services), service sub-type (professional / technical / royalty / non-compete), date of deduction, gross amount paid, tax deducted, status (booked / pending / under processing), and challan CIN. Filter Form 168 by payment code 1003 to see all professional and technical fee credits across deductors. Reconcile by joining on deductor TAN, quarter, and deductee PAN.",
          "article": "TDS Payment Code 1003 (Section 393(1)(b)): Professional and Technical Fees Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1003-section-393-1-b-professional-fees"
        },
        {
          "q": "What are the most common reconciliation issues for code 1003?",
          "a": "Four issues recur for code 1003. First, the 10% versus 2% sub-classification — a software development contract may be technical (2%) but a software licensing fee with knowledge transfer could be royalty (10%). Second, the dual threshold counter — ₹30,000 for professional fees runs separately from ₹30,000 for technical fees, so an ERP that aggregates both into a single threshold counter under-deducts. Third, the boundary between code 1002 (contractor, 2%) and code 1003 (professional, 10%) for service-based payments. Fourth, code 1003 versus code 1062 (Section 413) for cross-border professional services to a non-resident — the latter is governed by treaty rates and Form 15CA/CB.",
          "article": "TDS Payment Code 1003 (Section 393(1)(b)): Professional and Technical Fees Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1003-section-393-1-b-professional-fees"
        },
        {
          "q": "What is TDS payment code 1007?",
          "a": "TDS payment code 1007 is the four-digit identifier under Section 393(1)(f) of the Income Tax Act 2025 for tax deducted on commission or brokerage payments made to resident parties, excluding insurance commission (which has its own code). It applies from April 1, 2026 and replaces the legacy Section 194H reference on challan ITNS 281, Form 26Q quarterly returns, Form 131 deductee certificates, and Form 168 (the new Form 26AS). The code covers sales commission, marketing commission, agency commission, sub-broker brokerage, and platform commissions where the underlying transaction is not e-commerce participant payout (which sits at code 1010 under Section 393(1)(j)).",
          "article": "TDS Payment Code 1007 (Section 393(1)(f)): Commission and Brokerage Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1007-section-393-1-f-commission-brokerage"
        },
        {
          "q": "What is the rate and threshold for payment code 1007?",
          "a": "Payment code 1007 carries a flat 5% rate on the gross commission or brokerage amount. The threshold is ₹15,000 in aggregate per deductee per financial year — the first ₹15,000 of cumulative commission payments to the same recipient in a financial year is exempt, and TDS applies on subsequent payments and retrospectively on the breaching payment. No PAN triggers 20% non-PAN deduction.",
          "article": "TDS Payment Code 1007 (Section 393(1)(f)): Commission and Brokerage Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1007-section-393-1-f-commission-brokerage"
        },
        {
          "q": "What did payment code 1007 replace under the 1961 Act?",
          "a": "Payment code 1007 replaces Section 194H of the Income Tax Act 1961. The 5% rate (it was 10% until 2016, reduced to 5% from June 1, 2016, then briefly at 2% during COVID, restored to 5%) and the ₹15,000 aggregate threshold carry over unchanged into Section 393(1)(f). The exclusion for insurance commission (governed separately) also carries forward. The 2025 Act is a renumbering exercise; the substantive rate and threshold for commission TDS remain identical.",
          "article": "TDS Payment Code 1007 (Section 393(1)(f)): Commission and Brokerage Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1007-section-393-1-f-commission-brokerage"
        },
        {
          "q": "How does code 1007 appear in Form 168 (the new Form 26AS)?",
          "a": "Form 168 lists each commission TDS credit with the deductor TAN, deductor name, payment code 1007, parent section 393, payment description (Commission and brokerage), date of deduction, gross commission amount, tax deducted at 5%, status (booked / pending / under processing), and challan CIN. To reconcile commission receivables for sales agents, distributors, or platform partners, filter Form 168 by payment code 1007 and join against your commission-payable ledger or invoice register.",
          "article": "TDS Payment Code 1007 (Section 393(1)(f)): Commission and Brokerage Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1007-section-393-1-f-commission-brokerage"
        },
        {
          "q": "What are the most common reconciliation issues for code 1007?",
          "a": "Four issues recur for code 1007. First, the boundary between commission (code 1007, 5%) and professional fees (code 1003, 10%) for service-based agents — a distribution agent on commission is 5%, a marketing consultant on retainer is 10%. Second, the threshold lapse — commission is often a small per-transaction amount but rolls up across many small payments to cross ₹15,000 quickly. Third, gross-versus-net commission — TDS applies on gross commission before any chargeback or claw-back adjustment. Fourth, the e-commerce participant overlap (code 1010, 1% under Section 393(1)(j)) — platform commissions paid to sellers as participant payouts go under 1010, not 1007.",
          "article": "TDS Payment Code 1007 (Section 393(1)(f)): Commission and Brokerage Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1007-section-393-1-f-commission-brokerage"
        },
        {
          "q": "What is TDS payment code 1009?",
          "a": "TDS payment code 1009 is the four-digit identifier under Section 393(1)(e) of the Income Tax Act 2025 for tax deducted on rent paid to a resident landlord for land, building (including factory building), or furniture and fittings let along with the building. It applies from April 1, 2026 and replaces the legacy Section 194I(b) reference on challan ITNS 281, Form 26Q quarterly returns, Form 131 deductee certificates, and Form 168 (the new Form 26AS). The code covers office rent, warehouse rent, retail store rent, factory rent, and any other rent on immovable property where the recipient is a resident.",
          "article": "TDS Payment Code 1009 (Section 393(1)(e)): Rent on Land and Building Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1009-section-393-1-e-rent-land-building"
        },
        {
          "q": "What is the rate and threshold for payment code 1009?",
          "a": "Payment code 1009 carries a flat 10% rate on the gross rent paid to a resident landlord for land, building, or furniture let with the building. The threshold is ₹2,40,000 in aggregate per deductee per financial year — equivalent to ₹20,000 per month — below which no TDS applies. No PAN triggers 20% non-PAN deduction. Note: rent on plant and machinery is a separate sub-clause with a 2% rate (formerly 194I(a)).",
          "article": "TDS Payment Code 1009 (Section 393(1)(e)): Rent on Land and Building Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1009-section-393-1-e-rent-land-building"
        },
        {
          "q": "What did payment code 1009 replace under the 1961 Act?",
          "a": "Payment code 1009 replaces Section 194I(b) of the Income Tax Act 1961 — specifically the land-and-building branch of Section 194I. The 10% rate and the ₹2,40,000 annual aggregate threshold carry over unchanged into Section 393(1)(e). The Income Tax Act 2025 is a renumbering exercise; the substantive rate and threshold for rent TDS on immovable property remain identical. The plant-and-machinery branch of 194I sits at a separate payment code with the 2% rate.",
          "article": "TDS Payment Code 1009 (Section 393(1)(e)): Rent on Land and Building Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1009-section-393-1-e-rent-land-building"
        },
        {
          "q": "How does code 1009 appear in Form 168 (the new Form 26AS)?",
          "a": "Form 168 lists each rent TDS credit with the deductor TAN, deductor name, payment code 1009, parent section 393, payment description (Rent on land, building, furniture), date of deduction, gross rent paid, tax deducted at 10%, status (booked / pending / under processing), and challan CIN. For a typical landlord with one tenant, Form 168 will show 12 monthly entries per FY. To reconcile rent receivables, filter Form 168 by payment code 1009 and join against the rent ledger on deductor TAN, deductee PAN, and month-of-deduction.",
          "article": "TDS Payment Code 1009 (Section 393(1)(e)): Rent on Land and Building Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1009-section-393-1-e-rent-land-building"
        },
        {
          "q": "What are the most common reconciliation issues for code 1009?",
          "a": "Four issues recur for code 1009. First, threshold trigger month — the ₹2,40,000 aggregate is annual, so a tenant paying ₹15,000 monthly does not trigger TDS but a tenant paying ₹25,000 monthly triggers from month one. Second, the joint owner split — a property co-owned by two individuals must have rent split for TDS purposes and the per-co-owner threshold checked separately. Third, advance rent and security deposit — security deposit (refundable) is not rent and not subject to code 1009; advance rent (non-refundable) is rent and is. Fourth, GST on rent gross-up — TDS under code 1009 is on gross rent before GST.",
          "article": "TDS Payment Code 1009 (Section 393(1)(e)): Rent on Land and Building Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1009-section-393-1-e-rent-land-building"
        },
        {
          "q": "What is TDS payment code 1010?",
          "a": "TDS payment code 1010 is the four-digit identifier under Section 393(1)(j) of the Income Tax Act 2025 for tax deducted by e-commerce operators on payments to e-commerce participants — the sellers, restaurants, drivers, or service providers who transact through a marketplace platform. It applies from April 1, 2026 and replaces the legacy Section 194O reference on challan ITNS 281, Form 26Q quarterly returns, Form 131 deductee certificates, and Form 168 (the new Form 26AS). The code covers Amazon, Flipkart, Meesho, Myntra, Zomato, Swiggy, Ola, Uber, Urban Company, and any other marketplace that aggregates supply and processes consumer payments to participant sellers.",
          "article": "TDS Payment Code 1010 (Section 393(1)(j)): E-Commerce Participant Payout Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1010-section-393-1-j-ecommerce-participant"
        },
        {
          "q": "What is the rate and threshold for payment code 1010?",
          "a": "Payment code 1010 carries a flat 1% rate on the gross transaction value (the consumer-side order amount inclusive of GST). There is effectively no threshold for business participants — TDS applies on every transaction. For an individual or HUF participant, an exemption applies if gross sales through the platform do not exceed ₹5,00,000 in the financial year AND the participant furnishes PAN/Aadhaar. No PAN triggers the standard 5% non-PAN rate (lower than the usual 20% for participant payouts under the legacy 194O regime, carried into 1010).",
          "article": "TDS Payment Code 1010 (Section 393(1)(j)): E-Commerce Participant Payout Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1010-section-393-1-j-ecommerce-participant"
        },
        {
          "q": "What did payment code 1010 replace under the 1961 Act?",
          "a": "Payment code 1010 replaces Section 194O of the Income Tax Act 1961, which was introduced from October 1, 2020 to bring e-commerce participants into the TDS net. The 1% rate (briefly reduced to 0.1% by the 2024 Finance Act for some participant categories, then standardised), the gross-transaction-value base (including GST), and the individual-participant exemption with the ₹5,00,000 threshold all carry over into Section 393(1)(j). The 2025 Act is a renumbering exercise; the substantive rate, base, and threshold rules remain identical.",
          "article": "TDS Payment Code 1010 (Section 393(1)(j)): E-Commerce Participant Payout Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1010-section-393-1-j-ecommerce-participant"
        },
        {
          "q": "How does code 1010 appear in Form 168 (the new Form 26AS)?",
          "a": "Form 168 lists each e-commerce participant payout TDS credit with the deductor TAN (the marketplace's TAN), deductor name, payment code 1010, parent section 393, payment description (E-commerce participant payouts), date of deduction (typically the date of customer-side transaction settlement), gross transaction value, tax deducted at 1%, status (booked / pending / under processing), and challan CIN. For an active seller on a marketplace, Form 168 will show one line per settlement batch (typically daily or weekly). Volumes for high-velocity sellers can run to thousands of lines per quarter.",
          "article": "TDS Payment Code 1010 (Section 393(1)(j)): E-Commerce Participant Payout Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1010-section-393-1-j-ecommerce-participant"
        },
        {
          "q": "What are the most common reconciliation issues for code 1010?",
          "a": "Four issues recur for code 1010. First, GST-inclusive versus GST-exclusive base — TDS is on gross transaction value including GST, so the seller's TDS receivable will look larger than 1% of taxable sales. Second, returns and refunds — TDS is on the original sale value; refunds and returns do not trigger TDS reversal in the same quarter but may surface in the next quarter's settlement reconciliation. Third, dual TDS exposure — payments may also attract code 1007 (commission) at 5% if the marketplace structure includes a separate commission payout. Fourth, multi-marketplace seller reconciliation — a seller on Amazon, Flipkart, and Meesho gets three TAN-keyed streams in Form 168, all under code 1010, and must reconcile each separately.",
          "article": "TDS Payment Code 1010 (Section 393(1)(j)): E-Commerce Participant Payout Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1010-section-393-1-j-ecommerce-participant"
        },
        {
          "q": "What is TDS payment code 1012?",
          "a": "TDS payment code 1012 is the four-digit identifier under Section 393(1)(k) of the Income Tax Act 2025 for buyer-deducted TDS on purchase of goods from a resident supplier. It applies from April 1, 2026 and replaces the legacy Section 194Q reference on challan ITNS 281, Form 26Q quarterly returns, Form 131 deductee certificates, and Form 168 (the new Form 26AS). The code applies only where the buyer's gross turnover, sales, or receipts in the immediately preceding financial year exceeded ₹10 crore AND the buyer's annual purchases from the same supplier exceed ₹50 lakh.",
          "article": "TDS Payment Code 1012 (Section 393(1)(k)): Purchase of Goods Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1012-section-393-1-k-purchase-goods"
        },
        {
          "q": "What is the rate and threshold for payment code 1012?",
          "a": "Payment code 1012 carries a flat 0.1% rate on the purchase value above ₹50 lakh from the same supplier in a financial year. The compound threshold requires both: (a) the buyer's prior-year turnover above ₹10 crore, and (b) cumulative purchases from a single resident supplier above ₹50 lakh in the current FY. Once both conditions are met, the buyer deducts 0.1% on every rupee of purchase value above ₹50 lakh from that supplier for the rest of the FY. No PAN triggers 5% non-PAN deduction (a softer rate than the usual 20%, specific to legacy 194Q carried into code 1012).",
          "article": "TDS Payment Code 1012 (Section 393(1)(k)): Purchase of Goods Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1012-section-393-1-k-purchase-goods"
        },
        {
          "q": "What did payment code 1012 replace under the 1961 Act?",
          "a": "Payment code 1012 replaces Section 194Q of the Income Tax Act 1961, introduced from July 1, 2021 to bring large-value goods purchases into the TDS net and to complement Section 206C(1H) TCS on sales of goods. The 0.1% rate, the ₹10 crore buyer-turnover trigger, the ₹50 lakh per-supplier annual threshold, and the priority rule (194Q overrides 206C(1H) when both apply) all carry over into Section 393(1)(k). The 2025 Act is a renumbering exercise; the substantive rate, threshold, and priority rules remain identical.",
          "article": "TDS Payment Code 1012 (Section 393(1)(k)): Purchase of Goods Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1012-section-393-1-k-purchase-goods"
        },
        {
          "q": "How does code 1012 appear in Form 168 (the new Form 26AS)?",
          "a": "Form 168 lists each goods-purchase TDS credit with the deductor TAN (the buyer's TAN), deductor name, payment code 1012, parent section 393, payment description (Purchase of goods), date of deduction, taxable purchase value (above the ₹50 lakh threshold), tax deducted at 0.1%, status (booked / pending / under processing), and challan CIN. For a supplier with one large buyer, Form 168 will show TDS lines starting from the point in the FY when cumulative purchases by that buyer crossed ₹50 lakh.",
          "article": "TDS Payment Code 1012 (Section 393(1)(k)): Purchase of Goods Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1012-section-393-1-k-purchase-goods"
        },
        {
          "q": "What are the most common reconciliation issues for code 1012?",
          "a": "Four issues recur for code 1012. First, the overlap with TCS Section 394 (formerly 206C(1H)) — when both 194Q (now 1012) and 206C(1H) (now a code in the 1075 range) apply, 194Q/1012 takes priority and the seller is exempt from TCS. Second, the ₹50 lakh threshold trigger month — once cumulative purchases cross ₹50 lakh, TDS applies on the breaching purchase and retrospectively on the amount above ₹50 lakh. Third, GST-inclusive versus exclusive base — TDS on goods purchase is on the value of purchase including GST. Fourth, year-on-year buyer-turnover qualifier reset — the ₹10 crore prior-year turnover must be re-checked every April.",
          "article": "TDS Payment Code 1012 (Section 393(1)(k)): Purchase of Goods Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1012-section-393-1-k-purchase-goods"
        },
        {
          "q": "What is TDS payment code 1062?",
          "a": "TDS payment code 1062 is the four-digit identifier under Section 413 of the Income Tax Act 2025 for tax deducted on any sum paid to a non-resident, foreign company, or foreign entity that is chargeable to tax in India. It applies from April 1, 2026 and replaces the legacy Section 195 reference on challan ITNS 281, Form 27Q quarterly returns (the non-resident equivalent of Form 26Q), Form 131 deductee certificates, and Form 168 (the new Form 26AS). The code covers foreign professional fees, royalties, fees for technical services, interest paid to non-residents, capital gains on transfer of Indian assets by non-residents, and payments to foreign OTAs, foreign vendors, and foreign group entities under cost-allocation agreements.",
          "article": "TDS Payment Code 1062 (Section 413): Non-Resident Payment Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1062-section-413-non-resident"
        },
        {
          "q": "What is the rate and threshold for payment code 1062?",
          "a": "Payment code 1062 has no fixed rate or threshold. The rate is determined by either the relevant Double Taxation Avoidance Agreement (DTAA, also called a tax treaty) between India and the country of residence of the recipient, or by the Income Tax Act 2025 rate for the specific income type — whichever is lower. Typical rates: 10% to 15% on royalty and fees for technical services under most treaties; 10% to 20% on interest; 20% to 30% on capital gains depending on asset type and holding period. No PAN or tax residency certificate (TRC) means the treaty benefit is unavailable and Act rates apply (often 20% or higher).",
          "article": "TDS Payment Code 1062 (Section 413): Non-Resident Payment Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1062-section-413-non-resident"
        },
        {
          "q": "What did payment code 1062 replace under the 1961 Act?",
          "a": "Payment code 1062 replaces Section 195 of the Income Tax Act 1961, which has governed cross-border TDS since 1961. The treaty-rate-versus-Act-rate principle, the Form 15CA/15CB workflow (chartered accountant certification of cross-border remittances), the tax residency certificate (TRC) requirement under Section 90(4)/(5), and the lower-deduction certificate application under Section 197 all carry over into Section 413. The 2025 Act is a renumbering exercise; the substantive treaty mechanics for cross-border TDS remain identical, subject to the most-favoured-nation clauses and CBDT clarifications on specific treaties.",
          "article": "TDS Payment Code 1062 (Section 413): Non-Resident Payment Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1062-section-413-non-resident"
        },
        {
          "q": "How does code 1062 appear in Form 168 (the new Form 26AS)?",
          "a": "Form 168 lists each non-resident payment TDS credit with the deductor TAN, deductor name, payment code 1062, parent section 413, payment description (Payment to non-resident), income type (royalty / FTS / interest / dividend / capital gain / other), country of residence of the deductee, date of deduction, gross amount paid, tax deducted at treaty rate, status (booked / pending / under processing), challan CIN, and Form 15CA/15CB reference. Cross-border deductees often do not have Indian PAN; in that case the line appears in the deductor's Form 27Q return but not in any deductee Form 168 — only Indian-resident deductees see Form 168 statements.",
          "article": "TDS Payment Code 1062 (Section 413): Non-Resident Payment Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1062-section-413-non-resident"
        },
        {
          "q": "What are the most common reconciliation issues for code 1062?",
          "a": "Five issues recur for code 1062. First, the treaty-rate-versus-Act-rate determination — if the deductee fails to furnish a valid TRC and a Form 10F self-declaration, Act rates apply and the deduction is higher than the treaty rate. Second, Form 15CA/15CB workflow — every cross-border remittance above ₹5,00,000 cumulative per FY requires CA certification on Form 15CB before the bank releases funds. Third, equalisation levy overlap (digital advertising, e-commerce services) — equalisation levy is not TDS and does not go through code 1062. Fourth, royalty versus FTS classification — different treaties may classify the same payment differently. Fifth, beneficial ownership — payments to a treaty-country intermediary that is not the beneficial owner can be denied treaty benefit.",
          "article": "TDS Payment Code 1062 (Section 413): Non-Resident Payment Reconciliation Guide",
          "url": "https://www.terra-insight.com/insights/tds-payment-code-1062-section-413-non-resident"
        },
        {
          "q": "What is a TDS payment code under the Income Tax Act 2025?",
          "a": "A TDS payment code is a four-digit numeric identifier in the 1001 to 1092 range that classifies the type of payment subject to TDS or TCS from April 1, 2026. Payment codes replace the legacy section references (194C, 194J, 194H, and so on) as the primary classification key on challan ITNS 281, on the new Form 131 certificate (replacing Form 16A), and on the updated Form 168 (replacing Form 26AS). Each payment code sits under one of three parent sections: 392 for salary TDS, 393 for non-salary TDS, and 394 for TCS.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "Do payment codes change the TDS rate or threshold?",
          "a": "No. The Income Tax Act 2025 is a consolidation exercise, not a rate reset. The 1% and 2% rates under the contractor payment code carry over from Section 194C. The 10% rate for professional fees carries over from Section 194J. The ₹30,000 per-transaction and ₹1,00,000 aggregate thresholds under the contractor bucket remain the same. What changes is the identifier shown on the challan and the return; the rate table behind it is structurally unchanged, subject to the final notification.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "When do I start using payment codes on challan ITNS 281?",
          "a": "Payment codes 1001 to 1092 apply to all TDS and TCS deductions made on or after April 1, 2026. A contractor payment processed on April 3, 2026 must be deposited with a challan that carries the corresponding payment code under Section 393, not the legacy 194C reference. Deductions made up to March 31, 2026, even if the challan is deposited in April by the standard 7th-of-month deadline, continue to use old section codes because the underlying deduction falls under the 1961 Act.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "How does payment code 1XXX interact with Section 194T on partner remuneration?",
          "a": "Section 194T, introduced by the Finance Act 2024, levies 10% TDS on partner remuneration (salary, commission, interest, bonus) above ₹20,000 in a financial year. Under the Income Tax Act 2025, this is absorbed into the 393 parent section with its own payment code, likely in the 393(1) sub-clause range alongside other non-salary TDS. The first applicable year is FY 2025-26, so Q4 returns filed in May 2026 will carry Section 194T using old numbering, while Q1 FY 2026-27 filings will carry the new payment code for the same payment type.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "Will 206AB and 206CCA higher-deduction codes have payment codes too?",
          "a": "Sections 206AB and 206CCA, which applied higher TDS and TCS rates to non-filers of income tax returns, have been abolished under the Income Tax Act 2025. There is no successor payment code for non-filer penalties in the 1001 to 1092 range. Finance teams that maintain separate vendor flags or master data columns for 206AB screening should decommission those filters from April 1, 2026 and stop running the non-filer check through the compliance portal as part of the monthly TDS workflow.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "Where does the payment code appear on a challan ITNS 281 deposited from April 1, 2026?",
          "a": "The challan now requires the four-digit payment code in the section identifier field instead of the legacy section dropdown. The bank's e-payment portal — whichever authorised bank handles your TDS deposits (HDFC, ICICI, SBI, Axis, and others) — has been updated to surface the new payment codes. The OLTAS challan acknowledgement (CIN) records the payment code, and that code becomes the join key for TRACES challan-to-return matching. A challan deposited with the wrong payment code can still go through OLTAS but will not match cleanly to the corresponding line in the quarterly return.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "How do I read a Form 168 entry — what does each column mean?",
          "a": "Form 168 (which replaces Form 26AS for FY 2026-27 and beyond) lists each TDS or TCS credit with these columns: deductor TAN and name, payment code (e.g. 1003), parent section (392 / 393 / 394), payment description (e.g. Professional and technical services), date of deduction, amount of credit, status (booked / pending / under processing), and challan CIN. The payment code is the new primary classifier — you filter the statement by payment code to see all credits of a given type aggregated across deductors. Reconciliation against your TDS receivable ledger should join on payment code rather than the legacy section number.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "What if my ERP vendor has not yet released the payment code update?",
          "a": "Many mid-market ERPs released payment code patches between January and March 2026, but some — especially smaller localised systems — are still on legacy section codes. Until the patch lands, the workaround is to maintain an external mapping table (a spreadsheet or a lightweight database) that translates the ERP's section output into the correct payment code at the point of challan preparation and return filing. The ERP's underlying ledger entries can continue to carry the legacy section code; the translation layer applies at the integration boundary. This is an acceptable bridge for a quarter or two but is not sustainable longer term — push the ERP vendor for a patch with a firm timeline.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "How do TCS payment codes under Section 394 differ from TDS payment codes under Section 393?",
          "a": "TCS — Tax Collected at Source — sits under Section 394, with payment codes in the 1071+ range. The mechanics differ: TCS is collected by the seller from the buyer (rather than deducted from a payment outflow), and the buyer claims credit in their own Form 168. Common TCS payment codes cover scrap and forest produce (former 206C(1)), motor vehicles above ₹10 lakh (former 206C(1F)), sale of goods above ₹50 lakh (former 206C(1H)), and remittances under LRS / overseas tour packages (former 206C(1G)). Reconciliation logic is similar to TDS — match the seller's TCS line against your buyer-side TCS expense — but the parent section and code range are distinct, so the ledger should keep TCS in its own bucket rather than mixing with non-salary TDS.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "I deducted TDS under the wrong code in April. How do I fix it now?",
          "a": "If the wrong payment code went onto the challan, file a challan correction request through the deductor's TRACES profile within the quarterly return preparation cycle (before May 31 for Q1 FY 2026-27). The correction reassigns the deposit to the correct payment code, and the corrected entry flows through to the deductee's Form 168 once the return is filed. If the wrong code only affects the internal ledger but the challan and return are correct, fix the ledger entry directly and re-run reconciliation — there is no government-side action needed. The most damaging case is when the challan is correct but the return preparation tool used the wrong payment code; that creates a TRACES challan-to-return mismatch that surfaces as a default notice and needs a return correction filing.",
          "article": "TDS Payment Codes 1001–1092: Complete Reference for the Income Tax Act 2025",
          "url": "https://www.terra-insight.com/insights/tds-payment-codes-1001-1092-india"
        },
        {
          "q": "Which TDS rates changed mid-year in FY 2024-25?",
          "a": "Two rates changed on October 1, 2024. Section 194H (commission and brokerage) dropped from 5% to 2%. Section 194-O (e-commerce operator deduction) dropped from 1% to 0.1%. Any payment made on or after October 1, 2024 must be deducted at the new rate. Payments before that date must retain the old rate. Reconciliation systems that apply a flat annual rate generate false variances across the boundary.",
          "article": "TDS Rate by Date Reconciliation: How to Apply the Correct Rate When Rates Change Mid-Year",
          "url": "https://www.terra-insight.com/insights/tds-rate-by-date-reconciliation-india"
        },
        {
          "q": "Which thresholds changed in FY 2025-26?",
          "a": "The Finance Act 2025 raised two thresholds effective April 1, 2025. Section 194J (professional and technical services) saw its threshold raised from ₹30,000 per payment to ₹50,000 per payment. Section 194A (interest other than from banks for senior citizens) saw its threshold raised from ₹50,000 to ₹1,00,000 per financial year. Deductions in April 2025 onwards must apply these new thresholds; FY 2024-25 deductions retain the older thresholds.",
          "article": "TDS Rate by Date Reconciliation: How to Apply the Correct Rate When Rates Change Mid-Year",
          "url": "https://www.terra-insight.com/insights/tds-rate-by-date-reconciliation-india"
        },
        {
          "q": "Why does mid-year rate change cause reconciliation mismatches?",
          "a": "When a single annual rate is applied to every transaction, deductions in the earlier half of the year are effectively over-deducted (or under-deducted) compared to the correct rate for that date. This produces three failure modes: ledger-to-certificate variances where the amount differs by the rate delta, Form 168 variances where the government statement does not match the deductor certificate, and income tax notices where the ITR credit claim cannot be validated. The resolution requires re-running deductions with the correct rate applied by payment date.",
          "article": "TDS Rate by Date Reconciliation: How to Apply the Correct Rate When Rates Change Mid-Year",
          "url": "https://www.terra-insight.com/insights/tds-rate-by-date-reconciliation-india"
        },
        {
          "q": "How is payment date defined for TDS rate selection?",
          "a": "For TDS rate selection, the payment date is the earlier of credit to the payee's account or actual payment — the same test used to determine when TDS liability arises under the Income Tax Act. An invoice dated September 28, 2024 that is paid on October 5, 2024 (for a Section 194H commission) attracts the new 2% rate because the payment occurred after the October 1 effective date. An invoice credited on September 30 and paid October 5 attracts the old 5% rate because the credit date is earlier.",
          "article": "TDS Rate by Date Reconciliation: How to Apply the Correct Rate When Rates Change Mid-Year",
          "url": "https://www.terra-insight.com/insights/tds-rate-by-date-reconciliation-india"
        },
        {
          "q": "What is the penalty for applying the wrong TDS rate?",
          "a": "Under-deduction attracts interest at 1% per month from the date TDS should have been deducted to the date of actual deduction, under Section 201(1A) of the 1961 Act (equivalent provision under Chapter XX of the 2025 Act). The deductor is also treated as an assessee in default and may face penalty up to the amount of TDS not deducted under Section 271C. For a company with 500 Section 194H transactions mis-deducted at 5% instead of 2% after October 1, 2024, the excess deducted must be refunded or adjusted in subsequent quarters, and the reconciliation variance must be resolved before Form 26AS for FY 2024-25 can be finalised.",
          "article": "TDS Rate by Date Reconciliation: How to Apply the Correct Rate When Rates Change Mid-Year",
          "url": "https://www.terra-insight.com/insights/tds-rate-by-date-reconciliation-india"
        }
      ]
    },
    "it-services-saas": {
      "label": "IT Services and SaaS Reconciliation",
      "faqs": [
        {
          "q": "What is deferred revenue and why must SaaS companies reconcile it?",
          "a": "Deferred revenue is the portion of cash received for a service that has not yet been delivered. Under Ind AS 115, a SaaS company that receives ₹12 lakh for a 12-month subscription must recognize only ₹1 lakh per month as revenue and carry ₹11 lakh as a current liability on day one. Reconciliation confirms that the deferred revenue balance on the balance sheet matches the sum of undelivered performance obligations across all active contracts. Errors here directly affect reported profit and Schedule III disclosures filed with the MCA.",
          "article": "Deferred Revenue Reconciliation for Indian SaaS Companies",
          "url": "https://www.terra-insight.com/insights/deferred-revenue-reconciliation-saas-india"
        },
        {
          "q": "How does GST apply to SaaS subscriptions in India?",
          "a": "SaaS services are classified as OIDAR (Online Information and Database Access or Retrieval) under GST and attract 18% GST under SAC 998314. For domestic customers, the SaaS company charges 18% GST on each invoice. For export customers, the company can either file a Letter of Undertaking (LUT) for zero-rated supply or pay IGST and claim a refund. The reconciliation must separate the GST component from the deferred revenue schedule — GST liability arises on invoice date, not on revenue recognition date.",
          "article": "Deferred Revenue Reconciliation for Indian SaaS Companies",
          "url": "https://www.terra-insight.com/insights/deferred-revenue-reconciliation-saas-india"
        },
        {
          "q": "What happens when a SaaS contract includes implementation and support along with the subscription?",
          "a": "A multi-element SaaS contract — subscription plus implementation plus annual support — contains three separate performance obligations under Ind AS 115. Each must be allocated a portion of the total transaction price based on standalone selling price. Implementation revenue is recognized on completion (point in time), subscription revenue over the contract period (over time), and support revenue over the support period. The deferred revenue schedule must track each element separately.",
          "article": "Deferred Revenue Reconciliation for Indian SaaS Companies",
          "url": "https://www.terra-insight.com/insights/deferred-revenue-reconciliation-saas-india"
        },
        {
          "q": "How often should Indian SaaS companies reconcile deferred revenue?",
          "a": "Monthly reconciliation is the minimum standard for SaaS companies with more than 100 active subscriptions. The process matches the deferred revenue waterfall schedule against three data sources: (1) cash received per bank statement, (2) invoices raised per the billing system, and (3) revenue recognized in the general ledger. Quarterly reconciliation is required at minimum for Ind AS-compliant companies to support the financial statement disclosures mandated under Schedule III — specifically the contract liability balance and revenue recognized from opening deferred revenue.",
          "article": "Deferred Revenue Reconciliation for Indian SaaS Companies",
          "url": "https://www.terra-insight.com/insights/deferred-revenue-reconciliation-saas-india"
        },
        {
          "q": "What is the difference between deferred revenue and contract liability under Ind AS 115?",
          "a": "Under Ind AS 115, a contract liability exists when the company has received payment before satisfying the performance obligation. Deferred revenue is the common accounting term for the same concept. For Indian SaaS companies, the Schedule III balance sheet reports this as 'Contract Liabilities' under current liabilities. The reconciliation must ensure that the contract liability balance equals total cash received minus total revenue recognized across all active contracts, with separate tracking for each performance obligation in multi-element arrangements.",
          "article": "Deferred Revenue Reconciliation for Indian SaaS Companies",
          "url": "https://www.terra-insight.com/insights/deferred-revenue-reconciliation-saas-india"
        },
        {
          "q": "When did Ind AS 115 become effective for Indian companies?",
          "a": "Ind AS 115 (Revenue from Contracts with Customers) became effective for all Indian companies following Ind AS from 1 April 2018, replacing Ind AS 18 (Revenue) and Ind AS 11 (Construction Contracts). The MCA notification required retrospective application with a cumulative catch-up adjustment on the transition date. Companies that did not adjust their revenue recognition processes in 2018 may still carry legacy recognition patterns that do not comply with the five-step model.",
          "article": "Ind AS 115 Revenue Reconciliation for Indian IT and SaaS Companies",
          "url": "https://www.terra-insight.com/insights/ind-as-115-revenue-reconciliation-india"
        },
        {
          "q": "What are the five steps of the Ind AS 115 revenue recognition model?",
          "a": "The five steps are: (1) Identify the contract with the customer, (2) Identify the performance obligations in the contract, (3) Determine the transaction price, (4) Allocate the transaction price to each performance obligation, and (5) Recognize revenue as each performance obligation is satisfied. For an IT services company, a single master service agreement may contain multiple performance obligations — development (milestone-based), maintenance (over time), and licences (point in time) — each requiring separate tracking.",
          "article": "Ind AS 115 Revenue Reconciliation for Indian IT and SaaS Companies",
          "url": "https://www.terra-insight.com/insights/ind-as-115-revenue-reconciliation-india"
        },
        {
          "q": "How should contract modifications be handled under Ind AS 115?",
          "a": "Contract modifications — scope changes, rate revisions, additional work orders — must be assessed as either a separate contract (if the additional goods/services are distinct and priced at standalone selling price) or a modification of the existing contract. If treated as a modification, the company must choose between prospective treatment (allocate remaining price to remaining obligations) or cumulative catch-up (recalculate from inception). Indian IT companies with change requests on fixed-price projects must document the modification type and adjust the revenue schedule accordingly.",
          "article": "Ind AS 115 Revenue Reconciliation for Indian IT and SaaS Companies",
          "url": "https://www.terra-insight.com/insights/ind-as-115-revenue-reconciliation-india"
        },
        {
          "q": "What disclosures does Ind AS 115 require in Indian financial statements?",
          "a": "Ind AS 115 requires disclosure of: (1) disaggregation of revenue by type (licence, subscription, services), geography, and timing (point in time vs over time); (2) contract balances — receivables, contract assets, and contract liabilities with opening and closing movements; (3) remaining performance obligations and expected timing of recognition; and (4) significant judgments — methods used to determine standalone selling prices and timing of satisfaction. These disclosures are mandatory in the notes to financial statements filed with the MCA under Schedule III.",
          "article": "Ind AS 115 Revenue Reconciliation for Indian IT and SaaS Companies",
          "url": "https://www.terra-insight.com/insights/ind-as-115-revenue-reconciliation-india"
        },
        {
          "q": "What is variable consideration under Ind AS 115 and how does it affect IT services revenue?",
          "a": "Variable consideration includes milestone bonuses, performance penalties, volume discounts, and SLA credits that make the transaction price uncertain at contract inception. Under Ind AS 115, the company must estimate variable consideration using either the expected value method (probability-weighted) or the most likely amount method, and include it in the transaction price only to the extent that a significant revenue reversal is not probable. For an IT company with a ₹50 lakh project and a 10% milestone bonus, the bonus is included in revenue only when achievement is highly probable — typically when the milestone is near completion.",
          "article": "Ind AS 115 Revenue Reconciliation for Indian IT and SaaS Companies",
          "url": "https://www.terra-insight.com/insights/ind-as-115-revenue-reconciliation-india"
        },
        {
          "q": "Is TDS on IT services contracts deducted under Section 194J or 194C?",
          "a": "The classification depends on the nature of the contract. Section 194J (10% TDS) applies to fees for professional or technical services — this covers software development, consulting, and technical advisory work. Section 194C (1% for individuals, 2% for companies) applies to contracts for carrying out work, which covers staff augmentation and outsourced process execution. Many IT services contracts involve both elements, and clients often classify the entire contract under one section. The reconciliation process must match the TDS rate applied by the client in Form 26AS against the rate the company expects based on the contract classification. Disputes are common and require correction returns by the deductor.",
          "article": "Milestone Billing Reconciliation for IT Services Companies in India",
          "url": "https://www.terra-insight.com/insights/milestone-billing-reconciliation-it-services"
        },
        {
          "q": "How should revenue be recognised for milestone-based IT contracts under Ind AS 115?",
          "a": "Under Ind AS 115, revenue for a milestone-based IT contract is recognised when (or as) each performance obligation is satisfied. For fixed-price contracts with defined deliverables, each milestone typically represents a distinct performance obligation if the client can benefit from each deliverable on its own. Revenue is recognised at the point when the client formally accepts the deliverable (sign-off). If the milestones are interdependent and the client only benefits from the completed whole, revenue is recognised over time using the input method (cost-to-cost) or output method (milestones completed as a percentage of total). The transaction price must be allocated to each milestone based on standalone selling prices.",
          "article": "Milestone Billing Reconciliation for IT Services Companies in India",
          "url": "https://www.terra-insight.com/insights/milestone-billing-reconciliation-it-services"
        },
        {
          "q": "What happens when a client withholds payment pending final milestone completion?",
          "a": "Many IT services contracts include retention clauses where 10-20% of each milestone payment is withheld until final delivery and acceptance. This retention creates a receivable that does not convert to cash until the project is complete, which may be 6-12 months after the milestone invoice was raised. The retention amount must be tracked as a separate receivable line item, not clubbed with the current milestone receivable. Under Ind AS 115, revenue is still recognised on milestone acceptance, but the retention receivable should be assessed for impairment if there is a significant delay in final acceptance.",
          "article": "Milestone Billing Reconciliation for IT Services Companies in India",
          "url": "https://www.terra-insight.com/insights/milestone-billing-reconciliation-it-services"
        },
        {
          "q": "How do Indian IT companies reconcile milestone invoices against Form 26AS?",
          "a": "Each milestone invoice triggers a TDS deduction by the client at 194J (10%) or 194C (1-2%). The deducted amount should appear in Form 26AS within the quarter it was deducted. The reconciliation matches: invoice number and amount in the billing system → TDS certificate (Form 16A) from the client → Form 26AS entry showing the certificate number, amount, and section. Common mismatches include: wrong section code (194C instead of 194J), wrong quarter of deposit by the deductor, amount mismatch due to GST inclusion in the TDS base, and TDS deducted but not deposited by the client within the due date (7th of the following month).",
          "article": "Milestone Billing Reconciliation for IT Services Companies in India",
          "url": "https://www.terra-insight.com/insights/milestone-billing-reconciliation-it-services"
        },
        {
          "q": "What is the typical milestone billing cycle for Indian IT services projects?",
          "a": "A standard milestone billing cycle for Indian IT services runs: deliverable completion by the project team (day 0) → internal quality review (day 1-3) → client submission and sign-off (day 3-10, contractual acceptance period is usually 7-15 working days) → invoice generation on acceptance (day 10-15) → client payment terms (30-60 days from invoice date) → TDS deduction by client at payment → net amount credited to bank. From deliverable completion to cash receipt, the typical cycle is 45-75 days. The reconciliation must track each milestone through every stage, because delays at any point — particularly client sign-off — cascade through the entire chain.",
          "article": "Milestone Billing Reconciliation for IT Services Companies in India",
          "url": "https://www.terra-insight.com/insights/milestone-billing-reconciliation-it-services"
        },
        {
          "q": "What is FIRC and why is it important for multi-currency reconciliation?",
          "a": "A Foreign Inward Remittance Certificate (FIRC) is issued by the Authorized Dealer (AD) bank as proof that foreign currency was received into India. Under RBI FEMA guidelines, every software export receipt must have a corresponding FIRC. During reconciliation, each FIRC must be matched to the invoice it relates to, the bank credit in INR, and the SOFTEX declaration — a four-way match. Missing FIRCs can trigger FEMA compliance queries during RBI audits.",
          "article": "Multi-Currency Reconciliation for Indian IT Services Companies",
          "url": "https://www.terra-insight.com/insights/multi-currency-reconciliation-it-services-india"
        },
        {
          "q": "How does the exchange rate variance arise in IT services payments?",
          "a": "An Indian IT company invoices USD 50,000 at ₹83.50 (booking value ₹41,75,000). The client pays 30 days later when the bank applies a rate of ₹84.20, crediting ₹42,10,000. The ₹35,000 difference is a foreign exchange gain that must be recognized in the P&L under Ind AS 21. If the rate had moved to ₹82.80, the ₹35,000 shortfall is a forex loss. Both must be classified separately from trade receivable adjustments.",
          "article": "Multi-Currency Reconciliation for Indian IT Services Companies",
          "url": "https://www.terra-insight.com/insights/multi-currency-reconciliation-it-services-india"
        },
        {
          "q": "What is SOFTEX and how does it affect reconciliation for STPI units?",
          "a": "SOFTEX is a statutory declaration filed with the Software Technology Parks of India (STPI) or SEZ authority for every software export. Each SOFTEX entry must match the corresponding invoice, FIRC, and bank credit. STPI units must file SOFTEX within 30 days of the invoice date. Reconciliation must verify that every export invoice has a filed SOFTEX and that the SOFTEX amount matches the FIRC amount after accounting for exchange rate differences.",
          "article": "Multi-Currency Reconciliation for Indian IT Services Companies",
          "url": "https://www.terra-insight.com/insights/multi-currency-reconciliation-it-services-india"
        },
        {
          "q": "How often must Indian IT companies report forex receipts to the RBI?",
          "a": "AD banks submit monthly returns to the RBI covering all foreign exchange transactions including software export receipts. Companies must provide supporting documents — FIRCs, invoices, and SOFTEX declarations — to the AD bank. For STPI/SEZ units, an annual performance report reconciling total exports against SOFTEX filings is also required. Any mismatch between reported receipts and actual bank credits can trigger an RBI inquiry under FEMA Section 13.",
          "article": "Multi-Currency Reconciliation for Indian IT Services Companies",
          "url": "https://www.terra-insight.com/insights/multi-currency-reconciliation-it-services-india"
        },
        {
          "q": "Can TDS under Section 195 apply to multi-currency transactions?",
          "a": "Section 195 applies when an Indian company makes payments to a non-resident, not when it receives payments from abroad. However, if an Indian IT company subcontracts work to a foreign vendor and pays in foreign currency, TDS under Section 195 must be deducted at the applicable rate (typically 10-40% depending on the nature of payment and DTAA provisions). The reconciliation must track the gross payment, TDS deducted, net remittance, and Form 15CA/15CB filing status for each outward payment.",
          "article": "Multi-Currency Reconciliation for Indian IT Services Companies",
          "url": "https://www.terra-insight.com/insights/multi-currency-reconciliation-it-services-india"
        },
        {
          "q": "What is deferred revenue in SaaS subscription reconciliation?",
          "a": "Deferred revenue is the portion of a subscription payment received upfront that has not yet been earned through service delivery. For example, if a customer pays ₹12,00,000 for a 12-month annual subscription on 1 July, only ₹1,00,000 is recognised as revenue in July. The remaining ₹11,00,000 sits as a current liability (deferred revenue) on the balance sheet. Under Ind AS 115, revenue is recognised over the subscription period as the performance obligation — providing access to the SaaS platform — is satisfied over time. The deferred revenue schedule must reconcile monthly against the revenue recognition schedule and the cash receipt ledger.",
          "article": "SaaS Subscription Reconciliation in India: MRR, Deferred Revenue, and Cash Matching",
          "url": "https://www.terra-insight.com/insights/saas-subscription-reconciliation-india"
        },
        {
          "q": "How does GST apply to SaaS subscriptions sold to Indian customers?",
          "a": "SaaS subscriptions sold to Indian customers attract GST at 18% under SAC code 998314 (licensing services for the right to use computer software). The SaaS company must charge CGST + SGST for intra-state sales or IGST for inter-state sales. For annual subscriptions billed upfront, GST is payable on the full invoice value in the month of billing, even though revenue recognition is spread over 12 months. This creates a timing difference between GST liability (immediate) and revenue recognition (deferred) that must be tracked in the reconciliation process.",
          "article": "SaaS Subscription Reconciliation in India: MRR, Deferred Revenue, and Cash Matching",
          "url": "https://www.terra-insight.com/insights/saas-subscription-reconciliation-india"
        },
        {
          "q": "Do Indian SaaS companies need to file a Letter of Undertaking (LUT) for export revenue?",
          "a": "Yes. Indian SaaS companies exporting services must file Form GST RFD-11 (Letter of Undertaking) with their jurisdictional GST officer before the start of each financial year. The LUT allows zero-rated export of services without payment of IGST. If the LUT is not filed or lapses, the company must charge IGST at 18% on export invoices and then claim a refund — a process that typically takes 60-90 days and creates a cash flow gap. The LUT filing deadline is before the first export invoice of the new financial year, and the company must not have been prosecuted for tax evasion exceeding ₹2.5 crore in the preceding two years.",
          "article": "SaaS Subscription Reconciliation in India: MRR, Deferred Revenue, and Cash Matching",
          "url": "https://www.terra-insight.com/insights/saas-subscription-reconciliation-india"
        },
        {
          "q": "How should forex gains and losses be reconciled for USD-billed SaaS subscriptions?",
          "a": "When an Indian SaaS company invoices in USD and receives payment in INR, three exchange rates are involved: the invoice date rate (for booking the receivable), the receipt date rate (for recording the bank credit), and the reporting date rate (for revaluing outstanding receivables under Ind AS 21). The difference between invoice date and receipt date rates creates a realised forex gain or loss. The difference between invoice date and reporting date rates creates an unrealised gain or loss. Both must be tracked per invoice and reconciled against the FIRC (Foreign Inward Remittance Certificate) issued by the bank. For a SaaS company with 200 USD-billed customers, this produces 600+ forex entries per quarter.",
          "article": "SaaS Subscription Reconciliation in India: MRR, Deferred Revenue, and Cash Matching",
          "url": "https://www.terra-insight.com/insights/saas-subscription-reconciliation-india"
        },
        {
          "q": "What is the Ind AS 115 performance obligation for a SaaS subscription?",
          "a": "Under Ind AS 115 (Revenue from Contracts with Customers), a SaaS subscription typically constitutes a single performance obligation: providing continuous access to the software platform over the subscription period. Revenue is recognised over time because the customer simultaneously receives and consumes the benefit. The transaction price is the total subscription fee, allocated evenly across the subscription period (straight-line basis). If the subscription includes distinct deliverables — such as implementation services, training, or a separate data migration module — each must be identified as a separate performance obligation and allocated a portion of the transaction price based on standalone selling price. ICAI's guidance note on Ind AS 115 provides detailed examples for technology companies.",
          "article": "SaaS Subscription Reconciliation in India: MRR, Deferred Revenue, and Cash Matching",
          "url": "https://www.terra-insight.com/insights/saas-subscription-reconciliation-india"
        },
        {
          "q": "How is TDS deducted on time-and-material IT services invoices?",
          "a": "Clients deduct TDS on T&M invoices under Section 194J at 10% for professional and technical services. The TDS is calculated on the invoice value excluding GST (per CBDT Circular 1/2014, TDS is deducted on the base amount when GST is shown separately on the invoice). For a monthly T&M invoice of ₹15,00,000 plus GST of ₹2,70,000 (18%), the client deducts TDS of ₹1,50,000 (10% of ₹15,00,000) and pays ₹16,20,000 (₹15,00,000 + ₹2,70,000 GST - ₹1,50,000 TDS). The TDS must be deposited by the client by the 7th of the following month and should appear in the IT company's Form 26AS within the same quarter.",
          "article": "Time-and-Material Billing Reconciliation for Indian IT Companies",
          "url": "https://www.terra-insight.com/insights/time-and-material-billing-reconciliation-india"
        },
        {
          "q": "What happens when approved timesheet hours do not match the invoiced hours?",
          "a": "A mismatch between approved timesheet hours and invoiced hours is one of the most common T&M reconciliation exceptions. Causes include: timesheets approved after the billing cut-off date (hours appear in the next month's invoice), client-rejected hours that were included in the invoice, rate card changes effective mid-month that were not applied to all line items, and leave or bench days incorrectly marked as billable. The resolution requires a three-way check: timesheet system (approved hours per consultant per client) vs. billing system (invoiced hours and rates) vs. client purchase order (contracted rate and maximum hours). Any variance above the contractual tolerance (typically 0.5-1% of monthly billing) must be investigated before invoice finalization.",
          "article": "Time-and-Material Billing Reconciliation for Indian IT Companies",
          "url": "https://www.terra-insight.com/insights/time-and-material-billing-reconciliation-india"
        },
        {
          "q": "How do Indian IT companies handle forex reconciliation on USD T&M billing?",
          "a": "Indian IT companies billing T&M clients in USD must reconcile at three exchange rate points: the invoice date rate (used to book the INR receivable), the FIRC (Foreign Inward Remittance Certificate) rate at which the bank converts the USD wire to INR, and the RBI reference rate on the reporting date for revaluing outstanding receivables. For a $50,000 monthly invoice booked at ₹84.20/USD (receivable = ₹42,10,000) and received at ₹84.50/USD (bank credit = ₹42,25,000), the realised forex gain of ₹15,000 must be recorded. Under Ind AS 21, unrealised gains on open receivables at quarter-end are recognised in profit and loss. The FIRC from the bank is the authoritative document for the actual conversion rate.",
          "article": "Time-and-Material Billing Reconciliation for Indian IT Companies",
          "url": "https://www.terra-insight.com/insights/time-and-material-billing-reconciliation-india"
        },
        {
          "q": "What is the typical month-end close timeline for T&M billing reconciliation?",
          "a": "For an Indian IT company with 15 clients on T&M billing, the month-end close for billing reconciliation typically follows: timesheet submission deadline (1st-2nd of the following month) → manager approval of timesheets (2nd-3rd) → billing team generates invoices from approved timesheets (3rd-5th) → invoices reviewed against rate cards and POs (5th-6th) → invoices dispatched to clients (6th-7th) → revenue recognised in the GL (7th-8th). The reconciliation of the previous month's receipts — matching bank credits to invoices, recording TDS receivables, and booking forex gains/losses — runs in parallel during days 1-5. For companies with 200+ consultants, this process extends to day 10-12 without automation.",
          "article": "Time-and-Material Billing Reconciliation for Indian IT Companies",
          "url": "https://www.terra-insight.com/insights/time-and-material-billing-reconciliation-india"
        },
        {
          "q": "Can a client deduct TDS under Section 194C instead of 194J for T&M contracts?",
          "a": "Yes, and this is a frequent source of reconciliation mismatches. Section 194C (1% for individuals, 2% for companies) applies to contracts for carrying out work, while Section 194J (10%) applies to professional or technical services. Some clients classify T&M staff augmentation contracts under 194C, arguing that the IT company is providing manpower rather than professional services. The IT company may disagree and expect 194J treatment. When the TDS rate in Form 26AS does not match the company's expectation, the finance team must either accept the lower credit and file the return accordingly, or request the client to file a TDS correction return (Form 26Q) changing the section code. The correction return process takes 30-60 days.",
          "article": "Time-and-Material Billing Reconciliation for Indian IT Companies",
          "url": "https://www.terra-insight.com/insights/time-and-material-billing-reconciliation-india"
        }
      ]
    },
    "glossary": {
      "label": "Reconciliation Glossary",
      "faqs": [
        {
          "q": "What is a reconciling item in bank reconciliation?",
          "a": "A reconciling item is any transaction that causes the balance per the bank statement to differ from the balance per the company's cashbook on the reconciliation date. Common reconciling items include cheques issued but not yet presented to the bank (outstanding cheques), deposits recorded in the books but not yet credited by the bank (deposits in transit), bank charges not yet recorded in the books, and direct credits received by the bank that the company has not yet posted.",
          "article": "Financial Reconciliation Dictionary: Terms Used in Indian Finance Operations",
          "url": "https://www.terra-insight.com/insights/financial-reconciliation-dictionary-india"
        },
        {
          "q": "What does match rate mean in reconciliation software?",
          "a": "Match rate is the percentage of transactions in a dataset that have been successfully matched to a corresponding entry in the other dataset being reconciled — for example, purchase invoices matched to bank debits, or settlement lines matched to order records. A match rate of 88% means 12% of transactions require manual review. Finance teams track match rate as the primary KPI for reconciliation efficiency; a consistently low match rate signals data quality issues, process gaps, or system misconfigurations.",
          "article": "Financial Reconciliation Dictionary: Terms Used in Indian Finance Operations",
          "url": "https://www.terra-insight.com/insights/financial-reconciliation-dictionary-india"
        },
        {
          "q": "What is an audit trail and why does it matter for finance compliance?",
          "a": "An audit trail is a time-stamped, tamper-evident log of every action taken on a transaction or reconciliation record — who matched it, when, what was changed, and on what basis. In India, audit trails are required under the Companies (Accounts) Amendment Rules, 2021, which mandate that accounting software maintain an uneditable log of all transactions from 1 April 2023. During statutory or internal audits, the audit trail is used to verify that reconciliations were completed on time, reviewed by the right people, and not retroactively altered.",
          "article": "Financial Reconciliation Dictionary: Terms Used in Indian Finance Operations",
          "url": "https://www.terra-insight.com/insights/financial-reconciliation-dictionary-india"
        },
        {
          "q": "What is the difference between GSTR-2A and GSTR-2B?",
          "a": "GSTR-2A is a dynamic, real-time statement that updates every time a supplier files or amends GSTR-1. GSTR-2B is a static, auto-drafted statement generated once per month on the 14th, showing ITC available based on supplier filings up to the cut-off date. For reconciliation purposes, GSTR-2B is the operationally significant statement because it determines what ITC a business can legally claim in that month's GSTR-3B.",
          "article": "GST Reconciliation Glossary: Terms Every Finance Team Must Know",
          "url": "https://www.terra-insight.com/insights/gst-reconciliation-glossary-india"
        },
        {
          "q": "What is ITC leakage and how does reconciliation prevent it?",
          "a": "ITC leakage occurs when a business is entitled to input tax credit but fails to claim it — typically because a supplier's invoice does not appear in GSTR-2B due to late filing, incorrect GSTIN, or invoice date beyond the cut-off. Systematic reconciliation between purchase registers and GSTR-2B identifies missing invoices, allowing the finance team to follow up with suppliers before the annual deadline, preventing permanent ITC loss.",
          "article": "GST Reconciliation Glossary: Terms Every Finance Team Must Know",
          "url": "https://www.terra-insight.com/insights/gst-reconciliation-glossary-india"
        },
        {
          "q": "When does a credit note affect GST reconciliation?",
          "a": "A credit note issued by a supplier reduces the ITC available to the recipient. Suppliers report credit notes in GSTR-1, which then flows into the recipient's GSTR-2B. If the recipient has already claimed ITC on the original invoice, the credit note creates a reversal obligation in GSTR-3B. Reconciliation must match credit notes in the purchase register against supplier-reported credit notes in GSTR-2B to avoid over-claiming ITC and the associated interest liability.",
          "article": "GST Reconciliation Glossary: Terms Every Finance Team Must Know",
          "url": "https://www.terra-insight.com/insights/gst-reconciliation-glossary-india"
        },
        {
          "q": "What is the difference between NACH and ECS?",
          "a": "ECS (Electronic Clearing Service) was the original RBI-managed bulk payment system introduced in the 1990s. NACH (National Automated Clearing House) was launched by NPCI in 2012 as a centralised, standardised replacement for ECS, offering faster processing, better error handling, and a unified mandate framework across all banks. Most banks migrated from ECS to NACH between 2016 and 2020, and the RBI formally discontinued ECS in December 2020. For reconciliation purposes, any legacy ECS references in older loan portfolios must be mapped to NACH equivalents.",
          "article": "NACH and Payments Glossary: Key Terms for Reconciliation",
          "url": "https://www.terra-insight.com/insights/nach-payments-glossary-india"
        },
        {
          "q": "What does a NACH return code mean and how do lenders handle it?",
          "a": "A NACH return code is a two-character code (R01 through R29 in the standard NPCI framework) assigned by the destination bank when it is unable to process a NACH debit instruction. R01 indicates insufficient funds; R02 means the account has been closed; R04 indicates an invalid account number; R14 means the account holder is deceased. Lenders use return codes to classify failed EMI presentations by root cause — operational errors (R04, R09) versus financial distress (R01) versus fraud signals (R02 in a new account). Return code data feeds directly into collection strategy and reconciliation of expected versus actual EMI receipts.",
          "article": "NACH and Payments Glossary: Key Terms for Reconciliation",
          "url": "https://www.terra-insight.com/insights/nach-payments-glossary-india"
        },
        {
          "q": "How long does NACH credit take to reflect in a bank account?",
          "a": "NACH credit (ACH Credit) transactions settle on a T+1 cycle — the beneficiary's bank account is credited one business day after the sponsor bank initiates the batch. For a batch submitted on Monday, credits typically appear in destination accounts by Tuesday morning. However, there is a processing cut-off time (usually early afternoon) for same-day submission; batches submitted after the cut-off are processed the next business day, effectively making them T+2. Finance teams reconciling NACH credit disbursements must account for this one-day lag when matching disbursement records to bank statement credits.",
          "article": "NACH and Payments Glossary: Key Terms for Reconciliation",
          "url": "https://www.terra-insight.com/insights/nach-payments-glossary-india"
        },
        {
          "q": "What is MDR and is it recoverable as ITC?",
          "a": "MDR (Merchant Discount Rate) is the fee charged by a payment gateway or acquirer as a percentage of the transaction value for processing card, UPI, or netbanking payments. MDR attracts 18% GST. Whether it is claimable as Input Tax Credit depends on how the business uses it — if the merchant's outputs are taxable, MDR GST is generally claimable as ITC, provided the payment gateway issues a valid GST invoice. Finance teams must obtain GST-compliant invoices or debit notes from their payment gateway monthly and reconcile them against the fee deductions shown in settlement reports.",
          "article": "Platform Settlement Glossary: Terms for E-Commerce and Payment Gateway Finance Teams",
          "url": "https://www.terra-insight.com/insights/platform-settlement-glossary-india"
        },
        {
          "q": "What is TCS on e-commerce platforms and how is it reconciled?",
          "a": "TCS under Section 52 of the CGST Act requires e-commerce operators to collect 1% GST (0.5% CGST + 0.5% SGST, or 1% IGST for inter-state) on net taxable sales made through their platform. This amount is deducted from the seller's settlement payout. Sellers can claim credit for this TCS in their GSTR-3B, but only after the operator files GSTR-8 and the amount appears in the seller's GSTR-2B. Reconciliation involves matching TCS deducted in settlement reports against amounts visible in GSTR-2B each month. Additionally, TDS under Section 194-O requires the operator to deduct 1% income tax TDS on gross sales where the seller's aggregate exceeds Rs 5 lakh.",
          "article": "Platform Settlement Glossary: Terms for E-Commerce and Payment Gateway Finance Teams",
          "url": "https://www.terra-insight.com/insights/platform-settlement-glossary-india"
        },
        {
          "q": "What is the difference between gross settlement and net settlement?",
          "a": "In gross settlement, the payment gateway or marketplace credits the full transaction value to the merchant and then separately debits fees, returns, and TDS in subsequent transactions or cycles. In net settlement — the standard model for most Indian payment gateways and marketplaces — the platform deducts MDR, platform commission, TCS, TDS, chargeback amounts, and returns before remitting the residual to the seller. Net settlement makes reconciliation more complex because the seller's books record full invoice value but bank credits reflect a lower net amount, requiring systematic deduction mapping.",
          "article": "Platform Settlement Glossary: Terms for E-Commerce and Payment Gateway Finance Teams",
          "url": "https://www.terra-insight.com/insights/platform-settlement-glossary-india"
        },
        {
          "q": "What is the difference between TAN and PAN in TDS?",
          "a": "TAN (Tax Deduction Account Number) is a 10-character identifier issued to entities that deduct or collect tax at source. PAN (Permanent Account Number) is assigned to every taxpayer — individuals and entities — and identifies the deductee whose credit is being reported. A single entity holds one PAN but may hold one TAN; deductors quote TAN on challans and returns, while deductees quote PAN to claim credit.",
          "article": "TDS Glossary: Essential Terms for TDS Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/tds-glossary-india"
        },
        {
          "q": "What is TRACES and how do finance teams use it?",
          "a": "TRACES (TDS Reconciliation Analysis and Correction Enabling System) is the Income Tax Department's portal at tdscpc.gov.in where deductors file and revise TDS returns, generate Form 16/16A, and download their 26AS data. Finance teams use it to verify that deposited challans have been mapped correctly, identify short or excess deductions, and download justification reports when mismatches appear between their records and the deductee's Form 26AS.",
          "article": "TDS Glossary: Essential Terms for TDS Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/tds-glossary-india"
        },
        {
          "q": "What is the difference between Form 16 and Form 16A?",
          "a": "Form 16 is issued by employers to salaried employees and covers TDS deducted on salary income under Section 192. Form 16A is issued for all other TDS deductions — contracts (194C), professional fees (194J), interest (194A), rent (194I), and so on. Both serve as certificates that tax has been deposited, but they apply to different income types and are generated separately from TRACES.",
          "article": "TDS Glossary: Essential Terms for TDS Reconciliation in India",
          "url": "https://www.terra-insight.com/insights/tds-glossary-india"
        }
      ]
    },
    "definitions-glossary": {
      "label": "Definitions and Glossary",
      "faqs": [
        {
          "q": "What is a bank reconciliation statement?",
          "a": "A bank reconciliation statement is a formal document that explains the difference between a company's bank account balance as per its books (ERP ledger or cashbook) and the balance shown in the bank statement for the same date. It lists each identified difference — outstanding cheques (issued but not yet presented to the bank), deposits in transit (received but not yet credited by the bank), bank charges not yet recorded in the books, and any errors by either party — and shows that after adjusting for all differences, the two balances agree. It is prepared at a minimum monthly and is required as evidence for statutory audits.",
          "article": "What Is a Reconciliation Statement? Definition and Types for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-a-reconciliation-statement"
        },
        {
          "q": "Is a reconciliation statement mandatory in India?",
          "a": "Several reconciliation statements are mandatory under Indian law. GSTR-9 (the annual GST return) requires a reconciliation of ITC claimed across all GSTR-3B filings for the year against the annual GSTR-2B, and a reconciliation of turnover between GSTR-1 and the financial statements — mandatory for all GST-registered entities with turnover above Rs 2 crore. TDS receivable reconciliation against Form 26AS is required for accurate ITR filing — any unclaimed credit or excess claim creates a demand notice from the Income Tax Department. Bank reconciliation is required by statutory auditors as part of the audit of cash and bank balances, under auditing standards issued by ICAI.",
          "article": "What Is a Reconciliation Statement? Definition and Types for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-a-reconciliation-statement"
        },
        {
          "q": "What is the difference between a reconciliation statement and a balance sheet?",
          "a": "A balance sheet is a financial statement showing the assets, liabilities, and equity of an entity at a specific point in time — it is a position statement derived from the accounting records. A reconciliation statement does not summarise financial position; it explains the difference between two specific records of the same underlying transactions. A bank reconciliation statement, for example, explains why the bank balance in the balance sheet (per books) differs from the bank statement balance — it is a supporting schedule that validates the balance sheet figure, not an alternative to it.",
          "article": "What Is a Reconciliation Statement? Definition and Types for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-a-reconciliation-statement"
        },
        {
          "q": "How long should reconciliation statements be retained?",
          "a": "For bank and statutory reconciliation in India, the standard retention period is 6 years. The Income Tax Act permits assessment or reassessment up to 6 years from the end of the relevant assessment year in standard cases and up to 10 years in cases involving income escaping assessment above Rs 50 lakh. ICAI's auditing standards require that audit evidence, including reconciliation statements that support financial statement balances, be retained for at least 7 years after the audit report date. Companies Act, 2013 (Section 128) requires books of account to be preserved for 8 years from the end of the financial year. In practice, 8 years is the safe retention period for all reconciliation documents.",
          "article": "What Is a Reconciliation Statement? Definition and Types for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-a-reconciliation-statement"
        },
        {
          "q": "What makes a reconciliation statement useful for auditors?",
          "a": "An audit-ready reconciliation statement must contain four elements: (1) both source records identified by name, period, and balance — for example, 'Bank of Baroda current account statement as at 31 March 2026: Rs 14,23,450 Dr' and 'Bank of Baroda ledger as per ERP as at 31 March 2026: Rs 14,10,200 Dr'; (2) every identified difference itemised with date, description, and amount — not a net total, but individual line items; (3) the classification of each difference (timing, error, pending investigation); and (4) the name and date of approval by a responsible person. An unclassified dump of unmatched rows with a residual balance does not satisfy audit requirements. Auditors also check that items classified as timing differences in the prior period have cleared in the subsequent period.",
          "article": "What Is a Reconciliation Statement? Definition and Types for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-a-reconciliation-statement"
        },
        {
          "q": "What is automated reconciliation software?",
          "a": "Software that ingests financial records from two or more sources — bank statements, ERP ledgers, gateway settlement files, GSTR-2B, Form 26AS — applies configurable matching rules, identifies matches and exceptions, classifies exceptions by variance type, and presents a structured queue for exception resolution. Configuration is done through rule setup rather than code development.",
          "article": "What Is Automated Reconciliation? How It Differs from Manual Matching",
          "url": "https://www.terra-insight.com/insights/what-is-automated-reconciliation"
        },
        {
          "q": "How does automated reconciliation improve match rates?",
          "a": "Manual reconciliation typically matches on a single field — amount, or amount plus date. Automated reconciliation combines multiple identifiers in sequence: UTR (where present), reference number, counterparty name, amount, and date within a tolerance band. The most reliable identifier is tried first; confirmed matches exit the queue immediately. This approach improved match rates from 51% to 88% on comparable datasets, reducing unmatched exception queues by more than a third and cutting the time finance teams spend on manual follow-up.",
          "article": "What Is Automated Reconciliation? How It Differs from Manual Matching",
          "url": "https://www.terra-insight.com/insights/what-is-automated-reconciliation"
        },
        {
          "q": "What is a tolerance band in reconciliation software?",
          "a": "A configured acceptable difference between two matched amounts. For example, ±₹10 for rounding differences in TDS matching (where tax is computed to paisa but rounded to rupee), or 5% tolerance for high-confidence UTR matches where MDR deductions create a predictable variance. Without tolerance bands, legitimate matches are rejected as mismatches, inflating the exception queue artificially.",
          "article": "What Is Automated Reconciliation? How It Differs from Manual Matching",
          "url": "https://www.terra-insight.com/insights/what-is-automated-reconciliation"
        },
        {
          "q": "How long does automated reconciliation take to implement?",
          "a": "Typically 2 to 4 weeks: week 1 is ERP field mapping and matching rule configuration; week 2 is integration testing with live data; week 3 is parallel run alongside the existing manual process; week 4 is production cutover and sign-off. No code development is required — implementation is configuration of ingestion formats, matching rules, and tolerance bands.",
          "article": "What Is Automated Reconciliation? How It Differs from Manual Matching",
          "url": "https://www.terra-insight.com/insights/what-is-automated-reconciliation"
        },
        {
          "q": "When does automated reconciliation justify the cost?",
          "a": "Above 10,000 transactions per month across multiple data sources, when manual reconciliation regularly produces more than 10% unmatched exceptions, or when TDS, GST, or NACH compliance creates quarterly bottlenecks that delay return filings. The break-even point for most Indian mid-market organisations is approximately 3 to 6 months based on reduction in finance team hours spent on matching and exception follow-up.",
          "article": "What Is Automated Reconciliation? How It Differs from Manual Matching",
          "url": "https://www.terra-insight.com/insights/what-is-automated-reconciliation"
        },
        {
          "q": "What is the difference between bank reconciliation and bookkeeping?",
          "a": "Bookkeeping is the recording of transactions in the company's ledger as they occur. Bank reconciliation is a separate control process that compares those recorded entries against what the bank has actually processed and reported. Bookkeeping captures timing; bank reconciliation verifies that the timing differences are expected and that no transactions have been missed, duplicated, or incorrectly recorded. The two processes are sequential — you cannot reconcile what has not been booked.",
          "article": "What Is Bank Reconciliation? Definition and Process for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-bank-reconciliation"
        },
        {
          "q": "How often should bank reconciliation be done?",
          "a": "For high-volume accounts — those receiving daily payment gateway settlements, NACH batch credits, or bulk vendor payment debits — daily reconciliation is standard practice. For accounts with moderate transaction volume (100–500 entries per month), weekly reconciliation is sufficient to keep the exception queue manageable. Monthly reconciliation is the regulatory minimum for statutory audit evidence. Enterprises with 5 or more bank accounts typically run reconciliation daily for operating accounts and weekly for payroll and escrow accounts.",
          "article": "What Is Bank Reconciliation? Definition and Process for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-bank-reconciliation"
        },
        {
          "q": "What is an outstanding cheque in bank reconciliation?",
          "a": "An outstanding cheque is a cheque that has been issued and recorded in the company's books as a payment, but has not yet been presented to the bank for clearing. It appears in the books as a credit to the bank account, but not yet as a debit in the bank statement. In India, cheques typically clear within 1–3 working days for local clearing and 1–5 working days for outstation cheques under CTS (Cheque Truncation System). Outstanding cheques older than 15 days should be investigated, as they may indicate that the cheque has been lost or that the payee has not deposited it.",
          "article": "What Is Bank Reconciliation? Definition and Process for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-bank-reconciliation"
        },
        {
          "q": "What does UTR number mean in bank reconciliation?",
          "a": "UTR stands for Unique Transaction Reference. For NEFT transactions, it is a 22-character alphanumeric code (e.g., HDFC226051234567890123). For RTGS transactions, it is a 22-character reference in a different format. For IMPS, a 12-digit reference number is used. In bank reconciliation, the UTR is the primary matching key for electronic fund transfers — matching the UTR from the bank statement against the UTR captured in the ERP's payment entry resolves the majority of electronic payment reconciliation items. Where the UTR is not captured at the time of booking (a common ERP data quality issue), secondary matching on amount plus date plus counterparty is required.",
          "article": "What Is Bank Reconciliation? Definition and Process for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-bank-reconciliation"
        },
        {
          "q": "When does bank reconciliation become too complex for Excel?",
          "a": "Excel-based bank reconciliation reaches its practical limit at approximately 500 transactions per month across multiple bank accounts. Beyond this threshold, the combination of manual copy-paste data preparation, VLOOKUP-based matching that fails on partial references, the absence of NACH batch grouping logic, and the inability to handle TDS deduction entries alongside payment entries makes the process error-prone and time-consuming. Organisations with multiple bank accounts, payment gateway settlement files, NACH mandates, and TDS entries in the same reconciliation cycle consistently report that Excel-based processes take 5–10 staff days per month and still leave a residual unmatched population that carries forward indefinitely.",
          "article": "What Is Bank Reconciliation? Definition and Process for Indian Finance Teams",
          "url": "https://www.terra-insight.com/insights/what-is-bank-reconciliation"
        },
        {
          "q": "What is Form 26AS used for?",
          "a": "Form 26AS serves three primary purposes in Indian enterprise finance. First, it is used to claim TDS credit when filing the income tax return — the credit claimed in the ITR must match what appears in Form 26AS, or the return will be processed with a demand. Second, it is used to reconcile the TDS receivable ledger in the company's ERP against the credits actually deposited by deductors — any entry in the TDS receivable ledger that does not appear in Form 26AS represents either a deposit error or a PAN mismatch to be resolved. Third, it serves as a compliance verification tool — the company can check whether all its customers and vendors who are required to deduct TDS have done so and filed returns correctly.",
          "article": "What Is Form 26AS? The Tax Credit Statement Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-form-26as"
        },
        {
          "q": "How do I download Form 26AS?",
          "a": "Form 26AS can be downloaded from the TRACES portal at www.tdscpc.gov.in by logging in with the PAN and date of birth or date of incorporation. It is also accessible through the Income Tax e-filing portal at incometax.gov.in. For enterprise use, TRACES allows bulk download of Form 26AS in text format, which can be imported into a reconciliation system for matching. The download covers a full financial year (April to March) and is available in HTML, text, or PDF format depending on the portal used.",
          "article": "What Is Form 26AS? The Tax Credit Statement Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-form-26as"
        },
        {
          "q": "How often is Form 26AS updated?",
          "a": "Form 26AS is updated within 3–7 working days after a TDS challan is processed by the bank and the data flows through the TIN (Tax Information Network). When a deductor files a quarterly TDS return, the deductee-level details — PAN, amount, section, quarter — are updated in Form 26AS within 7–10 working days after the return is processed by the TDS CPC. This means that for the January–March quarter, whose return is due by 15 May, the Form 26AS credits may not fully stabilise until late May or early June — a timing consideration for companies that begin ITR preparation in April.",
          "article": "What Is Form 26AS? The Tax Credit Statement Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-form-26as"
        },
        {
          "q": "What is the difference between Form 26AS and AIS?",
          "a": "Form 26AS (Annual Tax Credit Statement) shows TDS by deductor at quarterly aggregation level — it tells you how much TDS a specific TAN deducted from you in a specific quarter under a specific section. AIS (Annual Information Statement), introduced in 2021 and accessible from the Income Tax e-filing portal, is more granular. AIS includes transaction-level details: individual interest credits from banks, dividend payments, purchase and sale of securities, mutual fund transactions, and foreign remittances — all reported to the Income Tax Department by the respective institutions. For TDS reconciliation, Form 26AS remains the primary document. AIS is used for verifying the completeness of income disclosure in the ITR.",
          "article": "What Is Form 26AS? The Tax Credit Statement Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-form-26as"
        },
        {
          "q": "What should I do if TDS is missing from Form 26AS?",
          "a": "If a TDS entry appears in the company's books as a receivable but is absent from Form 26AS, there are three possible causes: (1) the deductor has not yet deposited the TDS (challan not filed) — the deductee should contact the deductor and request evidence of challan payment; (2) the deductor has deposited but not yet filed the quarterly return — the credit will appear after the return is filed and processed; (3) the deductor filed the return with an incorrect PAN for the deductee — a TRACES correction return (Form 26A or Form 15G amendment) is required. Once the correction return is filed and processed, the credit will appear in the deductee's Form 26AS within 7–10 working days. The deductee cannot correct Form 26AS directly — the correction must come from the deductor.",
          "article": "What Is Form 26AS? The Tax Credit Statement Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-form-26as"
        },
        {
          "q": "What is the difference between GSTR-2A and GSTR-2B?",
          "a": "GSTR-2A is a dynamic, continuously updated statement that reflects all inward supply details reported by suppliers in real time as they file their GSTR-1 or IFF (Invoice Furnishing Facility). It updates every time a supplier files a return, which means it changes throughout the month. GSTR-2B is a static monthly snapshot taken on the 12th-14th of the following month, covering only invoices filed by suppliers up to the GSTR-1 filing deadline for that period. From a compliance perspective, GSTR-2B is the operative document: under Rule 36(4) as amended from January 2022, ITC can only be claimed to the extent it appears in GSTR-2B for that month. GSTR-2A is useful for monitoring supplier filing behaviour during the month; GSTR-2B determines what ITC can actually be claimed.",
          "article": "What Is GSTR-2B? The Auto-Populated ITC Statement Explained",
          "url": "https://www.terra-insight.com/insights/what-is-gstr-2b"
        },
        {
          "q": "When is GSTR-2B available?",
          "a": "GSTR-2B for a given month is available from the 12th to 14th of the following month, after the GSTR-1 filing deadline has passed (11th of the following month for monthly filers). For taxpayers under the QRMP scheme (Quarterly Return Monthly Payment), who file GSTR-1 quarterly, GSTR-2B reflects the invoices reported by their quarterly-filing suppliers in the IFF (for months 1 and 2) and in the full GSTR-1 (for month 3). The statement is available for download in JSON or Excel format from the GST portal at www.gst.gov.in.",
          "article": "What Is GSTR-2B? The Auto-Populated ITC Statement Explained",
          "url": "https://www.terra-insight.com/insights/what-is-gstr-2b"
        },
        {
          "q": "Can I claim ITC not appearing in GSTR-2B?",
          "a": "No. Under Rule 36(4) of the CGST Rules, as amended with effect from 1 January 2022, ITC is restricted to the amount reflected in GSTR-2B for the period. The earlier provision allowing 5% provisional ITC over and above GSTR-2A (and subsequently GSTR-2B) was removed. If a supplier's invoice does not appear in GSTR-2B for the current month because the supplier filed GSTR-1 late, the ITC on that invoice will only be available in the GSTR-2B of the month in which the supplier eventually files the return — which may be the next month or later.",
          "article": "What Is GSTR-2B? The Auto-Populated ITC Statement Explained",
          "url": "https://www.terra-insight.com/insights/what-is-gstr-2b"
        },
        {
          "q": "What should I do if a supplier's invoice doesn't appear in GSTR-2B?",
          "a": "If an invoice is in the purchase register but absent from GSTR-2B, the supplier has not yet filed GSTR-1 for the period. The steps are: (1) contact the supplier and confirm the GSTIN and invoice details are correct; (2) request the supplier to file their GSTR-1, which will make the invoice appear in the next month's GSTR-2B; (3) do not claim ITC on the invoice until it appears in GSTR-2B; (4) if the supplier files a late return with an amended invoice number or GSTIN, reconcile the amended version when it appears. Repeatedly late suppliers create a systematic ITC delay that accumulates over multiple periods and should be flagged for vendor compliance review.",
          "article": "What Is GSTR-2B? The Auto-Populated ITC Statement Explained",
          "url": "https://www.terra-insight.com/insights/what-is-gstr-2b"
        },
        {
          "q": "How do I reconcile GSTR-2B with my purchase register?",
          "a": "Download GSTR-2B from the GST portal in JSON or Excel format. Export the purchase register from your ERP for the same period. Match each entry on GSTIN of the supplier, invoice number, invoice date, and taxable amount. A tolerance of Rs 1–2 on the tax amount accounts for rounding differences. Classify unmatched items into: (1) in purchase register but not in GSTR-2B — supplier has not filed; (2) in GSTR-2B but not in purchase register — invoice not received or not booked; (3) amount mismatch — supplier filed a different invoice amount; (4) GSTIN mismatch — supplier filed under a different GSTIN than what is on the invoice. Each category requires a different resolution path. For high-volume operations above 500 invoices per month, manual VLOOKUP-based matching is not reliable and purpose-built GSTR-2B reconciliation software is required.",
          "article": "What Is GSTR-2B? The Auto-Populated ITC Statement Explained",
          "url": "https://www.terra-insight.com/insights/what-is-gstr-2b"
        },
        {
          "q": "What are the conditions for claiming ITC in GST?",
          "a": "There are four conditions: (1) the supplier has filed GSTR-1 and the invoice appears in the buyer's GSTR-2B; (2) the buyer holds a valid tax invoice or debit note; (3) goods or services have been received; and (4) the GST amount has been paid to the supplier within 180 days of the invoice date. If payment is not made within 180 days, the ITC previously claimed must be reversed along with interest at 18% per annum.",
          "article": "What Is ITC in GST? Input Tax Credit Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-itc-in-gst"
        },
        {
          "q": "What is blocked ITC under Section 17(5)?",
          "a": "Section 17(5) lists categories where ITC is NOT available even if GST was paid: motor vehicles for personal use, food and outdoor catering, beauty treatment, club memberships, life and health insurance (unless mandatory for employees), and works contract services for immovable property. These blocks apply regardless of whether the invoice appears in GSTR-2B.",
          "article": "What Is ITC in GST? Input Tax Credit Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-itc-in-gst"
        },
        {
          "q": "What happens if ITC is claimed beyond GSTR-2B amounts?",
          "a": "Under Rule 36(4), ITC in excess of GSTR-2B is subject to reversal. The tax officer can raise a demand notice under Section 73 or 74, and interest at 18% per annum accrues from the date of the wrongful claim. In cases of fraud or deliberate suppression, a penalty equal to the ITC amount can be levied under Section 74.",
          "article": "What Is ITC in GST? Input Tax Credit Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-itc-in-gst"
        },
        {
          "q": "Can ITC be claimed on capital goods?",
          "a": "Yes. ITC on capital goods (machinery, equipment, computers) is fully available if the asset is used exclusively for taxable supply and the invoice appears in GSTR-2B. If the capital good is used partly for exempt supply, ITC must be proportionately reversed under Rule 42 and Rule 43 over the useful life of the asset.",
          "article": "What Is ITC in GST? Input Tax Credit Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-itc-in-gst"
        },
        {
          "q": "What is the time limit for claiming ITC?",
          "a": "ITC for a financial year must be claimed by the earlier of: 30 November of the following financial year, or the date of filing the annual return (GSTR-9) for that year. After this deadline, the ITC lapses permanently and cannot be carried forward. This makes timely GSTR-2B reconciliation each month critical for large buyer organisations.",
          "article": "What Is ITC in GST? Input Tax Credit Explained for Indian Businesses",
          "url": "https://www.terra-insight.com/insights/what-is-itc-in-gst"
        },
        {
          "q": "What is NACH debit?",
          "a": "NACH Debit is used by institutions — NBFCs, banks, insurance companies — to collect recurring payments from customers' accounts, such as EMI, insurance premium, or SIP contributions, after the customer has registered a standing mandate. The institution submits a batch debit file through its sponsor bank to NPCI, which routes debits to destination banks.",
          "article": "What Is NACH in Banking? National Automated Clearing House Explained",
          "url": "https://www.terra-insight.com/insights/what-is-nach"
        },
        {
          "q": "What is the difference between NACH and ECS?",
          "a": "ECS (Electronic Clearing Service) was managed individually by each RBI regional office and participating bank. NACH replaced it with a centralised clearing hub at NPCI, a standardised XML-based file format, UMRN-based mandate tracking, and faster T+1 settlement. Disputes and return handling that previously required bilateral bank coordination now follow a uniform NPCI process.",
          "article": "What Is NACH in Banking? National Automated Clearing House Explained",
          "url": "https://www.terra-insight.com/insights/what-is-nach"
        },
        {
          "q": "What is a NACH mandate?",
          "a": "A NACH mandate is a standing instruction registered by an account holder authorising a specific institution to debit their account on a recurring basis — for a defined amount, frequency, and period. Each mandate is assigned a UMRN (Unique Mandate Reference Number) by NPCI, which becomes the tracking identifier for all debits and returns under that instruction.",
          "article": "What Is NACH in Banking? National Automated Clearing House Explained",
          "url": "https://www.terra-insight.com/insights/what-is-nach"
        },
        {
          "q": "What does NACH return code 01 mean?",
          "a": "Return code 01 means insufficient funds in the account at the time of the debit attempt. The transaction is reversed to the sponsor bank, and the presenting institution must follow up with the borrower or policyholder. Repeated return code 01 occurrences on the same UMRN may trigger mandate suspension depending on lender policy.",
          "article": "What Is NACH in Banking? National Automated Clearing House Explained",
          "url": "https://www.terra-insight.com/insights/what-is-nach"
        },
        {
          "q": "Who uses NACH in India?",
          "a": "NACH is used by NBFCs and banks for EMI collection on personal, home, and auto loans; by insurance companies for recurring premium collection; by mutual funds for SIP debits; and by the government for direct benefit transfers and salary disbursements via NACH Credit. Most institutions processing more than 500 recurring transactions per month operate through NACH.",
          "article": "What Is NACH in Banking? National Automated Clearing House Explained",
          "url": "https://www.terra-insight.com/insights/what-is-nach"
        },
        {
          "q": "What is MDR in payment gateway settlement?",
          "a": "MDR (Merchant Discount Rate) is the processing fee charged by the gateway on each transaction, deducted before the settlement amount is transferred to the merchant. MDR is 0% for UPI transactions (government mandate), 1.5–2% for domestic debit cards, and 2.5–3.5% for international credit cards. GST at 18% is levied on MDR; this GST component is ITC-eligible for GST-registered merchants.",
          "article": "What Is a Payment Gateway Settlement? How Online Payments Reach Your Bank Account",
          "url": "https://www.terra-insight.com/insights/what-is-payment-gateway-settlement"
        },
        {
          "q": "How long does Razorpay settlement take?",
          "a": "Razorpay's standard settlement cycle is T+2 — two working days after the payment capture date. Merchants with strong transaction history and no chargeback issues may qualify for T+1 settlement. Refunds are settled separately and typically take T+5 to T+7 to reflect in the bank account, appearing as a deduction from a future settlement batch rather than a separate credit.",
          "article": "What Is a Payment Gateway Settlement? How Online Payments Reach Your Bank Account",
          "url": "https://www.terra-insight.com/insights/what-is-payment-gateway-settlement"
        },
        {
          "q": "What is the settlement file from a payment gateway?",
          "a": "The settlement file is a structured report — typically CSV or Excel — provided by the gateway for each settlement batch. It contains the individual transaction amounts, deductions (MDR, GST on MDR, refunds, chargebacks, fees), and the net settlement amount transferred. The settlement file is the primary document for matching the NEFT bank credit to individual order records in the order management system.",
          "article": "What Is a Payment Gateway Settlement? How Online Payments Reach Your Bank Account",
          "url": "https://www.terra-insight.com/insights/what-is-payment-gateway-settlement"
        },
        {
          "q": "What is TCS in online marketplace settlements?",
          "a": "TCS (Tax Collected at Source) at 1% of net order value is deducted by e-commerce operators — Amazon, Flipkart, Meesho, Myntra — on every seller payout under Section 52 of the CGST Act. This TCS appears in the seller's Form 26AS (Part A-I) and GSTR-2A and is creditable against the seller's GST output liability. Sellers must reconcile TCS deducted in settlement files against Form 26AS amounts quarterly.",
          "article": "What Is a Payment Gateway Settlement? How Online Payments Reach Your Bank Account",
          "url": "https://www.terra-insight.com/insights/what-is-payment-gateway-settlement"
        },
        {
          "q": "How do I reconcile payment gateway settlements?",
          "a": "The reconciliation has two stages: (1) match the net NEFT credit in the bank statement to the settlement batch in the gateway settlement file, using settlement ID or settlement date as the match key; (2) match each transaction in the settlement file to the corresponding order in the order management system using Order ID or Payment ID. Deductions — MDR, TCS, refunds — must be classified separately to ensure the gross-to-net bridge is fully accounted for.",
          "article": "What Is a Payment Gateway Settlement? How Online Payments Reach Your Bank Account",
          "url": "https://www.terra-insight.com/insights/what-is-payment-gateway-settlement"
        },
        {
          "q": "What is TDS and who deducts it?",
          "a": "TDS (Tax Deducted at Source) is a withholding tax mechanism under the Income Tax Act, 1961. The entity making a payment — the deductor — deducts a specified percentage of the payment amount before crediting the payee (the deductee). The deductor deposits the deducted amount to the government using ITNS Challan 281, quoting the deductor's TAN (Tax Deduction Account Number) and the deductee's PAN. The deductor then submits a quarterly TDS return (Form 26Q for non-salary, Form 24Q for salary), after which the deductee can see the credit in Form 26AS and claim it in the income tax return.",
          "article": "What Is TDS Deduction? How Tax Deducted at Source Works in India",
          "url": "https://www.terra-insight.com/insights/what-is-tds-deduction"
        },
        {
          "q": "What is the TDS rate under Section 194J?",
          "a": "Section 194J covers fees for professional or technical services. The rate is 10% for professional services (lawyers, doctors, architects, management consultants) and 2% for technical services where the payment is for a notified category of technical services. The threshold below which TDS is not required is Rs 30,000 per financial year per payee. From April 2020, the rate for call centre operations was reduced to 2%, and for royalties to 10%. The applicable rate depends on the nature of service and must be verified against the current notification, as rates have been amended several times.",
          "article": "What Is TDS Deduction? How Tax Deducted at Source Works in India",
          "url": "https://www.terra-insight.com/insights/what-is-tds-deduction"
        },
        {
          "q": "What is the TDS deposit deadline?",
          "a": "The standard TDS deposit deadline is the 7th of the month following the month of deduction. For example, TDS deducted in January must be deposited by 7 February. The exception is March: TDS deducted in March must be deposited by 30 April. Failure to deposit on time attracts simple interest at 1.5% per month (or part of month) from the date of deduction to the date of deposit. Late deposit is an offence under Section 276B and can attract prosecution in addition to interest. Late filing of the quarterly return attracts a fee of Rs 200 per day under Section 234E, up to the TDS amount.",
          "article": "What Is TDS Deduction? How Tax Deducted at Source Works in India",
          "url": "https://www.terra-insight.com/insights/what-is-tds-deduction"
        },
        {
          "q": "What is the difference between TDS and TCS?",
          "a": "TDS (Tax Deducted at Source) is deducted by the payer at the time of making payment to the payee. TCS (Tax Collected at Source) is collected by the seller from the buyer at the time of sale. Section 206C covers TCS on sale of specified goods (scrap, tendu leaves, timber, minerals). Section 52 of the GST Act and Section 194-O of the Income Tax Act extend TCS obligations to e-commerce operators collecting payments on behalf of sellers. TCS is deposited by the seller/platform, not the buyer, which is the structural difference from TDS. Both TDS and TCS are visible in the deductee's or collectee's Form 26AS.",
          "article": "What Is TDS Deduction? How Tax Deducted at Source Works in India",
          "url": "https://www.terra-insight.com/insights/what-is-tds-deduction"
        },
        {
          "q": "How do I reconcile TDS with Form 26AS?",
          "a": "Download Form 26AS from the TRACES portal (www.tdscpc.gov.in) for the relevant financial year. Export the TDS receivable ledger from your ERP for the same period. Match each entry in the TDS receivable ledger against Part A1 of Form 26AS by TAN of deductor, quarter of deduction, and section code. Where an entry appears in the TDS receivable ledger but not in Form 26AS, the deductor has either not deposited the TDS or has filed the return with an incorrect PAN for the deductee. Classify each mismatch using variance codes: PAN_MISMATCH (deductor filed with wrong PAN), NOT_DEPOSITED (challan not filed), QUARTER_ERROR (deducted in one quarter but filed in another), or RATE_DIFFERENCE (deducted at a different rate than expected). For PAN_MISMATCH and QUARTER_ERROR, the deductor must file a correction return on TRACES.",
          "article": "What Is TDS Deduction? How Tax Deducted at Source Works in India",
          "url": "https://www.terra-insight.com/insights/what-is-tds-deduction"
        },
        {
          "q": "What is a UTR number in NEFT?",
          "a": "UTR for NEFT is a 22-character reference. The first 4 characters are the remitting bank's IFSC code, followed by a sequence code encoding the year, month, day, and transaction number for that batch. The UTR is visible in the bank statement under the transaction narration, typically in the format: NEFT/[UTR]/[sender name].",
          "article": "What Is a UTR Number? Unique Transaction Reference in Indian Banking",
          "url": "https://www.terra-insight.com/insights/what-is-utr-number"
        },
        {
          "q": "Is UTR the same as transaction ID?",
          "a": "No. UTR is assigned by the payment clearing system — NEFT, RTGS, or IMPS infrastructure — and is the same reference visible to both the sending and receiving bank. Transaction ID is assigned by your bank or mobile application and is internal to that institution. UTR is the interbank-level reference used to trace or dispute a payment; transaction ID cannot be used for this.",
          "article": "What Is a UTR Number? Unique Transaction Reference in Indian Banking",
          "url": "https://www.terra-insight.com/insights/what-is-utr-number"
        },
        {
          "q": "Why is UTR important in bank reconciliation?",
          "a": "UTR is the primary match key for reconciling bank statement credits to ERP ledger entries. When UTR is available on both sides of the match, a single-field lookup produces a deterministic result. Without UTR, the system must match on amount plus approximate date plus counterparty name — a combination that produces far more ambiguous matches and false positives, particularly when multiple same-amount payments arrive from the same sender in the same week.",
          "article": "What Is a UTR Number? Unique Transaction Reference in Indian Banking",
          "url": "https://www.terra-insight.com/insights/what-is-utr-number"
        },
        {
          "q": "How long does it take for a NEFT UTR to appear in the recipient's bank statement?",
          "a": "NEFT settles in half-hourly batches between 8 AM and 7 PM on business days. The UTR typically appears in the recipient's account statement within 30 to 120 minutes of transfer initiation, depending on batch timing and destination bank processing. Transfers initiated after 7 PM are held for the next business day's first batch.",
          "article": "What Is a UTR Number? Unique Transaction Reference in Indian Banking",
          "url": "https://www.terra-insight.com/insights/what-is-utr-number"
        },
        {
          "q": "What should I do if a UTR number is missing from a reconciliation entry?",
          "a": "First, check whether the ERP captured the full bank narration from the bank statement import — many systems truncate narration fields. If missing, log into the bank portal and retrieve the UTR from full transaction history. As a fallback, match manually on amount, date, and sender name, then update the ERP entry with the UTR before closing the period. Persistent UTR gaps indicate a narration field-width issue in the ERP data mapping.",
          "article": "What Is a UTR Number? Unique Transaction Reference in Indian Banking",
          "url": "https://www.terra-insight.com/insights/what-is-utr-number"
        }
      ]
    }
  }
}