CLIENT
NoWALL
GEOGRAPHY
170+ countries
MIGRATION
No-code stack → Odoo
STATUS
Live, running the daily flow
The rules the system enforces
Daily
a hard day close - after it, only a single named authority can touch yesterday’s records
Δ alarm
a defined delta threshold - any larger gap between sent and received fires an alarm
Δ = 0
the reconciliation target: fact balance vs. ledger balance, checked live on every entry
0 deletes
nothing is ever deleted - cancelled deals and operations go to the archive, fully logged
What they came with
Deals in one no-code database, cash flow in another, balances in a third - held together by automation scripts and manual discipline.
✕Double paymentNothing stops two people from paying the same client - only attention and luck
✕Silent editsYesterday’s records can be changed today, by anyone, with no trace
✕Balance driftThe ledger and the real bank/wallet balances quietly diverge until someone counts by hand
✕Held by disciplineControls are rules people try to follow, not things the system enforces - one busy evening breaks them
“It worked - as long as nobody ever made the mistake the system couldn’t catch.”
One deal, one chain
A deal is born in a Telegram chat and dies only when the money has landed.
Every status change in the pipeline creates or updates its linked cash-flow operation automatically. Watch the pulse travel the chain - that is one deal moving through the system.
Telegram chat→
Deal created→
Expected income→
Income→
Distribution→
Sending→
Expense→
Deal closed→
Telegram · client chat●
Need to pay an invoice in the EU, today if possible
Payment received - sending within 4 hours ✓
Sent. Confirmation attached.
two-way
⇄
sync
Odoo · Deal Nº 4180live
StatusIn progress
Claimed byOperator 1 - only owner reassigns
AttributionPromo + UTM - locked once set
Cash-flow opE-0412 · auto-created
What we built
The operational core rebuilt on Odoo - workflows the team knew, controls made structural instead of behavioral.
✳︎
Telegram-native deal pipeline
✳︎
Chat platform two-way sync
✳︎
Cash-flow ledger with lifecycle
✳︎
Live treasury reconciliation
✳︎
Financial alarms & escalation
✳︎
Full audit trail & archive
Clients never see a form - they chat. A manager tags a conversation and the deal materializes in Odoo with the client name, dialog link and UTM attribution; status changes message the client back in the same chat. Every currency movement is a first-class operation with an owner, a status lifecycle and a hard link to its deal. Client debt is computed live across all in-progress payouts and converted to a virtual "To Send" position in USDT. USDT rates refresh on a fixed daily schedule; day-end balance snapshots are frozen; a weekly verification loop gives the auditor dated sign-offs. In a payments business, the ERP isn’t back office - it is the product’s backbone.
treasury · reconciled live
Fact balance
128 450
Ledger balance
128 450
checked on every entry
Δ = 0
DAY CLOSE
Same hour, daily
After it, only a single named authority can touch yesterday's records - and every change is logged.
Guardrails, by design
The rules that used to live in red text and discipline are now physics of the system.
Things that cannot happen - rather than things people try not to do.
R-01 · No double-send
One operation, one owner
An operation claimed by one operator is visibly owned - and only the responsible person can reassign it. Two people can no longer pay the same client.
R-02 · No backdating
History freezes at the daily close
Records are editable until the day close; after that, only a single named authority can change history - and every such change is logged.
R-03 · No silent edits
Every change carries a name
Who, when, previous value and new value on every field change. Creation timestamps and authorship are read-only for regular staff.
R-04 · No deletions
Archive instead of delete
Deals and operations are never deleted - cancellations move to a fully searchable archive with their complete history intact.
R-05 · No unapproved spend
Budget waits for a name
Budget operations don’t count and can’t execute until a single named verifier approves - then a task lands on the account’s operator.
R-06 · No stale problems
Stuck too long? Escalated.
Timers on every in-work status; a payout stuck past its SLA notifies the operations director with an "assign responsible" task and deadline.
What changed
0
ways to send a payment twice - ownership and status lifecycle make it structurally impossible
Daily
books close every day; rates refresh and balance snapshots freeze at the same hour
Δ = 0
fact vs. ledger reconciliation checked continuously - on every single entry
100%
of history logged: every field change, every cancellation, every sign-off, forever searchable
✳︎
“In our business, speed is the sales pitch - but control is the business. We needed a system where a payment physically can’t be sent twice and yesterday’s numbers physically can’t change. That’s exactly what we got.”
NoWALL
If your operations are the product, build them like one.
We move fast-running businesses off spreadsheets and no-code stacks onto systems with real controls - without breaking the workflows your team already trusts.
Book a Demo
Yerevan · Serving CH / FR / DE / EU
English · French · Russian · Armenian
English · French · Russian · Armenian
★4.9/5on Clutch
START
Book a Demo
© 2026 ERPSWISS. Official Odoo Partner.
Weeks, not months.