The platform
A process that can’t lose its place.
Onboarding a trade relationship takes weeks and touches a dozen people across three companies. Most of the delay isn’t decision-making — it’s the handoffs. TerraTrade runs the whole thing as one durable process, so the work never stalls quietly and every decision leaves a record.
Origination to disbursement, on one system of record.
One spine, three altitudes
Design it once. Watch it run. Do the work.
Most operations tools pick one of these and bolt the others on. TerraTrade keeps them as three views of a single process, which is why the deal in front of you and the process on the whiteboard never disagree.
-
Design
What the process is
Lay out the steps: who does each one, in what order, what has to be true before the next begins, and how long it may take. Different client types, countries and funding partners get different routes through it. This is configuration, not a release — operations change it without waiting for engineers.
Journey template
-
Run
Where a deal actually is
Every live deal walks the process it was started on, and keeps walking it even if the template changes underneath. One screen answers the only question anyone asks: which step, whose turn, how long has it been sitting there.
Live instance
-
Do
The work someone picks up
Each step becomes a task with an owner, a deadline and the exact screen needed to finish it. Automated steps are tasks too — the system’s result is recorded on the task, so nothing happens invisibly and nothing is unattributable.
Task
Durability
Weeks-long processes that survive everything.
The hard part of onboarding isn’t any single step. It’s waiting three days for a customer, sending a reminder, then carrying on exactly where you stopped — a thousand times, without dropping one. Scripts and scheduled jobs lose that state. TerraTrade’s process engine doesn’t.
- Survives restarts
- Deploys, crashes and cloud incidents don’t reset a deal. The process resumes mid-step with its history intact.
- Retries on its own
- A credit bureau that times out is retried with backoff. A person who doesn’t respond is reminded. Neither needs anyone to notice.
- Clocks that know your week
- Deadlines run on business hours and holidays per region, so a Friday-evening handoff isn’t overdue on Saturday morning.
- Replayable history
- Every state change is journaled. A stuck deal can be inspected step by step rather than guessed at.
- Request sent
- Waiting on client — day 3
- Reminder issued
- Document received
- Review resumed
Evidence and decisions
Documents have a life, not a folder.
A document store tells you a file exists. It doesn’t tell you whether anyone checked it, whether it’s still current, or what was decided because of it. Every document here moves through a defined lifecycle, and the decision it supports is stamped onto the record.
-
Required
The process says this deal needs it, and who must provide it.
-
Uploaded
Received from the client portal, an email, or an integration.
-
Read
Fields extracted automatically and cross-checked against the others.
-
Reviewed
A person confirms or corrects the extraction, with a reason on record.
-
Approved
Accepted, with a freshness clock — credit information expires on schedule.
Decisions are as-of, not current
When an analyst clears a counterparty or a country, the record keeps what they decided, when, and on which evidence — not just today’s status. That distinction is the difference between a system you can be audited on and one you can only apologise for.
Integrations
The unglamorous moat.
Every external check is a small, dull, multi-week project: its own authentication, rate limits, data mapping and per-country quirks. They’re already built, and they run inside the same process as everything else — so a failed check is a retried step, not a dropped ball.
- 01 Credit and company data
- Company registries and credit bureaux, with report freshness enforced by the process.
- 02 Document AI
- Extraction and cross-validation across invoices, bills of lading, purchase orders and shipping records.
- 03 Screening
- Sanctions and politically-exposed-person checks through a specialist screening provider, at onboarding and on a schedule after it.
- 04 Documents out
- Term sheets and agreements generated from templates, with signature fields placed automatically.
- 05 E-signature
- Signature requests sent and tracked, with completion signalled back into the process.
- 06 Your own credentials
- Run any integration on your own contract and keys instead of ours, per tenant.
Tenancy and brand
Your brand, your clients, our rails.
Multi-tenancy here means isolation in the database, not a filter in the application — a query that forgets to scope itself returns nothing rather than someone else’s book.
- 01 Row-level isolation
- Enforced per tenant and per company by the database itself, underneath the application.
- 02 Roles and bundles
- Permissions grouped into bundles and assigned by role, so operations, credit, clients and funders each see only their slice.
- 03 Your brand and domain
- Logo, palette and domain per tenant, on a client portal your customers recognise as yours.
- 04 Invite-only access
- Staff sign in with a password or passkey, client users by magic link, and enterprise clients through their own identity provider.
Audit
When someone asks what happened in March.
For a regulated lender the audit trail is not reporting, it is the product. Every step of a workflow is journaled as it runs and every decision is stamped onto the record it belongs to, rather than reconstructed afterwards from whatever the database happens to hold today.
- 01 Who approved what, when, and the reason they gave
- 02 Which document or check the decision was based on
- 03 Every workflow state change journaled and replayable, step by step
- 04 Exports an examiner can read without a walkthrough
Next
See it on your own process.
The fastest way to judge this is to bring us one of your own onboarding cases — the awkward one — and watch it laid out as a journey. Forty-five minutes, no slides.
- A walkthrough on your process, not a canned demo
- Straight answers on what isn’t built yet
- Weeks to a live programme, not a two-year build