# Money leaves on your rule, invoices settle themselves URL: https://www.orla.finance/en/product/money Markdown twin of that page. Append `.md` to any Orla page URL to get one. Bills go out in one batch under your rule; invoices take a card, a transfer or a stablecoin. #### Bills to pay What do we owe, what is late, what waits for me? - Bills by status, with the ones waiting for your approval on top. - Accept, reject, set monthly, pay a selection, attach the paper; tax and dates in the panel. - An expense with no paper gets a self-billed invoice, kept on the payment. - A bill flips itself to paid when the matching arrival lands. - Before a bill is paid the book looks for one it already has: the same number written differently (INV-007 and inv 7), the same amount from that supplier inside ninety days under a new number, a close number with a rounded amount, and money that already went to that payee for that sum on any rail. Each match says what matched and whether the older one is paid. - Nothing is decided for you: the verdict is two presses, this is a duplicate or this is a different bill, and both papers stay. A supplier who bills the same amount every month is not a duplicate. For: Office manager, Accountant, Founder. #### Payments and batches Who signs, and what leaves when? - A queue for signature with an approval threshold and the number of signatures it takes; the person who prepared a payment never signs it themselves, and the rule sees to it. - Up to 200 payouts per batch, on the Scale and Enterprise plans: CSV preview, duplicate warning, autosave, templates. - The rule checks the batch total, so it cannot be dodged by slicing. - The assistant may put a payment in the queue and never signs it. - Amend a payment after approval but before the money leaves. - Pay from your own bank, and each rail names where its guarantee sits. Revolut Business: the consent carries no right to pay, so a prepared payment waits inside Revolut for a person on your team. Mercury: the token can only request a payment, and an admin approves it in Mercury's own queue. Airwallex: the run lands as a draft batch that your people submit and approve in Airwallex; Orla never submits one. - Slash has no drafts, so nothing is created there until a person with the right to release payments presses Send via Slash after the quorum in Orla, and your own approval rules in Slash stand behind that press. From a Safe, Orla proposes and the owners sign and execute in Safe{Wallet}; Orla never signs as an owner and never executes. - On each of the bank rails the access is one you grant yourself, with exactly the rights the form lists, a ceiling per payment is set when you connect, and the expense is booked only once the bank says paid. The rails are switched on space by space. - This does not look like you: a line under a payment that is far above what the payee is usually paid, a large first payment to a payee the book has never paid, or the same sum to the same payee twice within a week. It explains, it never blocks: signing works exactly as it did, and nothing is held up. For: Founder, Finance lead, Treasury. #### Cards Can each person have a card with a ceiling? - Virtual cards from one prepaid balance, topped up in USDT or USDC. Visa or Mastercard is chosen once, when the card is issued; both spend the same balance, and the choice costs the space nothing. - A card per person with a ceiling, freeze and block, the issuer's history checked against what you allocated, so a stray charge shows up the same day. - A card is issued only after the holder opens their own link and confirms, and cards issued now ask the holder for no identity documents. - A top up gets a deposit address that is yours while it is open, and it is credited by that address, not by the amount: more or less than the figure shown, USDC where you chose USDT, or two transfers are each credited, minus the fee said up front. A top up still waiting for its transfer can be cancelled by an owner or an admin; one the money has already reached cannot. - An agent can hold a card too. On a card issued now the balance loaded onto it is the whole limit: the card carries no merchant rules and no ceiling per payment, and Orla refuses to save rules nobody would enforce, so load only what the agent may spend. - Refunds are answered in the books on their own. For: Founder, Team member, Office manager. #### Invoices and quotes Who owes us, what is late, what arrived? - Four figures as filters: owed, overdue, received this month, paid without an invoice. - Recurring invoices, reminders, and an invoice that marks itself paid when money lands. - Paid by card via your Stripe, by transfer or in stablecoins; a quote becomes the invoice. - A credit note corrects a sent invoice as a second document, never an edit. - Who owes you is one line per client, not per invoice: what they owe, how late the oldest is, the reminders sent and whether they answered, the day they promised, and one next step with its reason, worked out by Orla rather than by the model. Write it down records the promised day; Send it mails the same reminder the schedule sends, on your press, and refuses when the client asked not to be written to. - The invoice mail names you in the subject and a reply reaches your billing email. The From line stays Orla on purpose: a mail about money cannot pretend to come from someone else. For: Finance lead, Office manager, Contractor. #### Contracts What did the contract promise, and what is not billed yet? - The assistant reads the signed file; monthly fee and milestones become the schedule of invoices to send. - Not billed yet, shown per contract; addenda accepted into the schedule; a quote or an order raised from a framework agreement without retyping the terms. - Rate cards price by unit or by order; a changed file is read again on its own. For: Founder, Finance lead, Office manager. #### Pay links How do I ask for money without an invoice? - A request by link, and a permanent payment address for the space. - Links expire; a machine gets a price instead of a page (x402). - On your @handle page a visitor names an amount and gets a link of their own. For: Contractor, Office manager, Founder. #### Loans and debts Who owes whom, and when? - Loans with a schedule: who owes you, whom you owe, and the nearest obligations on both sides. - Repayments are linked to the rows that paid them. - Rate changes and prepayment rebuild the schedule; only interest counts as cost. For: Founder, Finance lead, Accountant. #### Calendar What has a date, and what balance does it leave? - Everything dated on one page: overdue, this week, coming in, month-end balance. - Contracts add what they promise; a row that looks recurring gets a hint. - The forecast names the low point and its day; unpriced rows are listed, not guessed. - By date or By series: every repeating charge once, the plans you added and the series found in history, each with its share of a month and the date of the next charge, and how much leaves in the next 30 days. - Ask what got more expensive: the last charge against the typical one before it, in the currency the supplier bills in, so a month with one extra seat does not read as a rise. One press writes the new price into the plan; nothing here cancels anything with the supplier, which only the supplier can do. - Ask what you pay this week: the signing queue, the calendar's dated obligations and the cash forecast come back as one order, each row marked fits or move, with the condition named beside it: it fits if Acme pays on the 15th. A card postpones one payment and never brings one forward, and the supplier's own due date never moves. For: Office manager, Finance lead, Founder. #### Earn and borrow Can idle stablecoins earn without handing over the keys? - Aave v3 positions per wallet with their rates; Orla never holds a key. - Calldata prepared unsigned, the health factor checked, a quorum on the large ones. - Liquidation risk is watched hourly; borrowing stays off without that watch. For: Treasury, Founder, Finance lead.