Weel

Weel implementations are designed to be fast, with most businesses live in under a week once verification is complete.​

• Sign up and verification: Finance team signs up, completes know‑your‑business (KYB) and Visa verification so Weel can issue corporate debit cards and connect to bank funding.​

• Configure entities, budgets, and policies: Set up entities, cost centres, projects, user roles, approval workflows, card limits, and expense/reimbursement rules to match existing finance policies.​

• Connect accounting/ERP: Link Xero, MYOB, QuickBooks Online, NetSuite, or other systems so coded and approved expenses sync automatically into the ledger.​

• Issue cards and onboard users: Instantly create virtual/physical Visa cards for teams, projects, and subscriptions; invite employees to the mobile app and provide short training or video guides.​

• Pilot and go‑live: Run a short pilot (often a few days to one cycle) to validate card controls, approvals, and sync, then roll out broadly with support from Weel’s onboarding and customer success team as needed.​

Weel is highly configurable and can be tailored across cards, budgets, approvals, data, and entities to match specific business needs.​

• Policy-driven card controls: You can program your expense policy directly into each card with custom spend limits (weekly, monthly, one-off), maximum transaction sizes, merchant locks (MCC restrictions), and role-based permissions per user, team, project, or subscription.​

• Flexible budgets and entities: Weel lets you create budgets for teams, departments, projects, events, or any custom unit, with separate limits, top-up schedules, and owners, across multiple entities and cost centres in one account.​

• Custom approval workflows: Using Approval Policies and the Approval Rule builder, finance teams can design fully custom, rule-based workflows for card payments, bills, reimbursements, and budget increases, routing by amount, budget, role, or specific user sequences.​

• Custom fields and coding: Admins can add custom expense fields (e.g., project code, client, region), control which fields are required before export, and auto-apply custom fields to current and future budgets and subscriptions for consistent reporting and analysis.​

• Tailored AP and policy enforcement: In AP, you can configure invoice approval steps, coding rules, and export mappings per accounting system, while features like Express Expense/card blocking windows and out-of-policy flags are tunable to your risk appetite and compliance requirements.​

Weel’s main additional costs sit around cards and usage-based transaction limits, with no mandatory implementation or basic support fees for standard plans.​

• Subscription only, setup optional: Core pricing is a monthly platform fee (Basic, Premium, Enterprise) plus per‑user and per‑transaction charges once you exceed included users and transaction bundles; any setup/onboarding fee is listed as optional rather than standard.​

• Physical card fees: Issuing physical Visa cards incurs a one‑off charge of A$15 plus GST per card, while virtual cards are included in plan allowances.​

• Overage transaction fees: Basic and some bundles include a capped number of “business payments” or expense records per month, after which extra transactions are billed (commonly around A$0.50–A$0.75 per transaction, depending on plan).​

• FX and international use: Local AUD card transactions are free, but international card spend attracts a foreign transaction/FX margin (e.g., around 0.95% plus up to ~1% currency conversion fee).​

• Premium services and support: Higher‑tier plans (especially Enterprise) bundle extras like advanced features, CSV/ERP exports, and dedicated account management/consulting into the subscription; there is no separate line item for standard maintenance or support on public pricing.​

Weel offers a mix of structured onboarding, self‑serve education, and ongoing human support to help new users ramp quickly.​

• New customers typically get tailored onboarding driven by the finance team’s goals, including help configuring budgets, cards, approval policies, and accounting integrations; this is supported by local customer success managers for larger or more complex accounts. For day‑to‑day learning, Weel provides self‑serve video guides, webinars such as “Expense Management Deep Dive,” help articles, and getting‑started resources that walk users through connecting accounting software, using custom fields, and managing expenses efficiently.​​

• Ongoing support is available in‑app and online, with channels including chat and email, plus access to support representatives for troubleshooting card issues, workflows, and integrations. Finance and operations teams can also leverage analytics and reporting within the platform to monitor adoption and adjust training, while customer success works with them on process alignment and continuous optimisation as usage scales.

Weel secures customer data with strong encryption, hardened infrastructure, and multiple fraud‑prevention and access controls.​

• Weel uses 256‑bit encryption to protect data in transit and at rest and hosts customer information in highly secure AWS data centres located in Australia. Payment details are never stored directly in Weel; instead, they are tokenised and held by PCI‑DSS–certified banking partners, and funds are kept in trust at an Australian Authorised Deposit‑Taking Institution (ADI) to segregate customer money from operating funds.​

• Access security includes SSO support via SAML/OIDC so organisations can enforce central identity policies, automatic web‑session timeouts, and the ability to instantly deactivate and reissue virtual cards if they are suspected to be compromised. Fraud and threat controls use “the latest fraud detection and AI technology” to analyse user behaviour, blocking suspicious activity in real time, while Visa Zero Liability protection further shields customers from unauthorised card transactions. Weel’s privacy policy adds administrative, technical, and physical safeguards around personal data handling, acknowledging that while no system is perfectly secure, it applies reasonable controls to prevent unauthorised access, use, or disclosure.

Weel uses a continuous release model with frequent incremental updates across its web platform and mobile apps, communicated through a public product-updates hub and app-store release notes.​

• On mobile, the iOS and Android apps show a steady cadence of new versions every few weeks, mixing minor bug fixes and performance improvements with feature drops like tax invoice validation, biometrics for secure actions, and UX tweaks. These updates are delivered via the Apple App Store and Google Play, so customers receive them through normal app updates without separate installation steps.​

• For the web application, Weel documents new functionality in its Product Updates hub, where posts highlight recent feature releases (e.g., navigation redesigns, accounts payable enhancements, NetSuite receipt exports) and tag them by area such as Features or AP. Changes are rolled out directly to the multi‑tenant cloud service, so customers typically get new capabilities automatically, with update notes and occasional webinars or explainer content used to help admins understand and adopt the changes.

Weel keeps customer organisations as the effective owners of their spend and transaction data, while Weel owns the platform and may separately own fully anonymised datasets it derives.

• Data ownership: Weel treats expense, card, and transaction records as the customer’s operational data and acts as the processing platform, passing this data into your accounting system (e.g., via Xero bank feeds or CSV exports) so you remain the system of record for financial reporting. A separate Weel property (weel.live) specifies that any anonymised data it generates becomes Weel’s property, which is consistent with the general pattern that de‑identified, aggregated usage data can be used by the vendor for analytics and service improvement while identifiable customer data remains under customer control.​

• Data portability and export: Weel supports portability by allowing all transaction data to be exported to external systems. Expenses can flow automatically to Xero, MYOB, QuickBooks, and similar tools via direct integrations or be downloaded as CSV files from the Transactions page for import into any accounting or BI environment. Customers can also use Weel as a “platform of record” and stream or export rich transactional datasets—amounts, GST, merchants, GL codes, budgets, entities—to other tools, ensuring they are not locked into Weel for long‑term storage or reporting.

Weel is built for flexible scaling, letting organisations adjust users, cards, entities, and plan tiers as needs change, with changes flowing through the monthly bill rather than long-term lock‑ins.​

Organisations can add or remove users, budgets, cards, and entities at any time from the admin console, and Weel’s pricing model (Basic, Premium, Enterprise) charges a base platform fee plus incremental per‑user and per‑transaction costs once included bundles are exceeded, so spend naturally scales with activity rather than fixed headcount blocks. Moving up a tier (for example, to access more advanced approvals, AP automation, or higher transaction allowances) can be done mid‑term, with proration handled on the next invoice; scaling down generally takes effect from the next billing cycle, and Weel notes that bills may increase or decrease over time as active users and usage thresholds change. Multi‑entity support also allows finance teams to bring additional subsidiaries or cost centres into Weel without separate contracts, while still consolidating reporting and controls at the group level.​

Weel subscriptions auto‑renew but are designed to be cancellable without long lock‑ins or complex exit penalties.​

• Contract term and renewal: Business plans are billed monthly or annually and continue on an auto‑renewing basis until cancelled; Weel reserves the right to change fees on renewal with notice via its Terms & Conditions and pricing page.​

• How to cancel the software subscription: Admins can cancel by contacting Weel or managing their billing according to the Terms; once cancelled, access runs until the end of the current paid period, with no new renewal charged unless the account is reactivated.​

• Subscription card and vendor-level cancellation: For individual SaaS or vendor subscriptions managed through Weel, each has its own virtual card, which can be paused, frozen, or cancelled instantly from the Subscriptions dashboard without affecting other payments.​

• Effect of freezing/cancelling subscription cards: Freezing stops further charges temporarily; cancelling a subscription card immediately prevents any new debits from that vendor while leaving the main Weel account active.​

• Refunds and disputes: Charge dispute and refund handling follows Weel’s account‑management policies—customers are encouraged to contact the merchant first, then Weel support for card-related disputes, with outcomes governed by card‑scheme rules and Weel’s Terms.​

Weel positions itself as a secure, regulated fintech platform, but only a few concrete compliance anchors are publicly stated.​

• Financial and payments compliance: We issue Visa business debit cards in partnership with regulated financial institutions, and customer funds are held in trust with an Australian Authorised Deposit‑Taking Institution (ADI), aligning with Australian financial services and client‑money segregation requirements. Card data and payment processing are handled by PCI‑DSS–certified banking/payment partners rather than being stored by Weel itself, which means cardholder data protection falls under PCI standards at the partner level.​

• Security and privacy alignment: Weel’s security overview references “bank‑grade” 256‑bit encryption, AWS hosting in Australia, and modern fraud‑detection and AI‑driven monitoring, which are consistent with best practices for SOC 2–2-style controls, although a formal SOC 2 attestation is not explicitly named on public pages. Its privacy policy commits to applying administrative, technical, and physical safeguards, complying with Australian Privacy Act obligations for handling personal information, and using partners who follow comparable data‑protection standards.​