Customer deposit balances being reviewed against open orders
Receivables · Deposits

A Deposit Is Not a Receivable

Money taken before delivery is a liability that behaves like a receivable in every report anybody looks at.

Key Takeaways
  • A deposit is a liability until the obligation behind it is met, and most systems record it in a way that makes that easy to forget.
  • Unapplied deposits accumulate when the payment and the order are captured in different places with different references.
  • Aged deposits create two problems at once: an overstated liability and an unclaimed property question a few years later.
  • Partial fulfilment is where the manual process breaks, because releasing part of a deposit needs a decision nobody scheduled.
  • ChatFin matches deposits to orders, releases them as fulfilment happens, and ages whatever cannot be matched.

Taking money before delivering is good commercial practice and poor accounting hygiene, because the resulting balance has no natural owner.

Sales considers the deal done, operations tracks the order, and finance holds a liability account that grows steadily and gets reviewed when somebody asks why it is so large.

This page covers where deposits lose their connection to the order, what an aged unapplied balance actually indicates, and how a governed agent can release them in the period the obligation is satisfied.

Customer DepositsPrepaymentsContract LiabilitiesOrder FulfilmentAgeingRevenue Timing
Diagram of an AI agent layer running deposit application above the ERP
The agent sits above your ERP. the ERP stays where it is.
01

Where the link breaks

A deposit is meaningful only in relation to something promised. When the payment reference does not carry the order number, that relationship exists only in somebody's memory of the deal.

Long lead times make it worse. By the time the goods ship or the project starts, the person who agreed the deposit may have moved on and the order may have been revised twice.

Reference mismatch: Payments arriving against a quotation number, a contract name or nothing at all rather than the order.
Order revisions: Deposits taken against a scope that changed, leaving the amount right and the linkage wrong.
Multiple intake channels: Card, wire and cheque deposits captured in different systems with no common identifier.
02

Partial fulfilment is the hard case

Full delivery makes release obvious. Partial delivery requires deciding how much of the deposit has been earned, which is a judgment tied to the contract rather than to the shipment.

Most teams handle this by waiting for full completion, which overstates the liability for months and understates revenue in exactly the periods the work was done.

Holding the release basis alongside the deposit turns that into a rule that runs automatically and a judgment that only gets made once.

A finance team working on deposit application
A deposit only means something in relation to what was promised. Photo by Mikhail Nilov via Pexels
03

A liability recorded by whoever took the money

Deposits arrive through several doors: a wire against a quotation, a card payment at order entry, a cheque with a signed contract. Each lands in a different system with a different reference, and the link back to the order that will consume it is made by a person or not at all.

Read

What the agent needs to see

Ledger detail from the ERP, plus deposit receipts and remittances taken from the source they arrive in, read through the API surface your ERP already exposes rather than the database.

Write

What it should be allowed to do

Prepare a deposit release entry and an aged unapplied list and leave it for the AR manager to approve. Reading widely and writing narrowly is the line that keeps this safe.

That division matters more than which model sits underneath. An agent that can read deposit receipts and remittances, sales orders and delivery records and the deposit liability ledger while posting only through the validated path a person uses gives you the coverage without handing over the ledger, and ChatFin works that way on every ERP it connects to.

04

What an aged deposit is telling you

A deposit sitting unapplied for a year usually means one of three things: the order was cancelled and never refunded, the deposit was applied manually elsewhere and this record was never cleared, or the customer overpaid.

All three are worth resolving, and two of them are customer money you may eventually be obliged to report as unclaimed property.

Ageing from the receipt date rather than the last touch date is what makes this visible, because a balance that gets re-referenced during clean up work looks new again.

Governed agent actions compared with unattended automation for deposit application
Prepared and approved, not posted blind.
05

The reporting side

Deposits and prepayments are contract liabilities, and the movement in that balance is something readers of your accounts pay attention to as an indicator of forward activity.

A balance that is accurate and aged supports that story. A balance that includes years of unresolved items does the opposite, and it invites questions in exactly the wrong place.

Agent

Matching and ageing

Deposits tied to orders across intake channels, released as fulfilment happens, unmatched items aged from receipt.

Human

Judgment and customer contact

Release basis on partial delivery, refund decisions, and any conversation about an overpayment.

06

Releasing a deposit is recognising revenue

Applying a deposit moves a balance out of liabilities and usually into revenue, which is the last place for an unexplained automatic posting. Each application arrives with the deposit, the order and the delivery evidence attached for the AR manager to approve.

The record kept against customer deposits is deliberately plain: the deposit receipts and remittances the agent read, the reasoning it applied, the draft it produced, what the AR manager changed, and the moment it posted. That is the trail an auditor asks for, and it is assembled while the work happens rather than reconstructed afterwards.

The wider argument for that design sits in why finance AI should read widely but write narrowly and connecting without database credentials.


A is prepared, reviewed and approved before it posts, and every step is logged from the source document to the entry. deposit release entry and an aged unapplied list
07

How ChatFin runs deposit application

Deposits are matched to the orders they were taken against and released as fulfilment happens rather than when somebody notices. Anything unmatched is aged from the date the money arrived, which is the number that tells you whether the balance is a liability or a windfall waiting to be found.

It connects to the ERP, the order management system and the billing system through the interfaces those systems already expose, which keeps the security review short and the setup measured in days rather than quarters.

Match deposit to order

Payments tied to the quotation, order or contract they were taken against, across every intake channel.

Track fulfilment

Delivery, milestone or service completion monitored so release happens when the obligation is met.

Age the unapplied balance

Deposits with no matching order or no progress aged from receipt with the customer identified.

Draft release and refund entries

Applications and refund proposals prepared with the deposit and delivery evidence attached.

A first run is usually read only against a period you have already closed, so you can compare what the agent found against what your team found before anything is trusted with a deposit release entry and an aged unapplied list.

Adding the workflow after this one costs no second integration, because NetSuite, SAP Business One, Acumatica and the other supported systems are already connected on the same terms.

"

A deposit sitting unapplied for a year is either a cancelled order, a duplicate, or somebody else's money.

ChatFin
The wider set of ChatFin finance agents that run on the same connection
One connection, one approval pattern, many workflows.

Frequently Asked Questions

Why not just release deposits when the invoice is raised?

That works when invoicing and fulfilment coincide. Where deposits are taken against long lead time orders, milestones or partial shipments, invoice timing and obligation satisfaction diverge, which is exactly the case the manual process handles worst.

Can it refund a customer automatically?

No. Refunds are drafted with the deposit history and the cancellation evidence attached, and the payment stays a human decision. Returning money to a customer is a commercial conversation as much as an accounting one.

How does it handle deposits with no order reference?

They are matched on customer, amount and timing against open orders and contracts, and anything with no plausible match is aged and surfaced with the remittance detail so somebody can resolve it while the trail is still warm.

This page is general information about finance operations and software, not legal, accounting, or tax advice. Confirm treatment for your own entity with your advisors.

Release it in the right period

Tie every deposit to the obligation behind it.

ChatFin matches deposits to the orders they were taken against, releases them as fulfilment happens, and ages anything that cannot be matched from the date the money arrived.

Applications and refunds are drafted with the deposit and delivery evidence attached, so the liability reflects what you still owe.

Book a Demo
See it on your own data

See your deposit balance matched and aged.

Bring your deposit liability detail and a period of orders. We will show what matches, what has been earned, and what has been sitting since the money arrived.

✓Runs on the ERP you already have, on your current version, with no database credentials
✓Reads through the governed API surface your ERP already exposes and writes back only approved drafts
✓Full audit trail from prompt to prepared payload on every action
Schedule a Demo
Confidential & private
Hero photograph by Tima Miroshnichenko, free to use under the Pexels License (commercial use permitted, attribution not required). Inline photograph by Mikhail Nilov under the same licence. Product visuals © ChatFin.