Connect Slash

Slash in your books, sent only on your press

The main account and every virtual account arrive with their statements. Slash has no drafts, so a transfer goes only when someone on your team presses Send via Slash.

Book a demo Start free

Here the last press is in Orla, not in Slash. Rolling out space by space.

What lands in the book

Main and virtual accounts, each with its statement

Named Slash · Operating and so on, after the account's own name.

Each account arrives with its available balance; rename any of them and your name is kept. Balances refresh about once an hour.
The statement arrives by itself: about a month back when you connect, hourly after that, and only posted movements. A pending one keeps its place until it posts.
A transfer between two of your own Slash accounts is one transfer, not an expense and an income.
A payment sent from Orla is not booked twice: when the statement brings the bank's version of it, the payment you already have gains the bank's reference and date.
Receive shows the account and routing number as Slash states them.

The key you give us

A key under one legal entity, with nothing on cards

Made in your own Slash dashboard. The form lists the permissions one by one.

What to create: An API key under the legal entity you want to connect, with read on accounts, balances and transactions, read and write on recipients and transfers, and nothing on cards. If the key can act for more than one entity, you paste the entity id too.
What that key could do: Create a transfer, because that is what paying from Slash takes. This is why the rule below is a press by a person, and why your own approval rules in Slash matter.
Checked before it is saved: Tried against Slash first. Once accepted it is stored encrypted and never shown again, not to you and not to us.
If Slash stops accepting it: The row says so, and Update key takes a fresh one while keeping the accounts, their history and the ceiling.
The ceiling: A ceiling per payment is set when you connect, and a payment above it is not sent.
A sandbox: Connects Slash's test environment instead of real money.

Who presses last

Slash has no drafts, so the press that sends is in Orla

A transfer created in Slash is a real transfer. Everything below follows from that.

After the approval: The payment waits as approved and nothing has moved. No transfer exists in Slash yet.
Who presses: Someone with the right to release payments presses Send via Slash, the way a PayPal payout is sent. Orla then creates the transfer by ACH, domestic wire or international wire, whichever way the recipient is set up in Slash.
The second guard: Your own approval rules in Slash. You are asked to keep them switched on for outbound transfers when you connect. Orla cannot read them, so it cannot tell you whether they are on.
Pressing twice: Never sends twice: the same payment carries the same key, and Slash answers with the transfer it already made.
If Slash did not answer: The payment says so, cannot be cancelled, and asks you to press send again rather than pay another way.
When the expense is booked: Only when Slash reports the transfer completed. One refused, cancelled or returned in Slash is refused in Orla, and nothing is booked for it.
The payee: Must already be a recipient in your Slash. When it is not, Add payee to Slash first shows exactly what will be written into your account and adds it only after you confirm. Two recipients that could be the one meant stop the payment instead of one being picked.
A payment Slash reverses: Caught within the hour, flagged, announced to the owner and the admins, and netted by a compensating entry. A transfer unanswered for two weeks asks you to check it in Slash.
Disconnecting: Not while Orla has transfers in flight in Slash: wait for them to complete, or cancel them there first.

Questions

The questions a finance lead asks before connecting the bank

Can Orla send money from our Slash account?

Only on a press by your own colleague. Slash has no drafts, so a transfer created there is real: Orla creates one when a person with the right to release payments presses Send via Slash on a payment the space already approved. Your approval rules in Slash are the second guard, and Orla cannot read them.

What happens if Send via Slash is pressed twice?

One transfer. The same payment carries the same key, and Slash answers with the transfer it already made. If Slash did not say whether the transfer was created, the payment says so, cannot be cancelled, and asks you to press send again rather than pay another way.

When does a Slash payment become an expense in the books?

Only when Slash reports the transfer completed. One refused, cancelled or returned in Slash is refused in Orla and nothing is booked. A transfer Slash reverses after completion is caught within the hour, flagged, announced to the owner and admins, and netted by a compensating entry.

Pay from another bank

Connect Slash, and know exactly which press sends

Your own account, reached with a key you made yourself; the money never passes through Orla. This rail is being switched on space by space.

Mercury →: Orla requests a payment with a token that has no Send Money permission; an admin approves it in Mercury.
Airwallex →: Each currency as its own account, and a draft batch that a person submits and approves inside Airwallex.
Safe →: Read from the chain with its owners and threshold; Orla proposes as a delegate, never signs and never executes.

See it on your own books

Thirty minutes: we connect an account, drop a real bill in, and close a month together.

Book a demo or start free and connect one account