[ NetSuite / Cash application ]

Cash application in NetSuite, matched by an agent

engini reads remittance advice from email and the payment files your bank or lockbox already produces, finds the open NetSuite invoices each payment covers, and creates the customer payment applied to them. Short pays, deductions and anything unclear go to a person with the proposed match attached.

NetSuiteOutlook or GmailSFTPExcel or SheetsSlack
Read the NetSuite guide →
One remittance, applied
  1. Remittance advice arrivesPDF from customer: 3 invoices, one wire
  2. AI extracts the detailspayer, amount, invoice numbers
  3. NetSuite logo
    Agent finds open invoicesCustomer: Northwind, 3 open invoices
  4. NetSuite logo
    Customer payment createdapplied to INV-881, 882, 884
  5. Slack logo
    Short pay flagged#cash-app: 120.00 short on INV-884
Illustration of the flow on this page, not a product screen.
What it does
Matches payments to open invoices and creates the customer payment in NetSuite
Systems
NetSuite, Outlook or Gmail, SFTP or shared folders, Slack or Teams
Built with
A workflow with engini AI Tools extraction and an AI agent step
Your control
Your match rules; unclear items go to a person; engini moves no money
[ 01 / The problem ]

Payments arrive. The matching waits for a person.

The money is already in the bank. What is missing is the link between that payment and the NetSuite invoices it pays. Remittance details come in as PDFs, email bodies and spreadsheets, each customer in its own format, and someone reads them and builds the customer payment by hand. Emagia describes the result: tedious manual matching, and errors that leave an inaccurate picture of what customers still owe.

Until cash is applied, collections chase invoices that are already paid, credit holds stay on good customers, and the AR aging is wrong at exactly the moment finance needs it right.

Why cash application resists simple rules

  • One wire pays several invoices, and the remittance lists them in the customer’s own words.
  • Short pays and deductions need a reason, not just a number.
  • The payer on the bank line is often a parent company or a third party.
  • Remittance arrives separately from the payment, sometimes days apart.

Where an AI agent fits

Reading a messy remittance and deciding which invoices it means is judgment work, and it is the same judgment every day. engini lets an AI agent read the remittance, look up the customer’s open invoices in NetSuite, and propose the match. When the amounts reconcile, it creates the customer payment applied to those invoices. When they do not, it posts the proposed match and the gap for a person to finish.

engini does not move money and does not connect to your bank in place of your treasury tools. It reads what your bank or lockbox already sends you, as email or as files on SFTP, OneDrive or Google Drive.

[ 02 / How it works ]

Read, match, apply, flag the rest

01 / Collect

Remittance and payment data

New remittance emails start the workflow. Lockbox or bank files on SFTP, OneDrive or Google Drive are picked up on a schedule.

02 / Extract

Pull the details

engini AI Tools extracts payer, amount, date and the invoice numbers the customer listed, from a PDF, an email body or a spreadsheet.

03 / Match

Find the invoices

An AI agent step looks up the customer and their open invoices in NetSuite and proposes which invoices the payment covers.

04 / Apply

Payment or review

When the amounts reconcile, it creates the customer payment applied to those invoices. Short pays and unclear items go to Slack or Teams with the proposed match.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
NetSuiteCustomer, open InvoicesRead
NetSuiteCustomer Payment applied to invoicesCreate
Outlook or GmailRemittance emails and attachmentsRead
SFTP, OneDrive or Google DriveLockbox and bank payment filesRead
Slack or TeamsShort pays and unclear items for reviewWrite
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the NetSuite logo, the engini mark and a frosted tile joined by a thin line, labeled remittance: payment, match, applied

Editorial image: one payment, several invoices.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: when a remittance email arrives in remit@ in Outlook, extract the payer, the amount and the invoice numbers with engini AI Tools, find that customer's open invoices in NetSuite, and if the listed invoices add up to the amount, create a NetSuite customer payment applied to them. Otherwise post the proposed match and the difference to #cash-app in Slack.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect NetSuite, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can AI read remittance advice and match it to NetSuite invoices?

Yes. engini AI Tools extracts the payer, amount and invoice numbers from the remittance, and an AI agent step finds the matching open invoices in NetSuite and proposes the match.

What about short payments and one payment for many invoices?

One payment applied to several invoices is the normal case: the agent creates one customer payment applied to each. When the amounts do not reconcile, it creates nothing and posts the proposed match with the gap, so a person can decide on the deduction.

Where does the payment data come from?

From what your bank or lockbox already sends: remittance emails, and payment files dropped on SFTP, OneDrive or Google Drive. engini does not move money and does not replace your bank connection.

Does a person check payments before they are applied?

You decide where the line is. A common setup applies only exact matches and sends everything else for review. engini has no approval step before an agent action, so the rule lives in the workflow: unclear items are posted, not applied.

How is this different from NetSuite bank matching?

NetSuite matches bank lines to transactions already in NetSuite. This flow creates the customer payment and applies it to the right invoices in the first place, using remittance details NetSuite never sees.