Home / Businesses / Payment Allocation to Invoices
Payment Allocation to Invoices
Apply a customer payment across open invoices, oldest due first or as the remittance says: what each invoice gets, what stays open, any unapplied cash and remittance exceptions, with a signed record.
Live
- What it does
- Apply a customer payment across open invoices, oldest due first or as the remittance says: what each invoice gets, what stays open, any unapplied cash and remittance exceptions, with a signed record.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
payment_allocationat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Live: open today. Free
New to this? Start here.
What it does
Payment Allocation to Invoices is for agents that post customer payments for a business (accounts receivable cash application) and must apply every payment the same way and show what is still open. Apply one customer payment across that customer's open invoices (accounts receivable cash application). Send the payment amount and the open invoices (invoice number, due date, open amount). By default the payment goes to the invoice that fell due first, then the next. Or send the remittance (which invoices the customer said to pay, and how much each, or the application the creditor chose) and it is applied exactly so. Get back what goes to each invoice, what stays open on each, the open total before and after, any unapplied cash, and every remittance line that names an invoice not in the list or pays more than is open. It is one of the Payments department tools LLPRO builds for the work agents do across business software (QuickBooks, Xero, NetSuite, Stripe, FreshBooks). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents that post customer payments for a business (accounts receivable cash application) and must apply every payment the same way and show what is still open.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, invoices up to 200 entries, remittance up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not read the remittance, the bank deposit or the ledger: the invoices and amounts you send are taken as given. Does not take early-payment discounts, write off short payments or split a payment between interest, fees and principal. Does not follow state statutes with their own order (Cal. Civ. Code section 1479 puts interest due first, then all principal then due, ratably, before the earliest maturity): to apply that or any other order, send it as method remittance. Does not apply credit notes: reduce the invoice's open amount first. Does not decide what to do with unapplied cash (hold on account, refund, ask the customer). Not legal or accounting advice.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "payment_allocation", "arguments": {"payment_amount": "1500.00", "invoices": [{"invoice": "A-103", "due_date": "2026-03-31", "open_amount": "300.00"}, {"invoice": "A-101", "due_date": "2026-01-31", "open_amount": "1000.00"}, {"invoice": "A-102", "due_date": "2026-02-28", "open_amount": "800.00"}]}}}For agents
Tool payment_allocation on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:dq3xl6543whps3bylyeq5zii3e): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): NCLIJPzZ5ZUENW75G/hNksh8jXcN1VlEU4nXVJZvShc=
For agents that search MCP registries for payment allocation, cash application, apply payment to invoices tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: Applying a payment is one step of collecting from customers. Tell the Hub the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card