OpenChainGraph Suite · OCG v0.8.0 · Core Verify Pack

Interest Accrual Recompute

Note (dated 2026-08-17): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site.

Independently recomputes a core-system-reported interest accrual figure from the caller-declared principal, annual rate, day-count basis, and days accrued, then diffs the recomputed figure against the core's reported amount under a caller-declared variance tolerance. This chain configures the existing audit recalculation suite to its interest_accrual category only, no new kernel, no new node. The day-count/compounding convention is a contract term the caller declares for each item, never inferred or defaulted. Not core-migration and not core-replacement: this recomputes and receipts one core-reported figure against an independent arithmetic derivation.

OpenChainGraph · 1 Step attestation mandate · Linear Hash-Anchored §4 chain_depth:1 Client-Side · Zero PII
Not accounting, tax, or legal advice. This does not replace your core processor and is not an audit of your vendor. Outputs are computed from your declared inputs only. Recompute outputs require review by qualified finance staff before use in any reconciliation or disclosure.
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 1 Step · Linear
1 ROOT · TERMINAL node
Recomputes each declared interest-accrual item (principal, annual_rate_pct, days_accrued, day_count_basis) independently and diffs the result against the core-reported interest figure, flagging any variance outside the caller-declared tolerance (tolerance_abs, tolerance_pct). This chain runs the interest_accrual category only; the suite's other categories are out of scope here. Only stage.
MCP Call · run_audit_recalc_suite
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "run_audit_recalc_suite",
    "arguments": {
      "tolerance": {"abs": 0, "pct": 5},
      "interest_accrual": [
        {
          "item_id": "I-1",
          "principal": 100000,
          "annual_rate_pct": 6,
          "days_accrued": 90,
          "day_count_basis": "actual_360",
          "client_reported_interest": 1490
        }
      ]
    }
  },
  "id": 1
}
Export Chain Artifact
Download a §4-compliant chain artifact with execution hash and step definitions. Hash is deterministic over canonical {policy_parameters, output_payload} per RFC 8785/JCS.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: The client says its accruals tie. Which recomputed items still fall outside our tolerance before we sign the workpaper?
Run the AINumbers MCP tool `run_chain` with {"chain":"interest-accrual-recompute"} and read `art-463-recalc-suite.flagged_count`.
Re-run with `inputs` for `art-463-recalc-suite`, reusing the values that result echoed, with `tolerance` changed so the absolute tolerance is 6000. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/interest-accrual-recompute.html