Collections from the phone with the real customer account
Updated:
With CoreDLS a salesperson or collector registers the receipt from the phone against the customer account and sees the real balance during the visit. Without signal the receipt stays on the phone and goes out by itself when the connection returns; at the end of the day the close is built per salesperson.
Collecting in the field gets complicated when the balance on screen is not the right one: the customer disputes it, the receipt is entered at night and the account is updated late. CoreDLS puts the real balance and the receipt in the same place, the phone of the person collecting.
What a collection looks like, step by step
- The collector opens the customer record: account statement, history and credit status, with the real balance held by the system.
- They register the receipt against the customer account, during the visit.
- The receipt is saved on the phone. With signal it goes out right away; without it, it is queued and goes out by itself when the connection returns.
- Sync is by differences: only what changed comes down, not the whole database, so the balance updates without waiting for a long download.
- At the end of the day, the close report is built per salesperson.
Where the balance on screen comes from
If the company uses CoreDLS as an extension of its ERP, the balance comes from the customer accounts of that system: the CoreDLS service reads what it needs and brings it to the phone. What is entered from the phone is left in CoreDLS own tables, and the ERP processes them when it wants; CoreDLS does not write to the ERP tables.
If the company uses the CoreDLS native ERP, customer accounts and collections live in the same system: up-to-date balances, collection management, late-payment interest and direct debit.
What changes for each role
| Role | What they do from the phone |
|---|---|
| Collector | Walks the list of customers, sees the real balance, registers receipts against the customer account and closes the day. |
| Salesperson | Before taking an order, sees the customer credit status; if the order exceeds the limit, it waits for authorization. |
| Supervisor or administration | Sees the end-of-day close per salesperson and defines as data who authorizes and when to warn or block. |
With voice and with permissions
- The hands-free voice assistant also works for collection receipts: the receipt is dictated, it reads the summary and registers when confirmed with PIN or fingerprint.
- Each person sees only the modules enabled for them; permissions are set per module, so collections can be open to the collector and closed to other roles.
- If someone loses the phone, the device is revoked from the administration and the session is closed.
Frequently asked questions
- Can I collect without signal?
- Yes. The receipt is saved on the phone, queued and sent by itself when the connection returns.
- Is the balance the collector sees the real one?
- It is the one in the company system customer account, synced by differences. With signal it updates on sync; without signal the last balance saved on the phone is shown.
- Does CoreDLS write to my ERP tables when a receipt is registered?
- No. The receipt stays in CoreDLS own tables and the customer system processes it when it wants.
- Can I see how much each salesperson collected?
- Yes. The end-of-day close is built per salesperson.
- Does it work if the company has no ERP?
- Yes. The CoreDLS native ERP includes customer accounts and collections, with up-to-date balances, late-payment interest and direct debit. Fiscal invoicing is for Argentina only.
You can request a half-hour demo: the app is shown with test data and technical questions are answered on the same call.