Skip to main content

Getting started — buyers

This page is a practical sequence for a buyer organisation coming onto Expereon. Exact screens and permissions depend on your roles and rollout phase.

1. Create the organisation and first users​

  • Register the buyer organisation with company details and complete email verification and any terms acceptance required during signup.
  • Sign in using your chosen method (for example password with optional two-factor authentication, or supported social login where enabled).
  • Complete the organisation profile so compliance and counterparties see consistent legal and contact data.

Hardening access early (two-factor authentication, password hygiene) reduces risk as financial activity ramps up.

2. Invite your team​

Administrators invite users and assign roles so that only the right people can change trust settings, approve invoices, or manage API keys. Non-admins may request invites through an approval path where that is enabled.

Ongoing administration includes deactivating leavers, reactivating returning staff, and reviewing user activity when you need an audit trail.

3. Organisation settings that affect payments​

From organisation settings, administrators typically:

  • Maintain company and contact details and branding such as an organisation avatar where supported.
  • Choose defaults for payment behaviour, such as the preferred payment source for new approvals (for example collateral versus available balance, where the product exposes that choice).
  • Open auto-approval configuration in one place while still honouring per-seller trust rules where applicable.
  • Review organisation-level activity and understand how organisation deletion requests work if you ever need to wind down.

4. Connect funding and understand balances​

Before invoices can be approved with confidence, finance connects payment providers or banks per currency as supported by your rollout.

You will:

  • Connect a provider for each currency you operate.
  • Deposit into available balance, withdraw when returning liquidity to your bank rails, and move funds between available and collateral when your treasury policy requires it.
  • Monitor collateral utilisation so new seller commitments remain within policy.
  • Use funding history filters and exports for month-end and reconciliation.

Remember the conceptual split from Key concepts: available is for flexibility; collateral backs obligations you have approved under that model.

5. Connect sellers​

Commercial relationships are mirrored in the product:

  • Add a seller relationship or invite the seller by email.
  • Accept incoming connection requests when sellers initiate them.
  • Configure trust (manual versus automatic paths, thresholds, caps) and collateral allocation models appropriate to each seller.
  • Optionally enable auto-accept of invoices where that matches your risk appetite.

You can deactivate, reactivate, or archive relationships as partnerships change.

6. Configure trust modes globally​

Organisation-wide trust settings express your default posture—manual approval for everything versus automation with limits. Complement those defaults with per-seller nuance from the previous step.

Pausing automation temporarily is a first-class concept when markets or incidents demand human review.

7. Wire booking reports to automatic invoices​

Most programmes expect booking data from your own systems to drive finance. Plan early for Integrations:

  • Issue API keys and test in sandbox with realistic single and batch booking payloads.
  • Subscribe to webhooks so downstream systems know when an invoice was auto-created or changed state.
  • Use API logs to prove parity between your booking store and Expereon’s invoice queue.

Where sellers also send booking or fulfilment updates via API, align on who owns which feed so the same reservation is not double-submitted.

8. Run the first invoices​

Move to Invoices and payments for the full loop: booking-driven creation, buyer review, approval, settlement, disputes, and refunds.