A payment needs a trade record
A payment confirmation tells you that money moved. A useful trade record helps explain why, what it covered, and what still needs attention.
Imagine a supplier fulfilling a purchase order in two deliveries. The buyer pays a deposit, then settles several invoices in one transfer. A payment confirmation records the transfer accurately. It does not, on its own, explain which delivery was accepted, how the deposit was allocated, or whether anything remains unpaid.
This ordinary example shapes how we think about ARRUS. Settlement is the first product focus, but the useful unit of information is the trade. A payment needs a connection to an agreement, the parties involved, and the evidence of what happened. Without those connections, someone has to reconstruct the story each time a question arrives.
Keep the relationships visible
A trade record should connect purchase orders, invoices, delivery evidence, and payment references without pretending they are interchangeable. An order describes an intention. An invoice asks for payment. Delivery evidence describes a physical event. Settlement records a financial event. They can support one another while still telling different parts of the story.
The links between them matter as much as the files. A payment may cover part of an invoice or several invoices. A delivery may arrive in stages. Our design should make those allocations understandable and leave room for an unresolved balance. A neat screen is not useful if it hides how the numbers relate.
Let the record show uncertainty
Uploaded, reviewed, accepted, and settled describe different states. Attaching a document should not silently turn it into verified evidence. A useful record preserves its source, the scope of any review, and the questions still open. This gives the next person enough context to know what they can rely on and what they need to check.
Corrections also belong in the story. If an invoice changes or a buyer challenges a delivery, overwriting the old state makes later reconciliation harder. We would rather keep an understandable sequence of changes, with responsibility attached, than suggest that a trade moves neatly from pending to complete without any exceptions.
Design for the next person
The person arranging a delivery may be different from the person matching an incoming payment. A domestic procurement supplier needs that handover to work, just as an international commodity trader does. The documents and participants differ, but both need to understand which obligation a payment relates to without starting another search through messages.
This is the standard we want the product to meet: someone with appropriate access should be able to follow the trade, identify the evidence, and see the next unresolved action. Settlement closes a financial step. The connected record carries its meaning forward into the next conversation, the next reconciliation, and the next trade.
Explore the product thinking in practice.
Explore the settlement-first approach