Multi-entity One ledger, four companies
MT940 / MT941 Automatic cash application
Role-scoped Down to one RM portfolio
Under 15 days To a live pilot entity
Ageing tells you how old. It never tells you why

Know why every rupee is still outstanding.

Not the ageing bucket — the reason. Never despatched. No proof of delivery. Deduction taken without advice. Promise broken twice. Arlens holds the answer against every open invoice, so the review meeting is about decisions rather than about who is pulling the report.

6–12 days
DSO reduction, two quarters
1.6–3.3%
Of annual revenue released
90%+
Receipts cleared without touch
15 days
To implement, start to live
Built for receivables in
Features

Built for the month-end you actually have.

Not a ledger that records the receivable — the working layer that collects it, and the evidence trail to prove every step.

Dunning that runs itself

Four ladders — standard commercial, government and PSU, SME, and key account — each with its own rungs, tone, contact role and escalation path. One consolidated letter per customer, not one per invoice. Eleven suppression rules stop it chasing a disputed bill or a promise that has not yet fallen due.

Invoice despatch with proof of delivery

Send the invoice from the application with the signed challan attached, and log the date, channel and recipient. When a customer says they never received the bill, you answer with a record instead of a shrug.

Advice to clearing entry, posted in the ERP

MT940 feeds bring the money in; the customer's remittance advice says which invoices it covers and what was withheld. Arlens matches both and posts a balanced clearing entry to the ERP — bank debited, customer control credited, TDS and each deduction to its own account. Nothing posts unless the legs balance to zero.

Fourteen-week cash forecast

Direct method, three scenarios, phased operating outflows and a covenant floor. Every open invoice is weighted by ageing, dispute status, despatch and delivery evidence — not by wishful thinking.

Customer due diligence

A seven-parameter scorecard maps to a limit multiplier, and the multiplier applied to tangible net worth gives the unsecured ceiling. Read alongside what your own ledger says about how long they actually take to pay.

Role-based access that means something

Two axes: what a role may do, and which rows it may see. Sign in as a relationship manager and you see your own portfolio — a materially different book, not a filtered view of everyone else's.

How it works

Import to clear, without leaving the system.

Five steps from the sales register to a cleared invoice with an ERP document number against it.

  1. Import

    Sales register from Excel or a nightly ERP sync. Validation runs row by row before anything is committed.

  2. Despatch

    Invoice out with proof of delivery attached, logged against the invoice with date, channel and recipient.

  3. Pursue

    Dunning ladders, a ranked worklist, promises to pay, and disputes routed to the function that owns them.

  4. Match

    Bank credit meets the remittance advice. Deductions are coded, TDS separated, unadvised variances flagged.

  5. Clear

    A balanced clearing entry posts to the ERP and the invoices come off the ledger with a document number against them.

Not a prototype

Open any screen. It is the real application.

The demonstration below runs the same code as a production deployment — real filters, real Excel downloads, real dunning ladders. Sign in as any of the four roles and the book changes underneath you.

Four roles, four different books

Every demonstration account uses the password Kredo@456. Sign in as the relationship manager and then as the finance admin on the same screen — the row-level scoping is the part that is hard to convey in a slide and obvious in thirty seconds of clicking.

Use cases

Where Arlens earns its place.

The situations Indian finance teams deal with every month — several entities on one ledger, payment runs that ignore your due date, deductions taken without advice.

Finance

Reducing DSO

Ten instrumented levers, measured weekly.

Treasury

Cash visibility

14-week forecast against a covenant floor.

Credit

Limit governance

Due diligence scoring before the order ships.

Audit

Evidence on demand

Read-only role, full trail, watermarked exports.

Shared services

Cash application

Advice to ERP clearing entry, untouched.

Why Arlens

What you get that a spreadsheet cannot give you.

Most receivables work sits between an ERP that records it and a spreadsheet that chases it. This is what closes that gap.

Capability Arlens ERP module or spreadsheet
Dunning Four strategies, 11 suppression rules, scheduled One reminder template, sent by hand
Reminder volume One consolidated letter per customer One email per open invoice
Proof of delivery Attached to the invoice, sent with reminders In a shared drive, if at all
Cash application MT940 feed, five-rule matching ladder Manual, from a bank statement PDF
Remittance advice Parsed, coded, matched to open items Read off a PDF and keyed by hand
Clearing entry in the ERP Balanced entry posted, TDS and deductions split Journal typed by an accountant
Cash forecast 14 weeks, three scenarios, covenant floor A spreadsheet someone updates on Fridays
Data scope by role Capability plus row-level portfolio scoping Everyone sees everything
Excel exports 34 workbooks, filters and subtotals carried Copy, paste, reformat
Deployment On-premise or hosted, no vendor lock-in Per-seat SaaS or a costly ERP licence
The business case

What a day of DSO is worth to you.

Receivables software is bought on one number: cash released, against what it costs to run. Here is the arithmetic on a mid-sized book — run it on your own figures before you believe it.

0 days
DSO removed — mid-case
0 %
Of revenue back in working capital
0 %
Cash applied straight through
0 x
Return on annual licence

Modelled on a ₹1,000 crore book billing ₹83 crore a month at 55 days DSO. One day of DSO on that book is ₹2.7 crore of cash. The ranges come from the levers Arlens instruments — invoice delivery lag, cash application, dispute routing, promise discipline — not from a claimed customer average. Your own baseline decides the outcome, and the pilot measures it before you commit.

Pricing

Priced per entity, not per invoice.

Your book grows without your licence cost following it. Start with a free pilot on one entity and your own open items — if it does not move DSO, you have lost nothing but the import.

Starter

A single legal entity finding its feet.

₹0
Pilot, 60 days
  • One legal entity
  • Sales register and ageing
  • Invoice despatch and POD
  • Manual bank statement upload
  • Up to 5 users
Start the pilot

Enterprise

Multi-entity groups with a treasury function.

₹1,25,000
per month
  • Unlimited legal entities
  • Customer due diligence module
  • Cash flow forecast and scenarios
  • Two-way ERP sync
  • Single sign-on and IP allow-list
  • Named customer success manager
Talk to us

On-premise

Your servers, your database, your rules.

Licence
annual, per entity
  • Deploy inside your network
  • Full source, no obfuscation
  • No data leaves your estate
  • Runs on standard infrastructure
  • Implementation and handover
Request terms
FAQ

The questions finance teams ask first.

How is this different from the receivables module in our ERP?
An ERP records the receivable accurately; it rarely helps you collect it. Arlens adds the working layer on top — dunning ladders that run unattended, proof of delivery attached to the invoice, a ranked worklist, promise tracking, dispute routing, and a cash forecast weighted by how likely each invoice actually is to be paid. It reads from your ERP and posts receipts back, so it complements the system of record rather than replacing it.
What does the dunning engine actually do?
Four ladders ship, matched to customer type by assignment rules. Each rung fires at an offset from the due date with its own template, tone, contact role and escalation path. Reminders are consolidated to one letter per customer carrying the full invoice schedule, so a customer with fifteen open invoices receives one email rather than fifteen. Eleven suppression rules run first — a disputed invoice, an unexpired promise, a customer on hold, or an invoice that was never despatched will not be chased.
What do we have to give you before the pilot starts?
An open-items extract and a customer master — the two reports your ERP already produces. Nothing else. We load them, agree the ageing buckets and the dunning ladders with your collections lead, and you are looking at your own book inside Arlens. No integration work is needed for the pilot; the ERP connector comes later, once the process is agreed and worth automating.
How does role-based access work?
On two axes. Capability answers what a role may do; data scope answers which rows it may see. A relationship manager is scoped to their own portfolio, so two managers signed in at once see entirely different books. Finance Admins see the entities assigned to them, and the read-only Auditor role sees everything but can change nothing.
What happens between the bank credit and the invoice being cleared?
The bank credit tells you money arrived; it does not tell you what it settles. The customer's remittance advice does — which invoices, what was withheld, and how much tax was deducted at source. Arlens parses the advice, matches it against open items, codes every deduction, and builds a clearing document: bank debited with what actually arrived, customer control credited with the full invoice value, and the difference posted to TDS receivable and the relevant deduction accounts. That document is posted to the ERP and returns a document number. It will not post if the legs do not balance to zero, if the bank credit differs from the advice beyond tolerance, or if a deduction needs a credit note that has not been approved — those go to an exception queue with the reason attached rather than into a suspense account.
How are customer deductions handled?
A deduction is a claim, not a payment shortfall, so each one is coded — rate difference, short quantity, quality rejection, freight recovered, liquidated damages, settlement discount, GST mismatch, retention, rounding. TDS and approved discounts clear automatically. Freight and tax mismatches are held for review. Anything contestable raises a dispute against the owning function with an SLA clock, so it is chased by the person who can actually resolve it rather than sitting in the collections queue.
Which banks and ERPs are supported?
Any bank that delivers SWIFT MT940, MT941 or ISO 20022 camt.053 — which covers every major Indian corporate bank — plus manual XLSX and CSV upload for the rest. The ERP connector ships configured for SAP S/4HANA over OData, with inbound invoices and customers and outbound receipt vouchers. Other systems connect through the same import and export contracts.
Can we run it on our own servers?
Yes. Arlens installs on standard web infrastructure your IT team already runs, with no specialist platform, no container orchestration and no external service dependency. The on-premise licence ships the full readable source, so nothing about your receivables book has to leave your network — which is usually the deciding factor for groups whose customer terms and margins sit inside that data.
How long does implementation take?
A pilot on one entity with imported open items typically runs inside two weeks. The work is rarely technical — it is agreeing the ageing buckets, the dunning ladders, who owns which customer, and which contact receives which class of letter. Groups with several entities and an ERP integration should plan for six to eight weeks.

The best AI assistant. Yours in 30 seconds.

Free forever to start. No credit card. Cancel anytime — but you won't want to.