Receivables operations, from ageing to resolution
Run the whole receivables follow-up book with clearer control.
DueCurrent connects portfolio health, ageing, next-action state, promises, disputes, protected accounts, and coverage analytics without sending messages or moving money.
The DueCurrent platform
One working system for the whole operation.
Each module answers a different question. Together they give the team a shared record of what exists, what needs attention, who decides, and what happened next.
Portfolio
See every normalized account and invoice state in one controlled working view.
Ageing
Review due-period and balance bands without exposing exact values in the public site.
Next actions
Keep the buyer-approved follow-up stage and accountable role visible.
Promises
Separate reported commitments from routine follow-up so context is not lost.
Disputes
Protect disputed and sensitive accounts from ordinary treatment until human review.
Coverage analytics
Follow eligible-record coverage and unresolved states across each review period.
Where the work gets stuck
The system is rarely the whole problem.
For b2b smb finance teams handling growing invoice volume with a small ar team.
Invoices and promises fall through when spreadsheets, calendars, accounting, and customer records are disconnected.
Basic dunning automates the easy reminders but leaves non-response, disputes, and high-value accounts for manual triage.
Bad automation can double-send, misclassify, or use the wrong tone with an important customer.
AR Follow-up Management · managed delivery
A daily collector list with context, the next action, and an editable draft.
We keep the records, definitions, checks, exceptions, and review pack moving across the six-module model. Your team keeps every decision that carries financial, legal, operational, or customer impact.
- One prioritized queue across due date, value, promise, dispute, and response state
- Context-aware drafts that follow a buyer-approved tone and escalation policy
- Human review for disputes, credit holds, sensitive accounts, and ambiguous payment state
Evaluate the product
Everything you need to decide whether this fits.
Explore the application model, exact deliverable, input boundary, rollout, and trade-offs before you share operational data.
Product tour
Move through all six modules in a realistic workspace built with fictional data.
02Capabilities
See the repeatable work behind every operating cycle.
03Sample deliverable
Walk through the reviewable output your team receives.
04Implementation
See the four checkpoints, responsibilities, and acceptance criteria.
05Data requirements
Review the accepted fields, excluded data, and handling lifecycle.
06Full FAQ
Get direct answers on capacity, switching, security, and service boundaries.
How it works
A complete operating view without a drawn-out rollout.
Start with the working records you already have. We map them into the connected model, run the review cycle, and improve the control record with your team.
- 1Step 1
Define reminder stages, protected accounts, and mandatory human-review states.
- 2Step 2
Use a sanitized receivables export and historical communication-state metadata.
- 3Step 3
Run a two-week supervised queue and measure follow-up coverage and exceptions.
Why we work this way
We started with the complaints, not a feature list.
Public operator discussions showed us where existing tools create extra work. Those recurring problems now shape the service and every client deliverable.
Excel · Outlook · HighRadius · BlackLine · Sidetrade
An AR operator described disconnected spreadsheets, ignored calendar reminders, misplaced correspondence, manual reconciliation, and a high-value invoice missed during staff absence.
What we changed: Unify follow-up state and promises in one queue, give every next action an owner, and preserve supervised escalation.
Read the source notesNetSuite · Automated dunning tools
A high-volume AR team used automated reminders for routine work but reserved human attention for non-response, credit holds, reconciliation, and high-value accounts; another operator reported double-sends during setup.
What we changed: Automate prioritization and drafts first, protect sensitive states, and measure error rates before enabling any send automation.
Read the source notesUseful before you hire us
Put the workflow into a register your team can actually run.
The human-safe ar escalation policy is a five-tab Excel workbook with a ready-to-fill register, worked fictional example, weekly review agenda, and metric dictionary.
Download the Excel workbook- 01Separate routine reminders from disputes and relationship-sensitive accounts
- 02Track promises to pay as dated commitments
- 03Require review for credit holds, legal language, and ambiguous balances
- 04Audit every send decision, source state, and approved template
Monthly service plans
Choose the plan that matches the workload.
Every plan is a month-to-month managed service with a generous, published capacity, a named cadence, and human review. The middle plan is the practical fit for most teams. Prices are in US dollars and exclude applicable sales tax.
Our promiseNo annual contract, card collection, or automatic sending. You approve the communication policy and every sensitive escalation. We take on no more than 5 new clients at a time, so every delivery gets a human review.
Compare the detailsStart with fit
Tell us where the work gets stuck.
Share the situation in general terms. We will review it personally and tell you which plan fits. No card or operational files are needed.
The practical details
Questions people ask before we start.
Will it send emails automatically?+
The service drafts only. Automatic sending is considered only for approved low-risk states after error rates are measured.
Does it replace our accounting system?+
No. It is a read-only prioritization and communication layer.
How do you protect customer relationships?+
Your team defines protected accounts, tone, quiet periods, escalation rules, and mandatory review states.
Can it handle disputes?+
It can classify and summarize a dispute for a collector; resolution and any legal or commercial decision remain human.
What do we receive each cycle?+
A human-reviewed receivables follow-up control pack, the supporting exception log, and the plan-specific review cadence shown on the pricing page.
What do you need from us?+
A named owner, the agreed definitions, and buyer-normalized B2B invoice-state and event metadata. The public inquiry form accepts none of that operational data.