{
  "title": "Bookkeeping invoice, credit and receipt matching data for AI",
  "source_page": "https://fiund.com/industries/bookkeeping-invoice-credit-match-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A duplicated receipt must be counted once against its named invoice",
    "context": "Original fictional invoices use abstract currency units and explicit document references. The exercise reconciles source records without bank credentials, real books or posting transactions.",
    "records": [
      [
        "BK1",
        "Dummy invoices",
        "Invoice I10=100 units; invoice I01=100. Distinct references despite same total."
      ],
      [
        "BK2",
        "Supplier credit",
        "Credit C1=20 explicitly applies to I10 only."
      ],
      [
        "BK3",
        "Receipt exports",
        "Receipt R1=80 explicitly applies to I10; the same R1 appears in two exports. No other receipt or I01 credit supplied."
      ]
    ],
    "question": "What open balances are supported, and does the second exported R1 or matching invoice amount justify another payment or match?",
    "answer": "BK2 and BK3 support I10's balance as 100−20−80=0, counting R1 once despite its duplicated export. I01 remains 100 with no supplied credit or receipt. Equal invoice totals do not override the explicit references, and a second representation of R1 is not another payment. Cite document identity and allocation evidence for the calculation without posting any entry or inferring missing cash movements.",
    "failureModes": [
      "Counting duplicate receipt exports as two payments.",
      "Applying an I10-specific credit or payment to I01 because their original totals match."
    ],
    "fields": [
      [
        "Invoice and source-document ID",
        "Defines the matching key."
      ],
      [
        "Credit and receipt allocation",
        "Makes balance arithmetic traceable."
      ],
      [
        "Duplicate identity across exports",
        "Prevents double-counted movements."
      ]
    ],
    "holdout": "Remove R1's invoice reference in a new case while leaving both equal-value invoices. Require an unresolved allocation rather than repeating the earlier match by amount.",
    "boundary": "Use independently authored records. Exclude real customers, suppliers, payment credentials and accounting-software screenshots."
  }
}