Discover
Sales, collections, bank and gateway data as they are. In about two minutes, the recoverable total split by heading, before any contract.
Accounts Receivable
The money arrives.Proving what it settled is the work.
DataTwin reads what your customers sent you, what your banks and gateways report, and what your ERP recorded, then rebuilds one reconciliation position across all three. Every receipt matched to an invoice, every short payment given a reason, every partial cleared to the line rather than parked in an unapplied bucket. We start on your history, read-only, before anything in your systems changes.
- Sits above the ERP and billing you already run
- Read-only until you turn application on
- Full transaction population, not a sample
Everything that proves a receipt, in one place
Eight kinds of evidence, one position back
Everything that proves a receipt
Live process
Evidence that settles a receipt
- Digital screenshotsCustomer proof of payment
- Bank statementsEvery account, every entity
- NEFT and UPI refsBuried in free text
- ERP collectionsWhat the ledger shows
- Gateway settlementsGross, fees, net, per cycle
- Cheque deposit slipsScanned, often handwritten
- Cash deposit refsBranch slip against book
- Undeposited chequesStill sitting in a drawer
DataTwin
Reads every source and rebuilds the reconciliation
What comes back
- Sales vs collectionsBilled against received
- Collections vs bankAnd gateway settlements
- Sales vs taxationReturns against the books
- Cash appliedPartials cleared, not parked
One reconciliation position: every receipt matched to an invoice, every difference named, every unapplied amount aged.
Read-only to start — nothing changes in your billing system or your bank. Every stage runs on the same engine that powers the DARP Framework and FSCP: acquire, process, govern, report.
Discover · Assess · Recover
We start with the reconciliation, not the rollout
Nothing about how your team collects cash changes on day one. We take the history as it is, rebuild the position, and show you what is sitting unrecovered inside it. Prevention comes after the number is agreed.
Assess
After the contract, each heading is drilled to the last invoice and receipt, then prioritised with your team. It ends in a signed-off scope of what to recover.
Recover
Only the signed-off scope is worked. Short payments evidenced, unapplied cash applied, wrong entries corrected, each with its trail.
Six reconciliations, one position
From the evidence to the books
1
Part 1
The evidence arrives however the payer chose to send it
A receipt is only provable if you can see all of it. Customers send screenshots, banks report in their own format, gateways settle net of fees on their own cycle, and cheques sit in a drawer until someone deposits them. All of it comes in, and the original is kept.
Collect
Every source, one queue
Bank feeds, gateway settlement files, ERP extracts, branch slips and the screenshots customers email. The original is always kept.
- Statement, settlement and ledger extracts on a schedule you set
- Customer proof of payment collected from the mailbox it lands in
- Cheque and cash deposit slips scanned and read in the same pipeline
Read
Not retyped
References, dates, amounts and payer names read off each document, including handwriting and the narration a UPI reference hides in.
- Handwritten slips and photographs handled in the same pipeline
- Payment references pulled out of free-text narration fields
- Every field confidence-scored; low confidence goes to a person
Normalise
One shape, many banks
Each bank, gateway and entity formats differently. They are brought to one shape, so a receipt can be compared across all of them at once.
- Multi-bank, multi-entity and multi-currency handled together
- Gateway gross, fee and net split out of the settlement line
- Duplicate deposits recognised across channels and periods
2
Part 2
Sales against collections
Billed is not received. The gap between the two is where a receivable quietly ages into a write-off, and most of it is not bad debt. It is a deduction nobody evidenced, or a payment nobody applied.
Matched to the invoice
Receipt to bill, by line
Each receipt tested against open invoices on reference, amount, payer and date, including one payment covering many invoices.
- One receipt against many invoices, and many receipts against one
- Payer name variants resolved back to the same customer
- Advances and on-account receipts held separately, never forced
Short payments named
A reason, not a balance
Where the customer paid less, the shortfall is classified rather than left open: discount taken, deduction claimed, tax withheld, or simply short.
- Deductions traced to the claim or credit note behind them
- Tax withheld at source matched to the certificate
- Unexplained shortfalls flagged with invoice and evidence attached
Ageing that holds
What is really outstanding
Once receipts are applied properly the ageing changes. What remains is genuinely outstanding, not unapplied cash sitting in the wrong bucket.
- Ageing rebuilt on applied cash rather than open balances
- Disputed and deducted amounts separated from ordinary overdue
- Customer position consolidated across entities and currencies
3
Part 3
Collections against banking and payment gateways
For anyone selling through cards, wallets or a marketplace, the money in the bank is never the money on the order. Fees, refunds, chargebacks and settlement cycles all sit in between, and each one is a place a difference can hide.
Bank to book
Line by line, both ways
Every bank line matched to a recorded receipt in both directions, so credits with nothing behind them surface as clearly as entries with no credit.
- Credits in the bank with no entry in the books, listed
- Entries in the books with no bank credit, listed
- Timing differences aged rather than quietly netted away
Gateway settlement
Gross, fee, net
Settlement files unpacked into gross, fee and net, then tested against the orders in that cycle and the amount that actually reached the account.
- Commission and fee re-performed against the agreed rate
- Refunds and chargebacks matched back to the original order
- Cycles that settled late, short or partly, flagged as they occur
Cash and cheque
The slow instruments
Deposit slips read and matched to the branch credit, with instruments that were received but never banked surfaced by age.
- Deposit slip against branch credit, per entity and account
- Cheques received but never deposited, surfaced and aged
- Returned and bounced instruments traced back to the invoice
4
Part 4
Cash application, including partial clearing
Cash application is where reconciliations are usually lost. A payment that does not exactly equal an invoice gets parked, and once it is parked nobody goes back to it. Here the settled portion clears against the lines it settles, and only the genuine residue stays open.
Applied on evidence
Most of it, without a person
Receipts applied to invoices on what the evidence says: remittance advice, reference, amount, and how that customer has historically paid.
- Remittance advice read from email, PDF or portal upload
- Customer payment behaviour learned and used as evidence
- Every application recorded with the reason it was made
Partial clearing
Cleared to the line, not parked
Where a payment settles part of an invoice, the settled portion clears and the residue stays open carrying the reason it stayed open.
- Invoices cleared line by line rather than all or nothing
- Residue carried with the deduction or dispute that caused it
- Nothing pushed into a suspense or unapplied account by default
Exceptions to a person
Only what needs judgement
What the evidence does not settle goes to your team with the candidate invoices ranked and the difference already quantified.
- Ranked candidates, each with the reason it was proposed
- Write-off and tolerance limits applied from your own policy
- Approval captured against the receipt, not left in an email
5
Part 5
Sales against taxation
The revenue you filed and the revenue you booked should be the same number. When they are not, the difference is usually found by a tax authority rather than by you, and by then it carries interest.
Return to ledger
Filed against booked
Output tax in the returns compared to the revenue and tax recorded in the ledger, period by period and registration by registration.
- Every registration and entity reconciled separately
- Amendments tracked back to the period they correct
- Differences explained by invoice, not by a summary total
Rate and classification
Re-performed, not assumed
Rate, place of supply and classification re-performed on the invoice itself, rather than trusted from the master data that produced it.
- Rate and classification checked against item and customer
- Place of supply and export treatment tested per invoice
- Credit notes tested against the invoice they reverse
Withholding and credits
What the customer deducted
Tax the customer withheld matched to the certificate, so the credit gets claimed instead of sitting as an unexplained shortfall.
- Withholding matched to the certificate and the period
- Certificates not received chased with the invoice attached
- Credits claimed reconciled to what was actually deducted
6
Part 6
Revenue recognition
Invoiced is not earned. Where delivery, service periods or milestones sit between the two, the recognised number has to be built from what actually happened rather than from what was billed.
Performance obligations
Built from the contract
Recognition driven by delivery, service period or milestone as the contract defines it, not by the date the invoice happened to be raised.
- Subscription and service periods spread across periods earned
- Milestone and delivery evidence linked to the entry
- Contract changes carried through to the remaining schedule
Deferred and unbilled
Both sides visible
Billed ahead sits in deferred revenue, earned ahead sits as unbilled, and both roll forward with the entries that moved them.
- Deferred and unbilled balances rolled forward with movement
- Schedules released automatically as the period is earned
- Cut-off tested at period end rather than assumed
Evidence for audit
Assembled as it happens
Contract, delivery evidence and the entry are held against one another, so testing recognition is a read rather than a reconstruction.
- Contract, evidence and journal held together per obligation
- Every recognition entry traceable to what it recognised
- Sample testing replaced by full-population evidence
Prevent
Then the same rules run forward, on the money coming in
Prevent is not a second build. The rules that found the money are the rules that run on tomorrow’s transactions, across the whole money-in lifecycle. That is where a one-off recovery starts compounding.
- 1
Order to invoice
Checked against the order, the contract price and the tax treatment before it is sent.
- 2
Invoice to collection
Due dates, reminders and promises tracked per customer, with the evidence attached.
- 3
Collection to bank
Bank and gateway lines matched to receipts daily, not at year end.
- 4
Bank to application
Receipts applied and partials cleared as they land, so nothing parks in suspense.
- 5
Application to books
Revenue, tax and deferrals posted from what happened, with the journal read back.
Under the hood
What is actually doing the work
Specialised agents with narrow, defined duties, coordinated by an orchestration agent. Deterministic rules run wherever something posts to the books. Nothing posts because a model was confident.
Reading the proof
Remittance Agent
Remittance advices, deposit slips and payment screenshots read in one pipeline, handwriting included, with the reference pulled out of free text.
Applying the evidence
Matching Agent
Receipts matched on reference, amount, payer and behaviour, partials cleared to the line, and every application recorded with its reason.
Recognised, not assumed
Revenue Agent
Recognition built from delivery and service periods, deferrals rolled forward, and tax re-performed on the invoice before anything posts.
What changes
What changes, honestly stated
Not a longer list of features. A different distribution of who does what, and when a difference is found.
Workload
How AR runs today
Receipts matched to invoices by hand, with the difficult ones left unapplied
How it runs on DataTwin
Most receipts applied on evidence; your team works only the exceptions that need judgement
Cycle time
How AR runs today
Reconciliation done at month end, weeks after the money actually moved
How it runs on DataTwin
Bank, gateway and ledger agreed daily, so a difference is found while it can still be answered
Unapplied cash
How AR runs today
Parked in suspense and revisited when somebody has the time
How it runs on DataTwin
Cleared to the line as it lands, with the residue carrying the reason it stayed open
Short payments
How AR runs today
Aged and eventually written off, because nobody evidenced the deduction
How it runs on DataTwin
Classified at the receipt, with the claim, credit note or certificate behind it attached
Tax
How AR runs today
Differences between returns and books surface in an assessment
How it runs on DataTwin
Return against ledger reconciled every period, per registration, explained by invoice
Revenue
How AR runs today
Recognition rebuilt in a spreadsheet at period end
How it runs on DataTwin
Built from obligations as they are met, with deferred and unbilled rolling forward
Audit
How AR runs today
Sample testing, with correction long after the event
How it runs on DataTwin
Evidence assembled as the transaction happens, so testing is a read rather than a project
Start here
Before you change anything, find out what it has already cost you
Everything above is prevention; it stops the next one. It does nothing about the last three years, which are sitting in your receivables history right now. So we start there, read-only, before there is anything to sign.
2min
This is how long it takes to understand how much can be recovered.
Send us sales, collections, bank statements and gateway settlements. We test the full transaction population, not a sample, and come back with what is recoverable, split by heading. Before any contract.
- Sales and collections
- Bank statements and gateway settlements
- Full population tested
- What is recoverable, by heading
Cash never applied
Receipts never applied. Duplicate deposits. Advances never set off against a bill.
Money short-paid
Deductions with no claim. Discounts outside terms. Tax withheld, no certificate.
Fees and settlements
Commission above the agreed rate. Cycles settled short. Refunds never traced back.
Entries that are wrong
Revenue in the wrong period. Deferrals never released. Balances that agree only in total.
We run these reconciliations for retail, edtech, manufacturing and pharma finance teams. The shape of the evidence differs in each; the questions do not.