---
title: "Cash Application Workflow for AR Teams | Kylon"
description: "How an AR team applies customer payments to invoices, researches unknown payers and handles credit memos and refunds in one Kylon room, with every application approved."
url: "https://kylon.io/use-cases/cash-application"
language: "en"
---
[HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Cash Application: Customer Payments Applied to the Right Invoice and the Right Payer
Use Case7 min read
# Cash Application: Customer Payments Applied to the Right Invoice and the Right Payer
Customer payments are applied, researched and re-checked in one Kylon room. Agents match each payment to open invoices from Stripe charges and Outlook remittances, and the AR manager approves every application before it is written.
[Get started](https://app.kylon.io/sign-up)
Kylon TeamProduct
November 6, 2026
## Money arrives before the paperwork
Cash application is the daily job of putting every customer payment against the invoices it pays. A Stripe charge usually names its invoice. A wire may arrive with a remittance advice listing five invoices, or with only a company name that matches no customer, because a parent company or a finance provider paid on the customer's behalf. Until the payment is applied, the customer looks overdue, and collections may chase an invoice that is already paid.
Payments and open invoices sit in Airtable, card and bank payments in Stripe, remittance advices in the AR mailbox on Outlook, and the application policy in Google Drive. Payer-research calls go on the Outlook calendar. When a credit memo, a late remittance or a refund changes the picture, the payment has to be looked at again, and the call booked to research it should come off the calendar.
## Who works in the room
People
- Cash application specialist
Works the daily payment queue and confirms the evidence on unclear payments
- AR manager
Approves every application and any change to the customer on a payment, and signs the closeout
- Collections lead
Runs payer-research calls and talks to customers about short payments
- Billing
Issues credit memos and confirms refunds
Agents
- AdaCash applier
Matches each payment to open invoices using Stripe charges and Outlook remittances, proposes the application, and writes Airtable once approved
AirtableStripeOutlook
- FinPayer research
Books payer-research calls for payments nobody can place, proposes cancelling them once a payment is applied, and drafts customer replies
Outlook[Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack)
- NovaExport review and closeout
Checks the summary export against the payments, proposes review flags, and tallies the day's closeout
Google DriveAirtable
AR keeps one Kylon room for cash application. A question about a payment, with or without a mention, goes to Ada, the default agent, which leads that thread. Fin owns payer research and customer mail, and Nova owns the export review and the closeout, so each picks up its own questions. When Ada applies a payment that had a research call booked, it mentions Fin with the payment id, and Fin proposes the cancellation in the same thread.
## Applying a day's payments
The application rules and the call policy live in Google Drive and are summarized in the room guidelines. Each step ends with a person.
```mermaid
flowchart TD
pay([The day's payments land
in Airtable])
match["Ada matches each payment to open
invoices and proposes an application"]
spec["Cash application specialist
confirms the evidence"]
research["Fin books a payer-research call
on the Outlook calendar"]
accept["Collections lead
accepts each call"]
ok1["AR manager approves before
Airtable is written"]
export["Nova checks the summary export
and proposes review flags"]
ok2["AR manager approves the flags"]
memo([A credit memo, late remittance
or payer memo arrives])
recheck["Ada re-checks each named payment
against the full rule list"]
ok3["Billing confirms the memo,
AR manager approves the change"]
cancel["Fin proposes cancelling the call
for each payment now applied"]
dup["Ada records a refunded duplicate
without creating a match"]
tally["Nova checks the closeout totals"]
sign["AR manager signs the closeout"]
pay --> match
match -->|matched| ok1
match -->|unclear| spec --> ok1
match -->|nobody can place| research --> accept
ok1 & accept --> export --> ok2 --> recheck
memo --> recheck
recheck --> ok3 --> cancel & dup
cancel & dup --> tally --> sign
class match,research,export,recheck,cancel,dup,tally agent
class spec,accept,ok1,ok2,ok3,sign person
class pay,memo event
classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712
classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712
classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42
```
| Stage | What happens | Who acts | Who decides |
| --- | --- | --- | --- |
| Application | Each payment is matched to open invoices from its Stripe charge or Outlook remittance, then applied, split or left unapplied | Ada | The AR manager approves before Airtable is written |
| Payer research | Payments nobody can place get a research call on the Outlook calendar | Fin | The collections lead accepts each call |
| Export review | A colleague's summary export is checked against the payments, and every candidate gets a review flag, including any the export misses | Nova | The AR manager approves the flags |
| Late remittances and credit memo | The named payments are re-checked, and a credit memo can turn a short payment into an exact one | Ada | Billing confirms the memo; the AR manager approves |
| Payer identification | A memo names the customer behind a third-party payment, and the customer field is corrected before the payment is applied | Ada, then Fin | The AR manager approves the change |
| Duplicate refund and closeout | A refunded duplicate is recorded without creating a match, and the day's totals are closed | Ada, checked by Nova | The AR manager signs the closeout |
Stages of one cash application cycle. Payments, customers and invoice ids in this example are illustrative.
## Memos, refunds and the calls nobody cancelled
Most changes come from outside AR. Billing issues a credit memo for a disputed line, and a payment that was short now covers its invoice exactly. Treasury forwards a late remittance naming the invoices a wire paid. A payer identification memo says a wire from a finance company was paid on behalf of a customer. Ada re-checks each named payment against the full rule list, corrects the customer field where the memo says so, and shows the before and after in the thread.
Two details decide whether the day closes cleanly. When a payment becomes applied, its payer-research call has no purpose left, so Fin proposes cancelling it in the same thread. And when a customer paid twice and the duplicate was refunded, the confirmed refund settles the duplicate but applies nothing. The remaining payment is still matched on its own evidence before it counts as applied.
## What the checks catch
- A candidate payment the summary export left out that still needs a review flag
- A payer-research call still booked for a payment that is now applied
- A payment from a finance provider still recorded under its name instead of the customer it pays for
- A confirmed duplicate refund treated as a match
- A short payment left short after a credit memo made it exact
## What stays with people
- Approving every application before Ada writes it to Airtable
- Approving a change to the customer on any payment
- Accepting each payer-research call and approving its cancellation
- Sending customer replies, which Fin prepares as drafts in Gmail or Outlook
## Integrations in this workflow
Kylon is not an accounts receivable system and it does not replace one. It sits across the payment, mail and file tools the AR team already uses and holds the day's coordination in one room.
- Airtable
- [Gmail](https://kylon.io/integrations/gmail)
- Google Drive
- Outlook
- [Slack](https://kylon.io/integrations/slack)
- Stripe
- **Airtable** holds the payments, the open invoices and each application
- **Stripe** holds charges and refunds, read as evidence for each payment
- **Outlook** carries the AR mailbox where remittances arrive, and the calendar for payer-research calls
- **Gmail** carries billing and treasury threads, with replies drafted for a person to send
- **Google Drive** keeps the application policy, the call rules and the summary exports
- **Slack** is where collections and billing flag customer news during the day
## Where to start
Pick one day of payments for a handful of large customers. Connect the Airtable base that holds payments and invoices, connect the AR mailbox through the cash application specialist's own Outlook account, and write one rule in the room guidelines: a payment is applied only on evidence for that payment, after the AR manager approves.
## Set it up with your agent
Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.
Set-up prompt
Set up our cash application desk in this Room. Take it one step at a time and wait for my OK before you move on.
1. Connect Airtable, Gmail, Google Drive, Outlook, Slack and Stripe. Tell me which ones still need connecting.
2. Ask me who works this desk: the cash application specialist, the AR manager, the collections lead and billing. Help me invite them to this Room.
3. Build a Cash Application App with Payment, Customer, Applied to and Status columns, one record per payment. Pull open payments and invoices from Airtable and remittances from the AR mailbox in Outlook.
4. Match each payment to its open invoices using the Stripe charge and the Outlook remittance. Flag unplaced payments, short payments a credit memo could make exact, payer-research calls still booked for applied payments, and payments recorded under a finance provider instead of the customer they pay for.
5. Propose each application and customer correction in the thread and show before and after for any customer change. Draft customer replies in Gmail or Outlook for the collections lead to send. Write nothing to Airtable and send nothing until the AR manager approves each application and every customer change. The collections lead accepts or cancels each payer-research call.
6. Write our rules, our call policy and who approves what into this Room's guideline so every payment follows the same order.
7. After one clean day, offer to turn the daily payment queue into an Automation.
Before you start, ask me for our rules one at a time.
[Get started](https://app.kylon.io/sign-up)
Your first company harness. Where humans and agents run your business together.
[Get started](https://app.kylon.io/sign-up)
## More Use Cases
[View all](https://kylon.io/use-cases)
[
### Property Tax Appeals: The Right Parcels Filed Within Each County's Capacity
Parcel triage, filing allocation, manifest review, comparable corrections and appeal letters run through one Kylon room. Agents compute each county's median and check every filing against Airtable, and the tax manager approves each change and each letter.
Real estateFinance operations
](https://kylon.io/use-cases/property-tax-appeals)[
### Utility Bill Validation: Every Bill Checked Against Tariff, Meter and Period Days
Each utility bill is checked against the site register, the tariff in force on each day and any meter swap. Agents do the arithmetic and draft the replies in one Kylon room, and the utilities lead approves every disposition and every message.
Real estateFinance operations
](https://kylon.io/use-cases/utility-bill-validation)