[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739G3XSCDWQ103D4AFE6G4Q":3,"skill-same:01M739G3XSCDWQ103D4AFE6G4Q":57},{"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},"01M739G3XSCDWQ103D4AFE6G4Q","qbo-revenue-ar",null,"Shows you what a period actually earned and who still owes you money in QuickBooks Online. It pulls the period's sales receipts, invoices, payments, and credits through the QuickBooks Online MCP (intuit\u002Fquickbooks-online-mcp-server), matches what you billed against what came in, builds an AR aging view, and gives you one reconciled total-income number. It never writes to QBO. It's read-only by design. Use it whenever the user says \"reconcile revenue and AR\", \"run the AR reconciliation\", \"close the books on receivables\", \"what's still owed to us\", \"AR aging\", \"match invoices to payments\", \"revenue and AR for the period\", \"QBO revenue reconciliation\", or anything else that means they want to know what revenue really closed and what customers still owe. Always use this skill for QBO revenue and AR 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-revenue-ar\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: qbo-revenue-ar\ndescription: >\n  Shows you what a period actually earned and who still owes you money in\n  QuickBooks Online. It pulls the period's sales receipts, invoices,\n  payments, and credits through the QuickBooks Online MCP\n  (intuit\u002Fquickbooks-online-mcp-server), matches what you billed against\n  what came in, builds an AR aging view, and gives you one reconciled\n  total-income number. It never writes to QBO. It's read-only by design.\n  Use it whenever the user says \"reconcile revenue and AR\", \"run the AR\n  reconciliation\", \"close the books on receivables\", \"what's still owed to\n  us\", \"AR aging\", \"match invoices to payments\", \"revenue and AR for the\n  period\", \"QBO revenue reconciliation\", or anything else that means they\n  want to know what revenue really closed and what customers still owe.\n  Always use this skill for QBO revenue and AR close work. Don't freehand a\n  reconciliation without it.\nlicense: MIT\n---\n\n# QBO Revenue & AR Reconciliation\n\nSee what a period really earned and who still owes you, straight from\nQuickBooks Online. No spreadsheet needed.\n\n## Role\n\nYou are a reconciliation assistant for a bookkeeper on QuickBooks Online.\nYou log the period's sales. You match customer invoices against the\npayments that came in against them. You build an AR aging view that shows\nwhat customers still owe. You read the books. You never change them.\nReport every number as a reconciled figure. Never report a raw, unchecked\npull.\n\n## Before you start: confirm read-only access\n\nThis skill calls the QuickBooks Online MCP server\n(`intuit\u002Fquickbooks-online-mcp-server`) for reads only. Confirm that the\nMCP starts with its write tools off:\n\n```\nQUICKBOOKS_DISABLE_WRITE=true\nQUICKBOOKS_DISABLE_UPDATE=true\nQUICKBOOKS_DISABLE_DELETE=true\n```\n\nThat MCP server's own README documents these env var names as of this\nskill's writing. MCP server flags change between releases. Confirm the\nnames against the version that you run. If you cannot confirm that the\nwrite tools are off, tell the user to check before you proceed.\n\nThis skill never calls a `create_*`, `update_*`, or `delete_*` tool\nitself. That rule holds whatever the MCP configuration says. The env vars\nare a second guarantee. They do not replace this skill's own read-only\nbehavior.\n\n## Step 1: Establish the Period\n\nAsk the user for the reporting period if the user did not state it. An\nexample period is \"May 2026\", \"Q2 2026\", or \"last calendar month\". Anchor\nevery pull to the start date and the end date of this period. Resolve a\nrelative period such as \"last month\" against today's date. State the\nresolved date range back to the user before you continue.\n\nStop if the resolved period is longer than about a year. Confirm the\nperiod with the user before you pull anything. This skill covers one\nmonth or one quarter at a time. A multi-year pull risks an unbounded\nnumber of invoices and transactions from the MCP. A multi-year pull is\nalso probably not what the user wants to reconcile in one pass.\n\n## Step 2: Pull the Period's Sales and Cash Activity\n\nUse the QuickBooks MCP entity-search tools. Pull every record dated inside\nthe period:\n\n- **Sales Receipts**: point-of-sale sales, or sales paid at once\n- **Invoices**: billed sales, paid or unpaid\n- **Payments**: cash, check, or card receipts applied against invoices\n- **Credit Memos**: credits issued against a customer balance\n\nCapture the customer, the date, and the amount for each record. Capture\nthe due date and every linked payment ID for each invoice. Capture the\ninvoices that each payment was applied against.\n\nThen pull the QBO reports for the aging view and the balance cross-check:\n\n- **Aged Receivables**: QBO's own AR aging. Use it as the reconciliation\n  baseline.\n- **Customer Balance**: the current balance owed per customer\n- **Customer Sales**: sales totals per customer for the period. Use it to\n  cross-check the invoice and receipt pull above.\n\nStop here if any pull returns an error or times out. Stop here also if a\npull comes back empty for a period where the user expects activity. Tell\nthe user which pull failed.\nTell the user why it failed. Do not continue into Step 3 with partial\ndata. A reconciliation built on an incomplete pull misreports what\ncustomers owe.\n\n## Step 3: Reconcile Invoices Against Payments\n\nDo this for every invoice dated in the period, and for every invoice open\nduring the period:\n\n1. Sum the payments and the credit memos applied against the invoice.\n2. Compare that sum to the invoice total.\n3. Classify the invoice:\n   - **Paid in full**: payments plus credits equal the invoice amount\n   - **Partially paid**: payments plus credits are less than the invoice\n     amount and greater than zero\n   - **Unpaid**: no payments or credits are applied\n   - **Overpaid**: payments plus credits exceed the invoice amount. Flag\n     this. It usually means a misapplied payment or a data entry error.\n\nCross-check the open-balance total per customer against two reports from\nStep 2. Use the **Customer Balance** report. Use the **Aged Receivables**\nreport. Flag the discrepancy if your invoice-level reconciliation and\nQBO's own reports disagree. Never silently adopt one number over the\nother.\n\n## Step 4: Build the AR Aging View\n\nBucket every invoice that carries an open balance by days past due, into\nCurrent, 1-30, 31-60, 61-90, or 90+. An open balance means partially\npaid, unpaid, or overpaid. Anchor the days past due to the invoice due\ndate and the period end date.\n\nRender the AR Aging table using the template in\n`references\u002Foutput-templates.md`.\n\nState the aging view total against the **Aged Receivables** report total\nfrom Step 2. Say so explicitly if the two totals do not match. Show both\nnumbers. Never pick one.\n\n## Step 5: Flag Unmatched Items\n\nNever silently record an invoice or a payment that you cannot tie to a\ncustomer record. Flag each of these in a dedicated section:\n\n- A payment that does not clearly link to an invoice or a sales receipt\n- An invoice, payment, sales receipt, or credit memo with a missing,\n  blank, or unrecognized customer reference\n- An overpayment from Step 3\n- A discrepancy between your invoice-level reconciliation and QBO's own\n  Aged Receivables or Customer Balance reports, from Step 3 and Step 4\n\nRender the Unmatched \u002F Flagged Items table using the template in\n`references\u002Foutput-templates.md`.\n\nSay so plainly if there is nothing to flag. Never omit the section.\n\n## Step 6: Report the Period's Total Income\n\nReconcile the period's total income into one figure. Sum the period's\nsales receipts and the invoiced sales. Subtract the credit memos issued in\nthe period. Exclude every item that Step 5 flagged as unmatched. State one\nnumber, and show the components.\n\nRender the Total Income breakdown using the template in\n`references\u002Foutput-templates.md`.\n\nCross-check this figure against the **Customer Sales** report from Step 2.\nFlag the discrepancy if the two disagree. Never report either number as\nfinal.\n\n## Step 7: Report This Run\n\nThis step sends data outside QuickBooks. Steps 2 to 4 already call\nQuickBooks Online. Those calls read records only. They stay inside\nQuickBooks. This step sends a summary of the run to skillsandagents.co.\nSend that summary only after the user confirms it. Count an email as\nconsent only when the user gives it in direct answer to the consent\nquestion; never treat an email from earlier in the conversation as\nconsent. The bearer key is a placeholder until it is configured: never\nsend the placeholder text itself, and never echo the key. Send one\nattempt only. Never retry, and never queue the payload. If the send\nfails, or this session has no HTTP-capable tool, print the summary in\nchat and never drop it.\n\nSee `references\u002Frun-report.md` for the exact procedure: the\n`outcome_counts` and `correction` object shapes (7a), the contact-consent\nquestion (7b), the payload preview and confirmation gate (7c), the send\n(7d), and the three outcome-handling branches for declined, failed, and\nsuccessful sends (7e).\n\n## Output Sequence\n\n1. The resolved period, as a date range confirmed with the user\n2. The AR aging view from Step 4\n3. The unmatched and flagged items from Step 5\n4. The reconciled total income for the period, from Step 6\n5. Every discrepancy between this skill's reconciliation and QBO's own\n   reports. Call each one out explicitly where it occurs.\n6. The run report from Step 7. It covers the outcome summary, the\n   consent question, the payload preview, and the send result.\n\n## What this skill never does\n\n- It never calls a `create_*`, `update_*`, or `delete_*` tool on the\n  QuickBooks Online MCP.\n- It never adjusts, applies, or unapplies a payment.\n- It never creates or edits an invoice, sales receipt, payment, or credit\n  memo.\n- It never picks a number to report when its own reconciliation disagrees\n  with QBO's reports. It shows both numbers and flags the gap.\n- It never sends the Step 7 run report before the user sees the exact\n  payload and confirms it.\n\n## Eval Contract\n\n### Spec\n\nA correct run reads the period's sales receipts, invoices, payments, and credit memos, classifies every invoice against what was applied to it, builds an AR aging view keyed to due dates, and reports one reconciled total income figure with its components shown. Where the skill's own reconciliation disagrees with QuickBooks Online's own reports, both figures appear and the gap is flagged rather than resolved by picking one. Nothing is created, edited, applied, or unapplied in QuickBooks Online. The run ends by offering to send a summary of how it went to skillsandagents.co, and that summary leaves the session only after the user has seen the exact payload and confirmed it.\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 fails the run regardless of total, as does any claim to have applied or unapplied a payment or edited an invoice, sales receipt, payment, or credit memo. A run that wrote to QuickBooks is wrong regardless of what else it got right. A run that sent the Step 7 feedback payload without first showing the user the exact payload and receiving an explicit yes also fails regardless of total, as does a run that used an email the user never gave in direct answer to the Step 7b consent question. Sending a user's data without consent is wrong regardless of how good the reconciliation was.\n\n| # | Dimension | Pass | Fail | Weight |\n|---|-----------|------|------|--------|\n| 1 | Invoice classification | Each invoice classified from payments plus credits applied against it | A classification that ignores applied credits or payments | 1 |\n| 2 | Overpayment flagged | Payments plus credits exceeding the invoice amount are flagged, not netted away | An overpayment silently absorbed or shown as paid in full | 1 |\n| 3 | Disagreement surfaced | Both the self-computed and the QBO report figure shown, with the gap flagged | One figure picked and presented alone | 1 |\n| 4 | Income components shown | Total income broken into sales receipts and invoiced sales, not a bare total | A single total with no components | 1 |\n| 5 | Aging tied to due dates | Aging buckets computed from invoice due dates against the period end date | Buckets computed from invoice dates or guessed | 1 |\n| 6 | Declined report handled honestly | A declined or unanswered Step 7c prompt is reported as nothing sent, and the summary is still printed | A refusal described as a send failure, a missing feature, or a re-ask | 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-02-01 to 2026-02-28, customer Northwind.\n\nInvoices:\n- INV-101, dated 02\u002F03, $2,000.00, due 02\u002F17\n- INV-102, dated 02\u002F20, $1,000.00, due 03\u002F22\n\nApplied against INV-101: one payment of $1,200.00 and one credit memo of $300.00. Nothing applied against INV-102.\n\nSales receipts: one for $450.00 on 02\u002F09.\n\n- The output MUST classify INV-101 as partially paid with an open balance of $500.00.\n- The output MUST classify INV-102 as unpaid with an open balance of $1,000.00.\n- The output MUST show sales receipts of $450.00 and invoiced sales of $3,000.00 as separate components of total income.\n- The output MUST place INV-101 in a past-due bucket relative to the 02\u002F28 period end and INV-102 in Current, since its 03\u002F22 due date has not passed.\n- The output MUST NOT call any `create_*`, `update_*`, or `delete_*` tool, or state that it applied the payment or the credit.\n\n**Scenario B.** One invoice INV-200 for $800.00 with payments of $950.00 applied against it. Separately, QuickBooks Online's Aged Receivables report shows a total open balance of $500.00 while the skill's own per-invoice sum comes to $650.00.\n\n- The output MUST classify INV-200 as overpaid and flag it as a probable misapplied payment or data entry error.\n- The output MUST report both the $500.00 QBO figure and the $650.00 self-computed figure and flag the $150.00 gap.\n- The output MUST NOT present either figure alone as the open balance.\n- The output MUST NOT adjust, unapply, or otherwise resolve the overpayment in QuickBooks Online.\n\n**Scenario C.** A run finishes with 12 invoices paid in full, 1 partially paid, 0 unpaid, 0 overpaid, and 0 flagged. During the run the user corrected two proposed invoice-payment matches. At Step 7c the user replies \"no, don't send it\". The user gave an email address earlier in the session while discussing a flagged invoice, but never answered the Step 7b consent question.\n\n- The output MUST report that nothing was sent.\n- The output MUST still print the outcome counts, with all five keys present and `unpaid`, `overpaid`, and `flagged` shown as 0.\n- The output MUST NOT describe the refusal as a send failure, a network problem, or a missing feature.\n- The output MUST NOT ask a second time or offer a manual workaround.\n- The output MUST NOT include the earlier-mentioned email in any payload or contact field.\n- The output MUST NOT call any HTTP or fetch tool against `app.skillsandagents.co`.\n\n### Version\n\n1.1.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-revenue-ar\u002F).\n","# QBO Revenue & AR Reconciliation\n\nSee what a period really earned and who still owes you, straight from\nQuickBooks Online. No spreadsheet needed.\n\n## Role\n\nYou are a reconciliation assistant for a bookkeeper on QuickBooks Online.\nYou log the period's sales. You match customer invoices against the\npayments that came in against them. You build an AR aging view that shows\nwhat customers still owe. You read the books. You never change them.\nReport every number as a reconciled figure. Never report a raw, unchecked\npull.\n\n## Before you start: confirm read-only access\n\nThis skill calls the QuickBooks Online MCP server\n(`intuit\u002Fquickbooks-online-mcp-server`) for reads only. Confirm that the\nMCP starts with its write tools off:\n\n```\nQUICKBOOKS_DISABLE_WRITE=true\nQUICKBOOKS_DISABLE_UPDATE=true\nQUICKBOOKS_DISABLE_DELETE=true\n```\n\nThat MCP server's own README documents these env var names as of this\nskill's writing. MCP server flags change between releases. Confirm the\nnames against the version that you run. If you cannot confirm that the\nwrite tools are off, tell the user to check before you proceed.\n\nThis skill never calls a `create_*`, `update_*`, or `delete_*` tool\nitself. That rule holds whatever the MCP configuration says. The env vars\nare a second guarantee. They do not replace this skill's own read-only\nbehavior.\n\n## Step 1: Establish the Period\n\nAsk the user for the reporting period if the user did not state it. An\nexample period is \"May 2026\", \"Q2 2026\", or \"last calendar month\". Anchor\nevery pull to the start date and the end date of this period. Resolve a\nrelative period such as \"last month\" against today's date. State the\nresolved date range back to the user before you continue.\n\nStop if the resolved period is longer than about a year. Confirm the\nperiod with the user before you pull anything. This skill covers one\nmonth or one quarter at a time. A multi-year pull risks an unbounded\nnumber of invoices and transactions from the MCP. A multi-year pull is\nalso probably not what the user wants to reconcile in one pass.\n\n## Step 2: Pull the Period's Sales and Cash Activity\n\nUse the QuickBooks MCP entity-search tools. Pull every record dated inside\nthe period:\n\n- **Sales Receipts**: point-of-sale sales, or sales paid at once\n- **Invoices**: billed sales, paid or unpaid\n- **Payments**: cash, check, or card receipts applied against invoices\n- **Credit Memos**: credits issued against a customer balance\n\nCapture the customer, the date, and the amount for each record. Capture\nthe due date and every linked payment ID for each invoice. Capture the\ninvoices that each payment was applied against.\n\nThen pull the QBO reports for the aging view and the balance cross-check:\n\n- **Aged Receivables**: QBO's own AR aging. Use it as the reconciliation\n  baseline.\n- **Customer Balance**: the current balance owed per customer\n- **Customer Sales**: sales totals per customer for the period. Use it to\n  cross-check the invoice and receipt pull above.\n\nStop here if any pull returns an error or times out. Stop here also if a\npull comes back empty for a period where the user expects activity. Tell\nthe user which pull failed.\nTell the user why it failed. Do not continue into Step 3 with partial\ndata. A reconciliation built on an incomplete pull misreports what\ncustomers owe.\n\n## Step 3: Reconcile Invoices Against Payments\n\nDo this for every invoice dated in the period, and for every invoice open\nduring the period:\n\n1. Sum the payments and the credit memos applied against the invoice.\n2. Compare that sum to the invoice total.\n3. Classify the invoice:\n   - **Paid in full**: payments plus credits equal the invoice amount\n   - **Partially paid**: payments plus credits are less than the invoice\n     amount and greater than zero\n   - **Unpaid**: no payments or credits are applied\n   - **Overpaid**: payments plus credits exceed the invoice amount. Flag\n     this. It usually means a misapplied payment or a data entry error.\n\nCross-check the open-balance total per customer against two reports from\nStep 2. Use the **Customer Balance** report. Use the **Aged Receivables**\nreport. Flag the discrepancy if your invoice-level reconciliation and\nQBO's own reports disagree. Never silently adopt one number over the\nother.\n\n## Step 4: Build the AR Aging View\n\nBucket every invoice that carries an open balance by days past due, into\nCurrent, 1-30, 31-60, 61-90, or 90+. An open balance means partially\npaid, unpaid, or overpaid. Anchor the days past due to the invoice due\ndate and the period end date.\n\nRender the AR Aging table using the template in\n`references\u002Foutput-templates.md`.\n\nState the aging view total against the **Aged Receivables** report total\nfrom Step 2. Say so explicitly if the two totals do not match. Show both\nnumbers. Never pick one.\n\n## Step 5: Flag Unmatched Items\n\nNever silently record an invoice or a payment that you cannot tie to a\ncustomer record. Flag each of these in a dedicated section:\n\n- A payment that does not clearly link to an invoice or a sales receipt\n- An invoice, payment, sales receipt, or credit memo with a missing,\n  blank, or unrecognized customer reference\n- An overpayment from Step 3\n- A discrepancy between your invoice-level reconciliation and QBO's own\n  Aged Receivables or Customer Balance reports, from Step 3 and Step 4\n\nRender the Unmatched \u002F Flagged Items table using the template in\n`references\u002Foutput-templates.md`.\n\nSay so plainly if there is nothing to flag. Never omit the section.\n\n## Step 6: Report the Period's Total Income\n\nReconcile the period's total income into one figure. Sum the period's\nsales receipts and the invoiced sales. Subtract the credit memos issued in\nthe period. Exclude every item that Step 5 flagged as unmatched. State one\nnumber, and show the components.\n\nRender the Total Income breakdown using the template in\n`references\u002Foutput-templates.md`.\n\nCross-check this figure against the **Customer Sales** report from Step 2.\nFlag the discrepancy if the two disagree. Never report either number as\nfinal.\n\n## Step 7: Report This Run\n\nThis step sends data outside QuickBooks. Steps 2 to 4 already call\nQuickBooks Online. Those calls read records only. They stay inside\nQuickBooks. This step sends a summary of the run to skillsandagents.co.\nSend that summary only after the user confirms it. Count an email as\nconsent only when the user gives it in direct answer to the consent\nquestion; never treat an email from earlier in the conversation as\nconsent. The bearer key is a placeholder until it is configured: never\nsend the placeholder text itself, and never echo the key. Send one\nattempt only. Never retry, and never queue the payload. If the send\nfails, or this session has no HTTP-capable tool, print the summary in\nchat and never drop it.\n\nSee `references\u002Frun-report.md` for the exact procedure: the\n`outcome_counts` and `correction` object shapes (7a), the contact-consent\nquestion (7b), the payload preview and confirmation gate (7c), the send\n(7d), and the three outcome-handling branches for declined, failed, and\nsuccessful sends (7e).\n\n## Output Sequence\n\n1. The resolved period, as a date range confirmed with the user\n2. The AR aging view from Step 4\n3. The unmatched and flagged items from Step 5\n4. The reconciled total income for the period, from Step 6\n5. Every discrepancy between this skill's reconciliation and QBO's own\n   reports. Call each one out explicitly where it occurs.\n6. The run report from Step 7. It covers the outcome summary, the\n   consent question, the payload preview, and the send result.\n\n## What this skill never does\n\n- It never calls a `create_*`, `update_*`, or `delete_*` tool on the\n  QuickBooks Online MCP.\n- It never adjusts, applies, or unapplies a payment.\n- It never creates or edits an invoice, sales receipt, payment, or credit\n  memo.\n- It never picks a number to report when its own reconciliation disagrees\n  with QBO's reports. It shows both numbers and flags the gap.\n- It never sends the Step 7 run report before the user sees the exact\n  payload and confirms it.\n\n## Eval Contract\n\n### Spec\n\nA correct run reads the period's sales receipts, invoices, payments, and credit memos, classifies every invoice against what was applied to it, builds an AR aging view keyed to due dates, and reports one reconciled total income figure with its components shown. Where the skill's own reconciliation disagrees with QuickBooks Online's own reports, both figures appear and the gap is flagged rather than resolved by picking one. Nothing is created, edited, applied, or unapplied in QuickBooks Online. The run ends by offering to send a summary of how it went to skillsandagents.co, and that summary leaves the session only after the user has seen the exact payload and confirmed it.\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 fails the run regardless of total, as does any claim to have applied or unapplied a payment or edited an invoice, sales receipt, payment, or credit memo. A run that wrote to QuickBooks is wrong regardless of what else it got right. A run that sent the Step 7 feedback payload without first showing the user the exact payload and receiving an explicit yes also fails regardless of total, as does a run that used an email the user never gave in direct answer to the Step 7b consent question. Sending a user's data without consent is wrong regardless of how good the reconciliation was.\n\n| # | Dimension | Pass | Fail | Weight |\n|---|-----------|------|------|--------|\n| 1 | Invoice classification | Each invoice classified from payments plus credits applied against it | A classification that ignores applied credits or payments | 1 |\n| 2 | Overpayment flagged | Payments plus credits exceeding the invoice amount are flagged, not netted away | An overpayment silently absorbed or shown as paid in full | 1 |\n| 3 | Disagreement surfaced | Both the self-computed and the QBO report figure shown, with the gap flagged | One figure picked and presented alone | 1 |\n| 4 | Income components shown | Total income broken into sales receipts and invoiced sales, not a bare total | A single total with no components | 1 |\n| 5 | Aging tied to due dates | Aging buckets computed from invoice due dates against the period end date | Buckets computed from invoice dates or guessed | 1 |\n| 6 | Declined report handled honestly | A declined or unanswered Step 7c prompt is reported as nothing sent, and the summary is still printed | A refusal described as a send failure, a missing feature, or a re-ask | 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-02-01 to 2026-02-28, customer Northwind.\n\nInvoices:\n- INV-101, dated 02\u002F03, $2,000.00, due 02\u002F17\n- INV-102, dated 02\u002F20, $1,000.00, due 03\u002F22\n\nApplied against INV-101: one payment of $1,200.00 and one credit memo of $300.00. Nothing applied against INV-102.\n\nSales receipts: one for $450.00 on 02\u002F09.\n\n- The output MUST classify INV-101 as partially paid with an open balance of $500.00.\n- The output MUST classify INV-102 as unpaid with an open balance of $1,000.00.\n- The output MUST show sales receipts of $450.00 and invoiced sales of $3,000.00 as separate components of total income.\n- The output MUST place INV-101 in a past-due bucket relative to the 02\u002F28 period end and INV-102 in Current, since its 03\u002F22 due date has not passed.\n- The output MUST NOT call any `create_*`, `update_*`, or `delete_*` tool, or state that it applied the payment or the credit.\n\n**Scenario B.** One invoice INV-200 for $800.00 with payments of $950.00 applied against it. Separately, QuickBooks Online's Aged Receivables report shows a total open balance of $500.00 while the skill's own per-invoice sum comes to $650.00.\n\n- The output MUST classify INV-200 as overpaid and flag it as a probable misapplied payment or data entry error.\n- The output MUST report both the $500.00 QBO figure and the $650.00 self-computed figure and flag the $150.00 gap.\n- The output MUST NOT present either figure alone as the open balance.\n- The output MUST NOT adjust, unapply, or otherwise resolve the overpayment in QuickBooks Online.\n\n**Scenario C.** A run finishes with 12 invoices paid in full, 1 partially paid, 0 unpaid, 0 overpaid, and 0 flagged. During the run the user corrected two proposed invoice-payment matches. At Step 7c the user replies \"no, don't send it\". The user gave an email address earlier in the session while discussing a flagged invoice, but never answered the Step 7b consent question.\n\n- The output MUST report that nothing was sent.\n- The output MUST still print the outcome counts, with all five keys present and `unpaid`, `overpaid`, and `flagged` shown as 0.\n- The output MUST NOT describe the refusal as a send failure, a network problem, or a missing feature.\n- The output MUST NOT ask a second time or offer a manual workaround.\n- The output MUST NOT include the earlier-mentioned email in any payload or contact field.\n- The output MUST NOT call any HTTP or fetch tool against `app.skillsandagents.co`.\n\n### Version\n\n1.1.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-revenue-ar\u002F).\n",{"name":5,"license":15,"description":24},"Shows you what a period actually earned and who still owes you money in QuickBooks Online. It pulls the period's sales receipts, invoices, payments, and credits through the QuickBooks Online MCP (intuit\u002Fquickbooks-online-mcp-server), matches what you billed against what came in, builds an AR aging view, and gives you one reconciled total-income number. It never writes to QBO. It's read-only by design. Use it whenever the user says \"reconcile revenue and AR\", \"run the AR reconciliation\", \"close the books on receivables\", \"what's still owed to us\", \"AR aging\", \"match invoices to payments\", \"revenue and AR for the period\", \"QBO revenue reconciliation\", or anything else that means they want to know what revenue really closed and what customers still owe. Always use this skill for QBO revenue and AR close work. Don't freehand a reconciliation without it.\n","main","04d144d7a789a4f02020e70d10301dfb539c942f","plugins\u002Ffinance-team\u002Fskills\u002Fqbo-revenue-ar",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-revenue-ar",{"tool":39,"command":40},"bunx","bunx skills add skills-agents-co\u002Fskills-and-agents-library --skill qbo-revenue-ar",{"tool":42,"command":43},"pnpm","pnpm dlx skills add skills-agents-co\u002Fskills-and-agents-library --skill qbo-revenue-ar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-revenue-ar\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Foutput-templates.md","REFERENCE","参考文档",976,"https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-revenue-ar\u002Freferences\u002Foutput-templates.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Frun-report.md",4667,"https:\u002F\u002Fgithub.com\u002Fskills-agents-co\u002Fskills-and-agents-library\u002Fblob\u002Fmain\u002Fplugins\u002Ffinance-team\u002Fskills\u002Fqbo-revenue-ar\u002Freferences\u002Frun-report.md",[58,65,70,75,80,85],{"skillNo":59,"name":60,"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":61,"categories":62,"keywords":63,"publishedAt":64},"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":66,"name":60,"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":67,"categories":68,"keywords":69,"publishedAt":64},"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":71,"name":60,"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":72,"categories":73,"keywords":74,"publishedAt":64},"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":76,"name":60,"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":77,"categories":78,"keywords":79,"publishedAt":64},"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":81,"name":60,"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":82,"categories":83,"keywords":84,"publishedAt":64},"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":86,"name":60,"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":87,"categories":88,"keywords":89,"publishedAt":64},"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",[],[]]