[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739F3PXS8ADE3MDY047P7GZ":3,"skill-same:01M739F3PXS8ADE3MDY047P7GZ":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M739F3PXS8ADE3MDY047P7GZ","qbo-bank-reconciliation",null,"Matches bank transactions against the QuickBooks Online register and the petty cash log for a stated period, so cash gets reconciled first in the close instead of last. It pulls the bank side from a connected bank MCP (the financial-pulse connector pattern: Grasshopper, Mercury) or from an uploaded or pasted statement, and the QBO side through the QuickBooks Online MCP (intuit\u002Fquickbooks-online-mcp-server). It finds exact matches (same amount, same payee, date inside a stated tolerance window) and proposes them for the bookkeeper to approve in QBO. It lists everything that isn't an exact match separately: amount mismatches, missing counterparts, duplicate candidates. It writes nothing to QBO or to the bank. It's read-only by design. Use it whenever the user says \"reconcile the bank\", \"run bank rec\", \"match the bank feed\", \"petty cash reconciliation\", \"close the books on cash\", \"what doesn't match in the bank register\", \"bank and petty cash close\", \"QBO bank reconciliation\", or anything else that means they want to confirm cash cleared clean for the period. Always use this skill for QBO bank-and-petty-cash close work. Don't freehand a reconciliation without it.","skills-agents-co\u002Fskills-and-agents-library","skills-agents-co","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F299904996?v=4","01M7395V3X9YG4DAJGNX9D0AD0","Skills and Agents Co","01M7395V4JMSP2MQCZZ98KPE89",1,"MIT","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-bank-reconciliation\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: qbo-bank-reconciliation\ndescription: >\n  Matches bank transactions against the QuickBooks Online register and the\n  petty cash log for a stated period, so cash gets reconciled first in the\n  close instead of last. It pulls the bank side from a connected bank MCP\n  (the financial-pulse connector pattern: Grasshopper, Mercury) or from an\n  uploaded or pasted statement, and the QBO side through the QuickBooks\n  Online MCP (intuit\u002Fquickbooks-online-mcp-server). It finds exact matches\n  (same amount, same payee, date inside a stated tolerance window) and\n  proposes them for the bookkeeper to approve in QBO. It lists everything\n  that isn't an exact match separately: amount mismatches, missing\n  counterparts, duplicate candidates. It writes nothing to QBO or to the\n  bank. It's read-only by design. Use it whenever the user says \"reconcile\n  the bank\", \"run bank rec\", \"match the bank feed\", \"petty cash\n  reconciliation\", \"close the books on cash\", \"what doesn't match in the\n  bank register\", \"bank and petty cash close\", \"QBO bank reconciliation\",\n  or anything else that means they want to confirm cash cleared clean for\n  the period. Always use this skill for QBO bank-and-petty-cash close work.\n  Don't freehand a reconciliation without it.\nlicense: MIT\n---\n\n# QBO Bank & Petty Cash Reconciliation\n\nConfirm cash is clean for the period: match the bank feed and petty cash log\nagainst the QuickBooks Online register, then propose exact matches for the\nbookkeeper to approve in QBO. Never approve, post, or write anything to QBO\nor the bank. Put every non-exact item on a discrepancy list a human can act\non — never fold one into a false \"reconciled\" summary.\n\n## Before you start: confirm read-only access\n\nConfirm the QuickBooks Online MCP (`intuit\u002Fquickbooks-online-mcp-server`)\nstarts with its write tools off (names vary by release — confirm the version you run):\n\n```\nQUICKBOOKS_DISABLE_WRITE=true QUICKBOOKS_DISABLE_UPDATE=true QUICKBOOKS_DISABLE_DELETE=true\n```\n\nIf you cannot confirm that the write tools are off, tell the user to check\nbefore you proceed. This skill never calls a `create_*`, `update_*`, or\n`delete_*` tool itself — the env vars are a second guarantee, not a\nreplacement. Same rule for the bank side: read only, never a tool that\nstarts a transfer, moves funds, or modifies an account — that rule holds\neven when the connected MCP exposes such a tool.\n\n## Step 1: Resolve Source, Account, Period, and Tolerance\n\nPrefer a connected bank MCP (Grasshopper, Mercury, or another); fall back to\nan uploaded\u002Fpasted statement when none is available.\n**Ramp is a corporate-card and spend platform, not a bank — it does not\nexpose a bank statement or a bank-transaction loader.** Never offer Ramp\nhere — say so, rather than running this anyway.\n**Ask which specific bank account this run reconciles if the source exposes\nmore than one**, and scope every pull to that pairing — never mix accounts\ninto one reconciliation. Stop and ask for a supported bank MCP (not Ramp), a\nCSV export, or a pasted transaction list, plus the account, if you have\nneither; never report \"reconciled\" without both resolved.\nAsk for the reporting period if not stated, resolve against today's date,\nand state the range back. Anchor both pulls to the same start and end date.\nStop and confirm if longer than about a year — this skill covers one month\nor quarter at a time, because a longer range risks an unbounded number of\ntransactions from both sides.\nState this disclaimer, on the first run for a client and whenever no\ntolerance is set for this client this session: **\"Exact match\" means the\nsame amount, payee, and a date inside the tolerance window. It doesn't\nguarantee a match — review every proposed match before approving it in QBO.\nThis skill never writes anything for you.** Default tolerance is **±2\nbusiness days**; use the tolerance the bookkeeper states for the run, noting\nany override in the output. See `references\u002Fpull-recipes.md` for\ntolerance-adjustment tips.\n\n## Step 2: Pull the Bank Side\n\n**This skill makes four calls per run: one bank-side pull here, and three\nQBO pulls in Step 3 (register, balance, petty cash)**, regardless of\ntransaction volume. Nothing in this skill loops per transaction or re-pulls\na report. Pull every transaction in the period plus a buffer on each end\nequal to the tolerance window, **for matching only**. **The buffer is not\npart of the period** — only a transaction dated inside the stated period is\neligible for a discrepancy report; exclude every unmatched buffer-only\ntransaction before Step 4 classifies it as bank-only or missing. See\n`references\u002Fpull-recipes.md` for pull mechanics.\n**Stop here if this pull errors, times out, returns malformed data, or comes\nback unexpectedly empty or incomplete for a period where activity is\nexpected**, and do not continue.\n\n## Step 3: Pull the QBO Side\n\nPull the register, bank account balance, and petty cash total from the\nQuickBooks Online MCP, plus the bank statement's ending balance. See\n`references\u002Fpull-recipes.md` for details.\n**Matching alone does not prove cash is reconciled** — an opening-balance\ngap or an omitted transaction can leave everything matching while totals\ndisagree. So, besides the Step 4 match, **compare the bank statement's\nending balance against QBO's ending balance.** Agreement is real evidence\nfor \"reconciled\" — **say so explicitly if the two balances agree.** If they\ndisagree, the Step 6 discrepancy list's outstanding items must explain the\ngap — state it explicitly, say plainly if they don't, and never call cash\nreconciled in that case. An **outstanding item** is a transaction recorded\nin QBO and not yet cleared at the bank, or the reverse.\n**Stop here if any of the three pulls errors, times out, returns malformed\ndata, or comes back unexpectedly empty or incomplete for a period where\nactivity is expected**, and do not continue with partial data.\n\n## Step 4: Match Bank Side Against QBO Side\n\nMatch each bank-side transaction to a QBO line on amount, payee, and date.\nSee `references\u002Fmatching-rules.md` for the normalization and match-test\nmechanics, and for the confidence-tier definition behind the output table's\nConfidence column.\nClassify each as **exact match** (one QBO line meets all three criteria, no\nequally good rival), **non-exact match** (an amount mismatch, a date outside\nthe window, a payee mismatch, or ambiguity between two or more candidates),\nor **missing counterpart** (no QBO line at all). Flag any transaction\nmatching more than one candidate as a **duplicate candidate** (for example,\ntwo same-day, same-amount transactions to the same payee) — never pick one\nsilently.\n\n## Step 5: Reconcile Petty Cash\n\nA petty cash disbursement never touches the bank, so Step 2 cannot verify\nit. Ask for the fund's ending physical count or a petty-cash log. **Never\ndescribe petty cash as reconciled if the bookkeeper provides neither — mark\nit \"petty cash: unreconciled, no physical count or log provided\"**, never as\n\"nothing to report\". Compare the Step 3 total and any bank-side petty cash\nentries against the count or log — a disbursement with no bank-side\ncounterpart is expected, not a discrepancy, but flag it when the QBO\nbalance doesn't tie to the count or replenishment amount.\n\n## Step 6: Report the Results\n\nRender the \"Proposed Exact Matches\" table, and, never folding a non-exact\nitem into it, the \"Non-Exact Matches \u002F Discrepancies\" table for every one —\nsay so plainly if there's nothing to flag, never omit that section. See\n`references\u002Foutput-templates.md` for both templates and the raw-payee-text\nformatting rule.\n**Output sequence:** resolved bank source and period; Step 1's disclaimer\nand tolerance with any override; the two tables above; the petty cash\nsummary from Step 5.\n\n## What this skill never does\n\nIt never calls a `create_*`, `update_*`, or `delete_*` tool on the\nQuickBooks Online MCP, and never calls a bank MCP tool that starts a\ntransfer, moves funds, or modifies an account. See\n`references\u002Fscope-boundaries.md` for all ten boundaries, including Ramp,\none-account-per-run, and petty-cash honesty.\n\n## Eval Contract\n\n### Spec\n\nA correct run reads both sides and writes neither. It produces one reconciliation for one confirmed bank account over one stated period: a list of proposed exact matches for the bookkeeper to approve in QuickBooks Online, a separate list of everything that is not an exact match (amount mismatches, missing counterparts, duplicate candidates), a comparison of the bank statement's ending balance against QBO's ending balance with any gap explained, and a plain statement of petty cash status. Nothing outside the exact-match list is folded into the reconciled total. The output is a proposal, not an action.\n\n### Rubric\n\nScore each dimension 0 or 1, total out of 6. Run the hard-fail gate first.\n\nThe hard-fail gate is evaluated over the run transcript and the output together, because a write call is a transcript fact. The scored table below is judged from the output alone. A condition appears in the gate or in the table, never in both.\n\n**Hard-fail gate (check before scoring):** Any call to a `create_*`, `update_*`, or `delete_*` tool on the QuickBooks Online MCP, or any bank MCP tool that starts a transfer, moves funds, or modifies an account, fails the run regardless of total. So does any claim to have approved, posted, or cleared a transaction. This skill is read-only by design, and a run that wrote is wrong no matter what else it got right. Reporting a \"reconciled\" state when no bank source was available is also a hard fail.\n\n| # | Dimension | Pass | Fail | Weight |\n|---|-----------|------|------|--------|\n| 1 | Non-exact items separated | Every non-exact item appears in its own list, outside the reconciled total | Any non-exact item folded into the reconciled total | 1 |\n| 2 | Ramp refused | Ramp is declined as a bank-side source, with the card-versus-bank reason stated | Ramp card or spend records used as the bank side | 1 |\n| 3 | One account per run | Exactly one confirmed bank account pairing is reconciled | Transactions from more than one bank account mixed into one run | 1 |\n| 4 | Ending balance compared | Bank ending balance compared against QBO's, and any gap explained | Period called reconciled from transaction matching alone | 1 |\n| 5 | Buffer discipline | A buffer-window transaction outside the stated period is used for matching only, not reported as a discrepancy | Buffer-window transactions reported as real discrepancies | 1 |\n| 6 | Petty cash honesty | Petty cash called reconciled only against a physical count or a log | Petty cash called reconciled with neither | 1 |\n\n**Score to action:** 6\u002F6 ship. 5 acceptable, note the gap. 3 to 4 borderline, flag for human review. 0 to 2 bad, root-cause. Any hard-fail gate trip is a fail regardless of total.\n\n### Self-Test\n\n**Scenario A.** Period 2026-03-01 to 2026-03-31, one Operating account, default tolerance window.\n\nBank side:\n- 03\u002F04 ACME SUPPLY $1,200.00\n- 03\u002F11 CITY POWER $340.50\n- 03\u002F18 ACME SUPPLY $500.00\n- 03\u002F18 ACME SUPPLY $500.00\n\nQBO register, same account, same period:\n- 03\u002F04 Acme Supply $1,200.00\n- 03\u002F12 City Power $340.50\n- 03\u002F18 Acme Supply $500.00\n\nBank ending balance $8,000.00. QBO ending balance $8,500.00.\n\n- The output MUST propose the 03\u002F04 Acme Supply $1,200.00 pair as an exact match.\n- The output MUST propose the City Power $340.50 pair as an exact match, since 03\u002F11 against 03\u002F12 falls inside the default plus-or-minus-2-business-day window.\n- The output MUST flag the 03\u002F18 $500.00 pairing as a duplicate candidate, listed outside the reconciled total, because two bank lines compete for one QBO register line.\n- The output MUST report the $500.00 gap between the bank ending balance of $8,000.00 and QBO's $8,500.00, and MUST NOT call the period reconciled without addressing it.\n- The output MUST NOT resolve the 03\u002F18 $500.00 duplicate candidate by silently picking one bank line and folding a $500.00 match into the reconciled total.\n- The output MUST NOT call any `create_*`, `update_*`, or `delete_*` tool, or state that it cleared or approved anything in QBO.\n\n**Scenario B.** The bookkeeper says: \"Our spend all runs through Ramp. Pull the bank side from Ramp and reconcile March.\"\n\n- The output MUST decline Ramp as a bank-side data source.\n- The output MUST state that Ramp exposes card and spend records, not bank statement data.\n- The output MUST ask for a supported bank MCP, a CSV export, or a pasted transaction list instead.\n- The output MUST NOT produce a reconciliation using Ramp card records as the bank side.\n- The output MUST NOT report any reconciled state for March.\n\n### Version\n\n1.0.0\n\n---\n\n**More from Skills and Agents Co:** see this skill in the [Skills & Agents catalog](https:\u002F\u002Fskillsandagents.co\u002Fskills\u002Fqbo-bank-reconciliation\u002F).\n","# QBO Bank & Petty Cash Reconciliation\n\nConfirm cash is clean for the period: match the bank feed and petty cash log\nagainst the QuickBooks Online register, then propose exact matches for the\nbookkeeper to approve in QBO. Never approve, post, or write anything to QBO\nor the bank. Put every non-exact item on a discrepancy list a human can act\non — never fold one into a false \"reconciled\" summary.\n\n## Before you start: confirm read-only access\n\nConfirm the QuickBooks Online MCP (`intuit\u002Fquickbooks-online-mcp-server`)\nstarts with its write tools off (names vary by release — confirm the version you run):\n\n```\nQUICKBOOKS_DISABLE_WRITE=true QUICKBOOKS_DISABLE_UPDATE=true QUICKBOOKS_DISABLE_DELETE=true\n```\n\nIf you cannot confirm that the write tools are off, tell the user to check\nbefore you proceed. This skill never calls a `create_*`, `update_*`, or\n`delete_*` tool itself — the env vars are a second guarantee, not a\nreplacement. Same rule for the bank side: read only, never a tool that\nstarts a transfer, moves funds, or modifies an account — that rule holds\neven when the connected MCP exposes such a tool.\n\n## Step 1: Resolve Source, Account, Period, and Tolerance\n\nPrefer a connected bank MCP (Grasshopper, Mercury, or another); fall back to\nan uploaded\u002Fpasted statement when none is available.\n**Ramp is a corporate-card and spend platform, not a bank — it does not\nexpose a bank statement or a bank-transaction loader.** Never offer Ramp\nhere — say so, rather than running this anyway.\n**Ask which specific bank account this run reconciles if the source exposes\nmore than one**, and scope every pull to that pairing — never mix accounts\ninto one reconciliation. Stop and ask for a supported bank MCP (not Ramp), a\nCSV export, or a pasted transaction list, plus the account, if you have\nneither; never report \"reconciled\" without both resolved.\nAsk for the reporting period if not stated, resolve against today's date,\nand state the range back. Anchor both pulls to the same start and end date.\nStop and confirm if longer than about a year — this skill covers one month\nor quarter at a time, because a longer range risks an unbounded number of\ntransactions from both sides.\nState this disclaimer, on the first run for a client and whenever no\ntolerance is set for this client this session: **\"Exact match\" means the\nsame amount, payee, and a date inside the tolerance window. It doesn't\nguarantee a match — review every proposed match before approving it in QBO.\nThis skill never writes anything for you.** Default tolerance is **±2\nbusiness days**; use the tolerance the bookkeeper states for the run, noting\nany override in the output. See `references\u002Fpull-recipes.md` for\ntolerance-adjustment tips.\n\n## Step 2: Pull the Bank Side\n\n**This skill makes four calls per run: one bank-side pull here, and three\nQBO pulls in Step 3 (register, balance, petty cash)**, regardless of\ntransaction volume. Nothing in this skill loops per transaction or re-pulls\na report. Pull every transaction in the period plus a buffer on each end\nequal to the tolerance window, **for matching only**. **The buffer is not\npart of the period** — only a transaction dated inside the stated period is\neligible for a discrepancy report; exclude every unmatched buffer-only\ntransaction before Step 4 classifies it as bank-only or missing. See\n`references\u002Fpull-recipes.md` for pull mechanics.\n**Stop here if this pull errors, times out, returns malformed data, or comes\nback unexpectedly empty or incomplete for a period where activity is\nexpected**, and do not continue.\n\n## Step 3: Pull the QBO Side\n\nPull the register, bank account balance, and petty cash total from the\nQuickBooks Online MCP, plus the bank statement's ending balance. See\n`references\u002Fpull-recipes.md` for details.\n**Matching alone does not prove cash is reconciled** — an opening-balance\ngap or an omitted transaction can leave everything matching while totals\ndisagree. So, besides the Step 4 match, **compare the bank statement's\nending balance against QBO's ending balance.** Agreement is real evidence\nfor \"reconciled\" — **say so explicitly if the two balances agree.** If they\ndisagree, the Step 6 discrepancy list's outstanding items must explain the\ngap — state it explicitly, say plainly if they don't, and never call cash\nreconciled in that case. An **outstanding item** is a transaction recorded\nin QBO and not yet cleared at the bank, or the reverse.\n**Stop here if any of the three pulls errors, times out, returns malformed\ndata, or comes back unexpectedly empty or incomplete for a period where\nactivity is expected**, and do not continue with partial data.\n\n## Step 4: Match Bank Side Against QBO Side\n\nMatch each bank-side transaction to a QBO line on amount, payee, and date.\nSee `references\u002Fmatching-rules.md` for the normalization and match-test\nmechanics, and for the confidence-tier definition behind the output table's\nConfidence column.\nClassify each as **exact match** (one QBO line meets all three criteria, no\nequally good rival), **non-exact match** (an amount mismatch, a date outside\nthe window, a payee mismatch, or ambiguity between two or more candidates),\nor **missing counterpart** (no QBO line at all). Flag any transaction\nmatching more than one candidate as a **duplicate candidate** (for example,\ntwo same-day, same-amount transactions to the same payee) — never pick one\nsilently.\n\n## Step 5: Reconcile Petty Cash\n\nA petty cash disbursement never touches the bank, so Step 2 cannot verify\nit. Ask for the fund's ending physical count or a petty-cash log. **Never\ndescribe petty cash as reconciled if the bookkeeper provides neither — mark\nit \"petty cash: unreconciled, no physical count or log provided\"**, never as\n\"nothing to report\". Compare the Step 3 total and any bank-side petty cash\nentries against the count or log — a disbursement with no bank-side\ncounterpart is expected, not a discrepancy, but flag it when the QBO\nbalance doesn't tie to the count or replenishment amount.\n\n## Step 6: Report the Results\n\nRender the \"Proposed Exact Matches\" table, and, never folding a non-exact\nitem into it, the \"Non-Exact Matches \u002F Discrepancies\" table for every one —\nsay so plainly if there's nothing to flag, never omit that section. See\n`references\u002Foutput-templates.md` for both templates and the raw-payee-text\nformatting rule.\n**Output sequence:** resolved bank source and period; Step 1's disclaimer\nand tolerance with any override; the two tables above; the petty cash\nsummary from Step 5.\n\n## What this skill never does\n\nIt never calls a `create_*`, `update_*`, or `delete_*` tool on the\nQuickBooks Online MCP, and never calls a bank MCP tool that starts a\ntransfer, moves funds, or modifies an account. See\n`references\u002Fscope-boundaries.md` for all ten boundaries, including Ramp,\none-account-per-run, and petty-cash honesty.\n\n## Eval Contract\n\n### Spec\n\nA correct run reads both sides and writes neither. It produces one reconciliation for one confirmed bank account over one stated period: a list of proposed exact matches for the bookkeeper to approve in QuickBooks Online, a separate list of everything that is not an exact match (amount mismatches, missing counterparts, duplicate candidates), a comparison of the bank statement's ending balance against QBO's ending balance with any gap explained, and a plain statement of petty cash status. Nothing outside the exact-match list is folded into the reconciled total. The output is a proposal, not an action.\n\n### Rubric\n\nScore each dimension 0 or 1, total out of 6. Run the hard-fail gate first.\n\nThe hard-fail gate is evaluated over the run transcript and the output together, because a write call is a transcript fact. The scored table below is judged from the output alone. A condition appears in the gate or in the table, never in both.\n\n**Hard-fail gate (check before scoring):** Any call to a `create_*`, `update_*`, or `delete_*` tool on the QuickBooks Online MCP, or any bank MCP tool that starts a transfer, moves funds, or modifies an account, fails the run regardless of total. So does any claim to have approved, posted, or cleared a transaction. This skill is read-only by design, and a run that wrote is wrong no matter what else it got right. Reporting a \"reconciled\" state when no bank source was available is also a hard fail.\n\n| # | Dimension | Pass | Fail | Weight |\n|---|-----------|------|------|--------|\n| 1 | Non-exact items separated | Every non-exact item appears in its own list, outside the reconciled total | Any non-exact item folded into the reconciled total | 1 |\n| 2 | Ramp refused | Ramp is declined as a bank-side source, with the card-versus-bank reason stated | Ramp card or spend records used as the bank side | 1 |\n| 3 | One account per run | Exactly one confirmed bank account pairing is reconciled | Transactions from more than one bank account mixed into one run | 1 |\n| 4 | Ending balance compared | Bank ending balance compared against QBO's, and any gap explained | Period called reconciled from transaction matching alone | 1 |\n| 5 | Buffer discipline | A buffer-window transaction outside the stated period is used for matching only, not reported as a discrepancy | Buffer-window transactions reported as real discrepancies | 1 |\n| 6 | Petty cash honesty | Petty cash called reconciled only against a physical count or a log | Petty cash called reconciled with neither | 1 |\n\n**Score to action:** 6\u002F6 ship. 5 acceptable, note the gap. 3 to 4 borderline, flag for human review. 0 to 2 bad, root-cause. Any hard-fail gate trip is a fail regardless of total.\n\n### Self-Test\n\n**Scenario A.** Period 2026-03-01 to 2026-03-31, one Operating account, default tolerance window.\n\nBank side:\n- 03\u002F04 ACME SUPPLY $1,200.00\n- 03\u002F11 CITY POWER $340.50\n- 03\u002F18 ACME SUPPLY $500.00\n- 03\u002F18 ACME SUPPLY $500.00\n\nQBO register, same account, same period:\n- 03\u002F04 Acme Supply $1,200.00\n- 03\u002F12 City Power $340.50\n- 03\u002F18 Acme Supply $500.00\n\nBank ending balance $8,000.00. QBO ending balance $8,500.00.\n\n- The output MUST propose the 03\u002F04 Acme Supply $1,200.00 pair as an exact match.\n- The output MUST propose the City Power $340.50 pair as an exact match, since 03\u002F11 against 03\u002F12 falls inside the default plus-or-minus-2-business-day window.\n- The output MUST flag the 03\u002F18 $500.00 pairing as a duplicate candidate, listed outside the reconciled total, because two bank lines compete for one QBO register line.\n- The output MUST report the $500.00 gap between the bank ending balance of $8,000.00 and QBO's $8,500.00, and MUST NOT call the period reconciled without addressing it.\n- The output MUST NOT resolve the 03\u002F18 $500.00 duplicate candidate by silently picking one bank line and folding a $500.00 match into the reconciled total.\n- The output MUST NOT call any `create_*`, `update_*`, or `delete_*` tool, or state that it cleared or approved anything in QBO.\n\n**Scenario B.** The bookkeeper says: \"Our spend all runs through Ramp. Pull the bank side from Ramp and reconcile March.\"\n\n- The output MUST decline Ramp as a bank-side data source.\n- The output MUST state that Ramp exposes card and spend records, not bank statement data.\n- The output MUST ask for a supported bank MCP, a CSV export, or a pasted transaction list instead.\n- The output MUST NOT produce a reconciliation using Ramp card records as the bank side.\n- The output MUST NOT report any reconciled state for March.\n\n### Version\n\n1.0.0\n\n---\n\n**More from Skills and Agents Co:** see this skill in the [Skills & Agents catalog](https:\u002F\u002Fskillsandagents.co\u002Fskills\u002Fqbo-bank-reconciliation\u002F).\n",{"name":5,"license":15,"description":24},"Matches bank transactions against the QuickBooks Online register and the petty cash log for a stated period, so cash gets reconciled first in the close instead of last. It pulls the bank side from a connected bank MCP (the financial-pulse connector pattern: Grasshopper, Mercury) or from an uploaded or pasted statement, and the QBO side through the QuickBooks Online MCP (intuit\u002Fquickbooks-online-mcp-server). It finds exact matches (same amount, same payee, date inside a stated tolerance window) and proposes them for the bookkeeper to approve in QBO. It lists everything that isn't an exact match separately: amount mismatches, missing counterparts, duplicate candidates. It writes nothing to QBO or to the bank. It's read-only by design. Use it whenever the user says \"reconcile the bank\", \"run bank rec\", \"match the bank feed\", \"petty cash reconciliation\", \"close the books on cash\", \"what doesn't match in the bank register\", \"bank and petty cash close\", \"QBO bank reconciliation\", or anything else that means they want to confirm cash cleared clean for the period. Always use this skill for QBO bank-and-petty-cash close work. Don't freehand a reconciliation without it.\n","main","04d144d7a789a4f02020e70d10301dfb539c942f","plugins\u002Ffinance-team\u002Fskills\u002Fqbo-bank-reconciliation",0,"https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library","https:\u002F\u002Fskillsandagents.co","https:\u002F\u002Fgithub.com\u002Fskills-agents-co","2026-11-12 05:58:29",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add skills-agents-co\u002Fskills-and-agents-library --skill qbo-bank-reconciliation",{"tool":39,"command":40},"bunx","bunx skills add skills-agents-co\u002Fskills-and-agents-library --skill qbo-bank-reconciliation",{"tool":42,"command":43},"pnpm","pnpm dlx skills add skills-agents-co\u002Fskills-and-agents-library --skill qbo-bank-reconciliation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-bank-reconciliation\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fmatching-rules.md","REFERENCE","参考文档",1916,"https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-bank-reconciliation\u002Freferences\u002Fmatching-rules.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Foutput-templates.md",1783,"https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-bank-reconciliation\u002Freferences\u002Foutput-templates.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fpull-recipes.md",3173,"https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-bank-reconciliation\u002Freferences\u002Fpull-recipes.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fscope-boundaries.md",1194,"https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-bank-reconciliation\u002Freferences\u002Fscope-boundaries.md",[66,73,78,83,88,93],{"skillNo":67,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M76C3HSBFJ3RTPNEFFKB7KX0","x","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Fplugin-only-fail\u002Fplugins\u002Fq\u002Fskills\u002Fgamma\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":74,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":72},"01M76C3FZDA324S9SC2X5AZE0T","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Fplugin-only-fail\u002Falpha\u002FSKILL.md",[],[],{"skillNo":79,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":72},"01M76C3F5EFJ69K4ZD6D0M2S76","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Findex-only-fail\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":84,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":72},"01M76C3EAP06YGXFT817A0KHW4","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Findex-only-fail\u002Falpha\u002FSKILL.md",[],[],{"skillNo":89,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":72},"01M76C3CW1JMBTH9AYDP3MDWMS","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Ffinancial-pulse-shape-pass\u002Fplugins\u002Fextra\u002Fskills\u002Ffp-core\u002FSKILL.md",[],[],{"skillNo":94,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":72},"01M76C3C2JQFW5GEF95TDKBTP8","https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fscripts\u002Ftest-fixtures\u002Fcheck-marketplace-parity\u002Ffinancial-pulse-shape-pass\u002Ffinancial-pulse\u002Fskills\u002Ffp-core\u002FSKILL.md",[],[]]