Weel Integration | DualEntry

Weel

Overview

Australian card spend arrives with GST attached, a budget it was drawn against, and a category that someone still has to turn into a GL account. Weel controls the spending and the approvals. DualEntry owns the ledger the spending has to land in. The connector between them does the coding.

A new or settled card transaction in Weel, or an approved expense, triggers the sync. The connector retrieves the record, applies your category-to-GL and team-to-dimension mappings, then posts the result to DualEntry: the net expense debits the mapped GL account, the Weel card-payable account is credited, and the GST posts as its own tax line at the amount and rate Weel recorded. The Weel transaction ID lands in the external reference field, the merchant becomes the line description, and the cardholder maps to an employee or vendor reference. At settlement, each posted transaction is matched to the Weel card statement so the card-payable balance in DualEntry reconciles to Weel.

The flow is inbound only: Weel spend moves into DualEntry, and DualEntry does not push your chart of accounts or journal entries back to Weel. Weel stays the source of truth for the transaction itself, the cardholder, the budget and the GST on it. DualEntry stays the source of truth for the chart of accounts, tax treatments and the posted ledger. Edits made in Weel post as adjustments rather than duplicates, so the DualEntry balance tracks the current state of the Weel transaction.

This connection is delivered by APIWorx, a managed integration platform that sits between Weel and DualEntry and runs the connector as a managed service on its own infrastructure.

Data synced

The integration syncs the following data types:

Card Transactions

Weel → DualEntry

Card Refunds and Adjustments

Weel → DualEntry

Approved Expenses and Reimbursements

Weel → DualEntry

GST and Tax Lines

Weel → DualEntry

Categories, Budgets and GL Mapping

Weel → DualEntry

Teams and Dimensions

Weel → DualEntry

Settlement and Reconciliation

Weel → DualEntry

Key Features

  1. GST on its own line
    The connector reads the GST amount and rate on each Weel transaction and posts a matching tax line in DualEntry. The mapped GL account receives the net expense and the tax treatment receives the GST, so tax is never rolled into the expense figure.
  2. Categories and budgets mapped once
    Every Weel category or budget is mapped to a DualEntry GL account and reuses that mapping on every transaction. A category with no mapping posts to a default holding account and is flagged rather than blocking the sync.
  3. Teams as dimensions
    If you track spend by department or project, map each Weel team to the corresponding DualEntry dimension. Mapped transactions and reimbursements then carry that dimension through onto the posted entry.
  4. A card-payable balance that reconciles
    Each charge debits the mapped expense account and credits the Weel card-payable account. Settlement events match posted transactions to the Weel statement, so the payable balance in DualEntry tracks Weel without a manual month-end comparison.
  5. Refunds and edits as adjustments
    A refund reverses the original charge against the same accounts, and an edit in Weel comes through as an adjustment instead of a second entry. The DualEntry balance reflects the current state of the transaction, not its first version.
  6. Reimbursements alongside card spend
    Approved employee expenses post as expense entries attributed to the cardholder and the budget they were drawn against, and carry through to your AP and GL workflows the same way a manually entered card expense would.
  7. Exceptions you can see
    Unmapped categories, amount or tax mismatches, and failed postings are all surfaced through the APIWorx portal and logged with the Weel transaction ID. A GST figure that does not match the mapped treatment raises an exception rather than posting something that would not reconcile, and transient failures retry automatically.
  8. How the connection is made
    Setup authorizes APIWorx against your Weel organization for read access to card transactions and expenses, and against your DualEntry company. APIWorx maintains and monitors the connector on its own infrastructure and retains the logs for troubleshooting and audit.

FAQ

Is this integration handled by third parties?
Yes. The connection is delivered by APIWorx, a managed integration platform that sits between Weel and DualEntry and runs the connector as a managed service on its own infrastructure, with continuous monitoring and logging.

How does integrating DualEntry with Weel help my business?
Weel card spend and approved reimbursements arrive in DualEntry already coded to the GL account you mapped, with the GST amount and rate on a separate tax line and the cardholder, team and budget carried through onto the entry.

Does data flow back from DualEntry to Weel?
No. The flow is inbound only: Weel spend moves into DualEntry, and DualEntry does not push your chart of accounts or journal entries back to Weel.

How is GST handled on Weel transactions?
Weel is an Australian platform and most transactions include GST, so the connector reads the GST amount and rate on the transaction and posts a matching tax line in DualEntry.

How often does the integration sync?
Transactions sync near real time on Weel events where webhooks are available, and on a configurable batch schedule otherwise.

What happens if a transaction fails to post?
The connector does not fail silently. Every exception is surfaced through the APIWorx portal and logged with the Weel transaction ID, across three cases: an unmapped category, an amount or tax mismatch against the Weel statement, and a failed posting to DualEntry.