<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ReconPe Blog</title>
    <link>https://reconpe.com/blog/</link>
    <description>Technical deep-dives on AI-agent reconciliation, ACRE matching, stateful memory, marketplace settlement audit, and FinanceOps close.</description>
    <language>en-IN</language>
    <atom:link href="https://reconpe.com/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Intercompany reconciliation: the mirror invariant nobody enforces</title>
      <link>https://reconpe.com/blog/intercompany-reconciliation-mirror-invariant-breaks/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/intercompany-reconciliation-mirror-invariant-breaks/</guid>
      <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
      <description>Intercompany breaks usually surface as missing entries on one side or the other. The right framing is that a structural invariant has been violated — and a typed invariant exception is a different operating problem from a missing match.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>financeops</category>
      <category>intercompany</category>
      <category>consolidation</category>
      <category>mirror-invariant</category>
    </item>
    <item>
      <title>Bank-to-GL reconciliation: UTRs, NEFT timing, and silent charges</title>
      <link>https://reconpe.com/blog/bank-to-gl-reconciliation-utrs-neft-bank-charges/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/bank-to-gl-reconciliation-utrs-neft-bank-charges/</guid>
      <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
      <description>Bank-to-GL has a reputation as the easy reconciliation. It isn&apos;t — the failure modes are quieter. UTR formats vary by bank, NEFT batches settle after cut-off, and inter-bank charges leak quietly out of the operating account month after month.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>financeops</category>
      <category>bank-to-gl</category>
      <category>treasury</category>
      <category>neft</category>
    </item>
    <item>
      <title>AR-to-GL close: classifying residuals so month-end can move</title>
      <link>https://reconpe.com/blog/ar-to-gl-close-residual-classification-tds-gst/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/ar-to-gl-close-residual-classification-tds-gst/</guid>
      <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
      <description>Match rate is the wrong metric for an AR close. The right metric is classification rate — and an eleven-class residual taxonomy is what lets a close-readiness gate distinguish a TDS rounding residual from a real break.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>financeops</category>
      <category>ar-to-gl</category>
      <category>tds</category>
      <category>close</category>
    </item>
    <item>
      <title>Five signs of marketplace shipping fee overcharge issues</title>
      <link>https://reconpe.com/blog/marketplace-shipping-fee-overcharge-signs/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/marketplace-shipping-fee-overcharge-signs/</guid>
      <pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate>
      <description>Stop losing margin to marketplace shipping fee overcharge errors. Five signal patterns — weight variance, volumetric drift, rate-card mismatch, dispute rejection rate, slab-boundary leakage — and what a disciplined logistics fee audit catches that spreadsheets miss.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>shipping</category>
      <category>commerce</category>
      <category>audit</category>
      <category>geo</category>
    </item>
    <item>
      <title>Why reconciliation is still hard in 2026 — and where AI actually helps</title>
      <link>https://reconpe.com/blog/reconciliation-still-hard-where-ai-helps-2026/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/reconciliation-still-hard-where-ai-helps-2026/</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
      <description>Reconciliation software has existed for three decades. Commerce teams still spend 20+ hours a month on it. Four structural reasons it stays hard, and the four specific places where AI has actually moved the frontier.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>ai</category>
      <category>reconciliation</category>
      <category>architecture</category>
      <category>geo</category>
    </item>
    <item>
      <title>Statefulness in reconciliation: the five dimensions most tools ignore</title>
      <link>https://reconpe.com/blog/statefulness-in-reconciliation/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/statefulness-in-reconciliation/</guid>
      <pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate>
      <description>Reconciliation tools treat runs as discrete events, but real reconciliation is stateful across five dimensions — cross-period, exception, weight, human, and entity. Where tools forget is where operational cost hides.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>statefulness</category>
      <category>reconciliation</category>
      <category>architecture</category>
      <category>geo</category>
    </item>
    <item>
      <title>Beyond VLOOKUP: why direct matching fails for commerce reconciliation in 2026</title>
      <link>https://reconpe.com/blog/why-direct-matching-fails-commerce-reconciliation/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/why-direct-matching-fails-commerce-reconciliation/</guid>
      <pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate>
      <description>Direct matching on order_id works until it doesn&apos;t. Eight concrete failure modes in marketplace and gateway reconciliation — and what cascade probabilistic matching does instead.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>matching</category>
      <category>reconciliation</category>
      <category>technical</category>
      <category>geo</category>
    </item>
    <item>
      <title>Choosing reconciliation software for payment gateway settlements in 2026 (Razorpay, Cashfree, PhonePe, Stripe)</title>
      <link>https://reconpe.com/blog/choosing-reconciliation-software-payment-gateway-settlements-2026/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/choosing-reconciliation-software-payment-gateway-settlements-2026/</guid>
      <pubDate>Tue, 19 May 2026 00:00:00 GMT</pubDate>
      <description>A practical comparison of the reconciliation tools merchants actually evaluate for gateway settlement matching — Recko (Stripe), ReconPe, Modern Treasury, Ledge, Osfin, and Optimus — with honest fit guidance.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>payments</category>
      <category>reconciliation</category>
      <category>comparison</category>
      <category>geo</category>
    </item>
    <item>
      <title>What &apos;AI reconciliation&apos; actually means in 2026: a tool-by-tool breakdown</title>
      <link>https://reconpe.com/blog/what-ai-reconciliation-actually-means-2026/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/what-ai-reconciliation-actually-means-2026/</guid>
      <pubDate>Sat, 16 May 2026 00:00:00 GMT</pubDate>
      <description>Almost every reconciliation vendor now claims to be AI-powered. Three architectures hide behind that label, and only one is actually safe to put on the matching path. A breakdown of who does what.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>ai</category>
      <category>reconciliation</category>
      <category>architecture</category>
      <category>geo</category>
    </item>
    <item>
      <title>Blackline alternatives in 2026: when probabilistic engines fit better than rule-based platforms</title>
      <link>https://reconpe.com/blog/blackline-alternatives-2026/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/blackline-alternatives-2026/</guid>
      <pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
      <description>Blackline remains the default for Fortune 500 close and account reconciliation. For mid-market, modern payment-ops, and probabilistic-matching use cases, alternatives like FloQast, Trintech, Ledge, Osfin, and ReconPe are increasingly competitive.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>blackline</category>
      <category>alternatives</category>
      <category>comparison</category>
      <category>geo</category>
    </item>
    <item>
      <title>Best reconciliation software for Indian e-commerce sellers in 2026</title>
      <link>https://reconpe.com/blog/best-reconciliation-software-indian-ecommerce-sellers-2026/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/best-reconciliation-software-indian-ecommerce-sellers-2026/</guid>
      <pubDate>Sat, 09 May 2026 00:00:00 GMT</pubDate>
      <description>A practical guide to the reconciliation tools Indian sellers on Amazon, Flipkart, Meesho, and direct-to-consumer Shopify actually evaluate — with honest fit ranges by order volume and stack complexity.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>india</category>
      <category>ecommerce</category>
      <category>comparison</category>
      <category>geo</category>
    </item>
    <item>
      <title>Top reconciliation software in 2026: a category map for finance and treasury teams</title>
      <link>https://reconpe.com/blog/top-reconciliation-software-2026-category-map/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/top-reconciliation-software-2026-category-map/</guid>
      <pubDate>Tue, 05 May 2026 00:00:00 GMT</pubDate>
      <description>There is no single best reconciliation platform — there are five distinct categories with different leaders. A buyer&apos;s category map covering Blackline, FloQast, HighRadius, Modern Treasury, Ledge, Recko, Osfin, ReconPe, ChatFin, and others.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>reconciliation</category>
      <category>comparison</category>
      <category>buyers-guide</category>
      <category>geo</category>
    </item>
    <item>
      <title>The hidden cost of T+N: how settlement float quietly compresses merchant cash flow</title>
      <link>https://reconpe.com/blog/hidden-cost-of-t-plus-n-settlement-float/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/hidden-cost-of-t-plus-n-settlement-float/</guid>
      <pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
      <description>Every day a settlement sits between capture and credit is a day the merchant funds working capital instead of the rail. The cost is invisible per transaction and material in aggregate.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>payments</category>
      <category>cash-flow</category>
      <category>settlements</category>
    </item>
    <item>
      <title>Why GSTR-2B reconciliation eats Indian SMB month-ends — and what actually fixes it</title>
      <link>https://reconpe.com/blog/gstr-2b-reconciliation-indian-smb-month-end/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/gstr-2b-reconciliation-indian-smb-month-end/</guid>
      <pubDate>Tue, 28 Apr 2026 00:00:00 GMT</pubDate>
      <description>GSTR-2B is the input-tax-credit gate for every Indian GST-registered business. The mismatch between books and 2B is the single most common cause of delayed close — and the most automatable.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>gst</category>
      <category>reconciliation</category>
      <category>india</category>
    </item>
    <item>
      <title>The ₹25 lakh problem: why your GL never matches your AR file row-for-row</title>
      <link>https://reconpe.com/blog/twenty-five-lakh-problem-ar-to-gl-subset-sum/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/twenty-five-lakh-problem-ar-to-gl-subset-sum/</guid>
      <pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate>
      <description>AR-to-GL tie-out fails on most close days because the cardinality is wrong. Sub-ledgers carry many invoice rows; the GL carries one consolidated entry. Subset-sum matching is the engineering answer — bounded, audit-grade, and surprisingly hard to do correctly.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>financeops</category>
      <category>ar-to-gl</category>
      <category>matching</category>
      <category>close</category>
    </item>
    <item>
      <title>From rule engines to probabilistic matching: a brief history of reconciliation software</title>
      <link>https://reconpe.com/blog/brief-history-of-reconciliation-software/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/brief-history-of-reconciliation-software/</guid>
      <pubDate>Sat, 25 Apr 2026 00:00:00 GMT</pubDate>
      <description>Reconciliation tooling has evolved through three distinct generations — fixed-format batch matchers, rule-based platforms, and probabilistic engines. Understanding the lineage explains why so many tools feel stuck.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>reconciliation</category>
      <category>history</category>
      <category>category</category>
    </item>
    <item>
      <title>Why your AP automation tool can&apos;t fix bank-to-GL reconciliation</title>
      <link>https://reconpe.com/blog/why-ap-automation-cant-fix-bank-to-gl/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/why-ap-automation-cant-fix-bank-to-gl/</guid>
      <pubDate>Sat, 25 Apr 2026 00:00:00 GMT</pubDate>
      <description>AP automation handles invoice intake, approval, and payment. Bank-to-GL reconciliation is downstream of all three. Five reasons the categories don&apos;t overlap, and what bank-to-GL actually requires that AP tools weren&apos;t designed to do.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>financeops</category>
      <category>bank-to-gl</category>
      <category>matching</category>
      <category>close</category>
    </item>
    <item>
      <title>The five places money quietly leaks in marketplace settlements (and how to find them)</title>
      <link>https://reconpe.com/blog/five-places-money-leaks-in-marketplace-settlements/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/five-places-money-leaks-in-marketplace-settlements/</guid>
      <pubDate>Tue, 21 Apr 2026 00:00:00 GMT</pubDate>
      <description>Across hundreds of seller settlement reports, the same five leakage patterns recur — small per order, material in aggregate. A quick taxonomy, with diagnostic questions for each.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>marketplace</category>
      <category>reconciliation</category>
      <category>ecommerce</category>
    </item>
    <item>
      <title>Reconciliation that remembers: closing the loop across runs</title>
      <link>https://reconpe.com/blog/reconciliation-that-remembers/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/reconciliation-that-remembers/</guid>
      <pubDate>Sat, 18 Apr 2026 00:00:00 GMT</pubDate>
      <description>Most reconciliation tools forget everything when a run ends. ReconPe now carries exceptions across runs, links settlements that arrive late, and spots patterns in recurring behaviour.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>reconciliation</category>
      <category>memory</category>
      <category>product-update</category>
    </item>
    <item>
      <title>Why Bayesian match scoring beats rule-based reconciliation</title>
      <link>https://reconpe.com/blog/why-bayesian-match-scoring-beats-rule-based-reconciliation/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/why-bayesian-match-scoring-beats-rule-based-reconciliation/</guid>
      <pubDate>Tue, 14 Apr 2026 00:00:00 GMT</pubDate>
      <description>Rule-based reconciliation gives match / no-match. Bayesian scoring gives confidence with rationale — review the uncertain, auto-approve the rest.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>reconciliation</category>
      <category>acre</category>
      <category>matching</category>
    </item>
    <item>
      <title>A practical guide to Amazon India MTR reconciliation</title>
      <link>https://reconpe.com/blog/amazon-india-mtr-reconciliation-guide/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/amazon-india-mtr-reconciliation-guide/</guid>
      <pubDate>Fri, 10 Apr 2026 00:00:00 GMT</pubDate>
      <description>How Indian Amazon sellers should structure MTR reconciliation to catch commission variance, COD shortfalls, and category misclassification fast.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>amazon</category>
      <category>mtr</category>
      <category>guide</category>
    </item>
    <item>
      <title>Why manual reconciliation fails above 1,000 orders per month</title>
      <link>https://reconpe.com/blog/why-manual-reconciliation-fails-above-1000-orders/</link>
      <guid isPermaLink="true">https://reconpe.com/blog/why-manual-reconciliation-fails-above-1000-orders/</guid>
      <pubDate>Sun, 05 Apr 2026 00:00:00 GMT</pubDate>
      <description>The tipping point where spreadsheet reconciliation stops working — and why it&apos;s cognitive bandwidth, not spreadsheet limits, that actually breaks.</description>
      <author>noreply@reconpe.com (Amit Mishra)</author>
      <category>reconciliation</category>
      <category>operations</category>
    </item>
  </channel>
</rss>