Ledger

An accounts receivable analyst, about $65,000 in salary and about $85,000 fully loaded once benefits, tax and overhead go on top. Ledger does not replace that person. It takes the part of the job that is a spreadsheet and a calendar reminder: the three-way reconciliation, the dunning schedule, the promise-to-pay follow-up, the Monday report.

Ledger is $20, less than that analyst costs per hour, and priced so you do not have to think about it. The number it moves is the one worth thinking about. Ten days off DSO on $2M of annual revenue frees about $55,000 of working capital, permanently.

Skills

Eight skills, reached from the composer with a slash.

• /ar-reconcileThree-way reconciliation of Stripe, QuickBooks and the AR ledger tab. This is the skill that stops Ledger from chasing money that already arrived, and the one that treats a disagreement between two systems as a finding rather than a tie to break.
• /collect-diagnoseWhy this invoice is late, with evidence, before anyone writes a firmer email. It keeps Ledger from escalating tone at a problem that tone cannot fix.
• /dunning-runThe send. Segment-aware, suppression-gated, timed against the buyer's payment cycle rather than yours.
• /ptp-trackCapture, verify and enforce promises to pay. A dated promise from a named person predicts cash better than any aging bucket, and no free template records one.
• /cash-forecastThirteen weeks of expected collections, weighted by what this company's customers actually did, with the accuracy of the last forecast attached.
• /escalate-briefThe memo that hands one invoice to a named human with everything needed to decide in two minutes, and a recommendation.
• /e1-consumeEdge E1. Reads Backstop's delivery health file and writes at most one hold recommendation per customer for your cash owner. Create it only if the same member owns Backstop. Skip it and everything else works.
• /e2-publishEdge E2. Publishes one collection-risk record per QuickBooks customer, in bands, for a co-located Backstop. Create it only if the same member owns Backstop.

Routines

Seven routines. Times are in the time zone you set.

Connectors

Stripe, QuickBooks, Gmail, Google Sheets, Slack. All five are first-party Grok Bot plugins. Nothing in this box needs an MCP server, a script, or an API key you paste anywhere. Stripe and QuickBooks are authorised read only. Ledger holds no write scope on any source system.

Ledger takes part in two optional edges. E1 lets a co-located Backstop tell Ledger which clients have delivery problems, and Ledger may write one advisory hold recommendation per customer to a tab your cash owner confirms or ignores. E2 runs the other way: Ledger publishes a collection-risk band per customer for Backstop to read. Both edges need Ledger and Backstop under the same Grok Bot member, and neither is on by default. Ledger passes every acceptance test and reports every number with both switched off.

Ledger never contacts a customer about an invoice it has not reconciled in the last 24 hours, on a pull that reached the last page of every endpoint. Chasing an invoice that was already paid is the single most expensive mistake in collections, and it is the default behaviour of most cheap dunning templates.

It never spends money, never signs anything, and never changes a record in Stripe or QuickBooks, because it holds no write scope there. Every consequential action, including every customer-facing send, needs a named human's approval, and approval covers the exact action and target it was given, never anything inferred from it.

Data from another bot can never cause Ledger to take an external action, never remove a finding from a human's view, and never widen what Ledger is allowed to do. The one thing an edge file can produce is an advisory row in a tab that no customer-facing path reads.

By email from Lemon Squeezy, within about a minute of payment:

• The share link, in a text file beside the ZIP. Add the bot to your Grok Bot account and its instructions, eight skills and seven routines come with it.
• Six documents, as a ZIP. BOT.md is the instruction block you paste and the table of every placeholder with a sane default. SKILLS.md is each skill in full, in xAI's six-section shape. ROUTINES.md is each routine with its schedule, input, expected result and approval boundary. SETUP.md is the part a template cannot carry: which connectors to authorise, which sheet to create, in what order. WORKSPACE.md is the file contract, including the two optional edges. EVAL.md is the acceptance tests.
• The acceptance tests in EVAL.md. Run them on day one, against real data with sending disabled, before you trust Ledger with a customer. They are also the condition of the 14-day refund.

No call, no name on the documents, no 24-hour wait. Open SETUP.md first. It gives the connector order and what the first hour looks like.