Money in, money out

Getting paid & paying out

Ask on the rail the payer actually uses, and let money leave through one door with a rule on it.

The public invoice page a client opens
Invoices

Every invoice, and where it stands.

Line items, a due date, and one link the client opens in a browser: no login, no app. Priced in the currency you quoted, whatever it settles in, and the list keeps outstanding, overdue and paid in view.

  • Your logo and your own numbering
  • A VAT or GST line when you need one
  • Partial payments tracked until the balance closes
Invoices with their statuses
Chasing

The reminders go out without you.

Four stages around the due date, each firing exactly once, each carrying the payment link. You stop being the person who has to ask.

  • The overdue alert reaches you even when client emails are off
  • A recurring invoice repeats itself weekly or monthly
  • When it lands, the client gets the confirmation and the PDF becomes their receipt
Reminders · INV-0001
Three days before the due dateSent
On the daySent
Three days afterQueued
Seven days afterWaiting
Each stage fires once. The client can be taken off the list, and the overdue alert still reaches you.
Statuses

The list answers before you ask.

Outstanding, overdue and paid across the top; drafts, partials and overdue as filters underneath. What is owed to you is one glance, not a spreadsheet.

Invoices with statuses and totals
  • Aging view: who owes whom, and for how long
  • A half-paid invoice says so, and keeps asking for the rest
  • Every column exports as CSV
Approvals

Money out goes through a door.

A claim or a bill enters, the approval rule decides who signs, and the batch leaves as one run.

SUBMITTED

Alex files a claim for $84 with the receipt attached.

AWAITING SIGNATURE

Over the $500 rule, so it waits for a second yes.

IN THE BATCH

Up to 200 payouts leave one account as a single run.

Payouts

Thirty transfers, one decision.

Collect bills, claims and payroll into a run of up to 200 payouts from one account. Every crypto address is screened before the money moves.

  • Anything over the rule waits for the second signature
  • Expense claims from the team go through the same door
  • A missing receipt is flagged before anyone approves
Payout run · August 5
27 payouts$8,340
Addresses screenedAwaiting second signature
You signed · Nina to co-signApprove
Crypto sends

You hold the key, so you press send.

Create a wallet in Orla or connect the one you use over WalletConnect. The transfer is signed in your browser and broadcast from there.

  • The seed is encrypted on your device with a wallet password
  • Passkey confirmation on the send
  • Payouts can be limited to whitelisted addresses
The send dialog: signed locally, passkey protected
Cards

A card per person, a cap per card.

Virtual Visa cards for the tools and the ads, topped up from the balance or straight from crypto, with a freeze in one tap.

  • A monthly cap the card stops at
  • 3DS codes delivered over Telegram
  • Every charge lands in the ledger already categorized
Studio · AdsVISA
•••• •••• •••• 7314
Alex11/29
Monthly cap$118 of $350
Top up fromUSDCBalance
Meta Ads · Advertising−$45.00
The specifics

What the documents carry.

Invoice railsBank transfer or stablecoins, the client picks
RemindersThree days before, on the day, three and seven days after
Partial paymentsTracked to the balance; overpaying is refused
Payment addressorla.finance/@you, up to ten accounts behind it
Payout batchUp to 200 payouts from one account in one run
ApprovalsA threshold with the signatures it needs, first match applies
ClaimsSubmitted with a receipt, decided, reimbursed from a space account
CardsMonthly cap, freeze, crypto top-ups, 3DS over Telegram
Pricing

Three invoices a month are free.

Send the first one today. Paid plans raise the limits when the work grows.