Dymico, the platform i3 builds and runs client software on
This page follows that one change from the email to the audit trail. Nothing about it is unusual, and that is the point: on Dymico, a change like this is an ordinary afternoon's work rather than a project.
The auditors had flagged large invoices approved by one person. The finance lead wrote to the developer who looks after their system.
Can we make invoices over R50 000 need a second sign-off? Ideally before month-end.
Sent to their i3 developerWhy it starts here. The person who asked is the person who will approve it. No backlog, no change-request form in between.
Invoices, users, roles and the approval screen all live in the same application. The developer read the real invoice code and its history, not a diagram of it, and found the one place the rule belongs.
What Dymico did. Code, data and version history sit in one place, so nothing had to be integrated or exported to answer the question.
No new system, no new screen. The rule sits next to the invoice it protects, with a test that proves it.
// large invoices need two different approvers beforeApprove: { session -> if (total > 50000 && approvers.unique().size() < 2) throw new Exception('Needs a second sign-off') }
On AI. An assistant may draft a change like this. A named person reads it, saves it and owns it, and the record says who.
The finance team kept working in the live app. The change ran on a separate branch, where the developer and Thandi could both try it.
There was no release window and no weekend deploy. Once Thandi approved it, the live app ran the new rule, and users saw it on their next invoice.
Overnight, the threshold turned out to catch too many routine orders. Finance asked for R100 000 instead. The developer went back to Monday's version in one step, then changed the number.
What Dymico did. Going back is a normal step, not an incident. The rolled-back version stays in the history.
Who asked, who changed it, who approved it, when it went live and when it was rolled back: every step on this page is in the record, with a name and a time against it. Nobody had to write a report.
Under the hood
To be clear
i3 developers write and own the changes. You get software built properly, without having to learn a builder.
We build what we ship, run it and look after it for as long as you want us to.
It connects to the accounting, CRM and identity systems you already use. Start where the value is.
30-minute walkthrough
Tell us the rule, report or screen you have been asking for. We will show you how it would go on Dymico, from email to audit trail.
i3 designs, builds and looks after everything we put on the platform.