Features

A system that stays organized when transactions get messy.

Smooth transactions are easy — any app can record them. The real test comes when things aren’t ideal: items come back, invoices aren’t fully paid, parts turn out damaged, supplier claims stall, or a ticket needs a correction. This is exactly where “simple” apps give up and tell the cashier to “sort it out” — and from there, stock, receivables, and reports quietly drift out of sync.

Automan handles those cases with repair, sales, and purchase returns, damaged stock, supplier warranty claims, automatic debt offsets, voids, and traceable corrections. The goal isn’t just fixing an invoice — it’s keeping stock, cash, receivables, payables, and reports consistent after the correction.

Four return paths in one system

  • Repair returns — a repaired unit comes back; costs, parts, and unit status adjust along the repair workflow.
  • Sales returns — a customer returns goods; stock is restored and the value adjusts receivables or cash.
  • Purchase returns — you send goods back to the supplier; stock decreases and your payable to the supplier is offset automatically.
  • Damaged stock & supplier claims — defective parts enter a Damaged Stock pool, then get claimed to the supplier with proof of origin.

Because all four adjust stock, cash, and payables/receivables automatically, there’s nothing to re-enter elsewhere — and reports stay consistent.

Automan return flow offsetting debt before issuing a refund Return on an unpaid invoice: the return value offsets the balance first, and only the surplus is refunded.

Returns on an unpaid invoice

This is the case that most often confuses a cashier. A customer returns goods, but the invoice isn’t fully paid. In a basic app, the cashier has to guess: offset the balance, or refund cash?

Automan resolves it with a consistent rule: the return value offsets the outstanding balance first. If there’s a surplus, it becomes a cash refund. The “Paid / Unpaid” status of the original transaction is recalculated automatically. The cashier doesn’t guess, and the shop’s receivables stay correct.

Damaged stock & supplier warranty claims

A damaged part doesn’t automatically mean a loss. As long as its purchase origin is recorded through spare parts inventory, a defective part can enter Damaged Stock and be claimed to the supplier. Automan keeps the part origin (purchase batch) and claim status, so a damaged part has a recovery path — instead of simply vanishing from the shelf.

Corrections that leave a trail, not a silent delete

Input mistakes will happen. The difference is that Automan doesn’t offer a “delete” button that erases the trail. Corrections go through a flow that keeps a history — what changed, from which value to which, and by whom. Paired with access control, the owner can fix mistakes without opening the door to fraud.

Why this decides whether you can trust your reports

A shop can look tidy as long as every transaction is smooth. The problem is that the messy cases decide whether the reports can be trusted. A return that’s only crossed out on paper makes stock and receivables slowly drift, and by month-end the numbers no longer match the cash drawer. With traceable returns, claims, and corrections, every fix flows cleanly into repair shop accounting — so the reports stay good enough to make decisions on. See the returns workflow demo to watch it in action.

FAQ

What happens with a return on an unpaid invoice?
The return value offsets the outstanding balance first. If there’s a surplus, it becomes a cash refund. The original transaction’s status is recalculated automatically — no manual reconciliation.
Does a damaged part become an immediate loss?
Not necessarily. A claimable damaged part goes into Damaged Stock, then gets claimed to the supplier through the warranty-claim flow. The part origin and claim process are recorded, so a damaged part isn’t written off silently.
Which types of returns are supported?
Four paths: repair returns, sales returns, purchase returns (back to the supplier), plus damaged stock and supplier warranty claims. Each one adjusts stock, cash, and payables/receivables automatically.
If an invoice is wrong, why not just delete it?
Deleting a transaction erases the trail and invites fraud. Automan uses a correction flow that keeps a history, so mistakes can be fixed without destroying evidence — the owner sees what changed and who changed it.

Already know the problem?

See the workflow demo that matches it.