Owns the obligation and approval.
Confirms the commercial terms, checks the invoice and authorises the payment through its agreed approval process.
Settlement / The first product layer
ARRUS is being built to connect the buyer’s approval, the partner’s payment updates and the supplier’s receipt. Follow one example to see how the record comes together.
Fictional transaction. Select a stage to explore the proposed workflow.
The buyer checks the invoice against the order and delivery evidence, then approves it under its own payment terms.
Packaged food supply
Approved for payment
Responsibility stays visible
Confirms the commercial terms, checks the invoice and authorises the payment through its agreed approval process.
Links documents, approval records, partner status and reconciliation. This is the product workflow we propose to validate with a pilot.
Payment, banking, conversion and custody functions sit with the relevant partners. Their confirmations provide the evidence behind the displayed status.
Provides the agreed trade documents and payment details, follows the receipt status and raises discrepancies against the same reference.
How the rails fit
The proposed infrastructure includes stablecoin-based settlement, custody and conversion through partners, with banking connections for receipt where required. The parties, authorisations, currency and evidence are specified for each pilot.
The example above shows the invoice and receipt in Indonesian rupiah. It illustrates the business workflow; it does not prescribe the intermediate settlement asset or claim that a particular partner route is already operating.
Start with a defined workflow
Choose a small supplier group, map the payment process and agree what success should look like.
Discuss a supplier-payment pilotOnboarding · Receipt visibility · Reconciliation