Short Pays and Deductions for Acumatica
The customer paid less than the invoice in Acumatica. Lunica reads the remittance, finds the reason, matches it to the invoice line, routes it to the person who owns the answer, and drafts the reply or the credit memo for Acumatica; a person decides.
Collections & ARUpdated Oct 202620 ERPs
See it work on Acumatica.
Click through the steps. Fictional data, in Acumatica’s terms; the real thing runs on Acumatica.
Inv AR204317 $9,412.50, paid $9,000.00. Pricing on the 2x4 SPF, see quote Q-4471. Tom
Harbor Point paid AR204317 $412.50 short. The stub says pricing.
The problem, as it happens in Acumatica.
A check comes in for $320 less than the invoice, with “freight” written on the stub. The clerk applies it short, the difference sits on the customer record as an open balance, and the question of whether freight was billed in error goes to whoever answers the phone. Dispatch says ask sales, sales says ask credit, and the invoice shows past due on the AR Aging report the whole time.
Nobody tracks what the deductions add up to. A builder who shorts every invoice by the fuel surcharge is teaching the counter a price nobody approved. The stubs that said “returned material” and “pricing” and “tax” are in a drawer, and the balance they add up to is written off at year end as uncollectable, when most of it was never in dispute.
How it works.
- 1
The deduction is read off the remittance
When a payment is applied short, Lunica reads the stub, the remittance email or the chargeback notice and names the reason: freight, pricing, returned material, tax, damage, or no reason given. The amount and the reason are logged against the invoice, not just the account.
- 2
Matched to the invoice line
The deduction is matched to the line it argues with: the freight line, the item whose price differs from the quote, the quantity that didn’t arrive. Lunica pulls what Acumatica has for that line, the quote, the delivery ticket and the tax status, and says what it found.
- 3
Routed to the person who owns the answer
Freight goes to dispatch, pricing to the salesperson on the account, tax to the controller, returned material to the yard. Each gets the invoice line, the stub and a one-line question. Their answer comes back to the desk.
- 4
The reply or the credit is drafted, a person decides
If the customer is right, the credit memo is prepared for Acumatica with the reason code. If the dealer is right, a short reply with the ticket or the quote attached. The credit desk sends the reply or posts the credit; the balance stays open until they do.
How it connects to Acumatica.
Lunica reads Acumatica’s open items, invoice lines, the customer record, quotes, and the delivery tickets in the files attached to the record through Acumatica’s OData and REST endpoints, under a role that can only read. The remittance itself comes from the scanner, the lockbox file or the AR inbox, read for that payment only. Contract pricing and the tax status on the customer record are read as Acumatica has them.
Nothing is posted to Acumatica on its own and nothing is sent on its own. A credit memo, when the customer is right, goes back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared, with the reason code your team uses, and a person posts it. A reply, when the dealer is right, is a draft until a person sends it. Lunica never writes a deduction off.
What a week looks like.
- Every short pay has a named reason by the end of the day it arrives.
- Freight, pricing and tax questions go to the person who can answer them, with the line in front of them.
- Credits for real errors posted with the right reason code; the rest answered with the ticket attached.
- A per-customer record of deductions, before the next credit review or the next contract price.
Questions
Does it post credit memos to Acumatica?
No. It prepares the credit memo with the invoice, the line, the amount and the reason code, and a person posts it. Until then the short balance stays open.
Does it write off small balances?
No. A small-balance rule, if your policy has one, is a line in the batch your team accepts; Lunica never writes anything off on its own.
How does it know who owns the answer?
A rule your team sets: freight to dispatch, pricing to the account’s salesperson, tax to the controller, returns to the yard. The names come from the customer record and your team list.
What if the stub says nothing?
The deduction is logged as “no reason given” and a short note asking the customer is drafted for the desk to send.
Does it see the customer’s contract price?
It reads what Acumatica has: the price on the invoice line and the contract or quote price if one exists. Where they differ, it says so and sends the question to sales.
Can we see deductions by customer?
Yes. Every deduction, reason and outcome on the account, and a book-wide view by reason.
Does it need a server?
Lunica runs on one server inside your network, whether Acumatica is in the cloud or on your own server, set up and maintained by Lunica. It reads Acumatica through Acumatica’s OData and REST endpoints, under a role that can only read. There is no inbound connection from outside your network.
What does Lunica read in Acumatica?
The customer record, open items and terms, purchase orders and receipts, the stock item, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Acumatica?
Nothing lands in Acumatica without a person. What belongs in Acumatica goes back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in the files attached to the record. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Short Pays and Deductions is written for every system on the list. You’re reading the Acumatica version.
See it on your Acumatica data.
Thirty minutes. We walk the workflow on Acumatica data, then map it to yours.