The Agentic Accounts Receivable Workflow: Invoicing and Collections Through Claude

Every business that invoices customers runs an accounts receivable loop, and most of it is still done by hand. Someone drafts the invoice, sends it, watches for payment, chases the ones that go quiet, matches the money that lands to the right open invoice, and closes the books. The work repeats, it runs on a calendar, and it is exactly the kind of process an agent can carry. This is the agentic accounts receivable playbook: how an AI agent connected to your Meow account can draft and send invoices, track their status, send reminders, match incoming payments, reconcile to the ledger, and hand the hard cases to a person.

It is the receivables counterpart to an accounts payable playbook. Payables is the money you owe; receivables is the money owed to you. This AR workflow automates the mirror image of the AP side: get the invoice out, get the cash in, and keep the ledger honest while it happens. Meow's agent connects through an MCP endpoint at meow.com/mcp, live today for Claude, ChatGPT, Cursor, and Gemini, so the examples below assume you are working through Claude.

The Manual AR Loop and Where It Leaks

A typical agentic accounts receivable process replaces five manual steps that most finance teams run every week. Each is simple on its own; the cost is in the repetition and the gaps between them.

Draft the invoice: someone pulls the customer record, the line items, the rate, and the terms, then formats an invoice. This is where errors enter: a wrong rate, a missing PO number, stale terms.

Send it: the invoice goes out by email with a payment link or wire instructions. If it goes out late, the payment clock starts late and the cash arrives late.

Chase it: past-due invoices need reminders. Follow-up slips first when the team is busy, and slipped follow-up is the largest driver of a rising days-sales-outstanding number.

Match the payment: money lands as an ACH deposit, a wire, or a USDC transfer, and someone ties it back to the open invoice it pays. Partial payments and missing remittance details make this slow and error-prone.

Reconcile it: the paid invoice is closed, the cash is booked, and the books are squared with the bank. Do it late and the aging report lies about who still owes what.

The leaks are time and cash. Time goes into formatting and re-keying. Cash leaks through late sends, skipped reminders, and receivables that quietly age past the point where they are likely to be collected. QuickBooks reports that a majority of US small businesses are owed money on unpaid invoices at any given time. See the QuickBooks accounts receivable guide and the Intuit QuickBooks Small Business Late Payments Report for the figures.

The Two Standing Prompts That Run the AR Workflow

The AR workflow runs on two standing prompts you set up once and let the agent execute on a schedule. A standing prompt is an instruction the agent applies to every matching event, not a one-off request.

Invoice generation: the first prompt tells the agent how to build and send invoices. For example: when a project is marked billable in the source system, draft an invoice using the customer's saved terms, the agreed rate, and the line items, then queue it for a human to approve before it sends. The prompt fixes the format, numbering, terms, and send channel so every invoice leaves the same way.

Payment matching: the second prompt tells the agent how to reconcile money in. For example: when a payment lands on the Meow balance, read the amount, the sender, and any memo, find the open invoice it pays, mark it paid, and post the reconciliation. Where a payment does not cleanly match one invoice, flag it for a person rather than guessing.

Together the two prompts cover the loop. The first moves invoices out. The second brings cash in and closes the record. The reminders and escalations hang off these two.

How the Agent Drafts and Sends Invoices Through Meow Invoicing

Meow Invoicing is the surface the agent uses to send invoices and collect payments. It does not invent a customer or a rate; it reads them from your records and assembles the invoice inside Meow.

Draft: the agent pulls the customer, the line items, the amount, the currency, and the payment terms, then produces a draft invoice with a unique number and a due date derived from the terms. Because one prompt builds every invoice, the numbering stays sequential and the terms stay consistent.

Approve: sending an invoice is a customer-facing action, so it passes through a human-approval gate by default. The agent presents the draft, you confirm or edit, and only then does it send. For repeat invoices you can widen the gate; for a new customer or an unusual amount you keep it tight.

Send and collect: once approved, Meow Invoicing sends the invoice with a payment link so the customer can pay by ACH, wire, or USDC. Because USDC and Fiat sit on the same Meow balance, the customer's choice of rail does not fragment your books; the money lands in one place.

Tracking Status and Sending Reminders

Once an invoice is out, the agent tracks its status and runs the follow-up cadence that manual teams tend to drop. This is where an agent earns its keep, because reminders are dull and easy to skip.

Status tracking: the agent watches each open invoice and knows whether it is current, due soon, or past due, and by how many days, building the aging view continuously rather than once a month.

Reminders and dunning: on the schedule you set, the agent sends reminders. A common cadence is a friendly note a few days after the due date, a firmer reminder around two weeks past due with the payment link up front, and a direct message near 30 days. The agent drafts each in your voice and queues the firmer messages for approval before they send.

Escalation triggers: the agent flags invoices that cross the thresholds you set, such as any invoice past 30 days or any balance above a set amount, and routes them to a person. It does the chasing that follows a rule and escalates the judgment calls.

Matching Incoming ACH, Wire, and USDC Payments to Open Invoices

The payment-matching prompt closes the loop on the cash side. Money can arrive as an ACH credit, a wire, or a USDC transfer, and the agent reconciles all three against the same open invoices.

Read the payment: when funds land on the Meow balance, the agent captures the amount, the sender, the rail, and any remittance memo. For USDC, the on-chain transaction hash serves as the settlement reference.

Match to an invoice: the agent looks for the open invoice that fits, first by exact amount and customer, then by memo or invoice number. A clean single match is marked paid under your prompt. A partial payment, a combined payment covering several invoices, or a payment with no usable memo is flagged for a person rather than force-matched.

Screening stays with the bank: incoming payments run through the partner bank's compliance checks, including OFAC screening against the Specially Designated Nationals list. The agent does not replace that layer; it reconciles what clears.

Reconciling to the Ledger

Reconciliation keeps the aging report truthful. Once a payment is matched, the agent records it so the invoice, the cash, and the accounting system all agree.

Close the invoice: the matched invoice moves to a paid state, and the amount drops off the open receivables balance. The aging view updates in the same pass, so the past-due list stays current.

Post to the books: Meow reconciles to QuickBooks the same day, so the cash receipt and the closed invoice post without a monthly re-keying exercise. Because USDC and fiat share one balance, a USDC payment reconciles through the same path as an ACH or wire receipt, with the transaction hash as the audit reference.

Keep the trail: every step the agent takes is logged, so an auditor can trace an invoice from draft to send to payment to ledger entry.

Human-Approval Gates and Escalating Aged Receivables

The permissions model is what makes this safe to run. By default an agent connected to a Meow account has zero ability to move money. The account holder turns on each capability explicitly, and every action the agent initiates routes back to a person for approval through Claude, SMS, Telegram, or the Meow dashboard. Account and routing numbers are never exposed to the model, and BSA, AML, and OFAC screening run through the partner bank on every transaction.

Gate the sensitive steps: sending an invoice, sending a dunning message, applying a credit or refund, and writing off a balance are all customer-facing or money-moving, so they sit behind approval by default. The agent prepares the action and a person releases it. Reading status, drafting, and matching a clean payment can run with a lighter touch because they do not move money or reach the customer.

Escalate aged receivables: past a threshold you set, an aged receivable stops being a reminder problem and becomes a judgment call about a payment plan, a collections referral, or a write-off. The agent hands these to a person with the full history attached: the invoice, the reminder trail, the days outstanding, and the payment record. It surfaces the decision; the human makes it.

A Realistic Before and After

The gains are worth stating as typical ranges rather than precise promises, because they depend on your terms, your customer base, and how disciplined your current process is.

Time per invoice: drafting and sending an invoice by hand commonly takes 10 to 20 minutes once you count pulling the data, formatting, and sending. With the agent drafting from your records and a person approving the send, the human time drops to a quick review, often under a minute. The larger saving is on reminders, which the agent runs on schedule instead of when someone remembers.

Days sales outstanding: DSO is the average number of days it takes to collect after invoicing. A healthy DSO usually sits within about 10 to 15 days of your stated terms. Teams that move from slipped, manual follow-up to a cadence that runs on time commonly pull several days out of DSO, which is working capital returned to the business. The QuickBooks days sales outstanding reference walks through the calculation and benchmarks by industry.

The before is a team that invoices late, chases inconsistently, and reconciles in a monthly scramble. The after is invoices out on time, reminders that never get skipped, payments matched as they land, and books current every day. The agent handles the repetition; the person keeps the judgment and the approvals.

Frequently Asked Questions

What is an agentic accounts receivable workflow? It is an accounts receivable process where an AI agent connected to your account handles the repetitive steps: drafting and sending invoices, tracking their status, sending payment reminders, matching incoming payments to open invoices, and reconciling to the ledger. A person still approves the sensitive steps and handles the judgment calls. Meow's agent connects through the MCP endpoint at meow.com/mcp, live for Claude, ChatGPT, Cursor, and Gemini.

Can the agent send invoices on its own without me approving them? Only if you choose to widen the gate. By default, sending an invoice passes through a human-approval gate because it is a customer-facing action. The agent drafts and queues it; you confirm or edit before it sends. For repeat, low-risk invoices you can loosen this; for new customers you keep approval tight.

How does the agent match an incoming payment to the right invoice? When money lands on your Meow balance as ACH, wire, or USDC, the agent reads the amount, the sender, the rail, and any memo or reference. It matches a clean, single payment to its open invoice by amount and customer, then by memo or invoice number, and marks it paid. Partial payments, combined payments, and payments with no usable memo are flagged for a person instead of being force-matched.

What happens with USDC payments versus ACH and wires? They reconcile through the same path. USDC and fiat sit on one Meow balance, so a USDC payment closes its invoice and posts to the books the same way an ACH or wire receipt does. The on-chain transaction hash carries as the settlement reference, and Meow reconciles to QuickBooks the same day.

Which AR actions require human approval? Anything customer-facing or money-moving: sending invoices, sending dunning messages, applying credits or refunds, and writing off balances. By default the agent has zero ability to move money, and every action it initiates routes back to a person through Claude, SMS, Telegram, or the Meow dashboard. Reading status, drafting, and matching a clean payment can run with a lighter touch.

How does this affect my day's sales outstanding? The largest lever is running the reminder cadence on time instead of skipping it when busy. Teams that move from inconsistent follow-up to a scheduled cadence commonly pull several days out of DSO. A healthy DSO usually sits within about 10 to 15 days of your terms; treat the improvement as a typical range, not a guarantee.

A Note on Meow

Meow Invoicing lets you send invoices and collect payments, with USDC and fiat running on the same balance and same-day reconciliation to QuickBooks. Meow does not try to be your accounting system or your credit team, and that is deliberate: the ledger stays where it belongs and the human keeps the judgment. What Meow supplies is the receivables rail and the agent that runs it, with a person approving every step that moves money or reaches a customer.

Put the AR loop on autopilot, keep your hand on the wheel

The repetitive parts of receivables, drafting, sending, chasing, matching, and reconciling, are ready to hand to an agent today, with approval gates on anything that matters. Set the two standing prompts, keep the human in the loop, and let the cash come in on schedule. Open an account at meow.com.

Meow Technologies is a financial technology company, not a bank or FDIC-insured depository institution. Banking services are provided by Grasshopper Bank, N.A.; Member FDIC. The FDIC's deposit insurance coverage only protects against the failure of an FDIC-insured bank.