Unposted and blocked

Two different things stop a transaction reaching the books, and they need two different fixes. One row carries no category at all, so nobody has said what it is. Another already carries a category and still has no ledger account to post to. This skill reads one month and reports both piles separately, each with the date basis it was cut on and whether its count is exact or a floor, so the work that is left is visible before the close is called done.

npx skills add wellapp-ai/skills --skill unposted-and-blocked
WWellapp
What has not reached the ledger this month?

Ask anything or use / for commands...

How the skill answers

Every step of the run, in order, with the card each one returns. A step that hands its work to another skill says which one.

  1. You ask

    What has not reached the ledger this month?

  2. Pin the workspaceSkill useddefine-workspace

    Workspaces

    Pick the workspaces to work in.

    Your workspaces
  3. Confirm the connections this answer needsSkill usedconnect-tools

    Connect a tool

    Pick a tool to connect it to Well.

    Available tools
    1 of 1
    QuickBooks avatar
    QuickBooks
    Category
    Accounting
    Data
    Accounting
    Direction
    Input
    Status
    Last sync
    1 selected
  4. Pin the monthSkill useddefine-period
  5. Probe the uncategorized pile before drawing it
  6. Draw the uncategorized pile, only when the probe found it open
  7. Probe the unposted pile before drawing it
  8. Draw the unposted pile, only when the probe found it open
  9. Keep the two counts apart
  10. State no amount
  11. If any required step errors or returns unusable data
  12. You get

    What in the month has not reached the ledger, and which pile each item sits in: waiting on a document, waiting on a category, or stopped with a reason.

Frequently asked questions

Does it tell me why each row is stuck?

No. It tells you which pile a row sits in, which is the fix it needs: a category, or a ledger account. It gives no per-row reason beyond that, and it does not invent one.

Why two counts instead of one?

Because they are two different problems. The unposted list holds only rows that already carry a category or a ledger role, so a row nobody has categorized yet appears in the uncategorized pile instead. Adding the two would merge a naming decision with a posting decision.

How much money is sitting outside the books?

The skill does not say. Both reads cap their page, no aggregate groups the unposted rows, and adding up a capped page gives a floor dressed as a total. It reports how many rows are waiting, not what they are worth.

Does it cover payroll?

Not as a pile of its own. It reads transactions, so a payslip that never reached Well is not a blocked row here, it is simply absent. Ask for the payroll read for what the payslips themselves say.

Can I trust a count of zero?

Only when the read succeeded and the page did not fill. A page that filled means more rows exist and the count is a floor. A read that failed means the pile is unknown, and the answer says so rather than reporting it clear.

Does it categorize or post anything?

No. Every tool it calls is a read. The cards carry the pickers, so a row is cleared on the card by the person looking at it, not by this skill.

Ask your first question today

Connect your tools, then ask in plain language. Every answer traces back to the record behind it. Free to start.