Ramp Payment Provider

Journeybee tracks what you owe your partners. Ramp is what pays it. Connect Ramp and Journeybee turns your approved commissions and spiffs into draft bills in Ramp Bill Pay, one bill per payment, addressed to the Ramp vendor you have linked to each partner or person. Your finance team approves and pays those bills in Ramp as they would any other bill, and Journeybee tracks each payment through to Paid.

Where to find it: Go to Settings, then Integrations. Ramp sits under the Payment section. Bills are created from the Payments page.

Who can use this: Admins only, on a paid plan, with the Payment tracking module enabled. Partners never see any of it.

How it works

Ramp does not know who your partners are, and Journeybee does not hold your money. The integration joins the two with three pieces:

A connection. You sign in to Ramp once and choose which Ramp entity pays partners and in which currency.
Recipient mappings. Each partner company, team member or partner contact you want to pay is linked to a vendor record in Ramp. Journeybee suggests matches, you confirm them.
Bills. From the Payments page you pick approved payments and Journeybee creates and submits a draft bill in Ramp for each one. Approval and payment happen in Ramp. Ramp tells Journeybee when the bill is paid, and the payment moves to Paid.

Journeybee only ever asks Ramp for permission to read your business, entities, vendors and bills, and to create bills. It cannot approve a bill, pay a bill, or create a vendor.

Before you start

You need a Ramp account with Bill Pay, and an entity with a funding account in the currency you pay partners in. Journeybee can pay in USD, EUR, GBP and CAD.
Every partner or person you want to pay needs a vendor record in Ramp already, with a default payment account in the currency you will pay them in. Journeybee links to vendors, it does not create them.
Someone in Ramp needs permission to approve and pay bills. Journeybee only submits drafts.
Your commission rules should already be in place, since payments are generated from them. See Commissions.
Ramp is enabled per account. If you are an admin and do not see the Ramp card, contact Journeybee support.

Connecting Ramp

Go to Settings, then Integrations, and click the Ramp card.
Click Connect. You are sent to Ramp to sign in and review the permissions Journeybee is asking for.
Approve the connection. You land back on the Ramp configuration page with the message Ramp account connected.

The Connection card at the top of the page shows the connection status, authorisation, webhooks, connected entity and the date you connected. Wait for Webhooks to show Active before you create any bills. That normally takes a few seconds, and until then the Payments page tells you Ramp is still getting ready.

If you cancel on Ramp's side you see Ramp connection was declined. If you take too long, The Ramp connection request expired or was invalid. Either way, click the card and connect again.

Configuring Ramp

The configuration page has three sections. Work through them in order.

1. Ramp payment settings

Ramp entity: the entity whose funding account pays the bills.
Currency: the currency partners are paid in. It defaults to your company currency, and the list only offers currencies the chosen entity has a funding account for. Ramp picks the funding account itself when it pays, so there is nothing to choose there.

Click Save. Changes apply to future payouts only.

2. Match keys

These decide what the matching job compares when it suggests Ramp vendors for your recipients. They save as soon as you change them.

Partner match field: Name, Primary domain, Email or Website of the partner company.
Individual match field: Email or Name of the team member or partner contact.

Pick whichever field you know is filled in on both sides. Email or domain is usually more reliable than a name.

3. Recipient mappings

The Partners tab lists your partner companies. The Individuals tab lists your own team members and your partner contacts, which is where spiff recipients live.

Click Run matching. Journeybee compares your recipients with your Ramp vendors using the match keys above and reports Matching complete: X of Y recipients suggested.
Suggested links show an amber Suggested badge. Hover it to see how it was matched and how confident the match is. Click the tick to confirm a suggestion, or the cross to remove it.
For anyone without a suggestion, type in the Ramp vendor column to search your Ramp vendors and pick the right one. A vendor you pick by hand is confirmed straight away.
To confirm in bulk, switch the filter to Suggested, check the list, and click Confirm all suggested.

Only confirmed mappings are paid. A suggested mapping that was never confirmed is skipped at payout time.

Two rules apply to every link. The recipient must be active: a partner that is invited or accepted and not offline, or a contact or team member that has not been archived or disabled. The vendor must have a default payment account in your configured currency, otherwise you see That Ramp vendor's currency doesn't match your configured currency.

Switching payments to Ramp

On the Payments page, set Payout method to Ramp. If you see Ramp is not fully configured yet, go back and complete the payment settings above. Only one payout method is active at a time, so if you were paying through XTRM this switches you over.

Creating bills in Ramp

Approve the payments you want to pay. Tick the checkmark in the Approved column. Only approved payments are eligible.
Click Create Ramp Bills at the top of the Payments page and select the payments to include. The Vendor links section warns you about any recipient that is not yet linked to a Ramp vendor.
Click Create draft bills in Ramp. Journeybee confirms Queued: draft bills are being created in Ramp and lists anything it skipped, with the reason.
Approve and pay in Ramp. Each payment becomes one draft bill in Ramp, already submitted for approval. Your Ramp approvers handle it from there.

Each bill is addressed to the linked vendor, drawn on your configured entity, and raised in the payment's own currency. The invoice number is JB- followed by the Journeybee transaction number, the memo names your company and whether it is a commission or a spiff, the due date is the payment's due date, and there is a single line for the full amount.

Payments show Processing from the moment they are queued until Ramp reports the bill paid, then Paid. Open a payment to see the step-by-step timeline, the status exactly as Ramp reports it, and an Open in Ramp link to the bill.

What gets skipped, and why

No Ramp vendor is linked to this recipient: map the partner or person on the configuration page.
The linked Ramp vendor is suggested but not yet confirmed: confirm the mapping.
The linked Ramp vendor has no default payment account: add one in Ramp.
The linked Ramp vendor belongs to a different Ramp connection: you disconnected and reconnected Ramp. Run matching again and confirm.
PLN is not one of your Ramp payout currencies (or any other currency outside USD, EUR, GBP and CAD, or one your entity cannot pay): pay that payment another way, for example Mark as Paid.
Recipient could not be resolved: the partner, contact or team member behind the payment has been archived or removed.

Paying in more than one currency

The currency in your Ramp settings is the default, not a limit. Each bill is raised in the currency of its payment, so a EUR commission and a GBP commission queued together become a EUR bill and a GBP bill. The only condition is that your chosen entity has a funding account in that currency. Payments in a currency the entity cannot pay are skipped and named in the result, and you can settle them another way.

When a payment needs review

Journeybee never marks a Ramp payment as failed on its own. If anything looks wrong, the payment is flagged Needs review and stays locked so it cannot be sent twice. Common reasons:

The bill was rejected, archived or deleted in Ramp.
The amount Ramp reports does not match the payment.
The payment was held by Ramp, for example awaiting release.
Ramp was disconnected while the payment was in flight.

Open the payment to see the exact reason, then check the bill in Ramp. The review dialog offers two choices: Keep locked, which leaves the payment as it is, or Acknowledge completed if you have confirmed in Ramp that the money went out. Neither one sends anything to Ramp.

Cancelling a payout

Open the payment and use the cancel action. What it does depends on how far the payment has got:

Before the draft exists in Ramp, the action is Cancel provider payout. Journeybee stops the payout, nothing is sent to Ramp, and the payment goes back to To be paid.
Once a bill exists in Ramp, the action is Request cancellation. Journeybee cannot stop a bill Ramp already has, so this flags the payment for review and keeps it locked. Cancel or archive the bill in Ramp yourself if it is still unpaid.

A reason is required either way, and is kept on the payment.

Disconnecting Ramp

Open the Ramp card under Settings, then Integrations, and click Disconnect on the Connection card.
Confirm Disconnect Ramp?

The disconnect is immediate. Journeybee removes its webhook from Ramp, revokes its access, deletes the stored credentials, archives your recipient mappings, and sets your payout method back to Manual. Your payment history stays exactly as it was.

Any payment still in flight is flagged Needs review with the reason The Ramp connection was disconnected while this payment was in flight. Ramp may still pay those bills, so check them in Ramp before you do anything else with them.

You can reconnect at any time. Because the old mappings were archived, run matching again and confirm your recipients before creating bills.

Troubleshooting

I cannot see the Ramp card. Only admins see unconnected integrations, and Ramp has to be enabled for your account. Contact Journeybee support.
"Ramp is still disconnecting. Try connecting again shortly." A previous disconnect is finishing. Wait a moment and connect again.
"The connected Ramp account didn't match what was expected." You signed in to a different Ramp business than the one this connection was made with. Disconnect, then connect again with the business you want.
Create Ramp Bills is greyed out. One of: the payout method is not Ramp, webhooks are not yet Active on the Connection card, the payment settings are incomplete, or there are no approved, unpaid payments.
"Ramp isn't fully configured yet. Finish the payment settings above first." You tried to link a recipient before saving an entity and currency. Save the payment settings, then map.
A currency shows as "not payable by this entity". The entity no longer has a funding account in your saved currency. Pick another currency, or add a funding account in Ramp and save again.
A payment is stuck in Processing. Open the bill in Ramp. Most often it is waiting for approval or payment there. Once Ramp pays it, Journeybee updates within seconds, and in any case checks with Ramp every hour. If the bill shows paid in Ramp and the payment is still Processing an hour later, contact support.
"Disconnect did not complete" on the Connection card. A disconnect was interrupted part way. Click Retry disconnect and it picks up where it left off.
"Ramp is temporarily unavailable. Try again shortly." Ramp did not answer. Wait and retry.

Good to know

Journeybee submits drafts. Approval and payment happen in Ramp under your normal Bill Pay rules, so nothing leaves your account without a Ramp approver saying so.
There are no wallets, no beneficiary registration and no partner-side sign-up with Ramp. Partners are paid to the payment account on their Ramp vendor record, exactly as any other vendor.
Spiffs go to individuals. Map the person on the Individuals tab. See Spiffs.
You can have both XTRM and Ramp connected, but only one payout method is active at a time. See XTRM Payment Provider and Payments.
Ramp payouts raise payments.processing, payments.completed and payments.failed events for your own integrations. See Developed Integrations.
There is no sandbox switch. Journeybee connects to your live Ramp business.
For the other tools you can connect, see Integrations.