Online Payments for DMSi Agility
A payment page under your name on every collections note, statement and invoice email, with the open invoices read from Agility. The customer pays by card or bank transfer and picks what the payment covers; the payment and its remittance are prepared for Agility and posted by a person.
Collections & ARUpdated Oct 202620 ERPs
See it work on Agility.
Click through the steps. Fictional data, in Agility’s terms; the real thing runs on Agility.
Hi Tom,
Your September statement is attached. Three invoices are open, $14,206.90 together; the oldest is from Aug 28.
You can pay any of them here, by card or bank transfer, and pick which ones.
Nora Ellison, Ridgeline Supply Co.
Minted at send for Harbor Point. Nothing changes about how the statement goes out.
Tools in this workflow.
Pieces your customers and your team use directly, on their own or inside this workflow.
The problem, as it happens in Agility.
A contractor wants to pay a statement from the truck and can’t. The options are a check in the mail, a card number read over the phone to whoever picks up at the counter, or a login to a portal nobody remembers. The payment arrives without a remittance, and the clerk guesses which invoices it covers from the amount and the customer master.
Card fees land on the dealer because nobody set a surcharge rule, or the rule exists and the counter forgets it. The payment that came in on the 2nd is keyed on the 9th, so the AR Aging report is wrong for a week and the collections sweep calls a customer who already paid.
How it works.
- 1
The link is minted at send
Every collections note, statement and invoice email carries a payment link under your name, minted at send for that customer. The page shows the open invoices as Agility has them that morning, nothing more.
- 2
The customer picks and pays
Card or bank transfer. The customer ticks the invoices the payment covers, or pays on account; a surcharge or a convenience fee applies by your rule, shown before they confirm. A receipt goes out under your name.
- 3
The payment is prepared for Agility
Each payment lands with its remittance: the invoices picked, the amount per invoice, the fee, the card or bank reference. It is batched for the day and prepared for Agility in the form your team posts.
- 4
A person posts
Your team reviews the batch, reapplies anything the customer paid on account, and posts it. Lunica reads Agility the next night and closes the loop: the invoice shows paid, and the note that would have gone out doesn’t.
How it connects to Agility.
Lunica reads Agility’s open items and the customer master nightly through a read-only login to the Agility database, so the payment page shows the customer the invoices and balance as Agility had them that morning, on the account’s own terms. The payment page itself is hosted by Lunica under your name; the connection to Agility runs on one Windows server inside your network, or beside DMSi’s hosted Agility.
Nothing is posted to Agility on its own. Each payment and its remittance come back as an Agility import or API call where one exists, or keyed by your team from what Lunica prepared, and a person posts the batch. A receipt goes to the customer who paid; every other email that carries a link is a draft until a person sends it, or scheduled mail to the customers your team enrolled.
What a week looks like.
- Every note and statement your team sends can be paid from a phone.
- Each payment arrives with the invoices it covers, not a guess from the amount.
- Card fees follow your surcharge rule every time, without the counter remembering.
- A day’s payments batched and ready to post that afternoon, so the sweep stops calling customers who paid.
Questions
Does it post payments to Agility?
No. Each payment and its remittance are prepared for Agility, batched for the day, and your team posts them. Lunica reads Agility the next night to confirm.
Card or bank?
Both. Card, and bank transfer by ACH. Which is offered, and to whom, is a rule your team sets; a large job account can be bank-only.
Can we pass the card fee to the customer?
Yes, where your state allows it. A surcharge or a convenience fee is a rule in your policy, shown to the customer before they confirm, and never applied to a bank transfer.
Whose name is on the page?
Yours. The page, the receipt and the link are under your name. Lunica hosts the page; the connection to Agility runs on one Windows server inside your network, or beside DMSi’s hosted Agility.
What if a customer pays the wrong invoices?
The remittance shows what they picked, and your team can reapply before posting. Overpayments and payments on account are flagged in the batch.
Is card data kept on our server?
No. Card and bank details are entered on the hosted page and handled by the payment processor; they are not kept on the server beside Agility.
Can a customer pay without a link?
Yes. The payment page has a front door: an account number and an invoice or statement number bring up the open items the same way.
Does it need a server?
Lunica runs on one Windows server inside your network, or beside DMSi’s hosted Agility, set up and maintained by Lunica. It reads DMSi Agility through a read-only login to the Agility database. There is no inbound connection from outside your network.
What does Lunica read in Agility?
The customer master, open items and terms, purchase orders and receipts, the item master, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Agility?
Nothing lands in Agility without a person. What belongs in Agility goes back as an Agility import or API call where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Agility’s document attachments. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Online Payments is written for every system on the list. You’re reading the Agility version.
See it on your Agility data.
Thirty minutes. We walk the workflow on Agility data, then map it to yours.